Skip to content

Conversation

@phlax
Copy link
Member

@phlax phlax commented Jan 10, 2025

No description provided.

@phlax phlax force-pushed the github-build branch 2 times, most recently from 5ae1a86 to 34214bb Compare January 10, 2025 13:53
@phlax phlax marked this pull request as draft January 10, 2025 14:28
@phlax phlax force-pushed the github-build branch 4 times, most recently from d609af7 to 71f5e04 Compare January 14, 2025 13:57
Signed-off-by: Ryan Northey <[email protected]>
@phlax
Copy link
Member Author

phlax commented May 16, 2025

cc @nnewton @kindlehl

this is as far as i got wrt fixing envoyproxy/envoy#39287

i need to go through ci to figure out exactly how far that was

i think the general idea i had - 2 gcp/s dirs

  • build cache - writeable on main, public readable for prs
  • publishing - separate GCS bucket that is also public readable

i think we can make it so netlify just proxies the publishing bucket

@envoyproxy envoyproxy deleted a comment from netlify bot May 16, 2025
@envoyproxy envoyproxy deleted a comment from netlify bot May 16, 2025
@envoyproxy envoyproxy deleted a comment from netlify bot May 16, 2025
@envoyproxy envoyproxy deleted a comment from netlify bot May 16, 2025
@phlax
Copy link
Member Author

phlax commented May 16, 2025

had a quick look at gcs fuse - i dont see any existing github actions - so not immediately clear if it would work out of the box

i think its a really good idea tho, so im going to experiment with it - we use gsutil syncing elsewhere - so this could be really handy - will look adding an action in the envoy toolshed repo as a next step

@phlax
Copy link
Member Author

phlax commented May 16, 2025

not immediately clear if it would work out of the box

initial experimentation is looking very promising

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.

1 participant