releng
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
releng [2015/07/15 09:39] Fatih Degirmenci create releng project page |
releng [2016/02/16 14:52] (current) Fatih Degirmenci |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Project: Release Engineering ===== | + | ====== Project: Release Engineering ====== |
| - | ==== Introduction ==== | + | ===== Introduction ===== |
| The Release Engineering project provides automation, tooling and software infrastructure support for OPNFV projects to achieve E2E automation in order to make sure all repeating/day to day activities are run in automated fashion, the tools community relies on is up and running at all times, and release related activities are handled properly. | The Release Engineering project provides automation, tooling and software infrastructure support for OPNFV projects to achieve E2E automation in order to make sure all repeating/day to day activities are run in automated fashion, the tools community relies on is up and running at all times, and release related activities are handled properly. | ||
| Line 8: | Line 8: | ||
| The scope of Release Engineering project includes | The scope of Release Engineering project includes | ||
| - | * collecting requirements from all OPNFV projects and analyze them | + | * collecting requirements from all OPNFV projects regarding automation and tooling, analyzes, and realizes them |
| - | * putting requirements on all OPNFV projects to make sure solutions are common to all | + | * putting requirements on all OPNFV projects to make sure solutions are as common as possible to all projects |
| - | * creating scripts | + | * creating scripts and Jenkins jobs in order to automate what can be automated |
| - | * creating and deploying corresponding Jenkins jobs | + | * evaluating and setting up, and maintaining the tools that are needed by the community |
| - | * evaluating and setting up the tools that are needed | + | |
| * providing software infrastructure support with regards to tools, scripts, and Jenkins jobs | * providing software infrastructure support with regards to tools, scripts, and Jenkins jobs | ||
| - | * guiding OPNFV community with Release Engineering specific, automation tasks | + | * guiding OPNFV community with automation tasks |
| * providing documentation | * providing documentation | ||
| Please see the [[releng:release_engineering_project_proposal|Release Engineering Project Proposal]] for more details. | Please see the [[releng:release_engineering_project_proposal|Release Engineering Project Proposal]] for more details. | ||
| - | ==== Meetings ==== | + | ===== Meetings ===== |
| - | Release Engineering project team is in the process of deciding when to have team meetings and with what means. The information on this page will be updated and the meeting schedule and IRC channel details will be available here. | + | Releng project does not have standing meetings. All the committers and contributors can be reached via IRC on different OPNFV channels. |
| - | Until the details are settled, please join the IRC channel **''#opnfv-octopus''**@**''Freenode''** if you need help and have discussions. | + | ===== Way of Working ===== |
| - | ==== Way of Working ==== | + | A survey within Releng Team has been held in order to get input regarding the team logistics/WoW. The logistics/WoW is decided as below in order to keep things simple to start with. |
| - | Release Engineering project team is in the process of deciding how to work in good way when it comes to keeping the backlog, reviewing and submitting changes and so on. The information on this page will be updated once the team decides the way forward. | + | * A change to releng repo must have at least one +2 from any committer but the owner before it can be submitted to master. |
| + | * A change to releng repo can be submitted whenever it fulfils the submit rule above. | ||
| + | * Releng Team holds weekly team meetings every Monday, 14:00-15:00 UTC. | ||
| + | * Releng Team uses #opnfv-octopus@Freenode chatroom for day to day communication/collaboration. | ||
| - | ==== Key Project Facts ==== | + | Please see the survey results from [[https://www.surveymonkey.com/results/SM-RVY9SFFY/|this link]]. |
| + | |||
| + | ===== Contributions to OpenStack ===== | ||
| + | |||
| + | Releng Project has been contributing to OpenStack Infra in order to patch missing functionality and use it in OPNFV. | ||
| + | |||
| + | Please see the details and accepted/merged commits on below table. | ||
| + | |||
| + | ^ Component ^ Subject ^ Is in use by OPNFV? | | ||
| + | | Jenkins Job Builder | [[https://review.openstack.org/#/c/202056/| Add support for forbidden file paths in gerrit trigger]] | Yes | | ||
| + | | Jenkins Job Builder | [[https://review.openstack.org/#/c/202180/| Validate and set compare types in gerrit trigger]] | Yes | | ||
| + | | Jenkins Job Builder | [[https://review.openstack.org/#/c/192397/| Add Google Cloud Storage Plugin support]] | No | | ||
| + | | Jenkins Job Builder | [[https://review.openstack.org/#/c/192720/| Add Disable Failed Job Plugin support]] | No | | ||
| + | | Jenkins Job Builder | [[https://review.openstack.org/#/c/163149/| Pass through git revision to triggered jobs]] | Yes | | ||
| + | |||
| + | |||
| + | |||
| + | ===== Key Project Facts ===== | ||
| {{scrape>https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob_plain;f=INFO;}} | {{scrape>https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob_plain;f=INFO;}} | ||
releng.1436953166.txt.gz · Last modified: 2015/07/15 09:39 by Fatih Degirmenci
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
