- Infra - oVirt List Archives

[JIRA] (OVIRT-1177) Please add emarcian@redhat.com to jenkins whitelist
by Barak Korren (oVirt JIRA) 22 Feb '17

22 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1177?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1177: ----------------------------------- Assignee: Barak Korren (was: infra) > Please add emarcian(a)redhat.com to jenkins whitelist > --------------------------------------------------- > > Key: OVIRT-1177 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1177 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: rgolan > Assignee: Barak Korren > > Hi Infra, > please add emarcian(a)redhat.com to jenkins whitelist > Thanks, > Roy -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1179) build-artifacts failure for ovirt-engine-nodejs
by Greg Sheremeta (oVirt JIRA) 22 Feb '17

22 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1179?page=com.atlassian.jira.… ] Greg Sheremeta updated OVIRT-1179: ---------------------------------- Resolution: Fixed Status: Done (was: To Do) > build-artifacts failure for ovirt-engine-nodejs > ----------------------------------------------- > > Key: OVIRT-1179 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1179 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hey, > It builds fine locally in mock_runner, and works in koji (brew). > http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_build-artifacts-fc2… > 15:44:23 make[1]: execvp: printf: Argument list too long > 15:44:23 deps/openssl/openssl.target.mk:860: recipe for target > '/home/jenkins/workspace/ovirt-engine-nodejs_master_build-artifacts-fc25-x86_64/ovirt-engine-nodejs/rpmbuild/BUILD/node-v6.9.4/out/Release/obj.target/deps/openssl/libopenssl.a' > failed > https://gerrit.ovirt.org/#/c/72375/ -- Juan tried messing with the ulimit, > but it didn't seem to help. The comments in the patch might help. > It also failed for the on-demand job. > Thanks, > Greg > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1179) build-artifacts failure for ovirt-engine-nodejs
by Greg Sheremeta (oVirt JIRA) 22 Feb '17

22 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1179?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1179: --------------------------------------- [~eedri], [~jhernand(a)redhat.com]'s patch in the previous comment will take care of this. Closing. > build-artifacts failure for ovirt-engine-nodejs > ----------------------------------------------- > > Key: OVIRT-1179 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1179 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hey, > It builds fine locally in mock_runner, and works in koji (brew). > http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_build-artifacts-fc2… > 15:44:23 make[1]: execvp: printf: Argument list too long > 15:44:23 deps/openssl/openssl.target.mk:860: recipe for target > '/home/jenkins/workspace/ovirt-engine-nodejs_master_build-artifacts-fc25-x86_64/ovirt-engine-nodejs/rpmbuild/BUILD/node-v6.9.4/out/Release/obj.target/deps/openssl/libopenssl.a' > failed > https://gerrit.ovirt.org/#/c/72375/ -- Juan tried messing with the ulimit, > but it didn't seem to help. The comments in the patch might help. > It also failed for the on-demand job. > Thanks, > Greg > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1179) build-artifacts failure for ovirt-engine-nodejs
by eyal edri [Administrator] (oVirt JIRA) 22 Feb '17

22 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1179?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1179: -------------------------------------------------- [~gshereme(a)redhat.com] anything needed from infra or this issue will be solved with the patch to the project? > build-artifacts failure for ovirt-engine-nodejs > ----------------------------------------------- > > Key: OVIRT-1179 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1179 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hey, > It builds fine locally in mock_runner, and works in koji (brew). > http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_build-artifacts-fc2… > 15:44:23 make[1]: execvp: printf: Argument list too long > 15:44:23 deps/openssl/openssl.target.mk:860: recipe for target > '/home/jenkins/workspace/ovirt-engine-nodejs_master_build-artifacts-fc25-x86_64/ovirt-engine-nodejs/rpmbuild/BUILD/node-v6.9.4/out/Release/obj.target/deps/openssl/libopenssl.a' > failed > https://gerrit.ovirt.org/#/c/72375/ -- Juan tried messing with the ulimit, > but it didn't seem to help. The comments in the patch might help. > It also failed for the on-demand job. > Thanks, > Greg > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1183) Reinstall some of the Jenkins hypervisors in PHX as ovirt-node
by eyal edri [Administrator] (oVirt JIRA) 22 Feb '17

22 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1183?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1183: --------------------------------------------- Epic Link: OVIRT-403 > Reinstall some of the Jenkins hypervisors in PHX as ovirt-node > --------------------------------------------------------------- > > Key: OVIRT-1183 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1183 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > Since we're running oVirt in PHX and already managed to find critical bugs due to it, > It would be nice to have a few hypervisors running ovirt-node instead of CentOS. > We can use it for Jenkins DC at first to see how it goes. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1183) Reinstall some of the Jenkins hypervisors in PHX as ovirt-node
by eyal edri [Administrator] (oVirt JIRA) 22 Feb '17

22 Feb '17

eyal edri [Administrator] created OVIRT-1183: ------------------------------------------------ Summary: Reinstall some of the Jenkins hypervisors in PHX as ovirt-node Key: OVIRT-1183 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1183 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri [Administrator] Assignee: infra Since we're running oVirt in PHX and already managed to find critical bugs due to it, It would be nice to have a few hypervisors running ovirt-node instead of CentOS. We can use it for Jenkins DC at first to see how it goes. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1182) Make a nice Garavter icon for Jenkins to show up in Gerrit comments
by Barak Korren (oVirt JIRA) 22 Feb '17

22 Feb '17

Barak Korren created OVIRT-1182: ----------------------------------- Summary: Make a nice Garavter icon for Jenkins to show up in Gerrit comments Key: OVIRT-1182 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1182 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Its nice if comments from Jenkins will have a Gravatar to make that clear, and more "friendly". See for example the Kubernetes CI bot. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1182) Make a nice Garavter icon for Jenkins to show up in Gerrit comments
by Barak Korren (oVirt JIRA) 22 Feb '17

22 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1182?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1182: -------------------------------- Epic Link: OVIRT-403 > Make a nice Garavter icon for Jenkins to show up in Gerrit comments > ------------------------------------------------------------------- > > Key: OVIRT-1182 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1182 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Its nice if comments from Jenkins will have a Gravatar to make that clear, and more "friendly". > See for example the Kubernetes CI bot. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

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 eyal edri [Administrator] (oVirt JIRA) 22 Feb '17

22 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1174: -------------------------------------------------- I know, this is why I wrote: "We do need to support other types like ISO and image files, but I wonder if we should keep failing if no artifacts are found." > 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: Jenkins > Reporter: Barak Korren > Assignee: infra > > 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 (v1000.773.3#100032)

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) 22 Feb '17

22 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1174: ------------------------------------- [~eedri] Not all artifacts are RPMs. Not producing RPMs does not mean not producing artifacts. For example, projects that will build containers and upload them to Dockerhub may not produce RPMs too. > 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: Jenkins > Reporter: Barak Korren > Assignee: infra > > 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 (v1000.773.3#100032)

1 0