[JIRA] (JENKINS-41641) Timeout waits even when slave is offline

2017-02-01 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41641  
 
 
  Timeout waits even when slave is offline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline, workflow-basic-steps-plugin  
 
 
Created: 
 2017/Feb/01 10:42 PM  
 
 
Environment: 
 org.jenkins-ci.main:jenkins-war:2.32.1  org.springframework:spring-webmvc:2.5.6.SEC03  commons-beanutils:commons-beanutils:1.8.3  oro:oro:2.0.8  org.jenkins-ci:task-reactor:1.4  org.kohsuke.stapler:stapler-jrebel:1.248  org.jenkins-ci.ui:handlebars:1.1.1  org.jenkins-ci.dom4j:dom4j:1.6.1-jenkins-4  org.jenkins-ci.modules:instance-identity:2.1  org.ow2.asm:asm-analysis:4.0  stax:stax-api:1.0.1  org.jenkins-ci.main:jenkins-core:2.32.1  org.jenkins-ci.modules:ssh-cli-auth:1.2  org.jenkins-ci:bytecode-compatibility-transformer:1.8  commons-jelly:commons-jelly-tags-xml:1.1  org.ow2.asm:asm-commons:4.0  org.kohsuke:access-modifier-annotation:1.4  org.samba.jcifs:jcifs:1.3.17-kohsuke-1  org.springframework:spring-dao:1.2.9  org.springframework:spring-aop:2.5.6.SEC03  org.fusesource.jansi:jansi:1.11  commons-httpclient:commons-httpclient:3.1  com.github.jnr:jnr-posix:3.0.1  org.codehaus.woodstox:wstx-asl:3.2.9  org.springframework:spring-core:2.5.6.SEC03  org.kohsuke:asm5:5.0.1  com.google.inject:guice:4.0  org.mindrot:jbcrypt:0.3m  org.apache.commons:commons-compress:1.10  com.github.jnr:jnr-constants:0.8.5  org.jvnet.libzfs:libzfs:0.5  org.jenkins-ci.ui:bootstrap:1.3.2  jfree:jcommon:1.0.12  org.jvnet:tiger-types:2.2  javax.xml.stream:stax-api:1.0-2  org.kohsuke:trilead-putty-extension:1.2  org.kohsuke.stapler:stapler-adjunct-zeroclipboard:1.3.5-1  org.apache.ant:ant:1.8.4  org.kohsuke.stapler:stapler-adjunct-codemirror:1.3  com.jcraft:jzlib:1.1.3-kohsuke-1  org.jenkins-ci.modules:slave-installer:1.5  org.kohsuke:libpam4j:1.8  org.jenkins-ci.main:remoting:3.2  commons-jelly:commons-jelly-tags-fmt:1.0  jline:jline:2.12  org.ow2.asm:asm-util:4.0  javax.servlet:jstl:1.1.0  org.jenkins-ci:winstone:3.1  com.github.jnr:jnr-ffi:1.0.7  net.java.sezpoz:sezpoz:1.12  org.apache.ant:ant-launcher:1.8.4  org.jenkins-ci:trilead-ssh2:build217-jenkins-8  commons-io:commons-io:2.4  com.github.jnr:jffi:1.2.7  org.jenkins-ci.modules:upstart-slave-installer:1.1  org.jvnet.hudson:jtidy:4aug2000r7-dev-hudson-1  org.jenkins-ci.modules:windows-slave-installer:1.6  org.kohsuke.stapler:stapler-jelly:1.248  org.springframework:spring-web:2.5.6.SEC03  org.jvnet.winp:winp:1.24  org.kohsuke.stapler:stapler-adjunct-timeline:1.4  org.apache.mina:mina-core:2.0.5  javax.annotation:javax.annotation-api:1.2  org.jenkins-ci:crypto-util:1.1  commons-discovery:commons-discovery:0.4  

[JIRA] (JENKINS-37366) Pipeline "currentBuild" should expose project name

2017-02-01 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary commented on  JENKINS-37366  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline "currentBuild" should expose project name   
 

  
 
 
 
 

 
 Can you use `env.JOB_NAME` instead? http://stackoverflow.com/a/41345704  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36724) Branch indexing hangs

2016-08-01 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary edited a comment on  JENKINS-36724  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Branch indexing hangs
 

  
 
 
 
 

 
 After a few days there are so many "Branch Indexing" messages that it fills up the screen and doesn't process new PRs anymore. :( !branch-indexing-hangs-2.png|thumbnail! *Jenkins needs to be restarted for this to be  fixed  bypassed .*  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36724) Branch indexing hangs

2016-08-01 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary edited a comment on  JENKINS-36724  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Branch indexing hangs
 

  
 
 
 
 

 
 After a few days there are so many "Branch Indexing" messages that it fills up the screen and doesn't process new PRs anymore. :( !branch-indexing-hangs-2.png|thumbnail!*Jenkins needs to be restarted for this to be fixed.*  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36724) Branch indexing hangs

2016-08-01 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary commented on  JENKINS-36724  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Branch indexing hangs
 

  
 
 
 
 

 
 After a few days there are so many "Branch Indexing" messages that it fills up the screen and doesn't process new PRs anymore.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36724) Branch indexing hangs

2016-08-01 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36724  
 
 
  Branch indexing hangs
 

  
 
 
 
 

 
Change By: 
 Shauvik Roy Choudhary  
 
 
Attachment: 
 branch-indexing-hangs-2.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36964) Parallel Docker pipeline

2016-07-28 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary edited a comment on  JENKINS-36964  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel Docker pipeline
 

  
 
 
 
 

 
 I think the docker-workflow-plugin is  perhaps  engineered to work with a single container at a time.  Please close this issue if that's the direction. However, I think it should support multiple containers.  Here is how I got my project to work by using the native docker commands by sh and not using this plugin , like this :{code}node {  def runCmd = { cmd ->sh "docker run --rm -v /home/mn:/src/mn ubuntu:latest ${cmd}"}stage 'Build'  runCmd 'npm install'  parallel ("frontend": {  runCmd "make frontend"},"backend": {  runCmd "make backend"}  )}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36964) Parallel Docker pipeline

2016-07-28 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary commented on  JENKINS-36964  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel Docker pipeline
 

  
 
 
 
 

 
 I think the docker-workflow-plugin is engineered to work with a single container at a time. I got my project to work by using the native docker commands by sh and not using this plugin, like this: 

 

node {
  def runCmd = { cmd ->
sh "docker run --rm -v /home/mn:/src/mn ubuntu:latest ${cmd}"
}
  
  stage 'Build'
  runCmd 'npm install'
  parallel (
"frontend": {
  runCmd "make frontend"
},
"backend": {
  runCmd "make backend"
}
  )
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36964) Parallel Docker pipeline

2016-07-28 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36964  
 
 
  Parallel Docker pipeline
 

  
 
 
 
 

 
Change By: 
 Shauvik Roy Choudhary  
 
 
Priority: 
 Critical Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36964) Parallel Docker pipeline

2016-07-27 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary edited a comment on  JENKINS-36964  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel Docker pipeline
 

  
 
 
 
 

 
 The problem is that the plugin seems to start two docker containers but then sends subsequent commands to the same container.Here are the two docker run commands on the console.{code :bash }[frontend] + docker run -d -t -v /home/mn:/src/mn ubuntu:latest:latest[backend] + docker run -d -t -v /home/mn:/src/mn ubuntu:latest{code}And here are the two docker exec commands:{code :bash }[frontend] + docker exec ce0926c89968932f4e5ff3a85fc39c16d435888c909c4e074cc1dd2af82e594b make frontend[backend] + docker exec ce0926c89968932f4e5ff3a85fc39c16d435888c909c4e074cc1dd2af82e594b make backend{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36964) Parallel Docker pipeline

2016-07-27 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary commented on  JENKINS-36964  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel Docker pipeline
 

  
 
 
 
 

 
 The problem is that the plugin seems to start two docker containers but then sends subsequent commands to the same container. Here are the tro docker run commands on the console. {{ [frontend] + docker run -d -t -v /home/mn:/src/mn ubuntu:latest:latest [backend] + docker run -d -t -v /home/mn:/src/mn ubuntu:latest }} And here are the two docker exec commands: {{ [frontend] + docker exec ce0926c89968932f4e5ff3a85fc39c16d435888c909c4e074cc1dd2af82e594b make frontend [backend] + docker exec ce0926c89968932f4e5ff3a85fc39c16d435888c909c4e074cc1dd2af82e594b make backend }}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36964) Parallel Docker pipeline

2016-07-27 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary edited a comment on  JENKINS-36964  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel Docker pipeline
 

  
 
 
 
 

 
 The problem is that the plugin seems to start two docker containers but then sends subsequent commands to the same container.Here are the  tro  two  docker run commands on the console.  { { code:bash} [frontend] + docker run -d -t -v /home/mn:/src/mn ubuntu:latest:latest[backend] + docker run -d -t -v /home/mn:/src/mn ubuntu:latest {code } } And here are the two docker exec commands:{ { code:bash} [frontend] + docker exec ce0926c89968932f4e5ff3a85fc39c16d435888c909c4e074cc1dd2af82e594b make frontend[backend] + docker exec ce0926c89968932f4e5ff3a85fc39c16d435888c909c4e074cc1dd2af82e594b make backend {code } }  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36964) Parallel Docker pipeline

2016-07-26 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36964  
 
 
  Parallel Docker pipeline
 

  
 
 
 
 

 
Change By: 
 Shauvik Roy Choudhary  
 

  
 
 
 
 

 
 docker withRun does not create separate containers when run within a parallel block. The output of the first step is shown in all steps. In the following example, "make frontend" fails and  it's  its  output is repeated in the shell steps of both frontend and backend steps.{code:java}node {  def runCmd = { cmd ->docker.image("ubuntu:latest").withRun("-t -v /home/mn:/src/mn") { c ->sh "docker exec ${c.id} ${cmd}"}}stage 'Build'  runCmd 'npm install'  parallel ("frontend": {  runCmd "make frontend"},"backend": {  runCmd "make backend"}  )}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36964) Parallel Docker pipeline

2016-07-26 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36964  
 
 
  Parallel Docker pipeline
 

  
 
 
 
 

 
Change By: 
 Shauvik Roy Choudhary  
 

  
 
 
 
 

 
 docker withRun does not create separate containers when run within a parallel block. The output of the first step is shown in all steps.In the following example, "make frontend" fails and it's output is repeated in the shell steps of both frontend and backend steps.   {code:java}node {  def runCmd = { cmd ->docker.image("ubuntu:latest").withRun("-t -v /home/mn:/src/mn") { c ->sh "docker exec ${c.id} ${cmd}"}}stage 'Build'  runCmd 'npm install'  parallel ("frontend": {  runCmd "make frontend"},"backend": {  runCmd "make backend"}  )}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36964) Parallel Docker pipeline

2016-07-26 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36964  
 
 
  Parallel Docker pipeline
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2016/Jul/26 7:08 PM  
 
 
Environment: 
 Jenkins version 2.7.1   Plugins:  ace-editor 1.1  ant 1.3  antisamy-markup-formatter 1.5  authentication-tokens 1.3  branch-api 1.10  build-timeout 1.17.1  cloudbees-folder 5.12  credentials 2.1.4  cvs 2.12  docker-commons 1.4.0  docker-workflow 1.6  durable-task 1.11  external-monitor-job 1.5  git 2.5.2  git-client 1.19.7  git-server 1.7  github 1.19.3  github-api 1.76  github-branch-source 1.8.1  github-organization-folder 1.3  google-login 1.2.1  handlebars 1.1.1  icon-shim 2.0.3  javadoc 1.4  jquery-detached 1.2.1  junit 1.15  ldap 1.12  mailer 1.17  mapdb-api 1.0.9.0  matrix-auth 1.4  matrix-project 1.7.1  maven-plugin 2.13  momentjs 1.1.1  pam-auth 1.3  pipeline-build-step 2.2  pipeline-input-step 2.0  pipeline-rest-api 1.6  pipeline-stage-step 2.1  pipeline-stage-view 1.6  plain-credentials 1.2  role-strategy 2.3.2  scm-api 1.2  script-security 1.21  simple-theme-plugin 0.3  slack 2.0.1  ssh-credentials 1.12  ssh-slaves 1.11  structs 1.2  subversion 2.6  thinBackup 1.7.4  timestamper 1.8.4  token-macro 1.12.1  translation 1.15  windows-slaves 1.1  workflow-aggregator 2.2  workflow-api 2.1  workflow-basic-steps 2.0  workflow-cps 2.9  workflow-cps-global-lib 2.1  workflow-durable-task-step 2.3  workflow-job 2.3  workflow-multibranch 2.8  workflow-scm-step 2.2  workflow-step-api 2.2  workflow-support 2.2   Environment:  java.runtime.name OpenJDK Runtime Environment  java.runtime.version 1.7.0_101-b00  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Shauvik Roy Choudhary  
 

  
 
 
 
 

 
 docker withRun does not create separate containers when run within a parallel block. The 

[JIRA] (JENKINS-36933) Name or alias Shell Script Step (sh)

2016-07-25 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36933  
 
 
  Name or alias Shell Script Step (sh)   
 

  
 
 
 
 

 
Change By: 
 Shauvik Roy Choudhary  
 

  
 
 
 
 

 
 The `sh` step adds a "Shell Script" step in the Pipeline. However, there could be multiple such steps including steps from various plugins (e.g., Docker), which makes it hard to distinguish the steps. We should perhaps add an optional parameter to sh to specify a name or alias which would then appear in the pipeline steps.e.g., the following can be the step for npm which would show as "Shell script: npm" in the pipeline view.  {code:java}sh cmd:"npm install", name: "npm"{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36933) Name or alias sh Steps

2016-07-25 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36933  
 
 
  Name or alias sh Steps   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 build-pipeline-plugin  
 
 
Created: 
 2016/Jul/25 8:46 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Shauvik Roy Choudhary  
 

  
 
 
 
 

 
 The `sh` step adds a "Shell Script" step in the Pipeline. However, there could be multiple such steps including steps from various plugins (e.g., Docker), which makes it hard to distinguish the steps. We should perhaps add an optional parameter to sh to specify a name or alias which would then appear in the pipeline steps. e.g., the following can be the step for npm which would show as "Shell script: npm" in the pipeline view. `sh cmd:"npm install", name: "npm"`   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
  

[JIRA] (JENKINS-36933) Name or alias Shell Script Step (sh)

2016-07-25 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36933  
 
 
  Name or alias Shell Script Step (sh)   
 

  
 
 
 
 

 
Change By: 
 Shauvik Roy Choudhary  
 
 
Summary: 
 Name or alias  Shell Script Step (  sh  Steps )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36933) Name or alias Shell Script Step (sh)

2016-07-25 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36933  
 
 
  Name or alias Shell Script Step (sh)   
 

  
 
 
 
 

 
Change By: 
 Shauvik Roy Choudhary  
 

  
 
 
 
 

 
 The `sh` step adds a "Shell Script" step in the Pipeline. However, there could be multiple such steps including steps from various plugins (e.g., Docker), which makes it hard to distinguish the steps. We should perhaps add an optional parameter to sh to specify a name or alias which would then appear in the pipeline steps.e.g., the following can be the step for npm which would show as "Shell script: npm" in the pipeline view. ` {code:java} sh cmd:"npm install", name: "npm" `   {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36724) Branch indexing hangs

2016-07-15 Thread shau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shauvik Roy Choudhary created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36724  
 
 
  Branch indexing hangs
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Attachments: 
 branch_indexing_hangs.png  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2016/Jul/15 6:07 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Shauvik Roy Choudhary  
 

  
 
 
 
 

 
 We've been noticing problems with our jenkins branch indexing, which seems to hang from several minutes to hours. We see a lot of Branch indexing jobs on the queue and in the Branch indexing log itself, it shows (what we believe) a complete log with a loading spinner gif at the end. Not sure what the error is. Would be happy to dig in and provide more info if needed. Jenkins version: 2.7.1 Installed Plugins: Ant Plugin - 1.3 Authentication Tokens API Plugin - 1.3 Branch API Plugin - 1.10 build timeout plugin - 1.17 CloudBees Docker Pipeline - 1.6 Credentials Plugin - 2.1.4 CVS Plug-in - 2.12 Docker Commons Plugin - 1.4.0 Durable Task Plugin - 1.11 External Monitor Job Type Plugin - 1.5 Folders Plugin - 5.12 Git client plugin - 1.19.6 Git plugin - 2.5.2 GIT server Plugin - 1.7 GitHub API Plugin - 1.76 GitHub Branch Source Plugin - 1.8.1 GitHub Organization Folder Plugin - 1.3 GitHub plugin - 1.19.2 Google Login Plugin - 1.2.1 Icon Shim Plugin - 2.0.3 Javadoc Plugin - 1.4 _javascript_ GUI Lib: ACE Editor bundle plugin - 1.1 _javascript_ GUI Lib: Handlebars bundle plugin - 1.1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin - 1.2.1 _javascript_ GUI Lib: Moment.js bundle plugin - 1.1.1 JUnit Plugin - 1.15 LDAP Plugin - 1.12 Mailer Plugin - 1.17 MapDB API Plugin - 1.0.9.0 Matrix Authorization Strategy Plugin - 1.4 Matrix Project Plugin - 1.7.1 Maven Integration plugin - 2.13 OWASP Markup Formatter Plugin - 1.5 PAM Authentication plugin - 1.3 Pipeline -