[JIRA] (OVIRT-1073) Drop nightly publishers in oVirt CI
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1073?page=com.atlassian.jir... ]
eyal edri [Administrator] commented on OVIRT-1073:
--------------------------------------------------
We won't drop the nightly publishers.
Instead we'll just stop publishing RPMs from it and it will only be used to sync tested RPMs each night to the snapshot repos, that way we'll have static nightly updated oVirt repos.
The code to support it for master is already merged and part of the master publisher.
We need to remove all the YAML code from the publisher job gradually until all is left is the code that sync the test repo.
fyi [~sbonazolla(a)redhat.com]
> Drop nightly publishers in oVirt CI
> -----------------------------------
>
> Key: OVIRT-1073
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
> We saw how destructive using the current publishers can be during 4.1 cycle,
> Problems we encountered:
> 1. It hides missing RPMs from experimental flows
> 2. It hides projects that needs to branch or using previous version released
> 3. It creates confusion of which RPMs are really tested in OST and give different results than experimental instead of having a single source of RPMs for oVirt.
> We should aim to drop it for 4.2 and use only experimental deployment.
> However, since we have errors on deploy to experimental flow, we can't progress with this until they will be solved.
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
7 years, 8 months
[JIRA] (OVIRT-1073) Drop nightly publishers in oVirt CI
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1073?page=com.atlassian.jir... ]
eyal edri [Administrator] updated OVIRT-1073:
---------------------------------------------
Status: In Progress (was: Blocked)
> Drop nightly publishers in oVirt CI
> -----------------------------------
>
> Key: OVIRT-1073
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
> We saw how destructive using the current publishers can be during 4.1 cycle,
> Problems we encountered:
> 1. It hides missing RPMs from experimental flows
> 2. It hides projects that needs to branch or using previous version released
> 3. It creates confusion of which RPMs are really tested in OST and give different results than experimental instead of having a single source of RPMs for oVirt.
> We should aim to drop it for 4.2 and use only experimental deployment.
> However, since we have errors on deploy to experimental flow, we can't progress with this until they will be solved.
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
7 years, 8 months
[JIRA] (OVIRT-1199) Re: Please add me to the CI white list
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1199?page=com.atlassian.jir... ]
eyal edri [Administrator] updated OVIRT-1199:
---------------------------------------------
Resolution: Fixed
Status: Done (was: To Do)
> Re: Please add me to the CI white list
> --------------------------------------
>
> Key: OVIRT-1199
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1199
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
> adding infra support to open a ticket.
> On Tue, Feb 21, 2017 at 5:58 PM, Milan Zamazal <mzamazal(a)redhat.com> wrote:
> > Hi, please put me to the CI white list on gerrit.ovirt.org so that
> > Jenkins runs for my patches.
> >
> > Thanks,
> > Milan
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
7 years, 8 months
Ovirt Jenkins Account
by Phillip Bailey
Hi,
I need a Jenkins account so that I can retrigger CI builds when necessary.
I'm not sure whether an account has been created for me previously. I was
going to attempt resetting my password to see if an account exists, but I
couldn't find a "reset password" link anywhere.
Could you please tell me if I have an account and what the process is for
having one created if I don't?
Thank you!
-Phillip Bailey
7 years, 8 months