Partnering:Projects:BYOB:BuildSystemDesign: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 36: Line 36:
* build per check-in: triggers all builds changed by the check-in. Builds are broken up by repack so that they can be parallelized across the build slaves. We'll have a suitable idle timer in place to catch "oops, i missed one thing"-type errors.
* build per check-in: triggers all builds changed by the check-in. Builds are broken up by repack so that they can be parallelized across the build slaves. We'll have a suitable idle timer in place to catch "oops, i missed one thing"-type errors.
* one-off/single builds: can be triggered from the buildbot master directly, but we could also hook up a sendchange request to the webtool to accomplish the same thing.
* one-off/single builds: can be triggered from the buildbot master directly, but we could also hook up a sendchange request to the webtool to accomplish the same thing.
* re-generate all active BYOB repacks: this will likely be a custom sendchange that will generate a job per repack. This will be useful for security releases.
* re-generate all active BYOB repacks: this will likely be a custom sendchange that will generate a job per repack. This will be useful for security releases, and can be hooked up to the webtool.
* signing poller: looks for builds in an incoming directory, signs them, puts them into the final location.
* signing poller: looks for builds in an incoming directory, signs them, puts them into the final location.
canmove, Confirmed users
2,850

edits

Navigation menu