Bug 1090891

Summary:	Jenkins
Product:	[Fedora] Fedora	Reporter:	Jaroslav Reznik <jreznik>
Component:	Changes Tracking	Assignee:	Jaroslav Reznik <jreznik>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:	Bara Ancincova <bancinco>
Priority:	unspecified
Version:	rawhide	CC:	mizdebsk, msrb
Target Milestone:	---	Keywords:	Tracking
Target Release:	---	Flags:	bancinco: fedora_requires_release_note+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ChangeAcceptedF21 SelfContainedChange
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	<title>Jenkins</title> <para>The official Fedora repositories now include <application>Jenkins</application>, an application written in Java that provides continuous integration services for software development. <application>Jenkins</application> allows you to build and test software projects continuously, as well as to monitor executions of jobs that were ran externally.</para> <para>For additional information, see the <ulink url="https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins">Meet Jenkins</ulink> webpage.</para>	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-08 15:22:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1096177
Bug Blocks:

Description Jaroslav Reznik 2014-04-24 11:09:11 UTC

This is a tracking bug for Change: Jenkins
For more details, see: http://fedoraproject.org//wiki/Changes/Jenkins

Jenkins is an open source continuous integration tool written in Java.

Comment 1 Jaroslav Reznik 2014-07-04 10:43:39 UTC

This message is a reminder that Fedora 21 Accepted Changes Freeze Deadline is on 2014-07-08 [1].

At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Freeze.

This bug should be set to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon. 

In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you.

[1] https://fedoraproject.org/wiki/Releases/21/Schedule

Comment 2 Bara Ancincova 2014-08-26 19:45:37 UTC

Ahoj Michale, 

could you please take a look at https://fedoraproject.org/wiki/Documentation_Development_Tools_Beat#Jenkins and let me know, if the release note is sufficient or what should I change/add/remove?

Thank you, 

Bara

Comment 3 Michal Srb 2014-09-01 07:38:02 UTC

Ahoj Báro,

Sorry for the late response. I think that the current text is OK, definitely sufficient. Thanks.

Comment 4 Jaroslav Reznik 2014-10-07 12:23:46 UTC

This message is a reminder that Fedora 21 Change Checkpoint: 100% Code Complete Deadline (Former Accepted Changes 100% Complete) is on 2014-10-14 [1].

All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA.

As for several System Wide Changes, Beta Change Deadline is a point of contingency plan. All incompleted Changes will be reported to FESCo on 2014-10-15 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik).

[1] https://fedoraproject.org/wiki/Releases/21/Schedule