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

Use Gemfile for bundler #2

Merged
merged 1 commit into from
Jan 9, 2016
Merged

Conversation

harding
Copy link
Contributor

@harding harding commented Jan 9, 2016

Create Gemfile, updated README.md and .travis.yml to use it with
bundler. This provides the following features:

  • Travis will automatically pull the dependencies from the Gemfile
  • Travis will cache the dependencies, speeding up CI testing
  • Simplifies instructions if we add new dependencies
  • Gemfile.lock makes sure everyone has exactly the same version of the
    dependencies, helping to stop some "works for me"/"doesn't work
    for me" bugs
  • Devs who use rvm will automatically have the correct version of ruby
    selected for them

Also removed ruby 2.2.3 from the .travis.yml since it causes the build
to run twice for each ruby version. Since we're not not doing app
development, we don't usually need to worry about forward compatability
at the minor-point-release level.

Also also corrected indent for env variable to get rid of a Travis error.

Create Gemfile, updated README.md and .travis.yml to use it with
bundler. This provides the following features:

- Travis will automatically pull the dependencies from the Gemfile

- Travis will cache the dependencies, speeding up CI testing

- Simplifies instructions if we add new dependencies

- Gemfile.lock makes sure everyone has exactly the same version of the
  dependencies, helping to stop some "works for me"/"doesn't work
  for me" bugs

- Devs who use rvm will automatically have the correct version of `ruby`
  selected for them

Also removed ruby 2.2.3 from the .travis.yml since it causes the build
to run twice for each ruby version.  Since we're not not doing app
development, we don't usually need to worry about forward compatability
at the minor-point-release level.

Also also corrected indent for env variable.
## Disable external link checking to prevent spurious failures because
## of other people's downtime. This can also avoid wasting their
## bandwidth.
script: bundle exec jekyll build && bundle exec htmlproof --disable-external ./_site
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we really want to not check external links? I thought it was a good check to catch links that go stale months or years later when no-one is looking.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think it's a good manual check that can be run time-to-time. But as an automated check it has two problems:

  1. It causes spurious CI failures when a server is temporarily unreachable.
  2. It sends the message that people should be polluting their PRs with unrelated link changes in order to fix CI failures.

btcdrak added a commit that referenced this pull request Jan 9, 2016
Use Gemfile for bundler
@btcdrak btcdrak merged commit e63df4e into bitcoin-core:gh-pages Jan 9, 2016
@harding harding deleted the gemfile branch January 16, 2016 14:55
ivan98q added a commit to ivan98q/bitcoincore.org that referenced this pull request Jan 18, 2018
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.

None yet

2 participants