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

Ensure post build clean occurs for non-mac&win platforms #1174

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

andrew-m-leonard
Copy link
Contributor

Fixes adoptium/temurin-build#4095

The refactor of the internal signing pipeline code was not calling postBuildWSclean for non-Windows&Mac platforms

Copy link

github-actions bot commented Jan 6, 2025

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"

@andrew-m-leonard
Copy link
Contributor Author

run tests

Copy link
Member

@sxa sxa left a comment

Choose a reason for hiding this comment

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

This is a side effect of having enableSigner mean two things:

  1. Enable GPG signing
  2. Enable the internal signing phase on applicable platforms (mac/windows).

Given the comment against this the if ( !enableSigner ) really wants to be if ( !enableInternalSigner ). This change will potentially clear out the workspace on Windows between the initial build and assemble phase which is not necessarily what we want. Would it make4 sense to switch the guard to something like if ( !enableSigner && (windows || mac) )

I thought I'd created an issue somewhere to try and create an explicit separate option for internal signing, which I think would be useful, but I can't find it so maybe I haven't created it yet :-)

@andrew-m-leonard
Copy link
Contributor Author

Copy link
Contributor

@adamfarley adamfarley left a comment

Choose a reason for hiding this comment

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

LGTM

@andrew-m-leonard andrew-m-leonard requested a review from sxa January 6, 2025 15:51
Copy link
Member

@sxa sxa left a comment

Choose a reason for hiding this comment

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

@eclipse-temurin-bot
Copy link
Collaborator

 PR TESTER RESULT 

✅ All pipelines passed! ✅

@karianna karianna merged commit f334a05 into adoptium:master Jan 6, 2025
30 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.

non-mac&windows builds seem to be leaving ~5GiB each in the workspace
5 participants