[BUILD-1116] Support slack notification when there's failed build on feature branch Created: 03/Aug/23 Updated: 19/Jan/24 Resolved: 19/Jan/24 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Lam Nguyen Bao | Assignee: | Christoph Meier |
| Resolution: | Resolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 3h | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Work Started: |
| Description |
ContextCurrently, we are experiencing build errors on the feature branch, but we remain unaware of them until someone manually checks the build. Therefore, I would like to explore potential solutions:
example: pages norsu feature branch: https://jenkins.magnolia-cms.com/job/modules/job/pages/job/feature%252FpagesVersion-6.3-norsu-SNAPSHOT/ public slack channel: https://magnolia-cms.slack.com/archives/C05KGC6JR0F
Possible "solution(s)"Pipeline-templates accept a new param a) New param to define a list of branch-names, for which we "send notifications" in case of build-failures.
b) New param notifyForFeatureBranches default is ... false or true? I propose: true c) No new param - just change code that it always notifies if it's a feature-branch
env.BRANCH_NAME.contains("feature/")
Or using FeatureBranch.isFeatureBranch(env.BRANCH_NAME)
In all cases - changes would be implemented in the script defaultAlways.groovy |