-
Notifications
You must be signed in to change notification settings - Fork 787
[CI] Simplify nightly docker images #16680
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
Conversation
Have a single docker image created with all the dependencies pre-installed so that it could be used for all internal CI needs for every target. Other workflows should be changed after this is merged and new image is uploaded to the registry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
@@ -78,7 +74,8 @@ development containers: | |||
NVidia/AMD and can be used for building DPC++ | |||
compiler from source with all backends enabled or for end-to-end testing | |||
with HIP/CUDA on machines with corresponding GPUs available. | |||
|
|||
- `devops/containers/nightly`: contains the latest successfully | |||
built nightly build of DPC++ compiler. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
built nightly build of DPC++ compiler. | |
built nightly build of DPC++ compiler, along with `latest` Intel drivers and NVidia/AMD development kits (same as `alldeps`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've done that on purpose. I'm planning to fuse tags for the base images as well, so that we'll only have 2204/2404/nightly images and once done that clarification will become irrelevant and even confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, seems reasonable to me.
@bader would you mind reviewing on behalf of the docs team? I need this merged to start working on the next step (modifying run-tests workflow). |
Built on top of #16680.
) Built on top of #16680.
First step on unifying our "base" image into a single "fat" container similarly to what's been done with nightly images at #16680.
First step on unifying our "base" image into a single "fat" container similarly to what's been done with nightly images at #16680.
Those dockerfiles were previosly renamed on `sycl` branch in intel#16255 and intel#16680. When we synced `.github` and `devops` changes from `sycl` to `sycl-rel-6_1_0` in intel#17612, we copied over new versions, but did not delete the old ones and this PR does exactly that.
Have a single docker image created with all the dependencies pre-installed so that it could be used for all internal CI needs for every target. Other workflows should be changed after this is merged and new image is uploaded to the registry.