mattermost-community/mattermost-plugin-circleci

More than the expected nr of notifications when using parallelism.

Open

#86 opened on Oct 1, 2021

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (6 forks)auto 404
Difficulty/3:HardHacktoberfestHelp WantedTech/GoUp For Grabs

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug When running a job in parallel, you get a notification for each executor, rather than one notification for the entire job.

To reproduce

  1. Set up parallelism in circle.
  2. Configure the mattermost circleci plugin according to the documentation.
  3. Add - mattermost-plugin-notify/status: to the end of the steps part of a job, as described in the orb documentation.
  4. Run a job on Circle
  5. Get a notification for each executor in the parallel job

Expected behavior Get one notification that informs whether the entire job failed or succeeded.

Contributor guide

Research direction
Inspect the notification handling code in the Mattermost CircleCI plugin, focusing on how it processes CircleCI webhooks for parallel job executions. Trace the logic that determines when to send a notification and identify the point where it triggers per executor instead of per job. Look for aggregation logic or a missing grouping by workflow/job ID.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoCircleCI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65