RepoMirrors
/
selinux
mirror of https://github.com/SELinuxProject/selinux
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
selinux/.circleci/config.yml

42 lines
1.6 KiB
YAML
Raw Normal View History

CircleCI: run scan-build and publish its results automatically CircleCI is a continuous integration system like Travis CI, which provides different features. Contrary to Travis CI, it is quite harder to build the project with several build configurations (so it is not a replacement), but it provides short-term storage for files produced by a build job in what is called "artifacts". Use this feature in order to store the results of clang's static analyzer (scan-build) after every pushed commit. This way makes it possible to quickly compare the result of the analyzer after applying some patches that were sent for review to the mailing list, as it no longer requires running the analyzer several times on the development machine. An output example is available at https://352-118970575-gh.circle-artifacts.com/0/output-scan-build/2019-09-21-164945-6152-1/index.html These web pages were created by the job described at https://circleci.com/gh/fishilico/selinux/352 Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
2019-09-21 21:30:37 +00:00
# Configuration file for https://circleci.com/
version: 2
jobs:
build:
docker:
# Use a Python image from https://hub.docker.com/r/circleci/python/tags/
- image: circleci/python:3.6
steps:
- checkout
# Install dependencies
- run: sudo apt-get update -qq
Replace PCRE with PCRE2 build dependencies Now that libselinux defaults to PCRE2 and mcstrans has been ported, update all documentation and scripts. Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
2021-11-23 18:32:49 +00:00
- run: sudo apt-get install -qq bison clang clang-tools flex gawk gettext libaudit-dev libcap-dev libcap-ng-dev libcunit1-dev libdbus-glib-1-dev libpcre2-dev python3-dev python-dev ruby-dev swig xmlto
CircleCI: run scan-build and publish its results automatically CircleCI is a continuous integration system like Travis CI, which provides different features. Contrary to Travis CI, it is quite harder to build the project with several build configurations (so it is not a replacement), but it provides short-term storage for files produced by a build job in what is called "artifacts". Use this feature in order to store the results of clang's static analyzer (scan-build) after every pushed commit. This way makes it possible to quickly compare the result of the analyzer after applying some patches that were sent for review to the mailing list, as it no longer requires running the analyzer several times on the development machine. An output example is available at https://352-118970575-gh.circle-artifacts.com/0/output-scan-build/2019-09-21-164945-6152-1/index.html These web pages were created by the job described at https://circleci.com/gh/fishilico/selinux/352 Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
2019-09-21 21:30:37 +00:00
- run:
name: Setup environment variables
command: |
echo 'export DESTDIR=$HOME/destdir' >> "$BASH_ENV"
CircleCI: do not add Debian-specific parameter when invoking setup.py Runners on https://circleci.com/ use a custom version of Python without Debian-specific patches which added option --install-layout=deb. This leads to the following error: error: option --install-layout not recognized Fix this by creating a new environment variable dedicated to detect CircleCI platform. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org> Acked-by: James Carter <jwcart2@gmail.com>
2022-06-29 07:12:54 +00:00
echo 'export IS_CIRCLE_CI=1' >> "$BASH_ENV"
CircleCI: run scan-build and publish its results automatically CircleCI is a continuous integration system like Travis CI, which provides different features. Contrary to Travis CI, it is quite harder to build the project with several build configurations (so it is not a replacement), but it provides short-term storage for files produced by a build job in what is called "artifacts". Use this feature in order to store the results of clang's static analyzer (scan-build) after every pushed commit. This way makes it possible to quickly compare the result of the analyzer after applying some patches that were sent for review to the mailing list, as it no longer requires running the analyzer several times on the development machine. An output example is available at https://352-118970575-gh.circle-artifacts.com/0/output-scan-build/2019-09-21-164945-6152-1/index.html These web pages were created by the job described at https://circleci.com/gh/fishilico/selinux/352 Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
2019-09-21 21:30:37 +00:00
# Download and install refpolicy headers for sepolgen tests
- run:
name: Download refpolicy Makefile
command: |
curl --location --retry 10 -o refpolicy.tar.bz2 https://github.com/SELinuxProject/refpolicy/releases/download/RELEASE_2_20180701/refpolicy-2.20180701.tar.bz2
tar -xvjf refpolicy.tar.bz2
sed -e "s,^PREFIX :=.*,PREFIX := $DESTDIR/usr," -i refpolicy/support/Makefile.devel
sudo make -C refpolicy install-headers
sudo mkdir -p /etc/selinux
echo 'SELINUXTYPE=refpolicy' | sudo tee /etc/selinux/config
echo 'SELINUX_DEVEL_PATH = /usr/share/selinux/refpolicy' | sudo tee /etc/selinux/sepolgen.conf
sed -e "s,\"\(/usr/bin/[cs]\),\"$DESTDIR\1," -i python/sepolgen/src/sepolgen/module.py
# Run clang's scan-build and store the result as artifacts
- run: ./scripts/run-scan-build
- store_artifacts:
path: scripts/output-scan-build
destination: output-scan-build