Scheduled pipelines appear in the post-merge MR section
Summary
Steps to reproduce
Two pipelines are configured for the dev
branch:
- On push (deployment)
- On schedule
A merged into dev
MR triggers the deployment pipeline. It's shown in the post-merge (#25140 (closed)) section.
After this, the scheduled pipeline on the dev
branch is triggered. It's not related to the MR.
Example Project
(TODO)
What is the current bug behavior?
The scheduled pipeline replaces the deployment pipeline in the MR's post-merge section.
What is the expected correct behavior?
The post-merge section displays only the pipelines which are directly linked to the MR, and doesn't show scheduled pipelines.
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Debian 9.12 Current User: git Using RVM: no Ruby Version: 2.6.6p146 Gem Version: 2.7.10 Bundler Version:1.17.3 Rake Version: 12.3.3 Redis Version: 5.0.9 Git Version: 2.27.0 Sidekiq Version:5.2.7 Go Version: unknown GitLab information Version: 13.1.1 Revision: bdb9883705a Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 11.7 URL: https://[removed] HTTP Clone URL: https://[removed]/some-group/some-project.git SSH Clone URL: git@[removed]:some-group/some-project.git Using LDAP: yes Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 13.3.0 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 13.3.0 ? ... OK (13.3.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) User output sanitized. Found 100 users of 100 limit.
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 4/7 ... yes 4/8 ... yes 4/9 ... yes 4/12 ... yes 4/14 ... yes 4/15 ... yes 3/17 ... yes 24/19 ... yes 4/22 ... yes 4/23 ... yes 4/24 ... yes 28/27 ... yes 28/28 ... yes 4/30 ... yes 4/31 ... yes 4/33 ... yes 4/36 ... yes 28/37 ... yes 30/38 ... yes 27/39 ... yes 30/41 ... yes 4/42 ... yes 30/44 ... yes 4/45 ... yes 4/46 ... yes 30/48 ... yes 30/50 ... yes 30/51 ... yes 30/52 ... yes 30/53 ... yes 30/54 ... yes 30/55 ... yes 30/58 ... yes 30/59 ... yes 30/60 ... yes 30/61 ... yes 30/62 ... yes 30/64 ... yes 30/66 ... yes 30/67 ... yes 30/68 ... yes 30/69 ... yes 30/70 ... yes 30/71 ... yes 30/72 ... yes 30/73 ... yes 30/75 ... yes 30/76 ... yes 30/77 ... yes 4/78 ... yes 75/83 ... yes 63/84 ... yes 30/87 ... yes 30/89 ... yes 75/90 ... yes 75/91 ... yes 28/92 ... yes 93/93 ... yes 99/94 ... yes 75/96 ... yes 75/97 ... yes 75/98 ... yes 75/99 ... yes 112/100 ... yes 119/101 ... yes 119/103 ... yes 119/106 ... yes 30/107 ... yes 30/109 ... yes 30/110 ... yes 30/111 ... yes 4/112 ... yes 119/113 ... yes 119/114 ... yes 119/116 ... yes 119/117 ... yes 119/118 ... yes 119/119 ... yes 119/120 ... yes 119/121 ... yes 119/122 ... yes 119/123 ... yes 30/124 ... yes 30/126 ... yes 119/127 ... yes 30/129 ... yes 72/130 ... yes 151/131 ... yes 30/133 ... yes 30/134 ... yes 30/136 ... yes 119/137 ... yes 13/138 ... yes 75/139 ... yes 4/140 ... yes 4/142 ... yes 132/143 ... yes 191/144 ... yes 75/147 ... yes 4/148 ... yes 131/149 ... yes 81/150 ... yes 213/151 ... yes 89/156 ... yes 208/157 ... yes 208/158 ... yes 29/159 ... yes 30/160 ... yes 30/161 ... yes 119/162 ... yes 4/163 ... yes 116/164 ... yes 127/165 ... yes 30/166 ... yes 244/168 ... yes 116/169 ... yes 261/171 ... yes 264/174 ... yes 264/175 ... yes 161/176 ... yes 130/177 ... yes 273/178 ... yes 4/179 ... yes 278/180 ... yes 13/181 ... yes 30/183 ... yes 111/184 ... yes 253/185 ... yes 30/186 ... yes 4/187 ... yes 4/188 ... yes 4/189 ... yes 299/190 ... yes 299/191 ... yes 75/192 ... yes 305/193 ... yes 305/195 ... yes 4/197 ... yes 305/199 ... yes 4/200 ... yes 317/202 ... yes 305/203 ... yes 199/204 ... yes 4/205 ... yes 8/206 ... yes 325/207 ... yes 119/208 ... yes 2/209 ... yes 232/210 ... yes 36/211 ... yes 30/212 ... yes 119/213 ... yes 75/214 ... yes 30/215 ... yes 178/216 ... yes 305/218 ... yes 4/219 ... yes 75/220 ... yes Redis version >= 4.0.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.6) Git version >= 2.22.0 ? ... yes (2.27.0) Git user has default SSH configuration? ... yes Active users: ... 312 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... no Try fixing it: Please migrate all projects to hashed storage as legacy storage is deprecated in 13.0 and support will be removed in 14.0. For more information see: doc/administration/repository_storage_types.md
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished