Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add docs for using --env within manual trigger #953

Merged
merged 2 commits into from
Oct 23, 2024
Merged

Add docs for using --env within manual trigger #953

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
358b2e5
Add docs for using --env within manual trigger
Frawless Oct 22, 2024
9302bd6
Comments from Laura
Frawless Oct 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/configuration/upstream/tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,6 +227,14 @@ The labels should be in the format of comma-separated string.
You can also configure [`test_command.default_labels`](/docs/configuration#default_labels) to allow commonly used job combinations
to be triggered without the need for manual specification.

## Running tests with specific environment variables
From time to time, you may need to pass specific environment variables to your jobs.
To achieve this, you can use the `--env` option, which passes environment variables to Testing Farm.
You can set as many environment variables as you want; you just need to pass `--env `for each one.
For example, you can use the following command `/packit test --env MY_ENV=test --env MY_ENV_2=test_2`.
This command allows you to use `MY_ENV` and `MY_ENV_2` in Testing Farm jobs.
You can also unset an environment variable by not setting its value like `/packit test --env MY_ENV=`.

lbarcziova marked this conversation as resolved.
Show resolved Hide resolved
## Test job statuses
By default, while test jobs are waiting for their corresponding build jobs to finish,
their statuses share updates with the build jobs, for example `SRPM build is in progress...`
Expand Down
Loading