Important for streamlined service delivery, we need a secure machine or machines on which we can build containers using blubber and push to the docker registry for use in staging.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Deployment pipeline profile | Thcipriani | operations/puppet | production | +58 -4 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T170453 FY2017/18 Program 6: Streamlined Service delivery | |||
| Invalid | None | T170480 FY2017/18 Program 6 - Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment. | |||
| Invalid | None | T170481 FY2017/18 Program 6 - Outcome 2 - Objective 2: Set up a continuous integration and deployment pipeline | |||
| Resolved | None | T157469 Mathoid CI Container Build | |||
| Resolved | dduvall | T175297 Define new Jenkins pipeline for container build phase | |||
| Resolved | thcipriani | T173128 Find CI container build location | |||
| Restricted Task |
Event Timeline
Comment Actions
Now that we have locked down the security for Jenkins a bit, contint1001 seems like a logical place to store credentials and run builds. We've discussed this a bit in the deployment pipeline meetings.
Ideally credentials would be managed there by puppet and used by the jenkins-deploy user to build containers via blubber.
Comment Actions
Change 382608 had a related patch set uploaded (by Thcipriani; owner: Thcipriani):
[operations/puppet@production] Deployment pipeline profile
Comment Actions
Current plan is to build and push containers from the CI hosts in production (currently contint1001).
Comment Actions
Change 382608 merged by Alexandros Kosiaris:
[operations/puppet@production] Deployment pipeline profile