Packaging CI jobs should register in CR before start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Fuel CI |
Bug Description
Right now, it does not happen and as a result it leaves wrong impression that CI is finished, while it is not. For example see
https:/
Example of good behaviour: mos-infra-ci leaves the following comment on start
-------
Patch Set 1: -Verified
Build started (check pipeline) http://
gate-oslo.
gate-oslo.
-------
As a result, gate-oslo.
The same should be done for all other CI jobs, specifically for 8.0-pkg-
Another bad example is comment from Pkgs Jenkins:
-------
Patch Set 1: -Verified
Starting pkg-build-mos jobs. http://
-------
It is bad because the comment it done in wrong format and as a result, it does not make 'pkg-build-mos' appear in the CI table
description: | updated |
Changed in fuel: | |
milestone: | none → 8.0 |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: area-ci |
I tried patch ('Report jobs that will run immediately' by Dmitry Teselkin) used by Infa CI - it not works with new Zuul (Infra uses 2.0.1, Packaging uses 2.1.0):
2015-11-11 09:25:04,595 ERROR zuul.Independen tPipelineManage r: Exception while reporting start: lib/python2. 7/dist- packages/ zuul/scheduler. py", line 1096, in reportStart getJobs( change) : lib/python2. 7/dist- packages/ zuul/model. py", line 123, in getJobs
Traceback (most recent call last):
File "/usr/local/
for job in self.pipeline.
File "/usr/local/
if not item.live:
AttributeError: 'Change' object has no attribute 'live'
So this feature needs more Zuul investigation.