Page History

...

release:
    stage: release
    image: registry.ethz.ch/project-openenzian/ci-images/publish:ubuntu-22.04
    script: /publish_artifacts
    rules:
      - if: '$CI_COMMIT_TAG'
    needs:
         - job: build
           artifacts: true
    variables:
        PROJECT_ID: 48046
        PACKAGE_NAME: release
        RELEASE_NAME: 'Release $CI_COMMIT_TAG'
        RELEASE_TAG: '$CI_COMMIT_TAG'
        ARTIFACT_PATHS: |
            build/shell_stub.bit
            build/shell_stub.ltx
            build/shell_stub_pblock_dynamic_partial.bit
            build/static_shell_routed.dcp
            build/shell_stub_routed.dcp

Accessing submodules of private repos in CI

By default, the CI job can only clone public git repos as submodules.  You can either:

• use a project access token (recommend), or
• use a personal access token in the CI (not recommended), or
• if the submodule project is also on the department GitLab:
  • enable CI for the submodule project: "Settings → General → Visibility, project features, permissions → CI/CD"
  • add the parent project to the list of allowed projects to access from CI: "Settings → CI/CD → Token Access → Allow CI job tokens from the following projects to access this project"
    • or maybe turn off the access restriction from CI completely (might have security concerns)

Using the released artifacts

...