Keeping up with Passbolt releases

[MTSym]

I would like to now if there is an automatic release workflow planned so that the helm chart can keep up with the releases of the docker image?

I know that I could simply change the image tag in the values config and then run the tests as well as deployment tests inside our own CI but it would be great if this workflow could be made in this repo so everyone could benefit of it.

Another question: Would it be helpful to just state in an Issue that the new version is running fine and can be upgraded? Regardless there would still be the problem with changed configurations.

[dlen]

Hello @MTSym,

If I understand correctly your idea is that we create a new release of this chart every time we version bump the docker images and that we run the automated unit tests on each release in GitHub?

[MTSym]

Yes.

I mean you do not need to run the unit tests on GitHub directly you can do that in your own CI too.

What I fear and what already is happening is that the passbolt version is on 4.1.x while the one within the Helm chart if 4.0.x. As I already stated, I know that I can modify the version in my own "values.yml" file but it would be great if it would be "official".

[dlen]

Alright, we did not like the idea of generating a new release only with minor changes such as the image tag but we'll look into it as it might bring some value for the community as you mentioned.

[MTSym]

Running the tests in public would also be great so you and people using the Helm chart can see if an upgrade to a newer version does break something.

Unfortunately that will only be working if you do some sort of integration test where you deploy the helm chart and check that stuff is working. Which would involve a lot of time.

[zimmski]

We are doing automatic releases and so i can give you some reasons on what improves with that:

Doing the automatic version releases (if the pass the CI) helps with a few details:

• Requires tests to check that the installation/update works as expected. This makes Passbolt and this chart super stable.
• Removes the need for updating versions completely from all Passbolt developers, i.e. one can focus on other things than updating numbers.
• Opens the way for automatic updates of base-images, language/library versions.

All that happens with a bot, that just screams if something is wrong, which simply means catching bugs as they happen.

[zimmski]

@dlen @pabloelcolombiano 4.2.0 was released a few days ago, so this issue popped up again on our list. Any chance that updating the Helm chart is just a task in releasing a new PassBolt version?

[Tecnobutrul]

Hi, we bumped the image tag to 4.2.0-1-ce on the new 0.4.2 version. Regading the automated way to update is in our radar, but since it implies a good amount of time it will not happen in short time.