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

Automated builds with Cake #91

Merged
merged 2 commits into from
Apr 26, 2017
Merged

Conversation

nbarbettini
Copy link
Contributor

@nbarbettini nbarbettini commented Apr 26, 2017

Closes #74

  • Automatically build and run tests
  • Supports deploying artifacts automatically (can be enabled later)

@nbarbettini nbarbettini requested a review from abatishchev April 26, 2017 14:05
@abatishchev abatishchev added this to the 3.0 milestone Apr 26, 2017
Copy link
Member

@abatishchev abatishchev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nbarbettini nbarbettini merged commit 0d29613 into jwt-dotnet:master Apr 26, 2017
@nbarbettini nbarbettini deleted the cake branch April 26, 2017 18:29
@nbarbettini
Copy link
Contributor Author

The next step should be to sign up for AppVeyor (if you haven't already) and turn it on for this repo. If you need help, let me know!

@abatishchev
Copy link
Member

Yes, please, go ahead, I haven't registered iirc, not for this project definitely.

@nbarbettini
Copy link
Contributor Author

I'm not sure if I can do it, but I'll check.

@nbarbettini
Copy link
Contributor Author

@abatishchev Yeah, since I'm not an owner of the repo, I can't turn it on for the main fork. I can turn it on for my personal fork. It should be pretty simple:

  1. Go to https://ci.appveyor.com/
  2. Register using Github, authorize it to your Github account
  3. Go to Projects, toggle this repo (jwt) on
  4. That should be it 😄

@abatishchev
Copy link
Member

I got this https://ci.appveyor.com/project/abatishchev/jwt/. Should I make any configuration changes?

@nbarbettini
Copy link
Contributor Author

I usually check "Ignore branches without appveyor.yml". Double check that Visual Studio 2017 is selected under Environment. Everything else should be handled by appveyor.yml. You can try kicking off a build manually and see if it works!

@abatishchev
Copy link
Member

  • Skip branches without appveyor.yml
  • Build worker image: Visual Studio 2017

@nbarbettini
Copy link
Contributor Author

After #92 that last step will be unnecessary 😄

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

Successfully merging this pull request may close these issues.

2 participants