Skip to content
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

Move away from using juju-bundle #23

Closed
simskij opened this issue Feb 17, 2022 · 0 comments · Fixed by #151
Closed

Move away from using juju-bundle #23

simskij opened this issue Feb 17, 2022 · 0 comments · Fixed by #151
Labels

Comments

@simskij
Copy link
Member

simskij commented Feb 17, 2022

Just a note for @DomFleischmann that we need to think
carefully about using this, and what the succession plan is > for that tool now that Ken has likely stopped maintaining it.

Originally posted by @jnsgruk in #21 (comment)

simskij added a commit that referenced this issue Apr 20, 2022
turn off bundle test pending #23 and #40
simskij added a commit that referenced this issue Apr 29, 2022
* get and update gh Release

* charmcraft parse status and release

* helper function for parsing gh release body

* release charm action

* build release charm action

* catch error from github tagging

* Add charm path input to support multi charm repos

charmcraft.metadata() would fail if metadata.yaml is not in the current
directory
update readme with more information

* polish readme

* no longer support revision number as input

* Update integrate.yaml

turn off bundle test pending #23 and #40

* add description for multi charm repo

* Update release-charm/README.md

Co-authored-by: Simon Aronsson <simme@arcticbit.se>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant