Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automatically build new Intel OneAPI versions #55

Merged
merged 2 commits into from
Jan 19, 2022
Merged

Automatically build new Intel OneAPI versions #55

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
889d374
Automatically build new Intel OneAPI versions
davidbeckingsale Jan 18, 2022
2174c40
Add name for Intel key
davidbeckingsale Jan 18, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions ubuntu/intel/uptodate.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,9 @@ dockerbuild:
build_args:
intel_version:
key: intel
versions:
- "2021.2.0"
name: intel-oneapi-compilers
Copy link
Contributor

Choose a reason for hiding this comment

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

How is this being passed into the Dockerfile?

Copy link
Contributor

Choose a reason for hiding this comment

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

oh nevermind, you are updating an existing one right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yup, the intel key is used in the existing Dockerfile to drive the Spack install. This change means the versions will come from the Spack package, rather than the list.

Copy link

@mdavis36 mdavis36 Jan 18, 2022 •
edited
Loading

Choose a reason for hiding this comment

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

@davidbeckingsale I see this building 2021.4 as the latest, any chance of getting a 2022 build or is this a limitation of the spack packages for oneapi?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It should be finding the versions in the Spack package, which has up to 2022.0.1 - let me figure out what's going on.

Copy link
Contributor

Choose a reason for hiding this comment

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

ug it was GitHub!! Poozers.
image

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I see the following on the "Action" tab:

This scheduled workflow is disabled because there hasn't been activity in this repository for at least 60 days. Enable this workflow to resume scheduled runs.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm re-running it now. It's weird normally I get an email notification but because this isn't my org I didn't.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We are going through the same steps at the same speed 😆

Copy link

Choose a reason for hiding this comment

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

We need github actions to update our actions

type: spack
startat: "2021.2.0"

# Look for ubuntu versions for our base builds
ubuntu_version:
Expand Down