June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Epic Link: (was: OVIRT-400) > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1174: -------------------------------- Status: Done (was: To Do) We no longer use deploy-to-experimental anywhere. > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1174: -------------------------------- Epic Link: (was: OVIRT-400) > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1174: -------------------------------- Epic Link: (was: OVIRT-400) > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1247) Re-factor SDK standard-CI jobs to not be different from other jobs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1247?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1247: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) Closing as wontfix since this ticket talks about the STDCI V1 jobs - we should convert the project to STDCI V2 anyway, so replacing this ticket with OVIRT-2232 > Re-factor SDK standard-CI jobs to not be different from other jobs > ------------------------------------------------------------------ > > Key: OVIRT-1247 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1247 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Right now the SDK building jobs use specialized YAML. This makes them different from all other Standard-CI jobs. Need to find a way make them like all the rest. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2232) Move SDK projects to STDCI V2
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2232?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2232: -------------------------------- Epic Link: OVIRT-2175 > Move SDK projects to STDCI V2 > ----------------------------- > > Key: OVIRT-2232 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2232 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > We have a strong incentive to do this since the SDK V1 jobs have their own messy job templates the require special maintenance... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2232) Move SDK projects to STDCI V2
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

Barak Korren created OVIRT-2232: ----------------------------------- Summary: Move SDK projects to STDCI V2 Key: OVIRT-2232 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2232 Project: oVirt - virtualization made easy Issue Type: New Feature Components: CI client projects Reporter: Barak Korren Assignee: infra We have a strong incentive to do this since the SDK V1 jobs have their own messy job templates the require special maintenance... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) This issue is relevant only for the STDCI V1 jobs. SInce we're going to switch the project to STDCI V2, closing with WONTFIX. > Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist > -------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Epic Link: (was: OVIRT-400) > Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist > -------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Epic Link: (was: OVIRT-400) > Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist > -------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0