After mirror pull was success, external repo new commit was detected but no CI was triggered
Summary
CI/CD for external project doesn't seem working on Staging.
Steps to reproduce
- Create new user
- Create new group under gitlab-qa-sanbox
- Invite user to group as owner
- Login as user and import Github project in the UI
- After importing succeed, make changes in Github
- Send API request to trigger mirror
Example Project
Gitlab project - https://staging.gitlab.com/gitlab-qa-sandbox-group/qa-test-2021-07-01-13-33-23-a8e508041b826656/github-project-with-pipeline-74c966ad89643f24/-/tree/main
Github project - https://github.com/gitlab-qa-github/test-project
Test user qa-user-eeef059f1629e74c
What is the current bug behavior?
No CI was triggered.
What is the expected correct behavior?
CI should triggered if new changes were pulled.
Relevant logs and/or screenshots
Output of checks
Staging.gitlab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
Edited by Tiffany Rea