test integration tests with multiple charm builds #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
addyess
force-pushed
the
testing/gh-int-tests-archive-charm-builds
branch
from
75940d4 to
bc6ce87
Compare
addyess
force-pushed
the
testing/gh-int-tests-archive-charm-builds
branch
3 times, most recently
from
3e03809 to
ed91516
Compare
addyess
force-pushed
the
testing/gh-int-tests-archive-charm-builds
branch
from
ed91516 to
d9bc4b8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Use an adjusted integration run algorithm which builds all the charms and artifacts those charms.
Rationale
This is so the later run publish-charm action can find the artifacts from passed integration tests and publish those to the edge channel
Juju Events Changes
None
Module Changes
None
Library Changes
None
Checklist
src-docsurgent,trivial,complex)