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

stop requiring mingw labels on Openj9 JDK8+11 builds #79

Merged
merged 1 commit into from
Mar 5, 2021

Conversation

sxa
Copy link
Member

@sxa sxa commented Mar 4, 2021

Based on adoptium/temurin-build#700 and the checks in #66 (comment) I think the tags are historic and no longer necessary as all bulid machines are set up the same way and the OpenJ9 builds no longer require special treatment (In fact 15+ do not have this tag).

@pshipton I presume you are not aware of any reason to keep mingw labels on the OpenJ9 builds to tie it to the IBM Cloud (SoftLayer) build machines we have?

Signed-off-by: Stewart X Addison [email protected]

@sxa sxa added the openj9 label Mar 4, 2021
@sxa sxa self-assigned this Mar 4, 2021
@github-actions
Copy link

github-actions bot commented Mar 4, 2021

Thank you for creating a pull request!
In order to run the pipeline tests I require an admin to post the following comment: run tests

@sxa
Copy link
Member Author

sxa commented Mar 4, 2021

run tests

@pshipton
Copy link

pshipton commented Mar 4, 2021

mingw is not required. OpenJ9 used to use mingw but switched to use clang ~Nov 2018.

@adoptopenjdk-github-bot
Copy link
Contributor

🟢 PR TESTER RESULT 🟢

✅ All pipelines passed! ✅

@M-Davies M-Davies added this to the March 2021 milestone Mar 4, 2021
@sxa
Copy link
Member Author

sxa commented Mar 5, 2021

mingw is not required. OpenJ9 used to use mingw but switched to use clang ~Nov 2018.

Seems to have just been an oversight that this limitation wasn't removed at that time :-) Thanks for the confirmation.

Copy link
Contributor

@andrew-m-leonard andrew-m-leonard left a comment

Choose a reason for hiding this comment

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

lgtm

@sxa
Copy link
Member Author

sxa commented Mar 5, 2021

Since this passed the checks it should be fairly safe. I'll merge and kick off 8 and 11 pipelines and provide the links here - we can see where all the jobs end up :-)

@sxa sxa merged commit 009cbc8 into adoptium:master Mar 5, 2021
@sxa
Copy link
Member Author

sxa commented Mar 5, 2021

vsebe pushed a commit to vsebe/ci-jenkins-pipelines that referenced this pull request Jul 11, 2022
Fix sign_build after merge
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.

5 participants