ci/cd base

[mina1460]

Description

creating a manually-triggered github workflow to release jimmctl snap to snapstore

Fixes CSS-4742

Engineering checklist

Check only items that apply

• Documentation updated
• Covered by unit tests
• Covered by integration tests

Test instructions

Not tested yet! running the workflow would release the snap to the snapstore, which I don't want to do.

Notes for code reviewers

Any guide on how test github actions that release packages would be appreciated

[ale8k]

I think there's a snap action... @kian99 you used it right?

[kian99]

I'm not sure if there's a snap action but I have used existing charm actions for releasing e.g. https://github.com/canonical/charming-actions we should look for existing Snap actions. I found https://github.com/snapcore/action-publish which I found via https://snapcraft.io/docs/ros-with-github-actions
There's also https://github.com/marketplace/actions/snapcraft-action

[mina1460]

@kian99 @ale8k
I am using the ready-made actions in the release yaml. I edited the name here so that it is also updated to jimmctl.

Are you referring to something else other than the one I used for snap building and publishing?

[kian99]

Ah yes I see that's the case in the release.yaml PR, I hadn't taken a look at that yet. This building one is fine, unless there is also a snapcore/build action you can use and clean up what already exists.

[kian99]

This is not the correct snapcraft.yaml to edit, this one is for the JIMM server, there will be another one where the name is JAAS that needs to be renamed to jimmctl

[kian99]

Ah yes I see that's the case in the release.yaml PR, I hadn't taken a look at that yet. This building one is fine, unless there is also a snapcore/build action you can use and clean up what already exists.

[kian99]

Same comments as in #1031 otherwise lgtm