- Infra - oVirt List Archives

[JIRA] (OVIRT-1155) Please enable https on resources.ovirt.org
by sbonazzo (oVirt JIRA) 16 Feb '17

16 Feb '17

sbonazzo created OVIRT-1155: ------------------------------- Summary: Please enable https on resources.ovirt.org Key: OVIRT-1155 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1155 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra If no technical issue is preventing us to enable https, please enable it for resources.ovirt.org. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

Barak Korren created OVIRT-1154: ----------------------------------- Summary: Make jenkins-whitelist use Gerrit groups 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.766.0#100032)

1 0

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Epic Link: OVIRT-400 > Make jenkins-whitelist use Gerrit groups > ---------------------------------------- > > 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.766.0#100032)

1 0

[JIRA] (OVIRT-1153) Ensure standard-CI uses the jenkins-whitelist
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1153?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1153: ----------------------------------- Assignee: Barak Korren (was: infra) > Ensure standard-CI uses the jenkins-whitelist > --------------------------------------------- > > Key: OVIRT-1153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > Standard-CI means everyone on the interned can submit a patch with an anutomation script that end up running in oVirt CI. > We want to limit this a little to ensure not anyone can try to hack us. We used to have the jenkins-whitelist repo for that, but it hasn't been used for the standard-CI jobs so far. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1153) Ensure standard-CI uses the jenkins-whitelist
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1153?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1153: ------------------------------------- Patch added to integrate whitelist: https://gerrit.ovirt.org/#/c/72402/ Need to also alert developers before merging > Ensure standard-CI uses the jenkins-whitelist > --------------------------------------------- > > Key: OVIRT-1153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Standard-CI means everyone on the interned can submit a patch with an anutomation script that end up running in oVirt CI. > We want to limit this a little to ensure not anyone can try to hack us. We used to have the jenkins-whitelist repo for that, but it hasn't been used for the standard-CI jobs so far. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1103) Please fix ovirt-system-test for 4.1-pre
by eyal edri [Administrator] (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1103?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1103: --------------------------------------------- Resolution: Won't Fix Status: Done (was: To Do) There is no need to maintain a job for 4.1-pre since its created only before release. We can utilize the existing manual job to run verification on 'pre' released and choose either 'stable' or 'tested' release as base. Its also possible to test upgrades now as well. http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests… > Please fix ovirt-system-test for 4.1-pre > ---------------------------------------- > > Key: OVIRT-1103 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1103 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Tried to use it for testing 4.1-pre repo with 4.1 async release and fails > on missing packages. > Tried also the manual job specifying both 4.1-pre and 4.1 repos, hoping > this would have fixed the missing packages requirements but it fails again. > Not enough time today for investigating myself. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1105) Re: Need a topic branch for experimental development
by eyal edri [Administrator] (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1105?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1105: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) branched created from master. > Re: Need a topic branch for experimental development > ---------------------------------------------------- > > Key: OVIRT-1105 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1105 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: infra > > Adding infra-support so a ticket will be opened > On Sun, Feb 5, 2017 at 1:17 PM, Roy Golan <rgolan(a)redhat.com> wrote: > > Hi infra, > > > > I want a new gerrit branch that will make it easier to collaborate with > > more developers on experimental, edgy changes. > > > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1153) Ensure standard-CI uses the jenkins-whitelist
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

Barak Korren created OVIRT-1153: ----------------------------------- Summary: Ensure standard-CI uses the jenkins-whitelist Key: OVIRT-1153 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: Highest Standard-CI means everyone on the interned can submit a patch with an anutomation script that end up running in oVirt CI. We want to limit this a little to ensure not anyone can try to hack us. We used to have the jenkins-whitelist repo for that, but it hasn't been used for the standard-CI jobs so far. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1153) Ensure standard-CI uses the jenkins-whitelist
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1153?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1153: -------------------------------- Epic Link: OVIRT-400 > Ensure standard-CI uses the jenkins-whitelist > --------------------------------------------- > > Key: OVIRT-1153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Standard-CI means everyone on the interned can submit a patch with an anutomation script that end up running in oVirt CI. > We want to limit this a little to ensure not anyone can try to hack us. We used to have the jenkins-whitelist repo for that, but it hasn't been used for the standard-CI jobs so far. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1093) new gerrit project request: ovirt-on-kubevirt
by eyal edri [Administrator] (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1093?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1093: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) please reopen if anything else is needed > new gerrit project request: ovirt-on-kubevirt > --------------------------------------------- > > Key: OVIRT-1093 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1093 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > On Jan 31, 2017 18:13, "Fabian Deutsch" <fdeutsch(a)redhat.com> wrote: > > Hey, > > > > could you please create the following repository on gerrit: > > > > ovirt-on-kubevirt.git > > > > This repository can documentation, diagrams, and a demo of how ovirt > > can consume KubeVirt. > > > > - fabian > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0