Build, deploy and then use prebuilt docker image #623
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
This avoids consumers from needing to wait for Dockerfile to build every run
3 tasks
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.
This relates to #452.
With these changes, once a PR is merged to
masteror a tag is added (e.g.v0.8.3), the newcontainer-build.ymlworkflow will run. This will then build some metadata for the image, login to Github Container Registry, and then build/push the package. The package will appear here. You can see an example of how it would look on my fork here.Then the action will now load the image from this public registry path:
image: 'docker://ghcr.io/stoplightio/spectral-action:0.8.3'It makes use of the public registry using the syntax described here and here (this is gcr, we will use ghcr).
You can see the CI test passing and pulling the image as expected here.
Note: You will need to add a secret to this repository called
CR_PATwhich has thewrite:packagespermission from a Personal Access Token (aka PAT). It will needs to be created here.