rfc:travis_ci

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
rfc:travis_ci [2014/04/25 07:47] stasrfc:travis_ci [2018/03/01 23:48] (current) – RFC was accepted + typo carusogabriel
Line 3: Line 3:
   * Date: 2014-04-13   * Date: 2014-04-13
   * Author: Stas Malyshev (stas@php.net)   * Author: Stas Malyshev (stas@php.net)
-  * Status: Draft+  * Status: Accepted
   * First Published at: http://wiki.php.net/rfc/travis_ci   * First Published at: http://wiki.php.net/rfc/travis_ci
  
Line 12: Line 12:
 making changes that break something without us noticing. However, making changes that break something without us noticing. However,
 there's a problem with this setup, and the problem is that CI build is there's a problem with this setup, and the problem is that CI build is
-never kept in the green for more than a few days, the "normal" state+never kept in the green for more than a few days, the "normal" state
 of it is always failing. I think this situation is not normal and embarrassing for the project, and propose to institute a policy of it is always failing. I think this situation is not normal and embarrassing for the project, and propose to institute a policy
 to change it. to change it.
Line 46: Line 46:
 These policies would also apply to any future CI system we may introduce, such as [[Jenkins]]. These policies would also apply to any future CI system we may introduce, such as [[Jenkins]].
  
-For the changes committed to multiple branches, the RM of the lowest branch is considered responsible, but if he is unable to resolve the problem, the RMs for other branches can step in. +For the changes committed to multiple branches, the RM of the lowest branch is considered responsible, but if they are unable to resolve the problem, the RMs for other branches can step in. 
 ===== Proposed PHP Version(s) ===== ===== Proposed PHP Version(s) =====
 The policy would apply for all branches in active development or maintenance, starting with PHP 5.5.  The policy would apply for all branches in active development or maintenance, starting with PHP 5.5. 
Line 54: Line 54:
 Proposed votes are as follows: Proposed votes are as follows:
  
-<doodle title="Accept the description in this RFC as an official policy of the PHP project with regard to the tests" auth="user" voteType="single">+<doodle title="Accept the description in this RFC as an official policy of the PHP project with regard to the tests" auth="user" voteType="single" closed="true">
    * Yes    * Yes
    * No    * No
Line 61: Line 61:
 Choose one or more of the four options above of handling bad commits, keeping in mind that choosing particular option would be the decision of the RM.  Choose one or more of the four options above of handling bad commits, keeping in mind that choosing particular option would be the decision of the RM. 
  
-<doodle title="Choose one or more of the four options above of handling bad commits" auth="user" voteType="multi">+<doodle title="Choose one or more of the four options above of handling bad commits" auth="user" voteType="multi" closed="true">
    * Revert ASAP    * Revert ASAP
    * Revert after 1 week    * Revert after 1 week
rfc/travis_ci.1398412040.txt.gz · Last modified: 2017/09/22 13:28 (external edit)