Changes between Initial Version and Version 1 of ContinuousIntegration/FixYourDamnBuildSlave


Ignore:
Timestamp:
09/13/2012 02:31:51 PM (2 years ago)
Author:
exarkun
Comment:

junk

Legend:

Unmodified
Added
Removed
Modified
  • ContinuousIntegration/FixYourDamnBuildSlave

    v1 v1  
     1Sometimes things go wrong on a build slave.  This might be a network problem, or the disk might fill up, Twisted might even add a new dependency that's not available.  Any one of a million, billion things could happen that prevent the slave from completing the builds assigned to it.  For slaves running supported builders, this is a major problem.  Supported builders need to be running their builds all the time. 
     2 
     3If a slave running a supported builder stops being able to complete the builds assigned to it: 
     4 
     5  1. Contact the slave operator and request that the problem be addressed. 
     6    1. If there is a problem that the slave operator cannot address, raise it with the community at large for assistance. 
     7  1. Otherwise, if the problem is not resolved after one week, follow up with the slave operator about the problem. 
     8  1. If no solution is forthcoming within two days, contact the community at large to seek a replacement for the slave. 
     9  1. If there is no replacement offered within one week, remind the community about the request. 
     10  1. If there is no replacement offered within one further week, announce the de-support of the platform represented by the slave. 
     11    1. Adjust the buildbot configuration to drop the slave. 
     12    1. File a ticket, added to the milestone for the next release, for announcing the de-support of the platform with the pre-release. 
     13  1. If the pre-release announcement with its warning brings a replacement slave, add it to the build slave and announce the ongoing support of the platform if the slave can be made green without delaying the release.