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

Failing when update is available for CI integration #6

Closed
andmos opened this issue Apr 4, 2020 · 1 comment
Closed

Failing when update is available for CI integration #6

andmos opened this issue Apr 4, 2020 · 1 comment

Comments

@andmos
Copy link

andmos commented Apr 4, 2020

It would be great with some switch/flag that changed the exitcode if an update is available for any package in a csproj or nuspec file. In that way, a CI build could be set up to run frequently and fail if an update is available that should be looked at.
Something like this should do the trick:

$ dotnet-deps
We found 7 😢 dependencies. For 🍺, type 'deps --update'
$ echo $?
1

That will integrate quite well with any CI tool.

@seesharper
Copy link
Owner

Closing this by #7 for now. Feel free to reopen if the need for a custom exit code should arise 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants