This repository has been archived by the owner on Oct 28, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Add releaseNotification step to simplify agent release pipelines #976
Merged
mergify
merged 4 commits into
elastic:master
from
v1v:feature/release-step-notifications
Feb 15, 2021
Merged
Add releaseNotification step to simplify agent release pipelines #976
mergify
merged 4 commits into
elastic:master
from
v1v:feature/release-step-notifications
Feb 15, 2021
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
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
v1v
added
enhancement
New feature or request
backport-to-7.x
Automatically backport PRs from master
ready-to-merge
labels
Feb 11, 2021
kuisathaverat
approved these changes
Feb 11, 2021
This was referenced Feb 11, 2021
cachedout
approved these changes
Feb 15, 2021
mergify bot
pushed a commit
that referenced
this pull request
Feb 15, 2021
* Add releaseNotification step to simplify agent release pipelines * REmove imports * update README docs Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 6e3bb9a)
v1v
referenced
this pull request
in v1v/apm-pipeline-library
Feb 15, 2021
… feature/override-google-storage-step * 'master' of github.com:elastic/apm-pipeline-library: [chore]: delegate delete to the core (#904) docs: update CHANGELOG.md [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release v1.1.186 chore: refactor jobs in folders (#974) Fix broken documentation (#970) Add releaseNotification step to simplify agent release pipelines (#976) chore(deps-dev): bump junit from 4.13.1 to 4.13.2 (#980) Disable/Enable pre-commit skipped tests in the report (#977) feat: support parameters for githubPrCheckApproved (#910) Automatically merge PRs for the 7.x branch (#971) chore: refactor params variables to args (#960)
v1v
added a commit
that referenced
this pull request
Mar 18, 2021
* upstream/7.x: Fix the getCause and getCauses for the AbortException (#1041) (#1042) gsutil for windows with python (#1008) (#1009) Report only one DeleteDir step failure (#1006) (#1007) [cosmetic] Replace multiline chars in the GitHub PR comment (#998) (#1003) [cosmetic] add the author (#999) (#1002) chore: use opentelemetry release (#1000) (#1001) Avoid cache gsutils temporary location (#994) (#995) [JCasC] google cloud engine local setup (#979) (#992) Support curl in addition to wget for gsutil (#988) (#989) Support windows for gsutil (#985) (#987) Add googleStorageUploadExt step (#867) (#982) Add releaseNotification step to simplify agent release pipelines (#976) (#981)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
backport-to-7.x
Automatically backport PRs from master
enhancement
New feature or request
groovy
ready-to-merge
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.
What does this PR do?
Create wrapper to notify by email and slack
Why is it important?
DRY approach, as we sue the same function in different release pipelines.