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.

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

Allow : in build docker image name #881

Merged
merged 1 commit into from
Jan 9, 2024

Conversation

sxa
Copy link
Member

@sxa sxa commented Jan 9, 2024

Also escapes the - character and adjusts the formatting of the error message. This was causing a problem for the riscv64 which use a slightly different format for these values and is causing a build job failure after the merging of #873

Signed-off-by: Stewart X Addison <sxa@redhat.com>
@sxa sxa self-assigned this Jan 9, 2024
@sxa sxa requested a review from steelhead31 January 9, 2024 14:52
Copy link

github-actions bot commented Jan 9, 2024

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,21"

@smlambert
Copy link
Contributor

In the long-run, is there a way to establish an actual naming convention and have riscv follow it, rather than having to make concessions for every case that doesn't follow a convention?

@sxa
Copy link
Member Author

sxa commented Jan 9, 2024

In the long-run, is there a way to establish an actual naming convention and have riscv follow it, rather than having to make concessions for every case that doesn't follow a convention?

We've never established an explicit convention but what RISC-V is as close as it reasonably be to everything else so is absolutely fine with a tag with the platform name in it and a parameter to tell docker that it's using a non-native container (for performance reasons) which is why it's different. It's a case of trailblazing and needing to have special parameters to do that. The parameters are broadly consistent with what Alibaba did for test.

Yeah we could make the convention more fixed, but it would have to include what we've done in this situation.

@sxa sxa merged commit f5a1dc3 into adoptium:master Jan 9, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants