GitHub Service integration sends status updates per pipeline-stage instead of per pipeline
What
We'll be sending pipeline information to GitHub in https://gitlab.com/gitlab-org/gitlab-ee/issues/3836 / https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4591.
This issue is for extending this to send per-job information
Details
@jamedjo in https://gitlab.com/gitlab-org/gitlab-ee/issues/3836#note_60218870:
One way we could iterate on this is to send more detailed statuses for failed jobs or pipeline stages. We could perhaps send one notification per pipeline stage, or send individual status updates on job failures with a small description of the error.
It would nice to at least be including stage names, and potentially job names in that status dialog.
If this integration is generic enough, then the SAST job could leverage it to push the commit status using a dedicated
context
named "security" and a link to the job page (where the security widget shows up)Yep definitely!
If we automatically had one context for each pipeline stage and an additional status for each failed job we could might be able to do that in a completely generic way.
We might want to limit the notifications on failed jobs though, as we don't want to preset too much information. We'd have to be sure to update/delete those on retry though.
@pedroms in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4591#note_60349494:
Can we pass the individual pipeline stages here (like this and [this]image; see live example here)?
If so, let's output:
[GitLab logo] GitLab CI/CD: {stage name} — Pipeline stage {status}