-
Notifications
You must be signed in to change notification settings - Fork 25
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
[CI] Fix the build on 3.0 #46
Open
sfgeorge
wants to merge
23
commits into
adhearsion:develop
Choose a base branch
from
sfgeorge:fix-the-build-on-3.0
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
0b1b94c
[CI] exhibit that the build is currently broken
sfgeorge a9d85a5
Use rake < 11.x until we upgrade RSpec past 2.x
sfgeorge 2777ef3
[CI] Test more Rubies
sfgeorge 3dbea15
Appease ruby-1.9.3 by holding cucumber back as < 3.0
sfgeorge 4691580
[CI] Relax Bundler development dependency.
sfgeorge 6a48e29
[CI] Always run cucumber in strict mode
sfgeorge c48b5a5
We don't use EventMachine
benlangfeld 6581059
Bump copyright year
benlangfeld c987ee9
Typo
benlangfeld 48da9cd
Make sure the test suite doesn't hang
benlangfeld f312242
[SPEC] Use simplified assertions from commit: "Make Stream usable in …
benlangfeld 937ef57
We don't support Celluloid 0.17 yet
benlangfeld 5c03334
Avoid rspec deprecations
benlangfeld 39625ca
Missed some RSpec deprecations
benlangfeld ece2346
[SPEC] Don't error on RSpec deprecations.
sfgeorge 7aecd91
The test server failing to shut down shouldn't itself fail specs
benlangfeld 976e90f
Convert specs to RSpec 2.99.2 syntax with Transpec
sfgeorge 6f33506
[SPEC] mark one skipped test as expected to fail
sfgeorge afd95f3
[SPEC] Replace undocumented, unsupported "feature" of #with
sfgeorge 2f41c09
[SPEC] Upgrade to RSpec 3.x
sfgeorge ab343b6
[SPEC] Run transpec one more time to fix deprecations
sfgeorge c55ec91
Revert "Use rake < 11.x until we upgrade RSpec past 2.x"
sfgeorge fc812fc
Merge branch 'fix-the-build' into fix-the-build-on-3.0
sfgeorge File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,19 @@ | ||
dist: xenial | ||
language: ruby | ||
sudo: false | ||
rvm: | ||
- 2.2.5 | ||
- 2.3.1 | ||
- jruby-9.1.2.0 | ||
- 2.2.10 | ||
- 2.3.8 | ||
- 2.4.5 | ||
- 2.5.3 | ||
- 2.6.3 | ||
- jruby-9.1.17.0 | ||
- jruby | ||
- ruby-head | ||
jdk: | ||
- openjdk8 # for jruby | ||
matrix: | ||
allow_failures: | ||
- rvm: ruby-head | ||
before_install: rvm list | ||
notifications: | ||
irc: "irc.freenode.org#adhearsion" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
default: --tags ~@wip | ||
default: --strict --tags ~@wip | ||
wip: --wip --tags @wip |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this was done to make Ruby 1.9.3 happy, but we no longer need to support that ancient version. Should this restriction be lifted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bklang I was thinking about that too (actually, I completed the cuke upgrade locally and confirmed it's a small effort).
Reason for possibly not doing it.. a handful of cucumber features fail unless we fully embrace cucumber >= 3.0n syntax. But since the syntax is not backwards compatible, it means that the same features will have to remain different on
support/2.x
vs.develop
.I'd lean towards having the two branches have a common denominator, unless it drags down
develop
in some way.But I can be swayed - I can update this branch to embrace cuke 3.0 if you like it. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your answer makes sense to me. There's no urgency to upgrade cucumber, so let's leave it for now. As you say, we can do this work whenever we have a better reason to do it, and in the meantime we benefit from keeping backports simple. 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Meant to reply back earlier... ... thanks man.