Fix the GitHub Omniauth instructions
Technically the screenshot is also out of date, but I honestly don't care enough to go through the effort of making a sample application, taking a screenshot, etc.
See merge request !3976
Prepend letter v to GitLab Workhorse version numbers
This helps to address gitlab-org/gitlab-ce#12684 so as to maintain consistency in all GitLab projects.
It also addresses: https://gitlab.com/gitlab-org/gitlab-workhorse/issues/4
Next Steps
- create a set of duplicate tags in workhorse to prevent errors when updating from the patch guide
See merge request !3088
Backport GitHub Enterprise import support from EE
These changes were pulled from GitLab EE to support configuring
an alternative API URL than the default https://api.github.com.
In addition, the `verify_ssl` flag allows users to disable SSL cert
checking.
One modification: add a default `args` option if it does not exist
to avoid breaking existing configurations.
See merge request !3892
Add API doc example with query string for triggering build
Make this explicit to prevent confusion as we saw in gitlab-org/gitlab-ci#413.
See merge request !3947
Changes support from IE 10+ to IE 11+
IE 11 was released 17 October 2013; 2 years ago. Generally what I have experienced is that support for browsers (when newer ones are available) continues for up to 2 years. Based on that info we would drop support for IE 10 and the latest IE we would support would be IE 11.
I also think this is more realistic since no one is really testing anything on IE 10 at the moment. We should start testing on all the browser that we currently support.
Also we can then have real support for flexbox and not need things like `-ms-flexbox` and other IE specific hacks.
cc @iamphill @annabeldunstone @elvongray @alfredo1 @rspeicher
See merge request !3913
These changes were pulled from GitLab EE to support configuring
an alternative API URL than the default https://api.github.com.
In addition, the `verify_ssl` flag allows users to disable SSL cert
checking.
One modification: add a default `args` option if it does not exist
to avoid breaking existing configurations.
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.
Achilleas Pipinellis
Connor Shea
Alex Jordan
Jacob Vosmaer (GitLab)
Rémy Coutable
David de Boer
Dmitriy Zaporozhets
Stan Hu
Alfredo Sumaran
Jacob Schatz
Jacob Schatz
Tomasz Maczukin
Yorick Peterse
Drew Blessing
Drew Blessing
Jacob Vosmaer
John McGehee
Robert Speicher
Douwe Maan