[JIRA] (JENKINS-38103) Need command to restart previously stopped container

2016-09-09 Thread arungu...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 arungupta created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38103  
 
 
  Need command to restart previously stopped container   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2016/Sep/09 2:10 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 arungupta  
 

  
 
 
 
 

 
 docker global variable does not seem to have a method to restart a previous stopped container. Image.run gives a container, Container only has stop method that stops and removes the container. Following two commands would be useful: 
 
Container.stop that only stops the container and does not remove it 
Container.restart restarts the previously stopped container 
 These would be useful methods, particularly for stateful containers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] [workflow-plugin] (JENKINS-30432) "Scripts not permitted to use method" in Jenkins Workflow

2015-09-16 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30432 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Scripts not permitted to use method" in Jenkins Workflow  
 
 
 
 
 
 
 
 
 
 
Can you explain in simple language on how https://github.com/javaee-samples/docker-java/blob/master/attendees/cicd/jenkins/plugins.txt would evolve? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [docker] (JENKINS-30361) Dependencies are not resolved for plugins.txt

2015-09-16 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Dependencies are not resolved for plugins.txt  
 
 
 
 
 
 
 
 
 
 
How would a simplified plugins.txt look like? 
Here is mine: 
https://github.com/javaee-samples/docker-java/blob/master/attendees/cicd/jenkins/plugins.txt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [docker] (JENKINS-30361) Dependencies are not resolved for plugins.txt

2015-09-16 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Dependencies are not resolved for plugins.txt  
 
 
 
 
 
 
 
 
 
 
Adding script-security 1.15 failed with: 

 

Sep 16, 2015 8:10:32 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin docker-commons
java.io.IOException: Dependency authentication-tokens (1.1) doesn't exist
	at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:480)
	at hudson.PluginManager$2$1$1.run(PluginManager.java:369)
	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:904)
	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.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Sep 16, 2015 8:10:32 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin docker-workflow
java.io.IOException: Dependency docker-commons (1.0) doesn't exist
	at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:480)
	at hudson.PluginManager$2$1$1.run(PluginManager.java:369)
	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:904)
	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.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
 

 
So added these two versions to plugins.txt. And now the image is giving: 

 

Sep 16, 2015 8:27:46 PM hudson.ExtensionFinder$Sezpoz scout
WARNING: Failed to scout org.jenkinsci.plugins.docker.commons.credentials.DockerServerCredentials$DescriptorImpl
java.lang.InstantiationException: java.lang.NoClassDefFoundError: com/cloudbees/plugins/credentials/impl/BaseStandardCredentials$BaseStandardCredentialsDescriptor
	at net.java.sezpoz.IndexItem.element(IndexItem.java:146)
	at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:666)
	at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:380)
	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:379)
	at hudson.ExtensionList.load(ExtensionList.java:300)
	at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253)
	at hudson.ExtensionList.get(ExtensionList.java:158)
	at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1257)
	at hudson.maven.PluginImpl.init(PluginImpl.java:58)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106)
	at 

[JIRA] [workflow-plugin] (JENKINS-30432) "Scripts not permitted to use method" in Jenkins Workflow

2015-09-14 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30432 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Scripts not permitted to use method" in Jenkins Workflow  
 
 
 
 
 
 
 
 
 
 
Workflow plugin is 1.10 Script Security is 1.13 
Docker image is created using https://github.com/javaee-samples/docker-java/tree/master/attendees/cicd/jenkins 
Specifying complete list of plugins is quite painful anyway. I was hoping that it would resolve the dependencies but apparently not, related to: https://issues.jenkins-ci.org/browse/JENKINS-30361 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30432) "Scripts not permitted to use method" in Jenkins Workflow

2015-09-14 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30432 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Scripts not permitted to use method" in Jenkins Workflow  
 
 
 
 
 
 
 
 
 
 
Dependency resolution is really messy and need to be cleaned up. I hope you don't expect developers to know each and every possible combination to work. If some combinations don't work, then an error should be thrown in the console, or a message be displayed. 
Can you help me create an exact list of plugins.txt? Or is this the only change required? 
A PR will be really useful. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [docker] (JENKINS-30361) Dependencies are not resolved for plugins.txt

2015-09-14 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Dependencies are not resolved for plugins.txt  
 
 
 
 
 
 
 
 
 
 
Is there a concept of latest plugin? I don't care about a particular version but just want the latest. 
Where can I find more details about Support Core plugin sample? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [docker] (JENKINS-30361) Dependencies are not resolved for plugins.txt

2015-09-14 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Dependencies are not resolved for plugins.txt  
 
 
 
 
 
 
 
 
 
 
How do I install it using plugins.txt? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30432) "Scripts not permitted to use method" in Jenkins Workflow

2015-09-14 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30432 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Scripts not permitted to use method" in Jenkins Workflow  
 
 
 
 
 
 
 
 
 
 
For a Docker image, how would the list of plugins be created otherwise? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30432) "Scripts not permitted to use method" in Jenkins Workflow

2015-09-14 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30432 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Scripts not permitted to use method" in Jenkins Workflow  
 
 
 
 
 
 
 
 
 
 
Jenkins version: 1.609.2 
Workflow: https://github.com/arun-gupta/javaee7-docker-workflow/blob/master/Jenkinsfile 
What else is needed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30432) "Scripts not permitted to use method" in Jenkins Workflow

2015-09-13 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30432 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Scripts not permitted to use method" in Jenkins Workflow  
 
 
 
 
 
 
 
 
 
 
Worked around by going to Manage Jenkins -> In-process Script Approval, and clicking on "Approve" button for invokeMethod. 
Weird, but worked! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30432) "Scripts not permitted to use method" in Jenkins Workflow

2015-09-13 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30432 
 
 
 
  "Scripts not permitted to use method" in Jenkins Workflow  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 13/Sep/15 11:13 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 arungupta 
 
 
 
 
 
 
 
 
 
 
Inlining the script https://github.com/arun-gupta/javaee7-docker-workflow/blob/master/Jenkinsfile in Jenkins workflow builds the project successfully. But referring as a SCM script gives the following error: 
First time build. Skipping changelog. Running: Allocate node : Start Running on master in /var/jenkins_home/jobs/hello2/workspace Running: Allocate node : Body : Start Running: Allocate node : Body : End Running: Allocate node : End Running: End of Workflow org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:150) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:77) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:60) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:103) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:100) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15) at WorkflowScript.run(WorkflowScript:2) at Unknown.Unknown(Unknown) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:69) at 

[JIRA] [core] (JENKINS-30431) Space in job name causes a spurious message from Maven

2015-09-13 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30431 
 
 
 
  Space in job name causes a spurious message from Maven  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 13/Sep/15 10:01 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 arungupta 
 
 
 
 
 
 
 
 
 
 
If the job's name contain a space then Maven is giving the following error: 
/tmp/apache-maven-3.3.3/bin/mvn: 200: local: Docker/workspace: bad variable name 
The job name is "Hello Docker" 
Jenkins version: 1.609.2 
The job succeeds fine but the warning message is suspicious. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

[JIRA] [docker] (JENKINS-30361) Dependencies are not resolved for plugins.txt

2015-09-09 Thread arungu...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 arungupta commented on  JENKINS-30361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Dependencies are not resolved for plugins.txt  
 
 
 
 
 
 
 
 
 
 
What would be the correct way to install the plugins? I'd like to specify only the plugin and Jenkins should be able to resolve the dependencies. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.