DAT-16417 Extensions nightly build review #136
Merged
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
chore(extension-attach-artifact-release.yml): update version of get_draft_release.sh, sign_artifact.sh, and upload_asset.sh to v0.5.8 chore(extension-release-prepare.yml): update version of extension-release-rollback.yml to v0.5.8 chore(extension-release-published.yml): update version of extension-release-prepare.yml to v0.5.8 chore(os-extension-test.yml): update version of sonar-pull-request.yml to v0.5.8 chore(package-linux.yml): update version of package-deb-pom.xml and sign_artifact.sh to v0.5.8 chore(pom-release-published.yml): update version of extension-release-prepare.yml to v0.5.8 chore(pro-extension-test.yml): update version of sonar-pull-request.yml to v0.5.8
added 14 commits
December 11, 2023 12:53
… builds Add Slack notification on build failure for nightly builds in the OS extension and Pro extension test workflows. This will notify the team on Slack when a build fails, providing details such as the branch, commit, and repository. The notification is sent using the rtCamp/action-slack-notify GitHub Action. The Slack notification includes the following information: - Color: The status of the job (success, failure, etc.) - Message: A link to view the details of the GitHub Actions run - Title: A message indicating that the build failed, including the branch, commit, and repository - Username: The username displayed for the Slack notification - Webhook: The Slack webhook URL for sending the notification - Icon Emoji: The emoji displayed for the Slack notification
…ures The Slack notification titles in the `os-extension-test.yml` and `pro-extension-test.yml` workflows were updated to better reflect the nature of the failures. The previous titles indicated that the build failed, but the actual issue was with the tests. The titles were changed to "❌ Tests failed on branch [branch name] for commit [commit hash] in repository [repository name]". This change improves the accuracy and clarity of the notification messages.
…version to DAT-16417 for compatibility and consistency
… to properly check for failure and nightly inputs The conditional expression in the Slack notification step was not properly checking for failure and nightly inputs. This commit fixes the conditional expression by adding the missing dollar sign before the `inputs` variable.
…l URL to the GitHub Actions run The Slack notification messages in the workflows `os-extension-test.yml` and `pro-extension-test.yml` have been updated to include the full URL to the GitHub Actions run. This will allow users to easily view the details of the failed build or tests directly from the Slack notification.
…test.yml and pro-extension-test.yml The Slack notification messages in the os-extension-test.yml and pro-extension-test.yml workflows have been updated to include a link to view the details on GitHub Actions. This will provide easier access to the specific workflow runs for failed builds and tests. The SLACK_MESSAGE environment variable has been modified to include the GitHub Actions URL using the $GITHUB_SERVER_URL, $GITHUB_REPOSITORY, and $GITHUB_RUN_ID variables. This will dynamically generate the URL based on the current workflow run. Additionally, the SLACK_TITLE environment variable has been updated to include the branch name and commit information for better context in the Slack notification.
…ment variable to correctly reference GitHub Actions variables The syntax error in the SLACK_MESSAGE environment variable has been fixed to correctly reference the GitHub Actions variables. This ensures that the Slack notification includes the correct link to view the details of the failed build on GitHub Actions.
…-extension-test.yml to use correct syntax for GitHub Actions variables
The SLACK_MESSAGE environment variable in the os-extension-test.yml and pro-extension-test.yml workflows was using incorrect syntax for referencing GitHub Actions variables. This has been updated to use the correct syntax `${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}`. This ensures that the Slack notification includes the correct link to view the details of the GitHub Actions run.
…y name for better context feat(workflows): add repository name to Slack notification footer for better identification
…e GitHub repository name in Slack notifications for both os-extension-test.yml and pro-extension-test.yml workflows
…sername @filipelautert and enable link names The Slack notification messages in the GitHub Actions workflows have been updated to include the username @filipelautert. This change improves the visibility of the user who triggered the workflow run. Additionally, the `SLACK_LINK_NAMES` environment variable has been set to true. This enables link names in the Slack messages, making it easier to mention and reference users and channels in the messages.
…test.yml and pro-extension-test.yml The Slack notification messages in the os-extension-test.yml and pro-extension-test.yml workflows have been updated to mention the username "filipe" instead of "filipelautert". This change improves the accuracy and consistency of the notification messages.
…c user The Slack notification messages in the workflows `os-extension-test.yml` and `pro-extension-test.yml` have been updated to mention the user with the ID `U042HRTL4DT`. This change was made to improve the visibility of the notifications and ensure that the relevant user is notified.
…version to v0.5.8 for better compatibility and stability
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.
chore(create-release.yml): update version of sonar-push.yml to v0.5.8
chore(extension-attach-artifact-release.yml): update version of get_draft_release.sh, sign_artifact.sh, and upload_asset.sh to v0.5.8
chore(extension-release-prepare.yml): update version of extension-release-rollback.yml to v0.5.8
chore(extension-release-published.yml): update version of extension-release-prepare.yml to v0.5.8
chore(os-extension-test.yml): update version of sonar-pull-request.yml to v0.5.8
chore(package-linux.yml): update version of package-deb-pom.xml and sign_artifact.sh to v0.5.8
chore(pom-release-published.yml): update version of extension-release-prepare.yml to v0.5.8
chore(pro-extension-test.yml): update version of sonar-pull-request.yml to v0.5.8