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

remove bundler from the Gemfile #1110

Merged
merged 1 commit into from
May 27, 2019
Merged

Conversation

mojavelinux
Copy link
Contributor

@mojavelinux mojavelinux commented May 14, 2019

  • bundler doesn't belong in the Gemfile
  • fixes builds
  • downgrade dependencies for unsupported Ruby versions

@mojavelinux mojavelinux force-pushed the fix-build branch 2 times, most recently from 1f988ef to 584bab6 Compare May 14, 2019 06:15
- bundler doesn't belong in the Gemfile
- fixes builds
- downgrade dependencies for unsupported Ruby versions
@mojavelinux
Copy link
Contributor Author

With this PR, the existing CI builds now pass. I think this is extremely important to get merged asap as it will allow other PRs to be reviewed more easily. Could you have a quick look @jneen? If you don't have time right now, is there someone else you could delegate it to? Thanks!

@ashmaroli
Copy link
Contributor

Prior attempt at resolving CI builds: #1062

@mojavelinux
Copy link
Contributor Author

This PR addresses several other outstanding issues without changing any other policy. So technically it could be merged without discussion.

@mojavelinux
Copy link
Contributor Author

Is there anything we can do to move this forward? I think it's the baseline to begin to free up the other PRs.

@ashmaroli
Copy link
Contributor

@mojavelinux I'm not affiliated with this project at all. But out of curiosity, may I ask what those "several other outstanding issues" are and how using parallel only for outdated Rubies help..?

@mojavelinux
Copy link
Contributor Author

Simply put, the build runs to completion so we can see if it's the incoming changes causing the build to fail. There are 128 open PRs. No PR can be merged if the build is failing. https://github.com/jneen/rouge/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc

To clarify, we're not using parallel just for outdated Rubies. We're downgrading the version of parallel for outdated Rubies because parallel doesn't support them anymore in the latest version.

@mojavelinux
Copy link
Contributor Author

(Whether to remove the outdated Rubies is a separate discussion that shouldn't have to hold up fixing the build).

@jneen
Copy link
Member

jneen commented May 17, 2019

I do not work on this project anymore. Please ping @dblessing and @gfx.

@ashmaroli
Copy link
Contributor

To clarify, we're not using parallel just for outdated Rubies.

Ah I see. parallel is an indirect dependency. It was not clear from the diff here. I had to check my local Gemfile.lock to realize that parallel is brought into the mix via RuboCop..

Gemfile Show resolved Hide resolved
pyrmont added a commit to pyrmont/rouge that referenced this pull request May 17, 2019
This commit is intended to be compatible with rouge-ruby#1110 (ie. it can be
applied after that PR). It removes older Rubies from those tested by
Travis and removes cruft from Gemfile that is no longer needed once
older Rubies are dropped.
@mojavelinux
Copy link
Contributor Author

@dblessing @gfx I'm still keen on getting this merged so we can get the build back to green. I think that's a first step in getting this project back on its feet.

@pyrmont pyrmont merged commit e74066d into rouge-ruby:master May 27, 2019
@mojavelinux
Copy link
Contributor Author

🍾 🍻 🎉

@mojavelinux mojavelinux deleted the fix-build branch May 27, 2019 06:53
@ashmaroli
Copy link
Contributor

Woohoo! The first commit since months... 🎉

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.

4 participants