Build and push Docker containers on merge
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	bd808
	Mar 26 2021, 12:11 AM

Description

Take the next step of wiring up pipelinelib by configuring zuul to fire a build job for our demo container when a patchset is merged to the repo.

Details

Subject	Repo	Branch	Lines +/-
build: Tag CI built production images as "latest"	wikimedia/toolhub	main	+1 -4
toolhub: Add publish pipeline config	integration/config	master	+5 -0
build: Add publish pipeline	wikimedia/toolhub	main	+33 -6

Customize query in gerrit

Related Objects
Search...

Status	Subtype	Assigned	Task
Open		None	T288685 Establish active/active multi-dc support for Toolhub
Resolved		bd808	T115650 Create an authoritative and well promoted catalog of Wikimedia tools
Resolved		bd808	T271483 Complete and announce initial production deployment of Toolhub
Duplicate	BUG REPORT	None	T287516 Generation of "demo" Dockerfile from Toolhub's blubber.yaml broken after refactoring
Resolved		bd808	T278503 Build and push Docker containers on merge

Event Timeline

bd808 created this task.Mar 26 2021, 12:11 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 26 2021, 12:11 AM

bd808 added a parent task: T271483: Complete and announce initial production deployment of Toolhub.Mar 29 2021, 11:00 PM

bd808 renamed this task from Build and push Docker containers for git tags to Build and push Docker containers on merge.Jul 22 2021, 9:30 PM

bd808 claimed this task.

bd808 triaged this task as High priority.

bd808 added a project: Developer-Advocacy (Jul-Sep 2021).

bd808 updated the task description. (Show Details)

Restricted Application added a project: User-bd808. · View Herald TranscriptJul 22 2021, 9:30 PM

I had a short call with @jeena and @dduvall today to get some help getting oriented on this. That discussion led to the edit changing from talking about tags to patchset merge as the trigger event. They also shared a number of links to existing docs which should be useful in preparing my patches:

The kask project is using tag pushes as a trigger as well, but the general workflow today is to allow a new image to be pushed into the repo with each gerrit merge and then control which particular image is used in a given cluster by pinning the container tag in the project's helm3 configuration.

After our call, I wrote up a new section in the PipelineLib user guide for Zuul integration of pipelines that publish/promote images. Hopefully that helps as well.