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

APIComparer Console as NuGet package? #51

Open
devlead opened this issue Sep 15, 2015 · 8 comments
Open

APIComparer Console as NuGet package? #51

devlead opened this issue Sep 15, 2015 · 8 comments

Comments

@devlead
Copy link
Contributor

devlead commented Sep 15, 2015

Just stumbled upon this project on the twitters and it looks really useful 👍

Would like to run something like this on build servers as part of their build scripts, is there an existing / planned NuGet package for the Console today?

@andreasohlund
Copy link
Owner

Not at this stage, I actually have some plans to

  1. Run it on the buildserver
  2. Include the report in the artifacts (we're on TeamCity)
  3. Make a ping back to the gihub status api to make sure the link to it included in the "checks" section of each pull request

Let me know if you want to take a stab at it!

devlead referenced this issue Sep 15, 2015
Need to redo this soon to use that same logic as the site
@andreasohlund
Copy link
Owner

Side note: We use apiapprover for most of our projects so any changes to the public api is visible in pull requests if you know what to look for

https://github.com/JakeGinnivan/ApiApprover

Example:

https://github.com/Particular/NServiceBus/pull/2890/files#diff-1eb180a4f6d35cd0c53fde55c1a077b3

@devlead
Copy link
Contributor Author

devlead commented Sep 15, 2015

Interesting, I'm one of the maintainers behind @cake-build , see this could be an great potential add-in or tool for us.

I see great benefit for a tool like this, thanks for your time, tips & info 👍

@Mpdreamz
Copy link

Mpdreamz commented Jan 7, 2016

+1 would love to see the console version on nuget

@andreasohlund
Copy link
Owner

Wouldn't chocolatey be more appropriate since its an "app" ?

@Mpdreamz
Copy link

Mpdreamz commented Jan 8, 2016

Not a big purist but most build related tools end up on nuget (xunit console, paket, gitlink) where as chocolatey is more for desktop app / services IMO 😄

@andreasohlund
Copy link
Owner

Fair enough, not having to bother with the approval mess that comes with chocolatey would be a win

@devlead
Copy link
Contributor Author

devlead commented Jan 8, 2016

@andreasohlund @Mpdreamz +1 for nuget, as it's almost always available in the build tool chain (i.e. Cake build scripts has "native" support for fetching tools via Nuget). Nothing stopping you from doing both though. Chocolatey is great for the dev machine or when you want it to be available globally.

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

3 participants