Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/marcelotsvaz/gitlab
Different types of reusable components used across all my projects on GitLab.
https://github.com/marcelotsvaz/gitlab
gitlab
Last synced: about 1 month ago
JSON representation
Different types of reusable components used across all my projects on GitLab.
- Host: GitHub
- URL: https://github.com/marcelotsvaz/gitlab
- Owner: Marcelotsvaz
- License: unlicense
- Created: 2024-08-07T18:13:31.000Z (5 months ago)
- Default Branch: main
- Last Pushed: 2024-08-12T22:19:24.000Z (5 months ago)
- Last Synced: 2024-10-19T22:36:25.365Z (2 months ago)
- Topics: gitlab
- Language: YAML
- Homepage:
- Size: 214 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: changelog.md
Awesome Lists containing this project
README
# GitLab Utils
This repository holds several resources used by my other repositories on GitLab.
## CI/CD Components
Reusable [components](https://docs.gitlab.com/ee/ci/components/) for GitLab CI/CD pipelines.
- `sane-workflow` - Prevent duplicated pipelines.
- `stages` - Default stages used in all my projects.
How to use:
```yaml
include:
- component: gitlab.com/vaz-projects/gitlab/[email protected]
```
### Conventions
All components in this repository use the following conventions.
1. Include the `stages` component. Most other components depend on it.
``` yaml
include:
- component: gitlab.com/vaz-projects/gitlab/[email protected]
```
1. Don't use `stage` directly. Use the provided base jobs instead. They properly define the rules for each stage (and have ✨pretty✨ names).
``` yaml
job:
extends: .buildStage
```
1. When using `extends` and `rules`: Include a reference to the base job's rules. Otherwise, all other rules would be overwritten.
``` yaml
job:
extends: .baseJob
rules:
- $VAR == 'VALUE'
- !reference [ .baseJob, rules ]
```
### Deployment Styles
The `stages` component support two different deployment styles:
1. Deploy on tag pipelines. Default branch is used pro development. Good for versioned releases.
- `feature-branch/without-mr`: Build & Test
- `feature-branch/with-mr`: Build & Test -> Deploy to review app
- `default-branch`: Build & Test
- `tag`: Build & Test -> Deploy to staging -> Deploy to production
1. Deploy on default branch pipelines. Default branch is used for staging and production. Good for continuous delivery/deployment.
- `feature-branch/without-mr`: Build & Test
- `feature-branch/with-mr`: Build & Test -> Deploy to review app
- `default-branch`: Build & Test -> Deploy to staging -> Deploy to production
- `tag`: Build & Test
``` yaml
include:
- component: gitlab.com/vaz-projects/gitlab/[email protected]
inputs:
deployOn: defaultBranch
```
## GitLab Runners
TODO
## Renovate Presets
TODO
## GitLab Project Configuration as Code
TODO