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

update: remove aarch32 jdk8 from release-pipeline default setting #525

Merged
merged 2 commits into from
Dec 6, 2022

Conversation

zdtsw
Copy link
Contributor

@zdtsw zdtsw commented Dec 2, 2022

some more for the release pipeline
- do not have aarch32 in the same batch of build by release-openjdk8-pipeline due to different scmReference
- good to manually trigger that release by sharing the same pipeline with other jdk8 targets
- make additionalConfigureArgs only set for jdk11+, default to ' '

Ref: #514

	- we have a later arrival scmReference tag and need extra input
	- good to manually trigger that release by sharing the same
pipelin
	- make additionalConfigureArgs only set for jdk11+, default to
''
@github-actions
Copy link

github-actions bot commented Dec 2, 2022

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,19"

Copy link
Contributor

@karianna karianna left a comment

Choose a reason for hiding this comment

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

Are the docs updated to reflect how to run this arm32 Java 8 build separately during a release cycle?

@@ -90,6 +90,10 @@ node('worker') {
config.put('defaultsJson', DEFAULTS_JSON)
config.put('adoptDefaultsJson', ADOPT_DEFAULTS_JSON)

if(${javaVersion} != "8") { // for jdk11+, need extra config args to pass down
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe that should be >= 11?

@zdtsw
Copy link
Contributor Author

zdtsw commented Dec 3, 2022

Are the docs updated to reflect how to run this arm32 Java 8 build separately during a release cycle?

I have a draft PR https://github.com/adoptium/temurin-build/pull/3159/files for all the changes we make for next release.
Still more things to be added for "auto" trigger and some.

Copy link
Contributor

@karianna karianna left a comment

Choose a reason for hiding this comment

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

LGTM assuming the arm32 docs/instructions get landed at the same time

@zdtsw
Copy link
Contributor Author

zdtsw commented Dec 4, 2022

LGTM assuming the arm32 docs/instructions get landed at the same time

docs will be merged before 2023 Jan release as new instruction of how to generate/use/trigger release pipelines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aarch generation Issues that provide enhancements or fixes to the job generators jenkins-pipeline
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants