Page MenuHomePhabricator
Create Task
Maniphest T91684

Continuous deployment for CI
Closed, DeclinedPublic
Actions

Description

Getting changes actually deployed for Zuul/Jenkins takes a while. Can we make it so Zuul/Jenkins deploy their changes themselves when there's a new changeset merge? Or maybe a Jenkins job that can be manually run to do it (thus making it "one click")?

Related Objects
Search...

Event Timeline

greg created this task.Mar 5 2015, 7:39 PM
greg raised the priority of this task from to Low.
greg updated the task description. (Show Details)
greg added a project: Continuous-Integration-Infrastructure.
greg added subscribers: greg, zeljkofilipin, hashar, • dduvall.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 5 2015, 7:39 PM
Legoktm subscribed.Mar 5 2015, 7:42 PM

Partial dupe of T49056, which just covers jenkins.

greg added a subtask: T49056: Jenkins: Set up postmerge job to auto-deploy jenkins-job-builder configuration.Mar 5 2015, 7:42 PM
Krinkle moved this task from Untriaged to Backlog on the Continuous-Integration-Infrastructure board.Apr 7 2015, 2:34 PM
JanZerebecki subscribed.Mar 15 2016, 5:58 PM
hashar closed this task as Declined.Mar 31 2017, 9:08 AM
hashar closed subtask T49056: Jenkins: Set up postmerge job to auto-deploy jenkins-job-builder configuration as Declined.

The automatic update sounds a bit scary. I would rather keep an extra manual step like for puppet change.

T129357 is about migrating the CI config to scap3 which would also open deployment to a larger set of people (currently one need access on the CI server). Lets use T129357.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL