Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Research possible approaches to speeding up dependencies portion of CI builds

Open
#1,084 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js
Domain
ci-cd

Research direction

Start with circle.yml and the listed dependencies override commands. Measure the current yarn global add, node-sass, yarn install, and bower install timings, then research faster approaches for those steps. Done means documenting viable options and their expected or measured impact on CI build time.

Written by the indexing model from the issue text.

Description

Difficulty: Easy

Problem

Our circle.yml does the following at time of writing:

dependencies:
  pre:
    - |
      if [[ ! -e ~/.yarn/bin/yarn || $(yarn --version) != "${YARN_VERSION}" ]]; then
        curl -o- -L https://yarnpkg.com/install.sh | bash -s -- --version $YARN_VERSION
      fi
  cache_directories:
    - ~/.yarn
    - ~/.cache/yarn
    - /home/ubuntu/nvm/versions/node/v6.9.4/bin
    - /home/ubuntu/nvm/versions/node/v6.9.4/lib/node_modules
  override:
    - yarn global add bower
    - yarn global add phantomjs-prebuilt
    - yarn add node-sass
    - yarn install
    - bower install

The slowest steps of the override are as follows:

  • yarn global add bower ~10s
  • yarn global add phantomjs-prebuilt ~10s
  • yarn add node-sass ~25s
  • yarn install ~25s

Someone should research if there is any way to speed any of these steps up.

Dominant language
JavaScript
Stars
120
Forks
75
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.

More from code-corps/code-corps-ember

All issues in code-corps/code-corps-ember

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.