-
Notifications
You must be signed in to change notification settings - Fork 13
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
Inspect the installation script that publishes PowerShell modules to the Gallery #388
Comments
Confirmed that the logging was the issue, since after #407 the release to the powershell gallery succeeds without errors (see https://dev.azure.com/codit/Arcus/_build/results?buildId=80513&view=logs&s=10f6e304-9e13-543a-c8b5-64733a986fd7). An earlier release failed where the nuget push returned a HTTP 400 bad request, which was correctly shown as an error and the release failed (see https://dev.azure.com/codit/Arcus/_build/results?buildId=80512&view=logs&j=d8644c48-ffa4-57a0-4dad-91968e195f84&t=c88a66d9-25c3-5b7a-40c9-937d8b63e849). |
The logging was mainly introduced (if I remember correctly) because we were having false positives for deployments. A failure ( |
From what I am seeing now the pipeline run fails with this error |
Ok, that's great. Best of both worlds, then. Thx a lot for investigating and fixing this! |
Describe the bug
The latest build (v1.0.1) failed with 'No such file or directory' while still successfully publishing the modules to the gallery.
To Reproduce
Steps to reproduce the behavior:
Not easy to test as it is a release pipeline.
Manual checks will be required.
Expected behavior
PowerShell modules are published and no errors are making the task fail.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: