[
https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jir...
]
Juan Hernández commented on OVIRT-1000:
---------------------------------------
Having the project and the RPM named the same is a price that I would't like to pay.
This has always been the case, even before the introduction of V4. The name of the Python
SDK, for example was ovirt-engine-sdk, but the name of the RPM was
ovirt-engine-sdk-python. For the Ruby SDK (which only has V4) the name is also different:
the repo is ovirt-engine-sdk-ruby but the name of the RPM is rubygem-ovirt-engine-sdk4. We
can't (or should not) force projects to adopt the names that the distribution
packaging requires.
Java SDK 4.1 branch don't execute jenkins jobs
----------------------------------------------
Key: OVIRT-1000
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1000
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: Jenkins
Reporter: Ondra Machacek
Assignee: infra
Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project,
you can see an example here:
https://gerrit.ovirt.org/#/c/69455/1
I've created a patch[1] which I think should fix build-artifacts job, not sure about
check-patch job.
[1]
https://gerrit.ovirt.org/#/c/69459/
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)