Last modified: 2014-11-05 13:59:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T73740, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 71740 - Jenkins: integration-zuul-layoutdiff job says "No layout changes" when there are
Jenkins: integration-zuul-layoutdiff job says "No layout changes" when there are
Status: NEW
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-07 08:19 UTC by Krinkle
Modified: 2014-11-05 13:59 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2014-10-07 08:19:45 UTC
https://gerrit.wikimedia.org/r/#/c/165173/ reports

> integration-zuul-layoutdiff
> No layout change apparently.

Yet the job very obviously detects various significant changes:
https://integration.wikimedia.org/ci/job/integration-zuul-layoutdiff/1823/console
Comment 1 Antoine "hashar" Musso (WMF) 2014-11-05 13:59:20 UTC
The layout-diff job does a validation layout for HEAD and HEAD^ and then uses diff. Possible scenarii are:

- layout validations fail -> build failure
- diff -> build failure

- layout ok and no diff -> build success

That maps to:

success-message:
  'Please carefully review the Zuul layout difference before deploying/merging.'
failure-message:
  'No layout change apparently. Nonetheless, please carefully review before deploying/merging.'


We should swap them and change the 'Please carefully...' message to 'FAILURE difference is being introduced, please carefully review the difference'.


We can guarantee the layout is valid with the job integration-zuul-layoutvalidation and make it a parent of the layout diff in Zuul config:

 check:
  - integration-zuul-layoutvalidation:
      integration-zuul-layoutdiff

This way the layoutdiff would only be triggered after the layout has been validated, so we now a failure must be caused by diff exiting non zero, and hence a diff has been introduced.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links