June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2207) Collect findbugs results in pipeline jobs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2207?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2207: -------------------------------- Epic Link: (was: OVIRT-400) > Collect findbugs results in pipeline jobs > ----------------------------------------- > > Key: OVIRT-2207 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2207 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to be able to view "findbugs" results in a convenient way such as the Jenkins "findbugs" plugin provides so that I can analyze the results. > Currently, this feature is supported in STDCI V1 jobs only and we need to have the same support in STDCI V2 jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2207) Collect findbugs results in pipeline jobs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2207?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2207: -------------------------------- Epic Link: (was: OVIRT-400) > Collect findbugs results in pipeline jobs > ----------------------------------------- > > Key: OVIRT-2207 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2207 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to be able to view "findbugs" results in a convenient way such as the Jenkins "findbugs" plugin provides so that I can analyze the results. > Currently, this feature is supported in STDCI V1 jobs only and we need to have the same support in STDCI V2 jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1290) Re-factor OST jobs YAML to reduce duplication
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1290?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1290: -------------------------------- Component/s: (was: oVirt CI) OST scheduled jobs OST Manual job > Re-factor OST jobs YAML to reduce duplication > --------------------------------------------- > > Key: OVIRT-1290 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1290 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job, OST scheduled jobs > Reporter: Barak Korren > Assignee: infra > Labels: ost, yaml > > Besides the experimental flow jobs, and the manual OST job, we also have a few more jobs that run specific OST suits on a scheduled basis. > Historically theses suits were written by different people and different job templates in YAML were also written for each suit. > At some point we have normalized all the suit names in OST to be of the following structure: > {code} > <suit_type>-suit-<ovirt version> > {code} > This was initially done to allow the mirror injection process to find the '{{reposync-config.repo}}' file but also facilitated the creation of the generic manual OST job. > Since all suites now follow the same naming convention there is no more reason to have separate YAML job templates per suit. This separation may even cause subtle issues. > All the YAML OST job templates should be unified so that we'll have just one job template that is parametrized by the suite type and oVirt version. Furthermore we can probably have just one YAML project entry to create all scheduled OST jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1290) Re-factor OST jobs YAML to reduce duplication
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1290?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1290: -------------------------------- Epic Link: (was: OVIRT-400) > Re-factor OST jobs YAML to reduce duplication > --------------------------------------------- > > Key: OVIRT-1290 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1290 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: ost, yaml > > Besides the experimental flow jobs, and the manual OST job, we also have a few more jobs that run specific OST suits on a scheduled basis. > Historically theses suits were written by different people and different job templates in YAML were also written for each suit. > At some point we have normalized all the suit names in OST to be of the following structure: > {code} > <suit_type>-suit-<ovirt version> > {code} > This was initially done to allow the mirror injection process to find the '{{reposync-config.repo}}' file but also facilitated the creation of the generic manual OST job. > Since all suites now follow the same naming convention there is no more reason to have separate YAML job templates per suit. This separation may even cause subtle issues. > All the YAML OST job templates should be unified so that we'll have just one job template that is parametrized by the suite type and oVirt version. Furthermore we can probably have just one YAML project entry to create all scheduled OST jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1290) Re-factor OST jobs YAML to reduce duplication
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1290?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1290: -------------------------------- Epic Link: (was: OVIRT-400) > Re-factor OST jobs YAML to reduce duplication > --------------------------------------------- > > Key: OVIRT-1290 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1290 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: ost, yaml > > Besides the experimental flow jobs, and the manual OST job, we also have a few more jobs that run specific OST suits on a scheduled basis. > Historically theses suits were written by different people and different job templates in YAML were also written for each suit. > At some point we have normalized all the suit names in OST to be of the following structure: > {code} > <suit_type>-suit-<ovirt version> > {code} > This was initially done to allow the mirror injection process to find the '{{reposync-config.repo}}' file but also facilitated the creation of the generic manual OST job. > Since all suites now follow the same naming convention there is no more reason to have separate YAML job templates per suit. This separation may even cause subtle issues. > All the YAML OST job templates should be unified so that we'll have just one job template that is parametrized by the suite type and oVirt version. Furthermore we can probably have just one YAML project entry to create all scheduled OST jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1311) Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1311?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1311: -------------------------------- Component/s: Repositories Mgmt > Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty > --------------------------------------------------------------------------------------- > > Key: OVIRT-1311 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1311 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > If The '{{*.ready}}' directory does not contain any RPMs, the cron job fails. This failure causes all repos not to get published until the failure is fixed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1311) Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1311?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1311: -------------------------------- Epic Link: (was: OVIRT-400) > Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty > --------------------------------------------------------------------------------------- > > Key: OVIRT-1311 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1311 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > If The '{{*.ready}}' directory does not contain any RPMs, the cron job fails. This failure causes all repos not to get published until the failure is fixed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1311) Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1311?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1311: -------------------------------- Epic Link: (was: OVIRT-400) > Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty > --------------------------------------------------------------------------------------- > > Key: OVIRT-1311 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1311 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > If The '{{*.ready}}' directory does not contain any RPMs, the cron job fails. This failure causes all repos not to get published until the failure is fixed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1312: -------------------------------- Epic Link: (was: OVIRT-400) > Make 'scan_for_artifacts.sh' publish repos separately > ----------------------------------------------------- > > Key: OVIRT-1312 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions. > The issue is that if one of the repos fails to sync, the rest do not get synced either. > We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1312: -------------------------------- Epic Link: (was: OVIRT-400) > Make 'scan_for_artifacts.sh' publish repos separately > ----------------------------------------------------- > > Key: OVIRT-1312 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions. > The issue is that if one of the repos fails to sync, the rest do not get synced either. > We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0