[
https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jir...
]
Barak Korren updated OVIRT-1248:
--------------------------------
Description:
Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a
message explaining what happened.
The SDK jobs set CI -1 instead.
It seems that it is because they are missing the Groovy post-build script that sets up the
specialized whitelist output.
This is probably because the YAML of the SDK jobs is different from all other jobs (see
OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced.
We need to fix this unless OVIRT-1247 get fixed sooner.
was:
Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a
message explaining what happened.
The SDK jobs set CI -1 instead.
It seems that it is because they are missing the Groovy post-build script that sets up the
specialized whitelist output.
This is probably because the YAML of the SDK jobs is different from all other jobs, so
they got overlooked when some if the whitelist changes were introduced.
Make SDK Standard-CI jobs show "friedly" output when
blocked by whitelist
-------------------------------------------------------------------------
Key: OVIRT-1248
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1248
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: Jenkins
Reporter: Barak Korren
Assignee: infra
Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a
message explaining what happened.
The SDK jobs set CI -1 instead.
It seems that it is because they are missing the Groovy post-build script that sets up
the specialized whitelist output.
This is probably because the YAML of the SDK jobs is different from all other jobs (see
OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced.
We need to fix this unless OVIRT-1247 get fixed sooner.
--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)