Emphasize that GitLab must be partially running when restoring backups.
This caused me a lot of pain until I caught on.
I also enhanced the GitLab Omnibus application data backup restore procedure. I verified the procedure by executing it with GitLab 8.6.4.
See merge request !3844
Document that only unicorn and sidekiq should be stopped.
And the rest of GitLab should remain running.
Also clarified the rest of the GitLab Omnibus restore procedure.
See merge request !3839
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
Fix php-docker example (for new docker versions)
`/.dockerinit` file doesn't exists in new Docker versions. Instead `/.dockerenv` can be used. This MR fixes the PHP example which was working only for older Docker versions.
Fixes gitlab-org/gitlab-ci-multi-runner#1241
See merge request !3907
Add new shortcuts
Closes#14904
- On a project: `i` To navigate to New Issue page.
- On a issuable: `l` To open Label dropdown on a issuable.
- Global: Typing `?` multiple times now toggles the modal.
See merge request !3686
This setup is quite a bit different from before. In the previous setup
raw data was kept around for 30 days and downsampled data for 7 days.
This became problematic for GitLab.com as the number of points and
series resulted in InfluxDB running out of memory when starting up
(besides taking up 30 GB of storage).
To work around this the new setup keeps raw data around for _only_ an
hour while keeping downsampled data around for 7 days. In turn all
Grafana dashboards _only_ query the downsampled data instead of also
querying raw data.
Based on rough calculations this setup needs around 2GB of storage for 1
week of data, excluding whatever is needed for storing the raw data
(this highly depends on the amount of traffic).
If users want to use this new setup they have to remove any existing
dashboards provided by GitLab.com and re-import the ones from the
Grafana dashboards repository
(https://gitlab.com/gitlab-org/grafana-dashboards/). Should users wish
to change their default retention policy the easiest way of doing so is
to simply drop the database and re-run the InfluxDB commands added by
this commit. Users who want to keep their default retention policy as-is
can simply create the "downsampled" policy and run the other commands.
This caused me a lot of pain until I caught on.
I also enhanced the GitLab Omnibus application data backup restore procedure. I verified the procedure by executing it with GitLab 8.6.4.
"git lfs init" is deprecated, use "git lfs install" instead.
Recent releases of git-lfs warn that "init" is a deprecated command and that "install" should be used.
See merge request !3779
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
Implement after_script which allows to do cleanups as part of the build process
This implements `after_script` in global context.
The `after_script` will be executed always after the job, even if the job were canceled.
This requires changes on Runner side that will be implemented in 1.2.
cc @tmaczukin @grzesiek
See merge request !3771
Alfredo Sumaran
Rémy Coutable
Achilleas Pipinellis
Jacob Schatz
Yorick Peterse
Tomasz Maczukin
Stan Hu
Drew Blessing
Drew Blessing
Jacob Vosmaer
John McGehee
Robert Speicher
Douwe Maan
Hannes Rosenögger
Grzegorz Bizon
Kamil Trzciński
Gabriel MazettoandDmitriy Zaporozhets
Felipe Artur
Grzegorz Bizon