Skip to content
Snippets Groups Projects
Commit 9655d1ed authored by Nicolas Borboën's avatar Nicolas Borboën
Browse files

[FIX] Unicode missing char in LaTeX

parent 2f87f566
No related branches found
No related tags found
No related merge requests found
Pipeline #16722 passed
...@@ -23,7 +23,7 @@ modifying the current one. We ended to do it the following way: ...@@ -23,7 +23,7 @@ modifying the current one. We ended to do it the following way:
That way, the things are kept as close as possible to a standard dev/stage/prod That way, the things are kept as close as possible to a standard dev/stage/prod
environment but still in the same repo, keeping it simple to understand. environment but still in the same repo, keeping it simple to understand.
> 💡 Before diving into it, you may want to check the > :bulb: Before diving into it, you may want to check the
[documentation](https://docs.gitlab.com/ce/ci/README.html) and some [real world [documentation](https://docs.gitlab.com/ce/ci/README.html) and some [real world
examples](https://docs.gitlab.com/ce/ci/examples/README.html). examples](https://docs.gitlab.com/ce/ci/examples/README.html).
...@@ -35,7 +35,7 @@ described here: https://docs.gitlab.com/runner/install/ ...@@ -35,7 +35,7 @@ described here: https://docs.gitlab.com/runner/install/
It creates the gitlab-runner user on your system. It creates the gitlab-runner user on your system.
> 💡 On some Linux, you may want to > :bulb: On some Linux, you may want to
remove the `~/.bash_logout` file to avoid the issue remove the `~/.bash_logout` file to avoid the issue
[4092](https://gitlab.com/gitlab-org/gitlab-runner/issues/4092) — thanks me [4092](https://gitlab.com/gitlab-org/gitlab-runner/issues/4092) — thanks me
later. later.
...@@ -70,7 +70,7 @@ be used by default. In the `.gitlab-ci.yaml` files, all the jobs are set to be ...@@ -70,7 +70,7 @@ be used by default. In the `.gitlab-ci.yaml` files, all the jobs are set to be
run with the tags "test" — please double check that this tag is defined in the run with the tags "test" — please double check that this tag is defined in the
runner configuration, or allow your runner to be ran without any tags. runner configuration, or allow your runner to be ran without any tags.
> 💡 Read more about tags here: https://docs.gitlab.com/ee/ci/runners/#using-tags > :bulb: Read more about tags here: https://docs.gitlab.com/ee/ci/runners/#using-tags
## Check and edit the `.gitlab-ci.yaml` ## Check and edit the `.gitlab-ci.yaml`
...@@ -81,14 +81,14 @@ In short, this file defines the pipeline process, which contain stages. A stage ...@@ -81,14 +81,14 @@ In short, this file defines the pipeline process, which contain stages. A stage
can contains jobs, which describes what to do. Jobs can be parallel and manual, can contains jobs, which describes what to do. Jobs can be parallel and manual,
as of the "deploy_to_production" job. as of the "deploy_to_production" job.
> 💡 Note that if you want to keep "produced" files between jobs, you have to use the > :bulb: Note that if you want to keep "produced" files between jobs, you have to use the
[artifacts](https://docs.gitlab.com/ce/user/project/pipelines/job_artifacts.html) system. [artifacts](https://docs.gitlab.com/ce/user/project/pipelines/job_artifacts.html) system.
The file of this project define 4 stages: The file of this project define 4 stages:
- test just prints out some env variables. - test: just prints out some env variables.
- build creates the README.pdf. - build: creates the README.pdf.
- deploy creates the release via the `deploy.sh` script. Need a variable. - deploy: creates the release via the `deploy.sh` script. Need a variable.
- control final steps, does nothing but echoing a string. - control: final steps, does nothing but echoing a string.
![project's pipeline](./project_pipeline.jpg "project's pipeline") ![project's pipeline](./project_pipeline.jpg "project's pipeline")
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment