-
-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split -dx and base Containerfiles and Workflows #1134
Comments
I'm in two minds about this... It would increase the feedback loop in PRs and make us wait around double the time before merging the PRs, however it would reduce the overall time spent on builders since dx would not need to build everything in the base again. |
I bet dx continues to rev fast so it might end up freeing up builders if they were split? I'm curious now lol. |
There is a blocker for this. -dx builds are now dependent on the underlying image to build and be available. On pull requests we do not publish those images meaning that we will be unable to ensure that nothing in the underlying base has broken -dx. |
Unless we allow PRs to be published, this is blocked. |
An alternative could be to split the Containerfiles, but build both in a single workflow/job. This reduces the total build runner minutes, but adds some separation. E.g.
|
Currently our -dx images build the base image in the process of building them. With the reusable build workflow we can possible have -dx built directly from the just built base image.
The text was updated successfully, but these errors were encountered: