[JIRA] (OVIRT-1466) Switche to deploying JJB via PIP
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1466?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1466:
--------------------------------
Epic Link: OVIRT-400
> Switche to deploying JJB via PIP
> --------------------------------
>
> Key: OVIRT-1466
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1466
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: jjb, standard-ci
>
> Since the JJB deployment job runs directly on the Jenkins master, we've been creating and using an RPM package for JJB. This made it hard to switch JJB versions.
> Once we implement OVIRT-1465, we gain sufficient isolation via mock to allow ourselves to install JJB via pip.
> We can set things up so that pip installs a specific JJB version, that way we can gate JJB version updates and have then checked by check-patch. We can even expand the upstream polling system to track JJB versions for us and create update patches.
--
This message was sent by Atlassian JIRA
(v1000.1075.0#100051)
7 years, 5 months
[JIRA] (OVIRT-1465) Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1465:
-----------------------------------
Summary: Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
Key: OVIRT-1465
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
Right not we have a custom job for running JJB after patches are merged to the 'jenkins' repo.
Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job.
--
This message was sent by Atlassian JIRA
(v1000.1075.0#100051)
7 years, 5 months
[JIRA] (OVIRT-1464) Jenkins data partition low space warning
by Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-1464:
-------------------------------------------
Summary: Jenkins data partition low space warning
Key: OVIRT-1464
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1464
Project: oVirt - virtualization made easy
Issue Type: Task
Components: oVirt CI
Reporter: Evgheni Dereveanchin
Assignee: infra
Jenkins data partition is running out of space again - it's at 20% free space again since it was last extended by OVIRT-728. THe disk needs to be extended and we may need to check if we can clean up space somehow.
--
This message was sent by Atlassian JIRA
(v1000.1075.0#100051)
7 years, 5 months
[JIRA] (OVIRT-1463) Make change-queue generate the OST report
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1463:
-----------------------------------
Summary: Make change-queue generate the OST report
Key: OVIRT-1463
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1463
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
Since the change-queue has all the information needed for this, we can make it generate the OST report.
--
This message was sent by Atlassian JIRA
(v1000.1075.0#100051)
7 years, 5 months
[JIRA] (OVIRT-1462) Generate more detailed output from change-queue tests
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1462:
-----------------------------------
Summary: Generate more detailed output from change-queue tests
Key: OVIRT-1462
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1462
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
The change-queue tester jobs can have some additional information that may be useful for understanding issues but is not reported anywhere ATM.
This information includes:
# If the test failed because a build job failed, and which build job made it fail.
# If the test failed during OST run, which suits failed.
This information should, at least, be presented in the test results screen, but may also be preserved and included in the email or Gerrit notifications about failing changes.
--
This message was sent by Atlassian JIRA
(v1000.1075.0#100051)
7 years, 5 months
[JIRA] (OVIRT-1462) Generate more detailed output from change-queue tests
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1462?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1462:
--------------------------------
Epic Link: OVIRT-400
> Generate more detailed output from change-queue tests
> -----------------------------------------------------
>
> Key: OVIRT-1462
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1462
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: change-queue
>
> The change-queue tester jobs can have some additional information that may be useful for understanding issues but is not reported anywhere ATM.
> This information includes:
> # If the test failed because a build job failed, and which build job made it fail.
> # If the test failed during OST run, which suits failed.
> This information should, at least, be presented in the test results screen, but may also be preserved and included in the email or Gerrit notifications about failing changes.
--
This message was sent by Atlassian JIRA
(v1000.1075.0#100051)
7 years, 5 months