.gitlab-ci.yml

# .gitlab-ci.yml
#
# cumulus
#
# pipelines can be triggered manually in the web


stages:
  - test
  - publish

variables:                         &default-vars
  GIT_STRATEGY:                    fetch
  GIT_DEPTH:                       100
  CARGO_INCREMENTAL:               0
  CARGO_TARGET_DIR:                "/ci-cache/${CI_PROJECT_NAME}/targets/${CI_COMMIT_REF_NAME}/${CI_JOB_NAME}"
  CI_IMAGE:                        "paritytech/ci-linux:production"
  DOCKER_OS:                       "debian:stretch"
  ARCH:                            "x86_64"

.rust-info-script:                 &rust-info-script
  - rustup show
  - cargo --version
  - rustup +nightly show
  - cargo +nightly --version
  - bash --version
  - sccache -s

.publish-refs:                     &publish-refs
  rules:
    - if: $CI_PIPELINE_SOURCE == "web"
    - if: $CI_PIPELINE_SOURCE == "schedule"
    - if: $CI_COMMIT_REF_NAME =~ /^v[0-9]+\.[0-9]+.*$/              # i.e. v1.0, v2.1rc1

.docker-env:                       &docker-env
  image:                           "${CI_IMAGE}"
  before_script:
    - *rust-info-script
    - ./scripts/ci/pre_cache.sh
    - sccache -s
  retry:
    max: 2
    when:
      - runner_system_failure
      - unknown_failure
      - api_failure
  interruptible:                   true
  tags:
    - linux-docker

.kubernetes-env:                   &kubernetes-env
  retry:
    max: 2
    when:
      - runner_system_failure
      - unknown_failure
      - api_failure
  interruptible:                   true
  tags:
    - kubernetes-parity-build

.collect-artifacts:                &collect-artifacts
  artifacts:
    name:                          "${CI_JOB_NAME}_${CI_COMMIT_REF_NAME}"
    when:                          on_success
    expire_in:                     28 days
    paths:
      - ./artifacts/

#### stage:                        test

test-linux-stable:
  stage:                           test
  <<:                              *docker-env
  rules:
    - if: $CI_COMMIT_REF_NAME == "master"
    - if: $CI_COMMIT_REF_NAME == "tags"
    - if: $CI_COMMIT_REF_NAME =~ /^[0-9]+$/                         # PRs
    # It doesn't make sense to build on every commit, so we build on tags
    - if: $CI_COMMIT_REF_NAME =~ /^v[0-9]+\.[0-9]+.*$/              # i.e. v1.0, v2.1rc1
      variables:
        ARE_WE_RELEASING_YET:      maybe!
    # web and schedule triggers can be provided with the non-empty variable ARE_WE_RELEASING_YET
    # to run building and publishing the binary.
    - if: $CI_PIPELINE_SOURCE == "web"
    - if: $CI_PIPELINE_SOURCE == "schedule"
  <<:                              *collect-artifacts
  variables:
    <<:                            *default-vars
    # Enable debug assertions since we are running optimized builds for testing
    # but still want to have debug assertions.
    RUSTFLAGS: "-Cdebug-assertions=y -Dwarnings"
  script:
    - time cargo test --all --release --locked -- --include-ignored
    # It's almost free to produce a binary here, please refrain from using it in production since
    # it goes with the debug assertions.
    - if [ "${ARE_WE_RELEASING_YET}" ]; then
        echo "___Building a binary___";
        time cargo build --release --locked --bin polkadot-collator;
        echo "___Packing the artifacts___";
        mkdir -p ./artifacts;
        mv ${CARGO_TARGET_DIR}/release/polkadot-collator ./artifacts/.;
        echo "___The VERSION is either a tag name or the curent branch if triggered not by a tag___";
        echo ${CI_COMMIT_REF_NAME} | tee ./artifacts/VERSION;
      else
        exit 0;
      fi
    - sccache -s

check-runtime-benchmarks:
  stage:                           test
  <<:                              *docker-env
  script:
    # Check that the node will compile with `runtime-benchmarks` feature flag.
    - time cargo check --features runtime-benchmarks
    - sccache -s

cargo-check-try-runtime:
  stage:                           test
  <<:                              *docker-env
  script:
    # Check that the node will compile with `try-runtime` feature flag.
    - time cargo check --features try-runtime
    - sccache -s

#### stage:                        publish

publish-s3:
  stage:                           publish
  <<:                              *kubernetes-env
  image:                           paritytech/awscli:latest
  <<:                              *publish-refs
  variables:
    GIT_STRATEGY:                  none
    BUCKET:                        "releases.parity.io"
    PREFIX:                        "cumulus/${ARCH}-${DOCKER_OS}"
  before_script:
    # Job will fail if no artifacts were provided by test-linux-stable job. It's only possible for
    # this test to fail if the pipeline was triggered by web or schedule trigger without supplying
    # a nono-empty ARE_WE_RELEASING_YET variable.
    - test -e ./artifacts/polkadot-collator ||
        ( echo "___No artifacts were provided by the previous job, please check the build there___"; exit 1 )
  script:
    - echo "___Publishing a binary with debug assertions!___"
    - echo "___VERSION = $(cat ./artifacts/VERSION) ___"
    - aws s3 sync ./artifacts/ s3://${BUCKET}/${PREFIX}/$(cat ./artifacts/VERSION)/
    - echo "___Updating objects in latest path___"
    - aws s3 sync s3://${BUCKET}/${PREFIX}/$(cat ./artifacts/VERSION)/ s3://${BUCKET}/${PREFIX}/latest/
  after_script:
    - aws s3 ls s3://${BUCKET}/${PREFIX}/latest/
        --recursive --human-readable --summarize