[Announcement] new manual job for ost

[Roy Golan]

I used this for both master and 4.1, for clean install and upgrade and it
is excellent, a huge leap forward. Saved me time and gave me confidence in
my verification. Kudos Daniel and team for this. (sorry for top-posting, I
started using inbox.gmail.com and didn't find yet how to respond inline)

On Thu, Feb 16, 2017 at 4:15 PM Daniel Belenky <dbelenky at redhat.com> wrote:

> Hi all,
>
> The oVirt infra team is proud to announce the *new manual job for
> ovirt-system-tests.*
> Link: http://jenkins.ovirt.org/job/ovirt-system-tests_manual/
>
> The new job supports a new feature: testing oVirt upgrades!
> The job can test upgrading current oVirt release from a previous release
> with various options, see table below for full available testing matrix.
>
> The new upgrade jobs will be soon added to the experimental flow and will
> be part of the gating done to oVirt tested repo ( i.e any rpm which breaks
> upgrade won't reach the tested repo ).
>
> *How to use?*
>
>    - In order to use the manual ost job, you first have to build RPMs
>    from your open patches. Just add a comment to your open patch and write *'ci
>    please build', *and you'll get a link to the job that builds your
>    patch.
>    - Go to the manual job, and click '*Build with parameters'*.
>    - Choose the oVirt version you wish to test (should match to the oVirt
>    version of your patch).
>    - Choose the suite type from the drop-down menu. The Available options
>    are:
>       - *Basic*
>       - *Upgrade from release*
>       - *Upgrade from prev release*
>
> versionprevreleaserelease
> master 4.0 4.1
> 4.1 4.0 4.1
> 4.0 ---- 4.0
>
>
>    - Add your custom URLs: here you should supply the link to the Jenkins
>    job that built your patch.
>    - Choose the fallback repo: This is the repo that the Job will fetch
>    the RPMs from. Your RPMs will be used on top of those RPMs.
>    - Choose Lago version: (Unless you want to test Lago's new features,
>    just use the table version)
>    - Click on *Build*, and let the job run. You'll get all the relevant
>    logs from the suites under the '*Build artifacts*' directory when the
>    job is done.
>
> For more detailed review of using the manual job, please refer to Verifying
> an oVirt patch with ovirt-system-tests
> <http://ovirt-system-tests.readthedocs.io/en/latest/docs/CI/developers_info.html?highlight=manual>
> .
> Please feel free to contact the infra team on infra at ovirt.org for any
> more questions you have.
>
> Sincerely,
>
> *Daniel Belenky*
>
> *RHV DevOps*
>
> *Red Hat Israel*
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20170216/3a1c3799/attachment.html>