[
https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25089#comment-25089
]
Juan Hernández commented on OVIRT-1000:
---------------------------------------
I am OK with separating the repositories. My only concern is preserving the
existing repositories for V4, as doing otherwise would disrupt the development
in the current active branches (V4 is active, V3 isn't). [~gshinar] told me
that creating new repositories for V3 won't solve the problem. My understanding
is that the problem is solved if we have different repositories for both
versions, no matter if the new ones are for V3 or V4. I also understand that
creating new repositories for the old versions may involve more work, maybe
renaming or updating more jobs. I am open to pay that price. Lets say that we
create the new two git repositories:
ovirt-engine-sdk-v3 - For V3 of the Python SDK.
ovirt-engine-sdk-java-v3 - For V3 of the Java SDK
The existing jobs will need to be updated so that they only build V4, and then
new jobs will need to be created to build V3. Am I missing something?
> 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)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
