-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[OKD 3.11] Testing GitLab Build Trigger - payload includes 3 commits and triggers build based on wrong commit #23799
Comments
fyi @openshift/openshift-team-developer-experience |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
/remove-lifecycle rotten |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
/lifecycle frozen |
Hello you lovely people!
I'm posting in hopes of verifying and/or identifying a bug.
When testing the integration in GitLab to trigger an OpenShift build, the webhook payload sent by GitLab contains an array commits containing the last 3 commits.
OpenShift triggers a build, but clones the oldest commit (which is the last one in the array) and not the newest (meaning it reverts to an older code version)
When instead pushing to the GitLab repository to trigger the webhook, the commit array only contains one entry - the most recent commit - the OpenShift build therefore is OK.
Version
oc v3.11.0+8de5c34
kubernetes v1.10.0+d4cacc0
openshift v3.11.0+1c3e643-87
kubernetes v1.11.0+d4cacc0
Steps To Reproduce
With test from GitLab
Actual commit to repository
Current Result
With test - build is potentially initiated with the wrong commit, therefore building the image with outdated code.
Expected Result
When triggering builds when testing the webhook from GitLab the checkout_sha should be used to identify the commit.
Additional Information
JSON Payloads (test and actual commit)
Sensitive information has been redacted
The text was updated successfully, but these errors were encountered: