[CHORE] Adding env var to trigger docs deploy manually from Buildkite…

… UI (#7397)
elastic · Dec 6, 2023 · a6eb185 · a6eb185
1 parent 5090391
commit a6eb185
Show file tree

Hide file tree

Showing 2 changed files with 19 additions and 3 deletions.
diff --git a/scripts/deploy/deploy_docs b/scripts/deploy/deploy_docs
@@ -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
       curl -L \
         -X DELETE \
         -H "Authorization: token ${GITHUB_TOKEN}" \
@@ -150,7 +150,13 @@ else
       publish_to_bucket
     fi
 
-  # Let users know neither job ran
+  # Manually deploy latest docs via Buildkite UI
+  elif [[ "${DEPLOY_ROOT}" == "true" ]]; then
+    echo "Maually deploying latest release. Deploying to root eui.elastic.co"
+    full_bucket_path="gs://${BUCKET}/"
+    publish_to_bucket
+
+  # Let users know none of the three jobs ran
   else
     echo "This is neither a pull request nor a tag release. No docs were deployed."
   fi

diff --git a/wiki/eui-team-processes/releasing-versions.md b/wiki/eui-team-processes/releasing-versions.md
@@ -40,7 +40,7 @@ npm whoami # Should return an error about not being logged in
 
 Buildkite automatically deploys our docs to the EUI `Bekitzur` environment. The Buildkite job is started when a new tag is pushed to the `main` branch.
 
-To view the progress of your job or check for errors:
+**To view the progress of your job or check for errors:**
 
 * Log in to Buildkite using Elastic SSO
 * Filter jobs by `eui-team`
@@ -50,6 +50,16 @@ To view the progress of your job or check for errors:
   * Click the `Rebuild` button if your job needs to be restarted **or**
   * Click the `.buildkite/scripts/pipelines/pipeline_deploy_docs.sh` row to view logs and environment details
 
+**To deploy release docs manually:**
+
+* Log in to Buildkite using Elastic SSO
+* Filter jobs by `eui-team`
+* Click on `eui-release-deploy-docs`
+* Click the green `New Build` button on the top right
+* Click the `Options` accordion to show the Environment Variables textbox
+* Add `DEPLOY_ROOT=true` to the Environment Variables textbox
+* Click `Create Build` to start the job manually
+
 ### Tag the release in GitHub
 
 We also update the [release's tag in github](https://github.com/elastic/eui/tags) by _creating a release_ for the version and copying over its _CHANGELOG_ entries.