Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-4557

Better way to update registry.quarkus.redhat.com

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • 3.15.NEXT
    • None
    • team/prod
    • None
    • False
    • None
    • False
    • ---

      Currently this is done manually by updating a platform version in git@gitlab.cee.redhat.com:quarkus/quarkus-extension-catalog-redhat.git and pushing the change.

      We should look into creating a job that could be triggered to do that.

      It could possibly be automated by triggering it on a certain event, possibly on an advisory being shipped live, although we need to make sure the binaries have been uploaded to MRRC at that point.

              ant@redhat.com Ant Stephenson
              olubyans@redhat.com Alexey Loubyansky
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: