All Projects → bahmutov → Condition Circle

bahmutov / Condition Circle

Checks CircleCI environment before publishing successful build using semantic-release

Programming Languages

javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to Condition Circle

Dont Break
Checks if the current version of your package would break dependent projects
Stars: ✭ 200 (+525%)
Mutual labels:  plugin, ci
ci playground
Playground for Cloud CI development for C++
Stars: ✭ 23 (-28.12%)
Mutual labels:  circleci, ci
circleci-config-sdk-ts
Generate CircleCI Configuration YAML from JavaScript or TypeScript. Use Dynamic Configuration and the Config SDK together for live generative config.
Stars: ✭ 59 (+84.38%)
Mutual labels:  circleci, ci
Pupernetes
Spin up a full fledged Kubernetes environment designed for local development & CI
Stars: ✭ 199 (+521.88%)
Mutual labels:  ci, circleci
CIAnalyzer
A tool collecting multi CI services build data and export it for creating self-hosting build dashboard.
Stars: ✭ 52 (+62.5%)
Mutual labels:  circleci, ci
Rok8s Scripts
Opinionated scripts for managing application deployment lifecycle in Kubernetes
Stars: ✭ 248 (+675%)
Mutual labels:  ci, circleci
developer-ci-benefits
Talk docs—includes CI (Continuous Integration) benefits, description, and setup tips 💡💪
Stars: ✭ 29 (-9.37%)
Mutual labels:  circleci, ci
Ci Detector
Detect continuous integration environment and get information of current build
Stars: ✭ 138 (+331.25%)
Mutual labels:  ci, circleci
jt tools
Ruby on Rails Continuous Deployment Ecosystem to maintain Healthy Stable Development
Stars: ✭ 13 (-59.37%)
Mutual labels:  circleci, ci
docker-coala-base
coala base docker image
Stars: ✭ 20 (-37.5%)
Mutual labels:  circleci, ci
Env Ci
Get environment variables exposed by CI services
Stars: ✭ 180 (+462.5%)
Mutual labels:  ci, circleci
CI-Utils
Utilities for running Common Lisp on CI platforms
Stars: ✭ 18 (-43.75%)
Mutual labels:  circleci, ci
Nevergreen
🐤 A build monitor with attitude
Stars: ✭ 170 (+431.25%)
Mutual labels:  ci, circleci
Jmeter Elasticsearch Backend Listener
JMeter plugin that lets you send sample results to an ElasticSearch engine to enable live monitoring of load tests.
Stars: ✭ 72 (+125%)
Mutual labels:  plugin, ci
Cistern
A terminal UI for Unix to monitor Continuous Integration pipelines from the command line. Current integrations include GitLab, Azure DevOps, Travis CI, AppVeyor and CircleCI.
Stars: ✭ 161 (+403.13%)
Mutual labels:  ci, circleci
ci-minikube
run minikube on ci
Stars: ✭ 28 (-12.5%)
Mutual labels:  circleci, ci
Ci Matters
Integration (comparison) of different continuous integration services on Android project
Stars: ✭ 119 (+271.88%)
Mutual labels:  ci, circleci
Monorepo
Showcase of how to manage building projects inside monorepo with Gradle as build tool and CircleCI, Bitbucket Pipelines, Travis CI or GitHub Actions as CI tool.
Stars: ✭ 129 (+303.13%)
Mutual labels:  ci, circleci
lighthouse-circleci-example
An example repo demonstrating Lighthouse testing in CircleCi
Stars: ✭ 21 (-34.37%)
Mutual labels:  circleci, ci
build-status
Emacs minor mode that monitors and shows a buffer's build status in the mode line.
Stars: ✭ 26 (-18.75%)
Mutual labels:  circleci, ci

condition-circle

Checks CircleCI environment before publishing successful build using semantic-release

Inspired by condition-travis

NPM

Circle CI semantic-release manpm

You can read the step by step guide guide to setting up semantic-release with CircleCI (not just configuring this plugin).

Install and configure

npm install --save-dev condition-circle

Add the following to the package.json

"release": {
  "verifyConditions": "condition-circle"
}

This tells semantic-release plugins to use this package to verify the environment to make sure we are running on CircleCI.

Create circle.yml file and add post test command. Make sure to ignore its output - if there is no new release to be published, the build is still ok.

machine:
  node:
    version: "8"
test:
  override:
    - npm test
  post:
    - npm run semantic-release || true

Advanced

If you want to see the log messages from this plugin when it verifies the environment, use the following command.

post:
  - DEBUG=condition npm run semantic-release || true

If you want to see all messages from the semantic-release module as it runs, set the environment variable npm_config_loglevel=verbose because semantic release uses NPM logger module.

Advanced debug

To try running this module from the command line without releasing anything

  1. Edit package.json, set release.debug flag to true
  2. Execute command
CIRCLECI=true CIRCLE_BRANCH=master DEBUG=condition \
  npm_config_loglevel=verbose npm run semantic-release

Related

Small print

Author: Gleb Bahmutov © 2015

License: MIT - do anything with the code, but don't blame me if it does not work.

Spread the word: tweet, star on github, etc.

Support: if you find any problems with this module, email / tweet / open issue on Github

MIT License

Copyright (c) 2015 Gleb Bahmutov

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].