-
Notifications
You must be signed in to change notification settings - Fork 81
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
[Fleet] Fix docker publish step in buildkite #2815
Conversation
@@ -105,6 +105,8 @@ steps: | |||
env: | |||
SERVICE_COMMIT_HASH: ${BUILDKITE_COMMIT:0:12} | |||
REMOTE_SERVICE_CONFIG: https://raw.githubusercontent.com/elastic/serverless-gitops/main/gen/gpctl/fleet/config.yaml | |||
depends_on: | |||
- step: "publish" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a dependency here so we do not update tags with non valid image
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@michel-laterman should we replace the |
@nchaulet I just fixed this by adding buildkite as a required step and removed the jenkins one. |
(cherry picked from commit 5cce568) # Conflicts: # .buildkite/pipeline.yml
…2818) * [Fleet] Fix docker publish step in buildkite (#2815) (cherry picked from commit 5cce568) # Conflicts: # .buildkite/pipeline.yml * Update pipeline.yml Fix conflicts --------- Co-authored-by: Nicolas Chaulet <[email protected]> Co-authored-by: Julien Lind <[email protected]>
Description
Fix docker publish step in buildkite
The if condition to build the docker image was not met
It seems according to buildkite doc that
BUILDKITE_PULL_REQUEST
should be false if it's not a pull request and not an empty string