[JIRA] (JENKINS-54656) cvs plugin broken - not possible to add new projects

2018-11-15 Thread rolf.offerma...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rolf Offermanns created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54656  
 
 
  cvs plugin broken - not possible to add new projects   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 jenkins-cvs-settings.png  
 
 
Components: 
 cvs-plugin  
 
 
Created: 
 2018-11-15 17:31  
 
 
Environment: 
 Jenkins 2.138.3 from official docker:lts image  cvs-plugin 2.14  
 
 
Labels: 
 cvs plugin  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Rolf Offermanns  
 

  
 
 
 
 

 
 The plugin crashes when trying to save a new project or edit an existing one (with a configured CVS repository). The problem seems to be the Exclude Regions setting, which does not show an input field and hence is null in the constructor. I will attach a screenshot of the settings dialog. The stack trace is this: java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at 

[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported

2015-02-19 Thread rolf.offerma...@gmx.net (JIRA)














































Rolf Offermanns
 commented on  JENKINS-22853


SEVERE: Trying to unexport an object thats already unexported















Seeing this multiple times per day (on heavy use even per hour). I have a setup with 6 slaves with 6 build processors, all running freestyle shell jobs. I build around 400 jobs per hour and have 2 out of 500 fails because of this problem. Please let me know if you need more information.
Example backtrace (this is 1.599 with slave ver. 2.49):

java.lang.IllegalStateException: Invalid object ID 13906 iota=13907
	at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354)
	at hudson.remoting.ExportTable.get(ExportTable.java:330)
	at hudson.remoting.Channel.getExportedObject(Channel.java:604)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
	at ..remote call to otto(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
	at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
	at hudson.remoting.Channel.call(Channel.java:752)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179)
	at com.sun.proxy.$Proxy66.join(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979)
	at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
	at hudson.model.Build$BuildExecution.build(Build.java:199)
	at hudson.model.Build$BuildExecution.doRun(Build.java:160)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536)
	at hudson.model.Run.execute(Run.java:1718)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)
Caused by: java.lang.Exception: Object was recently deallocated
#13906 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=hudson.Launcher$RemoteProcess
  Created at Thu Feb 19 11:24:20 CET 2015
	at hudson.remoting.ExportTable$Entry.init(ExportTable.java:99)
	at hudson.remoting.ExportTable.export(ExportTable.java:305)
	at hudson.remoting.Channel.internalExport(Channel.java:600)
	at hudson.remoting.Channel.export(Channel.java:591)
	at hudson.remoting.Channel.export(Channel.java:561)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
  Released at Thu Feb 19 11:24:20 CET 2015
	at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131)
	at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382)
	at hudson.remoting.Channel.unexport(Channel.java:612)
	at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43)
	at hudson.remoting.Channel$2.handle(Channel.java:483)
	at 

[JIRA] [publish-over-ssh-plugin] (JENKINS-19811) PublishOverSSHPlugin fails occasionally because jsch exception ( verify: false )

2015-02-03 Thread rolf.offerma...@gmx.net (JIRA)














































Rolf Offermanns
 commented on  JENKINS-19811


PublishOverSSHPlugin fails occasionally because jsch exception ( verify: false )















Unfortunately the jsch update does not fix it for me. I still see the verify:false errors. I am currently running an ssh plugin build from ericcitaire:master.



























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







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


[JIRA] [job-dsl-plugin] (JENKINS-25922) Add support for Publish Over SSH

2015-01-27 Thread rolf.offerma...@gmx.net (JIRA)














































Rolf Offermanns
 commented on  JENKINS-25922


Add support for Publish Over SSH















The support is incomplete. The current implementation only allows to use the plugin in a step context. It can also be used in a publisher context, which is not implemented, yet. Shall I open a new issue for 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] [job-dsl-plugin] (JENKINS-26636) publishOverSSH support incomplete - missing publisher context

2015-01-27 Thread rolf.offerma...@gmx.net (JIRA)














































Rolf Offermanns
 created  JENKINS-26636


publishOverSSH support incomplete - missing publisher context















Issue Type:


Bug



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


27/Jan/15 4:05 PM



Description:


Support for the publishOverSSH was added in JENKINS 25922.
The publishOverSSH can be added within the builders/ section, which is the method currently supported via job-dsl. However the publishOverSSH plugin can also be added to the publishers/ section, which is currently not supported via job-dsl.

As far as I can see, the sub-node is identical in both sections. I will attach a config.xml snippet.

Please add support for using the plugin in the publishers section.




Environment:


job-dsl-plugin: 1.28




Project:


Jenkins



Priority:


Minor



Reporter:


Rolf Offermanns

























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] [job-dsl-plugin] (JENKINS-26636) publishOverSSH support incomplete - missing publisher context

2015-01-27 Thread rolf.offerma...@gmx.net (JIRA)














































Rolf Offermanns
 commented on  JENKINS-26636


publishOverSSH support incomplete - missing publisher context















Working config.xml snippet:

...
 publishers
jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin plugin="publish-over-ssh@1.12"
  consolePrefixSSH: /consolePrefix
  delegate
publishers
  jenkins.plugins.publish_over_ssh.BapSshPublisher
configNamemySSHHost/configName
verbosefalse/verbose
transfers
  jenkins.plugins.publish_over_ssh.BapSshTransfer
remoteDirectory/remoteDirectory
sourceFiles*.rpm/sourceFiles
excludes/excludes
removePrefix/removePrefix
   remoteDirectorySDFfalse/remoteDirectorySDF
flattenfalse/flatten
cleanRemotefalse/cleanRemote
noDefaultExcludesfalse/noDefaultExcludes
makeEmptyDirsfalse/makeEmptyDirs
patternSeparator, +/patternSeparator
execCommand/execCommand
execTimeout12/execTimeout
usePtyfalse/usePty
  /jenkins.plugins.publish_over_ssh.BapSshTransfer
/transfers
useWorkspaceInPromotionfalse/useWorkspaceInPromotion
usePromotionTimestampfalse/usePromotionTimestamp
  /jenkins.plugins.publish_over_ssh.BapSshPublisher
/publishers
continueOnErrorfalse/continueOnError
failOnErrorfalse/failOnError
alwaysPublishFromMasterfalse/alwaysPublishFromMaster
hostConfigurationAccess class="jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin" reference="../.."/
  /delegate
/jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin
  /publishers



























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.