An error occurred fetching the project authors.
- 10 Dec, 2019 1 commit
-
-
GitLab Bot authored
-
- 27 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 22 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 08 Nov, 2019 2 commits
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- 01 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 29 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 28 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 16 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 20 Aug, 2019 1 commit
-
-
drew authored
- Added Gitlab::Ci::Config::Entry::Rules and Gitlab::Ci::Config::Entry::Rules:Rule to handle lists of Rule objects to be evalauted for job inclusion - Added `if:` and `changes:` as available Rules::Rule::Clause classes - Added Rules handling logic to Seed::Build#included? with extra specs - Use DisallowedKeysValidator to mutually exclude rules: from only:/except: on job config
-
- 13 Aug, 2019 1 commit
-
-
Kamil Trzciński authored
Since we are unsure what would be the behavior of `stage:` when we work on DAG. Let's make `stage:` to be required today with `needs:`.
-
- 01 Aug, 2019 1 commit
-
-
Kamil Trzciński authored
This implements the support for `needs:` keyword as part of GitLab CI. That makes some of the jobs to be run out of order.
-
- 26 Jul, 2019 1 commit
-
-
Thong Kuah authored
Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
-
- 18 Jun, 2019 1 commit
-
-
Kamil Trzciński authored
This moves all existing `image/services/before_script/variables` into `default:`. This allows us to easily add a default and top-level entries. `default`: is keep backward compatible: to be considered to be job if `default:script:` is specified. This behavior should be removed. All existing `image/services/before_script/variables` are properly handled in root context.
-
- 05 Jun, 2019 1 commit
-
-
Wolphin authored
-
- 14 Jan, 2019 1 commit
-
-
Grzegorz Bizon authored
-
- 04 Jan, 2019 1 commit
-
-
Kamil Trzciński authored
These are data columns that store runtime configuration of build needed to execute it on runner and within pipeline. The definition of this data is that once used, and when no longer needed (due to retry capability) they can be freely removed. They use `jsonb` on PostgreSQL, and `text` on MySQL (due to lacking support for json datatype on old enough version).
-
- 13 Dec, 2018 1 commit
-
-
Kamil Trzciński authored
-
- 04 Dec, 2018 1 commit
-
-
Shinya Maeda authored
Currently, if a job does not have only/except policies, the policy is considered as an unspecified state, and therefore the job is executed regardless of how it's executed and which branch/tags are targetted. Ideally, this should be specified as only: ['branches', 'tags'], as it indicates that unspecified policy jobs are meant to run on any git references.
-
- 08 Nov, 2018 1 commit
-
-
Kamil Trzciński authored
This prevents some of the abusive behaviors, of someone putting 100000 and creating out of memory condition easily
-
- 07 Nov, 2018 6 commits
-
-
Markus Doits authored
-
Markus Doits authored
-
Markus Doits authored
-
Markus Doits authored
before: - Method `validate_retry` has a Cognitive Complexity of 7 (exceeds 5 allowed). Consider refactoring. - Method `validate_retry_max` has a Cognitive Complexity of 9 (exceeds 5 allowed). Consider refactoring. - Method `validate_retry_when` has a Cognitive Complexity of 14 (exceeds 5 allowed). Consider refactoring.
-
Markus Doits authored
-
Markus Doits authored
-
- 27 Oct, 2018 1 commit
-
-
Matija Čupić authored
-
- 26 Oct, 2018 1 commit
-
-
Matija Čupić authored
-
- 04 Oct, 2018 1 commit
-
-
Shinya Maeda authored
-
- 02 Oct, 2018 1 commit
-
-
Shinya Maeda authored
-
- 05 Sep, 2018 1 commit
-
-
Grzegorz Bizon authored
-
- 19 Jul, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 17 Jul, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 05 Jul, 2017 1 commit
-
-
Nick Thomas authored
-
- 14 Jun, 2017 1 commit
-
-
Robert Speicher authored
-
- 12 Jun, 2017 1 commit
-
-
Tomasz Maczukin authored
-
- 06 Mar, 2017 1 commit
-
-
Grzegorz Bizon authored
This makes it possible to maintain backwards compatibility with configs created when manual actions were non-blocking. From now manual actions are blocking if configured with `allow_failure: false`, otherwise manual actions are optional, and their status is ignored.
-
- 03 Mar, 2017 1 commit
- 02 Mar, 2017 1 commit
-
-
Lin Jen-Shin authored
* Replace Unspecified with a field so that it's less surprising * Define inspect for Node for easy debugging (and avoid building a very huge string potentially from built-in inspect) * Set default cache key to 'default'
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
This reverts commit e00fb2bdc2090e9cabeb1eb35a2672a882cc96e9. # Conflicts: # .rubocop.yml # .rubocop_todo.yml # lib/gitlab/ci/config/entry/global.rb # lib/gitlab/ci/config/entry/jobs.rb # spec/lib/gitlab/ci/config/entry/factory_spec.rb # spec/lib/gitlab/ci/config/entry/global_spec.rb # spec/lib/gitlab/ci/config/entry/job_spec.rb # spec/lib/gitlab/ci/status/build/factory_spec.rb # spec/lib/gitlab/incoming_email_spec.rb
-