forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/.gitlab-ci.yml

128 lines
2.8 KiB
YAML
Raw Normal View History

Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
---
# global settings
CI: only use Alpine edge image for the shellcheck task (!733)
2019-11-10 11:05:10 +00:00
image: alpine:latest
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
after_script:
- .gitlab-ci/move_logs.sh $CI_PROJECT_DIR
stages:
- first
- second
CI: check if maintainers can write to MR branch (!248) Check if users activated the 'Allow commits from members who can merge to the target branch' option in their MRs. Add the "only" parameter to each job in .gitlab.yml, so the pipeline can properly run in a "merge request specific context" and give us the environment variable that contains the MR ID.
2019-02-09 21:18:00 +00:00
# defaults for "only"
# We need to run the CI jobs in a "merge request specific context", if CI is
# running in a merge request. Otherwise the environment variable that holds the
# merge request ID is not available. This means, we must set the "only"
# variable accordingly - and if we only do it for one job, all other jobs will
# not get executed. So have the defaults here, and use them in all jobs that
# should run on both the master branch, and in merge requests.
# https://docs.gitlab.com/ee/ci/merge_request_pipelines/index.html#excluding-certain-jobs
.only-default: &only-default
only:
- master
- merge_requests
- tags
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
# device documentation
wiki:
stage: first
CI: check if maintainers can write to MR branch (!248) Check if users activated the 'Allow commits from members who can merge to the target branch' option in their MRs. Add the "only" parameter to each job in .gitlab.yml, so the pipeline can properly run in a "merge request specific context" and give us the environment variable that contains the MR ID.
2019-02-09 21:18:00 +00:00
<<: *only-default
CI: various improvements (!694) * Only run the wiki test, if anything matching device/device-* was modified. * Split testcase linting (flake8) from shellcheck and only run flake8 if .gitlab-ci/* was modified. * Rename .gitlab-ci/static_code_analysis.sh to .gitlab-ci/shellcheck.sh and make it scan all pre/post install/upgrade/deinstall scripts. [ci:skip-vercheck]: other commits in this merge request have several intended version downgrades, such as 3 -> 1.0.0
2019-10-31 11:19:39 +00:00
only:
CI: fix wiki test (!737) Run it even if the last commit in the MR does not touch device/device-*.
2019-11-11 23:27:49 +00:00
refs:
- merge_requests
CI: various improvements (!694) * Only run the wiki test, if anything matching device/device-* was modified. * Split testcase linting (flake8) from shellcheck and only run flake8 if .gitlab-ci/* was modified. * Rename .gitlab-ci/static_code_analysis.sh to .gitlab-ci/shellcheck.sh and make it scan all pre/post install/upgrade/deinstall scripts. [ci:skip-vercheck]: other commits in this merge request have several intended version downgrades, such as 3 -> 1.0.0
2019-10-31 11:19:39 +00:00
changes:
CI: update for device/* -> device/testing/* move (!1067)
2020-03-14 08:30:58 +00:00
- device/*/device-*/*
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
before_script:
- apk -q add python3
script:
- .gitlab-ci/check_devices_in_wiki.py --booting
CI: various improvements (!694) * Only run the wiki test, if anything matching device/device-* was modified. * Split testcase linting (flake8) from shellcheck and only run flake8 if .gitlab-ci/* was modified. * Rename .gitlab-ci/static_code_analysis.sh to .gitlab-ci/shellcheck.sh and make it scan all pre/post install/upgrade/deinstall scripts. [ci:skip-vercheck]: other commits in this merge request have several intended version downgrades, such as 3 -> 1.0.0
2019-10-31 11:19:39 +00:00
# testcases linting
testcases-linting:
stage: first
<<: *only-default
only:
CI: fix wiki test (!737) Run it even if the last commit in the MR does not touch device/device-*.
2019-11-11 23:27:49 +00:00
refs:
- merge_requests
CI: various improvements (!694) * Only run the wiki test, if anything matching device/device-* was modified. * Split testcase linting (flake8) from shellcheck and only run flake8 if .gitlab-ci/* was modified. * Rename .gitlab-ci/static_code_analysis.sh to .gitlab-ci/shellcheck.sh and make it scan all pre/post install/upgrade/deinstall scripts. [ci:skip-vercheck]: other commits in this merge request have several intended version downgrades, such as 3 -> 1.0.0
2019-10-31 11:19:39 +00:00
changes:
- .gitlab-ci/*
CI: run flake8 for changes in testcases too (!1069)
2020-03-21 21:34:52 +00:00
- .gitlab-ci/*/*
CI: various improvements (!694) * Only run the wiki test, if anything matching device/device-* was modified. * Split testcase linting (flake8) from shellcheck and only run flake8 if .gitlab-ci/* was modified. * Rename .gitlab-ci/static_code_analysis.sh to .gitlab-ci/shellcheck.sh and make it scan all pre/post install/upgrade/deinstall scripts. [ci:skip-vercheck]: other commits in this merge request have several intended version downgrades, such as 3 -> 1.0.0
2019-10-31 11:19:39 +00:00
before_script:
CI: fix incorrect py-flake8 package name (!736)
2019-11-11 22:24:39 +00:00
- apk -q add py-flake8
CI: various improvements (!694) * Only run the wiki test, if anything matching device/device-* was modified. * Split testcase linting (flake8) from shellcheck and only run flake8 if .gitlab-ci/* was modified. * Rename .gitlab-ci/static_code_analysis.sh to .gitlab-ci/shellcheck.sh and make it scan all pre/post install/upgrade/deinstall scripts. [ci:skip-vercheck]: other commits in this merge request have several intended version downgrades, such as 3 -> 1.0.0
2019-10-31 11:19:39 +00:00
script:
- flake8 --ignore E501,F401,E722,W504,W605
# shellcheck
shellcheck:
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
stage: first
CI: check if maintainers can write to MR branch (!248) Check if users activated the 'Allow commits from members who can merge to the target branch' option in their MRs. Add the "only" parameter to each job in .gitlab.yml, so the pipeline can properly run in a "merge request specific context" and give us the environment variable that contains the MR ID.
2019-02-09 21:18:00 +00:00
<<: *only-default
CI: only use Alpine edge image for the shellcheck task (!733)
2019-11-10 11:05:10 +00:00
image: alpine:edge
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
before_script:
CI: only use Alpine edge image for the shellcheck task (!733)
2019-11-10 11:05:10 +00:00
- apk -q upgrade
CI: various improvements (!694) * Only run the wiki test, if anything matching device/device-* was modified. * Split testcase linting (flake8) from shellcheck and only run flake8 if .gitlab-ci/* was modified. * Rename .gitlab-ci/static_code_analysis.sh to .gitlab-ci/shellcheck.sh and make it scan all pre/post install/upgrade/deinstall scripts. [ci:skip-vercheck]: other commits in this merge request have several intended version downgrades, such as 3 -> 1.0.0
2019-10-31 11:19:39 +00:00
- apk -q add shellcheck
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
script:
CI: various improvements (!694) * Only run the wiki test, if anything matching device/device-* was modified. * Split testcase linting (flake8) from shellcheck and only run flake8 if .gitlab-ci/* was modified. * Rename .gitlab-ci/static_code_analysis.sh to .gitlab-ci/shellcheck.sh and make it scan all pre/post install/upgrade/deinstall scripts. [ci:skip-vercheck]: other commits in this merge request have several intended version downgrades, such as 3 -> 1.0.0
2019-10-31 11:19:39 +00:00
- .gitlab-ci/shellcheck.sh
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
# aports checks (generic)
aports-static:
stage: first
CI: check if maintainers can write to MR branch (!248) Check if users activated the 'Allow commits from members who can merge to the target branch' option in their MRs. Add the "only" parameter to each job in .gitlab.yml, so the pipeline can properly run in a "merge request specific context" and give us the environment variable that contains the MR ID.
2019-02-09 21:18:00 +00:00
<<: *only-default
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
before_script:
- .gitlab-ci/install_pmbootstrap.sh pytest
script:
CI: add check_changed_aports_versions.py (!382) Make sure that changed aports always have a higher version than what is currently in master. This check can be skipped with ci:skip-vercheck (in square brackets). Related: #187
2019-05-19 20:20:39 +00:00
- apk -q add git
CI: remove upstream compatibility checks (!1085) Do not run upstream compatibility checks whenever pushing to master. This is confusing, because if the upstream compatibility check fails, then it appears that the last patch was broken in some way although it isn't related. I've moved the upstream compatibility checks to a separate repository already, and added a badge to the pmaports gitlab project that indicates whether they are currently succeding or not. The checks run hourly now. Related: https://gitlab.com/postmarketOS/monitoring Fixes: #457
2020-03-21 15:36:38 +00:00
- su pmos -c ".gitlab-ci/run_testcases.sh"
CI: add check_changed_aports_versions.py (!382) Make sure that changed aports always have a higher version than what is currently in master. This check can be skipped with ci:skip-vercheck (in square brackets). Related: #187
2019-05-19 20:20:39 +00:00
- su pmos -c ".gitlab-ci/check_changed_aports_versions.py"
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
artifacts:
when: on_failure
paths:
- log.txt
- log_testsuite_pmaports.txt
- pmbootstrap.cfg
expire_in: 1 week
CI: enable APKBUILD linting (!860)
2020-01-05 17:05:51 +00:00
# APKBUILD linting
aport-lint:
stage: first
CI: skip linting check for temp/ folder (!864) Since we copy these aports directly from Alpine and try to keep them in sync, we don't want to differ from upstream because our CI doesn't pass on linting. If the APKBUILD should be improved, it should be done upstream which is then synced back to us.
2020-01-06 17:25:27 +00:00
before_script:
- apk -q add git atools python3
CI: enable APKBUILD linting (!860)
2020-01-05 17:05:51 +00:00
script:
CI: skip linting check for temp/ folder (!864) Since we copy these aports directly from Alpine and try to keep them in sync, we don't want to differ from upstream because our CI doesn't pass on linting. If the APKBUILD should be improved, it should be done upstream which is then synced back to us.
2020-01-06 17:25:27 +00:00
- .gitlab-ci/apkbuild-linting.py
CI: enable APKBUILD linting (!860)
2020-01-05 17:05:51 +00:00
only:
- merge_requests
CI: allow failure for aport linting check
2020-01-13 14:01:01 +00:00
allow_failure: true
CI: enable APKBUILD linting (!860)
2020-01-05 17:05:51 +00:00
CI: split out kconfig check and only run when kernel package has changed (!738)
2019-11-12 23:28:57 +00:00
# kernel kconfig check
kernel-kconfig:
stage: first
only:
refs:
- master
- merge_requests
changes:
CI: update for device/* -> device/testing/* move (!1067)
2020-03-14 08:30:58 +00:00
- device/*/linux-*/config-*
CI: split out kconfig check and only run when kernel package has changed (!738)
2019-11-12 23:28:57 +00:00
- main/linux-*/config-*
before_script:
- .gitlab-ci/install_pmbootstrap.sh pytest
script:
- su pmos -c "pmbootstrap kconfig check"
CI: check if maintainers can write to MR branch (!248) Check if users activated the 'Allow commits from members who can merge to the target branch' option in their MRs. Add the "only" parameter to each job in .gitlab.yml, so the pipeline can properly run in a "merge request specific context" and give us the environment variable that contains the MR ID.
2019-02-09 21:18:00 +00:00
# MR settings
# (Checks for "Allow commits from members who can merge to the target branch")
mr-settings:
stage: first
only:
- merge_requests
before_script:
- apk -q add python3
script:
- .gitlab-ci/check_mr_settings.py
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
# build changed aports
aports-build:
stage: second
CI: check if maintainers can write to MR branch (!248) Check if users activated the 'Allow commits from members who can merge to the target branch' option in their MRs. Add the "only" parameter to each job in .gitlab.yml, so the pipeline can properly run in a "merge request specific context" and give us the environment variable that contains the MR ID.
2019-02-09 21:18:00 +00:00
<<: *only-default
Add test cases and .gitignore Copy all test cases from the pmbootstrap repository, that are actually testing the aports. They were all adjusted to work nicely in this repository, together with a brand new set of gitlab-ci configs. This also includes the changes from this merge request, that had a better detection of changed packages: <https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>
2018-08-30 22:39:24 +00:00
before_script:
- .gitlab-ci/install_pmbootstrap.sh git
script:
CI package build: don't buffer output and silent "git fetch"
2018-09-26 05:57:29 +00:00
- PYTHONUNBUFFERED=1 su pmos -c ".gitlab-ci/build_changed_aports.py"
Reference in a new issue Copy permalink