- 27 Oct, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
Now, when requesting a commit from the Repository model, the results are not cached. This means we're fetching the same commit by oid multiple times during the same request. To prevent us from doing this, we now cache results. Caching is done only based on object id (aka SHA). Given we cache on the Repository model, results are scoped to the associated project, eventhough the change of two repositories having the same oids for different commits is small.
-
- 05 Oct, 2017 5 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
Conflicts: app/models/ci/pipeline.rb
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 25 Sep, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 18 Sep, 2017 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
Use project full path that can be received from a pipeline object
-
- 14 Sep, 2017 1 commit
-
-
Yorick Peterse authored
This ensures that if a pipeline is present for the last commit on a project's homepage we only run 1 query to get the builds, instead of running 2 queries. See https://gitlab.com/gitlab-org/gitlab-ce/issues/36878#note_40073339 for more information.
-
- 12 Sep, 2017 2 commits
-
-
Maxim Rydkin authored
-
Maxim Rydkin authored
-
- 06 Sep, 2017 7 commits
-
-
Kamil Trzcinski authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
-
- 04 Sep, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 03 Sep, 2017 2 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 01 Sep, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 31 Aug, 2017 3 commits
-
-
Zeger-Jan van de Weg authored
Given the user can soon have multiple config sources for CI, we now store what type at the time of the pipeline run we chose. This will give us insight into what triggered the new pipeline so we can display it to the enduser.
-
Zeger-Jan van de Weg authored
Behind an application setting, which defaults to false, this commit implements the implied CI/CD config. Which means that in the case we can't find the `.gitlab-ci.yml` on the commit we want to start a pipeline for, we fall back to an implied configuration. For now the Bash template has been copied to `Auto-Devops.gitlab-ci.yml` so the tests actually work. Fixes #34777
-
Grzegorz Bizon authored
-
- 26 Aug, 2017 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 23 Aug, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
It was missing and expected it wouldn't hurt anyone
-
- 01 Aug, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 28 Jul, 2017 2 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 06 Jul, 2017 1 commit
-
-
Yorick Peterse authored
This is allowed for existing instances so we don't end up 76 offenses right away, but for new code one should _only_ use this if they _have_ to remove non database data. Even then it's usually better to do this in a service class as this gives you more control over how to remove the data (e.g. in bulk).
-
- 05 Jul, 2017 3 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 04 Jul, 2017 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 03 Jul, 2017 2 commits
-
-
Lin Jen-Shin authored
updating builds and updating pipelines. We check against being able to merge or push if the ref is protected.
-
Lin Jen-Shin authored
-