Tunir
Summary
Tunir is a self contained CI Continuous Integration which will be used to test Fedora Cloud images nightly. This tool can be used separately by any developer in their Fedora 21 system to run/test their local tests/jobs.
Owner
- Name: Kushal Das
- Email: kushaldas@gmail.com
- Release notes owner:
Current status
- Targeted release: Fedora 22
- Percentage Completed: 100%
- Last updated: 2015-02-24
- Tracker bug: #1191545
Detailed Description
Tunir is a very simple CI system written keeping Fedora Cloud images at mind. At the same time it is generic enough to be used by anyone to configure and run jobs/tests in their local system. We will be able to track the status of nightly cloud builds, we can also keep track other changes like, the dependencies pulled in, or the overall size of the images. The same tool can used as a self contained CI system by any Fedora user to run their own tests locally. The tool has a minimal dependency and very simple to configure and maintain.
This tool right now can create vm(s) based on cloud images (without needing an actual cloud), or can run the tests in a bare metal box, or it can even create jobs inside Docker containers.
Example:
$ sudo tunir --job dockerjob --stateless
The above command will run a stateless job named "dockerjob", it will not save the result into any database as it is a stateless run.
Benefit to Fedora
We will be be able to track the changes and run regular tests against nightly and other cloud builds. It will also help any developer to adopt Fedora as a system for development by allowing them to use the same service in their local boxes.
Scope
- Proposal owners: kushaldas@gmail.com to work on tunir
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
Also more information can be found in the project documentation site.
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change)o
- Blocks product? product