New answers tagged

1

The error you are getting is from your Kubernetes cluster being unable to pull container image from GitLab. Providing a temporary credential to pull the containers as deploy time is not a great solution. For example, say your Kubernetes cluster needs to scale up by adding another node, the node will come up and try and pull the container, but the secret will ...


1

While I generally do not recommend GitFlow these days, fully automated way to do what you ask is possible to achieve with an external system. Below I will describe how to do it with Reliza Hub (which is the one I'm developing - but you may find other options). Here is the idea - You create your project in Reliza Hub and choose versioning schema, i.e. semver....


1

My solution is very similar to @taleodor's, but it 1) uses the predefined CI_REGISTRY_USER variable, and 2) just resets the existing origin's url: before_script: - git remote set-url origin https://${CI_REGISTRY_USER}:${API_TOKEN}@${CI_REPOSITORY_URL#*@} I'd also recommend you use an access token for the project, not the user. Create the token by ...


Top 50 recent answers are included