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

Can Not Use Command Telnet In Git Bash

Answer : That's because telnet is not provided with git. In windows, you need to go to control panel, programs, turn windows features on/off and enable the telnet client. To add on to @lostbard's answer and @signonsridhar's comment, telnet utility need to be invoked with winpty to work on git bash. Example: MINGW64 ~ $ which telnet /c/WINDOWS/system32/telnet MINGW64 ~ $ winpty telnet localhost 2181 Zookeeper version: 3.4.14-4c25d480e66aadd371de8bd2fd8da255ac140bcf, built on 03/06/2019 16:18 GMT
Read more

AspenTech InfoPlus 21 - How To Connect And Query Data

Image
Answer : InfoPlus21 is process historian containing list of templates of different tag structure e.g. IP_AnalogDef, IP_DescreteDef, IP_TextDef etc. Based on process tags from DCS/OPC/Any other historian, the IP21 records are created and each record acts as a table in historian. ANS1: Aspentech software is only windows based compatibility however IP21 aspenONE Process Explorer is web based and therefore you can access it over any operating system using host url. ANS2: you can try SELECT statement to get data from IP21 Historian using it's end-user component SQLPlus or on excel add-ins. e.g. SELECT NAME, IP_DESCRIPTION, IP_PLANT_AREA, IP_ENG_UNITS FROM IP_ANALOGDEF RESULTS: I hope this help you understand better. Otherwise you need to first learn the structure of your IP21 historian tags to build the query e.g. If it has customized structure, then you have to build your own. Welcome in industrial-IT ! For these technology, the best option is the 'AspenTech...
Read more