95a7fbe97c
Artifacts expire date What do you think @grzesiek? The syntax will be simple: ``` job: artifacts: expire_in: 7d ``` - [x] Implement `expire_in` - [x] Check current design of expiry information with @jschatz1 and @markpundsack - [x] Add tests in GitLab application for a `ExpireBuildArtifactsWorker` and for `ArtifactsController::keep` - [x] Add user documentation how to use `artifacts:expire_in` - [x] Prepare GitLab Runner changes to pass `expire_in`: gitlab-org/gitlab-ci-multi-runner!191 - [x] Fix `timeago` with help of @jschatz1 - [x] Merge latest master after builds view changes @iamphill - [ ] Add Omnibus support for `expire_build_artifacts_worker` cron job - [ ] Add documentation how to configure `expire_build_artifacts_worker` This is based on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4201. See merge request !4200 |
||
---|---|---|
.. | ||
api | ||
build_artifacts | ||
docker | ||
examples | ||
img | ||
permissions | ||
quick_start | ||
runners | ||
services | ||
ssh_keys | ||
triggers | ||
variables | ||
yaml | ||
enable_or_disable_ci.md | ||
README.md |
GitLab CI Documentation
CI User documentation
- Get started with GitLab CI
- CI examples for various languages
- Learn how to enable or disable GitLab CI
- Learn how
.gitlab-ci.yml
works - Configure a Runner, the application that runs your builds
- Use Docker images with GitLab Runner
- Use CI to build Docker images
- Use variables in your
.gitlab-ci.yml
- Use SSH keys in your build environment
- Trigger builds through the API
- Build artifacts
- User permissions
- API
- CI services (linked docker containers)