On Thu, Jul 20, 2017 at 11:32 AM, Martin Perina <mperina(a)redhat.com> wrote:
On Thu, Jul 20, 2017 at 9:49 AM, Daniel Belenky <dbelenky(a)redhat.com>
wrote:
> Hi all,
>
> In order to free space in our Jenkins master host (
jenkins.ovirt.org),
> we'll need to remove some of the jobs and their artifacts.
> For now, we are planning to remove all 4.0 jobs.
>
Are we absolutely sure that we will not need to release any other
async/downstream release to 4.0 engine and VDSM? I remember we have removed
3.6 build jobs
and later we reintroduced them again because of async/downstream
releases ...
Although I think it's OK to remove 4.0 jobs for other projects ...
If you problem is disk space (not cpu/memory load), then perhaps
remove all 4.0 builds not marked "Keep this build forever"? Should
save a lot of space I guess, and have a very little effect otherwise.
I think it's worth keeping all jobs for now.
If there is any job that you want to keep, please reply to this email with
> details.
>
> Thanks,
> --
>
> DANIEL BELENKY
>
> Associate sw engineer
>
> RHEV DEVOPS
>
> EMEA VIRTUALIZATION R&D
>
> Red Hat Israel <
https://www.redhat.com/>
>
> dbelenky(a)redhat.com IRC: #rhev-integ, #rhev-dev
> <
https://red.ht/sig>
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/devel
>
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Didi