Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-03-18 | Add latest changes from gitlab-org/gitlab@14-9-stable-eev14.9.0-rc42 | GitLab Bot | |
2022-02-18 | Add latest changes from gitlab-org/gitlab@14-8-stable-eev14.8.0-rc42 | GitLab Bot | |
2022-01-20 | Add latest changes from gitlab-org/gitlab@14-7-stable-eev14.7.0-rc42 | GitLab Bot | |
2021-12-20 | Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42 | GitLab Bot | |
2021-09-20 | Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42 | GitLab Bot | |
2021-08-19 | Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42 | GitLab Bot | |
2021-02-18 | Add latest changes from gitlab-org/gitlab@13-9-stable-eev13.9.0-rc42 | GitLab Bot | |
2020-12-17 | Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42 | GitLab Bot | |
2020-10-21 | Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42 | GitLab Bot | |
2020-08-20 | Add latest changes from gitlab-org/gitlab@13-3-stable-ee | GitLab Bot | |
2020-07-20 | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | |
2020-06-18 | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | |
2020-03-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-04 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-16 | Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-80898 | GitLab Bot | |
2019-12-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-08 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-01 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-28 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-08-20 | Introducing new Syntax for Ci::Build inclusion rules | drew | |
- 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 | |||
2019-08-13 | Require `stage:` to be set with `needs:` | Kamil Trzciński | |
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:`. | |||
2019-07-02 | Prevent Billion Laughs attack | Fabio Pitino | |
It keeps track of the memory being used when loading the YAML file as well as the depth of nesting. Track exception when YAML is too big | |||
2019-06-18 | Introduce default: for gitlab-ci.yml | Kamil Trzciński | |
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. | |||
2019-05-20 | Fix typos in the whole gitlab-ce project | Yoginth | |
2019-04-05 | fix(gitlab-ci-config): allow strings in the 'include' keyword | Paul 🐻 | |
This fix is a followup to !24098 which introduced a validation of the `include:` keyword of a gitlab-ci configuration file when triggered from /ci/lint API calls. However, there was a test case missing: the case of a single string as value. I have added a test case for that which shows that the code was not validating it correctly. This commit fixes that to allow all `include:` valid inputs. | |||
2019-04-04 | Allow to use untrusted Regexp via feature flag | Kamil Trzciński | |
This brings support for untrusted regexp for 'only:refs:' when enabled via feature flag: alllow_unsafe_ruby_regexp. This is by default disabled, and should not be used in production | |||
2019-04-03 | Add port section to CI Image object | Francisco Javier López | |
In order to implement https://gitlab.com/gitlab-org/gitlab-ee/issues/10179 we need several modifications on the CI config file. We are adding a new ports section in the default Image object. Each of these ports will accept: number, protocol and name. By default this new configuration will be only enabled in the Web IDE config file. | |||
2019-03-15 | Make CI refs matching to to use UntrustedRegexp | Kamil Trzciński | |
This makes ref validation to use always `UntrustedRegexp`. This also splits the existing RubySyntax into separate class. | |||
2019-01-15 | Simplify code related to setting default config values | Grzegorz Bizon | |
2019-01-15 | Make default config entry value configurable | Grzegorz Bizon | |
Introduce `default:` configuration entry setting that makes it possible to configure a default value of an entry, what overrides class-level `def self.default` value. | |||
2019-01-14 | Make fabrication of default config entry more readable | Grzegorz Bizon | |
2019-01-14 | Refactor only/except configuration policies | Grzegorz Bizon | |
This commit refactors only/except policies so that these policies could be self-contained. This also adds some changes to YAML configuration library to provide more context to default entry value fabrication process. | |||
2018-11-29 | ci/config: generalize Config validation into Gitlab::Config:: module | Kamil Trzciński | |
This decouples Ci::Config to provide a common interface for handling user configuration files. |