Tree: 0781020be2

master

1.1.0

1.2.0

1.3.0

2.0.0

2.1.0

2.5.0

2.5.1

2.5.2

2.6.0

3.0.0

3.0.1

3.0.2

3.0.3

3.1.0

3.10.0

3.10.1

3.10.2

3.11.0

3.11.1

3.12.0

3.13.0

3.14.0

3.15.0

3.16.0

3.16.1

3.17.0

3.18.0

3.19.0

3.19.1

3.2.0

3.3.0

3.3.1

3.4.0

3.5.0

3.6.0

3.6.1

3.7.0

3.7.1

3.8.0

3.8.1

3.9.0

4.0.0

4.1.0

4.10.0

4.10.1

4.10.2

4.10.3

4.10.4

4.11.0

4.12.0

4.2.0

4.3.0

4.4.0

4.5.0

4.5.1

4.6.0

4.7.0

4.8.0

4.8.1

4.9.0

5.0.0

5.1.0

5.2.0

5.2.1

5.2.2

5.2.3

5.2.4

5.2.5

6.0.0

6.1.0

6.2.0

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '0781020be2'

${ noResults }

Commit Graph

3 Commits (0781020be2613a61de52640939d1e05f73a2287b)

Author	SHA1	Message	Date
Clark Boylan	4c6566b9d5	Add more logging to zuul merger process ... Add logging to the zuul merger process that includes change numbers so that threads of execution can be easily tracked from the zuul server log files to the zuul merger log files. Change-Id: Ic591f3941d6fe84874e16c8309a101a2918979a2	9 years ago
James E. Blair	ef6f2aa0be	Register merge jobs before starting the worker ... It's possible gear doesn't deal with this case gracefully. Change-Id: Icbc79ffdad7de05df53b590ca62a7539fd62c6b5	9 years ago
James E. Blair	4076e2b432	Split the merger into a separate process ... Connect it to Zuul via Gearman. Any number of mergers may be deployed. Directly find the pipeline for a build when processing a result, so that the procedure is roughly the same for build and merge results. The timer trigger currently requires the gerrit trigger also be configured. Make that explicit inside of the timer trigger so that the scheduler API interaction with triggers is cleaner. Change-Id: I69498813764753c97c426e42d17596c2ef1d87cf	9 years ago