[CHORE] Adding env var to trigger docs deploy manually from Buildkite UI #7397
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Buildkite test this |
|
Preview staging links for this PR:
|
💚 Build Succeeded
History
cc @1Copenut |
JasonStoltz
approved these changes
Dec 5, 2023
tkajtoch
reviewed
Dec 6, 2023
| @@ -45,7 +45,7 @@ post_comment_to_gh() | |||
| curl -s -L "https://api.github.com/repos/elastic/eui/issues/${GIT_PULL_REQUEST_ID}/comments" \ | |||
| | jq -c '.[] | select(.user.login == "kibanamachine") | .id' \ | |||
| ) | |||
| for comment_id in ${kibanamachine_comment_ids[@]}; do | |||
| for comment_id in "${kibanamachine_comment_ids[@]}"; do | |||
tkajtoch
reviewed
Dec 6, 2023
tkajtoch
approved these changes
Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
PR adds conditional logic to our
deploy_docsshell script to listen forDEPLOY_ROOTenv variable. If this variable is added to the release deploy docs job, it will trigger the build without pushing a new tag / release. PR closes #7396.QA
Manually triggering the job assumes two key pieces of information:
mainbranch. Selected by default in Buildkite UI.HEADcommit on main. Selected by default in Buildkite UI.QA will be done in two parts, all in Buildkite: