Fwd: [oVirt Jenkins] standard-enqueue - Build #6908 - FAILURE!

[Juan Hernández]

On 11/15/2017 02:33 PM, Barak Korren wrote:
> Hi Juan,
> 
> What is the point of the
> 'ovirt-engine-api-metamodel_1.1_build-artifacts-*' jobs?
> 
> For post-merge jobs, the 'version' part of the job names is supposed
> to refer to an oVirt version.
> We keep getting errors like the one below because the system is trying
> to 'release' the package into a non-existent oVirt version (1.1 in
> this case)...
>

The version part of those jobs is the version of the project, the 
`ovirt-egnine-api-metamodel` project in this case. Why should it be the 
version of the `ovirt-engine` project?

If the version needs to be the version of the `ovirt-engine` project we 
can change it, but doesn't seem right to me.

Note also that these jobs don't produce anything that needs to be 
released as part of the oVirt project. The artifacts are released via 
Maven Central, and used only during build time of the engine and the SDKs.

> ---------- Forwarded message ----------
> From:  <jenkins at jenkins.phx.ovirt.org>
> Date: 15 November 2017 at 10:49
> Subject: [oVirt Jenkins] standard-enqueue - Build #6908 - FAILURE!
> To: infra at ovirt.org
> 
> 
> Build: http://jenkins.ovirt.org/job/standard-enqueue/6908/
> Build Name: #6908
> Build Description: Gerrit: 84151 - ovirt-engine-api-metamodel (1.1)
> Build Status: FAILURE
> Gerrit change: https://gerrit.ovirt.org/84151
> - title: [maven-release-plugin] prepare for next development iteration
> - project: ovirt-engine-api-metamodel
> - branch: metamodel_1.1
> - author: Juan Hernandez <juan.hernandez at redhat.com>
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
> 
> 
>