From Fedora Project Wiki
(Example job)
(→‎Current status: updating percentage completed to 100%)
 
(5 intermediate revisions by 2 users not shown)
Line 31: Line 31:
 
== Current status ==
 
== Current status ==
 
* Targeted release: [[Releases/22 | Fedora 22 ]]  
 
* Targeted release: [[Releases/22 | Fedora 22 ]]  
* Last updated: 2015-01-20
+
* Percentage Completed: 100%
 +
* Last updated: 2015-02-24
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
 
Bugzilla states meaning as usual:
 
Bugzilla states meaning as usual:
Line 40: Line 41:
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
-->
 
-->
* Tracker bug: <will be assigned by the Wrangler>
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1191545 #1191545]
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 56: Line 57:
  
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
  
Line 62: Line 62:
 
    
 
    
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
 
== Scope ==
 
== Scope ==
* Proposal owners: kushaldas@gmail.com
+
* Proposal owners: kushaldas@gmail.com to work on tunir
 
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
Line 129: Line 128:
  
 
http://tunir.rtfd.org
 
http://tunir.rtfd.org
 
  
 
== Release Notes ==
 
== Release Notes ==
Line 137: Line 135:
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
 
-->
 
-->
 
+
[[Category:ChangeAcceptedF22]]
[[Category:ChangePageIncomplete]]
 
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 13:31, 24 February 2015


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

Documentation

http://tunir.rtfd.org

Release Notes