CircleCI - Different Value To Environment Variable According To The Branch


Answer :

The question is almost 2 years now but recently I was looking for similar solution and I found it.

It refers to CircleCI's feature called Contexts (https://circleci.com/docs/2.0/contexts/). Thanks to Contexts you can create multiple sets of environment variables which are available within entire organisation. Then you can dynamically load one of the sets depending of workflows' filters property.

Let me demonstrate it with following example:

Imagine you have two branches and you want each of them to be deployed into different server. What you have to do is:

  1. create two contexts (e.g. prod-ctx and dev-ctx) and define SERVER_URLenvironment variable in each of them. You need to log into CircleCI dashboard and go to "Settings" -> "Contexts".

  2. in your .circleci/config.yml define job's template and call it deploy:

deploy: &deploy steps:   - ...
  1. define workflows:
workflows:   version: 2   deploy:     jobs:       - deploy-dev:           context: dev-ctx           filters:             branches:               only:                 - develop       - deploy-prod:           context: prod-ctx           filters:             branches:               only:                 - master
  1. finally define two jobs deploy-prod and deploy-dev which would use deploy template:
jobs:   deploy-dev:     <<: *deploy    deploy-prod:     <<: *deploy

Above steps create two jobs and run them depending on filters condition. Additionally, each job gets different set of environment variables but the logic of deployment stays the same and is defined once. Thanks to this, we achieved dynamic environment variables values for different branches.


Use a bash script

In my projects, I archive that by using a bash script.

For example, this is my circle.yml :

machine:   node:     version: 6.9.5  dependencies:   override:     - yarn install  compile:   override:     - chmod -x compile.sh     - bash ./compile.sh

And this is my compile.sh 

#!/bin/bash  if [ "${CIRCLE_BRANCH}" == "development" ] then   export NODE_ENV=development   export MONGODB_URI=${DEVELOPMENT_DB}   npm run build elif [ "${CIRCLE_BRANCH}" == "staging" ] then   export NODE_ENV=staging   export MONGODB_URI=${STAGING_DB}   npm run build elif [ "${CIRCLE_BRANCH}" == "master" ] then   export NODE_ENV=production   export MONGODB_URI=${PRODUCTION_DB}   npm run build else   export NODE_ENV=development   export MONGODB_URI=${DEVELOPMENT_DB}   npm run build fi  echo "Sucessfull build for environment: ${NODE_ENV}"  exit 0

Comments

Post a Comment

Popular posts from this blog

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz
Read more

Can Feynman Diagrams Be Used To Represent Any Perturbation Theory?

Answer : Diagram machinery works also for perturbation theory in classical statistical mechanics and classical field theories. Generally, various kinds of diagrams constitute a pictorial way of talking about tensor products and their contractions while hiding the multi-linear algebra from the layman. In the simplest case, vertices (or blobs) represent vectors, matrices, tensors; vertices have ingoing and/or outgoing ports; ingoing ports denote (contravariant) ro indices; outgoing ports denote (covariant) co indices; directed arcs between blobs give a pair of equal indices summed over; different base spaces ⇔ \Leftrightarrow ⇔ different arc types; symmetric tensors ⇔ \Leftrightarrow ⇔ undirected diagrams; no labels are needed for internal lines. In many cases, the directed arcs are decorated (as thin, thick, broken,wavy, curly lines), each decoration indicating the presence of a so-called propagator, a function of its label to use as a weight in the sum, which may beco
Read more