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

Revamp appveyor.yml file. #1590

Merged
merged 1 commit into from
Apr 22, 2016
Merged

Revamp appveyor.yml file. #1590

merged 1 commit into from
Apr 22, 2016

Conversation

djberg96
Copy link
Contributor

This is an update to the appveyor.yml file. A bit about the changes:

  • Only tests the master branch. I'm not sure why we care about other branches but I can add them if you feel it's necessary.
  • Uses Powershell in the "install" portion instead of cmd.exe. This makes it easier to skip gem installation if the dependencies we need are already installed. PS is just better in general.
  • Removes all that Travis stuff. I have no idea what that's about. This ain't Travis.
  • Caches the gem directories for each distribution. We don't need to re-provision gems every time we build, so this speeds up the build process.
  • No after-test task. No idea why we care about that.

I tried it with local settings on my own fork and it worked fine. All the builds, including 1.9.3, were green.

@@ -1,38 +1,38 @@
---
version: "{build}"
version: '{build}'
branches:
Copy link
Member

Choose a reason for hiding this comment

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

We do want these other branches

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@segiddins Why, do we ever backport? It's no problem to add them, just curious.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, we have in the past and might need to in the future, especially for security-related issues.

@simi
Copy link
Member

simi commented Apr 22, 2016

What about this line? Is that ENV['TRAVIS'] really Travis specific or CI specific? I think both Travis and Appveyor exports ENV['CI'].

Added additional branches, set TRAVIS env variable.
@djberg96
Copy link
Contributor Author

@segiddins Ok, I've updated the PR to include the additional branches.

@simi I've updated the PR so that it sets ENV['TRAVIS'] first. You're right that appveyor does export ENV["CI"] - it's set to true - so we should probably look at converting all instances of those in a future PR if "CI" serves as a sort of universal environment variable for continuous integration services in general.

@segiddins
Copy link
Member

@duckinator I'll let you review this

@duckinator
Copy link
Member

@simi we export the TRAVIS environment variable ourself. I'll look into this part as a separate PR after I catch up on my backlog -- I'll either use one they both already export, or renaming the one we export to be more generic. :)

@segiddins looking at it now.

@duckinator
Copy link
Member

@djberg96 this looks good to me! You even got 1.9.3 tests working on Appveyor. :D

@homu r+

@homu
Copy link
Contributor

homu commented Apr 22, 2016

📌 Commit e66fd6f has been approved by duckinator

@homu
Copy link
Contributor

homu commented Apr 22, 2016

⚡ Test exempted - status

@homu homu merged commit e66fd6f into rubygems:master Apr 22, 2016
homu added a commit that referenced this pull request Apr 22, 2016
Revamp appveyor.yml file.

This is an update to the appveyor.yml file. A bit about the changes:

* Only tests the master branch. I'm not sure why we care about other branches but I can add them if you feel it's necessary.
* Uses Powershell in the "install" portion instead of cmd.exe. This makes it easier to skip gem installation if the dependencies we need are already installed. PS is just better in general.
* Removes all that Travis stuff. I have no idea what that's about. This ain't Travis.
* Caches the gem directories for each distribution. We don't need to re-provision gems every time we build, so this speeds up the build process.
* No after-test task. No idea why we care about that.

I tried it with local settings on my own fork and it worked fine. All the builds, including 1.9.3, were green.
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

Successfully merging this pull request may close these issues.

6 participants