Deploy to ECS - two pipelines created when pushing to branch
Summary
I was doing some tests on a sample project (related to deployment to ECS) when I noticed that two different pipelines, with different jobs, where triggered upon a push on a branch.
@mark.cesario noticed the same problem on one of his test project and let me know about it.
Example Project
https://gitlab.com/ebaque/rails-docker-ecs/pipelines
What is the current bug behavior?
Two pipelines created after a push to a branch.
What is the expected correct behavior?
One pipeline with all relevant jobs should be created.
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
(If you can, link to the line of code that might be responsible for the problem)