January 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1001: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by Petr Horacek (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] Petr Horacek commented on OVIRT-1001: ------------------------------------- It works, thanks again. > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1001: -------------------------------------------------- done, you should have admin rights on that repo now. > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by Petr Horacek (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] Petr Horacek commented on OVIRT-1001: ------------------------------------- Ok, could you please set those rights to phoracek(a)redhat.com? Thanks a lot. > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1001: -------------------------------------------------- Usually the maintainer of the project does it from GitHub, So you just need to permission updated - who should be the maintainer on the GitHub project? > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by Petr Horacek (oVirt JIRA) 03 Jan '17

03 Jan '17

Petr Horacek created OVIRT-1001: ----------------------------------- Summary: GitHub token for ovirt-engine-api-model and Travis CI Key: OVIRT-1001 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Petr Horacek Assignee: infra Hello, I'd like to publish documentation made by https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built and deployed by Travis). I've already done that on my fork https://github.com/phoracek/ovirt-engine-api-model but I'd like it to be publicly available on ovirt.github.io/ovirt-engine-api-model. What I need for that is GitHub token (https://github.com/settings/tokens/new) that will give me 'public_repo' scope rights (to be able to create a new branch and push commits into it). It will be encrypted for Travis and therefore not usable by others. Second think is to enable Travis for ovirt-engine-api-model repository. Maybe it would be also necessary to enable GitHub Pages on the project, but I think it will be done automatically with branch gh-pages. Would it be possible? Is there a better way, such as creating a new user, give him rights for the repository and generate token for it? Thanks, Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1000: -------------------------------------------------- So what do you suggest? can you layout the new repos/name you'd like to see for V3+V4 and where they should be built? > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-973: -------------------------------------------- Summary: add support for custom build params on build-on-demand jobs (was: nightly ovirt-engine build is missing Chrome permutation) > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-973: ------------------------------------------------- I changed the job to add support for it, but its not trivial and not sure when we can do it, If someone needs a specific build, he'll need to run it locally for now or send a patch like suggested in this ticket > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-973) nightly ovirt-engine build is missing Chrome permutation
by Vojtech Szocs (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] Vojtech Szocs commented on OVIRT-973: ------------------------------------- bq. How much time it will add if we'll add chrome to the permutations? At least +50% GWT build time, I'd say. bq. I wouldn't want to pay a constant time penalty just because a single manual test needed it. Agreed. GWT Chrome build should be opt-in, only when needed. bq. You can easily send a patch to build-artifacts with the permutations you want and then use the 'build-on-demand' job using 'ci please build' to build rpms using the new PARAMS. Good point, but can we have a "long standing" (forever open) patch for this purpose? Just to clarify, what I meant in my previous comment was this: 1, user gets a nightly Engine build (FF-only) 2, user decides he/she needs Chrome support for that particular build 3, user re-triggers the particular build and passes some param (defined in Jenkins job config and somehow passed to build script) to trigger Chrome GWT permutation > nightly ovirt-engine build is missing Chrome permutation > -------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0