date:20150105
















































Oleg Nenashev
 assigned  JENKINS-24857 to Oleg Nenashev



Builds happening because of false-positive SCM changes
















Change By:


Oleg Nenashev
(05/Jan/15 9:06 AM)




Assignee:


Oleg Nenashev



























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] [perforce-plugin] (JENKINS-24857) Builds happening because of false-positive SCM changes















































Oleg Nenashev
 commented on  JENKINS-24857


Builds happening because of false-positive SCM changes















I cannot reproduce the issue.
It would be great if you could provide archives with the two builds (improper triggering + a previous one). Build logs and XML files would be useful.



























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] [subversion-plugin] (JENKINS-24377) Create Tag (Tag this build) Not working

2015-01-05 Thread r...@kamstrup.dk (JIRA)















































Rasmus Pedersen
 commented on  JENKINS-24377


Create Tag (Tag this build) Not working















Realized that the svn authentication depending on the cached of the svn password stored in the user profile.
Does this mean that the username and password you choose for "Credentials for tagging" has no meaning?



























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] [hp-application-automation-tools-plugin] (JENKINS-23314) LR Scenario does not return SLA information in results

2015-01-05 Thread grainne.nichoil...@hp.com (JIRA)















































Grainne Ni Choiligh
 commented on  JENKINS-23314


LR Scenario does not return SLA information in results















I am seeing the same issue. For my case, the fact that Jenkins reports the test as Passed even though Performance Centre correctly shows the SLA as violated is the more critical issue, since we want to fail any builds that cause performance regression.



























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] [email-ext-plugin] (JENKINS-26286) Can not use token (like WARNINGS_NEW) in pre-send script email

2015-01-05 Thread ktou...@free.fr (JIRA)















































Kristel Touron
 created  JENKINS-26286


Can not use token (like WARNINGS_NEW) in pre-send script email















Issue Type:


Improvement



Assignee:


Alex Earl



Components:


email-ext-plugin



Created:


05/Jan/15 9:57 AM



Description:


I try to send an email only if I have new warnings.
I used the email-ext plugin. in the core of the email I can use the token WARNINGS_NEW. but when I try to cancel the email in the pre-send script if WARNINGS_NEW = 0 it does not recognize the token.




Project:


Jenkins



Priority:


Minor



Reporter:


Kristel Touron

























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-26287) lonk tasknames in console-outline overlap console output

2015-01-05 Thread roman.pi...@fluidtime.com (JIRA)















































Roman Pickl
 created  JENKINS-26287


lonk tasknames in console-outline overlap console output















Issue Type:


Bug



Assignee:


Gregory Boissinot



Attachments:


console-outline.png



Components:


core, gradle-plugin



Created:


05/Jan/15 9:57 AM



Description:


the console-outline table overlaps the console output in case of long tasknames.
Any Ideas to improve the UI?




Environment:


Jenkins ver. 1.580.1




Project:


Jenkins



Labels:


user-experience
UI,




Priority:


Minor



Reporter:


Roman Pickl

























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-26287) long tasknames in console-outline overlap console output

2015-01-05 Thread roman.pi...@fluidtime.com (JIRA)















































Roman Pickl
 updated  JENKINS-26287


long tasknames in console-outline overlap console output
















Change By:


Roman Pickl
(05/Jan/15 9:59 AM)




Summary:


lonk
long
 tasknames in console-outline overlap console output



























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] [envinject-plugin] (JENKINS-22126) envinject overrides build parameters with node environment

2015-01-05 Thread nicolas.del...@gmail.com (JIRA)
















































Nicolas De Loof
 resolved  JENKINS-22126 as Fixed


envinject overrides build parameters with node environment
















Change By:


Nicolas De Loof
(05/Jan/15 10:08 AM)




Status:


Open
Resolved





Assignee:


Gregory Boissinot
Nicolas De Loof





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







-- 
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-19513) Jenkins should reconnect to a node after ChannelClosedException

2015-01-05 Thread j...@langevin.me (JIRA)















































Jonathan Langevin
 commented on  JENKINS-19513


Jenkins should reconnect to a node after ChannelClosedException















Same problem for me, using EC2 slaves 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







-- 
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-4501) WorkspaceCleanupThread deletes Matrix project workspaces

2015-01-05 Thread i...@torstenreinhard.de (JIRA)















































Torsten Reinhard
 reopened  JENKINS-4501


WorkspaceCleanupThread deletes Matrix project workspaces
















I have the same issue on 

	Jenkins ver. 1.569
	Tomcat7



all my workspaces on a slave have been deleted:

(updating existing workspace as expected )

04.01.2015 01:23:20 Building remotely on machine-02 in workspace /path/to/jenkins-slave/workspace/DevOps-vagrant-up-paybackce-matrix-test1-CI/label/machine-02/vb_name/test1-cae-extint-1
04.01.2015 01:23:21 Updating http:///vagrant/trunk at revision '2015-01-04T01:22:00.296 +0100'


WorkspaceCleanupThread was executed 

Jan 04, 2015 12:47:27 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Workspace clean-up
Jan 04, 2015 12:47:30 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Workspace clean-up. 3,457 ms
Jan 04, 2015 12:57:16 PM hudson.model.Run execute


(checking out new workspace - unexpected and leads to errors)

05.01.2015 01:22:22 Building remotely on machine-02 in workspace /path/to/jenkins-slave/workspace/DevOps-vagrant-up-paybackce-matrix-test1-CI/label/machine-02/vb_name/test1-cae-extint-1
05.01.2015 01:22:23 Checking out a fresh workspace because there's no workspace at /path/to/jenkins-slave/workspace/DevOps-vagrant-up-paybackce-matrix-test1-CI/label/machine-02/vb_name/test1-cae-extint-1


I re-opened the issue so all information is in here now, I hope you agree.





Change By:


Torsten Reinhard
(05/Jan/15 10:21 AM)




Resolution:


Incomplete





Status:


Resolved
Reopened



























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-flowdock] (JENKINS-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException

2015-01-05 Thread swapnils...@gmail.com (JIRA)















































swapnil soor
 commented on  JENKINS-26257


ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















ANY UPDATE ON THIS, THIS IS CAUSING RELEASE BUILD ERRORS..PLEASE PROVIDE THE SOLUTION. THANKS!



























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] [git-parameter-plugin] (JENKINS-23188) Tag List Empty

2015-01-05 Thread netmi...@gmail.com (JIRA)















































Mike .
 commented on  JENKINS-23188


Tag List Empty















Using Git Client Plugin 1.14.1. Unfortunately, still not working here, though the error message has changed:


Jan 05, 2015 11:25:18 AM net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents
INFO: generateContents contenttype PT_TAG RemoteConfig [https://gitserver/repo.git]
Jan 05, 2015 11:25:18 AM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: it.tagMap in /jenkins/view/All/job/MY_PROJ-release/build. Reason: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:94)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)

[JIRA] [unity3d-plugin] (JENKINS-22492) java.io.IOException: Pipe broken

2015-01-05 Thread johannes.sp...@gmail.com (JIRA)















































Johannes Spohr
 commented on  JENKINS-22492


java.io.IOException: Pipe broken















I`m still seeing this issue with Unity 4.5.4. It happens after the workspace was wiped and Unity reimports all assets, which takes up to 2 hours on a larger project.



























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] [sauce-ondemand-plugin] (JENKINS-26288) Sauce connect remains running when test job is cancelled

2015-01-05 Thread pasi_r...@hotmail.com (JIRA)

Pasi Romo
created JENKINS-26288

Sauce connect remains running when test job is cancelled

Issue Type:

Bug

Assignee:

Kohsuke Kawaguchi

Components:

sauce-ondemand-plugin

Created:

05/Jan/15 11:07 AM

Description:

I have noticed that in some occasions if the test job using sauce on demand plugin is interrupted manually at an early stage the sauce connect remains running even if the job gets cancelled. Here is an example log (shortened) of such a run:

Launching Sauce Connect on server
02 Jan 13:53:46 - Sauce Connect 4.3.5, build 1588 c1405ab
02 Jan 13:53:46 - Using CA certificate bundle /etc/ssl/certs/ca-certificates.crt.
02 Jan 13:53:46 - Command line arguments: /home/jenkins/sc-4.3.5-linux/bin/sc
02 Jan 13:53:48 - Please wait for 'you may start your tests' to start your tests.
02 Jan 13:53:48 - Starting secure remote tunnel VM...
Build was aborted
Aborted by Jenkins user
Incremented process count for test, now 1
Test reports were found but none of them are new. Did tests run?

At this point:

sauce connection is up and running even if there are no tests running
internally jenkins has incremented the process count to 1 i.e. all the following builds will increment the process count based on this

Eventually:

the sauce connection won't get cleaned at any point by jenkins because the process count remains 1 i.e. jenkins won't shut down the sauce connection because it thinks there are tests running using it
if the sauce connection is stopped out-side of jenkins (e.g. from sauce labs UI) all the following tests will fail because jenkins expects the sauce connect tunnel to exist
since the incremented process count is maintained in some running java-process, at this point it seems that the only way to correct the situation is to e.g. re-boot the jenkins-server, which will clear the process count and following tests can start the sauce connect normally

This problem occurs relatively rarely and is difficult to reproduce, but when it occurs can be problematic because of failing tests.

Project:

Jenkins

Priority:

Major

Reporter:

Pasi Romo

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] [instant-messaging-plugin] (JENKINS-6560) Plugin should use project.getFullDisplayName() instead of project.getName()

2015-01-05 Thread peter.van.d...@netherlabs.nl (JIRA)















































Peter van Dijk
 commented on  JENKINS-6560


Plugin should use project.getFullDisplayName() instead of project.getName()















A similar problem happens in 'currently building': I get "opencsw#2: unstable11s,opencsw (Elapsed time: 30 min, Estimated remaining time: 29 min)" where unstable11s,opencsw are matrix properties. The actual build name is missing.

Using IRC 2.25 + instant-messaging 1.30.

Can we reopen this ticket because the issue is similar?



























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] [instant-messaging-plugin] (JENKINS-6560) Plugin should use project.getFullDisplayName() instead of project.getName()

2015-01-05 Thread peter.van.d...@netherlabs.nl (JIRA)















































Peter van Dijk
 reopened  JENKINS-6560


Plugin should use project.getFullDisplayName() instead of project.getName()
















Please reopen for !cb, see comment at https://issues.jenkins-ci.org/browse/JENKINS-6560?focusedCommentId=218649&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-218649





Change By:


Peter van Dijk
(05/Jan/15 11:31 AM)




Resolution:


Fixed





Status:


Closed
Reopened



























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] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions

2015-01-05 Thread golube...@gmail.com (JIRA)

Valeri Golubev
commented on JENKINS-24338

Issues with docker permissions

I had the same issue, as described earlier, that docker container was successfully running under 'su - jenkins' but failed when executing by script build step.
Versions:
jenkins: 1.555
os: CentOS release 6.6 (Final)
docker: Docker version 1.3.2, build 39fa2fa/1.3.2

I found a work-around, that probably can be helpful to further clarify the issue.

In order to allow jenkins to create and manage docker containers via 'execute script' build step, you can configure docker service to apply 'jenkins' group ownership to the socket, rather than adding jenkins user to the default-used 'docker' group.
This configuration can be achieved by adding the '-G jenkins' arguments to the docker service config file.

For example, on centos6, I updated the following file:
cat /etc/sysconfig/docker

Docker Upstart and SysVinit configuration file

Customize location of Docker binary (especially for development testing).
DOCKER="/usr/bin/docker"
0
Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS=' --host=unix:///var/run/docker.sock --restart=false -g /opt/app/jenkins/docker -G jenkins'

and it resulted to the following permissions:
srw-rw 1 root jenkins 0 Jan 5 12:22 docker.sock

[JIRA] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions

2015-01-05 Thread golube...@gmail.com (JIRA)

Valeri Golubev
edited a comment on JENKINS-24338

Issues with docker permissions

I found a work-around, that probably can be helpful to further clarify the issue.

For example, on centos6, I updated the following file:

cat /etc/sysconfig/docker

Docker Upstart and SysVinit configuration file

and it resulted to the following permissions:
srw-rw 1 root jenkins 0 Jan 5 12:22 docker.sock

[JIRA] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions

2015-01-05 Thread golube...@gmail.com (JIRA)

Valeri Golubev
edited a comment on JENKINS-24338

Issues with docker permissions

I found a work-around, that probably can be helpful to further clarify the issue.

For example, on centos6, I updated the following file:

cat /etc/sysconfig/docker
# Docker Upstart and SysVinit configuration file

# Customize location of Docker binary (especially for development testing).
DOCKER="/usr/bin/docker"
0
# Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS=' --host=unix:///var/run/docker.sock --restart=false -g /opt/app/jenkins/docker -G jenkins'

and it resulted to the following permissions:
srw-rw 1 root jenkins 0 Jan 5 12:22 docker.sock

[JIRA] [core] (JENKINS-4501) WorkspaceCleanupThread deletes Matrix project workspaces
















































Daniel Beck
 resolved  JENKINS-4501 as Incomplete


WorkspaceCleanupThread deletes Matrix project workspaces
















Please file a new issue as I requested above. The behavior of workspace cleanup was completely rewritten in 1.551, so whatever's wrong in later versions is likely unrelated to this report.

That said, 1.569 is over half a year old and too old for new issue reports. I hope that's just a typo.

Make sure to create a log recorder for the logger hudson.model.WorkspaceCleanupThread on level ALL to find out what it actually does (https://wiki.jenkins-ci.org/display/JENKINS/Logging). "Deleted all workspaces" doesn't look like the cleanup thread's behavior at all.

Resolving as incomplete again.





Change By:


Daniel Beck
(05/Jan/15 11:51 AM)




Status:


Reopened
Resolved





Resolution:


Incomplete



























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-flowdock] (JENKINS-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException

Daniel Beck
commented on JENKINS-26257

ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException

First off, ALL CAPS TEXT IS CONSIDERED YELLING so stop that. Besides, it's both more difficult to read and unprofessional, making you look like a 12 year old.

Second, you should read and follow the advice of https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue because this report doesn't contain nearly enough information to investigate further. In fact, the little information it contains is partially wrong (Flowdock Plugin and Plugin Usage Plugin have absolutely nothing to do with your problem), which means it's your own fault nobody cares. You addressed the report to completely wrong components.

Third, everyone handling these reports is an unpaid volunteer working in their spare time and under no obligation to do anything. This, combined with the previous two points means that it's unlikely you'll get help here.

There are companies providing paid support for Jenkins (e.g. CloudBees when buying a Jenkins Enterprise subscription). Consider going that route to get guaranteed response times.

[JIRA] [jacoco-plugin] (JENKINS-26254) Jacoco plugin is too slow and occupies too much microprocessor time

2015-01-05 Thread il...@redhat.com (JIRA)















































Ilia Meerovich
 commented on  JENKINS-26254


Jacoco plugin is too slow and occupies too much microprocessor time















OK, I made a little investigation.
It seems that serialization/de-serialisation in https://github.com/jenkinsci/jacoco-plugin/blob/master/src/main/java/hudson/plugins/jacoco/ExecutionFileLoader.java
takes a lot of cpu, also load doesn't not spread evenly on all cores (I used htop).
In our case I'm speaking about ovirt project (~3800 classes).
iftop doesn't shows significant network traffic and iostat also doesn't shows significant load.
So analyse of the same jacoco.exec file on idle jenkins taking 30-50 seconds, but on production jenkins it can take 30-50 minutes.





























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] [junit-plugin] (JENKINS-9980) Add the "Publish JUnit test result report" option to maven job configuration page

2015-01-05 Thread javier.palac...@fon.com (JIRA)















































Javier Palacios
 commented on  JENKINS-9980


Add the "Publish JUnit test result report" option to maven job configuration page















We also have this problem. We run the additional tests from a shell buildstep. If the buildstep runs after the maven execution the extra tests are not reported, but if we move the step to pre-build stage, they get properly shown.
The main drawback of this workaround is that 'clean' target cannot be used in the list of maven goals, because it removes the target/surefire-reports directory where the junit reports are copied to.



























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-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















































Oleg Nenashev
 updated  JENKINS-26257


ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException
















Change By:


Oleg Nenashev
(05/Jan/15 12:33 PM)




Component/s:


core





Component/s:


remoting





Component/s:


jenkins-flowdock





Component/s:


plugin-usage-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







-- 
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-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















































Oleg Nenashev
 commented on  JENKINS-26257


ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















+1 regarding Daniel's comments

Regarding the issue...
Probably, it's a bug in remoting layer. Seems the provided stacktrace is incomplete, so it's impossible to find the real cause. 

The core is quite old (1.518), so as a first step I would recommend updating to the latest or latest LTS version.



























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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page

2015-01-05 Thread svvivekan...@gmail.com (JIRA)















































Vivekanand SV
 updated  JENKINS-26077


Multiple Test Reports Graphs and Links in Job Page
















Change By:


Vivekanand SV
(05/Jan/15 12:34 PM)




Description:


I've upgraded Jenkins from 1.575 to 1.594. After updating, then I open the job page, I see 2 graphs and links for the test reports. Though test reports are correct and available, there are 2 instance of it pointing to the same URLs.I use xUnit plugin to publish my JUnit reports as I needed a way to change the build status based on the test PASS/FAIL count that I wanted which I was not able to do in JUnit plugin.Also, all the builds are not shown in the graphs. In the reference image attached, I've been using both Cobertura and xUnit for all the builds, but test graph starts only from build #322 while it should've started from build #291 as in the Cobertura graph.I've attached the screen shot of the job page
 and config page
 for reference.
And the config.xml has the following content under the publishers tagRemoved tag contents for brevity.





Attachment:


Screen Shot 2014-12-18 at 10.30.54 am.png



























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-25869) Jenkins is getting crashed and shutting down once in a while

2015-01-05 Thread hvam...@gmail.com (JIRA)















































Vamsi Hari
 updated  JENKINS-25869


Jenkins is getting crashed and shutting down once in a while
















Daniel - I had attached all the info requested by you. FYI, In the job config files i had commented host names and mentioned respective details over there.  





Change By:


Vamsi Hari
(05/Jan/15 12:55 PM)




Attachment:


PortalEXT-EAR-deployment-PEO-config.xml





Attachment:


PortalEXT-myts-static-STATIC-deployment-config.xml





Attachment:


support.zip





Attachment:


System Information [Jenkins].htm



























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] [email-ext-plugin] (JENKINS-26286) Can not use token (like WARNINGS_NEW) in pre-send script email

2015-01-05 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-26286


Can not use token (like WARNINGS_NEW) in pre-send script email















That's correct, you would need to use code to retrieve the warning count.



























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] [findbugs-plugin] (JENKINS-21723) Findbugs plugin uses absolute URL for link to report















































Ulli Hafner
 commented on  JENKINS-21723


Findbugs plugin uses absolute URL for link to report















Does the column that links to the latest stable build work? It also uses a absolute URL: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/views/LastStableColumn/column.jelly



























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] [findbugs-plugin] (JENKINS-21723) Findbugs plugin uses absolute URL for link to report













































  
Ulli Hafner
 edited a comment on  JENKINS-21723


Findbugs plugin uses absolute URL for link to report
















Does the column that links to the latest stable build work? It also uses an absolute URL: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/views/LastStableColumn/column.jelly



























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] [bitbucket-plugin] (JENKINS-24999) Build triggered by SCM change without activating trigger in the job configuration















































SCM/JIRA link daemon
 commented on  JENKINS-24999


Build triggered by SCM change without activating trigger in the job configuration















Code changed in jenkins
User: Felix Belzunce Arcos
Path:
 src/main/java/com/cloudbees/jenkins/plugins/BitBucketTrigger.java
 src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java
http://jenkins-ci.org/commit/bitbucket-plugin/d5e9cb6a15d9ed1e2313fa656a2361170c74042e
Log:
  JENKINS-24999





























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] [bitbucket-plugin] (JENKINS-24999) Build triggered by SCM change without activating trigger in the job configuration















































SCM/JIRA link daemon
 commented on  JENKINS-24999


Build triggered by SCM change without activating trigger in the job configuration















Code changed in jenkins
User: Nicolas De loof
Path:
 src/main/java/com/cloudbees/jenkins/plugins/BitBucketTrigger.java
 src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java
http://jenkins-ci.org/commit/bitbucket-plugin/3e96df05dbf8d8e3a0b896c18f28a48b3fcd2c97
Log:
  Merge pull request #4 from fbelzunc/JENKINS-24999

[Fixed JENKINS-24999] Build triggered by SCM change without activating trigger in the job configuration


Compare: https://github.com/jenkinsci/bitbucket-plugin/compare/a035a1b8b27a...3e96df05dbf8




























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-25601) JDK9 with jigsaw file layer is not detected as valid JDK

2015-01-05 Thread barb...@irit.fr (JIRA)















































Eric Barboni
 commented on  JENKINS-25601


JDK9 with jigsaw file layer is not detected as valid JDK 















Hi, sorry for the delay.
  I build from source (skipping test because of javassist && jdk 8 ) as I did not find a jenkins.war on the cloudbees jenkins instance.

It's working: JDK 9 folder is detected as jdk, and older jdk 7 or jdk 8 are also detected as jdk



























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] [email-ext-plugin] (JENKINS-26286) Can not use token (like WARNINGS_NEW) in pre-send script email

2015-01-05 Thread ktou...@free.fr (JIRA)













































  
Kristel Touron
 updated  JENKINS-26286


Can not use token (like WARNINGS_NEW) in pre-send script email
















Do you have any idea where is the info stored? 
I can't find any work around in Google.



























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-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587

2015-01-05 Thread clifford...@gmail.com (JIRA)















































Clifford Sanders
 commented on  JENKINS-26048


Jenkins no longer cleaning up child processes when build stopped - as of 1.587















One of our maven jobs aborts because of a timeout during a test but the process on the slave is never stopped.

I created a freestyle job with an 'Invoke top-level Maven targets' build step. When the job aborts the process on the slave is also stopped.

During the holidays we updated from 1.574 to 1.594



























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] [otabuilder-plugin] (JENKINS-26289) Plugin update fails

2015-01-05 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 created  JENKINS-26289


Plugin update fails















Issue Type:


Bug



Assignee:


Unassigned


Components:


otabuilder-plugin



Created:


05/Jan/15 1:19 PM



Description:


hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/otabuilder/0.3.1/otabuilder.hpi (redirected to: http://mirrors.jenkins-ci.org/plugins/otabuilder/0.3.1/otabuilder.hpi)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:791)
	at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1138)
	at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1298)
	at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1116)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/plugins/otabuilder/0.3.1/otabuilder.hpi
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1675)
	at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1673)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1671)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1244)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:756)
	... 7 more
Caused by: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/plugins/otabuilder/0.3.1/otabuilder.hpi
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1624)
	at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2678)
	at java.net.URLConnection.getHeaderFieldLong(URLConnection.java:639)
	at java.net.URLConnection.getContentLengthLong(URLConnection.java:511)
	at java.net.URLConnection.getContentLength(URLConnection.java:495)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:755)
	... 7 more




Project:


Jenkins



Priority:


Major



Reporter:


James Howe

























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] [git-plugin] (JENKINS-26290) Git plugin periodically fails to find commit

2015-01-05 Thread m...@mikemcquaid.com (JIRA)















































Mike McQuaid
 created  JENKINS-26290


Git plugin periodically fails to find commit















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-plugin



Created:


05/Jan/15 1:26 PM



Description:


Thanks for all your great work with this plugin; not sure how I'd live without it!

Around ~1% of jobs triggered by GitHub pull requests fail to find the merge commit with output like the below. I'd love to help you debug this as it's been driving me mad for a wee while (I don't know why I've only just filed this now). If I immediately rebuild the job then it always works fine so it's a weird intermittent issue. Even a workaround that would let me e.g. retry the Git operations here would be fantastic.

Thanks folks!

Started by upstream project "Homebrew Pull Requests" build number 19312
originally caused by:
 GitHub pull request #35564 of commit 13c8c95db0d399cd387ec362e35d9917df1465f8 automatically merged.
[EnvInject] - Loading node environment variables.
Building remotely on yosemite in workspace /Users/brew/Jenkins/workspace/Homebrew Pull Requests/version/yosemite
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/Homebrew/homebrew.git # timeout=10
Fetching upstream changes from https://github.com/Homebrew/homebrew.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress https://github.com/Homebrew/homebrew.git +refs/heads/:refs/remotes/origin/ +refs/pull/:refs/remotes/origin/pr/ # timeout=5
Checking out Revision c1d392f8a050cb7049b3afee8772b34491150e21 (origin/pr/35564/merge)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c1d392f8a050cb7049b3afee8772b34491150e21
FATAL: Could not checkout null with start point c1d392f8a050cb7049b3afee8772b34491150e21
hudson.plugins.git.GitException: Could not checkout null with start point c1d392f8a050cb7049b3afee8772b34491150e21
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1674)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
	at ..remote call to yosemite(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
	at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
	at hudson.remoting.Channel.call(Channel.java:752)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
	at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
	at com.sun.proxy.$Proxy52.execute(Unknown Source)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:992)
	at hudson.scm.SCM.checkout(SCM.java:488)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1257)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
	at hudson.model.Run.execute(Run.java:1745)
	at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Execut

[JIRA] [core] (JENKINS-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException

2015-01-05 Thread swapnils...@gmail.com (JIRA)















































swapnil soor
 commented on  JENKINS-26257


ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















Sorry for irritation caused due to cap letter , I had no intentions to do so. I do understand being this a free service nobody is obliged to provide guaranteed response. But most of the time I found good solutions by the experts here only.

Anyways thanks for the response Daniel. I will change the component to core, thanks!

@Oleg, Sorry the Jenkins Version Used is: 1.588, we had upgraded this recently. I have provided only the error snippet, may be I might have missed in our setup which is leading to this error, any clue/pointer in debuging would be helpful.

Since it was throwing the exception in hudson packages, I thought its a coding bug. On jenkins console I am getting below exception though the build is successful, right after Maven Build Success message.
Error is repetitive hence didn't posted the whole thread:

[INFO] Final Memory: 245M/562M
[INFO] 
ERROR: Asynchronous execution failure
java.util.concurrent.ExecutionException: java.lang.ClassCastException
	at hudson.remoting.Channel$3.adapt(Channel.java:784)
	at hudson.remoting.Channel$3.adapt(Channel.java:779)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
	at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:143)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:701)
Caused by: java.lang.ClassCastException
	line no..21
	..
	..
	line no..2020
ERROR: Asynchronous execution failure
java.util.concurrent.ExecutionException: java.lang.ClassCastException
	at hudson.remoting.Channel$3.adapt(Channel.java:784)
	at hudson.remoting.Channel$3.adapt(Channel.java:779)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
	at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:143)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:701)
Caused by: java.lang.ClassCastException
	at .(Unknown Source)
	at ..remote call to channel(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
	at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
	at hudson.remoting.Channel$3.adapt(Channel.java:782)
	... 14 more
ERROR: Asynchronous execution failure
java.util.concurrent.ExecutionException: java.lang.ClassCastException
	at hudson.remoting.Channel$3.adapt(Channel.java:784)
	at hudson.remoting.Channel$3.adapt(Channel.java:779)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
	at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:143)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask$Sync.

[JIRA] [workflow-plugin] (JENKINS-26157) Subversion doesn't work correctly

2015-01-05 Thread tg9...@gmx-topmail.de (JIRA)















































Thomas Goeppel
 commented on  JENKINS-26157


Subversion doesn't work correctly















Yes, it does! I had read it before, but one needs to be somewhat familiar with the code to understand the documentation.



























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] [email-ext-plugin] (JENKINS-26286) Can not use token (like WARNINGS_NEW) in pre-send script email

2015-01-05 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-26286


Can not use token (like WARNINGS_NEW) in pre-send script email















I'd take a look at the code for the Warnings Plugin. https://github.com/jenkinsci/warnings-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







-- 
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] [git-plugin] (JENKINS-26290) Git plugin periodically fails to find commit

2015-01-05 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-26290


Git plugin periodically fails to find commit















I've seen that message infrequently myself. If you're willing to insert some debugging code into the git plugin and deploy it into your environment where the random failure happens, it could provide deeper understand of the problem.

What I'd suggest (without having written the code):


	Insert additional debug code into the GitException which only executes if the stderr of the exception includes the message "reference is not a tree"
	In that additional debug code, run "git show "
	In that additional debug code, run "git ls-remote origin "



I think the intermittent nature of the problem means that you'll need to insert the debug code into your production instance, or you'll need to configure another instance which shows the problem.



























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] [git-plugin] (JENKINS-26290) Git plugin periodically fails to find commit

2015-01-05 Thread mark.earl.wa...@gmail.com (JIRA)













































  
Mark Waite
 edited a comment on  JENKINS-26290


Git plugin periodically fails to find commit
















I've seen that message infrequently myself. If you're willing to insert some debugging code into the git plugin and deploy it into your environment where the random failure happens, it could provide deeper understanding of the problem.

What I'd suggest (without having written the code):


	Insert additional debug code into the GitException which only executes if the stderr of the exception includes the message "reference is not a tree"
	In that additional debug code, run "git show "
	In that additional debug code, run "git ls-remote origin "



I think the intermittent nature of the problem means that you'll need to insert the debug code into your production instance, or you'll need to configure another instance which shows the problem.



























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] [maven-plugin] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587















































Daniel Beck
 updated  JENKINS-26048


Jenkins no longer cleaning up child processes when build stopped - as of 1.587
















Comment indicates this issue is specific to the Maven project type.





Change By:


Daniel Beck
(05/Jan/15 2:32 PM)




Component/s:


maven-plugin





Component/s:


core



























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] [git-plugin] (JENKINS-26290) Git plugin periodically fails to find commit

2015-01-05 Thread m...@mikemcquaid.com (JIRA)















































Mike McQuaid
 commented on  JENKINS-26290


Git plugin periodically fails to find commit















I'm willing to insert that code, yeh. Longer-term I'd also be happy with just a retry on this too.



























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-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















































Daniel Beck
 commented on  JENKINS-26257


ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















Make sure the slave.jar on the slaves is up to date. VersionColumn Plugin can help you with that. SSH Slaves take care of this automatically, but if you're launching using a different mechanism, that may be a problem.



























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] [scm-sync-configuration-plugin] (JENKINS-24621) Footer shadows save button on job config

2015-01-05 Thread aforlo...@gmail.com (JIRA)















































Anthony Forloney
 commented on  JENKINS-24621


Footer shadows save button on job config















This problem also exists without the SCM Sync Plugin installed.



























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-25869) Jenkins is getting crashed and shutting down once in a while

2015-01-05 Thread michael_gir...@choicehotels.com (JIRA)















































Daniel Beck
 commented on  JENKINS-25869


Jenkins is getting crashed and shutting down once in a while















I'd try to make sure to unset the http_proxy and related environment variables before starting the Jenkins process (or rather Tomcat in your case?), instead (if necessary) using proxy configuration in Jenkins (Manage Jenkins » Manage Plugins » Advanced). This may result in child processes (e.g. shell scripts and the tools they run) not inheriting the proxy configuration by default though.

The bug may well be in the gconf (Gnome) library or the JDK, as that's where the crash occurs.
http://hg.openjdk.java.net/jdk7u/jdk7u/jdk/file/54acd5cd0485/src/solaris/native/sun/net/spi/DefaultProxySelector.c#l155

Please also note that the user and password to the proxy are included in plain text in the support bundle (nodes/master/environment.txt), so you should change those now.



























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] [cli] (JENKINS-26291) cli list-jobs returns display name instead of job name















































michael giroux
 created  JENKINS-26291


cli list-jobs returns display name instead of job name















Issue Type:


Bug



Assignee:


Unassigned


Components:


cli



Created:


05/Jan/15 3:11 PM



Description:


cli list-jobs returned the display-name for a job.  Subsequent attempt to use the job name to get the configuration returned an error:
No such job 'springframework-beanmapper-util'; perhaps you meant 'Springframework-Extensions-Release'?

Example script:
IFS=$'\n'
for a in cli list-jobs
do
  cli get-job "$a"
done

The cli get-job fails for any job that has a display-name set to a value that does not match the actual job name.




Environment:


Jenkins 1.565.2

Linux  2.6.18-398.el5 #1 SMP Tue Aug 12 06:26:17 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux






Project:


Jenkins



Priority:


Minor



Reporter:


michael giroux

























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] [ownership-plugin] (JENKINS-26064) There is a problem when use with Active Directory plugin
















































Oleg Nenashev
 resolved  JENKINS-26064 as Duplicate


There is a problem when use with Active Directory plugin
















No response. Closing as a duplicate of JENKINS-25400 





Change By:


Oleg Nenashev
(05/Jan/15 3:19 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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] [ownership-plugin] (JENKINS-21838) Allow to authenticate as a job's owner during the build
















































Oleg Nenashev
 resolved  JENKINS-21838 as Fixed


Allow to authenticate as a job's owner during the build
















Fixed in 0.5





Change By:


Oleg Nenashev
(05/Jan/15 3:21 PM)




Status:


In Progress
Resolved





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







-- 
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] [junit-plugin] (JENKINS-9980) Add the "Publish JUnit test result report" option to maven job configuration page

2015-01-05 Thread javier.palac...@fon.com (JIRA)













































  
Javier Palacios
 edited a comment on  JENKINS-9980


Add the "Publish JUnit test result report" option to maven job configuration page
















We also have this problem. We run the additional tests from a shell buildstep. If the buildstep runs after the maven execution the extra tests are not reported, but if we move the step to pre-build stage, they get properly shown.
The main drawback of this workaround is that 'clean' target cannot be used in the list of maven goals, because it removes the target/surefire-reports directory where the junit reports are copied to.

Update:
If the execution of the extra tests can be binded to the maven test phase, the produced junit does appear in jenkins along standard surefire reports if the resulting junit xml is copied there. At least for us and for now, this is an acceptable workaround.



























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] [cli] (JENKINS-26291) cli list-jobs returns display name instead of job name

2015-01-05 Thread csaba.gyo...@siemens-enterprise.com (JIRA)
















































Daniel Beck
 resolved  JENKINS-26291 as Duplicate


cli list-jobs returns display name instead of job name
















Duplicates JENKINS-25338





Change By:


Daniel Beck
(05/Jan/15 3:51 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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] [perforce-plugin] (JENKINS-25830) Since upgrading to 1.590 the "Max # of builds to keep with artifacts" option does not seem to work

2015-01-05 Thread mcough...@symantec.com (JIRA)















































martin coughlan
 commented on  JENKINS-25830


Since upgrading to 1.590 the "Max # of builds to keep with artifacts" option does not seem to work















Hi Oleg

Sorry about the delay we were offline because of the xmas holidays. We fixed the issue by updating the perforce plugin version. sorry if this wasted a lot of your time.

thanks
Martin



























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-26292) Symlinks unter builds (lastSuccessfulBuild, lastFailedBuild, , etc) are not working in a shared folder

Csaba Gyorfi
created JENKINS-26292

Symlinks unter builds (lastSuccessfulBuild, lastFailedBuild, , etc) are not working in a shared folder

Issue Type:

Bug

Assignee:

Unassigned

Components:

core

Created:

05/Jan/15 4:01 PM

Description:

Our Jenkins server runs on a windows 2008R2 x64 system. In order to provide an easy access to the artifacts for the developers, I want to share the folder:
Jenkins\jobs\\builds

When attempting to browse than this directory from remote over the share, the symnlinks (lastSuccessfulBuild, lastFailedBuild, , etc) do not work - since they contain fix path reference.
It could work if Jenkins would create shortcuts or directory junctions instead of the symlink (see http://superuser.com/questions/343074/directory-junction-vs-directory-symbolic-link).

Is there any known workaround to solve this?
In my opinion the symlinks shall be excahnged to directory junctions, or it should be possible to configure which way Jenkins shall create the links.

Environment:

windows 2008 R2 x64

Project:

Jenkins

Priority:

Major

Reporter:

Csaba Gyorfi

[JIRA] [ec2-plugin] (JENKINS-15078) Be able to set Instance Name

2015-01-05 Thread bosox...@gmail.com (JIRA)















































Jay Perry
 commented on  JENKINS-15078


Be able to set Instance Name















Any way to get the Name tag set in aws so when I go to the aws console I can tell what agents are what?



























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] [ec2-plugin] (JENKINS-15078) Be able to set Instance Name

2015-01-05 Thread bosox...@gmail.com (JIRA)













































  
Jay Perry
 edited a comment on  JENKINS-15078


Be able to set Instance Name
















Any way to get the Name tag set in aws so when I go to the aws console I can tell what agents are what?  It seems you can add a tag in Jenkins after the node is up but I would like to have any instances created as part of a cloud profile to get a particular aws tag.  Is this supported?



























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] [ec2-plugin] (JENKINS-15078) Be able to set Instance Name

2015-01-05 Thread bosox...@gmail.com (JIRA)















































Jay Perry
 commented on  JENKINS-15078


Be able to set Instance Name















Nevermind, I was able to find Tags in the Advanced section.



























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] [dashboard-view-plugin] (JENKINS-19634) Test Statistic Grid: not sorting by percentage correctly

2015-01-05 Thread shawn.mccart...@gmail.com (JIRA)















































Shawn McCarthy
 commented on  JENKINS-19634


Test Statistic Grid: not sorting by percentage correctly















I created a pull request for this : https://github.com/jenkinsci/jenkins/pull/1509 . I attached the screenshots in the pull request as well. I updated sortable.js to check for data that ends with % , and sort it just like currency (remove all characters except 0-9 and '.'). This doesn't take into consideration if the percentage is <100% or >0% (treats it as 100 and 0 respectively).



























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] [perforce-plugin] (JENKINS-25830) Since upgrading to 1.590 the "Max # of builds to keep with artifacts" option does not seem to work















































Oleg Nenashev
 commented on  JENKINS-25830


Since upgrading to 1.590 the "Max # of builds to keep with artifacts" option does not seem to work















No problem. 1.3.29 was quite unstable due to my changes in variables substitution engine. It may affect the log rotation if Jenkins tries to clean a job's workspace from it. 

Please re-open the issue if it happens again



























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] [perforce-plugin] (JENKINS-25830) Since upgrading to 1.590 the "Max # of builds to keep with artifacts" option does not seem to work
















































Oleg Nenashev
 resolved  JENKINS-25830 as Cannot Reproduce


Since upgrading to 1.590 the "Max # of builds to keep with artifacts" option does not seem to work
















Change By:


Oleg Nenashev
(05/Jan/15 4:34 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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] [email-ext-plugin] (JENKINS-26293) email-ext-plugin FILE token macro apostrophe escaping

2015-01-05 Thread denisblanche...@gmail.com (JIRA)

Denis Blanchette
created JENKINS-26293

email-ext-plugin FILE token macro apostrophe escaping

Issue Type:

Bug

Assignee:

Alex Earl

Components:

email-ext-plugin

Created:

05/Jan/15 4:36 PM

Description:

I have a job that sends an HTML e-mail with the email-ext-plugin.

The content is configured as such :
${FILE, path="MyFile.html"}

Where MyFile.html is generated from a Python script.

There is an apostrophe in the content of the file. Before the latest update to email-ext-plugin it was displayed "'". Now it is displayed "'" in the email client (tested on OWA and Outlook).

The change seems to be related to this line : https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/plugins/CssInliner.java#L78
The added .escapeMode(Entities.EscapeMode.xhtml)) changes the apostrophe to it's ampersand escaped version.

There is probably a good reason why this line was modified in the first place, but I wonder if there would be a way to make it work on my end. Maybe make the escaping mode configurable?

Thank you

Environment:

Email Extension Plugin 2.39, Token Macro 1.10, Jenkins 1.580.2. Windows Server 2012

Project:

Jenkins

Labels:

email-ext

Priority:

Minor

Reporter:

Denis Blanchette

[JIRA] [core] (JENKINS-26294) WARNING: 'stapler-class' is deprecated is shown on almost every extension















































Ulli Hafner
 created  JENKINS-26294


WARNING: 'stapler-class' is deprecated is shown on almost every extension















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


05/Jan/15 4:38 PM



Description:


Due to commit https://github.com/stapler/stapler/commit/82b0a45924b083796d04c94661bbef7b80e2d2bf the Jenkins log fills with a lot of messages. Seems that almost every plug-in/extension is affected. 

Example log:
https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/lastCompletedBuild/testReport/plugins/CheckStylePluginTest/should_collect_warnings_in_build/

In my plug-ins I don't use stapler-class explicitely, this is something inherited from core. So it is not clear what to do as a plg-in developer.




Project:


Jenkins



Priority:


Minor



Reporter:


Ulli Hafner

























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-26294) WARNING: 'stapler-class' is deprecated is shown for almost every extension















































Ulli Hafner
 updated  JENKINS-26294


WARNING: 'stapler-class' is deprecated is shown for almost every extension
















Change By:


Ulli Hafner
(05/Jan/15 4:39 PM)




Summary:


WARNING: 'stapler-class' is deprecated is shown
 on
 for
 almost every extension



























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-26294) WARNING: 'stapler-class' is deprecated is shown for almost every extension















































Ulli Hafner
 updated  JENKINS-26294


WARNING: 'stapler-class' is deprecated is shown for almost every extension
















Change By:


Ulli Hafner
(05/Jan/15 4:42 PM)




Description:


Due to commit https://github.com/stapler/stapler/commit/82b0a45924b083796d04c94661bbef7b80e2d2bf the Jenkins log fills with a lot of messages. Seems that almost every plug-in/extension is affected. Example log:https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/lastCompletedBuild/testReport/plugins/CheckStylePluginTest/should_collect_warnings_in_build/In my plug-ins I don't use stapler-class explicitely, this might be something inherited from core. So it is not clear what to do as a plug-in developer. Is there anything I can do here in my plug-in? One affected plug-in is checkstyle: here I get the messages for {noformat}master54521|WARNING: 'stapler-class' is deprecated: hudson.plugins.checkstyle.CheckStylePublishermaster52856|WARNING: 'stapler-class' is deprecated: hudson.plugins.checkstyle.CheckStyleColumn

{noformat}



























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-26294) WARNING: 'stapler-class' is deprecated is shown for almost every extension















































Ulli Hafner
 updated  JENKINS-26294


WARNING: 'stapler-class' is deprecated is shown for almost every extension
















Change By:


Ulli Hafner
(05/Jan/15 4:41 PM)




Description:


Due to commit https://github.com/stapler/stapler/commit/82b0a45924b083796d04c94661bbef7b80e2d2bf the Jenkins log fills with a lot of messages. Seems that almost every plug-in/extension is affected. Example log:https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/lastCompletedBuild/testReport/plugins/CheckStylePluginTest/should_collect_warnings_in_build/In my plug-ins I don't use stapler-class explicitely, this
 is
 might be
 something inherited from core. So it is not clear what to do as a
 plg
 plug
-in developer.
 Is there anything I can do here in my plug-in? One affected plug-in is checkstyle: here I get the messages for {noformat}master54521|WARNING: 'stapler-class' is deprecated: hudson.plugins.checkstyle.CheckStylePublishermaster52856|WARNING: 'stapler-class' is deprecated: hudson.plugins.checkstyle.CheckStyleColumn{noformat}



























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] [email-ext-plugin] (JENKINS-26293) email-ext-plugin FILE token macro apostrophe escaping

2015-01-05 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-26293


email-ext-plugin FILE token macro apostrophe escaping















I actually have a different fix for this already for the next release.



























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] [xcode-plugin] (JENKINS-26295) Parsing issue due to unit test made with Swift

2015-01-05 Thread clem...@omsignal.com (JIRA)















































Clem Jan
 created  JENKINS-26295


Parsing issue due to unit test made with Swift















Issue Type:


Bug



Assignee:


Unassigned


Components:


xcode-plugin



Created:


05/Jan/15 4:55 PM



Description:


(Using jenkins Xcode plugin)
I tried with Objective C unit test and it is working. But when we are running Swift unit tests we have this issue :

Test Case '-[OMPlus_DemoTests.OMSWorkoutReportProjectorTests testZeroesDontContributeToAggregates]' started.
/Users/builder/.jenkins/jobs/project/workspace/projectName/OMPlus-Demo-Tests/OMSWorkoutReportProjectorTests.swift:256: error: -[OMPlus_DemoTests.OMSWorkoutReportProjectorTests testZeroesDontContributeToAggregates] : XCTAssertEqual failed: ("18") is not equal to ("15") - peak HR from second workout
FATAL: Log statements out of sync: current test suite was 'OMSWorkoutReportProjectorTests' and not 'OMPlus_DemoTests.OMSWorkoutReportProjectorTests'

Do you have a fix in progress for this issue ?




Project:


Jenkins



Priority:


Blocker



Reporter:


Clem Jan

























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-21341) Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int)

2015-01-05 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 commented on  JENKINS-21341


Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int)















Pity this was not backported to the 1.554.x line.



























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build
















































SCM/JIRA link daemon
 resolved  JENKINS-13458 as Fixed


Add switch to set reference build always as the latest build
















Change By:


SCM/JIRA link daemon
(05/Jan/15 5:17 PM)




Status:


Open
Resolved





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







-- 
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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/tasks/MavenTasksResultAction.java
 src/main/java/hudson/plugins/tasks/TasksAnnotationsAggregator.java
 src/main/java/hudson/plugins/tasks/TasksMavenResult.java
 src/main/java/hudson/plugins/tasks/TasksMavenResultAction.java
 src/main/java/hudson/plugins/tasks/TasksPublisher.java
 src/main/java/hudson/plugins/tasks/TasksReporter.java
 src/main/java/hudson/plugins/tasks/TasksReporterResult.java
 src/main/java/hudson/plugins/tasks/TasksResult.java
http://jenkins-ci.org/commit/tasks-plugin/0ae7469b4f68430d7c2d29567fb80ef41819b989
Log:
  [FIXED JENKINS-13458] Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/analysis/core/AbstractAnnotationParser.java
 src/main/java/hudson/plugins/analysis/core/BuildHistory.java
 src/main/java/hudson/plugins/analysis/core/BuildResult.java
 src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java
 src/main/java/hudson/plugins/analysis/core/HealthAwareRecorder.java
 src/main/java/hudson/plugins/analysis/core/HealthAwareReporter.java
 src/main/resources/util/thresholds.jelly
 src/main/resources/util/thresholds.properties
 src/main/resources/util/thresholds_de.properties
 src/test/java/hudson/plugins/analysis/core/BuildHistoryTest.java
http://jenkins-ci.org/commit/analysis-core-plugin/1a2ebe2a80da6cdf429a442cc3b2be8494337441
Log:
  [FIXED JENKINS-13458] Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/analysis/collector/AnalysisAnnotationsAggregator.java
 src/main/java/hudson/plugins/analysis/collector/AnalysisPublisher.java
 src/main/java/hudson/plugins/analysis/collector/AnalysisResult.java
http://jenkins-ci.org/commit/analysis-collector-plugin/8c4ac1d376dfa056f60c7968d426a7a0aed0982d
Log:
  [FIXED JENKINS-13458] Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/dry/DryAnnotationsAggregator.java
 src/main/java/hudson/plugins/dry/DryMavenResult.java
 src/main/java/hudson/plugins/dry/DryMavenResultAction.java
 src/main/java/hudson/plugins/dry/DryPublisher.java
 src/main/java/hudson/plugins/dry/DryReporter.java
 src/main/java/hudson/plugins/dry/DryReporterResult.java
 src/main/java/hudson/plugins/dry/DryResult.java
 src/main/java/hudson/plugins/dry/MavenDryResultAction.java
http://jenkins-ci.org/commit/dry-plugin/ee4a8b6203a4caf10855dd8ddf5341a6f55e08ee
Log:
  [FIXED JENKINS-13458] Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 .idea/codeStyleSettings.xml
 .idea/libraries/Maven__org_jvnet_hudson_plugins_analysis_core_1_65.xml
 .idea/libraries/Maven__org_jvnet_hudson_plugins_analysis_test_1_11.xml
 analysis-collector
 analysis-core
 dry
 pmd
 tasks
 warnings
http://jenkins-ci.org/commit/analysis-suite-plugin/43474638ad5a84ca7d9a697a1ad9d19119f603b1
Log:
  [FIXED JENKINS-13458] Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/warnings/WarningsAnnotationsAggregator.java
 src/main/java/hudson/plugins/warnings/WarningsBuildHistory.java
 src/main/java/hudson/plugins/warnings/WarningsProjectAction.java
 src/main/java/hudson/plugins/warnings/WarningsPublisher.java
 src/main/java/hudson/plugins/warnings/WarningsResult.java
 src/test/java/hudson/plugins/warnings/WarningsPublisherTest.java
http://jenkins-ci.org/commit/warnings-plugin/96c2df676a21dc3c3368f8e91e7c188d2946403e
Log:
  [FIXED JENKINS-13458] Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsAnnotationsAggregator.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsMavenResult.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsMavenResultAction.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsPublisher.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporter.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporterResult.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsResult.java
 plugin/src/main/java/hudson/plugins/findbugs/MavenFindBugsResultAction.java
http://jenkins-ci.org/commit/findbugs-plugin/2b0b1b8d1b3da6fdb454b4e3caabce62e22c8a7d
Log:
  [FIXED JENKINS-13458] Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 checkstyle.iml
 pom.xml
 src/main/java/hudson/plugins/checkstyle/CheckStyleAnnotationsAggregator.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleMavenResult.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleMavenResultAction.java
 src/main/java/hudson/plugins/checkstyle/CheckStylePublisher.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleReporter.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleReporterResult.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleResult.java
 src/main/java/hudson/plugins/checkstyle/MavenCheckStyleResultAction.java
 src/main/java/hudson/plugins/checkstyle/parser/CheckStyleParser.java
 src/test/java/hudson/plugins/checkstyle/parser/CheckStyleParserTest.java
 src/test/resources/hudson/plugins/checkstyle/parser/checkstyle-result-build1.xml
 src/test/resources/hudson/plugins/checkstyle/parser/checkstyle-result-build2.xml
 src/test/resources/hudson/plugins/checkstyle/parser/checkstyle-result-build3.xml
 src/test/resources/hudson/plugins/checkstyle/parser/checkstyle-result-build4.xml
http://jenkins-ci.org/commit/checkstyle-plugin/369e5fb065dc8fa3137f0c9016451d3e11a8f5fc
Log:
  [FIXED JENKINS-13458] Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 pmd.iml
 pom.xml
 src/main/java/hudson/plugins/pmd/PmdAnnotationsAggregator.java
 src/main/java/hudson/plugins/pmd/PmdMavenResult.java
 src/main/java/hudson/plugins/pmd/PmdMavenResultAction.java
 src/main/java/hudson/plugins/pmd/PmdPublisher.java
 src/main/java/hudson/plugins/pmd/PmdReporter.java
 src/main/java/hudson/plugins/pmd/PmdReporterResult.java
 src/main/java/hudson/plugins/pmd/PmdResult.java
 src/main/java/hudson/plugins/pmd/parser/PmdParser.java
http://jenkins-ci.org/commit/pmd-plugin/bf11ab5a02fdbbae20a7503fad468723f6bee29b
Log:
  [FIXED JENKINS-13458] Added an option to use previous build as a reference.





























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-26294) WARNING: 'stapler-class' is deprecated is shown for almost every extension
















































Daniel Beck
 resolved  JENKINS-26294 as Duplicate


WARNING: 'stapler-class' is deprecated is shown for almost every extension
















https://github.com/jenkinsci/jenkins/pull/1443 will fix this.





Change By:


Daniel Beck
(05/Jan/15 5:41 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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-26292) Symlinks unter builds (lastSuccessfulBuild, lastFailedBuild, , etc) are not working in a shared folder















































Daniel Beck
 commented on  JENKINS-26292


Symlinks unter builds (lastSuccessfulBuild, lastFailedBuild, , etc) are not working in a shared folder















Directory junctions are probably considered directories by Java, which means they're indistinguishable from folders, making a complete mess of everything.



























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] [labeled-test-groups-publisher-plugin] (JENKINS-13376) Ability to add in new groups of test types















































SCM/JIRA link daemon
 commented on  JENKINS-13376


Ability to add in new groups of test types















Code changed in jenkins
User: Larry Bordowitz
Path:
 src/main/java/hudson/plugins/labeledgroupedtests/LabeledTestGroupConfiguration.java
 src/main/java/hudson/plugins/labeledgroupedtests/LabeledTestResultGroupPublisher.java
 src/main/resources/hudson/plugins/labeledgroupedtests/LabeledTestGroupConfiguration/config.jelly
 src/main/resources/hudson/plugins/labeledgroupedtests/LabeledTestResultGroupPublisher/config.jelly
http://jenkins-ci.org/commit/labeled-test-groups-publisher-plugin/186aae1a037f5485d89fd403aca4d44660671b9a
Log:
  JENKINS-13376 Changed the test label from a finite selection to a customizable text label.





























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] [labeled-test-groups-publisher-plugin] (JENKINS-13376) Ability to add in new groups of test types















































SCM/JIRA link daemon
 commented on  JENKINS-13376


Ability to add in new groups of test types















Code changed in jenkins
User: Larry Bordowitz
Path:
 src/main/java/hudson/plugins/labeledgroupedtests/LabeledTestGroupConfiguration.java
 src/main/java/hudson/plugins/labeledgroupedtests/LabeledTestResultGroupPublisher.java
 src/main/resources/hudson/plugins/labeledgroupedtests/LabeledTestGroupConfiguration/config.jelly
 src/main/resources/hudson/plugins/labeledgroupedtests/LabeledTestResultGroupPublisher/config.jelly
http://jenkins-ci.org/commit/labeled-test-groups-publisher-plugin/0085c51cce1685f20b80303d11362a28cba9afe0
Log:
  Merge pull request #2 from lbordowitz/FreeLabel

JENKINS-13376 Free the test group label!


Compare: https://github.com/jenkinsci/labeled-test-groups-publisher-plugin/compare/1a9f51d2ec85...0085c51cce16




























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] [labeled-test-groups-publisher-plugin] (JENKINS-13376) Ability to add in new groups of test types

2015-01-05 Thread lbordow...@yahoo-inc.com (JIRA)
















































Larry Bordowitz
 assigned  JENKINS-13376 to Larry Bordowitz



Ability to add in new groups of test types
















Change By:


Larry Bordowitz
(05/Jan/15 5:53 PM)




Assignee:


Laurence Bordowitz



























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] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)

2015-01-05 Thread glimb...@gmail.com (JIRA)















































Grant Limberg
 reopened  JENKINS-25588


Integrate vSphere Cloud plugin with Credentials plugin (auth options)
















Looks to be a few issues with this update.

Upgraded to this plugin today.  All I get is the following.  In the main Jenkins Configuration page, after adding a credential for the VM server and hitting Text Connection:

"Username is not specified"

When trying to launch a slave:

javax.servlet.ServletException: java.lang.RuntimeException: org.jenkinsci.plugins.vsphere.tools.VSphereException: java.net.MalformedURLException: no protocol: null/sdk
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at com.marvelution.jenkins.plugins.jira.filter.ApplinksServletFilter.doFilter(ApplinksServletFilter.java:83)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
	at org.eclipse.jetty.security.Se

[JIRA] [github-oauth-plugin] (JENKINS-26296) Fix for null pointer exception when user enters github url with wrong format















































alex rothenberg
 created  JENKINS-26296


Fix for null pointer exception when user enters github url with wrong format















Issue Type:


Bug



Assignee:


Sam Kottler



Components:


github-oauth-plugin



Created:


05/Jan/15 6:12 PM



Description:


When a user enters a github url with a bad format the gitub-oauth-plugin would throw a null pointer exception breaking the jenkins UI for the homepage.

Now it checks for the null and will treat that job as forbidden so not shown.

Fix is in Github PR - https://github.com/jenkinsci/github-oauth-plugin/pull/32 




Project:


Jenkins



Priority:


Major



Reporter:


alex rothenberg

























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] [labeled-test-groups-publisher-plugin] (JENKINS-13376) Ability to add in new groups of test types

2015-01-05 Thread lbordow...@yahoo-inc.com (JIRA)
















































Larry Bordowitz
 resolved  JENKINS-13376 as Fixed


Ability to add in new groups of test types
















Let me know if this works alright. The fix should provide backwards compatibility, so it shouldn't interfere with previous versions if you upgrade it.





Change By:


Larry Bordowitz
(05/Jan/15 6:11 PM)




Status:


Open
Resolved





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







-- 
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] [s3-plugin] (JENKINS-26297) S3 download link incorrect when Destination bucket includes a path prefix

2015-01-05 Thread jenkins.l...@o172.net (JIRA)















































Liam Scott
 created  JENKINS-26297


S3 download link incorrect when Destination bucket includes a path prefix















Issue Type:


Bug



Assignee:


Michael Watt



Components:


s3-plugin



Created:


05/Jan/15 6:13 PM



Description:


The "Publish artifacts to S3 Bucket" action setting "Destination bucket" may include a prefix, e.g. 



 Destination bucket: my-bucket-name/prefix



This works fine for upload - the files are stored under this "folder".

But the download links generated by the plugin (the signed S3 URLs) ignore the prefix, hence they point to a non-existent s3 object.




Environment:


s3 plugin v0.7




Project:


Jenkins



Labels:


s3
artifact-download




Priority:


Minor



Reporter:


Liam Scott

























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] [github-oauth-plugin] (JENKINS-13354) Jenkins very slow when not an admin















































alex rothenberg
 commented on  JENKINS-13354


Jenkins very slow when not an admin















This was merged and fixed in the source (https://github.com/jenkinsci/github-oauth-plugin/commit/08912451c6dc7b33977a1755aecb6836b5378902) but I'm not sure if the plugin was released with the fix.



























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] [github-oauth-plugin] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin















































alex rothenberg
 commented on  JENKINS-24383


Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin















Addressed in github PR - https://github.com/jenkinsci/github-oauth-plugin/pull/32



























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] [xcode-plugin] (JENKINS-26295) Parsing issue due to unit test made with Swift

2015-01-05 Thread lacos...@java.net (JIRA)















































lacostej
 commented on  JENKINS-26295


Parsing issue due to unit test made with Swift















I think I know what goes on, but I would prefer a full console/test output so that we can reproduce the issue properly.

Can you try sending it ?

It should look like https://github.com/jenkinsci/xcode-plugin/blob/master/src/test/resources/XCTest_output_failing_1.txt




























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] [github-oauth-plugin] (JENKINS-26296) Fix for null pointer exception when user enters github url with wrong format
















































alex rothenberg
 resolved  JENKINS-26296 as Duplicate


Fix for null pointer exception when user enters github url with wrong format
















Duplicate of JENKINS-24383





Change By:


alex rothenberg
(05/Jan/15 6:32 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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] [global-variable-string-parameter-plugin] (JENKINS-24920) Global Password cannot handle $ character















































Oleg Nenashev
 commented on  JENKINS-24920


Global Password cannot handle $ character















Haiqing, could you retry your case with perforce-1.3.33?
There was a re-work of variables handling, so probably the issue has been resolved.

If it still failing, do you specify the password directly in the configuration entry?



























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] [xcode-plugin] (JENKINS-26295) Parsing issue due to unit test made with Swift

2015-01-05 Thread clem...@omsignal.com (JIRA)















































Clem Jan
 commented on  JENKINS-26295


Parsing issue due to unit test made with Swift















So you want logs from xCode console ? Not from Jenkins console ?



























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] [email-ext-plugin] (JENKINS-26293) email-ext-plugin FILE token macro apostrophe escaping

2015-01-05 Thread denisblanche...@gmail.com (JIRA)















































Denis Blanchette
 commented on  JENKINS-26293


email-ext-plugin FILE token macro apostrophe escaping















Great! Thank you for the fast reply.



























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] [github-oauth-plugin] (JENKINS-23672) Jobs page load takes ages when "Use Github repository permissions" is checked















































alex rothenberg
 commented on  JENKINS-23672


Jobs page load takes ages when "Use Github repository permissions" is checked















Fixed with github PR and merged into master - https://github.com/jenkinsci/github-oauth-plugin/commit/08912451c6dc7b33977a1755aecb6836b5378902. Not sure it has been released in a new version of the plugin yet.

Duplicate of JENKINS-24069



























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] [instant-messaging-plugin] (JENKINS-6560) Plugin should use project.getFullDisplayName() instead of project.getName()

2015-01-05 Thread ku...@gmx.de (JIRA)















































kutzi
 commented on  JENKINS-6560


Plugin should use project.getFullDisplayName() instead of project.getName()















Can you please exactly describe what you're seeing vs what would you expect? Ideally with steps how to reproduce it with a minimal matrix job.

Sorry, I don't use any matrix jobs personally, so I'm not into the material.



























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] [junit-plugin] (JENKINS-26276) Expose JUnit test results to workflow scripts

2015-01-05 Thread a...@bedatadriven.com (JIRA)















































Alexander Bertram
 commented on  JENKINS-26276


Expose JUnit test results to workflow scripts















Pull request here: https://github.com/jenkinsci/junit-plugin/pull/9
There seems to be an issue with the commit status: the 'default' context has been set to pending but 'jenkins' context is set to success.
The pull request does seem to have been successfully built however:
https://jenkins.ci.cloudbees.com/job/plugins/job/junit-plugin/36/



























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] [instant-messaging-plugin] (JENKINS-6560) Plugin should use project.getFullDisplayName() instead of project.getName()