February 2017 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1182) Make a nice Garavter icon for Jenkins to show up in Gerrit comments

by Barak Korren (oVirt JIRA)

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)

8 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1182) Make a nice Garavter icon for Jenkins to show up in Gerrit comments

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1182?page=com.atlassian.jir... ] 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)

8 years, 2 months

1
0
0 / 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)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jir... ] 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)

8 years, 2 months

1
0
0 / 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)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jir... ] 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)

8 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1181) Remove the CI-whitelsit GitHub mirror

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-1181: ----------------------------------- Summary: Remove the CI-whitelsit GitHub mirror Key: OVIRT-1181 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1181 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: High Having this on GitHub makes the a list of people's email-addresses far too public. It also makes people confused and try to update it with GitHub pull requests. We should probably remove the GitHub mirror, and also make sure the Gerrit repo is also not that easy to look into. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

8 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1181) Remove the CI-whitelsit GitHub mirror

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1181?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1181: -------------------------------- Epic Link: OVIRT-403 > Remove the CI-whitelsit GitHub mirror > ------------------------------------- > > Key: OVIRT-1181 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1181 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > Having this on GitHub makes the a list of people's email-addresses far too public. > It also makes people confused and try to update it with GitHub pull requests. > We should probably remove the GitHub mirror, and also make sure the Gerrit repo is also not that easy to look into. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

8 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1179) build-artifacts failure for ovirt-engine-nodejs

by Juan Hernández (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1179?page=com.atlassian.jir... ] Juan Hernández commented on OVIRT-1179: --------------------------------------- Here is the patch: Use 'mktemp' to create the build directory https://gerrit.ovirt.org/72840 > 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-f... > 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)

8 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1179) build-artifacts failure for ovirt-engine-nodejs

by Juan Hernández (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1179?page=com.atlassian.jir... ] Juan Hernández commented on OVIRT-1179: --------------------------------------- [~bkorren(a)redhat.com] is completely right, mktemp is better than a fixed path, I will submit a patch to change that. Note that the only possible downside is that in some distributions (Fedora, for example) the /tmp directory is mounted by default as a tmpfs filesystem, so in those cases the build will run completely in memory, which may cause issues in low memory environments. > 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-f... > 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)

8 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1154: ------------------------------------- The +1 is meant for allowing first-time submitters to have their code checked. I think we should probably most of the various ideas raised here rather then just picking one or the other. One reason to do that for example is that some maintainers may prefer seeing the output of CI prior to setting CR+1. > 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: Jenkins > 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 (v1000.773.3#100032)

8 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1180) No Build Executes message from CI

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1180?page=com.atlassian.jir... ] Barak Korren reassigned OVIRT-1180: ----------------------------------- Assignee: Barak Korren (was: infra) > No Build Executes message from CI > --------------------------------- > > Key: OVIRT-1180 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1180 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: Barak Korren > > Hello, > I go the following message from gerrit this morning: > (happened on several patches) > --- > No Builds Executed > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc25-x86_64/1612/ : To > avoid overloading the infrastructure, a whitelist for > running gerrit triggered jobs has been set in place, if > you feel like you should be in it, please contact infra at > ovirt dot org. > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/7476/ : To > avoid overloading the infrastructure, a whitelist for > running gerrit triggered jobs has been set in place, if > you feel like you should be in it, please contact infra at > ovirt dot org. > --- > Thanks, > Edy. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

8 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra February 2017