Could you clarify what is the purpose of the first two variables you define at the top of your .yaml file? (variables: WORKON_HOME: "$CI_PROJECT_DIR/nikola/.cache/venvs" PIPENV_CACHE_DIR: "$CI_PROJECT_DIR/nikola/.cache/pipenv") what is the point of this on your pipeline? where are these variables used?
The $CI_PROJECT_DIR vars are passed in from Gitlab CI itself, that's why they aren't declared inside the yaml file. The WORKON_HOME and PIPENV_CACHE_DIR vars simply tell the programs to cache stuff in a predicable location so that our CI caching process can find it every time.
Learning gitlab CI nowadays, these are very helpful!
This was very useful, Egee! Love these DevOps videos
Incredibly helpful and concise, thank you for this video! Big fan of the more infrastructure side of DevOps ;)
Loved watching this!
Still, I didn't understand the two directory that defined in the head. what will be stored inside WORKON_HOME and inside PIPENV_CACHE_DIR?
very helpful and useful. 👍
@Egee - I believe there is no "build" command when running "pipenv run nikola build"?, isn't it?
Could you clarify what is the purpose of the first two variables you define at the top of your .yaml file? (variables:
WORKON_HOME: "$CI_PROJECT_DIR/nikola/.cache/venvs"
PIPENV_CACHE_DIR: "$CI_PROJECT_DIR/nikola/.cache/pipenv")
what is the point of this on your pipeline? where are these variables used?
The $CI_PROJECT_DIR vars are passed in from Gitlab CI itself, that's why they aren't declared inside the yaml file. The WORKON_HOME and PIPENV_CACHE_DIR vars simply tell the programs to cache stuff in a predicable location so that our CI caching process can find it every time.
At @1:47 you are referring to jobs as stages. Those were jobs for a single stage.