date:20141222















































Hans Marggraff
 created  JENKINS-26191


Empty workflow configuration screen















Issue Type:


Bug



Assignee:


Jesse Glick



Attachments:


jenkins-no-workflow.PNG



Components:


workflow-plugin



Created:


22/Dec/14 11:17 AM



Description:


I installed all plugins named workflow-xx (was that right??)
and trued to define a workflow job.
However the configuration screen does not allow me to enter a workflow definition.
When I press save I get a NPE.
So I cannot use the plugin at all.

java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
	at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46)
	at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
-

Caused by: java.lang.NullPointerException
	at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.hash(ScriptApproval.java:314)
	at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.configuring(ScriptApproval.java:357)
	at org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition.init(CpsFlowDefinition.java:76)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
	at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:447)
	at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:699)
	at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:81)
	at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:596)
	at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:400)
	at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:396)
	at org.jenkinsci.plugins.workflow.job.WorkflowJob.submit(WorkflowJob.java:156)
	at hudson.model.Job.doConfigSubmit(Job.java:1188)
	... 83 more






Environment:


Linux, Jetty, Jenkins 1.595, workflow plugin 1.1




Project:


Jenkins



Labels:


workflow




Priority:


Blocker



Reporter:


Hans Marggraff

























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] [deploy-plugin] (JENKINS-22403) allow deploy plugin to accept parametrized variables like %parameter% or $parameter

2014-12-22 Thread sbre...@hotmail.com (JIRA)















































First Name Last Name
 commented on  JENKINS-22403


allow deploy plugin to accept parametrized variables like %parameter% or $parameter















Contact me privately, we have an enterprise grade solution. Regards, Balazs



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit-plugin] (JENKINS-26153) JUnit missing builds

2014-12-22 Thread te...@java.net (JIRA)















































James Nord
 commented on  JENKINS-26153


JUnit missing builds















did you delete the failed build?

Sounds like JENKINS-25340



























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-25842) User Permissions Wiped After Jenkins Restart

2014-12-22 Thread cjp...@gmail.com (JIRA)















































Chris Parr
 commented on  JENKINS-25842


User Permissions Wiped After Jenkins Restart















Hi,

To reproduce just follow the steps in the description on a clean install.

I don't know Eli, but I do have a work around for this. It seems to be either a config persistence issue or an issue with the style of user id (or both). 

1. Make sure user IDs are lower case
2. After setting up security, go to the general config page and save (even though you don't change anything).

I picked up these hints from the Jenkins user list. I tried them both at the same time and they gave me a secure working instance. Don't know if perhaps step 1 on it's own would work, but I didn't have time to test on a clean instance.

Cheers

Chris



























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-26192) Add support for Grape (@Grab) in workflow scripts

2014-12-22 Thread d...@baltrinic.com (JIRA)















































Kenneth Baltrinic
 created  JENKINS-26192


Add support for Grape (@Grab) in workflow scripts















Issue Type:


New Feature



Assignee:


Jesse Glick



Components:


workflow-plugin



Created:


22/Dec/14 12:32 PM



Description:


The workflow plugin and its groovy DSL should support the use of Grape and the @Grab attribute to allow the creation of workflows that depend on external libraries such as HTTP Builder or jYaml.

This issue seems closely related to JENKINS-18349 and other issues referenced in the comments of that issue.




Project:


Jenkins



Priority:


Major



Reporter:


Kenneth Baltrinic

























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-26191) Empty workflow configuration screen















































Hans Marggraff
 updated  JENKINS-26191


Empty workflow configuration screen
















Change By:


Hans Marggraff
(22/Dec/14 12:32 PM)




Description:


Iinstalledallpluginsnamedworkflow-xx(wasthatright??)and
trued
tried
todefineaworkflowjob.Howevertheconfigurationscreendoesnotallowmetoenteraworkflowdefinition.WhenIpresssaveIgetaNPE.SoIcannotusethepluginatall.java.lang.reflect.InvocationTargetException	atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)	atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)	atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)	atjava.lang.reflect.Method.invoke(Method.java:601)	atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)	atorg.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46)	atorg.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399)	atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)-Causedby:java.lang.NullPointerException	atorg.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.hash(ScriptApproval.java:314)	atorg.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.configuring(ScriptApproval.java:357)	atorg.jenkinsci.plugins.workflow.cps.CpsFlowDefinition.init(CpsFlowDefinition.java:76)	atsun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeMethod)	atsun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)	atsun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)	atjava.lang.reflect.Constructor.newInstance(Constructor.java:525)	atorg.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:447)	atorg.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:699)	atorg.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:81)	atorg.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:596)	atorg.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:400)	atorg.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:396)	atorg.jenkinsci.plugins.workflow.job.WorkflowJob.submit(WorkflowJob.java:156)	athudson.model.Job.doConfigSubmit(Job.java:1188)	...83more



























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] [groovy-plugin] (JENKINS-18349) Allow to use @Grab in a Script Console

2014-12-22 Thread d...@baltrinic.com (JIRA)















































Kenneth Baltrinic
 commented on  JENKINS-18349


Allow to use @Grab in a Script Console















I have added a separate ticket for the workflow plugin: JENKINS-26192



























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-26193) Workflow plugin input step is not shown in browser















































Hans Marggraff
 created  JENKINS-26193


Workflow plugin input step is not shown in browser















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


workflow-plugin



Created:


22/Dec/14 12:42 PM



Description:


When a workflow requests input there is no input page shown. Instead one must open the build via its id and can then open the input page from the left.
Otherwise the build just hangs without asking for input.

In the menu of the build, the items
"paused for input"
and "running steps" each appear twice.




Environment:


windows, tomcat 8, jenkins 1594, workflow 1.1




Project:


Jenkins



Priority:


Minor



Reporter:


Hans Marggraff

























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-26194) Workflow plugin gives no access to build parameters or environment















































Hans Marggraff
 created  JENKINS-26194


Workflow plugin gives no access to build parameters or environment















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


workflow-plugin



Created:


22/Dec/14 12:46 PM



Description:


Are there bindings available to the build environment to access build parameters or stuff like the build number?
Where are they documented?




Project:


Jenkins



Priority:


Major



Reporter:


Hans Marggraff

























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-26172) Simple ping failed!

2014-12-22 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-26172


Simple ping failed! 















Well... not exactly. Jenkins uses a fork of J-Interop, and could probably extend the error message:

https://github.com/kohsuke/j-interop/blob/kohsuke/j-interop/src/org/jinterop/dcom/core/JIComOxidStub.java#L261

However it's on kohsuke's account, so he'd need to do that. You could file a pull request referencing this issue with improved diagnostics and request a release and integration in 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] [gerrit-trigger-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger















































SCM/JIRA link daemon
 commented on  JENKINS-23152


builds getting lost due to GerritTrigger















Code changed in jenkins
User: Robert Sandell
Path:
 pom.xml
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/UnreviewedPatchesListener.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/events/PluginDraftPublishedEvent.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/replication/ReplicationCache.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/replication/ReplicationQueueTaskDispatcher.java
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement/index_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement/newServer_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer/index_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer/remove_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/Messages.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/Messages_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritCause/description_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/manual/ManualTriggerAction/ajaxTriggerMonitor_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/manual/ManualTriggerAction/help-Search_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/manual/ManualTriggerAction/index_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/events/PluginCommentAddedContainsEvent/config_ja.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/events/PluginDraftPublishedEvent/config.jelly
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/events/PluginPatchsetCreatedEvent/config_ja.properties
 src/main/webapp/help-GerritNoConnectionOnStartup_ja.html
 src/main/webapp/help-GerritNotificationLevel_ja.html
 src/main/webapp/help-GerritServerName_ja.html
 src/main/webapp/help-ReplicationCacheExpiration_ja.html
 src/main/webapp/help-ReplicationSlaveHost_ja.html
 src/main/webapp/help-ReplicationSlaveName_ja.html
 src/main/webapp/help-ReplicationSlaveTimeout_ja.html
 src/main/webapp/help-Replication_ja.html
 src/main/webapp/help-defaultSlave_ja.html
 src/main/webapp/help-enableSlaveSelectionInJobs_ja.html
 src/main/webapp/trigger/help-DependencyJobs_ja.html
 src/main/webapp/trigger/help-DraftPublished.html
 src/main/webapp/trigger/help-DraftPublished_ja.html
 src/main/webapp/trigger/help-ExcludeNoCodeChange_ja.html
 src/main/webapp/trigger/help-ExcludeTrivialRebase_ja.html
 src/main/webapp/trigger/help-ReadableMessage_ja.html
 src/main/webapp/trigger/help-SilentStartMode.html
 src/main/webapp/trigger/help-TriggerUnreviewedPatches_ja.html
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServerHudsonTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/api/GerritTriggerApiTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritProjectListTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/DuplicatesUtil.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/MockGerritHudsonTriggerConfig.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/Setup.java

[JIRA] [gerrit-trigger-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger















































SCM/JIRA link daemon
 commented on  JENKINS-23152


builds getting lost due to GerritTrigger















Code changed in jenkins
User: Robert Sandell
Path:
 pom.xml
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/PluginImpl.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/EventListener.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTimer.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTimerTask.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritUserCause.java
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/UnreviewedPatchesListener.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/dependency/DependencyQueueTaskDispatcherTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListenerTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/job/rest/BuildCompletedRestCommandJobHudsonTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemoryTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/MemoryImprintTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/replication/ReplicationQueueTaskDispatcherTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/spec/DuplicateGerritListenersHudsonTestCase.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/spec/DuplicateGerritListenersPreloadedProjectHudsonTestCase.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/spec/SpecGerritTriggerHudsonTest.java
 src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/spec/gerritnotifier/SpecGerritVerifiedSetterTest.java
http://jenkins-ci.org/commit/gerrit-trigger-plugin/c3899eaf4e05a43430b332c628e17f82964eda1a
Log:
  Merge pull request #193 from jenkinsci/JENKINS-23152

Fix for JENKINS-23152


Compare: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/19bfb019b070...c3899eaf4e05




























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-26172) Simple ping failed!

2014-12-22 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-26172


Simple ping failed! 















Maybe configure a log recorder with the logger org.jinterop on level FINE or so to see what else appears.



























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-26172) Simple ping failed!

2014-12-22 Thread davida2...@java.net (JIRA)















































davida2009
 commented on  JENKINS-26172


Simple ping failed! 















Thanks for your help. I think that filing a pull request is beyond my expertise, but I will try the log recorder if the error reoccurs (it was cleared by a restart).



























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-24895) An existing connection was forcibly closed by the remote host

2014-12-22 Thread ganc...@libero.it (JIRA)















































Graziano Ancona
 commented on  JENKINS-24895


An existing connection was forcibly closed by the remote host















Hi 
@Anuvrath: I launched only the slaves via batch, the server is still running as a service
@Leslie: Seems more this problem: https://issues.jenkins-ci.org/browse/JENKINS-18781



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-10222) Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)

2014-12-22 Thread alan.birt...@eu.sony.com (JIRA)















































Alan Birtles
 commented on  JENKINS-10222


Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)















just had a similar issue, in our case we had the svn url defined as http://server:80/svn/repo, I think the svn checkout strips out the port number then the polling thinks that the workspace doesn't contain the same working copy.



























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-26195) Failed to update permalink: unable to delete

Jesse Glick
created JENKINS-26195

Failed to update permalink: unable to delete

Issue Type:

Bug

Assignee:

Unassigned

Components:

core

Created:

22/Dec/14 2:50 PM

Description:

Sometimes users report seeing exceptions such as

... jenkins.model.PeepholePermalink updateCache
WARNING: Failed to update ... lastSuccessfulBuild permalink for ...
java.io.IOException: Unable to delete /jenkins/jobs/.../builds/lastSuccessfulBuild
at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112)
at jenkins.model.PeepholePermalink.writeSymlink(PeepholePermalink.java:200)
at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:150)
at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:122)
at hudson.model.Job.getLastSuccessfulBuild(Job.java:857)

In one case this was discovered to be due to lastSuccessfulBuild being an actual directory rather than a symlink, due to an incorrect restoration from backup. But AtomicFileWriter should use Util.deleteFile or similar to make sure that Java 7 methods are first used to perform the deletion, which provide better diagnostics.

Project:

Jenkins

Labels:

robustness
symlink
permalink

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: 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version















































Jesse Glick
 commented on  JENKINS-10860


Unable to determine Maven version















A related but distinct stack trace blocking polling:


… hudson.triggers.SCMTrigger$Runner runPolling
SEVERE: Failed to record SCM polling for …
java.lang.RuntimeException: Unable to determine Maven version
	at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.isMavenVersionValid(MavenExtractorEnvironment.java:153)
	at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.buildEnvVars(MavenExtractorEnvironment.java:112)
	at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:914)
	at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56)
	at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:167)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:554)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:516)
	at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:384)
	at hudson.scm.SCM.poll(SCM.java:401)
	at …
Caused by: java.lang.IllegalArgumentException: mavenHome '…' doesn't seem to exist on this node (or you don't have sufficient rights to access it)
	at hudson.maven.MavenEmbedderUtils.buildClassRealm(MavenEmbedderUtils.java:76)
	at hudson.maven.MavenEmbedderUtils.getMavenVersion(MavenEmbedderUtils.java:188)
	at hudson.maven.MavenEmbedderUtils.isAtLeastMavenVersion(MavenEmbedderUtils.java:215)
	at org.jfrog.hudson.maven3.MavenVersionCallable.call(MavenVersionCallable.java:45)
	at org.jfrog.hudson.maven3.MavenVersionCallable.call(MavenVersionCallable.java:33)
	at …
	at org.jfrog.hudson.util.MavenVersionHelper.isAtLeast(MavenVersionHelper.java:110)
	at org.jfrog.hudson.util.MavenVersionHelper.isAtLeastVersion(MavenVersionHelper.java:82)
	at org.jfrog.hudson.util.MavenVersionHelper.isAtLeastResolutionCapableVersion(MavenVersionHelper.java:72)
	at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.isMavenVersionValid(MavenExtractorEnvironment.java:151)




























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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version















































Jesse Glick
 updated  JENKINS-10860


Unable to determine Maven version
















Change By:


Jesse Glick
(22/Dec/14 3:03 PM)




Labels:


robustness



























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-26196) FilePath.installIfNecessaryFrom can fail due to server error even when unpacked dir already exists















































Jesse Glick
 created  JENKINS-26196


FilePath.installIfNecessaryFrom can fail due to server error even when unpacked dir already exists















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


22/Dec/14 3:39 PM



Description:


FilePath.installIfNecessaryFrom, used from ZipExtractionInstaller, is designed to log a warning but continue in case the tool is already unpacked and the server returns an error while it is checking for a newer archive. Yet this stack trace suggests that this logic is not working, because the IOException comes after connect in getInputStream:


Unpacking URL to TOOLPATH on SLAVE
ERROR: Failed to download URL from slave; will retry from master
java.io.IOException: remote file operation failed: TOOLPATH at hudson.remoting.Channel@...:SLAVE: java.net.ConnectException: Connection timed out
	at hudson.FilePath.act(FilePath.java:976)
	at hudson.FilePath.act(FilePath.java:958)
	at hudson.FilePath.installIfNecessaryFrom(FilePath.java:797)
	at hudson.tools.ZipExtractionInstaller.performInstallation(ZipExtractionInstaller.java:79)
	at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68)
	at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107)
	at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:205)
	at hudson.model.JDK.forNode(JDK.java:130)
	at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:350)
	at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1444)
	at hudson.model.AbstractProject._poll(AbstractProject.java:1421)
	at hudson.model.AbstractProject.poll(AbstractProject.java:1332)
	at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119)
	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515)
	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544)
	at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:579)
	at java.net.Socket.connect(Socket.java:528)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
	at sun.net.www.http.HttpClient.init(HttpClient.java:211)
	at sun.net.www.http.HttpClient.New(HttpClient.java:308)
	at sun.net.www.http.HttpClient.New(HttpClient.java:326)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:996)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:932)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:850)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1300)
	at java.net.URL.openStream(URL.java:1037)
	at hudson.FilePath$Unpack.invoke(FilePath.java:833)
	at hudson.FilePath$Unpack.invoke(FilePath.java:827)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2577)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at

[JIRA] [workflow-plugin] (JENKINS-26194) Workflow plugin gives no access to build parameters or environment
















































Jesse Glick
 resolved  JENKINS-26194 as Not A Defect


Workflow plugin gives no access to build parameters or environment
















Parameters are directly accessible as Groovy variables. BUILD_NUMBER and the like are environment variables.





Change By:


Jesse Glick
(22/Dec/14 4:13 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] [workflow-plugin] (JENKINS-26194) Workflow plugin gives no access to build parameters or environment















































SCM/JIRA link daemon
 commented on  JENKINS-26194


Workflow plugin gives no access to build parameters or environment















Code changed in jenkins
User: Jesse Glick
Path:
 TUTORIAL.md
http://jenkins-ci.org/commit/workflow-plugin/d3e64f600fcb9bc2c4323abe138d23af90e9700f
Log:
  JENKINS-26194 Noting default environment variables and parameters.





























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-26193) Workflow plugin input step is not shown in browser
















































Jesse Glick
 resolved  JENKINS-26193 as Incomplete


Workflow plugin input step is not shown in browser
















there is no input page shown.

Where are you looking for an “input page”?

one must open the build via its id and can then open the input page from the left.

Yes, when a flow build is paused for input it will have this link in the sidebar. What is the issue?

Otherwise the build just hangs without asking for input.

The console log should indicate that it is waiting for input, and provide a hyperlink to give it (or to immediately Proceed if no parameters were specified).

In the menu of the build, the items "paused for input" and "running steps" each appear twice.

Certainly this should not happen, and I have never seen it. Do you know how to reproduce such a condition from scratch?





Change By:


Jesse Glick
(22/Dec/14 4:17 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] [openid-plugin] (JENKINS-26003) username is endpoint URL after openid SSO

2014-12-22 Thread junaid.sha...@msn.com (JIRA)















































junaid shaikh
 commented on  JENKINS-26003


username is endpoint URL after openid SSO















Hi,

I am not able to figure where to tinker in order to solve this. 

Problem description: 

CAS is configured with LDAP and openid and used as authentication for my Jenkins server. 

After successful login from CAS, it gets redirected back to my jenkins server page. However on the top right corner where ideally the displayName of the user should be, it shows the openid provider URL as it was provided in the openid configuration using jenkins openid plugin. Please refer to image as shown in the screenshot .

anyone knows where I can configure so that the displayName on the jenkins is displayed as the user from my LDAP server.



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] [workflow-plugin] (JENKINS-26192) Add support for Grape (@Grab) in workflow scripts

Jesse Glick
commented on JENKINS-26192

Add support for Grape (@Grab) in workflow scripts

(I could have sworn this was already filed, but I cannot find it now. The idea was brought up during the Workflow Summit a couple months ago but perhaps I failed to record it.)

There are two major reasons why Grape support could be problematic here. First, binary dependencies (compiled to *.class) cannot participate in CPS transformation, and thus calls to libraries would be considered “native” methods which cannot survive a Jenkins restart. If the call does significant I/O, especially network I/O, this would make the flow less robust. (This consideration shows why this issue differs from JENKINS-18349; the plain Groovy plugin just makes a call to the standard embedded Groovy runtime, whereas Workflow uses its own CPS-transformed interpreter.)

Second, when running in Groovy sandbox mode, the normal case when running a secured Jenkins instance with a distinction between administrators and job maintainers, any native calls would have to whitelisted, which assumes they are unconditionally safe—which might not be true if, say, a URL handling library permits file-protocol URLs. This consideration is in common with other plugins allowing use of Groovy in Jenkins.

Both these considerations would also apply if the workflow definition were to support the optional binary classpath feature in the Script Security plugin (currently it does not).

While it is obviously not practical to do so for every useful Groovy library, in general it is best to create custom workflow steps for important operations. These can then be made to survive restarts (or slave disconnections) if necessary, and can perform any necessary input validation and/or access control checks. Where applicable the step can also interact with files in a remote (slave) workspace, which would be impossible if using a non-Jenkins-specific library directly.

If you need to perform some complex or expensive tasks with unrestricted Groovy physically running on a slave, it may be simplest and most effective to simply write that code in a *.groovy file in your workspace (for example, in an SCM checkout) and then use tool and sh/bat to run Groovy as an external process; or even put this stuff into a Gradle script, Groovy Maven plugin execution, etc. The workflow script itself should be limited to simple and extremely lightweight logical operations focused on orchestrating the overall flow of control and interacting with other Jenkins features—slave allocation, user input, and the like.

[JIRA] [workflow-plugin] (JENKINS-26191) Empty workflow configuration screen

Jesse Glick
resolved JENKINS-26191 as Cannot Reproduce

Empty workflow configuration screen

Here script is null in the CpsFlowDefinition, whereas it should be at worst an empty string. But I think this is a red herring. From the screenshot I gather that the configuration of the definition, including the script field, did not appear at all for some reason. Most likely there is some error either in your Jenkins logs or in the browser _javascript_ console which would explain why the configuration form is broken.

Did you try restarting Jenkins after installing the Workflow plugin? Currently some features are known not to work after an initial dynamic install (but I have not heard of this problem).

At any rate, I tried running 1.595 on a fresh $JENKINS_HOME and installing Workflow: Aggregator (which pulls in its dependencies), and was able to configure and save a new flow.

Change By:

Jesse Glick
(22/Dec/14 4:49 PM)

Status:

Open
Resolved

Resolution:

CannotReproduce

[JIRA] [workflow-plugin] (JENKINS-26185) Reusing workspaces between stages and nodes
















































Jesse Glick
 resolved  JENKINS-26185 as Not A Defect


Reusing workspaces between stages and nodes
















Currently your best option is to use archive in the first workspace followed by unarchive in the second, as is shown in one of the examples in the Workflow tutorial.





Change By:


Jesse Glick
(22/Dec/14 4:52 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] [parameterized-trigger-plugin] (JENKINS-26050) Workflow integration

Jesse Glick
commented on JENKINS-26050

Workflow integration

Job doesn't provide scheduleBuild2
Job doesn't provide getQueuePeriod getQuietPeriod?

ParameterizedJobMixIn provides both. SCMTriggerItem is not appropriate here.

Job doesn't provide findNearest

This should really be deprecated, and callers directed to use the more general Items.findNearest.

DependencyGraph works only for AbstractProject.

True; until this core refactoring is done, this mode would simply not be supported for workflows. See the third paragraph of my original description.

AbstractProject doesn't implements SCMTriggerItem

It is implement by Project. At any rate, as above, do not pay attention to this interface here.

Does workflow-plugin provides alternate way to define dependencies between workflow projects?

Other than the fact that a workflow can build another and provide an UpstreamCause, no, there is no DependencyGraph support. Again, for TriggerBuilder (and one mode of BuildTrigger) this does not matter.

[JIRA] [parameterized-trigger-plugin] (JENKINS-26009) Cannot trigger workflow projects using parameterized-trigger-plugin
















































Jesse Glick
 resolved  JENKINS-26009 as Duplicate


Cannot trigger workflow projects using parameterized-trigger-plugin
















Change By:


Jesse Glick
(22/Dec/14 4:59 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] [git-plugin] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds















































pmv
 commented on  JENKINS-20258


Git plugin with checkout to subdir and prune stale branches fails all builds















Thanks for the update.  Is there an open ticket I can watch for this feature (rather than commenting on this old one)?

Personally I'd be in favor of a "use this feature with JGit at your own risk" message rather than not supporting prune at all, but I understand your logic.



























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-25174) Run parameters should display in human readable form rather than build numbers















































SCM/JIRA link daemon
 commented on  JENKINS-25174


Run parameters should display in human readable form rather than build numbers















Code changed in jenkins
User: Daniel Beck
Path:
 core/src/main/resources/hudson/model/RunParameterValue/value.jelly
http://jenkins-ci.org/commit/jenkins/3ed7778bd42b99fc5fbef66d63d96604c279ec78
Log:
  FIXED JENKINS-25174 Show run display name on parameters page





























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-25174) Run parameters should display in human readable form rather than build numbers
















































SCM/JIRA link daemon
 resolved  JENKINS-25174 as Fixed


Run parameters should display in human readable form rather than build numbers
















Change By:


SCM/JIRA link daemon
(22/Dec/14 5:16 PM)




Status:


InProgress
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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

2014-12-22 Thread jason.mcguin...@instinet.co.uk (JIRA)















































J McG
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















I hope the update will be officially released soon!



























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-20148) Misleading description of the 'workspace' permission















































SCM/JIRA link daemon
 commented on  JENKINS-20148


Misleading description of the workspace permission















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/resources/hudson/model/Messages.properties
http://jenkins-ci.org/commit/jenkins/dd1b65dc9b28135598c0b2aa42538a7a6cd94ed5
Log:
  JENKINS-20148 Merged #1494.


Compare: https://github.com/jenkinsci/jenkins/compare/d5d6ca21ec0d...dd1b65dc9b28




























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-20148) Misleading description of the 'workspace' permission















































SCM/JIRA link daemon
 commented on  JENKINS-20148


Misleading description of the workspace permission















Code changed in jenkins
User: Daniel Beck
Path:
 core/src/main/resources/hudson/model/Messages.properties
http://jenkins-ci.org/commit/jenkins/801f37d5a11554fb97bf9c8edbd9f3e5bd21a47f
Log:
  FIXED JENKINS-20148 Rephrase Workspace permission description





























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-20148) Misleading description of the 'workspace' permission
















































SCM/JIRA link daemon
 resolved  JENKINS-20148 as Fixed


Misleading description of the workspace permission
















Change By:


SCM/JIRA link daemon
(22/Dec/14 5:25 PM)




Status:


InProgress
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] [git-plugin] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds

2014-12-22 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-20258


Git plugin with checkout to subdir and prune stale branches fails all builds















I've been unwilling to accept incompatible behavior between CliGit and JGit. Use at your own risk seems too risky for a plugin used in over 50 000 installations.

You're welcome to open a separate bug report / enhancement request to track it. That seems like it will make it easier to track, and easier to report the problem to the upstream JGit process.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-26197) Allow prune option when using JGit















































pmv
 created  JENKINS-26197


Allow prune option when using JGit















Issue Type:


Improvement



Assignee:


Nicolas De Loof



Components:


git-plugin



Created:


22/Dec/14 5:57 PM



Description:


Currently users are not able to use the prune option with JGit.  Apparently JGit does have the prune feature, but it prunes more than git CLI:  https://issues.jenkins-ci.org/browse/JENKINS-20258?focusedCommentId=218092page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-218092

I don't see any issues on the JGit bug tracker about this, but perhaps it's my search:
https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=__all__content=pruneno_redirect=1order=relevance%20descproduct=JGitquery_format=specific




Project:


Jenkins



Labels:


git
plugin




Priority:


Minor



Reporter:


pmv

























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-25897) Infinite loop with crontab H H(19-24) * * *















































Jesse Glick
 commented on  JENKINS-25897


Infinite loop with crontab H H(19-24) * * *















Right, this should end in 23, not 24.



























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-18313) H cron syntax - cannot specify between 10 pm and 6 am















































Jesse Glick
 commented on  JENKINS-18313


H cron syntax - cannot specify between 10 pm and 6 am
















H H(22-23) * * *
H H(0-5) * * *




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-22053) NullPointerException during polling when using git inverse branch choosing strategy

2014-12-22 Thread bosox...@gmail.com (JIRA)

Jay Perry
commented on JENKINS-22053

NullPointerException during polling when using git inverse branch choosing strategy

I currently running into this

Started on Dec 22, 2014 12:59:00 PM
Using strategy: Inverse
[poll] Last Built Revision: Revision 87279712b25ea4b4fdefc47021c16f3a5108b448 (refs/remotes/origin/master)
using GIT_SSH to set credentials
git ls-remote -h g...@bitbucket.org:company/myapp.git master # timeout=10
FATAL: hudson.plugins.git.GitException: Error performing command: git ls-remote -h g...@bitbucket.org:company/myapp.git master
hudson.util.IOException2: hudson.plugins.git.GitException: Error performing command: git ls-remote -h g...@bitbucket.org:company/myapp.git master
at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:518)
at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:384)
at hudson.scm.SCM.poll(SCM.java:401)
at hudson.model.AbstractProject._poll(AbstractProject.java:1429)

I am using Jenkins 1.580.1 and git plugin 2.3.2. I do not get this when running master as it only happens with the Inverse setting. Please help as it prevents my builds from running. Thanks in advance.

[JIRA] [git-plugin] (JENKINS-22053) NullPointerException during polling when using git inverse branch choosing strategy

2014-12-22 Thread bosox...@gmail.com (JIRA)















































Jay Perry
 commented on  JENKINS-22053


NullPointerException during polling when using git inverse branch choosing strategy















git client plugin is 1.13.0 too



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [join-plugin] (JENKINS-26198) Join plugin collapsing builds

2014-12-22 Thread brian.sm...@novatel.com (JIRA)















































Brian Smith
 created  JENKINS-26198


Join plugin collapsing builds















Issue Type:


Bug



Assignee:


mdonohue



Components:


join-plugin



Created:


22/Dec/14 6:11 PM



Description:


If one of our downstream jobs is running behind (do to a lack of available resources on the particular node that it requires) the jobs are all collapsed together (like if we had a Quiet Period).

I wouldn't mind this so much but it uses the artifacts from the first job that kicks it off and not the last one. this means that we end up with a large number of untested changes.

SuccessConsole Output

Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2043
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2044
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2045
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2046
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2047
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2048
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2049
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2050
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2051
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2052
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2053
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2054
originally caused by:
 Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2055
originally caused by:
 Started by an SCM change
Building remotely on CDS_TestNode104 (TestNode SOLO OEM638 COM_12 ANT_ ETHERNET DEBUG) in workspace d:\builds\Jenkins\workspace\M6_TEST_MAIN_COMMIT_SPACING_STRESS

Deleting project workspace... done

Email was triggered for: Before Build
Sending email for trigger: Before Build
An attempt to send an e-mail to empty list of recipients, ignored.
Copied 2 artifacts from "M6_BUILD_MAIN_COMMIT" build number 2043

As you can see the latest build was 2055 but it is using the artifacts from 2043.

We don't see this behavior when we are not using the Join Plugin.




Environment:


Windows Server and slaves. Join Plugin v1.15, Jenkins 1.554.2.




Project:


Jenkins



Priority:


Major



Reporter:


Brian Smith

























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-25174) Run parameters should display in human readable form rather than build numbers

2014-12-22 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-25174


Run parameters should display in human readable form rather than build numbers















Integrated in  jenkins_main_trunk #3884
 FIXED JENKINS-25174 Show run display name on parameters page (Revision 3ed7778bd42b99fc5fbef66d63d96604c279ec78)

 Result = SUCCESS
daniel-beck : 3ed7778bd42b99fc5fbef66d63d96604c279ec78
Files : 

	core/src/main/resources/hudson/model/RunParameterValue/value.jelly





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-22053) NullPointerException during polling when using git inverse branch choosing strategy

2014-12-22 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-22053


NullPointerException during polling when using git inverse branch choosing strategy















Jay Perry that is not a null pointer exception, so I think it belongs somewhere other than attached to this closed bug. I'd first suggest that you ask the Jenkins user mailing list for help. If they are unable to help, then you'll need to submit a new bug report. You might also try using https to access your bitbucket repository rather than ssh. There has been at least one case where a private bitbucket repository is accessible from the plugin by one protocol and not by another.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-22053) NullPointerException during polling when using git inverse branch choosing strategy

2014-12-22 Thread bosox...@gmail.com (JIRA)















































Jay Perry
 commented on  JENKINS-22053


NullPointerException during polling when using git inverse branch choosing strategy















Thanks Mark.  I'll try the mailing list.



























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-26199) Build system requirements not listed

2014-12-22 Thread tg9...@gmx-topmail.de (JIRA)

Thomas Goeppel
created JENKINS-26199

Build system requirements not listed

Issue Type:

Improvement

Assignee:

Jesse Glick

Components:

workflow-plugin

Created:

22/Dec/14 6:56 PM

Description:

After several rounds of trial-and-error with 'head', and tag 'workflow-1.1' I'm still not sure why tests fail. Currently I'm using Ubuntu 14.04 / JDK 1.8.0_25 (I had open-jdk7), and I've installed all the stuff that tests threw at me (e.g. mercurial). I assigned port 8081 to my local Jenkins test installation, and removed ~/.jenkins (which mvn hpi:run uses if it exists). Normally I use Eclipse following the Jenkins plugin development recommendations, but I also tried using Netbeans (8.02) (which brought even more problems).

Right now I still need to remove most of the tests from
cps/src/test/groovy/org/jenkinsci/plugins/workflow/cps/CpsScriptTest.groovy in order to get the workflow-plugin running.

Possibly there are system dependencies that my workstation doesn't meet. I know that the Java platform is supposed to be OS independent, but obviously it's not that simple. It would be very helpful if there were a list of requirements for the build- and test environment (Linux, BSD, Mac, Windows, distribution, installed software ... ).

Project:

Jenkins

Priority:

Major

Reporter:

Thomas Goeppel

[JIRA] [core] (JENKINS-24895) An existing connection was forcibly closed by the remote host

2014-12-22 Thread anuvrath.jo...@gmail.com (JIRA)















































Anuvrath Joshi
 commented on  JENKINS-24895


An existing connection was forcibly closed by the remote host















Hello @Graziano,

Am already running them as just an application using slave-agent instead of Widows service due network issues. But Master is running as Windows service.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-26197) Allow prune option when using JGit















































pmv
 commented on  JENKINS-26197


Allow prune option when using JGit















Currently if you choose the prune option with jgit (Git 2.3.1/Git-client 1.12.0) this is the output:

Fetching changes from the remote Git repository
Pruning obsolete local branches
ERROR: Error fetching remote repo 'origin'
ERROR: Error fetching remote repo 'origin'



Not very descriptive, but maybe someone will find this ticket if searching on this error.  Perhaps JENKINS-9052 did not apply to JGit?



























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] [hockeyapp-plugin] (JENKINS-26200) Failed to scout net.hockeyapp.jenkins.releaseNotes.ChangelogReleaseNotes$DescriptorImpl

2014-12-22 Thread m.smollin...@gmail.com (JIRA)















































Matt Smollinger
 created  JENKINS-26200


Failed to scout net.hockeyapp.jenkins.releaseNotes.ChangelogReleaseNotes$DescriptorImpl















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


log.txt



Components:


hockeyapp-plugin



Created:


22/Dec/14 7:10 PM



Description:


Seems like since updating to 1.2.0 of hockeyapp, Jenkins has been unable to load the plugin. Here's a excerpt of the log, with the full log attached as a file:

Dec 22, 2014 1:50:45 PM WARNING hudson.ExtensionFinder$Sezpoz scout
Failed to scout net.hockeyapp.jenkins.releaseNotes.ChangelogReleaseNotes$DescriptorImpl
java.lang.InstantiationException: java.lang.UnsupportedClassVersionError: net/hockeyapp/jenkins/releaseNotes/ChangelogReleaseNotes$DescriptorImpl : Unsupported major.minor version 51.0
	at net.java.sezpoz.IndexItem.element(IndexItem.java:146)
	at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:666)
	at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:349)
	at hudson.ExtensionList.load(ExtensionList.java:300)
	at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253)
	at hudson.ExtensionList.iterator(ExtensionList.java:143)
	at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:348)
	at hudson.ExtensionList.load(ExtensionList.java:300)
	at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253)
	at hudson.ExtensionList.size(ExtensionList.java:162)
	at com.sonyericsson.hudson.plugins.gerrit.trigger.PluginImpl.postInitialize(PluginImpl.java:298)
	at hudson.PluginManager$2$1$2.run(PluginManager.java:386)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:903)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:695)
Caused by: java.lang.UnsupportedClassVersionError: net/hockeyapp/jenkins/releaseNotes/ChangelogReleaseNotes$DescriptorImpl : Unsupported major.minor version 51.0
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
	at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138)
	at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:768)
	at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309)
	at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365)
	at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44)
	at jenkins.ClassLoaderReflectionToolkit._findClass(ClassLoaderReflectionToolkit.java:86)
	at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:1110)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
	at net.java.sezpoz.IndexItem.element(IndexItem.java:134)
	... 19 more





Environment:


Jenkins version 1.595 running on OS X 10.9.5

Pertinent installed plugins: git, gerrit-trigger, Xcode




Project:


Jenkins



Priority:


Major



Reporter:


Matt Smollinger

[JIRA] [workflow-plugin] (JENKINS-26199) Build system requirements not listed















































Jesse Glick
 updated  JENKINS-26199


Build system requirements not listed
















Change By:


Jesse Glick
(22/Dec/14 7:12 PM)




Issue Type:


Improvement
Task





Labels:


testing



























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-26199) Build system requirements not listed















































Jesse Glick
 commented on  JENKINS-26199


Build system requirements not listed















There are no specific build requirements I know of, other than that many tests are known not to run on Windows (because they rely on the sh step and the like). Personally I use NetBeans with JDK 8 on Ubuntu 14.10.

So what are your test failures? (And do you really need to run all tests yourself, or would mvn -DskipTests clean install suffice? If you intend to submit changes, just file a pull request and your changes will be tested automatically.)

~/.jenkins/ is irrelevant for development; mvn hpi:run does not use it (it uses ./work), and tests using JenkinsRule certainly do not use it.



























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-20148) Misleading description of the 'workspace' permission

2014-12-22 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-20148


Misleading description of the workspace permission















Integrated in  jenkins_main_trunk #3885
 FIXED JENKINS-20148 Rephrase Workspace permission description (Revision 801f37d5a11554fb97bf9c8edbd9f3e5bd21a47f)

 Result = SUCCESS
daniel-beck : 801f37d5a11554fb97bf9c8edbd9f3e5bd21a47f
Files : 

	core/src/main/resources/hudson/model/Messages.properties





























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] [hockeyapp-plugin] (JENKINS-26200) Failed to scout net.hockeyapp.jenkins.releaseNotes.ChangelogReleaseNotes$DescriptorImpl

2014-12-22 Thread m.smollin...@gmail.com (JIRA)















































Matt Smollinger
 updated  JENKINS-26200


Failed to scout net.hockeyapp.jenkins.releaseNotes.ChangelogReleaseNotes$DescriptorImpl
















Change By:


Matt Smollinger
(22/Dec/14 7:20 PM)




Description:


Seemslikesinceupdatingto1.2.0ofhockeyapp,Jenkinshasbeenunabletoloadtheplugin.Heresaexcerptofthelog,withthefulllogattachedasafile:Dec22,20141:50:45PMWARNINGhudson.ExtensionFinder$SezpozscoutFailedtoscoutnet.hockeyapp.jenkins.releaseNotes.ChangelogReleaseNotes$DescriptorImpljava.lang.InstantiationException:java.lang.UnsupportedClassVersionError:net/hockeyapp/jenkins/releaseNotes/ChangelogReleaseNotes$DescriptorImpl:Unsupportedmajor.minorversion51.0	atnet.java.sezpoz.IndexItem.element(IndexItem.java:146)	athudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:666)	athudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:349)	athudson.ExtensionList.load(ExtensionList.java:300)	athudson.ExtensionList.ensureLoaded(ExtensionList.java:253)	athudson.ExtensionList.iterator(ExtensionList.java:143)	athudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:348)	athudson.ExtensionList.load(ExtensionList.java:300)	athudson.ExtensionList.ensureLoaded(ExtensionList.java:253)	athudson.ExtensionList.size(ExtensionList.java:162)	atcom.sonyericsson.hudson.plugins.gerrit.trigger.PluginImpl.postInitialize(PluginImpl.java:298)	athudson.PluginManager$2$1$2.run(PluginManager.java:386)	atorg.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)	atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)	atjenkins.model.Jenkins$7.runTask(Jenkins.java:903)	atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)	atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)	atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)	atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)	atjava.lang.Thread.run(Thread.java:695)Causedby:java.lang.UnsupportedClassVersionError:net/hockeyapp/jenkins/releaseNotes/ChangelogReleaseNotes$DescriptorImpl:Unsupportedmajor.minorversion51.0	atjava.lang.ClassLoader.defineClass1(NativeMethod)	atjava.lang.ClassLoader.defineClassCond(ClassLoader.java:637)	atjava.lang.ClassLoader.defineClass(ClassLoader.java:621)	atjenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138)	athudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:768)	atjenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309)	atjenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365)	atjenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325)	atsun.reflect.GeneratedMethodAccessor3.invoke(UnknownSource)	atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)	atjava.lang.reflect.Method.invoke(Method.java:597)	atjenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44)	atjenkins.ClassLoaderReflectionToolkit._findClass(ClassLoaderReflectionToolkit.java:86)	athudson.PluginManager$UberClassLoader.findClass(PluginManager.java:1110)	atjava.lang.ClassLoader.loadClass(ClassLoader.java:306)	atjava.lang.ClassLoader.loadClass(ClassLoader.java:247)	atnet.java.sezpoz.IndexItem.element(IndexItem.java:134)	...19more
Canconfirmdowngradingto1.1.0resolvesthisissue.



























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] [hockeyapp-plugin] (JENKINS-23549) HockeyApp Plugin : ArrayIndexOutOfBoundsException

2014-12-22 Thread antek.baran...@gmail.com (JIRA)















































Antek Baranski
 commented on  JENKINS-23549


HockeyApp Plugin : ArrayIndexOutOfBoundsException















What version are you using? Here is the snippet of code that does the empty / 0 check, so I don't see how what you are seeing could happen: 

if (application.libsPath != null  !application.libsPath.isEmpty()) {
  FilePath remoteLibsFiles[] = remoteWorkspace.list(vars.expand(application.libsPath));
  // Take the first one that matches the pattern
  if (remoteLibsFiles.length == 0) {
listener.getLogger().println("No LIBS found to upload in: " + vars.expand(application.libsPath));
return this.failGracefully;
  }



























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-26201) Unreleased workspace locks after SCM polling

Jesse Glick
created JENKINS-26201

Unreleased workspace locks after SCM polling

Issue Type:

Bug

Assignee:

Jesse Glick

Components:

core

Created:

22/Dec/14 8:04 PM

Description:

A user reports many builds stuck waiting for a lock on the project's primary workspace (not @2, etc.), which should only be possible if some code has acquired a "quick" lease on the workspace but then failed to ever release it. There are no threads shown holding the workspace lock. Several threads in AbstractProject.pollWithWorkspace and elsewhere are waiting for it, in some cases for days.

https://github.com/jenkinsci/jenkins/blob/jenkins-1.580.1/core/src/main/java/hudson/model/AbstractProject.java#L1442-1445 shows a potential window of vulnerability: if getBuiltOn, createLauncher, decorateByEnv, or getEnvironment threw an exception, and it went reported or was somehow lost in the logs, the lease could be left locked indefinitely.

Project:

Jenkins

Labels:

workspace
lock
robustness
polling

Priority:

Major

Reporter:

Jesse Glick

[JIRA] [core] (JENKINS-26201) Unreleased workspace locks after SCM polling















































Jesse Glick
 started work on  JENKINS-26201


Unreleased workspace locks after SCM polling
















Change By:


Jesse Glick
(22/Dec/14 8:05 PM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github-plugin] (JENKINS-26202) Can't save project configurations

2014-12-22 Thread gabriel...@gmail.com (JIRA)















































Gabriel Corrêa de Oliveira
 created  JENKINS-26202


Cant save project configurations















Issue Type:


Bug



Assignee:


Unassigned


Components:


github-plugin



Created:


22/Dec/14 8:18 PM



Description:


After upgrading Jenkins to the latest versions, I can no longer save project configurations.

An error page with the following exception is show:


javax.servlet.ServletException: java.lang.AssertionError: class com.cloudbees.jenkins.GitHubPushTrigger is missing its descriptor
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
	at

[JIRA] [core] (JENKINS-26201) Unreleased workspace locks after SCM polling















































Jesse Glick
 commented on  JENKINS-26201


Unreleased workspace locks after SCM polling















http://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-war/1.580.1.JENKINS-26201-workspace-lock-1/jenkins-war-1.580.1.JENKINS-26201-workspace-lock-1.war may be used to test a backport of this.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-20258) Git plugin with checkout to subdir and prune stale branches fails all builds















































pmv
 commented on  JENKINS-20258


Git plugin with checkout to subdir and prune stale branches fails all builds















Created and linked JENKINS-26197.



























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-26199) Build system requirements not listed

2014-12-22 Thread tg9...@gmx-topmail.de (JIRA)















































Thomas Goeppel
 commented on  JENKINS-26199


Build system requirements not listed















You're using Ubuntu, too - that's great (and safes me a lot of money, and frustration :-]) I'll give Netbeans one more try, the Stapler plugin makes me curious.

First, here is the CpsScriptTest failure I get: 

```
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.815 sec  FAILURE! - in org.jenkinsci.plugins.workflow.cps.CpsScriptTest
evaluateShallBeCpsTransformed(org.jenkinsci.plugins.workflow.cps.CpsScriptTest)  Time elapsed: 2.715 sec   FAILURE!
org.codehaus.groovy.runtime.powerassert.PowerAssertionError: assert future != null





   null   false
	at org.codehaus.groovy.runtime.InvokerHelper.assertFailed(InvokerHelper.java:386)
	at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.assertFailed(ScriptBytecodeAdapter.java:658)
	at org.jenkinsci.plugins.workflow.cps.CpsScriptTest.evaluateShallBeCpsTransformed(CpsScriptTest.groovy:74)


Results :

Failed tests: 
  CpsScriptTest.evaluateShallBeCpsTransformed:74 assert future != null





   null   false

Tests run: 21, Failures: 1, Errors: 0, Skipped: 0
```

The test code in tag 'workflow-1.1' was different, but it failed, too. 

Second, you may have guessed that I'm a Jenkins-dev newbie (comming from the world of embedded control). I assumed that I better don't issue any pull-request before I know that my code doesn't break tests (which I can't when I switch off tests . Assumptions are often wrong, but I read all the docs on development carefully, and it they only told me to run 'mvn clean install', there is no word about skipping the tests. Of course, you must assume a certain 'dev proficiency', but sometimes such things make the learning curve steep.

Third, try adding a directory ~/.jenkins without write access, and run 'mvn clean install'. On my machine this makes (many) tests fail. On the other hand, if that folder doesn't exist, it's there after the test are done.

This is what I find there: 

```
thomas@thomas-W500:~$ ls .jenkins/
cache
thomas@thomas-W500:~$ ls .jenkins/cache/
jars
thomas@thomas-W500:~$ ls .jenkins/cache/jars/
04  1A  2C  3A  4B  50  53  63  68  76  86  94  A7  D2  DB  F5
09  1F  37  43  4F  52  61  65  69  78  8D  9B  C2  D5  F2  FE
thomas@thomas-W500:~$ ls .jenkins/cache/jars/04
66AB2CDE8F87045B932F61151D38B9.jar
```

Maybe that's because I run 'mvn install' from the workflow-plugin root, and not from 'aggregator', but in my opinion that's not obvious.

It would also have been helpful to know, where I should run 'mvn hpi:run' (maybe it's obvious, but the workflow plugin is a 'bit' more complex than most examples , and I have still to figure out how to do this with netbeans).

Of course, most of this isn't a problem of the workflow-plugin, but every bit of information helps.



























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-19392) First-time display with many Maven jobs blocked in FingerprintAction.compact
















































Jesse Glick
 assigned  JENKINS-19392 to Jesse Glick



First-time display with many Maven jobs blocked in FingerprintAction.compact
















Change By:


Jesse Glick
(22/Dec/14 9:01 PM)




Assignee:


JesseGlick



























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-19392) First-time display with many Maven jobs blocked in FingerprintAction.compact















































Jesse Glick
 started work on  JENKINS-19392


First-time display with many Maven jobs blocked in FingerprintAction.compact
















Change By:


Jesse Glick
(22/Dec/14 9:01 PM)




Status:


Open
InProgress



























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-26199) CpsScriptTest.evaluateShallBeCpsTransformed failures















































Jesse Glick
 updated  JENKINS-26199


CpsScriptTest.evaluateShallBeCpsTransformed failures
















Change By:


Jesse Glick
(22/Dec/14 9:37 PM)




Summary:


Buildsystemrequirementsnotlisted
CpsScriptTest.evaluateShallBeCpsTransformedfailures





Assignee:


JesseGlick
KohsukeKawaguchi



























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-26199) Build system requirements not listed

Jesse Glick
commented on JENKINS-26199

Build system requirements not listed

Stapler plugins are available for both NetBeans and IntelliJ. Either are well supported for Jenkins plugin development. Eclipse is not well supported.

I did not write CpsScriptTest but perhaps Kohsuke Kawaguchi can take a look at that failure. Anyway, a single test failure is not much cause for concern, when there are a number of tests that fail on occasion, perhaps due to race conditions. You can just file a pull request and a Jenkins builder will automatically run all tests against your changes and report any failures, which plugin maintainers would evaluate to see if they are significant or not. I rarely run all tests in the Workflow plugin myself, as it would take much too long; I would only run tests I think might be related to changes I am making.

~/.jenkins/cache/ is JENKINS-18578.

For Workflow, hpi:run should be run inside aggregator, which from NetBeans you can do via just pressing Run Project when you have the Jenkins developer plugin installed: https://github.com/jenkinsci/workflow-plugin/blob/master/README.md#source-organization

By the way, if you are unfamiliar with Jenkins development, I will warn you that many (though not all) parts of Workflow are especially tough to get into, compared to most other Jenkins plugins.

[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable















































Jesse Glick
 updated  JENKINS-18578


Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
















Change By:


Jesse Glick
(22/Dec/14 9:38 PM)




Labels:


cacheconfiguration
jenkins
robustness
slave



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [perforce-plugin] (JENKINS-20553) matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME

2014-12-22 Thread richard....@gmail.com (JIRA)















































Richard Joh
 commented on  JENKINS-20553


matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME 















In which version, will this fix be released?  I have Perforce plugin 1.3.31 and still have this problem.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23487) Add support of shared directories mapping to Windows slave services

2014-12-22 Thread michelene.c...@am.sony.com (JIRA)















































M Chon
 commented on  JENKINS-23487


Add support of shared directories mapping to Windows slave services















I am trying to set up my Windows Jenkins server to use a NetApp filer partition for workspaces.
It seems to work OK in a Cygwin shell, but breaks in a Windows batch shell:

Started by user jdoe
Building in workspace \\nas02\bld101_workspaces$\jdoe_test\workspace
workspace $ C:\cygwin\bin\bash.exe -xe C:\UsersSVC\AppData\Local\Temp\hudson3077854122063339861.sh
+ pwd
//nas02/bld101_workspaces$/jdoe_test/workspace
+ touch save_bash.txt
workspace $ cmd /c call C:\UsersSVC\AppData\Local\Temp\hudson527196630851665020.bat
'\\nas02\bld101_workspaces$\joe_test\workspace'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported.  Defaulting to Windows directory.



























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-23487) Add support of shared directories mapping to Windows slave services

2014-12-22 Thread michelene.c...@am.sony.com (JIRA)













































 
M Chon
 edited a comment on  JENKINS-23487


Add support of shared directories mapping to Windows slave services
















I am trying to set up my Windows Jenkins server to use a NetApp filer partition for workspaces.
It seems to work OK in a Cygwin shell, but breaks in a Windows batch shell:

Started by user jdoe
Building in workspace \\nas02\bld101_workspaces$\jdoe_test\workspace
workspace $ C:\cygwin\bin\bash.exe -xe C:\UsersSVC\AppData\Local\Temp\hudson3077854122063339861.sh
+ pwd
//nas02/bld101_workspaces$/jdoe_test/workspace
+ touch save_bash.txt
workspace $ cmd /c call C:\UsersSVC\AppData\Local\Temp\hudson527196630851665020.bat
'\\nas02\bld101_workspaces$\joe_test\workspace'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported.  Defaulting to Windows directory.

C:\Windowsdir



























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















































Jesse Glick
 updated  JENKINS-25628


config.xml files do not end in newline
















Change By:


Jesse Glick
(22/Dec/14 9:47 PM)




Labels:


xstream



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [perforce-plugin] (JENKINS-20553) matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME

2014-12-22 Thread mr...@sjm.com (JIRA)















































Michael Rose
 commented on  JENKINS-20553


matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME 















There haven't been any release for the perforce plugin in a long time. I don't think it is being developed anymore. I migrated my projects to use p4 plugin instead. The plugin is relatively new; it has some new functionality, but is also missing some of the functionality of the perforce plugin. It is still being actively developed though and Paul Allen has been pretty good about providing support.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher

2014-12-22 Thread daniel.fi...@gmail.com (JIRA)















































Daniel Figus
 commented on  JENKINS-24786


Since 2.2.6, environment variables are not expanded in git publisher















Created pull request 283 containing fix and tests. The updated git-plugin runs in our production jenkins without issues. Could you please review and provide feedback?



























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] [unreliable-slave-plugin] (JENKINS-23568) Unreliable slave Plugin will offline the slave or not? what’s the meaning of “try slave reconnect of put offline”? how to use the plugin?
















































SCM/JIRA link daemon
 resolved  JENKINS-23568 as Fixed


Unreliable slave Plugin will offline the slave or not? what’s the meaning of “try slave reconnect of put offline”? how to use the plugin?
















Change By:


SCM/JIRA link daemon
(22/Dec/14 10:02 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] [core] (JENKINS-19392) First-time display with many Maven jobs blocked in FingerprintAction.compact















































SCM/JIRA link daemon
 commented on  JENKINS-19392


First-time display with many Maven jobs blocked in FingerprintAction.compact















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/tasks/Fingerprinter.java
http://jenkins-ci.org/commit/jenkins/2f59ffc475dc73a9a9cd5a7596819f3242c22f6f
Log:
  FIXED JENKINS-19392 Simpler and more efficient to use String.intern to compact fingerprint data.
This should work across builds and even across jobs, and does not force us to load other builds.


Compare: https://github.com/jenkinsci/jenkins/compare/c5c6bc050d49...2f59ffc475dc




























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-19392) First-time display with many Maven jobs blocked in FingerprintAction.compact
















































SCM/JIRA link daemon
 resolved  JENKINS-19392 as Fixed


First-time display with many Maven jobs blocked in FingerprintAction.compact
















Change By:


SCM/JIRA link daemon
(22/Dec/14 10:02 PM)




Status:


InProgress
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] [unreliable-slave-plugin] (JENKINS-23568) Unreliable slave Plugin will offline the slave or not? what’s the meaning of “try slave reconnect of put offline”? how to use the plugin?