#11807 move resultsdb-ci-listener deployment pipeline
Opened 3 months ago by kevin. Modified 3 months ago

The resultsdb-ci-listener is a app we run in openshift. It takes messages from CI and inserts them into resultsdb's database.

Right now, changes to the app require:

Changes made in https://pagure.io/ci-resultsdb-listener/ for the app itself.
Then, image changes made in https://pagure.io/kube-sig/resultsdb-ci-listener-images
Then, an image built in quay.io and pushed out
Finally changes in ansible to use that container (if it's not :latest).

IMHO we should move this to:

Changes made in https://pagure.io/ci-resultsdb-listener/ for the app in production and staging branches.
Our openshift using s2i to see the changes and build it and deploy it.


Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

3 months ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog