fix(ci): add a "build-id" input var to ci builds #438
Merged
Conversation
This file contains hidden or 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
Codecov Report
@@ Coverage Diff @@
## main #438 +/- ##
=======================================
Coverage 12.08% 12.08%
=======================================
Files 44 44
Lines 5451 5451
=======================================
Hits 659 659
Misses 4675 4675
Partials 117 117 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Currently, the github workflows dependencies are chained as follows: build.yaml -> ci.yaml release.yaml -> ci.yaml convert.yaml -> ci.yaml build.yaml and release.yaml are inline builds but operate on different build triggers. convert.yaml is timer-based and works offline. Signed-off-by: Ramkumar Chinchani <rchincha@cisco.com>
smoser
approved these changes
Mar 10, 2023
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.
Currently, the github workflows dependencies are chained as follows:
build.yaml -> ci.yaml
release.yaml -> ci.yaml
convert.yaml -> ci.yaml
build.yaml and release.yaml are inline builds but operate on different build triggers. convert.yaml is timer-based and works offline.
What type of PR is this?
Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.