You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "jamesnetherton (via GitHub)" <gi...@apache.org> on 2023/11/30 08:00:29 UTC
[PR] Use native builder image pull strategy 'missing' to reduce interactions with quay.io [camel-quarkus]
jamesnetherton opened a new pull request, #5573:
URL: https://github.com/apache/camel-quarkus/pull/5573
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Use native builder image pull strategy 'missing' to reduce interactions with quay.io [camel-quarkus]
Posted by "aldettinger (via GitHub)" <gi...@apache.org>.
aldettinger commented on PR #5573:
URL: https://github.com/apache/camel-quarkus/pull/5573#issuecomment-1833489094
@jamesnetherton Looks interesting.
So, at each ci build, on first container build the image is pulled only once, and then reused ? And then we have a chance to get a potential container build image update on next build ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Use native builder image pull strategy 'missing' to reduce interactions with quay.io [camel-quarkus]
Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton commented on PR #5573:
URL: https://github.com/apache/camel-quarkus/pull/5573#issuecomment-1833494893
> So, at each ci build, on first container build the image is pulled only once, and then reused ?
Yes, correct. Pulled once on each CI node running the native build
> And then we have a chance to get a potential container build image update on next build ?
Yeah - CI nodes are ephemeral. So we start with a clean slate on every workflow run.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Use native builder image pull strategy 'missing' to reduce interactions with quay.io [camel-quarkus]
Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton merged PR #5573:
URL: https://github.com/apache/camel-quarkus/pull/5573
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org