Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D DataEngineering
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Diese GitLab Instanz ist nicht für den produktiven Einsatz gedacht!
Bitte https://gitlab.ost.ch benutzen!
Diese Instanz ist nur nuch zur Datenmigration online.

Vielen Dank für euer Verständnis.

  • Lehre und Unterricht
  • Datenbank- und Informations-Systeme
  • DataEngineering
  • Issues
  • #20

Closed
Open
Created Mar 15, 2017 by Marcel Huber@m1huberOwner

Adjust .gitlab-ci.yml to use correct registry when forking

Context

CI Build

Summary

The predefined variables section contains a hardcoded repository location which is not possible to push to in forked projects.

Steps to reproduce

Fork this project, make a commit and see the preparation step failing :(

What is the current issue behavior?

Pushing to the base projects registry fails, See !22 (merged)

What is the expected correct behavior?

A push to the forked projects repository should succeed.

Relevant logs and/or screenshots

--

Possible fixes

We should probably use CI_REGISTRY_IMAGE instead of the hardcoded string.

See available CI Variables

Assignee
Assign to
Time tracking