[JIRA] [template-project] (JENKINS-23204) Template Plugin to be able to import job parameters
Mickael Istria created JENKINS-23204 Template Plugin to be able to import job parameters Issue Type: New Feature Affects Versions: current Assignee: huybrechts Components: template-project Created: 27/May/14 4:28 PM Description: The Template Project Plugin should provide the ability to import Parameters from another (or several others) jobs. Project: Jenkins Priority: Major Reporter: Mickael Istria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15181) Add a reason or comment when disabling a build
Mickael Istria updated JENKINS-15181 Add a reason or comment when disabling a build Change By: Mickael Istria (19/May/14 8:18 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15181) Add a reason or comment when disabling a build
Mickael Istria commented on JENKINS-15181 Add a reason or comment when disabling a build I'm aware of that, and that's currently what we are using. However, I'm not very happy of it. When a job already has a long description, it makes the reason why it's disabled gets somewhere in the long description, it is more difficult to find. Also, the current UI doesn't encourage people to give a reason when they disable jobs whereas sharing why you disable a job is generally quite valuable. Having it a text "Reason" field just after the "Disable Build" radio button would encourage people to share the reason why a build is disabled. On the main job page, we could read things such as "Job is currently disabled. Reason: It's a draft and is currently always failing". So what you suggest works, but it's just a workaround IMHO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17249) Graph does not show all job results (most likely ignoring ignore)
Mickael Istria
created JENKINS-17249
Graph does not show all job results (most likely ignoring ignore)
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Attachments:
buildFlowBug.png
Components:
build-flow
Created:
18/Mar/13 8:12 AM
Description:
Using version 0.8, it looks like the diagram shows less things than what happened.
See build log
ignore(FAILURE) {
Trigger job jbosstools-base_master
jbosstools-base_master #203 completed
// SUCCESS ignored
}
parallel {
parallel {
parallel {
ignore(FAILURE) {
ignore(FAILURE) {
Trigger job jbosstools-forge_master
ignore(FAILURE) {
Trigger job jbosstools-server_master
Trigger job jbosstools-hibernate_master
ignore(FAILURE) {
Trigger job jbosstools-vpe_master
jbosstools-forge_master #271 completed
// SUCCESS ignored
}
jbosstools-vpe_master #308 completed
// SUCCESS ignored
}
ignore(FAILURE) {
Trigger job jbosstools-jst_master
jbosstools-jst_master #330 completed : UNSTABLE
// UNSTABLE ignored
}
jbosstools-hibernate_master #270 completed : FAILURE
// FAILURE ignored
}
ignore(FAILURE) {
Trigger job jbosstools-birt_master
jbosstools-birt_master #411 completed
// SUCCESS ignored
}
}
jbosstools-server_master #227 completed : FAILURE
// FAILURE ignored
}
ignore(FAILURE) {
Trigger job jbosstools-build-sites.aggregate.webtools-site_master
jbosstools-build-sites.aggregate.webtools-site_master #677 completed
// SUCCESS ignored
}
ignore(FAILURE) {
Trigger job jbosstools-openshift_master
jbosstools-openshift_master #321 completed
// SUCCESS ignored
}
ignore(FAILURE) {
Trigger job jbosstools-webservices_master
jbosstools-webservices_master #309 completed
// SUCCESS ignored
}
parallel {
}
}
}
tells result about 9 jobs.
However, the resulting diagram does not show all and seems to end whenever there is a job that is no "SUCCESS"
The diagram shows only results for 6 jobs (for example, it's missing the jbosstools-birt_master)
Project:
Jenkins
Priority:
Major
Reporter:
Mickael Istria
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16486) Links broken when user-defined axis values contain comma
Mickael Istria updated JENKINS-16486 Links broken when user-defined axis values contain comma Change By: Mickael Istria (25/Jan/13 1:28 PM) Description: Linksarebrokenwhenauser-definedaxisvaluescontaincomma.Stepstoreproduce 1. # Creatematrixjob 2. # createuser-definedaxiswithvaluea,bwithoutquotes 3. # Runjob 4. # ClickconfigurationExpected:configurationbuildpageResult:404. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16111) Support properties such as $JOB_NAME in links
Mickael Istria
created JENKINS-16111
Support properties such as $JOB_NAME in links
Issue Type:
New Feature
Affects Versions:
current
Assignee:
Unassigned
Components:
sidebar-link
Created:
12/Dec/12 7:07 PM
Description:
It would be interesting to have the SideBar Link supporting most properties from Hudson environment and Hudson properties plugin.
I have a use case where I'd like to use ${JOB_NAME} but could not find any way to get it (or other syntax) to work.
Project:
Jenkins
Priority:
Major
Reporter:
Mickael Istria
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16010) Plugin consumes too much memory
Mickael Istria
created JENKINS-16010
Plugin consumes too much memory
Issue Type:
Bug
Affects Versions:
current
Assignee:
Ognjen Bubalo
Components:
jacoco
Created:
03/Dec/12 7:17 AM
Description:
Imported from GitHub: https://github.com/jenkinsci/jacoco-plugin/issues/12
Report by Greg Temchenko ("soid" on GitHub)
I broke down my Jenkins trying to use this plugin. It turned out that plugin stores the entire coverage in XML format in build.xml file in jenkins (Unknown macro: {Jenkins} /jobs/Unknown macro: {Project} /builds/Unknown macro: {Build} /build.xml). Boolean values about covered/uncovered lines stored there as XML tags with indentation for readability
booleantrue/boolean
Thus my 600K code coverage .exec bin file consumed more than 700M on the hard disk for the build.xml.
This is a half of the problem. Further Jenkins keeps all builds information including mentioned above build.xml in RAM. That's how I've caught OutOfMemory exceptions in Jenkins and got it broken.
And a comment from Jesse Glick ("jglick")
For what it’s worth Kohsuke I recently did some minor memory usage fixes in the Cobertura plugin, and I experimented with more: https://github.com/jenkinsci/cobertura-plugin/compare/master...trove
This issue makes the plugin forbidden to installation on JBoss Jenkins instance.
Project:
Jenkins
Priority:
Critical
Reporter:
Mickael Istria
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16010) Plugin consumes too much memory
Mickael Istria
updated JENKINS-16010
Plugin consumes too much memory
Change By:
Mickael Istria
(03/Dec/12 7:18 AM)
Description:
ImportedfromGitHub:https://github.com/jenkinsci/jacoco-plugin/issues/12ReportbyGregTemchenko(soidonGitHub){quote}IbrokedownmyJenkinstryingtousethisplugin.ItturnedoutthatpluginstorestheentirecoverageinXMLformatinbuild.xmlfileinjenkins(
{Jenkins}
JENKINS_HOME
/jobs/
{
[
Project
}
]
/builds/
{
[
Build
}
]
/build.xml).Booleanvaluesaboutcovered/uncoveredlinesstoredthereasXMLtagswithindentationforreadability:)booleantrue/booleanThusmy600Kcodecoverage.execbinfileconsumedmorethan700Montheharddiskforthebuild.xml.Thisisahalfoftheproblem.FurtherJenkinskeepsallbuildsinformationincludingmentionedabovebuild.xmlinRAM.ThatshowIvecaughtOutOfMemoryexceptionsinJenkinsandgotitbroken.{quote}AndacommentfromJesseGlick(jglick){quote}Forwhatit’sworthKohsukeIrecentlydidsomeminormemoryusagefixesintheCoberturaplugin,andIexperimentedwithmore:https://github.com/jenkinsci/cobertura-plugin/compare/master...trove{quote}ThisissuemakesthepluginforbiddentoinstallationonJBossJenkinsinstance.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15831) Switch line colors in graph
Mickael Istria created JENKINS-15831 Switch line colors in graph Issue Type: Improvement Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 15/Nov/12 8:23 AM Description: Currently, on coverage trend graph, covered is red and missed is blue. However, on the class views (on both Jacoco Jenkins plugin, Jacoco HTML reports, Sonar...) and in general understanding, red usually means not-covered. So it would be better to switch color on graph, so red would means uncovered and blue would mean covered. Project: Jenkins Priority: Major Reporter: Mickael Istria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15538) Show source highlighting on the whole class
Mickael Istria created JENKINS-15538 Show source highlighting on the whole class Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco Created: 16/Oct/12 4:42 PM Description: When browsing coverage reports in Jenkins, it is not possible to show hightlighting on the whole class. Coverage is only highlighted at method scope. IT would be easier to highlight coverage at the class level rather than at the method level Project: Jenkins Priority: Major Reporter: Mickael Istria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15539) Provide a link to the jacoco.exec
Mickael Istria created JENKINS-15539 Provide a link to the jacoco.exec Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco Created: 16/Oct/12 4:45 PM Description: The most convenient way to work with coverage results is to load them into IDE. EclEmma takes as input the Jacoco.exec files and provides source reports and highlighting directly in Eclipse workspace. It would be nice to provide a link to those jacoco.exec files and to some useful resources on how to consume them efficiently in IDE. Project: Jenkins Priority: Major Reporter: Mickael Istria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14939) Support single jacoco.exec + multiple modules for sources and classes (based on patterns)
Mickael Istria updated JENKINS-14939 Support single jacoco.exec + multiple modules for sources and classes (based on patterns) Made it blocker since it make the plugin not usable in many cases Change By: Mickael Istria (27/Sep/12 9:01 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15338) Sonar plugin can't consume installed Maven runtimes
Mickael Istria created JENKINS-15338 Sonar plugin cant consume installed Maven runtimes Issue Type: Bug Assignee: sonarteam Components: sonar Created: 27/Sep/12 3:07 PM Description: I have a machine where I cannot access "mvn" in path directly. Instead, all Maven build steps have to select an installation of Maven to run against. Maven installations are configured for the whole Jenkins. Sonar plugin should follow the same principle and ask user for a Maven installaiton to use, instead of assuming it can use a "mvn" from PATH. Project: Jenkins Priority: Blocker Reporter: Mickael Istria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15338) Sonar plugin can't consume installed Maven runtimes
Mickael Istria commented on JENKINS-15338 Sonar plugin cant consume installed Maven runtimes Some background: failing job https://hudson.eclipse.org/sandbox/job/SWTBot-Sonar/3/console workspace $ mvn -f /opt/users/hudsonbuild/.hudson/jobs/SWTBot-Sonar/workspace/pom.xml -e -B sonar:sonar -Dmaven.repo.local=$WORKSPACE/.maven/repo -Dsonar.host.url="" href="http://dev.eclipse.org/sonar">http://dev.eclipse.org/sonar FATAL: command execution failed java.io.IOException: Cannot run program "mvn" (in directory "/opt/users/hudsonbuild/.hudson/jobs/SWTBot-Sonar/workspace"): java.io.IOException: error=13, Permission denied This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14274) Multi module reporting
Mickael Istria commented on JENKINS-14274 Multi module reporting I have the following layout after I build my project: *sources/ **plugins/ ***pluginA/ ***pluginB/ **tests/ ***testA/ ***testB/ **target/ ***jacoco.exec ***coverage-report/ coverage-report.xml html/... HTML reports show me everything I need: percentages, highlighted sources from classes from all my modules. Reports contains aggregated report for all tests, and relies on classes from all modules. The Jacoco Jenkins plugin only show me "all classes", I cannot drill dows as I can do with HTML reports. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14274) Multi module reporting
Mickael Istria edited a comment on JENKINS-14274 Multi module reporting I have the following layout after I build my project: sources/ plugins/ pluginA/ pluginB/ tests/ testA/ testB/ target/ jacoco.exec coverage-report/ coverage-report.xml html/... HTML reports show me everything I need: percentages, highlighted sources from classes from all my modules. Reports contains aggregated report for all tests, and relies on classes from all modules. The Jacoco Jenkins plugin only show me "all classes", I cannot drill dows as I can do with HTML reports. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14274) Multi module reporting
Mickael Istria updated JENKINS-14274 Multi module reporting Change By: Mickael Istria (16/Aug/12 2:54 PM) Attachment: reports.jpeg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14274) Multi module reporting
Mickael Istria commented on JENKINS-14274 Multi module reporting As you know the Jenkins Jacoco plugin still doesn't support "Multi module reporting" That's indeed the topic of this report. I'm just detailing my use-case here, to ensure it gets covered by the fix. using "jacoco:report" will create you only the last module. Sure, I know this issue: http://sourceforge.net/tracker/?func=detailaid=3474708group_id=177969atid=883354 If I understand you correctly, you tried to create one exec file that containing all coverage data from all module project, its good idea but still the jenkins plugin will create report only for the last module. To make it work you must to attach the module classes to the jacoco directory when running jacoco report. Until we have a multi module reporting implemented in Jenkins Jacoco plugin, you can use the following temporary solution using Ant task: http://java.dzone.com/articles/jacoco-maven-multi-module That's what I did. IMy HTML and XML reports, generated with the Jacoco Ant task work just fine, they correctly find classes and sources for all modules I want. So my reports are good, but when passing the XML report to Jacoco Jenkins plugin, it cannot see the classes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14274) Multi module reporting
Mickael Istria updated JENKINS-14274 Multi module reporting Sample config.xml for the project on which one this issue happen. Change By: Mickael Istria (16/Aug/12 3:53 PM) Attachment: config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14279) Report missed items rather that coverage percentage
Mickael Istria created JENKINS-14279 Report missed items rather that coverage percentage Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco Created: 02/Jul/12 3:45 PM Description: Coverage percentage is often a meaningless metric. Instead, or in addition, Jacoco Jenkins plugin should be able to show missed items, as the Jacoco report task does by default. It makes it faster to know which piece of code is not covered and to find places where to focus effort. Project: Jenkins Priority: Major Reporter: Mickael Istria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14279) Report missed items rather that coverage percentage
Mickael Istria commented on JENKINS-14279 Report missed items rather that coverage percentage Original discussion: https://groups.google.com/forum/?fromgroups#!topic/jenkins-jacoco-plugin-mailing-list/016MPoIIr2c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10835) Add support for JaCoCo coverage results
Mickael Istria resolved JENKINS-10835 as Fixed Add support for JaCoCo coverage results @Jose: you should use the jacoco plugin which is already available in version 0.1. See Ognjen's comment for useful links on this topic. Change By: Mickael Istria (29/Jun/12 8:23 AM) Status: Open Resolved Assignee: KohsukeKawaguchi OgnjenBubalo Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10835) Add support for JaCoCo coverage results
Mickael Istria commented on JENKINS-10835 Add support for JaCoCo coverage results Link to Jacoco reports plugin: https://wiki.jenkins-ci.org/display/JENKINS/JaCoCo+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14013) Create a public instance of Jenkins using OpenShift cloud
Mickael Istria commented on JENKINS-14013 Create a public instance of Jenkins using OpenShift cloud You could also ask for build of Jacoco plugin in nemo.sonarsource.org. This service for OSS projects provides you a Jenkins instance @CloudBees + reports in a Sonar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14159) 404 when trying to see coverage on java code
Mickael Istria created JENKINS-14159 404 when trying to see coverage on java code Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 20/Jun/12 10:50 AM Description: I have a maven job that produce fully-functional report files (including showing source code with coverage hightlights in HTML reports). I try to integrate it into Jacoco Jenkins plugin, but I get a 404 when browsing to source code. See https://vimeo.com/44304664 Project: Jenkins Priority: Major Reporter: Mickael Istria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10835) Add support for JaCoCo coverage results
[ https://issues.jenkins-ci.org/browse/JENKINS-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160643#comment-160643 ] Mickael Istria commented on JENKINS-10835: -- EclEmma plugin for Jacoco reports in Eclipse is great. I guess they have a cool API to parse jacoco.exec files and a cleaner way than turning them into Emma reports with XSL. Add support for JaCoCo coverage results --- Key: JENKINS-10835 URL: https://issues.jenkins-ci.org/browse/JENKINS-10835 Project: Jenkins Issue Type: New Feature Components: emma Reporter: Daniel Hirscher Assignee: Kohsuke Kawaguchi Attachments: jacoco_to_emma.xslt JaCoCo is the successor of emma. Maybe it is possible to support the new coverage file format. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10835) Add support for JaCoCo coverage results
[ https://issues.jenkins-ci.org/browse/JENKINS-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160532#comment-160532 ] Mickael Istria commented on JENKINS-10835: -- On a side note, this topic was suggested as a subject for a GSoC by JBoss (Jonathan is the mentor) https://community.jboss.org/wiki/GSoC12Ideas#A_Jenkins_plugin_to_visualize_Jacoco_code_coverage_reports Any help of finding and motivating a student for to work on this in the GSoC context is welcome! Add support for JaCoCo coverage results --- Key: JENKINS-10835 URL: https://issues.jenkins-ci.org/browse/JENKINS-10835 Project: Jenkins Issue Type: New Feature Components: emma Reporter: Daniel Hirscher Assignee: Kohsuke Kawaguchi Attachments: jacoco_to_emma.xslt JaCoCo is the successor of emma. Maybe it is possible to support the new coverage file format. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12815) Add an option to select Build status when no Test is found
Mickael Istria created JENKINS-12815: Summary: Add an option to select Build status when no Test is found Key: JENKINS-12815 URL: https://issues.jenkins-ci.org/browse/JENKINS-12815 Project: Jenkins Issue Type: New Feature Components: junit Affects Versions: current Environment: any Reporter: Mickael Istria Currently, when no test report is found by JUnit report plugin (ie fileset is empty), build fails. In some cases, this behaviour is too constraining and implies stopping a cascade of builds for example, and this is not always the mist convenient behavior for a build stack. This plugin should provide an option to select build status when fileset is empty: * FAILED (Red): current default behaviour * UNSTABLE (Orange) * STABLE (Blue/Green) This is an issue we have to build JBoss Tools, which we had to workaround by adding build steps, or adding dummy files to the fileset to avoid locking all builds in case of test failing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
