[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jir... ]
eyal edri [Administrator] reassigned OVIRT-1193:
------------------------------------------------
Assignee: Daniel Belenky (was: infra)
> add on request 'ci help' command via Gerrit
> -------------------------------------------
>
> Key: OVIRT-1193
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Gerrit/git
> Reporter: Barak Korren
> Assignee: Daniel Belenky
>
> On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote:
> > Hi,
> >
> > do you think it would make sense to send a copy-and-paste ready
> > message with help to every new gerrit change?
> >
> > It could provide all the system test (lago) links, mention the Rerun
> > hooks syntax and so on. Just so we do not have to search for it all
> > the time?
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
> Adding infra-support to get a Jira ticket opened.
> --
> Barak Korren
> bkorren(a)redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.824.3#100035)
7 years, 9 months
[JIRA] (OVIRT-1264) Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects'
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1264?page=com.atlassian.jir... ]
eyal edri [Administrator] reassigned OVIRT-1264:
------------------------------------------------
Assignee: Daniel Belenky (was: infra)
> Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects'
> -------------------------------------------------------------------------------
>
> Key: OVIRT-1264
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1264
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: Daniel Belenky
>
> We've been doing some work recently to enable using the 'jenkins' repo to create different jobs for different Jenkins instances. I had been working on enabling its use to configure the staging server, while Gil had been working on using it downstream.
> This work is based on the assumption that the '{{jobs/confs/yaml}}' directory only contains job templates and not individual job definitions. This is certainly true for all standard-CI jobs.
> I have found, however, a few jobs that are defined inside the YAML directory. These include:
> - ovirt-engine_master_coverity-analysis
> - scan_security_and_license_ovirt-engine_master
> - system_gerrit-alert-old-patches
> - system_jenkins-report
> Some of these jobs seem quite old. Can we remove them? Alternatively we could move the definitions to the '{{projects}}' directory, or, ideally, re-factor them into separate 'job-template' and 'project' definitions that reside in the right places.
--
This message was sent by Atlassian JIRA
(v1000.824.3#100035)
7 years, 9 months
[JIRA] (OVIRT-1245) Consider way for organize disaster recovery solution for lists
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1245?page=com.atlassian.jir... ]
eyal edri [Administrator] updated OVIRT-1245:
---------------------------------------------
Epic Link: OVIRT-403
> Consider way for organize disaster recovery solution for lists
> --------------------------------------------------------------
>
> Key: OVIRT-1245
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1245
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Pavel Zhukov
> Assignee: infra
>
> │08:50:51 sbonazzo1 | landgraf: we're lucky enough we have mirrors for users │
> │08:51:05 sbonazzo1 | landgraf: too bad we don't have redundant CI infra :-) │
> │08:51:27 landgraf | sbonazzo1: and lists.. │
> │08:51:40 landgraf | sbonazzo1: so we cannot send outage ntifications there :) │
> │08:51:51 sbonazzo1 | landgraf: yep │
> │08:52:03 sbonazzo1 | landgraf: maybe worth to open a jira ticket for it │
> │08:52:10 sbonazzo1 | landgraf: it will be a huge improvement │
> │08:53:30 sbonazzo1 | landgraf: do we have a disaster recovery plan?
--
This message was sent by Atlassian JIRA
(v1000.824.3#100035)
7 years, 9 months
[JIRA] (OVIRT-1245) Consider way for organize disaster recovery solution for lists
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1245?page=com.atlassian.jir... ]
eyal edri [Administrator] updated OVIRT-1245:
---------------------------------------------
Epic Link: OVIRT-403
> Consider way for organize disaster recovery solution for lists
> --------------------------------------------------------------
>
> Key: OVIRT-1245
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1245
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Pavel Zhukov
> Assignee: infra
>
> │08:50:51 sbonazzo1 | landgraf: we're lucky enough we have mirrors for users │
> │08:51:05 sbonazzo1 | landgraf: too bad we don't have redundant CI infra :-) │
> │08:51:27 landgraf | sbonazzo1: and lists.. │
> │08:51:40 landgraf | sbonazzo1: so we cannot send outage ntifications there :) │
> │08:51:51 sbonazzo1 | landgraf: yep │
> │08:52:03 sbonazzo1 | landgraf: maybe worth to open a jira ticket for it │
> │08:52:10 sbonazzo1 | landgraf: it will be a huge improvement │
> │08:53:30 sbonazzo1 | landgraf: do we have a disaster recovery plan?
--
This message was sent by Atlassian JIRA
(v1000.824.3#100035)
7 years, 9 months