[JIRA] (OVIRT-2610) Add alerts for Jenkins job queue
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2610?page=com.atlassian.jir... ]
Evgheni Dereveanchin reassigned OVIRT-2610:
-------------------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
> Add alerts for Jenkins job queue
> --------------------------------
>
> Key: OVIRT-2610
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2610
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Evgheni Dereveanchin
> Assignee: Evgheni Dereveanchin
>
> We do have some monitoring in place for Jenkins job queues yet there are no alerts configured.
> Opening ticket to discuss adding alerts and normal actions that should be taken if one happens.
> Sample actions for the infra owner:
> * verify that jobs aren't stuck waiting for a label that has no hosts assigned
> * verify that a stuck job isn't blocking queues (CQ in particular)
> Monitoring can be added to Nagios using a trivial plugin based on API output:
> # curl jenkins.ovirt.org/queue/api/xml | grep -o '<item' | wc -l
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
5 years, 11 months
[JIRA] (OVIRT-2610) Add alerts for Jenkins job queue
by Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-2610:
-------------------------------------------
Summary: Add alerts for Jenkins job queue
Key: OVIRT-2610
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2610
Project: oVirt - virtualization made easy
Issue Type: Improvement
Reporter: Evgheni Dereveanchin
Assignee: infra
We do have some monitoring in place for Jenkins job queues yet there are no alerts configured.
Opening ticket to discuss adding alerts and normal actions that should be taken if one happens.
Sample actions for the infra owner:
* verify that jobs aren't stuck waiting for a label that has no hosts assigned
* verify that a stuck job isn't blocking queues (CQ in particular)
Monitoring can be added to Nagios using a trivial plugin based on API output:
# curl jenkins.ovirt.org/queue/api/xml | grep -o '<item' | wc -l
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
5 years, 11 months
[JIRA] (OVIRT-2609) stdci style reports sometimes disappear pretty
fast
by Roman Mohr (oVirt JIRA)
Roman Mohr created OVIRT-2609:
---------------------------------
Summary: stdci style reports sometimes disappear pretty fast
Key: OVIRT-2609
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2609
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Roman Mohr
Assignee: infra
Can there be a SLA defined for how long we can see test results until they
get removed?
It does not have to be like on travis (where I can still see all my build
logs from years ago), but at least a predictable period would be nice. The
PR in [1] did for instance not have the results anymore from 5 days ago.
Thanks,
Roman
[1] https://github.com/kubevirt/kubevirt/pull/1744
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
5 years, 11 months