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.readthe
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
On Sun, Feb 5, 2017 at 4:38 PM, Marc Young <3vilpeng...@gmail.com> wrote:
> I'm not sure the process for posting on oVirt.org but I wouldn't mind at
> all. I was going to write one on my personal blog as well. I'll send an
> email in a few.
>
> As for the tests, the unit tests are rspec and can ru
I'm not sure the process for posting on oVirt.org but I wouldn't mind at
all. I was going to write one on my personal blog as well. I'll send an
email in a few.
As for the tests, the unit tests are rspec and can run without a server.
The acceptance tests were, in my mind, just going to be a bunch
On Feb 5, 2017 1:58 PM, "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
Excellent news - saw it on twitter!
Can you send an email to the users
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 pu
On 5 February 2017 at 15:11, Marc Young <3vilpeng...@gmail.com> wrote:
> Thanks for the quick reply, I was actually in the process of rephrasing to
> make sure my question was clear. Thanks, I found the Jenkins instance and
> I'll follow that ticket. In the meantime I'll spin up my own to do github
Thanks for the quick reply, I was actually in the process of rephrasing to
make sure my question was clear. Thanks, I found the Jenkins instance and
I'll follow that ticket. In the meantime I'll spin up my own to do github
pull request tests, it's not a problem.
On Sun, Feb 5, 2017, 6:58 AM Marc Y
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 permane
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
Great, thanks!
I will let you know if something doesn't work as it should
On Sun, Feb 5, 2017 at 12:09 PM, Shlomo Ben David
wrote:
> Hi Tal,
>
> I'm going to apply today the verify grade (-1) for the following hooks:
>
>
>1. *check_product* - if the patch project is not the same as the bug
>
Hi All,
I'm going to apply today the verify grade (-1) for the following hooks:
1. *check_product* - It will return a verify grade (-1) if the patch
project is not the same as the bug product.
2. *check_target_milestone* - It will return a verify grade (-1) if the
patch branch major
Hi Tal,
I'm going to apply today the verify grade (-1) for the following hooks:
1. *check_product* - if the patch project is not the same as the bug
product will return a verify grade (-1).
2. *check_target_milestone* - if the patch branch major version is not
the same as the bug tar
> 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, b
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 respon
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.
>
16 matches
Mail list logo
