[FOLIO-2339] Address incompatible bundler version when building FOLIO devdocs site Created: 04/Nov/19  Updated: 03/Jun/20  Resolved: 11/Nov/19

Status: Closed
Project: FOLIO
Components: Documentation
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Peter Murray Assignee: Peter Murray
Resolution: Done Votes: 0
Labels: devweb
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-2302 Update dev.f.o site dependencies 2019... Closed
Sprint:

 Description   

Errors in the AWS CodeBuild log:

[Container] 2019/11/02 03:20:23 Entering phase INSTALL 
[Container] 2019/11/02 03:20:23 Running command bundle install --path vendor/bundle 
You must use Bundler 2 or greater with this lockfile. 
 
[Container] 2019/11/02 03:20:23 Command did not exit successfully bundle install --path vendor/bundle exit status 20 
[Container] 2019/11/02 03:20:23 Phase complete: INSTALL State: FAILED 


 Comments   
Comment by Peter Murray [ 04/Nov/19 ]

Re-ran build with a previously successful configuration. It seemed to build correctly, but also said:

[Container] 2019/11/04 15:13:35 Entering phase INSTALL 
[Container] 2019/11/04 15:13:35 Running command bundle install --path vendor/bundle 
Warning: the running version of Bundler (1.13.5) is older than the version that created the lockfile (1.17.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
Comment by David Crossley [ 04/Nov/19 ]

With the new branch that is not building ( FOLIO-2302 Closed ), i had upgraded my local version of bundler to v2, so that is why the committed Gemfile.lock of this branch has newer version.

Comment by Peter Murray [ 11/Nov/19 ]

So much going on here. First, the Serverless devdoc build stack was pinning the version of Ruby to 2.3.1 – pretty old. To use later versions of Ruby, one now specifies a general-purpose CodeBuild image in the CodeBuild definition, then puts one or more runtime specifications in the buildspec.yml file.

Also hit on a edge case for naming S3 buckets – they can't end in a dash. So the branch-based CloudFormation stack was failing. Fixed that too.

It should be okay to merge the FOLIO-2302 Closed branch on devdocs now.

Comment by David Crossley [ 12/Nov/19 ]

Thanks a million Peter. All back in working order. Merged that branch now.

Generated at Thu Feb 08 23:19:56 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.