Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with continuous-deployment
Search options answers only
not deleted
user 25974
Use this tag for questions about automatically deploying software to a production environment as part of a CI pipeline. For questions about manual deployment to production use the [continuous-delivery] tag.
14
votes
Accepted
Can I run multiple pipelines in a single GitLab repo using GitLab CI/CD?
Yes, you can use the rules syntax. You can use this in combination with regex for commit message, ci_pipeline_source or any other available CI variables.
job1:
script:
- do something on schedu …
- 381
2
votes
Accepted
Should I struggle for minimalistic context in GitLab CI jobs?
Your use case is very simple, so relying on GIT_STRATEGY=fetch is probably sufficient and as you said the default behavior.
You should be cautious using artifacts unnecessarily as they are uploaded to …
- 381