| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
Add config for CI Runner that prevents it from picking untagged jobs
Closes #3456
See merge request !4039
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Update 'after_script' introduction note
Related to gitlab-org/gitlab-ci-multi-runner#1321
See merge request !4205
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix broken documentation links
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/15249
- [x] `/help/ui`- This is working for me
- [x] `/help/ci/examples/deployment/README.md` - Fixed
- [x] `/help/ci/api/projects.md` - Fixed
- [x] `/help/markdown/LICENSE` - Cannot do much to fix it, added a note.
- [x] `/help/ci/ssh/README.md` - Cannot find this link referenced anywhere.
See merge request !3903
|
| |
| |
| |
| | |
[ci skip]
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix broken link in CI quickstart docs
The newline between the `[label]` and the `(link)` caused it to be interpreted literally: http://doc.gitlab.com/ce/ci/quick_start/README.html
See merge request !3541
|
| | |
| | |
| | | |
The space between the [label] and the (link) caused it to be interpreted literally.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
blost -> blog
See merge request !4063
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Update CI example docs.
Docs for CI examples are updated as follows:
- Fix a dead link from CI example top to `dpl`
- Specify Django for a Python project, not Rails
- Use the latest Python Docker image as [Heroku supports only Python 3.5.1 (and 2.7.11)](https://devcenter.heroku.com/articles/python-support)
- Show the latest Docker Hub URL links.
See merge request !4082
|
| |/ / / |
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Documentation fix in CI SSH keys setup
In recent versions of Docker, the `/.dockerinit` file doesn't exist any more when running inside a container. That file is used in the example here to detect whether the runner is running inside Docker or not. Change it to check for the existence of `/.dockerenv`, which does exist in all current versions of Docker.
See merge request !3938
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
/.dockerenv instead [ci skip]
Signed-off-by: Jason Roehm <jasonr@3db-labs.com>
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Update using_docker_build.md, clarify the 'privileged' mode requirement
Related to #15428
Fixes gitlab-org/gitlab-ci-multi-runner#1261
See merge request !3909
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
[ci skip]
|
| |/ / /
|/| | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Replace '-n' with '--name' in docker related documentation
`-n` for `docker run` is outdated. We should use `--name` instead. This MR fixes the example in documentation.
Fixes #15174
See merge request !3908
|
| |/ / /
| | | |
| | | |
| | | | |
[ci skip]
|
|/ / /
| | |
| | |
| | | |
[ci skip]
|
| | |
| | |
| | |
| | | |
[ci skip]
|
| | |
| | |
| | |
| | | |
[ci skip]
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add notice about GitLab Runner to requirements docs
This is related to #14589, and problems that may stem from running
GitLab Runner on same machine user installed GitLab web app on.
See merge request !3518
|
| |/ / |
|
|\ \ \ |
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | |/ / / |
|
| | |\ \ \
| | | |_|/
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix typos in CI docs.
See merge request !3709
|
| | | | | |
|
|\ \ \ \ \
| |/ / / / |
|
| | | | | |
|
|/ / / / |
|
|/ / / |
|
| | |
| | |
| | | |
This must be an error as the sentence doesn't make sense otherwise
|
|/ /
| |
| |
| | |
[ci skip]
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
CI: Add 'triggers' keyword to 'only' and 'except' lists to allow control over when triggers cause builds to run
Currently, the `only` and `except` keywords in `.gitlab-ci.yml` only accept ref names or the special `branches` and `tags` keywords. However, these are primarily useful when controlling how repository activity affects the creation of builds. In my case, instead of building on every commit, I'd like to use the following logic:
- If the repository is tagged, do a build.
- Any other normal commits should not cause a build.
- If a build is triggered via the API, always create one for the specified ref.
From what I can tell, this isn't possible via the existing YAML syntax. In this MR, I introduce a new keyword `triggers` that goes along with `branches` and `tags`. I can implement the logic above using the following job configuration:
```yaml
only:
- tags
- triggers
```
I updated the tests and documentation to reflect this and everything seems to pass.
See merge request !3230
|