Confirmed users
2,456
edits
ReleaseEngineering/Release build promotion: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Release build promotion (view source)
Revision as of 17:58, 16 March 2016
, 16 March 2016→How is this different?: we improve visibility of process too
m (→What is it?: linkify ReleaseEngineering) |
(→How is this different?: we improve visibility of process too) |
||
| Line 7: | Line 7: | ||
The previous release pipeline also started with builds produced and tested by CI. However, when it came time to do a release, we would create an entirely new set of builds with slightly different build configuration. These builds would not get the regular CI testing. | The previous release pipeline also started with builds produced and tested by CI. However, when it came time to do a release, we would create an entirely new set of builds with slightly different build configuration. These builds would not get the regular CI testing. | ||
Release build promotion improves the process by removing the second set of builds. This drastically improves the total time to do a release, and also increases our confidence in our products since we now are shipping exactly what's been tested. | Release build promotion improves the process by removing the second set of builds. This drastically improves the total time to do a release, and also increases our confidence in our products since we now are shipping exactly what's been tested. We also improve visibility of the release process; all the tasks that make up the release are now reported to Treeherder along with the corresponding CI builds. | ||
= Current status = | = Current status = | ||