- Sep 03, 2022
-
-
Edmund Smith authored
-
Edmund Smith authored
Although these are written as unit tests, these are really integration tests, because we only interact with the runner through the mocks it is connected to. There is no obvious way to write unit tests for Run in this framework. Each test simply spawns a runner using the two mocks (gitlab-runner-mock and lava-api-mock), and then tries to observe the gitlab-runner-mock state, after mutating the lava-api-mock state.
-
Edmund Smith authored
jog log -> job log
-
Edmund Smith authored
The log handling is complicated enough that it benefits from separating out, in order to make testing more practical. There are no functional changes. Tests to follow in a subsequent commit.
-
- Aug 12, 2022
-
-
Sjoerd Simons authored
Adjust the docker image generation to differentiate between tags and normal builds. For normal commmits it generates containers as <branch name>:<sha + pipeline id> as is the case now. For tags it the images will be placed under the lava-gitlab-runner name directly with the image tag matching the repository tag. The tagged images will also be protected from garbage collection to prevent users potentially missing images Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>
-
- Aug 11, 2022
-
-
Sjoerd Simons authored
Initial template transformation See merge request !3
-
Edmund Smith authored
This uses handlebars to substitute for job variables provided by gitlab, with the prefix of `job.`, so to substitute for `CI_JOB_TOKEN` you can use `{{ job.CI_JOB_TOKEN }}`. Note that this is the runner, and template transformations may already have been applied at an earlier generation step for the job (e.g. using jinja) which means the actual substitutions in this phase may need to have been escaped.
-
- Jul 18, 2022
-
-
Sjoerd Simons authored
-
- May 16, 2022
-
-
Sjoerd Simons authored
-
- Apr 13, 2022
-
-
Sjoerd Simons authored
Fix some grammatical issues See merge request !2
-
- Mar 31, 2022
-
-
Sjoerd Simons authored
-
- Mar 22, 2022
-
-
Sjoerd Simons authored
When using a namespace bound service account one cannot create namespaces; So removed that from and assume it has previously been setup
-
- Mar 21, 2022
-
-
Sjoerd Simons authored
The runner isn't expected to interact with the k8s APIs, so there is no need to create a service account
-
- Mar 05, 2022
-
-
Sjoerd Simons authored
Apparently in at least Apertis sometimes the runner was asked to monitor job files without any jobs in it. Which resulted in it actually querying for all jobs as queries had no filter. Adjust things to consider monitoring no jobs a failure Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>
-
Sjoerd Simons authored
-
Sjoerd Simons authored
This starts the port to the latest gitlab runner crate (0.0.2); It also converts the logging to tracing infrastructure which is now also used by gitlab-runner Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>
-
- Oct 23, 2021
-
-
Sjoerd Simons authored
Lava seems to be easily overwelmed when a lot of job queries happen so use a bigger interval one that backs off quickly as a workaround for now. Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>
-
- Oct 15, 2021
-
-
Christopher Obbard authored
The example jobs don't work by default since they include a wildcard. YAML expects wildcards to be inside double-quotes. Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>
-
Christopher Obbard authored
Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>
-
- Oct 02, 2021
-
-
Sjoerd Simons authored
-
- Oct 01, 2021
-
-
Sjoerd Simons authored
Add README See merge request !1
-
Sjoerd Simons authored
-
Sjoerd Simons authored
Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>
-
Sjoerd Simons authored
-
Sjoerd Simons authored
-
Sjoerd Simons authored
-