Skip to content

Conversation

@aelovikov-intel
Copy link
Contributor

It's unused in trunk and is only passed in sycl-rel-nightly.yml in sycl-rel-* branches (trunk version of it is an empty dummy stub). Not sure how future "release" branches are expected to get one.

I think making the change results in better alignment between different artifacts produced the workflow, no other reasons beyond that.

It's unused in trunk and is only passed in `sycl-rel-nightly.yml` in
`sycl-rel-*` branches (trunk version of it is an empty dummy stub). Not sure how
future "release" branches are expected to get one.
Copy link
Contributor

@KornevNikita KornevNikita left a comment

Choose a reason for hiding this comment

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

Not sure how future "release" branches are expected to get one.

If I understand your point correctly - sycl-rel-(x+1) will take the sycl-rel-nightly.yml workflow file from the sycl-rel-x branch.

In general LGTM, just minor notes.

type: string
required: false
description: |
If provided, create an addition toolchain artifact with the same name
Copy link
Contributor

Choose a reason for hiding this comment

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

Typo?
Same for windows

Suggested change
If provided, create an addition toolchain artifact with the same name
If provided, create an additional toolchain artifact with the same name

required: false
description: |
If provided, create an addition toolchain artifact with the same name
(`inputs.toolchain_artifact_filename`) as `toolchain_artifact` above
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a bit confusing. It's an archive name, not an artifact name, isn't it? From this sentence it seems like it creates one more "sycl_linux_default" or so. Can't we say "If provided, create an additional toolchain artifact without utilities used for testing called inputs.release_toolchain_artifact or just "If provided, create an additional toolchain artifact without utilities used for testing"?

Copy link
Contributor

@KornevNikita KornevNikita left a comment

Choose a reason for hiding this comment

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

@aelovikov-intel could you please also update it for win? Otherwise LGTM

@aelovikov-intel aelovikov-intel merged commit e193e79 into sycl Jul 31, 2025
33 of 35 checks passed
@aelovikov-intel aelovikov-intel deleted the ci-pack-release branch July 31, 2025 18:51
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.

4 participants