From Fedora Project Wiki
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Jenkins =
= Jenkins <!-- The name of your change proposal --> =


[[File:Jenkins_logo.png]]
== Summary ==
Jenkins is an open source continuous integration tool written in Java.


This wiki page shows progress of packaging [http://jenkins-ci.org/ Jenkins] in Fedora.
== Owner ==
<!--
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
This should link to your home wiki page so we know who you are.
-->
* Name: [[User:msrb| Michal Srb]]
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: msrb@redhat.com
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
* Product:
* Responsible WG:
-->


== Tasks ==
== Current status ==
* Targeted release: [[Releases/21 | Fedora 21 ]]
* Last updated: 2014-04-07
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
Bugzilla states meaning as usual:
NEW -> change proposal is submitted and announced
ASSIGNED -> accepted by FESCo with on going development
MODIFIED -> change is substantially done and testable
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)
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>


* create packaging guidelines for Java web applications
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Jenkins provides continuous integration services for software development. It is a server-based system. Builds can be started by various means, including being triggered by commit in a version control system, scheduling via a cron-like mechanism, building when other builds have completed, and by requesting a specific build URL.


* useful link: [https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Repositories list of all Jenkins related GitHub repositories]
== Benefit to Fedora ==
<!-- 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?-->
Users will be given chance to [https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins meet Jenkins] via official Fedora repositories.


* add support for handling .hpi artifacts to javapackages-tools
== Scope ==
** .hpi artifacts are jenkins plugins
<!-- What work do the developers have to accomplish to complete the change 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?-->


* jenkins bundles yui2, javascript library (https://github.com/yui/yui2)
* Proposal owners: All necessary Jenkins dependencies should be already in Fedora. Jenkins needs mainly testing and bugfixing.
<!-- 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?-->


* stapler-adjunct-codemirror, jar containing nothing len javascript
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** how to package this?
<!-- What work do other developers 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?-->


* port maven-hpi-plugin to jetty 9
* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** currently uses jetty 6
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
** low priority, only "run" mojo requires jetty


* stapler-adjunct-timeline bundles some javascript
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** it's simile timeline [http://www.simile-widgets.org/timeline/]
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
*** simile-timeline needs jquery [https://bugzilla.redhat.com/show_bug.cgi?id=857992]


== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->


* rawhide:
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** json-lib needs to be updated to latest master branch
N/A (not a System Wide Change)
*** and this will break gooddata-cl and possibly other packages
*** json-lib in Fedora possibly contains "evil" code from Douglas Crockford (rhbz#1055917)
** jnr-posix needs to by updated to 3.x
*** vondruch prepared update for jruby, but it's not in git yet


== jenkins-core ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.


{| id="current_progress" class="wikitable sortable" border="1"
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
!#
!Package
!Version
!Review request
!Packager
!Comments
!URL
|-
|1
|jenkins-ci-pom
|1.30
|{{result|fail}}
skip
|[[User:Msrb|msrb]]
|unknown license, reported upstream by mizdebsk [https://issues.jenkins-ci.org/browse/JENKINS-17682]
not really needed
|parent POM
URL: [https://github.com/jenkinsci/pom/]
|-
|2
|localizer
|1.15
|[https://bugzilla.redhat.com/show_bug.cgi?id=961398]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/kohsuke/localizer]
|-
|3
|stapler
|1.207
|[https://bugzilla.redhat.com/show_bug.cgi?id=967807]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/stapler/stapler/]
|-
|4
|maven-hpi-plugin
|1.95
|[https://bugzilla.redhat.com/show_bug.cgi?id=967816]{{result|pass}}
|[[User:Msrb|msrb]]
|requires jetty 6 from some reason
|Maven plugin for building Jenkins plugins
URL: [https://github.com/jenkinsci/maven-hpi-plugin]
|-
|5
|tiger-types
|1.4
|[https://bugzilla.redhat.com/show_bug.cgi?id=870997]{{result|pass}}
|[[User:Msrb|msrb]]
|packaged by gil long time ago
|URL: [http://java.net/projects/tiger-types]
|-
|6
|annotation-indexer
|1.4
|[https://bugzilla.redhat.com/show_bug.cgi?id=961392]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/jenkinsci/lib-annotation-indexer/tags]
|-
|7
|metainf-services
|1.4
|[https://bugzilla.redhat.com/show_bug.cgi?id=960532]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/kohsuke/metainf-services/]
|-
|8
|jinterop-proxy
|1.1
|
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/kohsuke/jinterop-proxy]
|-
|9
|memory-monitor
|1.7
|[https://bugzilla.redhat.com/show_bug.cgi?id=961817]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/jenkinsci/extras-memory-monitor]
|-
|10
|commons-jelly:commons-jelly-tags-xml
|
|
|
|
|URL: ?
|-
|11
|access-modifier-annotation
|1.4
|[https://bugzilla.redhat.com/show_bug.cgi?id=961394]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/kohsuke/access-modifier]
|-
|12
|org.springframework:spring-dao
|2.5
|
|
|probably our springframework-tx package,
but Jenkins uses older version (2.5, we have 3.1)
|URL: ?
|-
|13
|libpam4j
|1.7
|[https://bugzilla.redhat.com/show_bug.cgi?id=960533]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/kohsuke/libpam4j]
|-
|14
|woodstox
|3.2.9
|{{result|pass}}
|
|already in fedora, package woodstock-core
(we have newer version, req.:3.2.9, we have:4.1.2
|URL: [http://wiki.fasterxml.com/WoodstoxDownload]
|-
|15
|jbcrypt
|0.3m
|{{result|pass}}
|
|already in fedora
(bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1020651])
|URL: [http://www.mindrot.org/projects/jBCrypt/]
|-
|16
|org.jvnet.hudson:xstream
|1.4.4-jenkins-2
|{{result|pass}}
|
|we already have xstream in fedora
Jenkins uses forked version
|URL: [http://maven.jenkins-ci.org/content/repositories/releases/org/jvnet/hudson/xstream/1.4.4-jenkins-3/]
|-
|17
|org.jvnet.libzfs:libzfs
|0.5
|
|
|solaris specific, we won't need this
|URL: [https://github.com/beobal/java-zfs/tree/master/libzfs]
|-
|18
|org.jenkins-ci:trilead-ssh2
|build214-jenkins-1
|{{result|pass}}
|
|we already have trilead-ssh2,
Jenkins uses patched version
|URL: [https://github.com/jenkinsci/trilead-ssh2]
|-
|19
|windows-remote-command
|1.3
|
|
|looks windows specific, we won't probably need this
|URL: [https://github.com/jenkinsci/lib-windows-remote-command]
|-
|20
|jfree:jcommon
|1.0.12
|{{result|pass}}
|
|already in fedora under different namespace
(org.jfree:jcommon:1.0.18)
|URL: ?
|-
|21
|org.kohsuke:trilead-putty-extension
|1.2
|[https://bugzilla.redhat.com/show_bug.cgi?id=968338]{{result|pass}}
|[[User:Msrb|msrb]]
|not 100% sure if needed, but debian guys have this
and it's really simple package
|URL: [https://github.com/kohsuke/trilead-putty-extension]
|-
|22
|akuma
|1.9
|[https://bugzilla.redhat.com/show_bug.cgi?id=961387]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/kohsuke/akuma]
|-
|23
|commons-jelly:commons-jelly-tags-fmt
|
|
|
|
|URL: ?
|-
|24
|net.java.sezpoz:sezpoz
|1.9
|[https://bugzilla.redhat.com/show_bug.cgi?id=958784]{{result|pass}}
|[[User:Msrb|msrb]]
|needed
|URL: [http://sezpoz.java.net/]
|-
|25
|org.jvnet.hudson:jtidy
|1.0
|{{result|pass}}
|
|jtidy package is already in fedora,
jenkins uses patched version
|URL: [http://repo1.maven.org/maven2/org/jvnet/hudson/jtidy/4aug2000r7-dev-hudson-1/]
|-
|26
|org.kohsuke:asm3
|3.3.1
|{{result|pass}}
|
|this should be only renamed asm3, see [http://kohsuke.org/2012/03/03/potd-package-renamed-asm/]
|URL: ?
|-
|27
|org.jruby.ext.posix:jna-posix
|1.0.3
|{{result|fail}}
replace
|[[User:Msrb|msrb]]
|needed
|URL: [https://kenai.com/projects/jna-posix/]
|-
|28
|org.jenkins-ci:crypto-util
|1.1
|[https://bugzilla.redhat.com/show_bug.cgi?id=961814]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/jenkinsci/lib-crypto-util]
|-
|29
|xmlpull:xmlpull
|1.1.3.8
|{{result|pass}}
|
|xpp3 package in fedora
|URL: [http://www.xmlpull.org/v1/download/]
|-
|30
|org.jenkins-ci:commons-jelly
|1.1-jenkins-20120928
|[https://bugzilla.redhat.com/show_bug.cgi?id=963693]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/jenkinsci/jelly]
|-
|31
|org.kohsuke.jinterop:j-interop
|
|
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/kohsuke/j-interop]
|-
|32
|com.sun.solaris:embedded_su4j
|1.1
|
|
|sounds solaris specific, probably not needed
|URL: [https://github.com/kohsuke/embedded_su4j]
|-
|33
|org.jenkins-ci:jmdns
|3.4.0
|[https://bugzilla.redhat.com/show_bug.cgi?id=958777]{{result|pass}}
|[[User:Msrb|msrb]]
|needed, Jenkins uses patched version
(update: forked on github, but no changes have been made so far)
|URL: [http://jmdns.sourceforge.net/] [https://github.com/jenkinsci/jmdns]
|-
|34
|org.jvnet.winp:winp
|1.6
|
|
|sounds windows specific, not needed
|URL: ?
|-
|35
|org.jenkins-ci:commons-jexl
|2.1.1
|{{result|pass}}
|
|looks like our version works just fine
|URL: ?
|-
|36
|org.jvnet.robust-http-client:robust-http-client
|1.2
|[https://bugzilla.redhat.com/show_bug.cgi?id=960559]{{result|pass}}
|[[User:Msrb|msrb]]
|needed
|URL: [https://github.com/kohsuke/robust-http-client]
|-
|37
|jfree:jfreechart
|1.0.9
|{{result|pass}}
|
|already in fedora under different namespace
(org.jfree:jfreechart:1.0.14)
|URL: ?
|-
|38
|org.jvnet.hudson.dom4j:dom4j
|1.6.1
|{{result|pass}}
|
|patched dom4j used in Jenkins,
required by stapler-jelly, our dom4j doesn't work with it
|URL: [https://github.com/jenkinsci/dom4j]
|-
|39
|org.jvnet.hudson:commons-jelly-tags-define
|
|
|
|
|URL: ?
|-
|40
|org.jenkins-ci.main:cli
|
|
|
|this is artifact from jenkins tarball
|URL: ?
|-
|41
|org.kohsuke:windows-package-checker
|1.1
|
|
|probably not needed
it looks out for windows reserved words in package names
|URL: [https://github.com/jenkinsci/windows-package-checker]
|-
|42
|org.kohsuke:owasp-html-sanitizer
|r88
|[https://bugzilla.redhat.com/show_bug.cgi?id=958139]{{result|pass}}
|[[User:Msrb|msrb]]
|project uses Makefile...
review request: [https://bugzilla.redhat.com/show_bug.cgi?id=958139]
|URL: [http://code.google.com/p/owasp-java-html-sanitizer/] [https://github.com/kohsuke/owasp-java-html-sanitizer]
|-
|43
|org.codehaus.groovy:groovy-all
|1.8.8
|{{result|pass}}
|
|needed, already in fedora
|URL: ?
|-
|44
|org.kohsuke.jinterop:j-interopdeps
|
|
|[[User:Msrb|msrb]]
|part of the j-interop package
|URL: ?
|-
|45
|org.acegisecurity:acegi-security
|
|{{result|fail}}
replace
|
|needed, now called spring-security [[https://bugzilla.redhat.com/show_bug.cgi?id=882477]]
|URL: ?
|-
|46
|org.jenkins-ci.main:remoting
|2.23
|[https://bugzilla.redhat.com/show_bug.cgi?id=963175]{{result|pass}}
|[[User:Msrb|msrb]]
|packaged
|URL: [https://github.com/jenkinsci/remoting]
|-
|47
|org.jenkins-ci:jinterop-wmi
|
|
|
|windows related, not needed
|URL: [https://github.com/jenkinsci/extras-jinterop-wmi]
|-
|48
|org.jenkins-ci:version-number
|1.1
|[https://bugzilla.redhat.com/show_bug.cgi?id=962691]{{result|pass}}
|[[User:Msrb|msrb]]
|needed
|URL: [https://github.com/jenkinsci/lib-version-number/]
|-
|49
|org.kohsuke.stapler:json-lib
|
|
|
|
|URL: [https://github.com/jenkinsci/json-lib]
|-
|50
|com.infradna.tool:bridge-method-annotation
|1.4
|[https://bugzilla.redhat.com/show_bug.cgi?id=969971]{{result|pass}}
|[[User:Msrb|msrb]]
|needed
it's an artifact from bridge-method-injector
|URL: [http://bridge-method-injector.infradna.com/] [https://github.com/infradna/bridge-method-injector]
|-
|51
|org.jvnet.hudson:activation
|
|
|
|
|URL: ?
|-
|52
|org.kohsuke.stapler:stapler-adjunct-zeroclipboard
|1.0.7-2
|
|
|javascript + .swf files (:/)
|URL: [https://github.com/stapler/stapler-adjunct-zeroclipboard]
|-
|53
|org.jvnet.hudson:task-reactor
|1.2
|[https://bugzilla.redhat.com/show_bug.cgi?id=961819]{{result|pass}}
|[[User:Msrb|msrb]]
|needed, we can safely use latest version 1.3
|URL: [https://github.com/jenkinsci/lib-task-reactor]
|-
|54
|findbugs:annotations
|1.3.9
|{{result|pass}}
|
|already in fedora
|URL: ?
|-
|55
|org.jenkins-ci:core-annotation-processors
|
|
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/jenkinsci/core-annotation-processors]
|-
|56
|com.sun.winsw:winsw
|1.10
|
|
|windows specific, not needed
(scope is 'provided' anyway)
|URL: [https://github.com/kohsuke/winsw]
|-
|57
|maven-jellydoc-plugin
|1.5
|
|[[User:Msrb|msrb]]
|not needed
|URL: [https://github.com/kohsuke/maven-jellydoc-plugin]
|-
|58
|maven-stapler-plugin
|1.16
|
|[[User:Msrb|msrb]]
|needed
|URL: [https://github.com/stapler/maven-stapler-plugin]
|-
|59
|stapler-adjunct-timeline
|1.4
|
|
|
|URL: [https://github.com/stapler/stapler-adjunct-timeline]
|-
|60
|stapler-adjunct-codemirror
|1.2
|
|
|
|URL: [https://github.com/stapler/stapler-adjunct-codemirror]
|-
|61
|org.zeroturnaround:jr-sdk
|2.1.1
|
|[[User:Msrb|msrb]]
|needed by stapler-jrebel
update: but it looks like stapler-jrebel is not actually needed
|URL: ?
|-
|62
|kohsuke-pom
|5
|[https://bugzilla.redhat.com/show_bug.cgi?id=960536]{{result|pass}}
|[[User:Msrb|msrb]]
|needed by many projects
|URL: [https://github.com/kohsuke/pom]
|-
|63
|maven-jellydoc-plugin
|1.4
|
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/kohsuke/maven-jellydoc-plugin]
|-
|64
|net.java.dev.textile-j:textile-j
|2.2.864
|
|[[User:Msrb|msrb]]
|
|URL: [https://java.net/projects/textile-j]
|-
|65
|org.jenkins-ci:constant-pool-scanner
|1.2
|[https://bugzilla.redhat.com/show_bug.cgi?id=1003614]{{result|pass}}
|[[User:Msrb|msrb]]
|needed by jenkins-remoting 2.32
|URL: [https://github.com/jenkinsci/constant-pool-scanner]
|-
|66
|org.jenkins-ci:bytecode-compatibility-transformer
|1.3
|[https://bugzilla.redhat.com/show_bug.cgi?id=1013986]{{result|pass}}
|[[User:Msrb|msrb]]
|
|URL: [https://github.com/jenkinsci/bytecode-compatibility-transformer]
|-
|}


== jenkins-war ==
A good "how to test" should answer these four questions:


{| id="current_progress" class="wikitable sortable" border="1"
0. What special hardware / data / etc. is needed (if any)?
!#
1. How do I prepare my system to test this change? What packages
!Package
need to be installed, config files edited, etc.?
!Version
2. What specific actions do I perform to check that the change is
!Review request
working like it's supposed to?
!Packager
3. What are the expected results of those actions?
!Comments
-->
!URL
Install latest "jenkins" package from koji, start the server (systemctl start jenkins.service), open your web browser (http://localhost:8080/jenkins) and try to use it, install plugins, etc.
|-
|1
|org.jenkins-ci:executable-war
|1.28
|
|[[User:Msrb|msrb]]
|done
|
URL: ?
|-
|2
|org.jenkins-ci.main:maven-plugin
|1.529
|
|[[User:Msrb|msrb]]
|
|
URL: ?
|-
|3
|org.jenkins-ci.modules:instance-identity
|1.3
|
|[[User:Msrb|msrb]]
|done
|
URL: ?
|-
|4
|org.jenkins-ci.modules:ssh-cli-auth
|1.2
|
|[[User:Msrb|msrb]]
|done
|
URL: ?
|-
|5
|org.jenkins-ci.modules:slave-installer
|1.2
|
|[[User:Msrb|msrb]]
|done
|
URL: ?
|-
|6
|org.jenkins-ci.modules:windows-slave-installer
|1.3
|
|[[User:Msrb|msrb]]
|do we need this?
|
URL: ?
|-
|7
|org.jenkins-ci.modules:launchd-slave-installer
|1.2
|
|[[User:Msrb|msrb]]
|do we need this?
|
URL: ?
|-
|8
|org.jenkins-ci.modules:upstart-slave-installer
|1.1
|
|[[User:Msrb|msrb]]
|do we need this?
|
URL: ?
|-
|9
|org.jenkins-ci.modules:sshd
|1.5
|
|[[User:Msrb|msrb]]
|port to spring-security
|
URL: ?
|-
|}


== maven-plugin ==
== User Experience ==
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


{| id="current_progress" class="wikitable sortable" border="1"
== Dependencies ==
!#
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
!Package
 
!Version
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
!Review request
N/A (not a System Wide Change)
!Packager
 
!Comments
== Contingency Plan ==
!URL
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
|-
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
|1
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
|org.jenkins-ci.plugins:javadoc
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
|1.0
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
|
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
|[[User:Msrb|msrb]]
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
|done
 
|
== Documentation ==
URL: ?
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->
|-
 
|2
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
|org.jenkins-ci.plugins:mailer
N/A (not a System Wide Change)
|1.5
 
|
== Release Notes ==
|[[User:Msrb|msrb]]
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
|done
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.  
|
 
URL: ?
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
|-
-->
|3
 
|org.jenkins-ci.main.maven:maven-agent
[[Category:ChangePageIncomplete]]
|1.4
<!-- When your change proposal page is completed and ready for review and announcement -->
|
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
|[[User:Msrb|msrb]]
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
|maven 2 support, not needed
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
|
 
URL: ?
<!-- Select proper category, default is Self Contained Change -->
|-
[[Category:SelfContainedChange]]
|4
<!-- [[Category:SystemWideChange]] -->
|org.jenkins-ci.main.maven:maven-interceptor
|1.4
|
|[[User:Msrb|msrb]]
|maven 2 support, not needed
|
URL: ?
|-
|5
|org.jvnet.hudson:maven2.1-interceptor
|1.2
|
|[[User:Msrb|msrb]]
|maven 2 support, not needed
|
URL: ?
|-
|6
|org.jenkins-ci.main.maven:maven3-agent
|1.4
|
|[[User:Msrb|msrb]]
|maven 3.0.x support, not available in Rawhide
|
URL: ?
|-
|7
|org.jenkins-ci.main.maven:maven31-agent
|1.4
|
|[[User:Msrb|msrb]]
|done
|
URL: ?
|-
|8
|org.jenkins-ci.main.maven:maven3-interceptor
|1.4
|
|[[User:Msrb|msrb]]
|maven 3.0.x support, not available in Rawhide
|
URL: ?
|-
|9
|org.jenkins-ci.main.maven:maven31-interceptor
|1.4
|
|[[User:Msrb|msrb]]
|done
|
URL: ?
|-
|10
|org.jenkins-ci.main.maven:maven3-interceptor-commons
|1.4
|
|[[User:Msrb|msrb]]
|done
|
URL: ?
|-
|11
|org.jenkins-ci.lib:lib-jenkins-maven-artifact-manager
|1.2
|
|[[User:Msrb|msrb]]
|skipped
|
URL: ?
|-
|12
|org.jenkins-ci.lib:lib-jenkins-maven-embedder
|3.11
|
|[[User:Msrb|msrb]]
|done
|
URL: ?
|-
|13
|org.jenkins-ci.plugins:token-macro
|1.1
|
|[[User:Msrb|msrb]]
|done
|
URL: ?
|-
|14
|findbugs:annotations
|
|
|[[User:Msrb|msrb]]
|skipped
|
URL: ?
|-
|}

Latest revision as of 11:48, 7 April 2014

Jenkins

Summary

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

Owner

  • Name: Michal Srb
  • Email: msrb@redhat.com
  • Release notes owner:

Current status

  • Targeted release: Fedora 21
  • Last updated: 2014-04-07
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Jenkins provides continuous integration services for software development. It is a server-based system. Builds can be started by various means, including being triggered by commit in a version control system, scheduling via a cron-like mechanism, building when other builds have completed, and by requesting a specific build URL.

Benefit to Fedora

Users will be given chance to meet Jenkins via official Fedora repositories.

Scope

  • Proposal owners: All necessary Jenkins dependencies should be already in Fedora. Jenkins needs mainly testing and bugfixing.
  • 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

Install latest "jenkins" package from koji, start the server (systemctl start jenkins.service), open your web browser (http://localhost:8080/jenkins) and try to use it, install plugins, etc.

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), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes