[JIRA] [hp-application-automation-tools-plugin] (JENKINS-35165) Jenkins plugin cannot work with ALM over SSL

2016-05-26 Thread xu-liang.ku...@hpe.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kuang commented on  JENKINS-35165 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins plugin cannot work with ALM over SSL  
 
 
 
 
 
 
 
 
 
 
there is something wrong about the method “GetTestRunLink” in file “hp-application-automation-tools-plugin\HpToolsLauncher\Runners\AlmTestSetsRunner.cs”. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-application-automation-tools-plugin] (JENKINS-35165) Jenkins plugin cannot work with ALM over SSL

2016-05-26 Thread xu-liang.ku...@hpe.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kuang created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35165 
 
 
 
  Jenkins plugin cannot work with ALM over SSL  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 hp-application-automation-tools-plugin 
 
 
 

Created:
 

 2016/May/27 6:47 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jason Kuang 
 
 
 
 
 
 
 
 
 
 
In Jenkins plugin, if the ALM server URL is started with https, then when executing a job whose build step is “Execute HP Functional Test Scripts from HP ALM”, the URL showing in Jenkins console will be wrong, looks like that: td://QC12_52_POC.SEPG.https://qc.nam.nsroot.net:660/qcbin/TestLabModule-3649890581?EntityType=IRun&EntityID=207, which should be : tds://qc12_52_poc.sepg.qc.nam.nsroot.net:660/qcbin/TestLabModule-3649890581?EntityType=ITestSet&EntityID=207. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 

[JIRA] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names

2016-05-26 Thread anna.freiho...@niradynamics.se (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anna Freiholtz commented on  JENKINS-34157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Warnings plugin doesn't allow environment variables in file names  
 
 
 
 
 
 
 
 
 
 
Ah, I see. 
1982 is the previous build number. I create a directory for each build using _ where reference could be M01_13387_B, master or something similar. 
So it seems to me it is only in the setting for file pattern the environment variable is not working for me. But since you cannot reproduce the error, I'm beginning to suspect there is something else interfering... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [conditional-buildstep-plugin] (JENKINS-35157) Allow conditional build step to be used in promotion process

2016-05-26 Thread d...@fortysix.ch (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dominik Bartholdi commented on  JENKINS-35157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow conditional build step to be used in promotion process  
 
 
 
 
 
 
 
 
 
 
can you explain a bit more what you exactly want? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35148) CLI list-jobs is not listing multibranch sub projects

2016-05-26 Thread webmas...@mheinzerling.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Heinzerling edited a comment on  JENKINS-35148 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CLI list-jobs is not listing multibranch sub projects  
 
 
 
 
 
 
 
 
 
 [~danielbeck], the jobs of a Multibranch Pipeline.  If I ask for all jobs I get the folder of the Multibranch Pipeline, but not it's content. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35148) CLI list-jobs is not listing multibranch sub projects

2016-05-26 Thread webmas...@mheinzerling.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Heinzerling edited a comment on  JENKINS-35148 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CLI list-jobs is not listing multibranch sub projects  
 
 
 
 
 
 
 
 
 
 The [~danielbeck], the  jobs of a Multibranch Pipeline. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35148) CLI list-jobs is not listing multibranch sub projects

2016-05-26 Thread webmas...@mheinzerling.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Heinzerling commented on  JENKINS-35148 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CLI list-jobs is not listing multibranch sub projects  
 
 
 
 
 
 
 
 
 
 
The jobs of a Multibranch Pipeline. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-5419) Select type of script depending on platform

2016-05-26 Thread matthauck (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Hauck commented on  JENKINS-5419 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Select type of script depending on platform  
 
 
 
 
 
 
 
 
 
 
I think this would be extremely valuable for the same reason. Not familiar with XShell and will check it out. Will it work smoothly with Jenkinsfile syntax?  
Having a built-in "run this command in a shell" command would be very beneficial for anything that uses the same build definition across multiple platforms – something encouraged (rightly so!) by the use of a single Jenkinsfile. It has always frustrated me that jenkins has had two separate commands for windows/non-windows when jenkins could easily choose the right decision for you.  
:+1: 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34520) Can't use Jenkinsfile for build git tags

2016-05-26 Thread l...@ligi.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 marcus ligi commented on  JENKINS-34520 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't use Jenkinsfile for build git tags  
 
 
 
 
 
 
 
 
 
 
Artem V. Navrotskiy thanks! But TAG_NAME is always null - same as in env.TAG_NAME 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34520) Can't use Jenkinsfile for build git tags

2016-05-26 Thread boz...@yandex.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Artem V. Navrotskiy commented on  JENKINS-34520 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't use Jenkinsfile for build git tags  
 
 
 
 
 
 
 
 
 
 
 
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.Binding getVariables
 
marcus ligi, Looks like you need some actions on Script Approval: https://jenkins.local/scriptApproval/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [plumber-plugin] (JENKINS-35164) What steps are allowed in pipeline action

2016-05-26 Thread michael.ne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35164 
 
 
 
  What steps are allowed in pipeline action  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 plumber-plugin 
 
 
 

Created:
 

 2016/May/27 3:55 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Neale 
 
 
 
 
 
 
 
 
 
 
When using  

 
pipeline {
..
}
 

 
I occasionally hit on odd bugs. Although, as I know it is limited what can be run there, I don't know what is a bug and what isn't. Having some quasi documentation on what can be done with pipeline steps here may help.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
   

[JIRA] [workflow-plugin] (JENKINS-34520) Can't use Jenkinsfile for build git tags

2016-05-26 Thread l...@ligi.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 marcus ligi edited a comment on  JENKINS-34520 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't use Jenkinsfile for build git tags  
 
 
 
 
 
 
 
 
 
 [~bozaro] sounds great - but when using it I get:{noformat}org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.Binding getVariables at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:160) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor$6.reject(SandboxInterceptor.java:243) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:363) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:23) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17) at WorkflowScript.run(WorkflowScript:1) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:62) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:54) at sun.reflect.GeneratedMethodAccessor390.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:277) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:77) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:186) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:184) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 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)Finished: FAILURE{noformat} Interesting:  echo env.BRANCH_NAME -> prints the branch nameecho env.TAG_NAME -> prints always null 
 
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [workflow-plugin] (JENKINS-34520) Can't use Jenkinsfile for build git tags

2016-05-26 Thread l...@ligi.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 marcus ligi commented on  JENKINS-34520 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't use Jenkinsfile for build git tags  
 
 
 
 
 
 
 
 
 
 
Artem V. Navrotskiy sounds great - but when using it I get: 

 
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.Binding getVariables
	at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:160)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor$6.reject(SandboxInterceptor.java:243)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:363)
	at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238)
	at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:23)
	at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17)
	at WorkflowScript.run(WorkflowScript:1)
	at ___cps.transform___(Native Method)
	at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:62)
	at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
	at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:54)
	at sun.reflect.GeneratedMethodAccessor390.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
	at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
	at com.cloudbees.groovy.cps.Next.step(Next.java:58)
	at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)
	at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:277)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:77)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:186)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:184)
	at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	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)
Finished: FAILURE
 

 
 
 
 
 
 
  

[JIRA] [core] (JENKINS-31487) Job status not updated in web UI during build

2016-05-26 Thread pe...@eisentraut.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Eisentraut commented on  JENKINS-31487 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job status not updated in web UI during build  
 
 
 
 
 
 
 
 
 
 
No custom CSS/JS here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35136) Javascript error after fresh install of jenkins 2.6 deb w/ default plugins

2016-05-26 Thread scottb...@mightygamesgroup.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Beca edited a comment on  JENKINS-35136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: _javascript_ error after fresh install of jenkins 2.6 deb w/ default plugins  
 
 
 
 
 
 
 
 
 
 As [~timbaer] mentioned,  I was having  this  the  exact problem  on  that [~timbaer] mentioned with  my Jenkins 2.6 install and it was being caused by the [Credentials Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin].The Credentials Plugin introduced a _javascript_ bug in version 2.0.5 of the plugin which they patched the day after in version 2.0.6. Now that I'm running 2.0.6 the problem has gone away so it is worth everyone updating that plugin and seeing if it fixes the problem for you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35136) Javascript error after fresh install of jenkins 2.6 deb w/ default plugins

2016-05-26 Thread scottb...@mightygamesgroup.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Beca commented on  JENKINS-35136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: _javascript_ error after fresh install of jenkins 2.6 deb w/ default plugins  
 
 
 
 
 
 
 
 
 
 
As Stefan Bieler mentioned, I was having this exact problem on my Jenkins 2.6 install and it was being caused by the Credentials Plugin. 
The Credentials Plugin introduced a _javascript_ bug in version 2.0.5 of the plugin which they patched the day after in version 2.0.6. Now that I'm running 2.0.6 the problem has gone away so it is worth everyone updating that plugin and seeing if it fixes the problem for you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [matrix-auth-plugin] (JENKINS-34616) Snippet generator fails on AuthorizationMatrixProperty

2016-05-26 Thread mev...@parchment.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Evans commented on  JENKINS-34616 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Snippet generator fails on AuthorizationMatrixProperty  
 
 
 
 
 
 
 
 
 
 
I originally required this to allow authorization for input. I found out I could just use 'submitter' for this, so I haven't looked into workarounds. Although I did try a simple snippet which ran successfully 

 

properties [[$class: 'AuthorizationMatrixProperty', user: ['user']]]
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [matrix-auth-plugin] (JENKINS-34616) Snippet generator fails on AuthorizationMatrixProperty

2016-05-26 Thread anth...@pioli.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Pioli commented on  JENKINS-34616 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Snippet generator fails on AuthorizationMatrixProperty  
 
 
 
 
 
 
 
 
 
 
not following - will AuthorizationMatrixProperty: 
 

work but not generate snippets
 

not work at all
 
 
If it will work do we have some samples to look at? google is not helping me find any 
If it will not work at all, any suggested workarounds? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [build-failure-analyzer-plugin] (JENKINS-35163) Ability to sync failure fields to statistics for build failure analyzer plugin

2016-05-26 Thread bi...@concur.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bill Westfall created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35163 
 
 
 
  Ability to sync failure fields to statistics for build failure analyzer plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Tomas Westling 
 
 
 

Components:
 

 build-failure-analyzer-plugin 
 
 
 

Created:
 

 2016/May/26 11:14 PM 
 
 
 

Labels:
 

 plugin 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Bill Westfall 
 
 
 
 
 
 
 
 
 
 
Would like to have the ability to sync the build failure analyzer failure definition fields (name, categories, description, etc) to the statistics field. Right now the statistics gets populated with the raw pattern field, but none of these more useful fields. This would help with aggregating the data downstream (ex. syncing the statistics from MongoDB to Elasticsearch and then being able to do a query in Elasticsearch on these fields) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
  

[JIRA] [github-oauth-plugin] (JENKINS-35152) Login stuck in strange state

2016-05-26 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Gleske commented on  JENKINS-35152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Login stuck in strange state  
 
 
 
 
 
 
 
 
 
 
Try: 
 

logging into your GitHub settings and removing Jenkins authorization entirely.
 

Log Jenkins again.
 

Jenkins should prompt you to authorize again.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update

2016-05-26 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Gleske commented on  JENKINS-34775 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Broken jobs after upgrade to 1.651.2 security update  
 
 
 
 
 
 
 
 
 
 
Andrei Kovrov Are you sure you're on 0.24? Your stack trace seems to indicate you may be on an older version. For example, github-oauth-0.22.3 has the casting error at line 644 like in your stack trace. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [s3-plugin] (JENKINS-16025) Allow full path when uploading a file

2016-05-26 Thread rich...@bittorrent.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Brooks commented on  JENKINS-16025 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow full path when uploading a file  
 
 
 
 
 
 
 
 
 
 
For the folks who replied after me or anyone else that comes across this issue, I've been very happy with just using the AWS CLI tool for uploading my artifacts as a post-build step. I have greater faith in Amazon maintaining their own command line tool than some third-party Jenkins plugin. However, be aware that it does introduce a dependency of the command line tool being installed on your slaves as well as the inject-passwords-as-environment-variables plugin (or however else you'd like to provision the command line tool with credentials). 
Here's a gist of what I'm doing to upload the entire contents of a `./artifacts` directory in my job's workspace while preserving the hierarchy of any files within that directory: https://gist.github.com/richard-bt/f35723140043fada2a3416d4f5b76b81 
(of course, modify the scripts to artifact files according to your needs - but I prefer to put the logic for how things should look in scripts that arrange the contents of my `./artifacts` directory prior to my post-build artifact step) 
After using Jenkins for a while I've adopted a preference for minimizing the number of dependencies I have on Jenkins plugins for doing things I could otherwise accomplish with a shell script - especially in having to support jobs running on various operating systems.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update

2016-05-26 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Gleske commented on  JENKINS-34775 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Broken jobs after upgrade to 1.651.2 security update  
 
 
 
 
 
 
 
 
 
 
I'm not personally able to create this exception. I am still not clear on how it's produced so I can't reproduce it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-29979) Workflow plugin unable to save perforce paramters

2016-05-26 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Allan BURDAJEWICZ commented on  JENKINS-29979 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workflow plugin unable to save perforce paramters  
 
 
 
 
 
 
 
 
 
 
Russell Gallop It is indeed an expected effect of this change. It needed to be made applicable for Job (see GenericSCMStep) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)

2016-05-26 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33984 
 
 
 
  Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-client-plugin] (JENKINS-35162) git plugin does not respect refspec

2016-05-26 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35162 
 
 
 
  git plugin does not respect refspec  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [analysis-collector-plugin] (JENKINS-33066) Add support for cppcheck plugin

2016-05-26 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner commented on  JENKINS-33066 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for cppcheck plugin  
 
 
 
 
 
 
 
 
 
 
It does not look like the plug-in depends on analysis core. So I do not see a chance that this will happen.  
(There will be a chance that this information can be shown in the not yet released quality-dashboard plug-in. I'll add a comment when the first public release will be available.) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-client-plugin] (JENKINS-35162) git plugin does not respect refspec

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35162 
 
 
 
  git plugin does not respect refspec  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Attachments:
 

 git error.png 
 
 
 

Components:
 

 git-client-plugin, git-plugin 
 
 
 

Created:
 

 2016/May/26 9:29 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Michael Fowler 
 
 
 
 
 
 
 
 
 
 
I set the refscpec such that Jenkins would not include the repo name in the branch name. Jenkins still appended the repo name to the branch name. I need the branch names in Jenkins to match that of the origin so that gitVersion functions correctly. See the attached image for details 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 

[JIRA] [analysis-collector-plugin] (JENKINS-33066) Add support for cppcheck plugin

2016-05-26 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner assigned an issue to Gregory Boissinot 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33066 
 
 
 
  Add support for cppcheck plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ulli Hafner 
 
 
 

Assignee:
 
 Ulli Hafner Gregory Boissinot 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [analysis-collector-plugin] (JENKINS-33066) Add support for cppcheck plugin

2016-05-26 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33066 
 
 
 
  Add support for cppcheck plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ulli Hafner 
 
 
 

Component/s:
 
 analysis-collector-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cppcheck-plugin] (JENKINS-33066) Add support for cppcheck plugin

2016-05-26 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33066 
 
 
 
  Add support for cppcheck plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ulli Hafner 
 
 
 

Component/s:
 
 cppcheck-plugin 
 
 
 

Component/s:
 
 analysis-collector-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-34141) false Static Analysis Warnings with symlinks in ClearCase

2016-05-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34141 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: false Static Analysis Warnings with symlinks in ClearCase  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/GccParser.java src/test/java/hudson/plugins/warnings/parser/GccParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue34141.txt http://jenkins-ci.org/commit/warnings-plugin/be45becbf4d8372be32098757cd1f892de31162e Log: [FIXED JENKINS-34141] Filenames should not contain spaces. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-34141) false Static Analysis Warnings with symlinks in ClearCase

2016-05-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34141 
 
 
 
  false Static Analysis Warnings with symlinks in ClearCase  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xvfb-plugin] (JENKINS-34066) Xvfb plugin is passing in -fbdir twice

2016-05-26 Thread zregv...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart resolved as Won't Do 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Decided that leaving `fbdir` up to user is not a good idea. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34066 
 
 
 
  Xvfb plugin is passing in -fbdir twice  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Won't Do 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xvfb-plugin] (JENKINS-34066) Xvfb plugin is passing in -fbdir twice

2016-05-26 Thread zregv...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart closed an issue as Won't Do 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34066 
 
 
 
  Xvfb plugin is passing in -fbdir twice  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xvfb-plugin] (JENKINS-34809) How to set default xvfb installation?

2016-05-26 Thread zregv...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart commented on  JENKINS-34809 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: How to set default xvfb installation?  
 
 
 
 
 
 
 
 
 
 
Hi Chris, I've answered on stackoverflow, pasted here for others to find as well: 
Use this script in `init.groovy.d` directory: 

 

import jenkins.model.Jenkins
import org.jenkinsci.plugins.xvfb.*

def installation = new XvfbInstallation('default', '/usr/local/bin', null)

Jenkins.getInstance()
   .getDescriptorByType(Xvfb.XvfbBuildWrapperDescriptor.class)
   .setInstallations(installation)
 

 
The `default` is the name of the Xvfb installation, and `/usr/local/bin` is the directory where Xvfb binary resides, change accordingly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xvfb-plugin] (JENKINS-32039) "screen" default does not work

2016-05-26 Thread zregv...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32039 
 
 
 
  "screen" default does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xvfb-plugin] (JENKINS-33206) Xvfb plugin doesn't remember "Log Xvfb output" set via the configuration page

2016-05-26 Thread zregv...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33206 
 
 
 
  Xvfb plugin doesn't remember "Log Xvfb output" set via the configuration page  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xvfb-plugin] (JENKINS-35102) Xvfb is not stopped

2016-05-26 Thread zregv...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart commented on  JENKINS-35102 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Xvfb is not stopped  
 
 
 
 
 
 
 
 
 
 
Hi Chris thanks for reporting the issue, can you provide more detail on how to reproduce the issue: 
 

are you running agents on same physical machine in separate containers?
 

is the build tied to one of the agents?
 

do you have multiple jobs run in parallel?
 

what kind of build job are you using (freestyle, maven, matrix, pipeline,...)?
 

any details about the job I should be aware of?
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xvfb-plugin] (JENKINS-34809) How to set default xvfb installation?

2016-05-26 Thread zregv...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34809 
 
 
 
  How to set default xvfb installation?  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler assigned an issue to Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33984 
 
 
 
  Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Fowler 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [build-pipeline-plugin] (JENKINS-30404) Run button not clickable with parameterized builds

2016-05-26 Thread alv...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
There was an issue in earlier version of the plugin where it would conflict with jQuery. 
Closing out. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30404 
 
 
 
  Run button not clickable with parameterized builds  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Alvizu 
 
 
 

Status:
 
 Open Closed 
 
 
 

Assignee:
 
 Dan Alvizu 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

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

[JIRA] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there are no changes

2016-05-26 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-19962 
 
 
 
  Add the ability to declare a job successful even if there are no changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raphael CHAUMIER 
 
 
 

Labels:
 
 deployment weblogic  weblogic-deployer-plugin-3.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there are no changes

2016-05-26 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER resolved as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-19962 
 
 
 
  Add the ability to declare a job successful even if there are no changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raphael CHAUMIER 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there are no changes

2016-05-26 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER started work on  JENKINS-19962 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Raphael CHAUMIER 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [project-inheritance-plugin] (JENKINS-22885) Creation of Inheritance Project throws Exception

2016-05-26 Thread electric.blue.jag...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Tal commented on  JENKINS-22885 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Creation of Inheritance Project throws Exception  
 
 
 
 
 
 
 
 
 
 
Bump, this is still and issue with latest version of this plugin 1.5.3 and Jenkins 2.5. Can we get a fix ?? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [weblogic-deployer-plugin] (JENKINS-35161) Use of variable for the deployment name

2016-05-26 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER resolved as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35161 
 
 
 
  Use of variable for the deployment name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raphael CHAUMIER 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [weblogic-deployer-plugin] (JENKINS-35161) Use of variable for the deployment name

2016-05-26 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35161 
 
 
 
  Use of variable for the deployment name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raphael CHAUMIER 
 
 
 

Labels:
 
 weblogic-deployer-plugin-3.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [weblogic-deployer-plugin] (JENKINS-35161) Use of variable for the deployment name

2016-05-26 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35161 
 
 
 
  Use of variable for the deployment name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raphael CHAUMIER 
 
 
 

Summary:
 
 Use of variable for the  deploymentname  deployment name 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [weblogic-deployer-plugin] (JENKINS-35161) Use of variable for the deployment name

2016-05-26 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER started work on  JENKINS-35161 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Raphael CHAUMIER 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [weblogic-deployer-plugin] (JENKINS-35161) Use of variable for the deploymentname

2016-05-26 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35161 
 
 
 
  Use of variable for the deploymentname  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Raphael CHAUMIER 
 
 
 

Components:
 

 weblogic-deployer-plugin 
 
 
 

Created:
 

 2016/May/26 8:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Raphael CHAUMIER 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribe

[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters

2016-05-26 Thread victor.leit...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor L commented on  JENKINS-29031 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Current Build Parameters doesn't pass custom job parameters  
 
 
 
 
 
 
 
 
 
 
Me too. Had to downgrade from 1.651.2 back to 1.642.4. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31831) Allow Workflow Snippet Generator to be used outside of a configuration page

2016-05-26 Thread mko...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Kobit commented on  JENKINS-31831 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow Workflow Snippet Generator to be used outside of a configuration page  
 
 
 
 
 
 
 
 
 
 
Greg Smith It looks like you go to `/pipeline-syntax` - that is the only place I found it. `http://jenkins/job/job-name/pipeline-syntax` 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there are no changes

2016-05-26 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER commented on  JENKINS-19962 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the ability to declare a job successful even if there are no changes  
 
 
 
 
 
 
 
 
 
 
Hi, 
I've just released the 3.4 version of the plugin. Tell me if it's ok then I will close the issue. 
Regards 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update

2016-05-26 Thread git.feedback.rawm...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrei Kovrov commented on  JENKINS-34775 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Broken jobs after upgrade to 1.651.2 security update  
 
 
 
 
 
 
 
 
 
 
Sam Gleske issue still exists in v0.24 

 

Sending email to: s...@mail.ru
FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken
java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken
	at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:644)
	at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1049)
	at hudson.model.User.get(User.java:395)
	at hudson.model.User.get(User.java:364)
	at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374)
	at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435)
	at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350)
	at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:672)
	at hudson.model.Run.execute(Run.java:1763)
	at hudson.matrix.MatrixBuild.run(MatrixBuild.java:301)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:410)
Finished: FAILURE
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-application-automation-tools-plugin] (JENKINS-35106) HP ALM plugin fails to find junit results file

2016-05-26 Thread mpen...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mpendas updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35106 
 
 
 
  HP ALM plugin fails to find junit results file  
 
 
 
 
 
 
 
 
 

Change By:
 
 mpendas 
 
 
 
 
 
 
 
 
 
 I am only trying to upload test results to ALM. This is running on RedHat Linux. No HP  LAM  ALM  software is installed on the jenkins machine.The Junit plugin finds the results file the HP ALM plugin does not find the file:Recording test resultsBuild step 'Publish JUnit test result report' changed build result to UNSTABLEINFO: 'Upload test result to ALM' Post Build Step is being invoked.INFO: No Test Report found.INFO: 'Upload test result to ALM' Completed.Finished: UNSTABLEThe file path for both plugins is: **/fit_tests/ApiResults.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35160) Unable to delete project

2016-05-26 Thread jennyh...@yahoo-inc.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jenny Hung created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35160 
 
 
 
  Unable to delete project  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/26 7:10 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jenny Hung 
 
 
 
 
 
 
 
 
 
 
I tried to delete a project, but getting following error: 
http://cheesecake.factory.corp.yahoo.com:/jenkins/user/jennyhung/my-views/view/All/job/GeminiE2E_SearchSharedLibrarySiteLinkTestSingle-verifyAdServingNoUse/doDelete 
A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace 
java.nio.file.FileSystemException: /home/y/var/jenkins/jobs/GeminiE2E_SearchSharedLibrarySiteLinkTestSingle-verifyAdServingNoUse/builds/2016-05-18_03-38-23/.nfs0fbbd2880082: Device or resource busy at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:244) at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103) at java.nio.fi

[JIRA] [plugin-usage-plugin] (JENKINS-35159) Plugin usage plugin does not count usages within a promotion process

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35159 
 
 
 
  Plugin usage plugin does not count usages within a promotion process  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Fowler 
 
 
 

Issue Type:
 
 Improvement Bug 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34542) Hang in ExecutorStepExecution

2016-05-26 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34542 
 
 
 
  Hang in ExecutorStepExecution  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [plugin-usage-plugin] (JENKINS-35159) Plugin usage plugin does not count usages within a promotion process

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35159 
 
 
 
  Plugin usage plugin does not count usages within a promotion process  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Christian Meyer 
 
 
 

Components:
 

 plugin-usage-plugin 
 
 
 

Created:
 

 2016/May/26 6:43 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Fowler 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message becau

[JIRA] [cflint-plugin] (JENKINS-28342) CF plugin: cannot use $PORT to start Rails project

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28342 
 
 
 
  CF plugin: cannot use $PORT to start Rails project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Fowler 
 
 
 

Component/s:
 
 cflint-plugin 
 
 
 

Component/s:
 
 plugin-usage-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-23785) Deploy to war files when trying to set version in "Context Path"

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-23785 
 
 
 
  Deploy to war files when trying to set version in "Context Path"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Fowler 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 plugin-usage-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-23847) Jenkins 1.572 doesn't clear values in Plugin if we try to pass NULL value later by saving the Project Configuration

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-23847 
 
 
 
  Jenkins 1.572 doesn't clear values in Plugin if we try to pass NULL value later by saving the Project Configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Fowler 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 plugin-usage-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-34749) Jenkins doesn't authenticate to proxy

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34749 
 
 
 
  Jenkins doesn't authenticate to proxy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Fowler 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 plugin-usage-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [swarm-plugin] (JENKINS-18802) Can't Run Swarm As a Windows Service

2016-05-26 Thread robd...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Duff commented on  JENKINS-18802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't Run Swarm As a Windows Service  
 
 
 
 
 
 
 
 
 
 
(Just for those stumbling upon this issue looking for an answer... https://github.com/kohsuke/winsw) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [s3-plugin] (JENKINS-34780) Files from the entry path are not copied to S3 bucket's root directory relatively

2016-05-26 Thread dim1...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dima Vartanian commented on  JENKINS-34780 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Files from the entry path are not copied to S3 bucket's root directory relatively  
 
 
 
 
 
 
 
 
 
 
Having this issue as well. Flatten works for me for now because I am uploading everything to a single directory but is definitely just a bandaid. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [build-failure-analyzer-plugin] (JENKINS-29024) Support displaying all matching captures

2016-05-26 Thread pe...@algarvio.me (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pedro Algarvio commented on  JENKINS-29024 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support displaying all matching captures  
 
 
 
 
 
 
 
 
 
 
I'd also like to get indications of all matches for a specific indication, not just the first. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cloudbees-folder-plugin] (JENKINS-35158) Searchbox must support Folders

2016-05-26 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier commented on  JENKINS-35158 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Searchbox must support Folders  
 
 
 
 
 
 
 
 
 
 
1.642.2 Daniel Beck 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-34965) Polling no longer triggering builds after Jenkins upgrade to 1.651.2

2016-05-26 Thread ku...@accretivetg.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Nuke commented on  JENKINS-34965 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Polling no longer triggering builds after Jenkins upgrade to 1.651.2  
 
 
 
 
 
 
 
 
 
 
Worked around this issue with a HTTP Request Post Receive hook from Stash to Jenkins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cloudbees-folder-plugin] (JENKINS-35158) Searchbox must support Folders

2016-05-26 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-35158 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Searchbox must support Folders  
 
 
 
 
 
 
 
 
 
 
What version of Jenkins is this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35148) CLI list-jobs is not listing multibranch sub projects

2016-05-26 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-35148 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CLI list-jobs is not listing multibranch sub projects  
 
 
 
 
 
 
 
 
 
 
What job type are you specifically referring to? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cloudbees-folder-plugin] (JENKINS-35158) Searchbox must support Folders

2016-05-26 Thread jcarsi...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julien Carsique updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35158 
 
 
 
  Searchbox must support Folders  
 
 
 
 
 
 
 
 
 

Change By:
 
 Julien Carsique 
 
 
 

Component/s:
 
 cloudbees-folder-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35158) Searchbox must support Folders

2016-05-26 Thread jcarsi...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julien Carsique created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35158 
 
 
 
  Searchbox must support Folders  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Pasted image at 2016_05_25 18_08.png 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/26 5:15 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Julien Carsique 
 
 
 
 
 
 
 
 
 
 
When using folders (plugin), the search returns two results for a unique job: one with the job name and one with the folder plus the job name. The second one works fine, not the first one. 
When the searched phrase exactly matches a job name, you are redirected to that job instead of getting a list of results. As a consequence, searching for a job contained in a folder by its exact name will lead to a 404 page. 
For instance, in the attached screenshot, searching for "addons_nuxeo-drive-server-7.10" which is contained in the "7.10" folder: 
 

hitting enter lead to 404
 

waiting for the suggested results returns an unusable "addons_nuxeo-drive-server-7.10" and a working "7.10 addons_nuxe

[JIRA] [conditional-buildstep-plugin] (JENKINS-35157) Allow conditional build step to be used in promotion process

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35157 
 
 
 
  Allow conditional build step to be used in promotion process  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Dominik Bartholdi 
 
 
 

Components:
 

 conditional-buildstep-plugin 
 
 
 

Created:
 

 2016/May/26 5:10 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Fowler 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message be

[JIRA] [core] (JENKINS-31487) Job status not updated in web UI during build

2016-05-26 Thread calla_feu...@condenast.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Calla Feucht commented on  JENKINS-31487 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job status not updated in web UI during build  
 
 
 
 
 
 
 
 
 
 
Hmm I don't know where/when it started, but I do know that it was not present in v1.596. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-31487) Job status not updated in web UI during build

2016-05-26 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31487 
 
 
 
  Job status not updated in web UI during build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 progress  regression  status 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-31487) Job status not updated in web UI during build

2016-05-26 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-31487 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job status not updated in web UI during build  
 
 
 
 
 
 
 
 
 
 
Anyone remember what the first version of Jenkins was to have this problem? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names

2016-05-26 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner edited a comment on  JENKINS-34157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Warnings plugin doesn't allow environment variables in file names  
 
 
 
 
 
 
 
 
 
 Yes, I know.  I already used in my test.  But your number looks quite strange: #1982_M01_13387_B. Is this value changed by a plug-in? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names

2016-05-26 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner edited a comment on  JENKINS-34157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Warnings plugin doesn't allow environment variables in file names  
 
 
 
 
 
 
 
 
 
 Yes, I know. But your number looks quite strange: #1982_M01_13387_B. Is this value changed by a plug-in . ?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names

2016-05-26 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner commented on  JENKINS-34157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Warnings plugin doesn't allow environment variables in file names  
 
 
 
 
 
 
 
 
 
 
Yes, I know. But your number looks quite strange: #1982_M01_13387_B. Is this value changed by a plug-in. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [valgrind-plugin] (JENKINS-35156) valgrind plugin crashes

2016-05-26 Thread nickbr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35156 
 
 
 
  valgrind plugin crashes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Johannes Ohlemacher 
 
 
 

Components:
 

 valgrind-plugin 
 
 
 

Created:
 

 2016/May/26 4:39 PM 
 
 
 

Environment:
 

 0.27 of the Valgrind Plugin  2.2 of Jenkins 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Nicholas Brown 
 
 
 
 
 
 
 
 
 
 
My logs contain: 
17:22:50 $ valgrind --version 17:22:50 [Valgrind] detected valgrind version (valgrind): 3.11.0 17:22:50 [Valgrind] includes files: binary_foo, binary_bar 17:22:50 [Valgrind] ERROR, java.lang.NullPointerException: null 17:22:50 Build step 'Run Valgrind' marked build as failure 
I'm using version 0.27 of the plugin, and Jenkins 2.2. 
Are there any steps to further debug what is causing this crash? 
 
 
 
 
 
 
 
 
 
 
 
 

 
   

[JIRA] [core] (JENKINS-31487) Job status not updated in web UI during build

2016-05-26 Thread calla_feu...@condenast.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Calla Feucht commented on  JENKINS-31487 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job status not updated in web UI during build  
 
 
 
 
 
 
 
 
 
 
Daniel Beck - Yep – no custom CSS/JS here, and we see this issue with v1.651.2. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [promoted-builds-plugin] (JENKINS-35155) Allow specifying multiple parameters in "Promote immediately once the build is complete based on build parameters" as in "Only when manually approved"

2016-05-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fowler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35155 
 
 
 
  Allow specifying multiple parameters in "Promote immediately once the build is complete based on build parameters" as in "Only when manually approved"  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 promoted-builds-plugin 
 
 
 

Created:
 

 2016/May/26 4:25 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Fowler 
 
 
 
 
 
 
 
 
 
 
Sometime multiple parameters need to be set before a build should be automatically promoted upon completion.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

[JIRA] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

2016-05-26 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
My current theory, based on nothing but guesswork, is that job creation submission is failing on Firefox? Maybe? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [credentials-plugin] (JENKINS-35150) Request blocked due to HTTP/HTTPS mismatch

2016-05-26 Thread stephenconno...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 stephenconnolly commented on  JENKINS-35150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Request blocked due to HTTP/HTTPS mismatch  
 
 
 
 
 
 
 
 
 
 
Have you set your Jenkins root URL on Manage Jenkins » Configure Jenkins? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [credentials-plugin] (JENKINS-35150) Request blocked due to HTTP/HTTPS mismatch

2016-05-26 Thread stephenconno...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 stephenconnolly resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35150 
 
 
 
  Request blocked due to HTTP/HTTPS mismatch  
 
 
 
 
 
 
 
 
 

Change By:
 
 stephenconnolly 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35136) Javascript error after fresh install of jenkins 2.6 deb w/ default plugins

2016-05-26 Thread stefan.bie...@asideas.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Bieler edited a comment on  JENKINS-35136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: _javascript_ error after fresh install of jenkins 2.6 deb w/ default plugins  
 
 
 
 
 
 
 
 
 
 Hi,I'm facing the exact same situation as stated above. However, with a slightly different setup. Running on jenkins v. 1.642.1 with various added plugins. The issue started showing  since  yesterday. Poorly, as of now, I cannot say if the system changed since then, as I have some collegues working on the system. I will try to add information as soon as they are available.Any help is highly appreciated!Regards,Stefan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-35136) Javascript error after fresh install of jenkins 2.6 deb w/ default plugins

2016-05-26 Thread stefan.bie...@asideas.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Bieler commented on  JENKINS-35136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: _javascript_ error after fresh install of jenkins 2.6 deb w/ default plugins  
 
 
 
 
 
 
 
 
 
 
Hi again, 
after digging through the internet, we found out that the credentials plugin might be worth a look. After disabling the plugin, everything works fine now. 
BR, 
Stefan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-29979) Workflow plugin unable to save perforce paramters

2016-05-26 Thread russell.gal...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop commented on  JENKINS-29979 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workflow plugin unable to save perforce paramters  
 
 
 
 
 
 
 
 
 
 
Built from bebc56d8b560728b07edeb3572ccd172c831c5ba and that works for me. 
It also seems that the snippet generator can now generate a checkout step for p4 (which is good). Is that an expected effect of this change? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-ext-plugin] (JENKINS-35154) Jira-ext Plugin does not set Servername for SNI Hosts

2016-05-26 Thread carsten.kirsch...@corussoft.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Carsten Kirschner created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35154 
 
 
 
  Jira-ext Plugin does not set Servername for SNI Hosts  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Dan Alvizu 
 
 
 

Components:
 

 jira-ext-plugin 
 
 
 

Created:
 

 2016/May/26 3:37 PM 
 
 
 

Environment:
 

 Jenkins 2.6, jira-ext 0.5, OpenJDK 1.8u91 64bit, Amazon Linux 64bit 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Carsten Kirschner 
 
 
 
 
 
 
 
 
 
 
The jira-ext Plugin does not set the servername parameter for ssl requests. Our Jira is behind SNIProxy and SNIProxy needs the servername to find the correct route. Without the following error occurs. The Jira Plugin works. 
Error finding FieldIds for issueKey: VITAL-1 
net.rcarz.jiraclient.JiraException: Exception getting fields for JIRA issue at org.jenkinsci.plugins.jiraext.svc.impl.JiraClientSvcImpl.getJiraFields(JiraClientSvcImpl.java:212) at org.jenkinsci.plugins.jiraext.view.UpdateField$DescriptorImpl.doQueryJiraFields(UpdateField.java:128) 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:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Funct

[JIRA] [core] (JENKINS-35136) Javascript error after fresh install of jenkins 2.6 deb w/ default plugins

2016-05-26 Thread stefan.bie...@asideas.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Bieler commented on  JENKINS-35136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: _javascript_ error after fresh install of jenkins 2.6 deb w/ default plugins  
 
 
 
 
 
 
 
 
 
 
Hi, 
I'm facing the exact same situation as stated above. However, with a slightly different setup. Running on jenkins v. 1.642.1 with various added plugins. The issue started showing since yesterday. Poorly, as of now, I cannot say if the system changed since then, as I have some collegues working on the system. I will try to add information as soon as they are available. 
Any help is highly appreciated! 
Regards, 
Stefan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-35090) ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin

2016-05-26 Thread kwhetst...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-35090 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin  
 
 
 
 
 
 
 
 
 
 
I'll take this as I've started working on getting the plugin working on PCT and ATH. This should get the credentials-plugin working on the 2.x line. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-35090) ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin

2016-05-26 Thread kwhetst...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone assigned an issue to Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35090 
 
 
 
  ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Assignee:
 
 Armando Fernandez Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-35090) ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin

2016-05-26 Thread kwhetst...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-35090 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33357) Gradle class not found Servlet Exception prevents Configure Pages from loading

2016-05-26 Thread ma...@prochera.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Marek Prochera commented on  JENKINS-33357 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Gradle class not found Servlet Exception prevents Configure Pages from loading  
 
 
 
 
 
 
 
 
 
 
Workaround  
1. Install gradle 

 

Unable to find source-code formatter for language: jbash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


sudo add-apt-repository ppa:cwchien/gradle
sudo apt-get update
sudo apt-get install gradle
 

 
2. install Gradle plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [sse-gateway-plugin] (JENKINS-35153) Events.JobChannel#job_crud_deleted publishing blocked by AccessControl

2016-05-26 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35153 
 
 
 
  Events.JobChannel#job_crud_deleted publishing blocked by AccessControl  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Tom FENNELLY 
 
 
 

Components:
 

 sse-gateway-plugin 
 
 
 

Created:
 

 2016/May/26 2:23 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Tom FENNELLY 
 
 
 
 
 
 
 
 
 
 
This is actually an issue in the pubsub-light-module. The GuavaPubsubBus does an AccessControlled check before allowing publishing of any message. The first part of that is to check for the existence of the model object associated with the event. But of course In the case of this delete event (or any other delete event), the model object no longer exists, causing the security check to fail and for the event to not be published. 
Need to come up with some event specific way of indicating that it's OK to forward the event if the model object does not exist. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 

[JIRA] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin

2016-05-26 Thread mr...@sjm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Rose commented on  JENKINS-25249 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Post-commit hook for P4 plugin  
 
 
 
 
 
 
 
 
 
 
Paul Allen: It would be nice if there was a way to get the changelist that was sync'd by the p4sync operation. It could populate the P4_CHANGELIST variable like it used to, but users would have to be aware that the variable only represents the most recent sync operation. Another possibility would be for p4sync to just return the changelist it used for the sync. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-32326) broken HTTP_PROXY handling on jenkins-slave (JNLP)

2016-05-26 Thread pub...@etiennebec.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Etienne Bec assigned an issue to Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32326 
 
 
 
  broken HTTP_PROXY handling on jenkins-slave (JNLP)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Etienne Bec 
 
 
 

Assignee:
 
 Etienne Bec Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [pipeline-stage-view-plugin] (JENKINS-33498) Improve full screen view of pipeline stage view

2016-05-26 Thread john.d.am...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Ament commented on  JENKINS-33498 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Improve full screen view of pipeline stage view  
 
 
 
 
 
 
 
 
 
 
Sam Van Oort I don't know if its 100%, but its definitely something bigger. Otherwise there's no benefit to switching to full screen mode (other than not having the sidebar). Maybe just increasing each cell to double the size (height and width) would help? 
Would it make sense for the header to go away as well? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-oauth-plugin] (JENKINS-35152) Login stuck in strange state

2016-05-26 Thread shie...@kkvesper.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johnny Shields created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35152 
 
 
 
  Login stuck in strange state  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Sam Gleske 
 
 
 

Components:
 

 github-oauth-plugin 
 
 
 

Created:
 

 2016/May/26 1:47 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Johnny Shields 
 
 
 
 
 
 
 
 
 
 
I accidentally messed up nginx config and tried to login via Github oauth, and for some reason I'm now permanently unable to access from Chrome browser at this IP address. Clearing cache / chrome incognito also does not work. 
Seems github is rejecting my logins, so issue may not be within this plugin. 
Firefox, etc. other browsers work fine. 
``` java.lang.RuntimeException: org.kohsuke.github.HttpException: Server returned HTTP response code: 401, message: 'Unauthorized' for URL: https://api.github.com/user at org.jenkinsci.plugins.GithubSecurityRealm$1.authenticate(GithubSecurityRealm.java:564) at jenkins.security.BasicHeaderRealPasswordAuthenticator.authenticate(BasicHeaderRealPasswordAuthenticator.java:56) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:79) 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:171) at org.eclipse.jetty.serv

  1   2   >