Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(circleci): Update CircleCI recipes config #2018

Merged
merged 1 commit into from
Jul 8, 2021
Merged

docs(circleci): Update CircleCI recipes config #2018

merged 1 commit into from
Jul 8, 2021

Conversation

KyleTryon
Copy link
Contributor

Updates the included CircleCI config file example.

  • Now uses 2.1 style config
  • Uses Node Orb
  • Use pre-defined node/test job
  • Uses Matrix jobs to test multiple node versions.
  • Updated Node versions
  • Using new CircleCI docker images (from node executor)
  • Updated language/terminology in description

Updates the included CircleCI config file example.

* Now uses 2.1 style config
* Uses Node Orb
* Use pre-defined node/test job
* Uses Matrix jobs to test multiple node versions.
* Updated Node versions
* Using new CircleCI docker images (from node executor)
* Updated language/terminology in description
@KyleTryon
Copy link
Contributor Author

If desired I could instead make a PR that does not use Orbs. The outcome would look much more similar to the existing config but only with updated images and such. The suggestion in this PR is more optimized though perhaps maybe a bit opaque for new users.

Copy link
Member

@gr2m gr2m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say you are the expert and know what's best 😄 thanks for the updates!

@gr2m gr2m merged commit 413ffd2 into semantic-release:master Jul 8, 2021
steps:
- checkout
- run: npm install
- node/install-packages # Install and automatically cache packages
# Run optional required steps before releasing
# - run: npm run build-script
- run: npx semantic-release
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry that i missed asking this before the merge, but does this step still belong here after defining the separate release job? it seems like this would run unconditionally w/o considering the required test job, but i could be misunderstanding something

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @travi,

This is assuming the user needs to run npm run build or something similar prior to running the semantic-release CLI. In that case, this is a more efficient way of installing packages.

Further down in the workflow you'll see this job requires the node/test job(s) to have completed first.

- release:
          requires:
            - node/test

Let me know if that clears it up, I could be misunderstanding something too

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, i think the detail that i was overlooking was the release name on line 24. without noticing that, i wasnt sure how the requirement was tied back to those steps. this is just my lack of familiarity with the CircleCI specifics, but it makes sense now. thanks for clarifying!

@github-actions
Copy link

🎉 This PR is included in version 17.4.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This PR is included in version 18.0.0-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants