gstreamer/.gitlab-ci.yml

include: "gitlab/ci_template.yml"

test manifest:
  variables:
    GIT_STRATEGY: fetch
  rules:
    - when: 'always'
  image: "$TEST_MANIFEST_IMAGE"
  stage: "preparation"
  script:
    - pytest-3 --junitxml=junit.xml --cov=build_manifest gitlab/build_manifest.py
  coverage: '/TOTAL.*\s+(\d+%)$/'
  artifacts:
    reports:
      junit:
        - "junit.xml"

test manifest amd64 docker:
  stage: "build docker"
  variables:
    REPO_SUFFIX: "$TEST_MANIFEST_AMD64_SUFFIX"
    TAG: "$TEST_MANIFEST_TAG-$GST_UPSTREAM_BRANCH"

    CONTEXT_DIR: "docker/test_manifest/"
    DOCKERFILE: "docker/test_manifest/Dockerfile"
  extends: .base
docker: allow to specify the branch to pull for various repos Declare an docker build-arg [1] and use it whenever cloning one of our repositories. If the buildarg is not specified, the variable defaults back to 'master' and thus the current behavior doesn't change. From the .gitlab-ci.yml file, when building pass the GST_UPSTREAM_BRANCH that's defined from the ci_template as the buildarg so we will be building the corresponding branches for the docker images. Close #33 [1] https://docs.docker.com/engine/reference/builder/#arg 2020-02-10 13:09:49 +00:00			`include: "gitlab/ci_template.yml"`

CI: run the build_manifest.py tests 2018-10-25 10:33:14 +00:00			`test manifest:`
Also run the main CI template in .gitlab-ci.yml Rename some job otherwise some names where too similare. 2018-11-09 18:57:45 +00:00			`variables:`
			`GIT_STRATEGY: fetch`
Only run CI automatically on merge_request 2020-03-04 22:30:06 +00:00			`rules:`
			`- when: 'always'`
ci_template: merge docker builds into the normal pipeline Port the build docker jobs to the template and integrate it into the pipeline. Then change the image uris to the new system, and the user forked registries. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-ci/-/merge_requests/308> 2020-06-19 12:27:36 +00:00			`image: "$TEST_MANIFEST_IMAGE"`
gitlab/ci_template.yml: rework the CI stages Idea is that in order to not consume many resources for broken builds, we will have a basic stage where just one simple set of build and test jobs is run. If that passes we will continue with the rest of the Pipeline suite. 2018-11-23 16:45:31 +00:00			`stage: "preparation"`
CI: run the build_manifest.py tests 2018-10-25 10:33:14 +00:00			`script:`
			`- pytest-3 --junitxml=junit.xml --cov=build_manifest gitlab/build_manifest.py`
			`coverage: '/TOTAL.*\s+(\d+%)$/'`
			`artifacts:`
			`reports:`
			`junit:`
Build the docker images and push them to the gitalb registry 2018-11-05 18:52:37 +00:00			`- "junit.xml"`

docker: add an image to run the tests of the manifest So in the futuere we can avoid installing pytest each time 2018-11-30 18:43:39 +00:00			`test manifest amd64 docker:`
			`stage: "build docker"`
			`variables:`
ci_template: merge docker builds into the normal pipeline Port the build docker jobs to the template and integrate it into the pipeline. Then change the image uris to the new system, and the user forked registries. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-ci/-/merge_requests/308> 2020-06-19 12:27:36 +00:00			`REPO_SUFFIX: "$TEST_MANIFEST_AMD64_SUFFIX"`
citemplate: use the fd.o pre existing buildah image to build containers Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-ci/-/merge_requests/308> 2020-06-25 09:49:05 +00:00			`TAG: "$TEST_MANIFEST_TAG-$GST_UPSTREAM_BRANCH"`
ci_template: merge docker builds into the normal pipeline Port the build docker jobs to the template and integrate it into the pipeline. Then change the image uris to the new system, and the user forked registries. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-ci/-/merge_requests/308> 2020-06-19 12:27:36 +00:00
docker: add an image to run the tests of the manifest So in the futuere we can avoid installing pytest each time 2018-11-30 18:43:39 +00:00			`CONTEXT_DIR: "docker/test_manifest/"`
			`DOCKERFILE: "docker/test_manifest/Dockerfile"`
			`extends: .base`