| cardoe | If I'm looking to publish the same container to quay and docker hub, the standard opendev-container-image jobs don't handle that right? | 02:19 |
|---|---|---|
| cardoe | Or do I need to define two container_images for the job? | 02:21 |
| tonyb | cardoe: I think you need to look for promote-container-image | 02:23 |
| tonyb | cardoe: let me see if I can find a good example | 02:23 |
| cardoe | I can push what I've hacked together if that would help. | 02:23 |
| cardoe | https://paste.opendev.org/show/b4kBF8wakQpuMEhNf3O3/ | 02:24 |
| cardoe | Maybe my approach is wrong | 02:24 |
| cardoe | https://opendev.org/openstack/loci/src/branch/master/zuul.d/project.yaml ultimately looking to replace that | 02:24 |
| cardoe | And make it more straight forward | 02:24 |
| tonyb | cardoe: It looks more complex than I would have expected, but please gimme 10 to digest it | 02:25 |
| cardoe | https://opendev.org/openstack/loci/src/branch/master/zuul.d/2023.2-ubuntu_jammy.yaml sorry that's what I'm replacing. | 02:25 |
| tonyb | cardoe: I'll start by saying that I'm not an expert on this but for a new conatiner image in system-coinfig I did: https://review.opendev.org/c/opendev/system-config/+/921321/14/zuul.d/docker-images/mediawiki.yaml and https://review.opendev.org/c/opendev/system-config/+/921321/14/zuul.d/project.yaml | 02:31 |
| tonyb | so in the check pipeline you build/check your image, in gate, you upload it | 02:32 |
| tonyb | and you define the inter-job dependencies in the pipeline rather than the job | 02:32 |
| cardoe | Looks pretty similar except the double container definition | 02:33 |
| tonyb | In your paste I only see the job definitions | 02:34 |
| cardoe | Yeah I haven't added them to the project yet. This isn't ready to commit. | 02:35 |
| tonyb | Seeing the pipline change would help, also I don't know for sure the "dependencies" in the job are what you want, but that could just be because it's different to what we do in system-config | 02:35 |
| tonyb | Also in your zuul_work_dir I think the project shoudl be 'opendev.org/openstack/loci', unless of course you're in the process of moving namespace ? | 02:38 |
| cardoe | yes thank you I got that wrong | 02:38 |
| tonyb | np. I think you're pretty close. I realise I misread your original question | 02:40 |
| Clark[m] | I think you can use the container jobs to upload to arbitrary registries | 02:41 |
| Clark[m] | There was a bunch of semi recent refactoring to make that possible | 02:41 |
| cardoe | So I don't need to define 2 container images? | 02:41 |
| tonyb | cardoe: If you build the image and push it to the intermediate registry then you can have n jobs push from the intermediate registry to each of the services you need | 02:43 |
| cardoe | That makes sense to me. | 02:43 |
| tonyb | As long as your build, or maybe upload job "provides" the image and any publish/promote "requires" it you should be fine | 02:44 |
| tonyb | cardoe: another option would be to offically only publish to one registry *cough*quay.io*cough* and then have a periodic job mirror from the source-of-truth to the other services | 02:45 |
| tonyb | cardoe: if lag/latency is fine | 02:46 |
| Clark[m] | Ya I think you define one artifact then promote it to multiple places | 02:46 |
| tonyb | cardoe: see: https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/mirror-container-images for that option | 02:48 |
| cardoe | I'm missing the connection between a job and roles liek that. | 02:50 |
| tonyb | cardoe: IIUC: the connection(s) are the various pipelines, check: is well check so it builds and tests the image, gate: will build/test and publish the image, and if you go down this path periodic: would take all the images on ${server_1} and mirror them to ${server_2} | 02:53 |
| tonyb | cardoe: I did say I'm not an expert, but that's how I understand it | 02:58 |
| cardoe | Can I variablize the provides and requires for a job? | 03:43 |
| cardoe | hrm... so use-buildset-registry as documented seems to fail.. https://zuul.opendev.org/t/openstack/stream/8643e5881f1c48238800b231bb97c0be?logfile=console.log | 04:19 |
| tonyb | cardoe: Gotta wait for the job to fully fail as that stream is closed | 04:22 |
| tonyb | cardoe: I guess the job is https://review.opendev.org/c/openstack/loci/+/946456/ | 04:22 |
| tonyb | cardoe: Okay so I see the failure: https://zuul.opendev.org/t/openstack/build/72d6fc100fd64fabafcc20152aefffb3 | 04:29 |
| tonyb | cardoe: I think rather than removing loci-buildset-registry you need to switch it for: opendev-buildset-registry | 04:34 |
| cardoe | tonyb: thanks! | 15:44 |
| opendevreview | Takashi Kajinami proposed opendev/system-config master: Update exclude list for puppetlabs repository sync https://review.opendev.org/c/opendev/system-config/+/946501 | 17:30 |
| opendevreview | Takashi Kajinami proposed opendev/system-config master: Update exclude list for puppetlabs repository sync https://review.opendev.org/c/opendev/system-config/+/946501 | 17:31 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!