[CI] Add job to run issue-bot
What does this MR do?
Adds a job to run issue bot.
Related issues
Closes gitlab-org/distribution/team-tasks#906 (closed).
To do
-
Create labels: pipeline failure
,pipeline failure::needs investigation
,pipeline failure::under investigation
in Charts project -
Create pipeline failure issue board in Charts project (https://gitlab.com/gitlab-org/charts/gitlab/-/boards/3503121?label_name[]=pipeline%20failure) -
[Needs CNG maintainer] Create project access token in CNG project with api
scope, and add to CNG project's CI variables asISSUE_BOT_API_TOKEN
-
[Needs CNG and Charts maintainer] Create project access token in Charts project with api
scope, and add to CNG project's CI variables asISSUE_TRACKER_API_TOKEN
-
[Needs CNG maintainer] Create CNG CI project variable: ISSUE_TRACKER_BASE_URL=https://gitlab.com/
-
[Needs CNG maintainer] Create CNG CI project variable: ISSUE_TRACKER_PROJECT_ID=3828396
(this is the Chart's project ID) -
Test issue creation (add a job that with exit 1
and comment out therules
block of the issue-bot job) (gitlab-org/charts/gitlab#2993 (closed)) -
Link to pipeline failure issue board in #g_distribution
channel's pinned links -
[Needs CNG maintainer] Disable Slack integration for the conditions where issue-bot will run
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Integration tests added to GitLab QA -
The impact any change in container size has should be evaluated
Edited by Jason Plum