rubygems_url Broken on Windows
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 35
- Forks
- 35
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 8
Description
Description
chef/scaffolding-chef-infra, on Windows only, sets the value of rubygems_url to a non-existent variable.
The linux scaffolding properly sets it here
The windows scaffolding sets it here which I believe should be the same as the linux version and rubygems_url "${cfg_rubygems_url}"
The outcome is that the rubygems url is never set or defaulted and produces the following output.
Scaffolding Version
chef/scaffolding-chef-infra v0.23.0
Platform Version
Windows Server 2012R2
Build or Run Output
FATAL: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '4'
---- Begin output of ["bundle", "install"] ----
STDOUT:
STDERR: [!] There was an error parsing `Gemfile`: The source must be an absolute URI. For example:
source 'https://rubygems.org'. Bundler cannot continue.
---- End output of ["bundle", "install"] ----
Ran ["bundle", "install"] returned 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare scaffolding-chef-infra/lib/linux/client-chunk.rb around lines 9-11 with scaffolding-chef-infra/lib/windows/client-chunk.rb around lines 13-15. Check how the Windows scaffolding assigns rubygems_url, then verify a Windows build using chef/scaffolding-chef-infra v0.23.0 no longer produces the invalid URI error during bundle install.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100