-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
CI: Add a specific package build folder on Windows jobs #8446
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
CI: Add a specific package build folder on Windows jobs #8446
Conversation
|
Sorry, should've put this in draft; seems the artifacts have not been uploaded for Windows, so there's some place I may have missed something. |
The packaging logic expects to enter into a specific folder to create Windows packages inside. This folder was not being created and the workflow was not complaining for its absence, using the root of the workspace. Add the folder as it exists for the other jobs.
4533743 to
ef369ec
Compare
| working-directory: ${{ steps.build_paths.outputs.PACKAGE_BUILD }} | ||
| id: packages | ||
| shell: bash | ||
| shell: powershell |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't look like powershell syntax to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
echo and ls definitely work under a powershell shell, they are just aliases (the .FullName part is the giveaway for powershell). Mostly this was to get the path to the files in the Windows format.
If you prefer I can change them to their non-aliased version; it was mostly for the reduced verbosity to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was the $() I wasn't sure of
| working-directory: ${{ steps.build_paths.outputs.PACKAGE_BUILD }} | ||
| id: packages | ||
| shell: bash | ||
| shell: powershell |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was the $() I wasn't sure of
The packaging logic expects to enter into a specific folder to create Windows packages inside.
This folder was not being created and the workflow was not complaining for its absence, using the root of the workspace.
Add the folder as it exists for the other jobs.