Commit Graph

34 Commits

Author SHA1 Message Date
GitLab Bot ed7568cc80 Add latest changes from gitlab-org/gitlab@master 2020-10-16 09:09:06 +00:00
GitLab Bot b17f0b91a6 Add latest changes from gitlab-org/gitlab@master 2020-10-12 15:08:32 +00:00
GitLab Bot 1850d48925 Add latest changes from gitlab-org/gitlab@master 2020-10-07 18:08:34 +00:00
GitLab Bot 418c3b2900 Add latest changes from gitlab-org/gitlab@master 2020-09-30 09:10:11 +00:00
GitLab Bot 61d62a2960 Add latest changes from gitlab-org/gitlab@master 2020-08-07 15:10:17 +00:00
GitLab Bot a7608a4940 Add latest changes from gitlab-org/gitlab@master 2020-07-20 09:09:22 +00:00
GitLab Bot ce34395e91 Add latest changes from gitlab-org/gitlab@master 2020-07-13 12:09:18 +00:00
GitLab Bot 4584816f15 Add latest changes from gitlab-org/gitlab@master 2020-06-22 00:08:57 +00:00
GitLab Bot f78257cbdd Add latest changes from gitlab-org/gitlab@master 2020-03-06 15:08:05 +00:00
GitLab Bot c6c7437861 Add latest changes from gitlab-org/gitlab@master 2020-03-04 12:07:52 +00:00
GitLab Bot ae78b85a25 Add latest changes from gitlab-org/gitlab@master 2020-02-24 12:09:00 +00:00
GitLab Bot 8b1228b0d4 Add latest changes from gitlab-org/gitlab@master 2020-01-10 15:07:47 +00:00
GitLab Bot d10a462fed Add latest changes from gitlab-org/gitlab@master 2019-12-16 12:07:43 +00:00
GitLab Bot 27d91a6299 Add latest changes from gitlab-org/gitlab@master 2019-12-10 15:07:52 +00:00
GitLab Bot 61f0c58946 Add latest changes from gitlab-org/gitlab@master 2019-11-08 12:06:32 +00:00
GitLab Bot deed6022ef Add latest changes from gitlab-org/gitlab@master 2019-11-01 12:06:26 +00:00
GitLab Bot cb3e6b9c1b Add latest changes from gitlab-org/gitlab@master 2019-10-29 18:06:15 +00:00
GitLab Bot dee9315801 Add latest changes from gitlab-org/gitlab@master 2019-10-29 15:07:20 +00:00
GitLab Bot 7515ec41c5 Add latest changes from gitlab-org/gitlab@master 2019-10-28 18:06:15 +00:00
GitLab Bot ad1e4b8fb8 Add latest changes from gitlab-org/gitlab@master 2019-10-21 15:05:58 +00:00
GitLab Bot f155cc9034 Add latest changes from gitlab-org/gitlab@master 2019-10-16 03:06:12 +00:00
drew ac77bb9376 Introducing new Syntax for Ci::Build inclusion rules
- 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-20 20:03:43 +00:00
Kamil Trzciński 583544d089 Require `stage:` to be set with `needs:`
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-08-13 11:47:30 +02:00
Kamil Trzciński 505d71ec88 Introduce default: for gitlab-ci.yml
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-06-18 10:36:07 +00:00
Yoginth 2f6a20ce66 Fix typos in the whole gitlab-ce project 2019-05-20 14:11:44 +00:00
Paul 🐻 9f36097db2 fix(gitlab-ci-config): allow strings in the 'include' keyword
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-05 06:44:33 +00:00
Kamil Trzciński 8a833c720e Allow to use untrusted Regexp via feature flag
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-04 15:00:56 +00:00
Francisco Javier López 6ee1d8cf77 Add port section to CI Image object
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-04-03 09:50:54 +00:00
Kamil Trzciński b22287f00f Make CI refs matching to to use UntrustedRegexp
This makes ref validation to use always `UntrustedRegexp`.
This also splits the existing RubySyntax into separate
class.
2019-03-15 14:38:28 +01:00
Grzegorz Bizon 3c5846cdaa Simplify code related to setting default config values 2019-01-15 11:23:32 +01:00
Grzegorz Bizon 7b712d3598 Make default config entry value configurable
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-15 11:18:14 +01:00
Grzegorz Bizon 67e90a123f Make fabrication of default config entry more readable 2019-01-14 14:27:31 +01:00
Grzegorz Bizon 8b185467e4 Refactor only/except configuration policies
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.
2019-01-14 14:22:13 +01:00
Kamil Trzciński 64b1044e7a ci/config: generalize Config validation into Gitlab::Config:: module
This decouples Ci::Config to provide a common interface for handling
user configuration files.
2018-11-29 16:09:18 +01:00