-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In gitlab, "apply" pipeline hangs on plans if there are no changes, since 0.25.0 #3725
Comments
We are getting some gitlab strangeness as well, not sure if the issue is related.
it then starts applying, gets to the 2nd of 10 applies, and just stops doing anything
The apply that never ends, is completed though..
This is on the Atlantis 0.25.0 |
I think the above PR might fix the issue, I still have to figure out how to test it on my side though |
maybe you guys can try to figure out how to reproduce it , maybe there is a
correlation with the number of projects in autoplan?
…On Wed, Sept 6, 2023, 7:13 p.m. Luke Massa ***@***.***> wrote:
I *think* the above PR might fix the issue, I still have to figure out
how to test it on my side though
—
Reply to this email directly, view it on GitHub
<#3725 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ3ERB3OYJY67BYR2D7FR3XZEUVLANCNFSM6AAAAAA4GVGKJM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I was actually just able to test out my change in #3747, which at least fixes the specific problem I reported. |
Community Note
Overview of the Issue
Since upgrading to 0.25.0, when an MR is planned in gitlab that does not have "no changes", the "apply" pipeline runs and hangs. After the user types "atlantis apply", the actual apply goes, so this seems more an aesthetic issue than anything, but it's confusing for users and also disrupts automation we have that expects there to be no pipelines running after plan finishes.
Reproduction Steps
Logs
Logs
Environment details
Atlantis server-side config file:
Repo
atlantis.yaml
file:Additional Context
This is what pipelines look like when there are changes. Note that the plan has been posted, and yet the pipeline has been stuck "running" doing nothing for several minutes (the same plan from the log output, which also went quiet after the plan was done).
When there are no changes, it still runs the "apply" job (which I believe is different than before, but not itself a problem). However in this case, it "completes", so there is no running pipelines, and this is fine.
The text was updated successfully, but these errors were encountered: