- Infra - oVirt List Archives

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by Greg Sheremeta (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1170: --------------------------------------- Yes, still need this. I just haven't gotten back to it yet. I'll test soon. > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Greg Sheremeta > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1084) build a generic yaml template for both github and gerrit projects
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1084?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1084: --------------------------------------------- Summary: build a generic yaml template for both github and gerrit projects (was: Merge github and gerrit jobs) > build a generic yaml template for both github and gerrit projects > ----------------------------------------------------------------- > > Key: OVIRT-1084 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1084 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > As per https://ovirt-jira.atlassian.net/browse/OVIRT-970 gerrit and github jobs contan a lot of common code and features so they should be merged and _github_ suffix removed from the job names. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1084) Merge github and gerrit jobs
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1084?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1084: -------------------------------------------------- OK, didn't understand it from the name of the ticket, i'll rename the ticket to reflect what needs to be done. > Merge github and gerrit jobs > ---------------------------- > > Key: OVIRT-1084 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1084 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > As per https://ovirt-jira.atlassian.net/browse/OVIRT-970 gerrit and github jobs contan a lot of common code and features so they should be merged and _github_ suffix removed from the job names. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-928) check why ost failed on hot plug test while no code got in to break it
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-928?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-928: -------------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > check why ost failed on hot plug test while no code got in to break it > ---------------------------------------------------------------------- > > Key: OVIRT-928 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-928 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: ost_failures > > http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-926: ------------------------------------------------- Any updates? Is this still reproducible? > check why 3.6 experimental job failed even if not error in shown on job > ----------------------------------------------------------------------- > > Key: OVIRT-926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: ost_failures > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/ > [~gbenhaim@redhat.com][~ngoldin@redhat.com][~ederevea][~bkorren@redhat.com] any ideas? -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-929) debug why 3.6 ost job failed on vm template test
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-929?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-929: -------------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > debug why 3.6 ost job failed on vm template test > ------------------------------------------------ > > Key: OVIRT-929 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-929 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: ost_failures > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4428/consoleF… -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

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) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1174: --------------------------------------------- Resolution: Won't Fix Status: Done (was: To Do) I think that as long as we don't have valid projects that doesn't produce artifacts we shouldn't fix it. As for containers - we will probably not trigger 'deploy-to-experimental' job anyway and use a different flow. > 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.824.3#100035)

1 0

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1170: -------------------------------------------------- Do we still need it? If it didn't work out in check-patch, another option is to add an OST test for it. > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Greg Sheremeta > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1193: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > add on request 'ci help' command via Gerrit > ------------------------------------------- > > Key: OVIRT-1193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Barak Korren > Assignee: Daniel Belenky > > On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote: > > Hi, > > > > do you think it would make sense to send a copy-and-paste ready > > message with help to every new gerrit change? > > > > It could provide all the system test (lago) links, mention the Rerun > > hooks syntax and so on. Just so we do not have to search for it all > > the time? > This is doable, but I think experienced users may find this annoying > it ifs too long. > I'm thinking it may be better to have such a message just suggesting > to type something like '@ci help' to get the full help. > It may even be possible to make it clickable with some trickery rather > then just copy-and-paster ready (I will need to check if its possible > to inject links into Gerrit comments). > Apart from that, Roy offered to write a Gerrit plugin that will add > buttons with the various CI commands. > Adding infra-support to get a Jira ticket opened. > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1264) Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects'
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1264?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1264: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects' > ------------------------------------------------------------------------------- > > Key: OVIRT-1264 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1264 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Daniel Belenky > > We've been doing some work recently to enable using the 'jenkins' repo to create different jobs for different Jenkins instances. I had been working on enabling its use to configure the staging server, while Gil had been working on using it downstream. > This work is based on the assumption that the '{{jobs/confs/yaml}}' directory only contains job templates and not individual job definitions. This is certainly true for all standard-CI jobs. > I have found, however, a few jobs that are defined inside the YAML directory. These include: > - ovirt-engine_master_coverity-analysis > - scan_security_and_license_ovirt-engine_master > - system_gerrit-alert-old-patches > - system_jenkins-report > Some of these jobs seem quite old. Can we remove them? Alternatively we could move the definitions to the '{{projects}}' directory, or, ideally, re-factor them into separate 'job-template' and 'project' definitions that reside in the right places. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0