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

Switch from git source to rubygems.manageiq.org #19564

Merged
merged 1 commit into from
Dec 10, 2019

Conversation

bdunne
Copy link
Member

@bdunne bdunne commented Nov 27, 2019

Gems published using: ManageIQ/manageiq-release#103

Gemfile Outdated Show resolved Hide resolved
@bdunne bdunne force-pushed the rubygems_manageiq_org branch from ed1ca15 to 8197268 Compare December 2, 2019 20:49
@bdunne bdunne force-pushed the rubygems_manageiq_org branch from 8197268 to e66d84d Compare December 2, 2019 20:55
@miq-bot
Copy link
Member

miq-bot commented Dec 2, 2019

Checked commit bdunne@e66d84d with ruby 2.5.5, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 1 offense detected

Gemfile

@Fryguy
Copy link
Member

Fryguy commented Dec 2, 2019

cc @simaishi Not sure how this affects the builds.

@simaishi
Copy link
Contributor

simaishi commented Dec 4, 2019

Since the gem version in this PR differs from what's current set in git based for each gem (thank you for that!), I don't think this switch will cause a problem.

@Fryguy
Copy link
Member

Fryguy commented Dec 5, 2019

@simaishi I'm also concerned because one of the gems is rugged ,which is a C extension

@simaishi
Copy link
Contributor

simaishi commented Dec 5, 2019

@simaishi I'm also concerned because one of the gems is rugged ,which is a C extension

That should be ok as we override rugged for downstream build anyway.

@Fryguy Fryguy merged commit 4ae33a2 into ManageIQ:master Dec 10, 2019
@Fryguy Fryguy added this to the Sprint 127 Ending Jan 6, 2020 milestone Dec 10, 2019
@bdunne bdunne deleted the rubygems_manageiq_org branch December 10, 2019 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants