You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, in the documentation, the Remote HTTP URL from a private repository section says: "If you are using the GitHub or the GitLab provider and If the remote task URL uses the same host as where the repository CRD is, Pipelines-as-Code will use the provided token to fetch the URL using the GitHub or GitLab API."
Should that work with remote pipeline URLs as well or that's only for remote task URLs?
I have a private repository on GitLab and I'm trying to use remote pipeline from another (private) repo in the same group. PaC (via Konflux) has a token for the group so it should be able to access the remote pipeline, but I'm getting Non-OK HTTP status: 403. It works via Tekton resolver.
It should use the gitlab token to fetch those, any chance you can create a srvkp ticket on pipelines-as-code in issues.redhat.com? that would make things easier to prio
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello, in the documentation, the Remote HTTP URL from a private repository section says:
"If you are using the GitHub or the GitLab provider and If the remote task URL uses the same host as where the repository CRD is, Pipelines-as-Code will use the provided token to fetch the URL using the GitHub or GitLab API."
Should that work with remote pipeline URLs as well or that's only for remote task URLs?
I have a private repository on GitLab and I'm trying to use remote pipeline from another (private) repo in the same group. PaC (via Konflux) has a token for the group so it should be able to access the remote pipeline, but I'm getting
Non-OK HTTP status: 403. It works via Tekton resolver.Thanks!
All reactions