Last modified: 2014-09-25 15:42:47 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 T73305, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 71305 - Convert puppetmaster sync cronjob to Jenkins job
Convert puppetmaster sync cronjob to Jenkins job
Status: NEW
Product: Wikimedia Labs
Classification: Unclassified
deployment-prep (beta) (Other open bugs)
unspecified
All All
: Normal enhancement
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-25 15:01 UTC by Bryan Davis
Modified: 2014-09-25 15:42 UTC (History)
9 users (show)

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


Attachments

Description Bryan Davis 2014-09-25 15:01:24 UTC
The beta cluster uses a cron job introduced in <https://gerrit.wikimedia.org/r/#/c/151099/> to fetch the latest operations/puppet.git upstream changes and rebase the local commits and cherry-picks on that new head. This works great except when it breaks due to an outdated cherry-pick in the local repo or a merge conflict with the new head and a local commit.

The current script has logging and a sane recovery method for dealing with this problem, but it does not have an alerting method. Additionally because it rebases once per hour it can sometimes be tricky to figure out exactly which locally applied changes are in conflict with which upstream changes.

I would like to see this process converted to a Jenkins job with a Zuul trigger on merges to the operations/puppet.git repository. This will allow us to see exactly which upstream merge first broke the rebase and also allow us to alert in the #-qa irc channel and possibly even #-operations when the rebase fails.
Comment 1 Greg Grossmeier 2014-09-25 15:42:47 UTC
(+1 to alerting both #-qa and #-operations)

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


Navigation
Links