delta/gitlab/gitlab-ce.git/spec/lib/ci, branch gitlab_intro_docs gitlab.com: gitlab-org/gitlab-ce.git adjusted behavior so canceled builds tagged as allowed to fail do not fail build 2016-03-17T14:55:10+00:00 Geoffrey Lalonde glalonde@google.com 2016-03-17T14:54:56+00:00 4117c815df73ba80258ca472470735826c68753a 






Merge remote-tracking branch 'origin/master' into gitlab-ci-yaml-updates
2016-03-11T13:22:49+00:00

Kamil Trzcinski
ayufan@ayufan.eu

2016-03-11T13:22:49+00:00

388f69b0de6450ec48a8b88df48bbe2d465593ea

# Conflicts:
#	spec/lib/ci/gitlab_ci_yaml_processor_spec.rb





# Conflicts:
#	spec/lib/ci/gitlab_ci_yaml_processor_spec.rb







Allow to define on which builds the current one depends on
2016-03-11T13:15:13+00:00

Kamil Trzcinski
ayufan@ayufan.eu

2016-03-11T13:15:13+00:00

9a271d80128451eecc9a301d5e9924c09740be07












Allow to pass name of created artifacts archive in `.gitlab-ci.yml`
2016-03-11T12:43:57+00:00

Kamil Trzcinski
ayufan@ayufan.eu

2016-03-11T12:43:57+00:00

d300ecf8d9e886ee7cff9b883bfcdbdb1e49769b












Describe special YAML features: the use of anchors and hidden jobs
2016-03-11T12:41:05+00:00

Kamil Trzcinski
ayufan@ayufan.eu

2016-03-11T12:39:11+00:00

ad4d3a075fc338280baaf6240861c9de7aa312ad












Support YAML alias/anchor usage in .gitlab-ci.yml
2016-03-08T07:49:32+00:00

Pascal Bach
pascal.bach@siemens.com

2016-02-24T14:48:56+00:00

344d6e6f89cceb33e371e10de8262154ee108fbe

This allows to reuse one job as a template for another one:

```
job1: &JOBTMPL
  script: execute-script-for-job

job2: *JOBTMPL

```

This also helps to solve some of the issues in #342

Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Fabio Huser <fabio.huser@siemens.com>





This allows to reuse one job as a template for another one:

```
job1: &JOBTMPL
  script: execute-script-for-job

job2: *JOBTMPL

```

This also helps to solve some of the issues in #342

Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Fabio Huser <fabio.huser@siemens.com>







Extend specs for summary build status
2016-02-20T15:35:29+00:00

Grzegorz Bizon
grzesiek.bizon@gmail.com

2016-02-20T15:35:29+00:00

c8b4c874d7b6752149e7eb37ab61771c016f132a

Additional specs cover a case when one of the builds is running but
allowed to fail. Previous implementation returned `running` status,
which is wrong. This behavior has been changed in 8.5, this commit adds
missing specs.





Additional specs cover a case when one of the builds is running but
allowed to fail. Previous implementation returned `running` status,
which is wrong. This behavior has been changed in 8.5, this commit adds
missing specs.







Fix missing ignored? for GenericCommitStatus
2016-02-19T18:58:43+00:00

Kamil Trzcinski
ayufan@ayufan.eu

2016-02-19T18:58:43+00:00

aa812dbfcc693f82e1a9b16e0e894d2800938d9e












Fix builds scheduler when first build is allowed to fail
2016-02-18T10:50:11+00:00

Grzegorz Bizon
grzesiek.bizon@gmail.com

2016-02-18T10:47:35+00:00

8114786665a59526a988ce346393243996769aff

Before this fix when there was only one relevant, previous build and it
failed, but was allowed to fail, entire build had been marked as
skipped.

Closes #3192





Before this fix when there was only one relevant, previous build and it
failed, but was allowed to fail, entire build had been marked as
skipped.

Closes #3192







Add specs for build status helper class
2016-02-18T09:52:57+00:00

Grzegorz Bizon
grzesiek.bizon@gmail.com

2016-02-18T09:52:57+00:00

0ae7c954537663aa2a574133e42d05eafe5db6fb