shaba/virt-viewer
1
0
Fork 0
mirror of https://gitlab.com/virt-viewer/virt-viewer.git synced 2025-01-06 13:17:45 +03:00
Code Issues Projects Releases Wiki Activity
f666425950
virt-viewer/ci/buildenv/fedora-39.sh

49 lines
1.1 KiB
Bash
Raw Normal View History

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, 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. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-09-30 11:50:04 +03:00
# THIS FILE WAS AUTO-GENERATED
#
# $ lcitool manifest ci/manifest.yml
#
# https://gitlab.com/libvirt/libvirt-ci
function install_buildenv() {
dnf update -y
dnf install -y \
bash-completion \
ca-certificates \
ccache \
cppi \
gcc \
gettext \
git \
glib2-devel \
ci: refresh with latest lcitool manifest This updates the distros: * Add Alpine 3.18, 3.19, Edge, CentOS Stream 9, Fedora 39, 40, Ubuntu 24.04, AlmaLinux 8, 9, Debian 11, 12 * Remove CentOS Stream 8, Fedora 37, 38, Ubuntu 20.04, Debian 10, Fedora 35, 36 * Rename OpenSUSE 15.3 to 15 Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2023-11-27 19:50:08 +03:00
glibc-devel \
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, 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. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-09-30 11:50:04 +03:00
glibc-langpack-en \
gtk-vnc2-devel \
gtk3-devel \
icoutils \
libgovirt-devel \
libtool \
libvirt-devel \
libvirt-gobject-devel \
libxml2 \
libxml2-devel \
make \
meson \
ninja-build \
pkgconfig \
rest-devel \
rpm-build \
spice-gtk3-devel \
vte291-devel
rpm -qa | sort > /packages.txt
mkdir -p /usr/libexec/ccache-wrappers
ln -s /usr/bin/ccache /usr/libexec/ccache-wrappers/cc
ln -s /usr/bin/ccache /usr/libexec/ccache-wrappers/gcc
}
ci: refresh with latest 'lcitool manifest' * Switch to using libvirt+minimal instead of libvirt project, for shorter build times * Actually do a git build job in CentOS Stream & AlmaLinux * Drop AlmaLinux 8 * Update to latest Alpine versions Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2024-06-18 13:12:02 +03:00
function export_buildenv() {
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, 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. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-09-30 11:50:04 +03:00
export CCACHE_WRAPPERSDIR="/usr/libexec/ccache-wrappers"
export LANG="en_US.UTF-8"
export MAKE="/usr/bin/make"
export NINJA="/usr/bin/ninja"
ci: refresh with latest 'lcitool manifest' * Switch to using libvirt+minimal instead of libvirt project, for shorter build times * Actually do a git build job in CentOS Stream & AlmaLinux * Drop AlmaLinux 8 * Update to latest Alpine versions Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2024-06-18 13:12:02 +03:00
}
Reference in New Issue Copy Permalink