An error occurred fetching the project authors.
- 14 Oct, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 13 Oct, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 04 Oct, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 03 Oct, 2016 1 commit
-
-
Kamil Trzcinski authored
Conflicts: app/models/ci/pipeline.rb app/models/commit_status.rb
-
- 30 Sep, 2016 1 commit
-
-
Paco Guzman authored
See: https://gitlab.com/gitlab-org/gitlab-ce/commit/6280fd3777920670ee42111fddf29576cbf85988#note_14766241 We wanted to avoid accesses to the file system, because it seems reasonable that if the mounter column has some content it’s because there are an associate file. This is an speed boost when you access to a bunch of build instances to show their information. The problem is that solution doesn’t work if you uses that method to detect the thing and you’re changing the uploaded file on instances that had that column empty. Until you don’t persist the instance the database column will be empty so we can have false negatives
-
- 22 Sep, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 21 Sep, 2016 3 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
So that we could read last few lines rather than read the entire file which could be huge.
-
Lin Jen-Shin authored
-
- 20 Sep, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 19 Sep, 2016 4 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
Environments that can have a URL with predefined CI variables.
-
- 16 Sep, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 15 Sep, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 13 Sep, 2016 1 commit
-
-
Kamil Trzcinski authored
Use a permissions of user to access all dependent projects from CI jobs (this also includes a container images, and in future LFS files)
-
- 09 Sep, 2016 1 commit
-
-
Sergey Gnuskov authored
-
- 01 Sep, 2016 4 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
- 31 Aug, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 25 Aug, 2016 1 commit
-
-
Paco Guzman authored
-
- 18 Aug, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 17 Aug, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 12 Aug, 2016 2 commits
-
-
Kamil Trzcinski authored
-
- 11 Aug, 2016 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
This change simplifies a Pipeline processing by introducing a special new status: created. This status is used for all builds that are created for a pipeline. We are then processing next stages and queueing some of the builds (created -> pending) or skipping them (created -> skipped). This makes it possible to simplify and solve a few ordering problems with how previously builds were scheduled. This also allows us to visualise a full pipeline (with created builds). This also removes an after_touch used for updating a pipeline state parameters. Right now in various places we explicitly call a reload_status! on pipeline to force it to be updated and saved.
-
- 04 Aug, 2016 1 commit
-
- 29 Jul, 2016 2 commits
-
-
Lin Jen-Shin authored
-
Paco Guzman authored
-
- 20 Jul, 2016 5 commits
-
-
Lin Jen-Shin authored
-
Kamil Trzcinski authored
-
Lin Jen-Shin authored
So we no longer join anything, just find the latest pipeline and load builds from there to avoid mixing builds. Thanks Kamil for the help and tests.
-
Kamil Trzcinski authored
-