Skip to content

Conversation

@Smjert
Copy link
Member

@Smjert Smjert commented Oct 17, 2024

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.

@Smjert Smjert added Windows CI/CD Anything about the Continuous Integration or Continuous Deployment tool used by the repository labels Oct 17, 2024
@Smjert Smjert requested a review from a team as a code owner October 17, 2024 18:59
@Smjert Smjert mentioned this pull request Oct 17, 2024
zwass
zwass previously approved these changes Oct 17, 2024
@Smjert
Copy link
Member Author

Smjert commented Oct 17, 2024

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.

@Smjert Smjert marked this pull request as draft October 17, 2024 19:54
@Smjert Smjert added the do not merge Do not merge PR as it's pending on some discussion or external factor. Reviewer should have context. label Oct 17, 2024
@Smjert Smjert removed the do not merge Do not merge PR as it's pending on some discussion or external factor. Reviewer should have context. label Oct 17, 2024
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.
@Smjert Smjert force-pushed the stefano/ci/windows-package-build-folder branch from 4533743 to ef369ec Compare October 18, 2024 10:49
@Smjert Smjert closed this Oct 20, 2024
@Smjert Smjert reopened this Oct 20, 2024
@Smjert Smjert marked this pull request as ready for review October 20, 2024 19:00
working-directory: ${{ steps.build_paths.outputs.PACKAGE_BUILD }}
id: packages
shell: bash
shell: powershell
Copy link
Member

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

Copy link
Member Author

@Smjert Smjert Oct 22, 2024

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.

Copy link
Member

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
Copy link
Member

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

@directionless directionless merged commit e360242 into osquery:master Oct 23, 2024
@Smjert Smjert deleted the stefano/ci/windows-package-build-folder branch October 23, 2024 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD Anything about the Continuous Integration or Continuous Deployment tool used by the repository Windows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants