[JIRA] (OVIRT-1105) Re: Need a topic branch for experimental development

2017-02-05 Thread rgolan (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=26718#comment-26718
 ] 

rgolan commented on OVIRT-1105:
---

project: ovirt-engine
branch name: experimental-dev

> Re: Need a topic branch for experimental development
> 
>
> Key: OVIRT-1105
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1105
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Gil Shinar
>Assignee: infra
>
> Adding infra-support so a ticket will be opened
> On Sun, Feb 5, 2017 at 1:17 PM, Roy Golan  wrote:
> > Hi infra,
> >
> > I want a new gerrit branch that will make it easier to collaborate with
> > more developers on experimental, edgy changes.
> >
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >



--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

oVirt infra daily report - unstable production jobs - 222

2017-02-05 Thread jenkins 
Good morning!

Attached is the HTML page with the jenkins status report. You can see it also 
here:
 - 
http://jenkins.ovirt.org/job/system_jenkins-report/222//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins

 
 
 
 RHEVM CI Jenkins Daily Report - 05/02/2017
 
00 Unstable Critical
 
   
   ovirt-live_master_experimental_create-iso-el7-x86_64
   
   This job generates a nightly iso of ovirt-live using experimental repos

   
   
   
   ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_master_check-patch-fc24-x86_64_archived_for_deletion
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt_3.6_he-system-tests
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt_4.0_he-system-tests
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt_4.1_system-tests_pre
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   repos_4.1_check-closure_fc24_merged
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   repos_master_check-closure_el7_merged
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   repos_master_check-closure_fc24_merged
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   ___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] Jenkins jobs ownership

2017-02-05 Thread Barak Korren 
On 5 February 2017 at 19:25, Nir Soffer  wrote:
> On Sun, Feb 5, 2017 at 11:33 AM, Martin Sivak  wrote:
>>> A repo where I do not have commit rights means I can't take full 
>>> responsibility.
>
> May pain points with jenkins project:
>
> - No documentation

Please:
http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards.html

> - The format is not stable, each time you edit the format is different

Nope. The examples in the doc above haven't change much, you can just do more.

> - No way to test changes, only infra guys can test changes, sometimes
>   even infra guys cannot test changes and they simply merge them
>   for testing

Just submit a patch the the Jenkins repo - it gets tested and you get
detailed report. For example:

http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/797/artifact/exported-artifacts/differences.html

> - The project format is full of duplication

Some files are unnecessarily messy, but there is no real duplication
in the format itself.

> - No commit right, cannot be responsible for something I cannot change

Nobody asked you to be responsible for the whole repo. Just a few
files in it that contain information the integration/infra teams
cannot possibly know.

>
> Compare with travis:
>
> - Everting defined in *my* project in .travis.yml

See thread I mentioned above.

> - Configuration format is well documented
>   https://docs.travis-ci.com/

We got docs too.

> - Configuration format is well designed, can do lot of work with very
>   little configuration
>   For example - this yaml define matrix of 3 builds:
>   https://github.com/oVirt/vdsm/blob/master/.travis.yml

And this will make a 12 job matrix:

  project:
name: 'vdsm_standard'
  project: vdsm
  trigger: 'on-change'
  version:
- master:
branch: master
- 4.1:
branch: ovirt-4.1
- 4.0:
branch: ovirt-4.0
- 3.6:
branch: ovirt-3.6
  distro:
- el7
- fc24
- fc25

Not really that different.
The real complexity start showing up because you don't really want the
full matrix, and also you want PPC64LE sometimes, etc. etc.

Point being, the real requirements are more complex then what you do on Travis.

> - Easy to test changes before merging (push to your fork on github)

Sent a patch to Gerrit, also see thread mentioned above and:
https://ovirt-jira.atlassian.net/browse/OVIRT-1013

> - Very nice web ui, e.g.
>   https://travis-ci.org/oVirt/vdsm/builds/198571421
>   https://travis-ci.org/oVirt/vdsm/jobs/198571422

Take a look at 'Jenkins Blue Ocean", we'll deploy that eventually.
Then again, the existing Jenkins UI is far more flexible then any of
the modern flashy UIs I've seen. I guess this is a KDE v.s. Gnome kind
of thing...

What really needs to happen is that the relevant info needs to end up
in a Gerrit comment.

-- 
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] Jenkins jobs ownership

2017-02-05 Thread Nir Soffer 
On Sun, Feb 5, 2017 at 11:33 AM, Martin Sivak  wrote:
>> A repo where I do not have commit rights means I can't take full 
>> responsibility.
>> A repo that is not atomically synchronized with my sources means I
>> can't take full responsibility.
>
> Having said that, I would be perfectly fine with a single repository
> that tracks the release configuration, but only if it also held the
> git repository link and hash/branch name that is supposed to be
> released. It would be in some way a "distgit repo". Something like
> Sandro has for builds.
>
> [ovirt-4.0.x-ci]
> git://gerrit.ovirt.org/project.git#ovirt-4.0.x
> git://gerrit.ovirt.org/project2.git#v4.0.x
> git://github.com/Me/repo#master
>
> [ovirt-4.0.6]
> git://gerrit.ovirt.org/project.git#ovirt-4.0.6
> git://gerrit.ovirt.org/project2.git#v4.0.6
> http://github.com/Me/repo/releases/x.y.z.zip
>
> Any release would then be reviewed by the CI team and that would be
> fine for me. It would allow any branch name or versioning convention
> and would not pollute the sources. It would also be gerrit agnostic.

Well said!

May pain points with jenkins project:

- No documentation
- The format is not stable, each time you edit the format is different
- No way to test changes, only infra guys can test changes, sometimes
  even infra guys cannot test changes and they simply merge them
  for testing
- The project format is full of duplication
- No commit right, cannot be responsible for something I cannot change

Compare with travis:

- Everting defined in *my* project in .travis.yml
- Configuration format is well documented
  https://docs.travis-ci.com/
- Configuration format is well designed, can do lot of work with very
  little configuration
  For example - this yaml define matrix of 3 builds:
  https://github.com/oVirt/vdsm/blob/master/.travis.yml
- Easy to test changes before merging (push to your fork on github)
- Very nice web ui, e.g.
  https://travis-ci.org/oVirt/vdsm/builds/198571421
  https://travis-ci.org/oVirt/vdsm/jobs/198571422

Nir

>
> Martin
>
>
> On Sun, Feb 5, 2017 at 10:17 AM, Martin Sivak  wrote:
>> Hi,
>>
>>> The fact that this is specified in the 'jenkins' repo **does not place
>>> this outside the maintainers` responsibility**.
>>
>> A repo where I do not have commit rights means I can't take full 
>> responsibility.
>> A repo that is not atomically synchronized with my sources means I
>> can't take full responsibility.
>>
>>> We actually have an initiative to move this information to the project
>>> repos. I've started with asking on devel list about how to specify
>>> this as part of Standard-CI [1]. But have received little topical
>>> response so far.
>>> [1]: http://lists.ovirt.org/pipermail/devel/2017-January/029161.html
>>
>> You've got enough responses already to propose a different schema than
>> fixed branch names. Just give us a config file. Seriously, stop
>> reinventing the wheel and take a look at how others are doing it
>> (distgit, travis, tito, ...).
>>
>> Martin
>>
>>>
>>> --
>>> Barak Korren
>>> bkor...@redhat.com
>>> RHCE, RHCi, RHV-DevOps Team
>>> https://ifireball.wordpress.com/
>>> ___
>>> Devel mailing list
>>> de...@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
> ___
> Devel mailing list
> de...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1107) [gerrit hooks] don't update bug status to MODIFIED if there is an open patch of other gerrit instance

2017-02-05 Thread Shlomo Ben David (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shlomo Ben David updated OVIRT-1107:

Epic Link: OVIRT-411

> [gerrit hooks] don't update bug status to MODIFIED if there is an open patch 
> of other gerrit instance
> -
>
> Key: OVIRT-1107
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1107
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: infra
>




--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1107) [gerrit hooks] don't update bug status to MODIFIED if there is an open patch of other gerrit instance

2017-02-05 Thread Shlomo Ben David (oVirt JIRA) 
Shlomo Ben David created OVIRT-1107:
---

 Summary: [gerrit hooks] don't update bug status to MODIFIED if 
there is an open patch of other gerrit instance
 Key: OVIRT-1107
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1107
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Shlomo Ben David
Assignee: infra






--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1107) [gerrit hooks] don't update bug status to MODIFIED if there is an open patch of other gerrit instance

2017-02-05 Thread Shlomo Ben David (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shlomo Ben David reassigned OVIRT-1107:
---

Assignee: Shlomo Ben David  (was: infra)

> [gerrit hooks] don't update bug status to MODIFIED if there is an open patch 
> of other gerrit instance
> -
>
> Key: OVIRT-1107
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1107
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: Shlomo Ben David
>




--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5130 - SUCCESS!

2017-02-05 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5130/,
Build Number: 5130,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1106) gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs

2017-02-05 Thread eyal edri [Administrator] (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri [Administrator] updated OVIRT-1106:
-
Epic Link: OVIRT-411

> gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs
> 
>
> Key: OVIRT-1106
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1106
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> Until now the Gerrit Hooks only updated oVirt bugs, but on some occasions a 
> patch have bug-url of a downstream bug, which should also be handled.
> We should enable all available hooks we have on 'RHV' bugs as well, 
> specifically:
> - add external tracker
> - verify backport
> - set POST
> - set MODIFIED ( if the hook detects that another external tracker for 
> internal gerrit instance is added, it shouldn't move to MODIFIED because the 
> bug might need to wait for a d/s patch )
> The improvement for the modified hook should be done as a seperate task afte 
> this one.



--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1106) gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs

2017-02-05 Thread eyal edri [Administrator] (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri [Administrator] updated OVIRT-1106:
-
Priority: High  (was: Medium)

> gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs
> 
>
> Key: OVIRT-1106
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1106
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: eyal edri [Administrator]
>Assignee: infra
>Priority: High
>
> Until now the Gerrit Hooks only updated oVirt bugs, but on some occasions a 
> patch have bug-url of a downstream bug, which should also be handled.
> We should enable all available hooks we have on 'RHV' bugs as well, 
> specifically:
> - add external tracker
> - verify backport
> - set POST
> - set MODIFIED ( if the hook detects that another external tracker for 
> internal gerrit instance is added, it shouldn't move to MODIFIED because the 
> bug might need to wait for a d/s patch )
> The improvement for the modified hook should be done as a seperate task afte 
> this one.



--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1106) gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs

2017-02-05 Thread eyal edri [Administrator] (oVirt JIRA) 
eyal edri [Administrator] created OVIRT-1106:


 Summary: gerrit hooks should also handle 'Red Hat Enterprise 
Virtualization' bugs
 Key: OVIRT-1106
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1106
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: eyal edri [Administrator]
Assignee: infra


Until now the Gerrit Hooks only updated oVirt bugs, but on some occasions a 
patch have bug-url of a downstream bug, which should also be handled.

We should enable all available hooks we have on 'RHV' bugs as well, 
specifically:

- add external tracker
- verify backport
- set POST
- set MODIFIED ( if the hook detects that another external tracker for internal 
gerrit instance is added, it shouldn't move to MODIFIED because the bug might 
need to wait for a d/s patch )

The improvement for the modified hook should be done as a seperate task afte 
this one.




--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5129 - FAILURE!

2017-02-05 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5129/,
Build Number: 5129,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5128 - FAILURE!

2017-02-05 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5128/,
Build Number: 5128,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] Question about testing

2017-02-05 Thread Eyal Edri 
On Sun, Feb 5, 2017 at 3:07 PM, Barak Korren  wrote:

> On 5 February 2017 at 14:58, Marc Young <3vilpeng...@gmail.com> wrote:
> > I see emails floating around about Jenkins.
> >
> > Is there a public Jenkins, or possibly one that I can be invited to?
> > I just finished the vagrant provider and pushed it to rubygems and am
> > currently bringing up a new permanent oVirt server so that i can write
> > some acceptance tests, but having access to a Jenkins and a testable
> > oVirt setup would save me a ton of time.
>
> Yes, oVirt has Jenkins server, and a set of standards about how to
> enable a project to use it [1].
> There is also the "oVirt Systems Tests" project [2] that knows how to
> bring up a fully functional oVirt for testing purposes.
>
> Since you're project is on GitHub as opposed to oVirt's Gerrit, I'm
> afraid it will have to wait a while until we can accomodate it, but
> hopefully not for long [3].
>

Adding Evgheni, the oVirt infra sys admin and the one who is also taking
care of the Jenkins server.
I'm also adding the 'infra@ovirt.org' which is the mailing list for the
oVirt infra team ( the team who provides all CI/CD/Testing services for the
oVirt project ).

So we have our 'production' jenkins @ jenkins.ovirt.org where all oVirt
projects are built & tested using the oVirt standard CI [1], as mentioned
below,
And we also have a staging jenkins [1] which is probably the best place to
do tests on before deploying to the production instance.

As for getting an oVirt instance up & running, its quite easy to do as
Barak said, you just need to run any 'basic suite' from the
ovirt-system-tests repository and you'll have a working oVirt running in
less than 20 min
on your laptop. More info on the OST doc page [2]


[1] http://jenkins-staging.phx.ovirt.org/login?from=%2F
[2]
http://ovirt-system-tests.readthedocs.io/en/latest/docs/general/running_tests.html



>
> [1]: http://ovirt-infra-docs.readthedocs.io/en/latest/CI/
> Build_and_test_standards.html
> [2]: http://ovirt-system-tests.readthedocs.io/en/latest/
> [3]: https://ovirt-jira.atlassian.net/browse/OVIRT-970
>
> --
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
> ___
> Devel mailing list
> de...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5127 - FAILURE!

2017-02-05 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5127/,
Build Number: 5127,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5126 - SUCCESS!

2017-02-05 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5126/,
Build Number: 5126,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5125 - FAILURE!

2017-02-05 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5125/,
Build Number: 5125,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1105) Re: Need a topic branch for experimental development

2017-02-05 Thread Barak Korren (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=26717#comment-26717
 ] 

Barak Korren commented on OVIRT-1105:
-

Can you think up of a name for it? Inventing names is hard...

Also, for which project? I have to just assume you mean engine...

> Re: Need a topic branch for experimental development
> 
>
> Key: OVIRT-1105
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1105
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Gil Shinar
>Assignee: infra
>
> Adding infra-support so a ticket will be opened
> On Sun, Feb 5, 2017 at 1:17 PM, Roy Golan  wrote:
> > Hi infra,
> >
> > I want a new gerrit branch that will make it easier to collaborate with
> > more developers on experimental, edgy changes.
> >
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >



--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1105) Re: Need a topic branch for experimental development

2017-02-05 Thread Gil Shinar (oVirt JIRA) 
Gil Shinar created OVIRT-1105:
-

 Summary: Re: Need a topic branch for experimental development
 Key: OVIRT-1105
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1105
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Gil Shinar
Assignee: infra


Adding infra-support so a ticket will be opened

On Sun, Feb 5, 2017 at 1:17 PM, Roy Golan  wrote:

> Hi infra,
>
> I want a new gerrit branch that will make it easier to collaborate with
> more developers on experimental, edgy changes.
>
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>



--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Need a topic branch for experimental development

2017-02-05 Thread Gil Shinar 
Adding infra-support so a ticket will be opened

On Sun, Feb 5, 2017 at 1:17 PM, Roy Golan  wrote:

> Hi infra,
>
> I want a new gerrit branch that will make it easier to collaborate with
> more developers on experimental, edgy changes.
>
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Need a topic branch for experimental development

2017-02-05 Thread Roy Golan 
Hi infra,

I want a new gerrit branch that will make it easier to collaborate with
more developers on experimental, edgy changes.
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5123 - SUCCESS!

2017-02-05 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5123/,
Build Number: 5123,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] Jenkins jobs ownership

2017-02-05 Thread Martin Sivak 
> A repo where I do not have commit rights means I can't take full 
> responsibility.
> A repo that is not atomically synchronized with my sources means I
> can't take full responsibility.

Having said that, I would be perfectly fine with a single repository
that tracks the release configuration, but only if it also held the
git repository link and hash/branch name that is supposed to be
released. It would be in some way a "distgit repo". Something like
Sandro has for builds.

[ovirt-4.0.x-ci]
git://gerrit.ovirt.org/project.git#ovirt-4.0.x
git://gerrit.ovirt.org/project2.git#v4.0.x
git://github.com/Me/repo#master

[ovirt-4.0.6]
git://gerrit.ovirt.org/project.git#ovirt-4.0.6
git://gerrit.ovirt.org/project2.git#v4.0.6
http://github.com/Me/repo/releases/x.y.z.zip

Any release would then be reviewed by the CI team and that would be
fine for me. It would allow any branch name or versioning convention
and would not pollute the sources. It would also be gerrit agnostic.

Martin


On Sun, Feb 5, 2017 at 10:17 AM, Martin Sivak  wrote:
> Hi,
>
>> The fact that this is specified in the 'jenkins' repo **does not place
>> this outside the maintainers` responsibility**.
>
> A repo where I do not have commit rights means I can't take full 
> responsibility.
> A repo that is not atomically synchronized with my sources means I
> can't take full responsibility.
>
>> We actually have an initiative to move this information to the project
>> repos. I've started with asking on devel list about how to specify
>> this as part of Standard-CI [1]. But have received little topical
>> response so far.
>> [1]: http://lists.ovirt.org/pipermail/devel/2017-January/029161.html
>
> You've got enough responses already to propose a different schema than
> fixed branch names. Just give us a config file. Seriously, stop
> reinventing the wheel and take a look at how others are doing it
> (distgit, travis, tito, ...).
>
> Martin
>
>>
>> --
>> Barak Korren
>> bkor...@redhat.com
>> RHCE, RHCi, RHV-DevOps Team
>> https://ifireball.wordpress.com/
>> ___
>> Devel mailing list
>> de...@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] Jenkins jobs ownership

2017-02-05 Thread Martin Sivak 
Hi,

> The fact that this is specified in the 'jenkins' repo **does not place
> this outside the maintainers` responsibility**.

A repo where I do not have commit rights means I can't take full responsibility.
A repo that is not atomically synchronized with my sources means I
can't take full responsibility.

> We actually have an initiative to move this information to the project
> repos. I've started with asking on devel list about how to specify
> this as part of Standard-CI [1]. But have received little topical
> response so far.
> [1]: http://lists.ovirt.org/pipermail/devel/2017-January/029161.html

You've got enough responses already to propose a different schema than
fixed branch names. Just give us a config file. Seriously, stop
reinventing the wheel and take a look at how others are doing it
(distgit, travis, tito, ...).

Martin

>
> --
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
> ___
> Devel mailing list
> de...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1098) Failing VDSM job: check-patch-fc24

2017-02-05 Thread Barak Korren (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1098:

Resolution: Duplicate
Status: Done  (was: To Do)

Looks like a duplicate of OVIRT-1086.

> Failing VDSM job: check-patch-fc24
> --
>
> Key: OVIRT-1098
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1098
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Edward Haas
>Assignee: infra
>
> Hello,
> Got a failure on VDSM job although all tests passed:
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/53/console
> Thanks,
> Edy.



--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Jenkins jobs ownership

2017-02-05 Thread Barak Korren 
On 3 February 2017 at 15:59, Sandro Bonazzola  wrote:
> 8<-
> Sandro, can someone from you team fix this?
>
...
>
> If you want us to maintain this, this code must move into ovirt-imageio
> repository, so we have full control of it.
> >8

There are currently two pieces of information about the project that
are needed to be known in order to build and release it, but are
currently specified in YAML in the 'jenkins' repo, rather then within
the project's own repo:
1. Which platforms should the project be built on
2. Which oVirt releases should particular build of the project be included in.

The fact that this is specified in the 'jenkins' repo **does not place
this outside the maintainers` responsibility**. Things are done this
way currently only because of a technical limitation with the way
Standard-CI jobs are currently created.

We actually have an initiative to move this information to the project
repos. I've started with asking on devel list about how to specify
this as part of Standard-CI [1]. But have received little topical
response so far.

[1]: http://lists.ovirt.org/pipermail/devel/2017-January/029161.html

-- 
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1098) Failing VDSM job: check-patch-fc24

2017-02-05 Thread Gil Shinar (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=26712#comment-26712
 ] 

Gil Shinar commented on OVIRT-1098:
---

There was some strange error in the mock scrubbing test but I saw it had 
succeeded in that same day.
Can I close the issue?

> Failing VDSM job: check-patch-fc24
> --
>
> Key: OVIRT-1098
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1098
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Edward Haas
>Assignee: infra
>
> Hello,
> Got a failure on VDSM job although all tests passed:
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/53/console
> Thanks,
> Edy.



--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra