The helm release failed again

Question

The helm release failed again <https github com runatlantis helm charts actions runs 4474671200 jobs 7863372900>

Justin S · Answer

The index yaml is updated with that version but containing the wrong appVersion <https github com runatlantis helm charts blob gh pages index yaml L5>

PePe Amengual · Answer

ahhh this is because we did not released 0 23 2 helm chart because it was a bug fix

PePe Amengual · Answer

< Dylan Page>

Justin S · Answer

Im having trouble seeing the issue with the release stuff Ive never had to deal with the github actions before but what you guys have appears to be very similar to what Jenkins uses and I have submitted a good amount of Pull Requests to them created new charts and not hit issues

Justin S · Answer

The only difference I can even find is you guys have a bit of filtering on your `on push` and your version of helm is barely newer

Justin S · Answer

When someone looks at the helm chart stuff id love to atleast know whats going on I think my company is going to be able to start contributing alot of gitlab specific stuff so I want to make sure im not giving you all broken releases every time

PePe Amengual · Answer

the github action auto increment the version we just need to manually increment to match the real version with Atlantis

PePe Amengual · Answer

and then they will be in sync

PePe Amengual · Answer

when you say `I think my company is going to be able to start contributing alot of gitlab` what does this means

PePe Amengual · Answer

code improvements to Gitlab VCS on atlantis

Justin S · Answer

Yes

Justin S · Answer

But the chart is still sitting there broken <https github com runatlantis helm charts tree atlantis 4 12 1>

Justin S · Answer

I cant do anything to fix that or I would

PePe Amengual · Answer

we will have to fix it

PePe Amengual · Answer

Justin S · Answer

I dont understand why the previous Pull Request Failed

Justin S · Answer

App Version and Chart Version were bumped both to correct values

PePe Amengual · Answer

but it was rerun on an existing tag

PePe Amengual · Answer

ohhhh wait no

Justin S · Answer

it was a brand new PR i made

PePe Amengual · Answer

it was not

Justin S · Answer

PePe Amengual · Answer

yes it was yours

Justin S · Answer

Because that new app version has the gitlab fixes we got into it

PePe Amengual · Answer

let me check

PePe Amengual · Answer

I can t see why it did not work

PePe Amengual · Answer

the github action is very simple

Justin S · Answer

i checked it against Jenkins and they appeared very similar

Justin S · Answer

the failure looked like it already existed somehow

PePe Amengual · Answer

I guess the only thing could be the chart releaser action was updated to the latest

PePe Amengual · Answer

I want to still try to merge my PR and see the only thin I could thing if that the tag was created by hand before the release happened

PePe Amengual · Answer

maybe this is the problem <https github com helm chart releaser pull 111>

Dylan Page · Answer

Sorry I was traveling yesterday This is our exact issue <https github com helm chart releaser action pull 80>

Dylan Page · Answer

the action does a git diff instead of checking chartVersion

PePe Amengual · Answer

mmm so it created the tag before checking basically

PePe Amengual · Answer

I added the SKIP yesterday and it worked so I wonder what it does

Dylan Page · Answer

no it will only cut a new tag if it detects changes in the git diff

Dylan Page · Answer

hence why when we do no op bumps it ll fail with tag already exists because it doesn t bump a new version

Dylan Page · Answer

kinda unimpressed with how flaky this action is

Dylan Page · Answer

maybe we just do it ourselves