[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira... ]
Barak Korren updated OVIRT-921:
-------------------------------
Epic Link: (was: OVIRT-400)
> Smarter cache handling for mock_runner.sh
> -----------------------------------------
>
> Key: OVIRT-921
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: mock, mock_runner.sh, performance, standard-ci
>
> We've improved our handing of mock caches in OVIRT-902, but it could be better.
> Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way:
> * Mock actually has two separate caches that could be handled separately:
> *# The yum cache - Caches package that are installed in the chroot
> *# The root cache - Keeps an archive of the whole chroot
> * We can make the yum cache shared by all the chroots that use the same repos
> * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file:
> ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}}
> ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}}
> * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer:
> ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}}
> * We can use a different compression algorithm for the chroot acche, this may yield better performance.
> * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years
[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira... ]
Barak Korren updated OVIRT-921:
-------------------------------
Epic Link: (was: OVIRT-400)
> Smarter cache handling for mock_runner.sh
> -----------------------------------------
>
> Key: OVIRT-921
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: mock, mock_runner.sh, performance, standard-ci
>
> We've improved our handing of mock caches in OVIRT-902, but it could be better.
> Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way:
> * Mock actually has two separate caches that could be handled separately:
> *# The yum cache - Caches package that are installed in the chroot
> *# The root cache - Keeps an archive of the whole chroot
> * We can make the yum cache shared by all the chroots that use the same repos
> * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file:
> ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}}
> ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}}
> * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer:
> ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}}
> * We can use a different compression algorithm for the chroot acche, this may yield better performance.
> * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years
[JIRA] (OVIRT-983) Improve CI output for Jenkins repo
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira... ]
Barak Korren updated OVIRT-983:
-------------------------------
Component/s: Standard CI (Pipelines)
> Improve CI output for Jenkins repo
> ----------------------------------
>
> Key: OVIRT-983
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI, Standard CI (Pipelines)
> Reporter: Barak Korren
> Assignee: infra
>
> Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch.
> The following improvements should be made to the job output:
> # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin.
> # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?)
> # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page.
> # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years
[JIRA] (OVIRT-983) Improve CI output for Jenkins repo
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira... ]
Barak Korren updated OVIRT-983:
-------------------------------
Epic Link: (was: OVIRT-400)
> Improve CI output for Jenkins repo
> ----------------------------------
>
> Key: OVIRT-983
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
>
> Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch.
> The following improvements should be made to the job output:
> # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin.
> # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?)
> # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page.
> # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years
[JIRA] (OVIRT-983) Improve CI output for Jenkins repo
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira... ]
Barak Korren updated OVIRT-983:
-------------------------------
Epic Link: (was: OVIRT-400)
> Improve CI output for Jenkins repo
> ----------------------------------
>
> Key: OVIRT-983
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
>
> Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch.
> The following improvements should be made to the job output:
> # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin.
> # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?)
> # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page.
> # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years
[JIRA] (OVIRT-1135) consider changing the welcoming message in
Jenkins.ovirt.org to something more meaningful
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1135?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1135:
--------------------------------
Epic Link: (was: OVIRT-400)
> consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful
> ------------------------------------------------------------------------------------------
>
> Key: OVIRT-1135
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins Master
> Reporter: eyal edri
> Assignee: Evgheni Dereveanchin
>
> Thanks,
> I've removed the duplicate message, and opening a ticket on this to
> consider more meaningful links or layout on the main page.
> On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
> > Hi all,
> >
> > If you click the "All" tab, you get double welcome message with
> > similar content.
> > Welcome to oVirt Jenkins continuous integration serverFor more
> > information about the oVirt project visit http://www.ovirt.org
> > Welcome to oVirt Jenkins continuous integration serverFor more info about
> > the oVirt project, visit oVirt.org <http://ovirt.org/>
> > See http://jenkins.ovirt.org/view/All/
> >
> > I think we can remove the welcome message entirely, it makes sense only
> > when
> > you visit http://jenkins.ovirt.org/, and only for unlogged users.
> >
> > Logged users do not need the welcome message, it takes valuable space on
> > the screen that
> > can be used for useful data.
> >
> > Nir
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years
[JIRA] (OVIRT-1135) consider changing the welcoming message in
Jenkins.ovirt.org to something more meaningful
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1135?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1135:
--------------------------------
Epic Link: (was: OVIRT-400)
> consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful
> ------------------------------------------------------------------------------------------
>
> Key: OVIRT-1135
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins Master
> Reporter: eyal edri
> Assignee: Evgheni Dereveanchin
>
> Thanks,
> I've removed the duplicate message, and opening a ticket on this to
> consider more meaningful links or layout on the main page.
> On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
> > Hi all,
> >
> > If you click the "All" tab, you get double welcome message with
> > similar content.
> > Welcome to oVirt Jenkins continuous integration serverFor more
> > information about the oVirt project visit http://www.ovirt.org
> > Welcome to oVirt Jenkins continuous integration serverFor more info about
> > the oVirt project, visit oVirt.org <http://ovirt.org/>
> > See http://jenkins.ovirt.org/view/All/
> >
> > I think we can remove the welcome message entirely, it makes sense only
> > when
> > you visit http://jenkins.ovirt.org/, and only for unlogged users.
> >
> > Logged users do not need the welcome message, it takes valuable space on
> > the screen that
> > can be used for useful data.
> >
> > Nir
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years
[JIRA] (OVIRT-1135) consider changing the welcoming message in
Jenkins.ovirt.org to something more meaningful
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1135?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1135:
--------------------------------
Component/s: Jenkins Master
> consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful
> ------------------------------------------------------------------------------------------
>
> Key: OVIRT-1135
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins Master
> Reporter: eyal edri
> Assignee: Evgheni Dereveanchin
>
> Thanks,
> I've removed the duplicate message, and opening a ticket on this to
> consider more meaningful links or layout on the main page.
> On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
> > Hi all,
> >
> > If you click the "All" tab, you get double welcome message with
> > similar content.
> > Welcome to oVirt Jenkins continuous integration serverFor more
> > information about the oVirt project visit http://www.ovirt.org
> > Welcome to oVirt Jenkins continuous integration serverFor more info about
> > the oVirt project, visit oVirt.org <http://ovirt.org/>
> > See http://jenkins.ovirt.org/view/All/
> >
> > I think we can remove the welcome message entirely, it makes sense only
> > when
> > you visit http://jenkins.ovirt.org/, and only for unlogged users.
> >
> > Logged users do not need the welcome message, it takes valuable space on
> > the screen that
> > can be used for useful data.
> >
> > Nir
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years
[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 updated OVIRT-1154:
--------------------------------
Component/s: Standard CI (Pipelines)
> 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: oVirt CI, Standard CI (Pipelines)
> 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
(v1001.0.0-SNAPSHOT#100087)
6 years