Atlantis 0.21.x cause duplicate pipelines in Gitlab

[frimik]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Overview of the Issue

If you have an internal pipeline in Gitlab, you will now get two separate pipeline IDs - one for the internal and one from the Atlantis commit status update.

Reproduction Steps

Have any pipeline enabled in gitlab via .gitlab-ci.yml AND the atlantis webhook as well. push a change in a merge request branch which starts both flows. You will get two pipeline IDs with each Stage in a separate pipeline.

Environment details

• Atlantis version: v0.21.x

Additional Context

Going back to v0.20.x restores the proper behaviour.

Slight suspicion it is being caused by #2636 - abb815e

Couldn't find anything else which seems related.

I've now also confirmed that rolling back only the commit from #2636 restores previous behaviour:

[nitrocode]

@jamengual should we release a patch 0.21.1 ?

[jamengual]

let's wait for @michelmzs to see if he replies?

[michelmzs]

I was able to reproduce the behavior here, we need to add the pipeline_id in the Commit Status to resolve this, I missed that. I can take a look into next days.

[nitrocode]

@michelmzs released a pre-release version for gitlab users

https://github.com/runatlantis/atlantis/releases/tag/v0.21.0-pre.20221207