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

PAC: PipelineInlineSpec only works with fully qualified URL, does not work with relative URLs

XMLWordPrintable

    • PAC: PipelineInlineSpec only works with fully qualified URL, does not work with relative URLs
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • SECFLOWOTL-117 - Enhancing Task/Pipeline Resolving Support in PAC
    • Hide
      You can now use relative paths to reference tasks from within a remote `Pipeline` definition. The resolver automatically constructs the full URL for the task based on the location of the remote pipeline file. This allows for more portable definitions by keeping tasks and their referencing pipelines co-located.
      Show
      You can now use relative paths to reference tasks from within a remote `Pipeline` definition. The resolver automatically constructs the full URL for the task based on the location of the remote pipeline file. This allows for more portable definitions by keeping tasks and their referencing pipelines co-located.
    • Feature
    • Done

      In the PipelineSpec Customer would like to reference the used tasks using relative paths (using full paths would be a nightmare to manage if they use tagged releases or branches).
      It seems that the resolver looks for tasks with relative URLs in the repo where the PipelineRun is defined, and not where the PipelineSpec is defined.

      Their expected behaviour is to look for the tasks where pipelinespec is defined.

              piyushgarg001 Piyush Garg
              rh-ee-ksaha Koustav Saha (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: