Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-01-20 | Add latest changes from gitlab-org/gitlab@13-8-stable-eev13.8.0-rc42 | Robert Speicher | |
2020-11-19 | Add latest changes from gitlab-org/gitlab@13-6-stable-eev13.6.0-rc42 | GitLab Bot | |
2020-10-21 | Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42 | GitLab Bot | |
2020-09-19 | Add latest changes from gitlab-org/gitlab@13-4-stable-ee | 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-25 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-14 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-10 | 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-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-16 | 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-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-05 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-25 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-31 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-23 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-20 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-09 | Passing job:rules downstream and E2E specs for job:rules configuration | drew | |
2019-09-06 | Merge branch 'ce-detect-github-pull-requests' into 'master' | Kamil Trzciński | |
Port CreateGithubPullRequestEvents migration from EE See merge request gitlab-org/gitlab-ce!31802 | |||
2019-09-05 | CE port for pipelines for external pull requests | Fabio Pitino | |
Detect if pipeline runs for a GitHub pull request When using a mirror for CI/CD only we register a pull_request webhook. When a pull_request webhook is received, if the source branch SHA matches the actual head of the branch in the repository we create immediately a new pipeline for the external pull request. Otherwise we store the pull request info for when the push webhook is received. When using "only/except: external_pull_requests" we can detect if the pipeline has a open pull request on GitHub and create or not the job based on that. | |||
2019-09-05 | New interruptible attribute supported in YAML parsing. | Cédric Tabin | |
Since it is not possible to dynamically detect if a job is automatically cancellable or not, a this new attribute is necessary. Moreover, it let the maintainer of the repo to adjust the behaviour of the auto cancellation feature to match exactly what he needs. | |||
2019-09-04 | Persist `needs:` validation as config error | Kamil Trzciński | |
In case when `needs:` is missing, but when requested by service, we would not save the pipeline with config_error. This makes it explicit that we want to persist the error as `config_error` failure reason. | |||
2019-08-13 | Require `needs:` to be present | Kamil Trzciński | |
This changes the `needs:` logic to require that all jobs to be present. Instead of skipping do fail the pipeline creation if `needs:` dependency is not found. | |||
2019-08-02 | Make needs: to require previous jobs | Kamil Trzciński | |
This changes `needs:` from weak reference to have a strong reference. This means that job will not be created unless all needs are present as part of a pipeline. | |||
2019-06-05 | preventing blocked users and their PipelineSchdules from creating new Pipelines | drew cimino | |
updated several specs and factories to accomodate new permissions | |||
2019-06-03 | Merge branch 'security-60039' into 'master' | GitLab Release Tools Bot | |
Disallow invalid MR branch name See merge request gitlab/gitlabhq!3052 | |||
2019-05-06 | Fix schedule head pipeline update | Shinya Maeda | |
Currently, schedule head pipeline update method which executed after pipeline creation does not take into account of merge reqeust pipelines. We should use dedicated `all_merge_requests` method in this case. | |||
2019-05-02 | Use full ref when creating MR pipeline in specs | Mark Chao | |
Continuation of 426488b7218e85ce69868ae4628801af2322b74a | |||
2019-04-16 | Rewind IID on Ci::Pipelines | Kamil Trzciński | |
If no pipeline is created we currently have IID gap. This is due to fact that we generate IID not on save, but rather ahead of time. This results, us, losing IIDs. | |||
2019-04-12 | Add frozen_string_literal to spec/services | Thong Kuah | |
Probably useful as we often move these files to "new" files. | |||
2019-04-09 | Use Gitlab::PushOptions for `ci.skip` push option | Luke Duncalfe | |
Previously the raw push option Array was sent to Pipeline::Chain::Skip. This commit updates this class (and the chain of classes that pass the push option parameters from the API internal `post_receive` endpoint to that class) to treat push options as a Hash of options parsed by GitLab::PushOptions. The GitLab::PushOptions class takes options like this: -o ci.skip -o merge_request.create -o merge_request.target=branch and turns them into a Hash like this: { ci: { skip: true }, merge_request: { create: true, target: 'branch' } } This now how Pipeline::Chain::Skip is determining if the `ci.skip` push option was used. | |||
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-01 | Add suffix for merge request event | Shinya Maeda | |
Fix ok Add spec Fix ok Fix Add changelog Fix Add memoization a fix | |||
2019-02-27 | Persist source sha and target sha for merge pipelines | Shinya Maeda | |
source_sha and target_sha are used for merge request pipelines |