Skip to main content

Usage

  • Create a new project
  • Create a Containerfile.
FROM alpine
  • Create GitLab pipeline file .gitlab-ci.yml:
include:
- component: $CI_SERVER_FQDN/xrow-public/ci-tools/common@stable
- component: $CI_SERVER_FQDN/xrow-public/ci-tools/container@stable
  inputs:
    name: myapplication
    path: .

Publish to a non default registry​

  • Set variables CI_REGISTRY, CI_REGISTRY_USER and CI_REGISTRY_PASSWORD at level of the project or group.
  • Create GitLab pipeline file .gitlab-ci.yml:
include:
- component: $CI_SERVER_FQDN/xrow-public/ci-tools/common@stable
- component: $CI_SERVER_FQDN/xrow-public/ci-tools/container@stable
  inputs:
    name: myapplication
    path: .

Inputs​

NameDescriptionDefaultType
------------
argsArguments to pass to the builder.string
containerfile-pathAlternate path to the Containerfile, if either Dockerfile or Containerfile in the conect directory.string
dependenciesThe dependencies that this job depends on.[]array
nameName for the pipeline jobs and the container.$CI_PROJECT_NAMEstring
needsThe jobs that this job depends on.[]array
pathPath to the directory containing Container sources / context..string
registryRegistry to store container image releases in$CI_REGISTRYstring
repository-pathRepository to store container image releases in$CI_REGISTRY_PROJECT_PATHstring
rulesThe jobs that this job depends on.[{"if":"$CI_PIPELINE_SOURCE == \"schedule\"","when":"never"},{"if":"$CI_PIPELINE_SOURCE == \"merge_request_event\"","when":"on_success"},{"when":"on_success"}]array
runtimeRepository to store container image releases inpodmanstring
scannersScanners to use. none, vuln, license, secret, misconfig["vuln","secret","license","misconfig"]array
scanning-allow-failureShould the pipeline fail if scanning the built container image fails?falseboolean
scanning-enabledShould the built container image be scanned?trueboolean
scanning-severityWhat level of severity should cause scanning of the built container to fail?CRITICALstring
scanning-timeoutHow long should the scanning process be allowed to run before timing out? Use format e.g. 5m0sstring
secretsSecrets to pass to the builder.string
stageThe pipeline stage that the jobs belongs to.buildstring
tagsThe runners that this job depends on.[]array
versionInternal version of the nested component to use.mainstring