How to set an (environment) variable in the build script in Gitlab CI?

Question

I have a dummy build script in the Gitlab CI:

pwd
ci_app_path=$(pwd)
echo "INFO: current directory: $ci_app_path"

and I get this output when the system start the build process:

pwd
/home/kai/gitlab-runners/gitlab-ci-runner/tmp/builds/project-1

ci_app_path=$(pwd)

echo "INFO: current directory: $ci_app_path"
INFO: current directory:

so the variable was not set (or was set only for that line: as I know each line executed separately)

I heard about push/pop mechanism to reach the functionality I desired, but could not find any details, how to implement that.

Update:

as I thought, each line is going executed separately. So the variable scope is only one line, where it is defined:

script:

pwd
ci_app_path=$(pwd) && echo "INFO: current directory: $ci_app_path"

output:

pwd
/home/devuser/gitlab-runners/gitlab-ci-runner/tmp/builds/project-1

ci_app_path=$(pwd) && echo "INFO: current directory: $ci_app_path"
INFO: current directory: /home/kai/gitlab-runners/gitlab-ci-runner/tmp/builds/project-1

I don't think that writing the whole script as a one-liner is a good idea/practice.

How to get the variables set while executing the build script?

P.S.

actually I wonder why the whole build script must contain no empty lines?, otherwise it returns:

No such file or directory

and a build fails on this place

I'm not familiar with gitlab, but this is the same type of issue faced with make (perhaps that is what gitlab ci uses?). With make, the idea is that if you have that many lines, you should save them to an external script and have make execute it. The Makefile is not a shell script, and should not be treated as one. gitlab ci may take the same approach. — chepner
– chepner, Commented Oct 14, 2013 at 12:34

Jakub Kania · Accepted Answer · 2016-12-02 11:58:21Z

10

Gitlab CI just plays shell commands so do what you do in *sh:

export ci_app_path=$(pwd)
echo "INFO: current directory: $ci_app_path"

answered Dec 2, 2016 at 11:58

Jakub Kania

16.6k2 gold badges44 silver badges51 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

rhtyd · Accepted Answer · 2013-11-28 14:23:48Z

1

By the time Gitlab-CI folks fix it, you may create a Makefile and export variables inside it and in Gitlab-CI pass the variables, for example

PWD=$PWD make

Makefile starts with a: export GOPATH=$(PWD)

answered Nov 28, 2013 at 14:23

rhtyd

112 bronze badges

Collectives™ on Stack Overflow

How to set an (environment) variable in the build script in Gitlab CI?

Update:

P.S.

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

Update:

P.S.

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related