-
Notifications
You must be signed in to change notification settings - Fork 585
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
Octopus deploy trace always marked failures #2428
Octopus deploy trace always marked failures #2428
Conversation
Release 5.18.0
* NEW: Add `Fake.DotNet.Testing.Coverlet`, thanks @Tarmil - #2413 * BUGFIX: `paket pack` module was broken, thanks @sergey-tihon - #2418
forgot how partial application works and that it is not just magic. also forgot ignore is a function.
@matthid The FAKE-CI failed due to the
I ran the |
Nvm about the previous comment. Looks like they are passing now. |
Maybe a flaky test, the error was:
Due to parallel build the output is further above. In any case I don't see this related to your changes. The Cli IntegrationTests are kind of flaky by design which is something I'm repeatedly think about but never come up with a good solution. |
result | ||
|
||
/// Creates a release and returns the exit code. | ||
let createReleaseWithExitCode setParams = |
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.
Are you sure this is doing what you intended? From a quick look it looks like this either returns 0
or throws an exception (without actually testing it)
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.
I hadn't tested that yet but looking at it again after the weekend, yes this seems wrong.
@matthid I added 2 tests but wanted to make sure me making the internals visible to the test project was an okay pattern for you before adding the rest. Also I wasn't sure the best way to handle the exception being throwing because it has the commandString in the message. I ended up creating the commandline again but I feel like a better solution exists. ( This part https://github.com/fsharp/FAKE/pull/2428/files#diff-79e02955429be1b80880ec40c24d8c6fR319 ) |
Yes it is. Thanks a lot! Looks very good now. Let's see how it works out! |
Description
Two changes:
A trace in the Octo.fs doesn't mark itself as successful before going out of scope so the output is always the
Failed
statusAdds additional functions to return the exit code of the octopus command.
TODO
help/markdown
)