Rémy Coutable 95a7fbe97c Merge branch 'artifacts-expire-date' into 'master' ...

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

2016-06-14 13:40:01 +00:00

..

fixtures

Merge remote-tracking branch 'origin/master' into rename-ci-commit-phase-2

2016-06-07 10:26:27 +02:00

migrate

Merge branch 'artifacts-expire-date' into 'master'

2016-06-14 13:40:01 +00:00

schema.rb

Merge remote-tracking branch 'origin/master' into artifacts-expire-date

2016-06-14 11:38:44 +02:00

seeds.rb

init commit

2011-10-09 00:36:38 +03:00