Closed Bug 1188473 Opened 6 years ago Closed 6 years ago
Create a gatekeeper Jenkins job to run the brick test
The brick test was implemented in bug 1139083, let's create a new jenkins job that runs right after the download build and then run the other job if it passes.
Review of the brick jobs. Jobs also triggers jobs that are neither in bitbar nor the brick test. So, for the Mountain View lab, the brick test would be ineffective. * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk.mozilla-central.nightly.download/ * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk.b2g-inbound.tinderbox.download/ * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk.mozilla-central.tinderbox.download/ Jobs that are okay to me: * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk.mozilla-inbound.tinderbox.download/ * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-spark.mozilla-central.nightly.download.tc/ These brick jobs are executed against Bitbar, even though bitbar is not mentioned in the name: * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.mozilla-inbound.tinderbox.ui.brick.sanity/ * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.b2g-inbound.tinderbox.ui.brick.bitbar/ * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.mozilla-central.tinderbox.ui.brick/ * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.mozilla-central.nightly.ui.brick/ * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-spark-319.mozilla-central.nightly.ui.brick.spark/ After taking a closer look, even the jobs that have an actual "bitbar" sibling, also run the brick test on bitbar. That's problematic we want to make sure that the bitbar is failing but not the lab, or the other way around. I think "sanity" is not necessary at the end of http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.mozilla-inbound.tinderbox.ui.brick.sanity/ Same thing for http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-spark-319.mozilla-central.nightly.ui.brick.spark/
Note: Bitbar hasn't been flaky for the last 3 days. That brick test passed, so the smoke job was triggered without any action from my side. As a consequence, unlike I said on Friday, I didn't change any brick job today. :Silne30, you can change every job mentioned in comment 1.  http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame-kk-319.mozilla-central.nightly.ui.brick/12/  http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame-kk-319.mozilla-central.nightly.ui.functional.smoke/404
Hey johan. Thanks for looking into these. The jobs are still failing but they are set up correctly now. Clearing NI.
Yes, that's due to bug 1198950. Since the brick has been fixed, there are some green runs, but still failures because of bug 1198950. http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame-kk-319.mozilla-central.nightly.ui.brick/ http://jenkins1.qa.scl3.mozilla.com/view/Bitbar/job/flame-kk-319.b2g-inbound.tinderbox.ui.brick.bitbar/ http://jenkins1.qa.scl3.mozilla.com/view/Bitbar/job/flame-kk-319.mozilla-central.nightly.ui.brick.bitbar/
The effect seen in bug 1198950 doesn't seem to appear very constantly. I finished up the brick job configuration. At that time, no test is red. Closing this bug, as the configuration is done.  http://jenkins1.qa.scl3.mozilla.com/view/Brick/
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.