If we want to deploy the same jobs we use for testing MediaWiki code on ci-jenkins to releases-jenkins we'll likely need docker to run the tasks in those jobs.
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T156445 Streamline/automate MW tarball security release process | |||
| Resolved | Dzahn | T208529 Install docker on releases-jenkins |
Event Timeline
Comment Actions
Change 474825 had a related patch set uploaded (by Thcipriani; owner: Thcipriani):
[operations/puppet@production] Install docker on releases-jenkins
Comment Actions
It was included when the sub-task was created from the parent: T156445: Streamline/automate MW tarball security release process. Remove from here.
Comment Actions
Unassigned for the time being. I have a patch for puppet but I am not actively working on this and I have a few things that I think are pre-requisites for this.
Comment Actions
Change 474825 had a related patch set uploaded (by Giuseppe Lavagetto; owner: Thcipriani):
[operations/puppet@production] Install docker on releases-jenkins
Comment Actions
Change 474825 abandoned by Thcipriani:
[operations/puppet@production] Install docker on releases-jenkins
Reason:
very old
Comment Actions
Change 655500 had a related patch set uploaded (by Dduvall; owner: Dduvall):
[operations/puppet@production] releases: Provide docker to PipelineLib based jobs
Comment Actions
Change 655500 merged by Dzahn:
[operations/puppet@production] releases: Provide docker to PipelineLib based jobs
Comment Actions
Change 657895 had a related patch set uploaded (by Dduvall; owner: Dduvall):
[operations/puppet@production] releases: Set declare_service: false for docker
Comment Actions
Change 657895 merged by Dzahn:
[operations/puppet@production] releases: Set declare_service: false for docker
Comment Actions
18:55 < marxarelli> mutante: great! and looks like the jenkins agent has access to the socket so we're good to go