Skip to content
Snippets Groups Projects
Commit e30b3031 authored by Ralf Jung's avatar Ralf Jung
Browse files

fix docs

parent 53d4a19f
No related branches found
No related tags found
No related merge requests found
...@@ -80,28 +80,29 @@ regular `make -jN` before submitting an MR. ...@@ -80,28 +80,29 @@ regular `make -jN` before submitting an MR.
## How to test effects on reverse dependencies ## How to test effects on reverse dependencies
The `iris-bot` script makes it easy tot est the effect of a branch on reverse The `iris-bot` script makes it easy to test the effect of a branch on reverse
dependencies. It can start tests ensuring they all still build, and it can do dependencies. It can start tests ensuring they all still build, and it can do
comparative timing runs. comparative timing runs.
If you have suitable permissions, you can trigger these builds yourself.
But first, you need to do some setup: you need to create a GitLab access token But first, you need to do some setup: you need to create a GitLab access token
and set the `GITLAB_TOKEN` environment variable to it. Go to and set the `GITLAB_TOKEN` environment variable to it. Go to
<https://gitlab.mpi-sws.org/-/profile/personal_access_tokens>, pick a suitable <https://gitlab.mpi-sws.org/-/profile/personal_access_tokens>, pick a suitable
name (such as "iris-bot"), select the "api" scope, and then click "Create name (such as "iris-bot"), select the "api" scope, and then click "Create
personal access token". Copy the value it shows and store it in some suitable personal access token". Copy the value it shows and store it in some suitable
place, you will not be able to retrieve this value from GitLab in the future! place; you will not be able to retrieve this value from GitLab in the future!
For example, you could create a `.env` file in your Iris clone containing: For example, you could create a `.env` file in your Iris clone containing:
``` ```
export GITLAB_TOKEN=<your token here> export GITLAB_TOKEN=<your token here>
``` ```
Then you can easily get the token back into the environment via `. .env`. Then you can easily get the token back into the environment via `. .env`.
Once that setup is done, you can now use `iris-bot`. Once that setup is done, you can now use `iris-bot`. Set at least one of
Set at least one of `IRIS_REV` or `STDPP_REV` to control which branches of these `IRIS_REV` or `STDPP_REV` to control which branches of these projects to build
projects to build against (default to default git branch). `IRIS_REPO` and against (they default to the default git branch). `IRIS_REPO` and `STDPP_REPO`
`STDPP_REPO` can be used to take branches from forks. Setting `IRIS` to can be used to control the repository in which the branch is situated. Setting
"user:branch" will use the given branch on that user's fork of Iris, and `IRIS` to "user:branch" will use the given branch on that user's fork of Iris,
similar for `STDPP` and similar for `STDPP`.
Supported commands: Supported commands:
- `./iris-bot build [$filter]`: Builds all reverse dependencies against the - `./iris-bot build [$filter]`: Builds all reverse dependencies against the
...@@ -116,7 +117,7 @@ Examples: ...@@ -116,7 +117,7 @@ Examples:
against `myname/mybranch` from the main Iris repository. against `myname/mybranch` from the main Iris repository.
- `IRIS=user:branch ./iris-bot build examples` builds the [examples] against - `IRIS=user:branch ./iris-bot build examples` builds the [examples] against
the `branch` in `user`'s fork of Iris. the `branch` in `user`'s fork of Iris.
- `IRIS_REV=myname/mybranch ./iris-bot time examples` measure the timing impact - `IRIS_REV=myname/mybranch ./iris-bot time examples` measures the timing impact
of `myname/mybranch` from the main Iris repository on the [examples]. of `myname/mybranch` from the main Iris repository on the [examples].
[examples]: https://gitlab.mpi-sws.org/iris/examples [examples]: https://gitlab.mpi-sws.org/iris/examples
...@@ -8,7 +8,7 @@ from datetime import datetime, timezone ...@@ -8,7 +8,7 @@ from datetime import datetime, timezone
# do further test/analysis on a branch (usually an MR). # do further test/analysis on a branch (usually an MR).
# Set the GITLAB_TOKEN environment variable to a GitLab access token. # Set the GITLAB_TOKEN environment variable to a GitLab access token.
# Set at least one of IRIS_REV or STDPP_REV to control which branches of these # Set at least one of IRIS_REV or STDPP_REV to control which branches of these
# projects to build against (default to default git branch). IRIS_REPO and # projects to build against (defaults to default git branch). IRIS_REPO and
# STDPP_REPO can be used to take branches from forks. Setting IRIS to # STDPP_REPO can be used to take branches from forks. Setting IRIS to
# "user:branch" will use the given branch on that user's fork of Iris, and # "user:branch" will use the given branch on that user's fork of Iris, and
# similar for STDPP. # similar for STDPP.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment