[lago-devel] Can I define somewhere the collect artifacts?

[Yaniv Kaul]

On Thu, Apr 14, 2016 at 10:59 AM, David Caro <dcaro at redhat.com> wrote:

> On 04/14 10:54, Yaniv Bronheim wrote:
> > to get the files from there to where? to be accessable from the jenkins
> > page after the build is done?
>
> I think I misunderstood something.
> So the files you are storing under /tmp/vdsm-results, are the already
> collected artifacts? If so, to get them pulled by jenkins then yes, you
> have
> to move them to exported-artifacts. This is like that because we are using
> the
> same standard for all the projects, so the jenkins code that we use for
> all of
> them is the same.
>
> If the /tmp/vdsm-results directiory is inside one of the vms created by
> lago
> and used for the vdsm functional tests, then to get it out when you do the
> 'lago collect' you should add it to the artifacts entry in the
> init.json/yaml
>

Yep, that's what I *think* I need to do. I'll test that.
But I suspect, since I've marked my hosts as 'hosts' for oVirt sake (since
otherwise no repository will be created!), that it tries to collect vdsm
logs - which may not exist if we fail before we even created the VDSM RPMs
- this is exactly where the scp from the VMs should not abort.
Y.


> > if so, I do it by copying the files I need to "exported-artifacts"
> folders,
> > then I also added the simple index.html with links to the files and
> folders
> > that I consider relevant for the results . this I do in the
> > build-artifacts.sh
> >
> >
> > On Wed, Apr 13, 2016 at 9:16 PM, David Caro <dcaro at redhat.com> wrote:
> >
> > > On 04/13 21:08, Yaniv Kaul wrote:
> > > > I'm extending the VDSM functional tests, and saving files under
> > > > /tmp/vdsm-results/ - can I simply ask somehow to get all files from
> > > there,
> > > > perhaps via the init.json.ini file would be the right place to add
> this?
> > >
> > > You can use the artifacts entry in the vm definition of the init config
> > > file,
> > > you can see an example here:
> > >
> > >
> > >
> https://github.com/lago-project/lago/blob/master/tests/functional/fixtures/collect/suite.yaml
> > >
> > > just specify the path to the directory instead of a file and it should
> > > recursively pull it
> > >
> > > >
> > > > TIA,
> > > > Y.
> > >
> > > > _______________________________________________
> > > > lago-devel mailing list
> > > > lago-devel at ovirt.org
> > > > http://lists.ovirt.org/mailman/listinfo/lago-devel
> > >
> > >
> > > --
> > > David Caro
> > >
> > > Red Hat S.L.
> > > Continuous Integration Engineer - EMEA ENG Virtualization R&D
> > >
> > > Tel.: +420 532 294 605
> > > Email: dcaro at redhat.com
> > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > Web: www.redhat.com
> > > RHT Global #: 82-62605
> > >
> > > _______________________________________________
> > > lago-devel mailing list
> > > lago-devel at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/lago-devel
> > >
> > >
> >
> >
> > --
> > *Yaniv Bronhaim.*
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R&D
>
> Tel.: +420 532 294 605
> Email: dcaro at redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/lago-devel/attachments/20160414/c87b6d3c/attachment-0001.html>