Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-7590

PaC Docs: Do Not Recommend Personal Fork Usage with Gitlab

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Customer Reported

      Description of Problem

      When triggering PaC Pipelines with GitLab, the flow only works if developers create their own branches on a given repository. They cannot use the more typical "personal fork" approach to trigger PaC builds.

      This is a known limitation that is not well documented upstream (and perhaps downstream, too?). Konflux generally relies on upstream documentation for its subprojects/components.


      Original support request:

      Request type: Error / Bug
      Reason of urgency: We can work around this by manually checking whether CI passed and then force merging, but that adds even more friction

      Request info

      Team: bootc
      Tenant: rhel-bootc
      Application: rhel-bootc
      Component: rhel-bootc

      Details:

              gitlab pipline status <-> konflux sync not working
              The gitlab <-> konflux pipeline integration seems to have just gone missing in https://gitlab.com/redhat/centos-stream/containers/bootc/
      
      It was getting less reliable recently but now just seems to have completely lost.
      
      We can manually note that the job passed and force merge, but this is obviously suboptimal.
      
      See also https://redhat-internal.slack.com/archives/C066HLR2RGA/p1742320139968869?thread_ts=1741960711.903619&cid=C066HLR2RGA
              

              Unassigned Unassigned
              walters@redhat.com Colin Walters
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: