linkedin / linkedin/dr-elephant

bower install error on running jenkins/build_image.sh

Open
#715 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.4k
Forks
839
PR merge metrics
No merged PRs in 30d

Description

When running jenkins/build_image.sh, we see this error coming up:
ECMDERR Failed to execute "git ls-remote --tags --heads https://github.com/ember-cli/ember-cli-shims.git", exit code of #128 that keeps the static files from being built:
cp dist/assets/dr-elephant.css /dr-elephant/public/assets/ember/
cp: cannot stat 'dist/assets/dr-elephant.css': No such file or directory

  • cp dist/assets/dr-elephant.js /dr-elephant/public/assets/ember/
    cp: cannot stat 'dist/assets/dr-elephant.js': No such file or directory
  • cp dist/assets/vendor.js /dr-elephant/public/assets/ember/
    cp: cannot stat 'dist/assets/vendor.js': No such file or directory
  • cp dist/assets/vendor.css /dr-elephant/public/assets/ember/
    cp: cannot stat 'dist/assets/vendor.css': No such file or directory
  • cp -r dist/fonts /dr-elephant/public/assets/
    cp: cannot stat 'dist/fonts': No such file or directory

this error can be fixed manually by calling
sudo npm install -g bower
cd web; bower install; cd ..
and adding SSL disabling configuration to web/.bowerrc file before running the script. but if I put this web/.bowerrc file into the directory before running the script and hoping for the compile.sh to pick it up. it doesn't work.
{
"directory": "bower_components",
"registry": "https://registry.bower.io/",
"strict-ssl": false
}

does anyone know what's wrong and how I can fix the issue here? https://github.com/linkedin/dr-elephant/blob/916c25d5845f534ec2648fe17d978cd48a8bd284/compile.sh#L374

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with jenkins/build_image.sh and compile.sh around line 374, then inspect web/.bowerrc and the Bower step that runs before static files are copied. Run the build to reproduce the git ls-remote failure and verify that the build completes with dist/assets and dist/fonts present.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
build-system, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.