2022-05-06 09:16:46 +03:00
include :
- 'ci/integration-template.yml'
2021-10-05 12:02:24 +03:00
2024-01-08 13:30:05 +03:00
# NOTE The integration tests use artifacts produced by the libvirt-perl
# and libvirt-python CI jobs, so the new target needs to be introduced
# there before it can be used here. The VM template for the target
# also needs to be created on the runner host.
2024-01-18 18:20:14 +03:00
centos-stream-9-tests :
extends : .integration_tests
2021-10-05 12:02:24 +03:00
variables :
# needed by libvirt-gitlab-executor
DISTRO : centos-stream-9
2022-03-30 17:45:04 +03:00
# can be overridden in forks to set a different runner tag
2022-03-21 15:51:53 +03:00
LIBVIRT_CI_INTEGRATION_RUNNER_TAG : redhat-vm-host
2021-10-05 12:02:24 +03:00
tags :
2022-03-21 15:51:53 +03:00
- $LIBVIRT_CI_INTEGRATION_RUNNER_TAG
2021-10-05 12:02:24 +03:00
needs :
2024-01-18 18:20:14 +03:00
- x86_64-centos-stream-9
2021-10-05 12:02:24 +03:00
- project : libvirt/libvirt-perl
2024-01-18 18:20:14 +03:00
job : x86_64-centos-stream-9
ci: refresh with latest lcitool manifest
This refresh switches the CI for contributors to be triggered by merge
requests. Pushing to a branch in a fork will no longer run CI pipelines,
in order to avoid consuming CI minutes. To regain the original behaviour
contributors can opt-in to a pipeline on push
git push <remote> -o ci.variable=RUN_PIPELINE=1
This variable can also be set globally on the repository, through the
web UI options Settings -> CI/CD -> Variables, though this is not
recommended. Upstream repo pushes to branches will run CI.
The use of containers has changed in this update, with only the upstream
repo creating containers, in order to avoid consuming contributors'
limited storage quotas. A fork with existing container images may delete
them. Containers will be rebuilt upstream when pushing commits with CI
changes to the default branch. Any other scenario with CI changes will
simply install build pre-requisite packages in a throaway environment,
using the ci/buildenv/ scripts. These scripts may also be used on a
contributor's local machines.
With pipelines triggered by merge requests, it is also now possible to
workaround the inability of contributors to run pipelines if they have
run out of CI quota. A project member can trigger a pipeline from the
merge request, which will run in context of upstream, however, note
this should only be done after reviewing the code for any malicious
CI changes.
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-09-30 11:50:04 +03:00
ref : master
artifacts : true
2022-10-10 11:51:01 +03:00
- project : libvirt/libvirt-python
2024-01-18 18:20:14 +03:00
job : x86_64-centos-stream-9
2022-10-10 11:51:01 +03:00
ref : master
artifacts : true
ci: refresh with latest lcitool manifest
This refresh switches the CI for contributors to be triggered by merge
requests. Pushing to a branch in a fork will no longer run CI pipelines,
in order to avoid consuming CI minutes. To regain the original behaviour
contributors can opt-in to a pipeline on push
git push <remote> -o ci.variable=RUN_PIPELINE=1
This variable can also be set globally on the repository, through the
web UI options Settings -> CI/CD -> Variables, though this is not
recommended. Upstream repo pushes to branches will run CI.
The use of containers has changed in this update, with only the upstream
repo creating containers, in order to avoid consuming contributors'
limited storage quotas. A fork with existing container images may delete
them. Containers will be rebuilt upstream when pushing commits with CI
changes to the default branch. Any other scenario with CI changes will
simply install build pre-requisite packages in a throaway environment,
using the ci/buildenv/ scripts. These scripts may also be used on a
contributor's local machines.
With pipelines triggered by merge requests, it is also now possible to
workaround the inability of contributors to run pipelines if they have
run out of CI quota. A project member can trigger a pipeline from the
merge request, which will run in context of upstream, however, note
this should only be done after reviewing the code for any malicious
CI changes.
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-09-30 11:50:04 +03:00
2024-01-08 13:30:05 +03:00
# NOTE The integration tests use artifacts produced by the libvirt-perl
# and libvirt-python CI jobs, so the new target needs to be introduced
# there before it can be used here. The VM template for the target
# also needs to be created on the runner host.
2024-01-18 18:20:14 +03:00
fedora-39-tests :
extends : .integration_tests
2023-05-02 18:08:21 +03:00
variables :
# needed by libvirt-gitlab-executor
2024-01-08 13:34:37 +03:00
DISTRO : fedora-39
2023-05-02 18:08:21 +03:00
# can be overridden in forks to set a different runner tag
LIBVIRT_CI_INTEGRATION_RUNNER_TAG : redhat-vm-host
tags :
- $LIBVIRT_CI_INTEGRATION_RUNNER_TAG
needs :
2024-01-18 18:20:14 +03:00
- x86_64-fedora-39
2023-05-02 18:08:21 +03:00
- project : libvirt/libvirt-perl
2024-01-18 18:20:14 +03:00
job : x86_64-fedora-39
2023-05-02 18:08:21 +03:00
ref : master
artifacts : true
- project : libvirt/libvirt-python
2024-01-18 18:20:14 +03:00
job : x86_64-fedora-39
2023-05-02 18:08:21 +03:00
ref : master
artifacts : true
2024-01-08 13:30:05 +03:00
# NOTE The integration tests use artifacts produced by the libvirt-perl
# and libvirt-python CI jobs, so the new target needs to be introduced
# there before it can be used here. The VM template for the target
# also needs to be created on the runner host.
2024-01-08 13:34:37 +03:00
.fedora-39-upstream-qemu-tests :
2024-01-18 18:20:14 +03:00
extends : .integration_tests
2022-05-26 16:43:36 +03:00
variables :
# needed by libvirt-gitlab-executor
2023-12-14 10:44:10 +03:00
DISTRO : fedora-39
2022-05-26 16:43:36 +03:00
# can be overridden in forks to set a different runner tag
LIBVIRT_CI_INTEGRATION_RUNNER_TAG : redhat-vm-host
tags :
- $LIBVIRT_CI_INTEGRATION_RUNNER_TAG
ci: refresh with latest lcitool manifest
This refresh switches the CI for contributors to be triggered by merge
requests. Pushing to a branch in a fork will no longer run CI pipelines,
in order to avoid consuming CI minutes. To regain the original behaviour
contributors can opt-in to a pipeline on push
git push <remote> -o ci.variable=RUN_PIPELINE=1
This variable can also be set globally on the repository, through the
web UI options Settings -> CI/CD -> Variables, though this is not
recommended. Upstream repo pushes to branches will run CI.
The use of containers has changed in this update, with only the upstream
repo creating containers, in order to avoid consuming contributors'
limited storage quotas. A fork with existing container images may delete
them. Containers will be rebuilt upstream when pushing commits with CI
changes to the default branch. Any other scenario with CI changes will
simply install build pre-requisite packages in a throaway environment,
using the ci/buildenv/ scripts. These scripts may also be used on a
contributor's local machines.
With pipelines triggered by merge requests, it is also now possible to
workaround the inability of contributors to run pipelines if they have
run out of CI quota. A project member can trigger a pipeline from the
merge request, which will run in context of upstream, however, note
this should only be done after reviewing the code for any malicious
CI changes.
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-09-30 11:50:04 +03:00
needs :
2024-01-18 18:20:14 +03:00
- x86_64-fedora-39
ci: refresh with latest lcitool manifest
This refresh switches the CI for contributors to be triggered by merge
requests. Pushing to a branch in a fork will no longer run CI pipelines,
in order to avoid consuming CI minutes. To regain the original behaviour
contributors can opt-in to a pipeline on push
git push <remote> -o ci.variable=RUN_PIPELINE=1
This variable can also be set globally on the repository, through the
web UI options Settings -> CI/CD -> Variables, though this is not
recommended. Upstream repo pushes to branches will run CI.
The use of containers has changed in this update, with only the upstream
repo creating containers, in order to avoid consuming contributors'
limited storage quotas. A fork with existing container images may delete
them. Containers will be rebuilt upstream when pushing commits with CI
changes to the default branch. Any other scenario with CI changes will
simply install build pre-requisite packages in a throaway environment,
using the ci/buildenv/ scripts. These scripts may also be used on a
contributor's local machines.
With pipelines triggered by merge requests, it is also now possible to
workaround the inability of contributors to run pipelines if they have
run out of CI quota. A project member can trigger a pipeline from the
merge request, which will run in context of upstream, however, note
this should only be done after reviewing the code for any malicious
CI changes.
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-09-30 11:50:04 +03:00
- project : libvirt/libvirt-perl
2024-01-18 18:20:14 +03:00
job : x86_64-fedora-39
ci: refresh with latest lcitool manifest
This refresh switches the CI for contributors to be triggered by merge
requests. Pushing to a branch in a fork will no longer run CI pipelines,
in order to avoid consuming CI minutes. To regain the original behaviour
contributors can opt-in to a pipeline on push
git push <remote> -o ci.variable=RUN_PIPELINE=1
This variable can also be set globally on the repository, through the
web UI options Settings -> CI/CD -> Variables, though this is not
recommended. Upstream repo pushes to branches will run CI.
The use of containers has changed in this update, with only the upstream
repo creating containers, in order to avoid consuming contributors'
limited storage quotas. A fork with existing container images may delete
them. Containers will be rebuilt upstream when pushing commits with CI
changes to the default branch. Any other scenario with CI changes will
simply install build pre-requisite packages in a throaway environment,
using the ci/buildenv/ scripts. These scripts may also be used on a
contributor's local machines.
With pipelines triggered by merge requests, it is also now possible to
workaround the inability of contributors to run pipelines if they have
run out of CI quota. A project member can trigger a pipeline from the
merge request, which will run in context of upstream, however, note
this should only be done after reviewing the code for any malicious
CI changes.
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-09-30 11:50:04 +03:00
ref : master
artifacts : true
2022-10-10 11:51:01 +03:00
- project : libvirt/libvirt-python
2024-01-18 18:20:14 +03:00
job : x86_64-fedora-39
2022-10-10 11:51:01 +03:00
ref : master
artifacts : true
