Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| devops:ci [2022-03-22 10:49] – Robbert Hofman | devops:ci [2022-09-02 16:04] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| ===== Authorization to clone git repos ===== | ===== Authorization to clone git repos ===== | ||
| - | Just like a normal git user, the CI pipeline also needs to prove it has the authority to clone a repository. | + | Just like a normal git user, the CI pipeline also needs to prove it has the authority to clone a repository. |
| - | As we know, there are 2 main ways to do that: over HTTPS (user/ | + | As we know, there are 2 main ways to do that: over HTTPS (user/ |
| - | In our case, the rosinstall files are defined using SSH (git@someurl), | + | In our case, the rosinstall files are defined using SSH (git@someurl), |
| === SSH === | === SSH === | ||
| - | Best practice | + | Best practice |
| === HTTPS === | === HTTPS === | ||
| You can use the environment variable $CI_JOB_TOKEN for free. It's included. You don't have to do anything. | You can use the environment variable $CI_JOB_TOKEN for free. It's included. You don't have to do anything. | ||
| - | < | + | < |
| some_early_stage: | some_early_stage: | ||
| script: | script: | ||
| Line 26: | Line 26: | ||
| </ | </ | ||
| + | ==== Propagating CI triggers ==== | ||
| + | We want the main pipeline to be triggered if a commit happens in ANY of the repositories that the pipeline depends on. \\ | ||
| + | This can be achieved by putting the following '' | ||
| + | <code yaml> | ||
| + | trigger-main: | ||
| + | trigger: | ||
| + | project: robotlab/ | ||
| + | branch: main | ||
| + | strategy: depend | ||
| + | </ | ||
| + | I learned that here: https:// | ||