- Infra - oVirt List Archives

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1495?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1495: ----------------------------- Epic Link: (was: OVIRT-403) > Check out Gerrit metrics feature to see if we can push stats to graphana > ------------------------------------------------------------------------ > > Key: OVIRT-1495 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: infra > > Gerrit 2.13 added a new feature that allows sending metrics to an external source like Graphite. > It would be interesting to see if we can push status about our Gerrit instance to our Graphana instance. > More info at: > https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metr… > https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metr… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1495?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1495: ----------------------------- Epic Link: (was: OVIRT-403) > Check out Gerrit metrics feature to see if we can push stats to graphana > ------------------------------------------------------------------------ > > Key: OVIRT-1495 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: infra > > Gerrit 2.13 added a new feature that allows sending metrics to an external source like Graphite. > It would be interesting to see if we can push status about our Gerrit instance to our Graphana instance. > More info at: > https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metr… > https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metr… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1866: -------------------------------- Epic Link: (was: OVIRT-400) > Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY > ---------------------------------------------------------------- > > Key: OVIRT-1866 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins > > It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. > [Link to subject in jenkincci-dev google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qi…] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1866: -------------------------------- Epic Link: (was: OVIRT-400) > Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY > ---------------------------------------------------------------- > > Key: OVIRT-1866 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins > > It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. > [Link to subject in jenkincci-dev google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qi…] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1867) Allow embedded secrets inside the source repo for CI
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1867: -------------------------------- Epic Link: (was: OVIRT-400) > Allow embedded secrets inside the source repo for CI > ---------------------------------------------------- > > Key: OVIRT-1867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Roman Mohr > Assignee: infra > Labels: credentials > > In order to improve the self-service capabilities of standard-ci it is > important for projects, that they can add their own secrets to projects (to > reach external services, e.g. docker hub, ...). > Travis has a very nice system which helps engineers there: > https://docs.travis-ci.com/user/encryption-keys/ > Basically the CI system needs to generate a public/private key pair for > every enabled git repo. The engineer simply fetches the public key via a > well know URL and encrypts the secrets. Then the encrypted secret can be > made part of the source repo. Before the tests are run the CI system > decrypts the secrets. Than can play together pretty well with Jenkinsfiles > too. > Benefit: > * Less manual intervention from CI team to add secrets to jobs > * Strengthen the config-in-code thinking -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1867) Allow embedded secrets inside the source repo for CI
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1867: -------------------------------- Epic Link: (was: OVIRT-400) > Allow embedded secrets inside the source repo for CI > ---------------------------------------------------- > > Key: OVIRT-1867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Roman Mohr > Assignee: infra > Labels: credentials > > In order to improve the self-service capabilities of standard-ci it is > important for projects, that they can add their own secrets to projects (to > reach external services, e.g. docker hub, ...). > Travis has a very nice system which helps engineers there: > https://docs.travis-ci.com/user/encryption-keys/ > Basically the CI system needs to generate a public/private key pair for > every enabled git repo. The engineer simply fetches the public key via a > well know URL and encrypts the secrets. Then the encrypted secret can be > made part of the source repo. Before the tests are run the CI system > decrypts the secrets. Than can play together pretty well with Jenkinsfiles > too. > Benefit: > * Less manual intervention from CI team to add secrets to jobs > * Strengthen the config-in-code thinking -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1868) Allow engineers to write Jenkinsfiles
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1868?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1868: -------------------------------- Epic Link: (was: OVIRT-400) > Allow engineers to write Jenkinsfiles > ------------------------------------- > > Key: OVIRT-1868 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1868 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Roman Mohr > Assignee: infra > > Looks like standard-ci switched internally to use Jenkinsfiles. However it > would be very valuable for engineers, if they could just write their > Jenkinsfile, instead of all the usual standard-ci yamls/scripts. > With the Jenkinsfile the chroot based approach seems to be pretty obsolete, > if you allow people to use the docker agent for the Jenkinsfile. For > KubeVirt it would make standard-ci finally really valuable. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1868) Allow engineers to write Jenkinsfiles
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1868?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1868: -------------------------------- Epic Link: (was: OVIRT-400) > Allow engineers to write Jenkinsfiles > ------------------------------------- > > Key: OVIRT-1868 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1868 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Roman Mohr > Assignee: infra > > Looks like standard-ci switched internally to use Jenkinsfiles. However it > would be very valuable for engineers, if they could just write their > Jenkinsfile, instead of all the usual standard-ci yamls/scripts. > With the Jenkinsfile the chroot based approach seems to be pretty obsolete, > if you allow people to use the docker agent for the Jenkinsfile. For > KubeVirt it would make standard-ci finally really valuable. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1874) Manual building UI
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1874?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1874: -------------------------------- Summary: Manual building UI (was: Manual building) > Manual building UI > ------------------ > > Key: OVIRT-1874 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1874 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Lev Veyde > Assignee: infra > Labels: builds, releases > > Hi, > We need the interface to be able to do manual builds from specific refs > (i.e. tag/hash) for the projects. > Thanks, > -- > Lev Veyde > Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1874) Manual building
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1874?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1874: -------------------------------- Epic Link: (was: OVIRT-400) > Manual building > --------------- > > Key: OVIRT-1874 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1874 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Lev Veyde > Assignee: infra > Labels: builds, releases > > Hi, > We need the interface to be able to do manual builds from specific refs > (i.e. tag/hash) for the projects. > Thanks, > -- > Lev Veyde > Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0