diff options
| author | Stan Hu <stanhu@gmail.com> | 2016-08-04 06:06:15 +0000 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2016-08-04 06:06:15 +0000 |
| commit | 95e5b4634db48656317242e2691388f68e8dcd37 (patch) | |
| tree | c706d10cb10e434fddf91d69381f29ca0240c154 /doc/administration/build_artifacts.md | |
| parent | 532202a5278a622de874b9dfc1c4f7fe9ddf5ce4 (diff) | |
| parent | a999153bcfcadc2d8a44eaceee1d63cc65957fcf (diff) | |
| download | gitlab-ce-95e5b4634db48656317242e2691388f68e8dcd37.tar.gz | |
Merge branch 'fix_slack_notification_build' into 'master'
Don't setup DB for slack notification build
## What does this MR do?
Fix error with build related to slack notification: https://gitlab.com/gitlab-org/gitlab-ee/builds/2834026
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## What are the relevant issue numbers?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
See merge request !5661
Diffstat (limited to 'doc/administration/build_artifacts.md')
0 files changed, 0 insertions, 0 deletions