Experimenting with passing matrix outputs from previous matrix jobs #4
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
added 16 commits
July 1, 2024 10:32
…s set of matrix jobs I need a way to reuse the tags, image names, contexts which are parameters used for building the image. Currently these are available in the matrix jobs but I need to access these in the subsequent jobs so that I can rebuild images from cache. Using custom github action for this: Write outputs: https://github.com/cloudposse/github-action-matrix-outputs-write Read outputs: https://github.com/cloudposse/github-action-matrix-outputs-read
Got an error but values are being passed between steps of matrix jobs. Perhaps missing double quotes was the problem, let's see if that resolves it. ------ Got this error: Error: Outputs should be valid YAML --------------------- host_namespace: ghcr.io/everest/everest-demo image: mqtt-server context: ./mosquitto tags: ghcr.io/everest/everest-demo/mqtt-server:0.0.16 ghcr.io/everest/everest-demo/mqtt-server:latest labels: org.opencontainers.image.created=2024-07-01T17:35:09.789Z --------------------- YAMLParseError: Implicit keys need to be on a single line at line 5, column 1: tags: ghcr.io/everest/everest-demo/mqtt-server:0.0.16 ghcr.io/everest/everest-demo/mqtt-server:latest ^ ----------
So the quotes weren't the issue actually but the fact that the tags passed from the meta step were multiline values. Hence using block level scalar >- to let YAML interpret them as multi-line commands.
Still got the same error for multiline values when using >- YAMLParseError: Implicit keys need to be on a single line at line 6, column 1: ghcr.io/everest/everest-demo/mqtt-server:0.0.16 ghcr.io/everest/everest-demo/mqtt-server:latest ^
The direct access to tags and labels was giving errors since tags and labels were multiline values whereas the matrix output custom action needed single line values for the YAML parser to correctly parse the parameters. I found that we can access the tags and labels via the json object which is an output from the meta action. So, trying that approach now. ------- Another possible approach that I came across, but didn't try yet. I found that with the meta action, we can specify the delimiter / separator type for tags and labels: https://github.com/docker/metadata-action#inputs While tags can have a CSV datatype in docker build push action, labels can only have a List datatype: https://github.com/docker/build-push-action?tab=readme-ov-file#inputs Hence I believe the aforementioned approach would not work. -------
The custom write and read seems to have passed. But error when trying to read data in the env variables part. Error: The template is not valid. .github/workflows/cicd.yaml (Line: 138, Col: 26): A mapping was not expected ----- Now trying to output results directly first, let's see.
…e / read action JSON object data is simply passed as "Object" for tags_labels. Expected list of tags and labels.
…rest-demo into automate-tests-2
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.
I need a way to reuse the tags, image names, contexts which are parameters used for building the image. Currently these are available in the matrix jobs but I need to access these in the subsequent jobs so that I can rebuild images from cache.
Using custom github action for this:
Write outputs
Read outputs