Skip to content
Snippets Groups Projects
Commit d0f39f91 authored by marcoemi.poleggi's avatar marcoemi.poleggi
Browse files

Update README.md

parent 6cdafa58
Branches
No related tags found
No related merge requests found
......@@ -53,7 +53,7 @@ conventions about the *command line prompt*:
Fork this project into your personal namespace and configure it (menu `Settings`):
- In `General > Visibility,...`:
* [x] `Repository > CI/CD:` active with "Only project members" (or empty)
* [x] `Operations`: active with "Only project members" (or empty)
* [x] `Environments`: active with "Only project members" (or empty)
Our GitLab instance comes with a shared Docker-based CI/CD *runner* (or executor).
Generate your [SSH key pair](https://docs.gitlab.com/ee/ci/ssh_keys/) to interact with your VM instance.
......@@ -85,13 +85,14 @@ stages:
- test
- deploy
# Do here anything common to all jobs' scripts
before_script:
- # install needed packages in this runner (Web servr, etc.)
- # configure the git client on this runner
- # set up SSH keys via ssh-agent
- # launch the ssh-agent and feed it our key from var $SSH_PRIVATE_KEY
- echo "$SSH_KNOWN_HOSTS" >> ~/.ssh/known_hosts
default:
# Do here anything common to all jobs' scripts
before_script:
- # install needed packages in this runner (Web servr, etc.)
- # configure the git client on this runner
- # set up SSH keys via ssh-agent
- # launch the ssh-agent and feed it our key from var $SSH_PRIVATE_KEY
- echo "$SSH_KNOWN_HOSTS" >> ~/.ssh/known_hosts
# Jobs run in parallel within the same stage, unless dependencies are expressed
unit_test1:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment