(→Tools) |
(Add team information) |
||
| (19 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| + | = MINT = | ||
| + | MINT (MeeGo Integration) is a set of integrated tools, that was created with the goal of creating a CI system around OBS for enabling vendors to build meego products. | ||
| + | It provides a business process automation system, interacting with many different systems such as bugzilla and OBS to facilitate product building. | ||
| + | |||
== Overview == | == Overview == | ||
| - | + | * MINT (MeeGo Integration) is a platform composed of integrated tools, that was created with the goal of creating a CI system around OBS for enabling vendors to build meego products. | |
| + | * MINT provides a business process automation system, interacting with many different systems such as bugzilla and OBS to facilitate product building. | ||
| + | * MINT is a platform not a product, delivering a base to build a CI infrastructure to suit each customer's need. | ||
| + | * MINT out-of-the-box provides an end-to-end build and release infrastructure for making linux based products. | ||
| + | * Different deployments may have additional systems and MINT is designed to allow components to be replaced or added to fulfill different needs. | ||
| + | |||
| + | === Features === | ||
| + | * Covers all the activities involved in continuous integration | ||
| + | ** Building through integration with OBS (http://en.opensuse.org//Portal:Build_Service) | ||
| + | ** publishing and notifictaions | ||
| + | ** Creation of installable/flashable images | ||
| + | ** On-device Testing, through integration with OTS (http://wiki.meego.com/Quality/QA-tools/OTS/About) | ||
| + | ** Error and feature management, through bugzilla integration (www.bugzilla.org) | ||
| + | ** Reporting on releases progress | ||
| + | * Distributed architecture means no single point of failure and better resource management | ||
| + | * Massive parallelism, all the components of the system run multiple parallel jobs serving several parallel workflows | ||
| + | * Parallel workflows, means you can run many different workflows servicing multiple products | ||
| + | * Simple workflow description language | ||
| + | * Reliable | ||
| + | ** based on mature, production level opensource projects | ||
| + | ** Reliable messaging using the AMQP standard, means no events will be lost | ||
| + | ** Workflow management based on ruote, an enterprise grade workflow engine | ||
| + | * Robust | ||
| + | ** Live migration of workflows, means you don't need to bring your system down for changing your workflow. Simply deploy your workflow and it gets loaded without disruption to currently running jobs | ||
| + | * Extensible. The system has a minimal core and all operations and functions are implemented as plugins ([[/BOSS/Participants|Participants]]) | ||
| + | |||
| + | == Architecture == | ||
| + | how does it all fit together | ||
| + | |||
| + | == Deployment == | ||
| + | === Joining the Team === | ||
| + | MINT is a set of open source tools and if you use it you should consider yourself a part of the team. | ||
| + | |||
| + | The primary communication tools are irc (#meego) and email (http://lists.meego.com/listinfo/meego-distribution-tools) | ||
| + | |||
| + | There are no bug components in bugzilla yet. | ||
| + | |||
| + | It's important to learn how to influence the project in order to get the best out of it and this is primarily done through participation | ||
| + | on the mailing list and in irc. The mailing list is also used for mutual support, to report security issues and discuss bugs. | ||
| + | |||
| + | === Planning === | ||
| + | * decide on a process, write it | ||
| + | * identify needed participants | ||
| + | === Installation === | ||
| + | === Configuration === | ||
== Tools == | == Tools == | ||
* [[/BOSS|Build Orchestration BOSS]] | * [[/BOSS|Build Orchestration BOSS]] | ||
| + | ** [[/BOSS_Launcher|Launcher documentation]] | ||
| + | ** [[/BOSS_Process|Process documentation]] | ||
| + | ** [[/BOSS_Testing|Testing]] | ||
| + | ** [[/BOSS/Standard_workflow|standard workflow]] | ||
* [[/REVS|Release reporting REVS]] | * [[/REVS|Release reporting REVS]] | ||
* [[/IMG|Image Creation IMG]] | * [[/IMG|Image Creation IMG]] | ||
| - | |||
| - | |||
| - | |||
* [[/BOSS_Participant|Participant documentation]] | * [[/BOSS_Participant|Participant documentation]] | ||
| - | * [[/ | + | * [[/BOSS/Participants|Participants]] |
| - | * [[/ | + | * [[/SKYNET|Skynet]] |
| + | |||
| + | == [[/Packaging|Release team packaging information]] == | ||
| + | |||
| + | == misc. == | ||
| + | * [[/devroot|devroot]] | ||
| + | * [[/BOSS/Installation|BOSS and Skynet]] | ||
Contents |
MINT (MeeGo Integration) is a set of integrated tools, that was created with the goal of creating a CI system around OBS for enabling vendors to build meego products. It provides a business process automation system, interacting with many different systems such as bugzilla and OBS to facilitate product building.
how does it all fit together
MINT is a set of open source tools and if you use it you should consider yourself a part of the team.
The primary communication tools are irc (#meego) and email (http://lists.meego.com/listinfo/meego-distribution-tools)
There are no bug components in bugzilla yet.
It's important to learn how to influence the project in order to get the best out of it and this is primarily done through participation on the mailing list and in irc. The mailing list is also used for mutual support, to report security issues and discuss bugs.