date:20141114















































Ulli Hafner
 updated  JENKINS-23239


Test failures running mvn install on source
















Change By:


Ulli Hafner
(14/Nov/14 10:01 AM)




Component/s:


core





Component/s:


lockable-resources-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] [maven-plugin] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2014-11-14 Thread maik.eb...@gmail.com (JIRA)















































Maik Ebert
 commented on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted















We also suffer from this problem.

Is there any workaround available?



























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-23239) Test failures running mvn install on source















































Ulli Hafner
 commented on  JENKINS-23239


Test failures running mvn install on source















This happens to all plug-ins that use JUnit rule in Java 8 environment:
{nocode}
@Rule
public JenkinsRule jenkins = new JenkinsRule();{nocode}



























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-23239) Test failures running mvn install on source

2014-11-14 Thread dieter.sedlma...@thermofisher.com (JIRA)













































 
Ulli Hafner
 edited a comment on  JENKINS-23239


Test failures running mvn install on source
















This happens to all plug-ins that use JUnit rule in Java 8 environment:

@Rule
public JenkinsRule jenkins = new JenkinsRule();




























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] [log-parser-plugin] (JENKINS-25614) Parsed errors and warnings are no exposed by REST api















































Dieter Sedlmayer
 created  JENKINS-25614


Parsed errors and warnings are no exposed by REST api















Issue Type:


Bug



Assignee:


rgoren



Components:


log-parser-plugin



Created:


14/Nov/14 10:33 AM



Description:


There is currently no way to retrieve the number of errors using the REST api, although the build summary lists them.




Environment:


Log-Parser-Plugin 1.0.8




Project:


Jenkins



Priority:


Major



Reporter:


Dieter Sedlmayer

























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] [plugin-proposals] (JENKINS-14087) ScriptTrigger plugin timer issue

2014-11-14 Thread lyubo.ray...@gmail.com (JIRA)















































Lyubomir Raykov
 commented on  JENKINS-14087


ScriptTrigger plugin timer issue















In our environment we experienced the same issue. It happens when the process which the trigger was running freezes.
In our case the Shell script from the trigger runs a Java tool which freezes and the triggers for all jobs stop.
When the process is killed, the triggers start running 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] [email-ext-plugin] (JENKINS-23990) Output more helpful messages for cases where emails can't or won't be sent

2014-11-14 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-23990


Output more helpful messages for cases where emails cant or wont be sent















Would it be helpful to write to the Jenkins logs instead of the build log? The concern is that if you log the information from the exception to the build log, it could contain information that users shouldn't necessarily see (mail server info, etc).



























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-25609) Build Queue is not being processed! Jobs Queueing up....
















































Daniel Beck
 resolved  JENKINS-25609 as Not A Defect


Build Queue is not being processed! Jobs Queueing up
















This is an issue tracker, not a support website. Please direct requests for assistance to the jenkinsci-users mailing list, or #jenkins on Freenode.





Change By:


Daniel Beck
(14/Nov/14 11:22 AM)




Status:


Open
Resolved





Resolution:


NotADefect



























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-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source















































Daniel Beck
 commented on  JENKINS-25606


PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source















Does it work with JDK 7? Is it the Oracle JDK or something more exotic?



























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] [gerrit-trigger-plugin] (JENKINS-25615) extra '/' getting added in the generated url for finding files in a given commit

2014-11-14 Thread anjan.tummalapa...@gmail.com (JIRA)















































Anjan Kumar
 created  JENKINS-25615


extra / getting added in the generated url for finding files in a given commit















Issue Type:


Bug



Assignee:


rsandell



Components:


gerrit-trigger-plugin



Created:


14/Nov/14 12:01 PM



Description:


Hi Rebert Sandell,

We are using gerrit (V2.10-rc0) as code review system and jenkins as build system. Trying to enable continuous integration for one of our projects.

Able to poll commits and query commits in gerrit from jenkins machine itself but facing blocker issue with the URL getting generated in CI job for finding files which are modified in a commit.

sample generated URL provided below

/http://jenkins  URL//a/changes/Id6d6768940833dbe046ba0bf484021f0955/revisions/93e67a23abd1877905dff2b8ee1f5f85c23/files/

exact issue is getting url//a/changes instead of url/a/changes

and failing with error
Request  1: GET to /http://gerrit.gainsight.com:8080//a/changes/Id6d6768940833dbe045e6496ba0bf484021f0955/revisions/93e67afeabb23abd1877905dff2b8ee1f5f85c23/files/
pl.touk.sonar.GerritPluginException: Error listing files

Can you please help me in resolving this issue..




Environment:


gerrit trigger (V2.11.1), Jenkins (V1.577)




Project:


Jenkins



Priority:


Blocker



Reporter:


Anjan Kumar

























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] [p4-plugin] (JENKINS-25554) Latest P4 plugin dies with IndexOutOfBoundsException















































Paul Allen
 commented on  JENKINS-25554


Latest P4 plugin dies with IndexOutOfBoundsException















I recently discovered the Workshop object was getting trampled in multi configuration projects or parallel execution.  So made a change to clone the object in 1.0.20, however I forgot one method.  I fixed this yesterday in 1.0.21.  The org.jenkinsci.plugins.p4.PerforceScm.setBuildLabel method has now gone.

Please can you try the latest (1.0.21) and if you find any issues post an updated stack trace.



























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] [p4-plugin] (JENKINS-25547) Clients on slave nodes are not auto-created
















































Paul Allen
 closed  JENKINS-25547 as Fixed


Clients on slave nodes are not auto-created
















1.0.21





Change By:


Paul Allen
(14/Nov/14 12:02 PM)




Status:


Open
Closed





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] [p4-plugin] (JENKINS-25556) Deploy p4jenkins test artifact















































Paul Allen
 commented on  JENKINS-25556


Deploy p4jenkins test artifact















Hi Dan,

Just checking what you mean by test artifacts? My tests for p4-plugin, the p4d executables in the 'src/test/resources/r14.1/bin./p4d'?

... and by deploy do you mean? Upload them to maven in some way? They are already on our FTP site and I have a copy in the Workshop  GitHub.

Thanks,
Paul 



























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] [jacoco-plugin] (JENKINS-25616) Support for coverage.xml generated by Android tools

2014-11-14 Thread a...@90a.nl (JIRA)















































Arno Moonen
 created  JENKINS-25616


Support for coverage.xml generated by Android tools















Issue Type:


Improvement



Assignee:


Ognjen Bubalo



Components:


jacoco-plugin



Created:


14/Nov/14 12:11 PM



Description:


When running gradle createDebugCoverageReport on an Android Gradle project, the built-in JaCoCo support builds an HTML report and an XML report.
As far as I know it is not possible to use this with Jenkins CI at the moment, because the plug-in wants the .exec file.

The report XML file starts with the following lines (looks like a standard format?):


?xml version="1.0" encoding="UTF-8" standalone="yes"?
!DOCTYPE report PUBLIC "-//JACOCO//DTD Report 1.0//EN" "report.dtd"
report name="debug"
sessioninfo id="unknownhost-a0d58b54" start="1415952183361" dump="1415952207146"/


I would love to see support for this in the Jenkins CI JaCoCo plug-in.

https://github.com/jenkinsci/jacoco-plugin/issues/49




Environment:


Android Gradle project




Project:


Jenkins



Priority:


Major



Reporter:


Arno Moonen

























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] [p4-plugin] (JENKINS-25491) Stack trace when attempting to delete P4 enabled job















































Paul Allen
 commented on  JENKINS-25491


Stack trace when attempting to delete P4 enabled job















Sorry for the delay, I have been a little bit swamped at the moment.  

Please can you send my the stack trace and I'll see if I can reproduce it here.



























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] [release-plugin] (JENKINS-25617) Support for remote triggering parameterized release builds

2014-11-14 Thread andreas.hochste...@gmail.com (JIRA)















































Andreas Hochsteger
 created  JENKINS-25617


Support for remote triggering parameterized release builds















Issue Type:


New Feature



Assignee:


Peter Hayes



Components:


release-plugin



Created:


14/Nov/14 12:43 PM



Description:


Currently it is possible to automatically trigger parameterized builds (as described in https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin) but not for release builds.
We would need it to automatically trigger a release build if a new tag has been pushed to the git repository.




Project:


Jenkins



Priority:


Major



Reporter:


Andreas Hochsteger

























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] [p4-plugin] (JENKINS-25602) Testing connection to an SSL server fails with 'Connection Error.'















































Paul Allen
 commented on  JENKINS-25602


Testing connection to an SSL server fails with Connection Error.















Thanks Rob for re-posting...

Looking into it 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] [p4-plugin] (JENKINS-25602) Testing connection to an SSL server fails with 'Connection Error.'















































SCM/JIRA link daemon
 commented on  JENKINS-25602


Testing connection to an SSL server fails with Connection Error.















Code changed in jenkins
User: Paul Allen
Path:
 src/main/java/org/jenkinsci/plugins/p4/client/ConnectionFactory.java
http://jenkins-ci.org/commit/p4-plugin/eee04714261f4cade97643fa73a5ce6efd365ee9
Log:
  SSL not adding trust.

JENKINS-25602





























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] [pretested-integration-plugin] (JENKINS-25618) Use standard commit message when the squash strategy is used

2014-11-14 Thread m...@praqma.net (JIRA)















































Mads Nielsen
 created  JENKINS-25618


Use standard commit message when the squash strategy is used















Issue Type:


Bug



Assignee:


Praqma Support



Components:


pretested-integration-plugin



Created:


14/Nov/14 1:13 PM



Description:


We should just re-use the perfectly fine commit message genearated when using the squash startegy.




Project:


Jenkins



Priority:


Minor



Reporter:


Mads Nielsen

























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] [p4-plugin] (JENKINS-25553) Unable to utilize the allwrite feature with static workspaces















































Paul Allen
 commented on  JENKINS-25553


Unable to utilize the allwrite feature with static workspaces















I think this is fixed: 


// Set clobber on to ensure workspace is always good
ClientOptions options = new ClientOptions();
options.setClobber(true);
iclient.setOptions(options);


changed to...


// Set clobber on to ensure workspace is always good
IClientOptions options = iclient.getOptions();
options.setClobber(true);
iclient.setOptions(options);


The old code created a 'new' object and would overwrite the settings.



























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] [p4-plugin] (JENKINS-25553) Unable to utilize the allwrite feature with static workspaces
















































Paul Allen
 closed  JENKINS-25553 as Fixed


Unable to utilize the allwrite feature with static workspaces
















1.0.21





Change By:


Paul Allen
(14/Nov/14 1:17 PM)




Status:


Open
Closed





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] [p4-plugin] (JENKINS-25491) Stack trace when attempting to delete P4 enabled job















































Paul Allen
 commented on  JENKINS-25491


Stack trace when attempting to delete P4 enabled job















I have not been able to reproduce this on OS X; I'll need to spin up a VM environment to see if this is Windows specific.

The processWorkspaceBeforeDeletion() function attempts to unsync code from your workspace.  However, even if this fails the delete should succeed.




























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] [disk-usage-plugin] (JENKINS-24627) ConcurrentModificationException with DiskUsage

2014-11-14 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-24627


ConcurrentModificationException with DiskUsage
















Nov 14, 2014 12:42:15 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate
Caught exception evaluating: from.getSizeInString(from.getJobRootDirDiskUsage()) in /view/Infrastructure/job/super-job/. Reason: java.util.ConcurrentModificationException
java.util.ConcurrentModificationException
	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:922)
	at java.util.HashMap$KeyIterator.next(HashMap.java:956)
	at hudson.plugins.disk_usage.ProjectDiskUsageAction.getBuildsDiskUsage(ProjectDiskUsageAction.java:232)
	at hudson.plugins.disk_usage.ProjectDiskUsageAction.getBuildsDiskUsage(ProjectDiskUsageAction.java:203)
	at hudson.plugins.disk_usage.ProjectDiskUsageAction.getJobRootDirDiskUsage(ProjectDiskUsageAction.java:134)
	at sun.reflect.GeneratedMethodAccessor676.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
	at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
	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.ASTExpression.value(ASTExpression.java:54)
	at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:81)
	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.impl.ExpressionScript.run(ExpressionScript.java:66)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
	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$1.run(CoreTagLibrary.java:98)
	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.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.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.ForEachTag.doTag(ForEachTag.java:150)
	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.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
	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.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.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.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
	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

[JIRA] [xshell-plugin] (JENKINS-25600) XShell does not kill running process if job is getting aborted

2014-11-14 Thread hsku...@gmail.com (JIRA)















































Henrik Skupin
 commented on  JENKINS-25600


XShell does not kill running process if job is getting aborted















Ok, I was able to get XShell built on my own and I checked a build before and after the above landed PR. As I'm able to see the broken behavior as reported here is really caused by your patch from PR #8.



























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] [youtrack-plugin] (JENKINS-24333) No action for executing command from build step

2014-11-14 Thread nup...@gmx.at (JIRA)

Wolfgang Ziegler
edited a comment on JENKINS-24333

No action for executing command from build step

Thanks, I tested the experiemental plugin.

Having the YOUTRACK_CHANGES variables is great and it seems to generally work except for the option "find issues ids in text" as it still parses the wrong issue IDs for me. I tried it with the YOUTRACK_CHANGES variable as well as with customly entered text - it always parses the issue ID "XYZ" instead of "#XYZ-123". I tried it with DEV and ORD prefixes, but obviously the project shortnames do not matter - the number is always missing while the prefix is parsed. E.g., it tried to post to the youtrack issue "DEV" and "ORD" what obviously fails.

When I enter an issue ID in the search query, it's working as it should.

I'm curious, is that YOUTRACK_CHANGES variable now available in all build steps as well or just for those youtrack plugin related settings?

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-25619) The connection was interrupted - issue with TSL

2014-11-14 Thread pawel.grzegrzo...@gmail.com (JIRA)















































Pawel Grzegrzolka
 created  JENKINS-25619


The connection was interrupted - issue with TSL















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


14/Nov/14 1:56 PM



Description:


I'm running Jenkins directly (via jetty) and have some problem with a SSL connection. I have signed Jenkins.crt certificate. 
I've imported it to keystore with a following command:

keytool -keystore keystore -import -alias jetty -file Jenkins.crt -trustcacerts



In jenkins.xml I use created keystore:

--httpsKeyStore="keystore" --httpsKeyStorePassword="xxx" --httpPort=8080 --httpsPort=443



Unfortunately SSL connection doesn't work, since it works fine with http.
IE shows error message 'This page can't be displayed' and Firefox complains as well 'The connection was interrupted'.

Jenkins doesn't show valuable information in the jenkins.err.log file:

INFO: Loaded all jobs
Nov 14, 2014 2:36:29 PM org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac: display name [Root WebApplicationContext]; startup date [Fri Nov 14 14:36:29 CET 2014]; root of context hierarchy
Nov 14, 2014 2:36:29 PM org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]: org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f
Nov 14, 2014 2:36:29 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f: defining beans [authenticationManager]; root of factory hierarchy
Nov 14, 2014 2:36:29 PM org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@7f02e185: display name [Root WebApplicationContext]; startup date [Fri Nov 14 14:36:29 CET 2014]; root of context hierarchy
Nov 14, 2014 2:36:29 PM org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]: org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba
Nov 14, 2014 2:36:29 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba: defining beans [filter,legacy]; root of factory hierarchy



It looks like some error with SSL in Jenkins.
I've tried to investigate it a little bit, so I saw that connection is OK with TLS1:

openssl s_client -connect 1.2.3.4:443 -prexit
Loading 'screen' into random state - done
CONNECTED(0154)
10120:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:./ssl/s23_lib.c:188:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 124 bytes
---
New, (NONE), Cipher is (NONE)
Compression: NONE
Expansion: NONE



With a DTLS1 it works fine:

openssl s_client   -connect 1.2.3.4:443 -dtls1 -prexit
Loading 'screen' into random state - done
CONNECTED(01DC)
write:errno=10054
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 0 bytes
---
New, (NONE), Cipher is (NONE)
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol  : unknown
Cipher: 
Session-ID:
Session-ID-ctx:
Master-Key:
Key-Arg   : None
Start Time: 1415973203
Timeout   : 7200 (sec)
Verify return code: 0 (ok)
---






Environment:


Jenkins: 1.583

Server: Windows Server 2013 R2

container: jetty

Installed: as a service

Web browser: IE10, Firefox 32.0

JAVA: Oracle JRE 1.7.0_60

[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables















































SCM/JIRA link daemon
 commented on  JENKINS-25501


Results not being propagated to ENV variables















Code changed in jenkins
User: Ulli Hafner
Path:
 src/test/java/plugins/AbstractAnalysisTest.java
 src/test/java/plugins/CheckStylePluginTest.java
 src/test/java/plugins/FindbugsPluginTest.java
 src/test/java/plugins/PmdPluginTest.java
 src/test/java/plugins/TaskScannerPluginTest.java
 src/test/java/plugins/WarningsPluginTest.java
http://jenkins-ci.org/commit/acceptance-test-harness/0fb931ed5147e9adf9bbd0449a549346d8eb
Log:
  JENKINS-25501 Added test case verifying that tokens are correctly produced and consumed.





























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] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables
















































Ulli Hafner
 resolved  JENKINS-25501 as Cannot Reproduce


Results not being propagated to ENV variables
















I finally managed it to set up some test cases. All tests are running quite well, so I think we are talking about different things in this issue. The analysis plugins only produce tokens for the token macro plugin. These tokens can then be consumed by supporting plugins (like email-ext). I.e. you can use ${WARNINGS_COUNT} as content of the mail subject or body. These tokens are not available as environment variables.  





Change By:


Ulli Hafner
(14/Nov/14 2:04 PM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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-25619) The connection was interrupted - issue with TSL

2014-11-14 Thread pawel.grzegrzo...@gmail.com (JIRA)















































Pawel Grzegrzolka
 updated  JENKINS-25619


The connection was interrupted - issue with TSL
















Change By:


Pawel Grzegrzolka
(14/Nov/14 2:26 PM)




Description:


ImrunningJenkinsdirectly(viajetty)andhavesomeproblemwithaSSLconnection.IhavesignedJenkins.crtcertificate.Iveimportedittokeystorewithafollowingcommand:{noformat}keytool-keystorekeystore-import-aliasjetty-fileJenkins.crt-trustcacerts{noformat}Injenkins.xmlIusecreatedkeystore:{noformat}--httpsKeyStore=keystore--httpsKeyStorePassword=xxx--httpPort=8080--httpsPort=443{noformat}UnfortunatelySSLconnectiondoesntwork,sinceitworksfinewithhttp.IEshowserrormessageThispagecantbedisplayedandFirefoxcomplainsaswellTheconnectionwasinterrupted.Jenkinsdoesntshowvaluableinformationinthejenkins.err.logfile:{noformat}INFO:LoadedalljobsNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@5962f7ac:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]:org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24fNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f:definingbeans[authenticationManager];rootoffactoryhierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@7f02e185:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]:org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0baNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba:definingbeans[filter,legacy];rootoffactoryhierarchy{noformat}ItlookslikesomeerrorwithSSLinJenkins.Ivetriedtoinvestigateitalittlebit,soIsawthatconnectionisOKwithTLS1:{noformat}openssls_client-connect
1
165
.
2
114
.
3
164
.
4
100
:443-
prexit
state-bugs-debug
Loadingscreenintorandomstate-doneCONNECTED(0154)
10120
SSL_connect
:
before/connectinitializationwriteto0x1f21d90[0x1f21dd8](108bytes=108(0x6C))-806a010301005100-1039.jQ..9..0010-38351600-00130a0700c08..50020-3332-2f0705008003..3..2../...0030-00800504-010080150040-120906004000-00141108..@.0050-06040080-0302008051bc7a43Q.zC0060-2310484d7a4f2172-9c4ba830#.HMzO!r.K.0SSL_connect:SSLv2/v3writeclienthelloAreadfrom0x1f21d90[0x1f27338](7bytes=0(0x0))7944:
error:140790E5:SSLroutines:SSL23_WRITE:sslhandshakefailure:./ssl/s23_lib.c:188:
---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten124bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONE
{noformat}WithaDTLS1
itworksfine
differenterroroccurs
:{noformat}openssls_client-connect1.2.3.4:443-dtls1-prexitLoadingscreenintorandomstate-doneCONNECTED(01DC)write:errno=10054---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten0bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONESSL-Session:Protocol:unknownCipher:Session-ID:Session-ID-ctx:Master-Key:Key-Arg:NoneStartTime:1415973203Timeout:7200(sec)Verifyreturncode:0(ok)---{noformat}



























This message is

[JIRA] [core] (JENKINS-25619) The connection was interrupted - issue with TSL

2014-11-14 Thread pawel.grzegrzo...@gmail.com (JIRA)















































Pawel Grzegrzolka
 updated  JENKINS-25619


The connection was interrupted - issue with TSL
















Change By:


Pawel Grzegrzolka
(14/Nov/14 2:27 PM)




Description:


ImrunningJenkinsdirectly(viajetty)andhavesomeproblemwithaSSLconnection.IhavesignedJenkins.crtcertificate.Iveimportedittokeystorewithafollowingcommand:{noformat}keytool-keystorekeystore-import-aliasjetty-fileJenkins.crt-trustcacerts{noformat}Injenkins.xmlIusecreatedkeystore:{noformat}--httpsKeyStore=keystore--httpsKeyStorePassword=xxx--httpPort=8080--httpsPort=443{noformat}UnfortunatelySSLconnectiondoesntwork,sinceitworksfinewithhttp.IEshowserrormessageThispagecantbedisplayedandFirefoxcomplainsaswellTheconnectionwasinterrupted.Jenkinsdoesntshowvaluableinformationinthejenkins.err.logfile:{noformat}INFO:LoadedalljobsNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@5962f7ac:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]:org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24fNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f:definingbeans[authenticationManager];rootoffactoryhierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@7f02e185:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]:org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0baNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba:definingbeans[filter,legacy];rootoffactoryhierarchy{noformat}ItlookslikesomeerrorwithSSLinJenkins.Ivetriedtoinvestigateitalittlebit,soIsawthatconnectionisOKwithTLS1:{noformat}openssls_client-connect165.114.164.100:443-state-
bugs-
debug
-prexit
Loadingscreenintorandomstate-doneCONNECTED(0154)SSL_connect:before/connectinitializationwriteto0x1f21d90[0x1f21dd8](108bytes=108(0x6C))-806a010301005100-1039.jQ..9..0010-38351600-00130a0700c08..50020-3332-2f0705008003..3..2../...0030-00800504-010080150040-120906004000-00141108..@.0050-06040080-0302008051bc7a43Q.zC0060-2310484d7a4f2172-9c4ba830#.HMzO!r.K.0SSL_connect:SSLv2/v3writeclienthelloAreadfrom0x1f21d90[0x1f27338](7bytes=0(0x0))7944:error:140790E5:SSLroutines:SSL23_WRITE:sslhandshakefailure:./ssl/s23_lib.c:188:
---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten108bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONE
{noformat}WithaDTLS1differenterroroccurs:{noformat}openssls_client-connect1.2.3.4:443-dtls1-prexitLoadingscreenintorandomstate-doneCONNECTED(01DC)write:errno=10054---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten0bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONESSL-Session:Protocol:unknownCipher:Session-ID:Session-ID-ctx:Master-Key:Key-Arg:NoneStartTime:1415973203Timeout:7200(sec)Verifyreturncode:0(ok)---{noformat}



























This message is automatically generated by JIRA.

[JIRA] [core] (JENKINS-25619) The connection was interrupted - issue with TSL

2014-11-14 Thread pawel.grzegrzo...@gmail.com (JIRA)















































Pawel Grzegrzolka
 updated  JENKINS-25619


The connection was interrupted - issue with TSL
















Change By:


Pawel Grzegrzolka
(14/Nov/14 2:31 PM)




Description:


ImrunningJenkinsdirectly(viajetty)andhavesomeproblemwithaSSLconnection.IhavesignedJenkins.crtcertificate.Iveimportedittokeystorewithafollowingcommand:{noformat}keytool-keystorekeystore-import-aliasjetty-fileJenkins.crt-trustcacerts{noformat}Injenkins.xmlIusecreatedkeystore:{noformat}--httpsKeyStore=keystore--httpsKeyStorePassword=xxx--httpPort=8080--httpsPort=443{noformat}UnfortunatelySSLconnectiondoesntwork,sinceitworksfinewithhttp.IEshowserrormessageThispagecantbedisplayedandFirefoxcomplainsaswellTheconnectionwasinterrupted.Jenkinsdoesntshowvaluableinformationinthejenkins.err.logfile:{noformat}INFO:LoadedalljobsNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@5962f7ac:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]:org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24fNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f:definingbeans[authenticationManager];rootoffactoryhierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@7f02e185:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]:org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0baNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba:definingbeans[filter,legacy];rootoffactoryhierarchy{noformat}ItlookslikesomeerrorwithSSLinJenkins.Ivetriedtoinvestigateitalittlebit,soIsawthatconnection
isOK
doesntwork
withTLS1:{noformat}openssls_client-connect165.114.164.100:443-state-debug-prexitLoadingscreenintorandomstate-doneCONNECTED(0154)SSL_connect:before/connectinitializationwriteto0x1f21d90[0x1f21dd8](108bytes=108(0x6C))-806a010301005100-1039.jQ..9..0010-38351600-00130a0700c08..50020-3332-2f0705008003..3..2../...0030-00800504-010080150040-120906004000-00141108..@.0050-06040080-0302008051bc7a43Q.zC0060-2310484d7a4f2172-9c4ba830#.HMzO!r.K.0SSL_connect:SSLv2/v3writeclienthelloAreadfrom0x1f21d90[0x1f27338](7bytes=0(0x0))7944:error:140790E5:SSLroutines:SSL23_WRITE:sslhandshakefailure:./ssl/s23_lib.c:188:---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten108bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONE{noformat}WithaDTLS1differenterroroccurs:{noformat}openssls_client-connect1.2.3.4:443-dtls1-prexitLoadingscreenintorandomstate-doneCONNECTED(01DC)write:errno=10054---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten0bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONESSL-Session:Protocol:unknownCipher:Session-ID:Session-ID-ctx:Master-Key:Key-Arg:NoneStartTime:1415973203Timeout:7200(sec)Verifyreturncode:0(ok)---{noformat}



























This message is automatically generated by JIRA.

[JIRA] [core] (JENKINS-25619) The connection was interrupted - issue with TSL

2014-11-14 Thread pawel.grzegrzo...@gmail.com (JIRA)















































Pawel Grzegrzolka
 updated  JENKINS-25619


The connection was interrupted - issue with TSL
















Change By:


Pawel Grzegrzolka
(14/Nov/14 2:32 PM)




Description:


ImrunningJenkinsdirectly(viajetty)andhavesomeproblemwithaSSLconnection.IhavesignedJenkins.crtcertificate.Iveimportedittokeystorewithafollowingcommand:{noformat}keytool-keystorekeystore-import-aliasjetty-fileJenkins.crt-trustcacerts{noformat}Injenkins.xmlIusecreatedkeystore:{noformat}--httpsKeyStore=keystore--httpsKeyStorePassword=xxx--httpPort=8080--httpsPort=443{noformat}UnfortunatelySSLconnectiondoesntwork,sinceitworksfinewithhttp.IEshowserrormessageThispagecantbedisplayedandFirefoxcomplainsaswellTheconnectionwasinterrupted.Jenkinsdoesntshowvaluableinformationinthejenkins.err.logfile:{noformat}INFO:LoadedalljobsNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@5962f7ac:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]:org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24fNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f:definingbeans[authenticationManager];rootoffactoryhierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@7f02e185:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]:org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0baNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba:definingbeans[filter,legacy];rootoffactoryhierarchy{noformat}ItlookslikesomeerrorwithSSLinJenkins.Ivetriedtoinvestigateitalittlebit,soIsawthatconnectiondoesntworkwithTLS1:{noformat}openssls_client-connect
165
1
.
114
2
.
164
3
.
100
4
:443-state-debug-prexitLoadingscreenintorandomstate-doneCONNECTED(0154)SSL_connect:before/connectinitializationwriteto0x1f21d90[0x1f21dd8](108bytes=108(0x6C))-806a010301005100-1039.jQ..9..0010-38351600-00130a0700c08..50020-3332-2f0705008003..3..2../...0030-00800504-010080150040-120906004000-00141108..@.0050-06040080-0302008051bc7a43Q.zC0060-2310484d7a4f2172-9c4ba830#.HMzO!r.K.0SSL_connect:SSLv2/v3writeclienthelloAreadfrom0x1f21d90[0x1f27338](7bytes=0(0x0))7944:error:140790E5:SSLroutines:SSL23_WRITE:sslhandshakefailure:./ssl/s23_lib.c:188:---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten108bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONE{noformat}WithaDTLS1differenterroroccurs:{noformat}openssls_client-connect1.2.3.4:443-dtls1-prexitLoadingscreenintorandomstate-doneCONNECTED(01DC)write:errno=10054---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten0bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONESSL-Session:Protocol:unknownCipher:Session-ID:Session-ID-ctx:Master-Key:Key-Arg:NoneStartTime:1415973203Timeout:7200(sec)Verifyreturncode:0(ok)---{noformat}



























This message is automatically generated by JIRA.

[JIRA] [p4-plugin] (JENKINS-25491) Stack trace when attempting to delete P4 enabled job















































SCM/JIRA link daemon
 commented on  JENKINS-25491


Stack trace when attempting to delete P4 enabled job















Code changed in jenkins
User: Paul Allen
Path:
 src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java
http://jenkins-ci.org/commit/p4-plugin/88e6506c40754d5c9c562fd5e23e36fd2b9fc90a
Log:
  Prevent error when deleting unbuilt jobs.

If a job has no previous build it could fail with a null pointer.

JENKINS-25491





























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-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source















































Joshua Strouse
 commented on  JENKINS-25606


PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source















It is indeed the Oracle JDK. I haven't tried JDK 7 yet, but I will post my results when I do.



























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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.

2014-11-14 Thread koo...@mail.ru (JIRA)















































Oleksandr Kulychok
 commented on  JENKINS-25583


Unexpected error in launching a slave. This is probably a bug in Jenkins.















Please read this - https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control
 Starting 1.587 (and 1.580.1), Jenkins added a subsystem to put a wall between a master and a slave to safely allow less trusted slaves to be connected to a master.



























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] [selenium-plugin] (JENKINS-23563) Cannot Restart Selenium Plugin

2014-11-14 Thread koo...@mail.ru (JIRA)















































Oleksandr Kulychok
 commented on  JENKINS-23563


Cannot Restart Selenium Plugin















Do you login with anonymous user?



























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] [matrix-auth-plugin] (JENKINS-23297) when saving GlobalMatrixAuthorizationStrategy: ClassCastException: net.sf.json.JSONArray cannot be cast to java.lang.Boolean

2014-11-14 Thread jgl...@cloudbees.com (JIRA)
















































Jesse Glick
 resolved  JENKINS-23297 as Fixed


when saving GlobalMatrixAuthorizationStrategy: ClassCastException: net.sf.json.JSONArray cannot be cast to java.lang.Boolean
















Robustness fix: https://github.com/jenkinsci/matrix-auth-plugin/commit/c71bb80c1806d05126277a90e3a99ddb67f095d0





Change By:


Jesse Glick
(14/Nov/14 4:00 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] [repository-connector-plugin] (JENKINS-25620) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)















































Raphaël UNIQUE
 created  JENKINS-25620


Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)















Issue Type:


Bug



Assignee:


Dominik Bartholdi



Components:


repository-connector-plugin



Created:


14/Nov/14 4:10 PM



Description:


Dominik Bartholdi

Job fails after Repository Connector Plugin upgrade (0.8.2 - 1.0.1); please note that same artifact (with same artifact version) is resolved as expected with 0.8.2.

Stack trace:

2014-09-19 12:25:54 INFO  [bio-8080-exec-7] - org.sonatype.security.model.source.FileModelConfigurationSource - Loading security configuration from: /home/TECH/tomcat/sonatype-work/nexus/conf/security.xml
2014-09-19 12:25:55 INFO  [bio-8080-exec-7] - org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage - Initializing remote transport for proxy repository "oss-snapshots" [id=oss-snapshots]...
2014-09-19 12:25:55 INFO  [bio-8080-exec-7] - org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage - Initializing remote transport for proxy repository "Apache Snapshots" [id=apache-snapshots]...
2014-09-19 12:25:55 INFO  [bio-8080-exec-7] - org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage - Initializing remote transport for proxy repository "Codehaus Snapshots" [id=codehaus-snapshots]...
2014-09-19 12:25:55 INFO  [bio-8080-exec-7] - org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage - Initializing remote transport for proxy repository "scct" [id=scct]...
2014-09-19 12:25:56 INFO  [bio-8080-exec-7] - org.sonatype.nexus.velocity.VelocityEngineProvider - Creating Nexus VelocityEngine
Sep 19, 2014 12:25:56 PM org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver logError
SEVERE: failed to resolve dependency for [Artifact }]
org.sonatype.aether.resolution.DependencyResolutionException: Could not find  in nexus (/nexus/content/groups/public)
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
at org.jvnet.hudson.plugins.repositoryconnector.aether.Aether.resolve(Aether.java:157)
at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.download(ArtifactResolver.java:129)
at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.perform(ArtifactResolver.java:101)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
at hudson.model.Build$BuildExecution.build(Build.java:198)
at hudson.model.Build$BuildExecution.doRun(Build.java:159)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1706)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not find artifact * in nexus (/nexus/content/groups/public)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:537)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
... 12 more
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact * in nexus (/nexus/content/groups/public)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:971)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:966)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.flush(WagonRepositoryConnector.java:707)
at

[JIRA] [disk-usage-plugin] (JENKINS-22721) Project page has broken layout on smaller screens

2014-11-14 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-22721


Project page has broken layout on smaller screens















Hi, could you provide PR link? Seems this issue still exist.



























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] [repository-connector-plugin] (JENKINS-25620) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)















































Raphaël UNIQUE
 updated  JENKINS-25620


Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)
















Change By:


Raphaël UNIQUE
(14/Nov/14 4:11 PM)




Description:


[~imod]JobfailsafterRepositoryConnectorPluginupgrade(*0.8.2*-*1.0.1*);pleasenotethatsameartifact(withsameartifactversion)isresolvedasexpectedwith*0.8.2*.Stacktrace:{noformat}
2014-09-1912:25:54INFO[bio-8080-exec-7]-org
.
sonatype
.
security
.
model.source.FileModelConfigurationSource-Loadingsecurityconfigurationfrom:/home/TECH/tomcat/sonatype-work/nexus/conf/security.xml

2014-09-1912
INFO
:
25
definerepo
:
55INFO
[
bio
Repositoryid=nexus
-
8080-exec-7]-org.sonatype.
stef,type=default,url="">
nexus.
proxy
xxx
.
storage.remote.httpclient.HttpClientRemoteStorage-Initializingremotetransportforproxyrepositoryoss-snapshots[id
com/nexus/content/groups/public,isRepositoryManager
=
oss-snapshots
true
]
Resolvingmetadatacom
.
stef
.
.2014-09-1912
soa
:
25
bam
:
55INFO[bio-8080-exec-7]-org
1
.
sonatype
0
.
nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage
5
-
InitializingremotetransportforproxyrepositoryApacheSnapshots[id=apache
SNAPSHOT/maven
-
snapshots]
metadata
.
xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvedmetadatacom
.
stef
.
2014-09-1912
soa
:
25
bam
:
55INFO[bio-8080-exec-7]-org
1
.
sonatype
0
.
nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage
5
-
InitializingremotetransportforproxyrepositoryCodehausSnapshots[id=codehaus
SNAPSHOT/maven
-
snapshots]
metadata
.
xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvingartifactcom
.
stef
.
2014-09-1912
soa
:
25
bam
:
55INFO[bio-8080-exec-7]-org
pom:1
.
sonatype
0
.
nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage
5
-
Initializingremotetransportforproxyrepositoryscct[id=scct]
SNAPSHOTResolvingmetadatacom
.
stef
.
.2014-09-1912
soa
:
25
bam
:
56INFO[bio
1.0.5
-
8080
SNAPSHOT/maven
-
exec-7]-org
metadata
.
sonatype.nexus.velocity.VelocityEngineProvider
xmlfrom/tmp/repositoryconnector
-
CreatingNexusVelocityEngine
repo(enhanced)

Sep19,201412
Resolvedmetadatacom.stef.soa
:
25
bam
:
56PMorg
1
.
jvnet
0
.
hudson
5-SNAPSHOT/maven-metadata
.
plugins.
xmlfrom/tmp/
repositoryconnector
.ArtifactResolverlogError
-repo(enhanced)

SEVERE
Downloading
:
failedtoresolvedependencyfor[Artifact}]org.sonatype.aether.resolution.DependencyResolutionException
http
:
Couldnotfindin
//
nexus
(
.xxx.com
/

nexus/content/groups/public
)atorg
/com/stef/soa/bam/1
.
sonatype
0
.
aether
5-SNAPSHOT/bam-1
.
impl
0
.
internal
5-SNAPSHOT
.
DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
pom

atorg.jvnet.hudson.plugins.repositoryconnector.aether.Aether.resolve(Aether.java:157)

at
class
org.
jvnet
apache
.
hudson
maven
.
plugins
wagon
.
repositoryconnector.ArtifactResolver.download(ArtifactResolver.java
ResourceDoesNotExistException
:
129)
Unabletolocateresourceinrepository

atorg
Resolvedartifactcom
.
jvnet
stef
.
hudson.plugins.repositoryconnector.ArtifactResolver.perform(ArtifactResolver.java
soa
:
101)athudson.tasks.BuildStepMonitor$
bam:pom:
1.
perform(BuildStepMonitor
0
.
java:20)
5-SNAPSHOTfromnull

athudson
Missingartifactdescriptorforcom
.
model
stef
.
AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java
soa
:
756)athudson.model.Build$BuildExecution.build(Build.java
bam
:
198)athudson.model.Build$BuildExecution.doRun(Build.java
war
:
159)athudson
1
.
model
0
.
AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
5-SNAPSHOT

athudson
Resolvingartifactcom
.
model
stef
.
Run.execute(Run.java
soa
:
1706)athudson.model.FreeStyleBuild.run(FreeStyleBuild.java
bam
:
43)athudson
war:1
.
model
0
.
ResourceController.execute(ResourceController.java:88)
5-SNAPSHOT

athudson
Resolvingmetadatacom
.
model
stef
.
Executor.run(Executor.java
soa
:
232)Causedby
bam
:
org
1
.
sonatype
0
.
aether
5-SNAPSHOT/maven-metadata
.
resolution.ArtifactResolutionException:Couldnotfindartifact*innexus(
xmlfrom
/
nexus
tmp
/
content/groups/public)atorg.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve
repositoryconnector-repo
(
DefaultArtifactResolver.java:537
enhanced
)
atorg
Resolvedmetadatacom
.
sonatype
stef
.

[JIRA] [repository-connector-plugin] (JENKINS-25620) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)















































Raphaël UNIQUE
 updated  JENKINS-25620


Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)
















Change By:


Raphaël UNIQUE
(14/Nov/14 4:18 PM)




Description:


[~imod]JobfailsafterRepositoryConnectorPluginupgrade(*0.8.2*-*1.0.1*);pleasenotethatsameartifact(withsameartifactversion)isresolvedasexpectedwith*0.8.2*.Log:{noformat}...INFO:definerepo:[Repositoryid=nexus-xxx,type=default,url="">Resolvingmetadatacom.xxx.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvedmetadatacom.xxx.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvingartifactcom.xxx.soa:bam:pom:1.0.5-SNAPSHOTResolvingmetadatacom.xxx.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvedmetadatacom.xxx.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Downloading:http://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-SNAPSHOT.pomclassorg.apache.maven.wagon.ResourceDoesNotExistException:UnabletolocateresourceinrepositoryResolvedartifactcom.xxx.soa:bam:pom:1.0.5-SNAPSHOTfromnullMissingartifactdescriptorforcom.xxx.soa:bam:war:1.0.5-SNAPSHOTResolvingartifactcom.xxx.soa:bam:war:1.0.5-SNAPSHOTResolvingmetadatacom.xxx.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvedmetadatacom.xxx.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Downloading:http://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-SNAPSHOT.warclassorg.apache.maven.wagon.ResourceDoesNotExistException:UnabletolocateresourceinrepositoryResolvedartifactcom.xxx.soa:bam:war:1.0.5-SNAPSHOTfromnull...{noformat}theurlusedreturna404error:http://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-SNAPSHOT.pomifilookat:http://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/maven-metadata.xml,ihave:{noformat}metadatamodelVersion=1.1.0groupIdcom.
stef
xxx
.soa/groupIdartifactIdbam/artifactIdversion1.0.5-SNAPSHOT/versionversioningsnapshottimestamp20141112.110743/timestampbuildNumber5/buildNumber/snapshotlastUpdated20141112110743/lastUpdatedsnapshotVersionssnapshotVersionextensionwar/extensionvalue1.0.5-20141112.110743-5/valueupdated20141112110743/updated/snapshotVersionsnapshotVersionextensionpom/extensionvalue1.0.5-20141112.110743-5/valueupdated20141112110743/updated/snapshotVersion/snapshotVersions/versioning/metadata{noformat}so,theurlusedtodownloadthepomshouldbe:http://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-20141112.110743-5.pominsteadofhttp://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-SNAPSHOT.pomthatsthesameforthewarfile



























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] [repository-connector-plugin] (JENKINS-25620) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)















































Raphaël UNIQUE
 updated  JENKINS-25620


Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)
















Change By:


Raphaël UNIQUE
(14/Nov/14 4:17 PM)




Description:


[~imod]JobfailsafterRepositoryConnectorPluginupgrade(*0.8.2*-*1.0.1*);pleasenotethatsameartifact(withsameartifactversion)isresolvedasexpectedwith*0.8.2*.
Stacktrace
Log
:{noformat}...INFO:definerepo:[Repositoryid=nexus-
stef
xxx
,type=default,url="">Resolvingmetadatacom.
stef
xxx
.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvedmetadatacom.
stef
xxx
.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvingartifactcom.
stef
xxx
.soa:bam:pom:1.0.5-SNAPSHOTResolvingmetadatacom.
stef
xxx
.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvedmetadatacom.
stef
xxx
.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Downloading:http://nexus.xxx.com/nexus/content/groups/public/com/
stef
xxx
/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-SNAPSHOT.pomclassorg.apache.maven.wagon.ResourceDoesNotExistException:UnabletolocateresourceinrepositoryResolvedartifactcom.
stef
xxx
.soa:bam:pom:1.0.5-SNAPSHOTfromnullMissingartifactdescriptorforcom.
stef
xxx
.soa:bam:war:1.0.5-SNAPSHOTResolvingartifactcom.
stef
xxx
.soa:bam:war:1.0.5-SNAPSHOTResolvingmetadatacom.
stef
xxx
.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Resolvedmetadatacom.
stef
xxx
.soa:bam:1.0.5-SNAPSHOT/maven-metadata.xmlfrom/tmp/repositoryconnector-repo(enhanced)Downloading:http://nexus.xxx.com/nexus/content/groups/public/com/
stef
xxx
/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-SNAPSHOT.warclassorg.apache.maven.wagon.ResourceDoesNotExistException:UnabletolocateresourceinrepositoryResolvedartifactcom.
stef
xxx
.soa:bam:war:1.0.5-SNAPSHOTfromnull...{noformat}
theurlusedreturna404error:http://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-SNAPSHOT.pomifilookat:http://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/maven-metadata.xml,ihave:{noformat}metadatamodelVersion=1.1.0groupIdcom.stef.soa/groupIdartifactIdbam/artifactIdversion1.0.5-SNAPSHOT/versionversioningsnapshottimestamp20141112.110743/timestampbuildNumber5/buildNumber/snapshotlastUpdated20141112110743/lastUpdatedsnapshotVersionssnapshotVersionextensionwar/extensionvalue1.0.5-20141112.110743-5/valueupdated20141112110743/updated/snapshotVersionsnapshotVersionextensionpom/extensionvalue1.0.5-20141112.110743-5/valueupdated20141112110743/updated/snapshotVersion/snapshotVersions/versioning/metadata{noformat}so,theurlusedtodownloadthepomshouldbe:http://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-20141112.110743-5.pominsteadofhttp://nexus.xxx.com/nexus/content/groups/public/com/xxx/soa/bam/1.0.5-SNAPSHOT/bam-1.0.5-SNAPSHOT.pomthatsthesameforthewarfile



























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-23239) Test failures running mvn install on source

2014-11-14 Thread jgl...@cloudbees.com (JIRA)
















































Jesse Glick
 resolved  JENKINS-23239 as Duplicate


Test failures running mvn install on source
















To fix in this case it suffices to update:


diff --git a/pom.xml b/pom.xml
index 0f577be..4d7c73d 100644
--- a/pom.xml
+++ b/pom.xml
@@ -13,7 +13,7 @@
 	parent
 		groupIdorg.jenkins-ci.plugins/groupId
 		artifactIdplugin/artifactId
-		version1.509.4/version
+		version1.554.1/version
 	/parent
 
 	groupIdorg.6wind.jenkins/groupId






Change By:


Jesse Glick
(14/Nov/14 4:55 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] [delivery-pipeline-plugin] (JENKINS-25607) Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed

2014-11-14 Thread damien.corabo...@gmail.com (JIRA)















































Damien Coraboeuf
 commented on  JENKINS-25607


Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed















Error shows:


java.lang.NoSuchMethodError: au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.init(Ljava/lang/String;Ljava/lang/String;Lau/com/centrumsystems/hudson/plugin/buildpipeline/ProjectGridBuilder;Ljava/lang/String;ZLjava/lang/String;Z)V




























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] [selenium-plugin] (JENKINS-23563) Cannot Restart Selenium Plugin

2014-11-14 Thread koo...@mail.ru (JIRA)















































Oleksandr Kulychok
 commented on  JENKINS-23563


Cannot Restart Selenium Plugin















Current revision has bug - if hub was not started (due configuration error), it cannot be restarted. You can provide correct configuration and then restart jenkins server.
Now I try to fix this bug and soon I'll provide Pull request (it also fixes many other issues and extends hub's timeout configuration)



























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] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job

2014-11-14 Thread mcan...@coveo.com (JIRA)















































Mathieu Cantin
 commented on  JENKINS-25111


Ability to Copy Artifacts from a Phase Job















You may copy the files on the good workspace or in a shared. If the jobs run on the same server, you can use ${WORKSPACE} for determine the workspace of the MultiJob Build in sub build phase.



























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] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables

2014-11-14 Thread jstarb...@scisolutions.com (JIRA)















































Jon Starbird
 commented on  JENKINS-25501


Results not being propagated to ENV variables















Ok. I didn't know that. However, I put them into the email-ext one and still don't get the correct values. 
I'll try it again today.  I have all plugins you've mentioned and the latest versions, based on the Long-term Support Release of Jenkins.



























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] [multijob-plugin] (JENKINS-25458) Version 1.14 forces a git checkout? unknown reasons

2014-11-14 Thread mcan...@coveo.com (JIRA)















































Mathieu Cantin
 commented on  JENKINS-25458


Version 1.14 forces a git checkout? unknown reasons















Do you have this problem with the 1.13? And do you check the "Build only if SCM changes" option?



























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-25528) Reboot dialog displayed during MSI installation when upgrading

2014-11-14 Thread malliina...@gmail.com (JIRA)















































Michael Skogberg
 commented on  JENKINS-25528


Reboot dialog displayed during MSI installation when upgrading















I discovered that if I make the MSI installation non-interactive by removing all UI elements from the .wxs file, the installation will not prompt for a reboot and will stop the previously running service as expected.



























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] [nodelabelparameter-plugin] (JENKINS-25622) NodeLabelParameter plugin

2014-11-14 Thread mbells.w...@gmail.com (JIRA)















































Matthew Bells
 created  JENKINS-25622


NodeLabelParameter plugin















Issue Type:


Bug



Assignee:


Dominik Bartholdi



Attachments:


Screenshot-Jenkins_NodeLabel_build_params.png, Screenshot-Jenkins_NodeLabel_build_queue.png



Components:


nodelabelparameter-plugin



Created:


14/Nov/14 5:48 PM



Description:


This plugin will break many APIs and other plugins when there is a job in the queue.

The queue parameter is missing the 'value' entry that is sent from Jenkins through JSON. See output after build.actions below.

- Steps to reproduce
Install Jenkins, install NodeLabelPlugin. (See environment for exact version info)
Create a job that uses the NodeLabelPlugin.
Build with Parameters, and fill in some some parameters (see screenshot).
Take a look at the queue (see screenshot).
Install Python jenkinsapi (using 0.2.16-2):
apt-get install python-jenkinsapi
Type in the following commands:

 import jenkinsapi
 jenkinsurl='http://localhost:8080'
 jobname='MyJob'
 jenkins = jenkinsapi.jenkins.Jenkins(jenkinsurl)
 queue=jenkins.get_queue()
 queued_builds = queue.get_queue_items_for_job(jobname)
 build=queued_builds[0]
 build.actions
[{'parameters': [{'name': 'job_id', 'value': '0'}, {'name': 'node_label'}, {'name': 'content_id', 'value': ''}, {'name': 'config_id', 'value': ''}]}, {'causes': [{'userName': 'Matt', 'userId': 'mbells', 'shortDescription': 'Started by user Matt'}]}]
 for b in queued_builds:
...print (b, b.get_parameters())
Traceback (most recent call last):
  File "stdin", line 2, in module
  File "/usr/lib/python2.7/dist-packages/jenkinsapi/queue.py", line 97, in get_parameters
return dict([(x['name'], x['value']) for x in parameters])





Environment:


Jenkins ver. 1.554.3

nodelabelparameter plugin ver. 1.5.1

Host OS: Ubuntu 14.04

To get Python api:




Project:


Jenkins



Labels:


nodelabelparameter




Priority:


Major



Reporter:


Matthew Bells

























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] [multijob-plugin] (JENKINS-25458) Version 1.14 forces a git checkout? unknown reasons

2014-11-14 Thread mcan...@coveo.com (JIRA)













































 
Mathieu Cantin
 edited a comment on  JENKINS-25458


Version 1.14 forces a git checkout? unknown reasons
















Do you have this problem with the 1.13? And do you check the "Build only if SCM changes" option? If no, I think this bug was fixed in 1.15.



























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] [nodelabelparameter-plugin] (JENKINS-25622) NodeLabelParameter plugin is missing value parameter for queue jobs

2014-11-14 Thread mbells.w...@gmail.com (JIRA)















































Matthew Bells
 updated  JENKINS-25622


NodeLabelParameter plugin is missing value parameter for queue jobs
















Change By:


Matthew Bells
(14/Nov/14 5:50 PM)




Summary:


NodeLabelParameterplugin
ismissingvalueparameterforqueuejobs



























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] [workflow-plugin] (JENKINS-25623) timeout step should be able to kill infinite loop

2014-11-14 Thread k...@kohsuke.org (JIRA)















































Kohsuke Kawaguchi
 created  JENKINS-25623


timeout step should be able to kill infinite loop















Issue Type:


Improvement



Assignee:


Kohsuke Kawaguchi



Components:


workflow-plugin



Created:


14/Nov/14 6:06 PM



Description:


Timeout step is currently only able to interrupt executions that are pausing (such as the 'sh' step.)

It would be nice if it can also interrupt infinite loops like while(true) ; by magically throwing an exception.

To safely doing this without race seems to require that CpsThread.runNextChunk spontaneously return even without the CPS code explicitly yielding. When resuming, any abnormal Outcome should act as if it's throwing the exception, and normal Outcome should get ignored and its natural result should be used instead.

The spontaneous return could happen every N instructions. Or CpsTransformer can insert Block that does it, like HotSpot inserts safepoint checks at the beginning of every function and every loop.




Project:


Jenkins



Priority:


Major



Reporter:


Kohsuke Kawaguchi

























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] [p4-plugin] (JENKINS-25602) Testing connection to an SSL server fails with 'Connection Error.'

2014-11-14 Thread mdougl...@kixeye.com (JIRA)















































Matthew Douglass
 commented on  JENKINS-25602


Testing connection to an SSL server fails with Connection Error.















Build and tested 1.0.22-SNAPSHOT from source this morning, worked great.  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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source















































Joshua Strouse
 commented on  JENKINS-25606


PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source















I ran it with JDK 7 (1.7.0_71) and got the following failed/error tests:
Failure - SecretRewriterTest.recursionDetection:100 assert 6==sw.rewriteRecursive(t, st)
Error - RunTest.testParseTimestampFromBuildDir:109 InvalidDirectoryName Invalid directory
Error - DefaultConfidentialStoreTest.roundtrip:52 IO javax.crypto.BadPaddingException

I've attached the output as mvnout2.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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source















































Joshua Strouse
 updated  JENKINS-25606


PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
















Result of using JDK 7 instead of 8.





Change By:


Joshua Strouse
(14/Nov/14 6:14 PM)




Attachment:


mvnout2.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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source













































 
Joshua Strouse
 edited a comment on  JENKINS-25606


PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
















ignore



























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] [delivery-pipeline-plugin] (JENKINS-25607) Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed

2014-11-14 Thread pat...@diabol.se (JIRA)















































Patrik Boström
 updated  JENKINS-25607


Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed
















Change By:


Patrik Boström
(14/Nov/14 6:42 PM)




Priority:


Minor
Major



























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] [delivery-pipeline-plugin] (JENKINS-25607) Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed

2014-11-14 Thread pat...@diabol.se (JIRA)















































Patrik Boström
 commented on  JENKINS-25607


Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed















Have created a fix for it. Opened a PR:
https://github.com/Diabol/delivery-pipeline-plugin/pull/86



























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-25343) Dropdown Add parameter not working
















































Daniel Beck
 resolved  JENKINS-25343 as Cannot Reproduce


Dropdown Add parameter not working
















Change By:


Daniel Beck
(14/Nov/14 7:00 PM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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-11962) Symlinking lastSuccessful build shouldn't fail with concurrent jobs

2014-11-14 Thread rdrab...@cisco.com (JIRA)

Rebecca Drabenstott
updated JENKINS-11962

Symlinking lastSuccessful build shouldnt fail with concurrent jobs

I have reproduced this issue in Jenkins 1.588 running on Red Hat Enterprise Linux Server release 5.5 (Tikanga). It is using Java 1.6.0_21-b06 from Sun (Oracle). I’m not sure my company would be happy if I publicly posted the entire contents of /systemInfo, but if there are specific sections of interest, I could possibly remove the sensitive data and post them.

It seems that one job gets stuck trying (and ultimately failing) to create a symlink. While it is stuck, other jobs get stuck too. The instant the first job finishes, the other jobs finish too. The job in this example runs very quickly and also gets stuck for a fairly short period of time, but we have seen the same behavior in other jobs that normally run on the order of many seconds to many minutes and they can get stuck for up to 20 minutes.

In the screen shot that I have attached, you can see that jobs 1098516, 1098517, 1098518 took longer than the others. Job 1098516 failed to create the symlink. I’m attaching the console output of the three jobs. I’m also attaching part of the Jenkins error log. There is an error in the error log, but it is difficult to tell if it is related or not. It is a frequent error and in other examples of this issue, the error does not always occur immediately before the stuck jobs finish.

Change By:

Rebecca Drabenstott
(14/Nov/14 7:11 PM)

Attachment:

ScreenShot.png

Attachment:

bugchugger_cleanup_1098516.txt

Attachment:

bugchugger_cleanup_1098517.txt

Attachment:

bugchugger_cleanup_1098518.txt

Attachment:

error

[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.

2014-11-14 Thread neal.sto...@gmail.com (JIRA)















































Neal Storey
 commented on  JENKINS-25583


Unexpected error in launching a slave. This is probably a bug in Jenkins.















I upgraded those 3 plugins and enabled that under Global Security and the node still would come online. I believe it's related to the problem though.



























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] [matrix-combinations-parameter-plugin] (JENKINS-25624) CLI Support for build submission parameters

2014-11-14 Thread nthieb...@gmail.com (JIRA)















































Norbert Thiebaud
 created  JENKINS-25624


CLI Support for build submission parameters















Issue Type:


Improvement



Assignee:


Unassigned


Components:


matrix-combinations-parameter-plugin



Created:


14/Nov/14 7:33 PM



Description:


when trying to start a job using ssh on get

$ ssh my_jenkins build my_job -f -p Platform=MacOSX,Windows -p GitRef=master
CLI parameter submission is not supported for the class hudson.plugins.matrix_configuration_parameter.MatrixCombinationsParameterDefinition type. Please file a bug report for this

so.. here is the filing 




Project:


Jenkins



Labels:


plugin
api




Priority:


Minor



Reporter:


Norbert Thiebaud

























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-25625) SECURITY-144-compat usage breaks tests due to code signing

2014-11-14 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 created  JENKINS-25625


SECURITY-144-compat usage breaks tests due to code signing















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


14/Nov/14 7:55 PM



Description:


Take a plugin which has a dependency on maven-plugin, such as copyartifact. Now update the dependency to 2.7.1 and try to run functional tests. Everything blows up:


=== Starting CopyArtifactTest.testMavenJobWithArchivePostBuildStep
... hudson.model.AbstractBuild$AbstractBuildExecution reportError
WARNING: Publisher hudson.tasks.ArtifactArchiver aborted due to exception
java.lang.SecurityException: class "org.jenkinsci.remoting.CallableDecorator"'s signer information does not match signer information of other classes in the same package
	at java.lang.ClassLoader.checkCerts(ClassLoader.java:952)
	at java.lang.ClassLoader.preDefineClass(ClassLoader.java:666)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:794)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
	at jenkins.FilePathFilter.current(FilePathFilter.java:108)
	at hudson.FilePath.reading(FilePath.java:2677)
	at hudson.FilePath.access$000(FilePath.java:190)
	at hudson.FilePath$40.invoke(FilePath.java:2034)
	at hudson.FilePath$40.invoke(FilePath.java:2027)
	at hudson.FilePath.act(FilePath.java:980)
	at hudson.FilePath.act(FilePath.java:958)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:2027)
	at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)
	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:218)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1037)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
	at hudson.model.Run.execute(Run.java:1770)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)


This is because remoting.jar is signed (which IMO it should not be), yet SECURITY144-compat.jar is not.

As a workaround it suffices to add


exclusions
  exclusion
groupIdorg.jenkins-ci/groupId
artifactIdSECURITY-144-compat/artifactId
  /exclusion
/exclusions


to the dependency, but this is not going to be sustainable if other plugins start adding the dep too.




Project:


Jenkins



Labels:


security
test




Priority:


Major



Reporter:


Jesse Glick

























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:

[JIRA] [ec2-plugin] (JENKINS-25626) Allow an option to start a JNLP agent and terminate SSH connection

2014-11-14 Thread arca...@ivanov.biz (JIRA)















































Arcadiy Ivanov
 created  JENKINS-25626


Allow an option to start a JNLP agent and terminate SSH connection















Issue Type:


New Feature



Assignee:


Arcadiy Ivanov



Components:


ec2-plugin



Created:


14/Nov/14 8:00 PM



Description:



	Add an option to start a slave.jar with JNLP connection and then terminate the spawning SSH. This allows to use NIO-based Channels with EC2 plugin and reduce the number of threads maintained with SSH-based communication links.






Project:


Jenkins



Priority:


Major



Reporter:


Arcadiy Ivanov

























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-25209) Add reboot slave after build for a slave template

2014-11-14 Thread arca...@ivanov.biz (JIRA)















































Arcadiy Ivanov
 stopped work on  JENKINS-25209


Add reboot slave after build for a slave template
















Change By:


Arcadiy Ivanov
(14/Nov/14 8:05 PM)




Status:


InProgress
Open



























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] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables















































Ulli Hafner
 commented on  JENKINS-25501


Results not being propagated to ENV variables















You need to use the latest warnings plugin 4.44 (this contains the fix of the snapshot version you have tested).

Is there a plugin that exposes tokens as environment variables?



























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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content















































SCM/JIRA link daemon
 commented on  JENKINS-25511


Checkstyle double-escapes content















Code changed in jenkins
User: Ulli Hafner
Path:
 src/test/java/hudson/plugins/checkstyle/parser/CheckStyleParserTest.java
 src/test/resources/hudson/plugins/checkstyle/parser/issue25511.xml
http://jenkins-ci.org/commit/checkstyle-plugin/15d6527b3e1f7bfaeba16cbe3ac18e693522b64d
Log:
  JENKINS-25511 Added testcase.


Compare: https://github.com/jenkinsci/checkstyle-plugin/compare/9b6bd2b36baf...15d6527b3e1f




























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-25626) Allow an option to start a JNLP agent and terminate SSH connection

2014-11-14 Thread arca...@ivanov.biz (JIRA)















































Arcadiy Ivanov
 updated  JENKINS-25626


Allow an option to start a JNLP agent and terminate SSH connection
















Change By:


Arcadiy Ivanov
(14/Nov/14 8:35 PM)




Description:


#Addanoptiontostartaslave.jarwithJNLPconnectionandthenterminatethespawningSSH.ThisallowstouseNIO-basedChannelswithEC2pluginandreducethenumberofthreadsmaintainedwithSSH-basedcommunicationlinks.

#Wouldallowaslaveprocesstoreconnecttomaster.



























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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content















































Ulli Hafner
 commented on  JENKINS-25511


Checkstyle double-escapes content















After adding the testcase I'm not sure if I still understand the problem What exactly is the problem and your expectation? In the testcase the excaped text is still is the same. Where exactly is the double-escaping visible?



























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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content













































 
Ulli Hafner
 edited a comment on  JENKINS-25511


Checkstyle double-escapes content
















After adding the testcase I'm not sure if I still understand the problem What exactly is the problem and your expectation? In the testcase the excaped text is still the same. Where exactly is the double-escaping visible?



























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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content













































 
Ulli Hafner
 edited a comment on  JENKINS-25511


Checkstyle double-escapes content
















After adding the test case I'm not sure if I still understand the problem What exactly is the problem and your expectation? In the test case the escaped text is still the same. Where exactly is the double-escaping visible?



























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] [checkstyle-plugin] (JENKINS-25408) View checkstyle 30 days slippery
















































Ulli Hafner
 resolved  JENKINS-25408 as Cannot Reproduce


View checkstyle 30 days slippery
















Change By:


Ulli Hafner
(14/Nov/14 8:40 PM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables

2014-11-14 Thread jstarb...@scisolutions.com (JIRA)















































Jon Starbird
 commented on  JENKINS-25501


Results not being propagated to ENV variables















No. What I was doing for my testing was using the Tokens Macro values and saving them into Environment variables. 
But for the emails I was using only the Tokens.  I'll try it again this afternoon.



























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-25627) Support for available resolutions

2014-11-14 Thread apg...@java.net (JIRA)















































apgray
 created  JENKINS-25627


Support for available resolutions















Issue Type:


Improvement



Assignee:


Kohsuke Kawaguchi



Components:


sauce-ondemand-plugin



Created:


14/Nov/14 8:44 PM



Description:


Non-mobile platforms have the option of specifying the resolution.  Available resolutions are variable depending on the Mac or PC OS and browser option selected.

The ondemand plugin should include options available resolutions for each desktop platforms in the same way that mobile platforms have two entries each for portrait or landscape device orientations.

Thank you.




Environment:


All




Project:


Jenkins



Priority:


Minor



Reporter:


apgray

























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] [multijob-plugin] (JENKINS-18458) Multijob plugin does not support Folder plugin

2014-11-14 Thread sschube...@gmail.com (JIRA)
















































Sebastian Schuberth
 resolved  JENKINS-18458 as Duplicate


Multijob plugin does not support Folder plugin
















Change By:


Sebastian Schuberth
(14/Nov/14 8: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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source













































 
Joshua Strouse
 edited a comment on  JENKINS-25606


PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
















ignore this comment



























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-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
















































Ulli Hafner
 resolved  JENKINS-22394 as Incomplete


Only one of multiple warnings parser is reported in Combined Analysis results
















Can you please add more details? I'm still don't understand what exactly should be changed.





Change By:


Ulli Hafner
(14/Nov/14 8:58 PM)




Status:


Open
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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content

2014-11-14 Thread aik.b...@gmail.com (JIRA)













































 
Alexander Obuhovich
 edited a comment on  JENKINS-25511


Checkstyle double-escapes content
















Here is how to reproduce:

1. create a job called "jobName" (name doesn't matter)
2. from within a job publish checkstyle report (the "phpcs_checkstyle.xml" file)
3. open /var/lib/jenkins/jobs/jobName/1/checkstyle.xml file (the "1" is build number)
4. that file should contain double escaped xml already
5. go to http://your.jenkins.instance.com/jobs/jobName/1/checkStyleResult/api/json?pretty=truetree=warnings*
6. the "message" key at least of some messages will have content escaped by XML rules twice (the
apos; and amp;quot;
)

I guess the XML file is source for /checkStyleResult/api/json page, so if new generated checkstyle.xml is escaped properly, then the JSON output from it will be as well.



























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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content

2014-11-14 Thread aik.b...@gmail.com (JIRA)















































Alexander Obuhovich
 commented on  JENKINS-25511


Checkstyle double-escapes content















Here is how to reproduce:

1. create a job called "jobName" (name doesn't matter)
2. from within a job publish checkstyle report (the "phpcs_checkstyle.xml" file)
3. open /var/lib/jenkins/jobs/jobName/1/checkstyle.xml file (the "1" is build number)
4. that file should contain double escaped xml already
5. go to http://your.jenkins.instance.com/jobs/jobName/1/checkStyleResult/api/json?pretty=truetree=warnings*
6. the "message" key at least of some messages will have content escaped by XML rules twice (the  apos; and  amp;quot

I guess the XML file is source for /checkStyleResult/api/json page, so if new generated checkstyle.xml is escaped properly, then the JSON output from it will be as well.



























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-25628) config.xml files do not end in newline

2014-11-14 Thread elliot.w...@gmail.com (JIRA)















































Elliot Wolk
 created  JENKINS-25628


config.xml files do not end in newline















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


14/Nov/14 10:01 PM



Description:


config.xml files for global config and for job config are not well-formed text files; the last line does not end in a linebreak {causing UNIX tools that rely on well-formed text files to break}

this is nightmarish when editing the files manually and using git to track changes to them, a pattern which is otherwise very successful. editors like vim save only well-formed text files, which are then malformed by jenkins when it touches them.




Project:


Jenkins



Priority:


Minor



Reporter:


Elliot Wolk

























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] [integrity-plugin] (JENKINS-25629) Checkpoints are done against wrong project!

2014-11-14 Thread gre...@hotmail.com (JIRA)















































Grigoriy Milman
 created  JENKINS-25629


Checkpoints are done against wrong project!















Issue Type:


Bug



Assignee:


Cletus DSouza



Components:


integrity-plugin



Created:


14/Nov/14 10:10 PM



Description:


We  have for all build jobs configurations the following settings: 

	Integrity - CM Configuration Name set as ${env['JOB_NAME']}
* Integrity - CM Checkpoint Configuration Name set as ${env['JOB_NAME']}



When checkpoint is executed at post build step for project related to job XYZ and at the same time another job ABC is doing resynchronization (and ABC may be was started earlier but still running), checkpoint is executed for project related to the job ABC with label defined in the build for XYZ.

By the way, PTC is really slow on our side.





Environment:


Windows




Project:


Jenkins



Priority:


Major



Reporter:


Grigoriy Milman

























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] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables

2014-11-14 Thread jstarb...@scisolutions.com (JIRA)















































Jon Starbird
 commented on  JENKINS-25501


Results not being propagated to ENV variables















Ok it is working in emails now, thanks.

Question, what I'm trying to accomplish is I only want my build to Fail or be Unstable with MSBuild warnings but I want the reports for Robocopy and a homemade parser to still be produced. So what I was doing was using the Conditional Multi Step task to run Warnings earlier in the build to get my MSBuild Warnings and then was trying to save those results out and that is where I was trying to put the values saved out as Environment Variables. 

Is there any way for to get those separate values out??



























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-jira-issue-updater] (JENKINS-25591) jenkins is crashing
















































Daniel Beck
 resolved  JENKINS-25591 as Not A Defect


jenkins is crashing
















It would be too much work to make this into a useful issue report, so resolving as Not A Defect.





Change By:


Daniel Beck
(14/Nov/14 10:46 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























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-25521) How to fix 'stapler-class is deprecated' warning?















































Daniel Beck
 commented on  JENKINS-25521


How to fix stapler-class is deprecated warning?















Alex Earl: I'm pretty sure this can be done transparently by preferring the new field ($class IIRC) over the old, and only accessing the older if the new one does not exist.



























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-25584) Improve error outputs if IOException happens on the disk overflow















































Daniel Beck
 commented on  JENKINS-25584


Improve error outputs if IOException happens on the disk overflow















The root exception is No space left on device, which seems pretty straightforward.

We could try to improve how exceptions are shown to users. There's already an issue for that though.



























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] [workflow-plugin] (JENKINS-25630) Step fails to inject subtypes of Run/Node/etc

2014-11-14 Thread k...@kohsuke.org (JIRA)















































Kohsuke Kawaguchi
 created  JENKINS-25630


Step fails to inject subtypes of Run/Node/etc















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


workflow-plugin



Created:


14/Nov/14 11:00 PM



Description:


Step implementation trying to inject a subtype of a common parameter type like WorkflowRun (as opposed to Run) would fail.

Instead this should succeed.




Project:


Jenkins



Priority:


Major



Reporter:


Kohsuke Kawaguchi

























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-25628) config.xml files do not end in newline