Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

On Wed, Jun 22, 2016 at 2:17 PM, Martin Sivak wrote: > > That's not automation, its just you (human) building the official build > in > > COPR > > rather in jenkins no? > > It is automated enough for me, I just upload (the equivalent of > tagging) the srpm and it builds it for

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

> That's not automation, its just you (human) building the official build in > COPR > rather in jenkins no? It is automated enough for me, I just upload (the equivalent of tagging) the srpm and it builds it for all platforms. It is then automatically released in the project repository. COPR is

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

On Wed, Jun 22, 2016 at 12:49 PM, Martin Sivak wrote: > > What I think we should do is to add support that once an official tag is > > done an official build will be triggered and done. > > The question is can the official build flow be automated? IIRC it > involves > > using

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

> What I think we should do is to add support that once an official tag is > done an official build will be triggered and done. > The question is can the official build flow be automated? IIRC it involves > using tarball + signing or some other manual work which isn't > similar to the way nigthly

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

On Wed, Jun 22, 2016 at 11:21 AM, Martin Sivak wrote: > > - you as packager / maintainer should add your build to the release > > configuration file[1] or send an email with the link to your builds to > the > > person handling the release > > Is there a way to automate this?

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

On Wed, Jun 22, 2016 at 11:21 AM, Martin Sivak wrote: >> - you as packager / maintainer should add your build to the release >> configuration file[1] or send an email with the link to your builds to the >> person handling the release > > Is there a way to automate this? Like

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

> - you as packager / maintainer should add your build to the release > configuration file[1] or send an email with the link to your builds to the > person handling the release Is there a way to automate this? Like giving you the URL of the release repository in COPR and using whatever latest

[ovirt-devel] [TIPS] How to get your package released in oVirt

Hi, since it seems not clear how to get your package included in a oVirt release, here's the procedure: - a new build planned is communicated to devel@ovirt.org from release engineering team - you as package maintainer should prepare your package to be released with desired version (configure.ac,