1083234 - Ship-it should start a build automatically once the associated ci build is green

Status: RESOLVED DUPLICATE of bug 1288573

(Release Engineering :: Applications: Shipit, defect)

Description

[Lawrence Mandel [:lmandel] (use needinfo)]

The process flow that relman uses when building betas and releases is on commit, grab the commit tag, create the build definition in ship-it, wait for the ci build to complete (green), and then click do eet in ship-it. 

Instead of having a release manager wait for the green ci build, I think we can optimize this process better by submitting a build to ship-it with the condition that ship-it should start the build once the ci build goes green. This should be the default but we do need a way to override so that we can go to build sooner if required.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

A couple of issues we'd have to deal with:
* having some idea of when all the results were done
* if test failures are significant or merely intermittent

There's some functionality in self-serve for this already, eg 
  https://secure.pub.build.mozilla.org/buildapi/self-serve/mozilla-inbound/rev/b08a0ab5efdf
but we'd need to go back an check it. I think it allows orange state on tests, which seems a little poor.

Comment 2

[[e-mail] (:bhearsum)]

Mass component change for ship it bugs.

Comment 5

[Nick Thomas [:nthomas] (UTC+12)]

Duping forwards to the release-promotion equivalent bug.