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

Chemistry - Bond Angles In NH3 And NCl3

Answer : Solution 1: As Tan Yong Boon stated, it is Bent’s Rule with which we can explain the lower bond angle of \ce N F 3 \ce{NF3} \ce NF 3 when compared to \ce N H 3 \ce{NH3} \ce N H 3 . The rule as stated by Henry Bent: Atomic s character concentrates in orbitals directed towards electropositive substituents. Fluorine is more electronegative that hydrogen, and the \ce N − F \ce{N−F} \ce N − F bond would have greater p character than the \ce N − H \ce{N−H} \ce N − H bond. And more s character leads to large bond angles. Thus, the bond angle is greater in \ce N H 3 \ce{NH3} \ce N H 3 than in \ce N F 3 \ce{NF3} \ce NF 3 . Now, consider \ce N C l 3 \ce{NCl3} \ce NCl 3 . Clearly, \ce C l \ce{Cl} \ce Cl atom islarger in size than the central atom, nitrogen. Hence the higher bond angle here is due to the steric crowding caused by \ce C l \ce{Cl} \ce Cl atoms.(More pronounced than the electrongativity of \ce C l \ce{Cl} \ce Cl atom). They repel eachother and hence b...
Read more

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

Change The Font Size Of Visual Studio Solution Explorer

Answer : Go to Tools->Options->Environment->Fonts and Colors In "Show Settings for" chose "Environment Font" In "Font" replace Automatic to for example, Arial and change size. Change the font size of that setting, all Font size in the Explorers (Solution Explorer, Server Explorer and Toolbox) and menus will change. You can set that in Tools, Options.
Read more