-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problematic rebuilding of a merged branch's pipeline #72
Comments
Could you add the following info:
When I had a brief look together with you, this looked credentials related - somehow the pipeline seemed to forget the credentials ... |
I believe the credential issue we looked together was a combination of this case and an additional case: merge was made through command line and without approval.
|
@sino92 Thanks for the log output, that might help to find the issue. Did you already search for this error message? Could also be a known issue elsewhere ... I am still pretty certain that merging via the CLI has no implications here. |
I figured out what causes this. When the webhook proxy deletes the pipeline, it does not delete the builds of that pipeline. Say you had 3 builds. When the pipeline is deleted and re-created later, it is done so without information about previous builds ( I guess we have to either delete the previous builds and/or remember |
This prevents builds from being orphaned, see: - https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/ - https://docs.openshift.com/container-platform/3.11/rest_api/apis-build.openshift.io/v1.BuildConfig.html#Delete-apis-build.openshift.io-v1-namespaces-namespace-buildconfigs-name Fixes opendevstack#72.
This prevents builds from being orphaned, see: - https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/ - https://docs.openshift.com/container-platform/3.11/rest_api/apis-build.openshift.io/v1.BuildConfig.html#Delete-apis-build.openshift.io-v1-namespaces-namespace-buildconfigs-name Fixes #72.
Steps To Replicate:
Going to OC and starting the pipeline there works
The text was updated successfully, but these errors were encountered: