> Maybe I'm not seeing something here.
What you are not seeing is that this is partially manual and spread
out across multiple repositories.
I do not want to add Jenkins build anywhere. I want to tell Jenkins
what it should build to get the latest release (hash/tag) and nightly
(branch) and be
On Fri, Feb 10, 2017 at 10:42 AM, Martin Sivak wrote:
> > I think you already can do that.
> > When you want to build for a release you can create automation/mom.spec
> > and change automaton/build-artifacts.sh
>
> But that is not what I am after. I want to be able to say: Use
On Fri, Feb 10, 2017 at 10:07 AM, Martin Sivak wrote:
> I am using copr for building mom for a single reason. We have no
> distgit equivalent where I would be able to mark an arbitrary git hash
> as a release (using my tag and branch structure) and so copr gives me
> the
I am using copr for building mom for a single reason. We have no
distgit equivalent where I would be able to mark an arbitrary git hash
as a release (using my tag and branch structure) and so copr gives me
the package release experience I want. Otherwise Jenkins would be fine
with me.
If we are
On Sun, Feb 5, 2017 at 6:25 PM, 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.
> >> A repo that is not atomically synchronized with my sources
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.
>
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
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
> 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,
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
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
On Sat, Feb 4, 2017 at 4:28 PM, Eyal Edri wrote:
>
>
> On Fri, Feb 3, 2017 at 3:59 PM, Sandro Bonazzola
> wrote:
>
>> Hi,
>>
>> I'm taking a discussion starting in gerrit to the mailing lists for
>> broader audience discussion.
>> In
On Fri, Feb 3, 2017 at 3:59 PM, Sandro Bonazzola
wrote:
> Hi,
>
> I'm taking a discussion starting in gerrit to the mailing lists for
> broader audience discussion.
> In https://gerrit.ovirt.org/69268 it has been asked:
>
>
Hi,
I'm taking a discussion starting in gerrit to the mailing lists for broader
audience discussion.
In https://gerrit.ovirt.org/69268 it has been asked:
8<-
Sandro, can someone from you team fix this?
It does not make sense that
14 matches
Mail list logo