4 дек. 2020 г. · Absolutely - create a repo for your shared .gitlab-ci.yml then within each project, have a .gitlab-ci.yml with an 'include' statement that ...

22 февр. 2024 г. · My compagnie decided to split our code base into several repos and I wonder how to deal with CI/CD. Basically I have: One "core" repo.

9 дек. 2023 г. · You should be testing the dependencies in their own CI, and then consuming the artifacts of that build in the dependant component, whether it's ...

24 июн. 2024 г. · You can create a pipeline in your central repo on tag push to trigger the pipelines in your downstream repos using Multi-project pipelines.

27 дек. 2023 г. · Another way would be to create api tokens to clone the other repository in the pipeline. Or you build a Docker image from one of your projects ...

5 авг. 2024 г. · I want to achieve two things within a repository consisting of multiple branches: Let's assume I have three branches, called dev, stage and prod.

26 мар. 2020 г. · The solution that comes to mind is to create my own debian image, have a key-pair in it, and proactively add that public key to the deploy keys of projectA.

30 сент. 2020 г. · GitLab has a lot of flexibility here. Your base is .gitlab-ci.yml and for management can be broken into multiple files using the include: key ...

17 мая 2022 г. · Lets say there are 3 repositories FRONTEND, BACKEND, DEPLOYMENT. First two have only code and dockerfiles. Third one has all files needed for deployment.

20 нояб. 2020 г. · We have 8-10 git repos with different components (backend, ECS cluster, other infra, BI tools , integration components and etc)