-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Add GitHub Action Workflow: create-deploy-tag #165213
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
--- | ||
# - This workflow creates a tag with the format "deploy@<timestamp>" on the main branch. | ||
# - It is triggered manually from the GitHub Actions UI. | ||
# - It is only allowed to run on the main branch and ensures that the tag is created | ||
# on the main branch only in a verification step. | ||
# This is only to prevent accidental creation of the tag on other branches and cannot be used to prevent malicious creation of the tag. | ||
|
||
name: create-deploy-tag | ||
|
||
on: | ||
workflow_dispatch: | ||
inputs: | ||
commit: | ||
description: "The commit to tag (default: latest commit on main)" | ||
|
||
concurrency: | ||
group: ${{ github.workflow }} | ||
|
||
jobs: | ||
create-deploy-tag: | ||
runs-on: ubuntu-latest | ||
permissions: | ||
contents: write | ||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v3 | ||
with: | ||
fetch-depth: 0 | ||
- name: Select commit to be tagged | ||
run: | | ||
commit="${{ github.event.inputs.commit || github.sha }}" | ||
echo "COMMIT=${commit}" >> "${GITHUB_ENV}" | ||
- name: Verify selected commit isn't already tagged | ||
run: | | ||
git tag --contains ${COMMIT} | grep -P "^deploy@\d+$" && { | ||
echo "Tag already exists on selected commit" | ||
exit 1 | ||
} || true | ||
- name: Verify branch | ||
run: | | ||
if [[ "${GITHUB_REF}" != "refs/heads/main" ]]; then | ||
echo "This workflow can only be run on the main branch" | ||
exit 1 | ||
fi | ||
- name: Prepare tag | ||
run: | | ||
tag_name="deploy@$(date +%s)" | ||
echo "TAG_NAME=${tag_name}" >> "${GITHUB_ENV}" | ||
- name: Create tag | ||
run: | | ||
git tag ${TAG_NAME} ${COMMIT} | ||
git push origin "refs/tags/${TAG_NAME}" | ||
- if: always() | ||
uses: elastic/apm-pipeline-library/.github/actions/notify-build-status@current | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Btw, I just copied this from the APM team and is using their notify script. I'm not sure if we have a more Elastic-wide generic script to do the same? It seems odd to me that APM has a custom one? |
||
with: | ||
message: ${{ job.status == 'success' && format('Created tag `{0}` for commit `{1}`', env.TAG_NAME, env.COMMIT) || 'Creating a deploy tag failed' }} | ||
vaultUrl: ${{ secrets.VAULT_ADDR }} | ||
vaultRoleId: ${{ secrets.VAULT_ROLE_ID }} | ||
vaultSecretId: ${{ secrets.VAULT_SECRET_ID }} | ||
slackChannel: "#kibana-mission-control" |
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.
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.
We probably want to skip this on forks?