| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-07-20 | 1 | -121/+0 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-06-21 | 1 | -0/+4 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-06-04 | 1 | -2/+16 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-05-26 | 1 | -0/+7 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-05-11 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-05-05 | 1 | -0/+4 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-04-14 | 1 | -1/+8 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-03-12 | 1 | -17/+6 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-03-03 | 1 | -0/+20 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-09-28 | 1 | -3/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-07-06 | 1 | -5/+0 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-06-26 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-05-27 | 1 | -13/+19 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-05 | 1 | -1/+5 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-08 | 1 | -2/+3 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-13 | 1 | -0/+2 |
| | | |||||
| * | Avoid calling freeze on already frozen strings in lib | Dinesh Panda | 2019-09-10 | 1 | -1/+1 |
| | | |||||
| * | CE: Add project download & project export audit eventce-port-4550-add-project-download-export-audit-event | manojmj | 2019-07-26 | 1 | -1/+1 |
| | | | | | | | This change adds audit events for download of repository and export of project. | ||||
| * | Upgrade to Rails 5.2upgrade-rails-5-2-ce | Heinrich Lee Yu | 2019-07-12 | 1 | -2/+1 |
| | | | | | Updates changed method names and fixes spec failures | ||||
| * | Properly handle multiple X-Forwarded-For addresses in runner IP | Stan Hu | 2019-02-24 | 1 | -1/+1 |
| | | | | | | | | | | | https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24624 extracted the X-Forwarded-For address directly, but this didn't consider the case where multiple proxies are in the chain. To fix this, we use the Rails implementation to filter trusted proxies, as documented by Grape: https://github.com/ruby-grape/grape#remote-ip Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58103 | ||||
| * | Get remote address for runner | Steve Azzopardi | 2019-01-24 | 1 | -1/+1 |
| | | | | | | | | | Check if `X-Forwarded-For` is set before getting the IP of the request, with this the real IP address of the runner is shown if it's behind a proxy. closes https://gitlab.com/gitlab-org/gitlab-ce/issues/53676 | ||||
| * | Enable frozen string in lib/api and lib/backup | gfyoung | 2018-09-29 | 1 | -0/+2 |
| | | | | | | | | | | | Partially addresses #47424. Had to make changes to spec files because stubbing methods on frozen objects is a mess in RSpec and leads to failures: https://github.com/rspec/rspec-mocks/issues/1190 | ||||
| * | Change update entrypoint instead of adding new keep-alive one | Tomasz Maczukin | 2018-06-07 | 1 | -0/+5 |
| | | |||||
| * | Persist runner IP address on contact (#43489) | Dylan Griffith | 2018-02-28 | 1 | -6/+12 |
| | | |||||
| * | Merge branch 'master' into ↵ | Matija Čupić | 2018-02-04 | 1 | -4/+2 |
| |\ | | | | | | | 38265-stuckcijobsworker-wrongly-detects-cancels-stuck-builds-when-per-job-timeout-is-more-than-an-hour | ||||
| | * | use Gitlab::UserSettings directly as a singleton instead of ↵ | Mario de la Ossa | 2018-02-02 | 1 | -4/+2 |
| | | | | | | | | | including/extending it | ||||
| * | | Refactor runner attribute caching implementation | Matija Čupić | 2018-02-04 | 1 | -1/+1 |
| | | | |||||
| * | | Move info update implementation to Ci::Runner model | Matija Čupić | 2018-01-29 | 1 | -26/+1 |
| | | | |||||
| * | | Update runner info on all authenticated requests | Matija Čupić | 2018-01-29 | 1 | -0/+2 |
| | | | |||||
| * | | Extend Runner API helpers with cache info storage | Matija Čupić | 2018-01-29 | 1 | -5/+11 |
| |/ | |||||
| * | Adds Rubocop rule for line break after guard clause | Jacopo | 2017-11-16 | 1 | -0/+1 |
| | | | | | Adds a rubocop rule (with autocorrect) to ensure line break after guard clauses. | ||||
| * | `current_application_settings` belongs on `Gitlab::CurrentSettings` | Sean McGivern | 2017-08-31 | 1 | -0/+2 |
| | | | | | | | | | | | | | | | | | The initializers including this were doing so at the top level, so every object loaded after them had a `current_application_settings` method. However, if someone had rack-attack enabled (which was loaded before these initializers), it would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't have that method. To fix this: 1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need `Object.new.current_application_settings` to work. 2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it like that in several places. 3. Change the initializers to use that new form. | ||||
| * | Fix current feature related specs | Tiago Botelho | 2017-06-28 | 1 | -1/+2 |
| | | |||||
| * | Backport API changes needed to fix sticking in EEbackport-sticking-api-helper-changes | Yorick Peterse | 2017-03-31 | 1 | -1/+5 |
| | | | | | | | These changes are ported over from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1502 to reduce the number of merge conflicts that may occur. | ||||
| * | Remove legacy Runners support in /api/v4/jobs/request | Tomasz Maczukin | 2017-03-20 | 1 | -8/+0 |
| | | | | | | | | | | | | | | | | In Runner v1.3.0 we've started to send User-Agent header with Runner's version data. Since GitLab v8.12.0 we've started to use this header to check if used Runner's version supports 204 status code instead of 404 as a response when there is no jobs to execute by a Runner. In APIv4 (introduced in GitLab 9.0.0) will require Runner v9.0.0. And writing more accurately: GitLab Runner v9.0.0 will require GitLab at least 9.0.0. Because of such breaking change we are able to switch entirely to 204 response code and there is no need to do check of User-Agent. This commit removes useless code and complexity. | ||||
| * | Fix rubocop offenses | Tomasz Maczukin | 2017-03-02 | 1 | -2/+2 |
| | | |||||
| * | Add artifacts uploading authorize API | Tomasz Maczukin | 2017-03-02 | 1 | -0/+4 |
| | | |||||
| * | Add job patch trace API | Tomasz Maczukin | 2017-03-02 | 1 | -0/+13 |
| | | |||||
| * | Add job update API | Tomasz Maczukin | 2017-03-02 | 1 | -1/+10 |
| | | |||||
| * | Fix rubocop offenses | Tomasz Maczukin | 2017-03-02 | 1 | -1/+1 |
| | | |||||
| * | Add jobs requesting API | Tomasz Maczukin | 2017-03-02 | 1 | -0/+28 |
| | | |||||
| * | Rename API::Ci to API::Runnerfeature/runners-v4-api | Tomasz Maczukin | 2017-02-16 | 1 | -0/+23 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |