Minor refactoring of .circleci yaml?
See original GitHub issueI wanted ask about: https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/.circleci/config.yml
I think
coverage:
docker:
- image: circleci/node:8
could simply take advantage of the alias defined earlier and use:
coverage:
<<: *defaults
Is there a reason why it doesn’t?
Also, I was curious about perhaps adding an alias for:
- checkout
- restore_cache:
<<: *cache_key_node_modules
- *npm_install_if_necessary
Since it pops up everywhere. Would this be overkill?
Thanks, Luiserebii~
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Minor refactoring of the .circleci config.yaml (#1885) · 188a5fd700 ...
Adding in "<<: *defaults" under "coverage" * Refactoring by capturing similar setup commands into single alias * Reverting changes, I am not certain...
Read more >Configuring CircleCI
This document is a reference for the CircleCI 2.x configuration keys that are used in the .circleci/config.yml file. You can see a complete...
Read more >Reusable Config Reference Guide - CircleCI
CircleCI reusable configuration elements require a version: 2.1 .circleci/config.yml file. Command, job, executor, and parameter names must start with a ...
Read more >Run jobs in parallel with workflows to decrease your build times
Learn how to use parallelism and workflows in your continuous integration and delivery (CI/CD) pipelines on CircleCI to improve efficiency ...
Read more >Configuration Introduction - CircleCI
Getting started with CircleCI config ... This guide covers the following topics: ... CircleCI believes in configuration as code. Consequently, the entire delivery ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Closed by accident, apologies, haha.
Closing as PR has been merged: #1885