Fix E2E reporting to release tracker #6348
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
|
Size Report 1Affected ProductsNo changes between base commit (2ce5d19) and merge commit (385db68).Test Logs |
Size Analysis Report 1Affected ProductsNo changes between base commit (2ce5d19) and merge commit (385db68).Test Logs |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
E2E tests are running fine but there's an issue with the REST call to the release tracker to log the result.
The E2E workflow was recently changed from a
workflow_dispatchtrigger to arepository_dispatchtrigger. This changes how it receives input from the calling REST request, so the old github env variables no longer work. The correct variable is now passed in to the Node script through env variables to the "Tests succeeded" and "Tests failed" steps.