Skip to content

Update ci-run to allow upload of junit results - #5147

Closed
etruong42 wants to merge 2 commits into
envoyproxy:mainfrom
etruong42:bep
Closed

Update ci-run to allow upload of junit results#5147
etruong42 wants to merge 2 commits into
envoyproxy:mainfrom
etruong42:bep

Conversation

@etruong42

Copy link
Copy Markdown

No description provided.

Signed-off-by: Ethan Truong <ethantruong@google.com>
@netlify

netlify Bot commented Aug 21, 2026

Copy link
Copy Markdown

Deploy Preview for nifty-bassi-e26446 ready!

Name Link
🔨 Latest commit c62f3fa
🔍 Latest deploy log https://app.netlify.com/projects/nifty-bassi-e26446/deploys/6a8dc4a467315f00083d8c65
😎 Deploy Preview https://deploy-preview-5147--nifty-bassi-e26446.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@phlax phlax left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably it would be better to make upload-artifact work the same way download-artifacts - ie with a foreach

Upload step loops through the `uploads` rather than require individually
named parameters.

Signed-off-by: Ethan Truong <ethantruong@google.com>
@etruong42

Copy link
Copy Markdown
Author

probably it would be better to make upload-artifact work the same way download-artifacts - ie with a foreach

I've added a new uploads parameter to loop through the artifacts to upload. I didn't remove the other fields to preserve backwards compatibility. LMKWYT!

@phlax

phlax commented Aug 25, 2026

Copy link
Copy Markdown
Member

snap! #5155

i started testing it but didnt get far

i think remove all backwards compat - esp the junit ones theres no junit landed yet - but i think we should just remove the upload-artifact altogether - envoy is the only consumer so cleaner to break

on that point - in my impl i made it a yaml config - so you can set things like fail-if-not-found or somesuch

@etruong42

Copy link
Copy Markdown
Author

snap! #5155

i started testing it but didnt get far

i think remove all backwards compat - esp the junit ones theres no junit landed yet - but i think we should just remove the upload-artifact altogether - envoy is the only consumer so cleaner to break

on that point - in my impl i made it a yaml config - so you can set things like fail-if-not-found or somesuch

I think your PR looks great! Should we close this one in the meantime? Happy to re-open later if it becomes relevant.

@phlax

phlax commented Aug 25, 2026

Copy link
Copy Markdown
Member

probably yep - just because it has a little extra in terms of configurability - apologies for taking over - mostly it was because i knew this was going to need to be tested before we land in envoy

@etruong42

Copy link
Copy Markdown
Author

probably yep - just because it has a little extra in terms of configurability - apologies for taking over - mostly it was because i knew this was going to need to be tested before we land in envoy

Not at all! This was not my wheelhouse at all, so I'm happy for an actual expert to take over.

@etruong42 etruong42 closed this Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants