delta/gitlab/gitlab-ce.git/config/initializers/1_settings.rb, branch docs-pages-https gitlab.com: gitlab-org/gitlab-ce.git Default to HTTPS for all Gravatar URLs 2018-01-25T09:00:46+00:00 Achilleas Pipinellis axil@gitlab.com 2018-01-24T09:11:30+00:00 85940d766a30edb707b3e5154f38ae90c935e0a2 If using gravatar.com, both plain_url and ssl_url in settings are now served via HTTPS. Make this the default. 
If using gravatar.com, both plain_url and ssl_url in settings are now
served via HTTPS. Make this the default.
Adds Rubocop rule for line break around conditionals 2018-01-11T16:34:01+00:00 🙈 jacopo beschi 🙉 intrip@gmail.com 2018-01-11T16:34:01+00:00 729f05f0e3c4835c91e20ccd1ddb630eb7ef4379 






Allow password authentication to be disabled entirely
2017-11-23T13:16:14+00:00

Markus Koller
markus-koller@gmx.ch

2017-11-23T13:16:14+00:00

257fd5713485a05460a9170190100643199a7e48












Set the default gitlab-shell timeout to 3 hours
2017-11-21T17:32:37+00:00

Nick Thomas
nick@gitlab.com

2017-11-21T17:13:21+00:00

afd5911557051c4dae652b386c7a91f746ff18a5












Cleanup transaction metrics
2017-11-02T17:11:43+00:00

Pawel Chojnacki
pawel@chojnacki.ws

2017-09-05T23:26:31+00:00

c97dc61a9e3e203bc7a3315dd6828eda320b4323












Merge branch 'bvl-circuitbreaker-improvements' into 'master'
2017-10-17T10:43:05+00:00

Douwe Maan
douwe@gitlab.com

2017-10-17T10:43:05+00:00

4bbdab764d808a86e2e726b4a717a64da8655a10

Make the circuitbreaker configurable at runtime

See merge request gitlab-org/gitlab-ce!14842




Make the circuitbreaker configurable at runtime

See merge request gitlab-org/gitlab-ce!14842






Read circuitbreaker settings from `Gitlab::CurrentSettings`
2017-10-17T09:50:32+00:00

Bob Van Landuyt
bob@vanlanduyt.co

2017-10-12T12:13:59+00:00

619021fd7a6ac68e2821f89f746fea3a72c25e3b

Instead of from the configuration file





Instead of from the configuration file







Make usage ping scheduling more robust
2017-10-16T09:31:20+00:00

Sean McGivern
sean@gitlab.com

2017-10-13T11:22:38+00:00

f4e94c6ff7b2b5e96edb56d30737687becc4a1a8

On GitLab.com, we see that cron jobs sometimes don't run. This appears to be
because the process that polls for current cron jobs only has a 60 second
validity period, so if (for whatever reason) it misses those 60 seconds, we have
to wait until the next execution.

For the usage ping, this is particularly problematic, as that's only scheduled
to run once a week.

Changing it to run for every minute in a 10 minute period should work around
this, if the above diagnosis is correct. The job itself obtains an exclusive
lease for 24 hours, so rescheduling in quick succession is safe.





On GitLab.com, we see that cron jobs sometimes don't run. This appears to be
because the process that polls for current cron jobs only has a 60 second
validity period, so if (for whatever reason) it misses those 60 seconds, we have
to wait until the next execution.

For the usage ping, this is particularly problematic, as that's only scheduled
to run once a week.

Changing it to run for every minute in a 10 minute period should work around
this, if the above diagnosis is correct. The job itself obtains an exclusive
lease for 24 hours, so rescheduling in quick succession is safe.







Incorporate feedback
2017-10-04T19:01:27+00:00

Zeger-Jan van de Weg
git@zjvandeweg.nl

2017-10-04T19:01:27+00:00

d5486807ba979172e35b81a6b74243225473b69f












Merge branch 'master' into 34102-online-view-of-artifacts-fe
2017-10-04T15:56:03+00:00

Eric Eastwood
contact@ericeastwood.com

2017-10-04T15:56:03+00:00

decf0443698a289ea39dbfff3ae5491936466c92