NextERP/runbot
5
0
Fork 0
mirror of https://github.com/odoo/runbot.git synced 2025-03-21 10:25:44 +07:00
Code Issues Actions Packages Projects Releases Wiki Activity
9684c2d97e
runbot/runbot/__manifest__.py

41 lines
1.2 KiB
Python
Raw Normal View History

[REF] runbot, runbot_cla: upgrade to Odoo 11.0 The previous code of runbot and runbot_cla was made for Odoo API version 8.0. This commit makes it work with Odoo API 11.0 and Python 3. Also, the present refactoring splits the code into multiple files to make it easier to read (I hope). The main change due to Python 3 is the job locking mechanism: Since PEP-446 file descriptors are non-inheritable by default. A new method (os.set_inheritable) was introduced to explicitely make fd inheritable. Also, the close_fds parameter of the subprocess.Popen method is now True by default. Finally, PEP-3151 changed the exception raised by fcntl.flock from IOError to OSError (and IOError became an alias of OSError). As a consequence of all that, the runbot locking mechanism to check if a job is finished was not working in python3.
2018-02-28 16:31:05 +07:00
# -*- coding: utf-8 -*-
{
'name': "runbot",
'summary': "Runbot",
'description': "Runbot for Odoo 11.0",
'author': "Odoo SA",
'website': "http://runbot.odoo.com",
'category': 'Website',
[IMP] runbot: add a build stat model When a build is done, various numerical informations could be extracted from log files. e.g.: global query count or tests query count ... The extraction regular expression could be hard-coded in a custom step but there is no place holder where to store the retrieved information. In order to compare results, we need to store it. With this commit, a new model `runbot.build.stat` is used to store key/values pair linked to a build/config_step. That way, extracted values can be stored. Also, another `runbot.build.stat.regex` is used to store regular expressions that can be used to grep log files and extract values. The regular expression must contain a named group like this: `(?P<value>.+)` The text catched by this group MUST be castable into a float. Optionally, another named group can be used in the regular expresion like this: `(?P<key>.+)` This `key` group will then be used to augment the key name in the database. Example: Consider a log line like this one: `odoo.addons.website_blog.tests.test_ui tested in 10.35s` A regular expression like this, named `test_duration`: `odoo.addons.(?P<key>.+) tested in (?P<value>\d+\.\d+)s` Should store the following key:value: `{ 'key': 'test_duration.website_blog.tests.test_ui', 'value': 10.35 }` A `generic` boolean field is present on the build.stat.regex object, meaning that when no regex are linked to a make_stats config step, then, all the generic regex will be applied. A wizard is added to help the creation the regular expressions, allowing to test if they work against a user provided example. A _make_stats method is added to the ConfigStep model which is called during the _schedule of a build, just before calling the next step. The regex search is only apllied in steps that have the `make_stats` boolean field set to true. Also, the build branch have to be flagged `make_stats` too or the build can have a key `make_stats` in its config_data field. The `make_stats` field on the branch is a compute stored field. That way, sticky branches are automaticaly set `make_stats' true. Finally, an SQL view is used to facilitate the stats visualisation.
2020-03-05 23:35:50 +07:00
'version': '4.10',
[REF] runbot, runbot_cla: upgrade to Odoo 11.0 The previous code of runbot and runbot_cla was made for Odoo API version 8.0. This commit makes it work with Odoo API 11.0 and Python 3. Also, the present refactoring splits the code into multiple files to make it easier to read (I hope). The main change due to Python 3 is the job locking mechanism: Since PEP-446 file descriptors are non-inheritable by default. A new method (os.set_inheritable) was introduced to explicitely make fd inheritable. Also, the close_fds parameter of the subprocess.Popen method is now True by default. Finally, PEP-3151 changed the exception raised by fcntl.flock from IOError to OSError (and IOError became an alias of OSError). As a consequence of all that, the runbot locking mechanism to check if a job is finished was not working in python3.
2018-02-28 16:31:05 +07:00
'depends': ['website', 'base'],
'data': [
'security/runbot_security.xml',
'security/ir.model.access.csv',
'security/ir.rule.csv',
[IMP] runbot: replace jobs by build configs This commit aims to replace static jobs by fully configurable build config. Each build has a config (custom or inherited from repo or branch). Each config has a list of steps. For now, a step can test/run odoo or create a new child build. A python job is also available. The mimic the previous behaviour of runbot, a default config is available with three steps, an install of base, an install+test of all modules, and a last step for run. Multibuilds are replace by a config containing cretaion steps. The created builds are not displayed in main views, but are available on parent build log page. The result of a parent takes the result of all children into account. This new mechanics will help to create some custom behaviours for specifics use cases, and latter help to parallelise work.
2019-04-22 20:49:33 +07:00
'views/assets.xml',
[REF] runbot, runbot_cla: upgrade to Odoo 11.0 The previous code of runbot and runbot_cla was made for Odoo API version 8.0. This commit makes it work with Odoo API 11.0 and Python 3. Also, the present refactoring splits the code into multiple files to make it easier to read (I hope). The main change due to Python 3 is the job locking mechanism: Since PEP-446 file descriptors are non-inheritable by default. A new method (os.set_inheritable) was introduced to explicitely make fd inheritable. Also, the close_fds parameter of the subprocess.Popen method is now True by default. Finally, PEP-3151 changed the exception raised by fcntl.flock from IOError to OSError (and IOError became an alias of OSError). As a consequence of all that, the runbot locking mechanism to check if a job is finished was not working in python3.
2018-02-28 16:31:05 +07:00
'views/repo_views.xml',
'views/branch_views.xml',
'views/build_views.xml',
[WIP] runbot: monitoring tools Add a new model runbot.host to keep info and configuration about hosts (worker servers), like number of worker, reserved or not, ping times (last start loop, successful iteration, end loop, ...) and also last errors, number of testing per host, psql connection count, ... A new monitoring frontend page is created, similar to glances but with additionnal information like hosts states and last_monitored builds (for nightly) Later this model will be used for runbot_build host instead of char. Host are automaticaly created when running _scheduler.
2019-08-19 21:03:14 +07:00
'views/host_views.xml',
[IMP] runbot: add build_error model With this commit, a new RunbotBuilError model is added in order to classify and manage errors that appears during runbot builds. This is an helper to find undeterministic bugs in Odoo builds. Build logs can be parsed on demand, during the parsing, the logs are cleaned with some regexes stored on the RunbotErrorRegex model. A hash is computed on the cleaned log, if a build error already exists with the same fingerprint, the build is appended on the build error. Errors can also be manually linked together with a parent/children relation in case of a related error log. e.g. the error message is different in two different branches but the bug is the same. Also, a new build_url field is added to the runbot_build in order to access the build web page from the backend.
2019-06-27 22:32:00 +07:00
'views/build_error_views.xml',
[IMP] runbot: add an error log model based on a SQL view With this commit, a new model is introduced to facilitate the tracking of the build errors. Its based on an SQL view (Thanks @Xavier-Do), that way, there is no new table in DB and this view is also useful from the PSQL CLI. In the UI, the search for errors easier than manipulate the ir_logging view because the builds informations can be used in search and filters.
2019-08-28 19:58:17 +07:00
'views/error_log_views.xml',
[IMP] runbot: replace jobs by build configs This commit aims to replace static jobs by fully configurable build config. Each build has a config (custom or inherited from repo or branch). Each config has a list of steps. For now, a step can test/run odoo or create a new child build. A python job is also available. The mimic the previous behaviour of runbot, a default config is available with three steps, an install of base, an install+test of all modules, and a last step for run. Multibuilds are replace by a config containing cretaion steps. The created builds are not displayed in main views, but are available on parent build log page. The result of a parent takes the result of all children into account. This new mechanics will help to create some custom behaviours for specifics use cases, and latter help to parallelise work.
2019-04-22 20:49:33 +07:00
'views/config_views.xml',
[REF] runbot, runbot_cla: upgrade to Odoo 11.0 The previous code of runbot and runbot_cla was made for Odoo API version 8.0. This commit makes it work with Odoo API 11.0 and Python 3. Also, the present refactoring splits the code into multiple files to make it easier to read (I hope). The main change due to Python 3 is the job locking mechanism: Since PEP-446 file descriptors are non-inheritable by default. A new method (os.set_inheritable) was introduced to explicitely make fd inheritable. Also, the close_fds parameter of the subprocess.Popen method is now True by default. Finally, PEP-3151 changed the exception raised by fcntl.flock from IOError to OSError (and IOError became an alias of OSError). As a consequence of all that, the runbot locking mechanism to check if a job is finished was not working in python3.
2018-02-28 16:31:05 +07:00
'views/res_config_settings_views.xml',
[IMP] runbot: add a build stat model When a build is done, various numerical informations could be extracted from log files. e.g.: global query count or tests query count ... The extraction regular expression could be hard-coded in a custom step but there is no place holder where to store the retrieved information. In order to compare results, we need to store it. With this commit, a new model `runbot.build.stat` is used to store key/values pair linked to a build/config_step. That way, extracted values can be stored. Also, another `runbot.build.stat.regex` is used to store regular expressions that can be used to grep log files and extract values. The regular expression must contain a named group like this: `(?P<value>.+)` The text catched by this group MUST be castable into a float. Optionally, another named group can be used in the regular expresion like this: `(?P<key>.+)` This `key` group will then be used to augment the key name in the database. Example: Consider a log line like this one: `odoo.addons.website_blog.tests.test_ui tested in 10.35s` A regular expression like this, named `test_duration`: `odoo.addons.(?P<key>.+) tested in (?P<value>\d+\.\d+)s` Should store the following key:value: `{ 'key': 'test_duration.website_blog.tests.test_ui', 'value': 10.35 }` A `generic` boolean field is present on the build.stat.regex object, meaning that when no regex are linked to a make_stats config step, then, all the generic regex will be applied. A wizard is added to help the creation the regular expressions, allowing to test if they work against a user provided example. A _make_stats method is added to the ConfigStep model which is called during the _schedule of a build, just before calling the next step. The regex search is only apllied in steps that have the `make_stats` boolean field set to true. Also, the build branch have to be flagged `make_stats` too or the build can have a key `make_stats` in its config_data field. The `make_stats` field on the branch is a compute stored field. That way, sticky branches are automaticaly set `make_stats' true. Finally, an SQL view is used to facilitate the stats visualisation.
2020-03-05 23:35:50 +07:00
'views/stat_views.xml',
[IMP] runbot: add a multibuild wizard Creating multi builds configs can be tedious. One must create 2 build configs and 2 build config steps in the right order. With this commit, a simple wizard is added that creates those 4 configurations by simply filling 4 fields. Also, a new field, group, is added in order to be able to gather config's and config steps into groups. The group is a Many2one on a config. While at it, the runbot menu has been a bit rearranged with everything about config's in a parent menu named Configs. Config's and config's steps tree views have been enhanced to show the config group and add some filters in the search views.
2019-10-19 18:10:40 +07:00
'wizards/mutli_build_wizard_views.xml',
[IMP] runbot: add a build stat model When a build is done, various numerical informations could be extracted from log files. e.g.: global query count or tests query count ... The extraction regular expression could be hard-coded in a custom step but there is no place holder where to store the retrieved information. In order to compare results, we need to store it. With this commit, a new model `runbot.build.stat` is used to store key/values pair linked to a build/config_step. That way, extracted values can be stored. Also, another `runbot.build.stat.regex` is used to store regular expressions that can be used to grep log files and extract values. The regular expression must contain a named group like this: `(?P<value>.+)` The text catched by this group MUST be castable into a float. Optionally, another named group can be used in the regular expresion like this: `(?P<key>.+)` This `key` group will then be used to augment the key name in the database. Example: Consider a log line like this one: `odoo.addons.website_blog.tests.test_ui tested in 10.35s` A regular expression like this, named `test_duration`: `odoo.addons.(?P<key>.+) tested in (?P<value>\d+\.\d+)s` Should store the following key:value: `{ 'key': 'test_duration.website_blog.tests.test_ui', 'value': 10.35 }` A `generic` boolean field is present on the build.stat.regex object, meaning that when no regex are linked to a make_stats config step, then, all the generic regex will be applied. A wizard is added to help the creation the regular expressions, allowing to test if they work against a user provided example. A _make_stats method is added to the ConfigStep model which is called during the _schedule of a build, just before calling the next step. The regex search is only apllied in steps that have the `make_stats` boolean field set to true. Also, the build branch have to be flagged `make_stats` too or the build can have a key `make_stats` in its config_data field. The `make_stats` field on the branch is a compute stored field. That way, sticky branches are automaticaly set `make_stats' true. Finally, an SQL view is used to facilitate the stats visualisation.
2020-03-05 23:35:50 +07:00
'wizards/stat_regex_wizard_views.xml',
[REF] runbot, runbot_cla: upgrade to Odoo 11.0 The previous code of runbot and runbot_cla was made for Odoo API version 8.0. This commit makes it work with Odoo API 11.0 and Python 3. Also, the present refactoring splits the code into multiple files to make it easier to read (I hope). The main change due to Python 3 is the job locking mechanism: Since PEP-446 file descriptors are non-inheritable by default. A new method (os.set_inheritable) was introduced to explicitely make fd inheritable. Also, the close_fds parameter of the subprocess.Popen method is now True by default. Finally, PEP-3151 changed the exception raised by fcntl.flock from IOError to OSError (and IOError became an alias of OSError). As a consequence of all that, the runbot locking mechanism to check if a job is finished was not working in python3.
2018-02-28 16:31:05 +07:00
'templates/frontend.xml',
'templates/build.xml',
'templates/assets.xml',
[FIX] runbot: add the dasboard view for sticky branches During the runbot migration to Odoo 11.0, the dashboard was lost in Limbo.
2018-03-13 17:15:39 +07:00
'templates/dashboard.xml',
[REF] runbot, runbot_cla: upgrade to Odoo 11.0 The previous code of runbot and runbot_cla was made for Odoo API version 8.0. This commit makes it work with Odoo API 11.0 and Python 3. Also, the present refactoring splits the code into multiple files to make it easier to read (I hope). The main change due to Python 3 is the job locking mechanism: Since PEP-446 file descriptors are non-inheritable by default. A new method (os.set_inheritable) was introduced to explicitely make fd inheritable. Also, the close_fds parameter of the subprocess.Popen method is now True by default. Finally, PEP-3151 changed the exception raised by fcntl.flock from IOError to OSError (and IOError became an alias of OSError). As a consequence of all that, the runbot locking mechanism to check if a job is finished was not working in python3.
2018-02-28 16:31:05 +07:00
'templates/nginx.xml',
[FIX] runbot: resurrect badges
2018-03-14 00:14:15 +07:00
'templates/badge.xml',
[IMP] runbot: add a frontend template for builds by branch The frontend view shows only the four last builds by branch, which is a little bit small to explore builds and search for failed builds. With this commit, a new frontend template displays a paged list of builds for a specified branch. Closes #39
2018-09-21 13:45:30 +07:00
'templates/branch.xml',
[IMP] runbot: replace jobs by build configs This commit aims to replace static jobs by fully configurable build config. Each build has a config (custom or inherited from repo or branch). Each config has a list of steps. For now, a step can test/run odoo or create a new child build. A python job is also available. The mimic the previous behaviour of runbot, a default config is available with three steps, an install of base, an install+test of all modules, and a last step for run. Multibuilds are replace by a config containing cretaion steps. The created builds are not displayed in main views, but are available on parent build log page. The result of a parent takes the result of all children into account. This new mechanics will help to create some custom behaviours for specifics use cases, and latter help to parallelise work.
2019-04-22 20:49:33 +07:00
'data/runbot_build_config_data.xml',
[IMP] runbot: add build_error model With this commit, a new RunbotBuilError model is added in order to classify and manage errors that appears during runbot builds. This is an helper to find undeterministic bugs in Odoo builds. Build logs can be parsed on demand, during the parsing, the logs are cleaned with some regexes stored on the RunbotErrorRegex model. A hash is computed on the cleaned log, if a build error already exists with the same fingerprint, the build is appended on the build error. Errors can also be manually linked together with a parent/children relation in case of a related error log. e.g. the error message is different in two different branches but the bug is the same. Also, a new build_url field is added to the runbot_build in order to access the build web page from the backend.
2019-06-27 22:32:00 +07:00
'data/build_parse.xml',
'data/runbot_error_regex_data.xml',
'data/error_link.xml',
[IMP] runbot: simplify views and adapt to odoo13 mainly fixes datetime and bootstrap layouts
2020-01-10 17:54:29 +07:00
'data/website_data.xml',
[REF] runbot, runbot_cla: upgrade to Odoo 11.0 The previous code of runbot and runbot_cla was made for Odoo API version 8.0. This commit makes it work with Odoo API 11.0 and Python 3. Also, the present refactoring splits the code into multiple files to make it easier to read (I hope). The main change due to Python 3 is the job locking mechanism: Since PEP-446 file descriptors are non-inheritable by default. A new method (os.set_inheritable) was introduced to explicitely make fd inheritable. Also, the close_fds parameter of the subprocess.Popen method is now True by default. Finally, PEP-3151 changed the exception raised by fcntl.flock from IOError to OSError (and IOError became an alias of OSError). As a consequence of all that, the runbot locking mechanism to check if a job is finished was not working in python3.
2018-02-28 16:31:05 +07:00
],
}
Reference in New Issue Copy Permalink