search

jenkins-x / lighthouse

Apache License 2.0
184 stars 115 forks source link

On /retest the pullrequest pipeline is picked from master branch instead of taking it from merge of PR branches #1119

Open nagenderRawat opened 4 years ago

nagenderRawat commented 4 years ago

After failing of PR pipeline once, on every /retest on PR comment a PR pipeline is triggered with pullrequest.yaml commited on master branch instead of using pullrequest.yaml from the merge of branches PR is made(for eg PR from feature => qa merge state).

They may be the case master have diff state of pullrequest.yaml so therefore It should always use the pullrequest.yaml from the branches taking part in PR, no matter if it the first time or rerun after fail using /retest...

Using jx3 alpha with tekton catalog jx cli -: 3.0.584 Tekton version -:

- chart: cdf/tekton-pipeline
  version: 0.17.1
  name: tekton-pipeline
  namespace: tekton-pipelines
  values:
  - versionStream/charts/cdf/tekton-pipeline/values.yaml.gotmpl
jenkins-x-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle rotten