date:20161101

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Michael Neale  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39425  
 
 
  REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 indian  
 
 
Assignee: 
 Vivek Pandey Michael Neale  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay started work on  JENKINS-39425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated  JENKINS-39425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39425  
 
 
  REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave   
 

  
 
 
 
 

 
 I'll check the certificate settings ASAP. Most likely the signing certificate is expired. If yes, I will create another issue for it  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39341) Update favourite card design

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39341  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update favourite card design   
 

  
 
 
 
 

 
 Could you also consider https://issues.jenkins-ci.org/browse/JENKINS-39426 which is a new (ish) requirement.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39427) Launching a parametrised job should use default parameters

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39427  
 
 
  Launching a parametrised job should use default parameters   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Assignee: 
 Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39427) Launching a parametrised job should use default parameters

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39427  
 
 
  Launching a parametrised job should use default parameters   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/02 5:34 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 When launching a parametrised pipeline (or freestyle job) you can have default parameters.  If you try to launch from blue ocean it fails hard as all parameters are null. Parameters should be set to their default values.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39341) Update favourite card design

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39341  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update favourite card design   
 

  
 
 
 
 

 
 Michael Neale I asked Brody Maclean to add his tweaks to the favourite card design here. Once we have it we can scope it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39339) Try BlueOcean button should keep currently open pipeline context

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39339  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Try BlueOcean button should keep currently open pipeline context   
 

  
 
 
 
 

 
 yeah not sure why that other one was closed (doesn't have a reason). Not deliberately related. Great minds think alike.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39426) Favorite card should show ETA and current stage (if pipeline) for executing run

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39426  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Favorite card should show ETA and current stage (if pipeline) for executing run   
 

  
 
 
 
 

 
 James Dumay is this a dupe? I can't find another one like it.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39341) Update favourite card design

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39341  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update favourite card design   
 

  
 
 
 
 

 
 What is the scope of this ticket?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39426) Favorite card should show ETA and current stage (if pipeline) for executing run

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39426  
 
 
  Favorite card should show ETA and current stage (if pipeline) for executing run   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screen Shot 2016-11-02 at 3.10.37 pm.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/02 4:11 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 When a card is in executing state, it would be nice to show the ETA (perhaps in a count down) and the currently executing stage (if it is a pipeline). There is plenty of spare realestate to show this (in the case of multibranch the branch name is shown, but otherwise some spare space).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
 Fix pending: https://github.com/jenkinsci/blueocean-plugin/pull/581  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
 Have a potential fix incoming...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

2016-11-01 Thread bwald...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Walding commented on  JENKINS-39425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
 An empty stage triggers it 

 
  stage("for the lulz") {
  
  }
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
 Vivek Pandey right there is a case where firstExecuted could be null, in fact there is a check for it:  

 
TimingInfo times = StatusAndTiming.computeChunkTiming(run, chunk.getPauseTimeMillis(), firstExecuted, chunk.getLastNode(), chunk.getNodeAfter());

if(times == null){
times = new TimingInfo();
}

GenericStatus status = (firstExecuted == null) ? GenericStatus.NOT_EXECUTED :StatusAndTiming
.computeChunkStatus(run, chunk.getNodeBefore(), firstExecuted, chunk.getLastNode(), chunk.getNodeAfter());

 

 However this check happens after it is attempted to be used to get the timing. It shouldn't be called if null.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
 The root cause seems to be that "firstExecuted" is null:  https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/rest/impl/pipeline/PipelineNodeGraphVisitor.java#L201 in PipelineNodeGraphVisitor.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
 OK did some digging.  The failure happens here:  https://github.com/jenkinsci/workflow-api-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/actions/TimingAction.java#L45 due to flowNode being null.  The ternary _expression_ https://github.com/jenkinsci/pipeline-graph-analysis-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/pipelinegraphanalysis/StatusAndTiming.java#L240 does not guard against firstNode being null (I am not sure if the true/false is correct either, but can't comment on that). Clearly firstNode is null, and it is trying to find the timing for it.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-20913) [jar caching] - winp.x64.dll access conflicts

2016-11-01 Thread bhi...@alumni.ucsd.edu (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Hines commented on  JENKINS-20913  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [jar caching] - winp.x64.dll access conflicts   
 

  
 
 
 
 

 
 We are also seeing this error pretty often.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

2016-11-01 Thread bwald...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Walding commented on  JENKINS-39425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
 Jenkins 2.28 + BlueOcean b11 - stack trace looks the same - but for the avoidance of doubt 

 
Caused by: java.lang.NullPointerException
	at org.jenkinsci.plugins.workflow.actions.TimingAction.getStartTime(TimingAction.java:45)
	at org.jenkinsci.plugins.workflow.pipelinegraphanalysis.StatusAndTiming.computeChunkTiming(StatusAndTiming.java:240)
	at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.handleChunkDone(PipelineNodeGraphVisitor.java:201)
	at org.jenkinsci.plugins.workflow.graphanalysis.StandardChunkVisitor.chunkStart(StandardChunkVisitor.java:40)
	at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.chunkStart(PipelineNodeGraphVisitor.java:74)
	at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:566)
	at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:551)
	at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.(PipelineNodeGraphVisitor.java:68)
	at io.jenkins.blueocean.rest.impl.pipeline.NodeGraphBuilder$NodeGraphBuilderFactory.getInstance(NodeGraphBuilder.java:37)
	at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeContainerImpl.(PipelineNodeContainerImpl.java:32)
	at io.jenkins.blueocean.rest.impl.pipeline.PipelineRunImpl.getNodes(PipelineRunImpl.java:81)
	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:335)
	at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	... 101 more
 

 As a test I created a multibranch pipeline test job that launches a secondary pipeline job (same structure as my failing job) - it did not have the same issue. So there is something subtle about it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39337) error step has no log output

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39337  
 
 
  error step has no log output   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39425  
 
 
  REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 There is a multibranch job taht [~bwalding] runs that fails to show the pipeline stage graph. This is due to /runs/N/nodes/ returning a 500 error, which is due to a null pointer exception. (this seems specific to multibranch) and And  has been failing since the update to bismuth. The stage view (classic) does not have this problem. Still working on how exactly to reproduce this but thought the stack trace may be useful on its own. {noformat}Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.workflow.actions.TimingAction.getStartTime(TimingAction.java:45) at org.jenkinsci.plugins.workflow.pipelinegraphanalysis.StatusAndTiming.computeChunkTiming(StatusAndTiming.java:240) at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.handleChunkDone(PipelineNodeGraphVisitor.java:201) at org.jenkinsci.plugins.workflow.graphanalysis.StandardChunkVisitor.chunkStart(StandardChunkVisitor.java:40) at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.chunkStart(PipelineNodeGraphVisitor.java:74) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:566) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:551) at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.(PipelineNodeGraphVisitor.java:68) at io.jenkins.blueocean.rest.impl.pipeline.NodeGraphBuilder$NodeGraphBuilderFactory.getInstance(NodeGraphBuilder.java:37) at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeContainerImpl.(PipelineNodeContainerImpl.java:32) at io.jenkins.blueocean.rest.impl.pipeline.PipelineRunImpl.getNodes(PipelineRunImpl.java:81) 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.MetaClass$3.doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746){noformat}

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39425  
 
 
  REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 There is a multibranch job taht [~bwalding] runs that fails to show the pipeline stage graph. This is due to /runs/N/nodes/ returning a 500 error, which is due to a null pointer exception.(this seems specific to multibranch) and has been failing since the update to bismuth.  The stage view (classic) does not have this problem.Still working on how exactly to reproduce this but thought the stack trace may be useful on its own. {noformat}Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.workflow.actions.TimingAction.getStartTime(TimingAction.java:45) at org.jenkinsci.plugins.workflow.pipelinegraphanalysis.StatusAndTiming.computeChunkTiming(StatusAndTiming.java:240) at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.handleChunkDone(PipelineNodeGraphVisitor.java:201) at org.jenkinsci.plugins.workflow.graphanalysis.StandardChunkVisitor.chunkStart(StandardChunkVisitor.java:40) at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.chunkStart(PipelineNodeGraphVisitor.java:74) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:566) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:551) at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.(PipelineNodeGraphVisitor.java:68) at io.jenkins.blueocean.rest.impl.pipeline.NodeGraphBuilder$NodeGraphBuilderFactory.getInstance(NodeGraphBuilder.java:37) at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeContainerImpl.(PipelineNodeContainerImpl.java:32) at io.jenkins.blueocean.rest.impl.pipeline.PipelineRunImpl.getNodes(PipelineRunImpl.java:81) 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.MetaClass$3.doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746){noformat}

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39425  
 
 
  REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Assignee: 
 Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39424) NTLM Authentication support for http-request-plugin

2016-11-01 Thread aburdukovs...@blizzard.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anton B created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39424  
 
 
  NTLM Authentication support for http-request-plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Janario Oliveira  
 
 
Components: 
 http-request-plugin  
 
 
Created: 
 2016/Nov/02 1:08 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Anton B  
 

  
 
 
 
 

 
 Please add NTLM authentication support to the httpRequest pipeline step.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-39425) REGRESSION: NPE when calculating getStartTime chunk time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39425  
 
 
  REGRESSION: NPE when calculating getStartTime chunk time   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/02 1:08 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 There is a multibranch job taht Ben Walding runs that fails to show the pipeline stage graph.  This is due to /runs/N/nodes/ returning a 500 error, which is due to a null pointer exception. (this seems specific to multibranch) and has been failing since the update to bismuth.  Still working on how exactly to reproduce this but thought the stack trace may be useful on its own.  

 
Caused by: java.lang.NullPointerException
	at org.jenkinsci.plugins.workflow.actions.TimingAction.getStartTime(TimingAction.java:45)
	at org.jenkinsci.plugins.workflow.pipelinegraphanalysis.StatusAndTiming.computeChunkTiming(StatusAndTiming.java:240)
	at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.handleChunkDone(PipelineNodeGraphVisitor.java:201)
	at org.jenkinsci.plugins.workflow.graphanalysis.StandardChunkVisitor.chunkStart(StandardChunkVisitor.java:40)
	at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.chunkStart(PipelineNodeGraphVisitor.java:74)
	at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:566)
	at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:551)
	at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.(PipelineNodeGraphVisitor.java:68)
	at io.jenkins.blueocean.rest.impl.pipeline.NodeGraphBuilder$NodeGraphBuilderFactory.getInstance(NodeGraphBuilder.java:37)
	at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeContainerImpl.(PipelineNodeContainerImpl.java:32)
	at

[JIRA] (JENKINS-39337) error step has no log output

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39337  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: error step has no log output   
 

  
 
 
 
 

 
 How is this designed at all? if it just throws an exception, why does this step exist? it doesn't provide anything extra over throw Exception("message here")?  It should at least log the message, or else be removed as a step with no purpose.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38765) Stage view renders incorrectly with stages appearing multiple times.

2016-11-01 Thread da...@vanlaatum.id.au (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum commented on  JENKINS-38765  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stage view renders incorrectly with stages appearing multiple times.   
 

  
 
 
 
 

 
 I am seeing the same thing. It only happends while the build is running as soon as it finishes it looks fine.It looks like its duplicating the stages on the server side as it appears there are duplicates in the json ajax.json   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38765) Stage view renders incorrectly with stages appearing multiple times.

2016-11-01 Thread da...@vanlaatum.id.au (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38765  
 
 
  Stage view renders incorrectly with stages appearing multiple times.   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Attachment: 
 ajax.json  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38765) Stage view renders incorrectly with stages appearing multiple times.

2016-11-01 Thread da...@vanlaatum.id.au (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38765  
 
 
  Stage view renders incorrectly with stages appearing multiple times.   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Attachment: 
 screenshot-1.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39422) Anchore plugin fails if input image is specified with a string containing a '/'

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39422  
 
 
  Anchore plugin fails if input image is specified with a string containing a '/'   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39422) Anchore plugin fails if input image is specified with a string containing a '/'

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39422  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore plugin fails if input image is specified with a string containing a '/'   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Nurmi Path: src/main/java/com/anchore/jenkins/plugins/anchore/AnchoreBuilder.java http://jenkins-ci.org/commit/anchore-container-scanner-plugin/4ce1f07c5f14063bac936e5b1ec0b0ad1dafd6e9 Log: [FIXED JENKINS-39422] removing the use of input image names in any file path naming Signed-off-by: Daniel Nurmi   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-16070) Deadlock using Windows native calls

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-16070  
 
 
  Deadlock using Windows native calls   
 

  
 
 
 
 

 
Change By: 
 Greg Smith  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-16070) Deadlock using Windows native calls

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith edited a comment on  JENKINS-16070  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock using Windows native calls   
 

  
 
 
 
 

 
 I am reopening this issue, as it is not resolved.  We have recreated it in latest LTS release, 2.19.2 as of this comment.   Our slaves are running latest Java 8 VMs. For details, and a similar matching stack trace, see linked issue JENKINS-39179  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-16070) Deadlock using Windows native calls

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith commented on  JENKINS-16070  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock using Windows native calls   
 

  
 
 
 
 

 
 I am reopening this issue, as it is not resolved. We have recreated it in latest LTS release, 2.19.2 as of this comment. For details, and a similar matching stack trace, see linked issue JENKINS-39179  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39423) "Site" field should be independent of each domain

2016-11-01 Thread fbelz...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39423  
 
 
  "Site" field should be independent of each domain   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Félix Belzunce Arcos  
 
 
Components: 
 active-directory-plugin  
 
 
Created: 
 2016/Nov/01 10:52 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Félix Belzunce Arcos  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because

[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith commented on  JENKINS-39179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All builds hang, JNA load deadlock on Windows slave   
 

  
 
 
 
 

 
 If it were possible to disable the SwapSpaceMonitor – perhaps that might be a way to remove this deadlock. But there seems to be no way to do that. Even when the swap space monitoring of slaves is disabled, the UserRequest still runs, as it seems to be updating the values, even if that slave condition is set to ignore.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave

2016-11-01 Thread nick.sonnev...@smartward.com.au (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39179  
 
 
  All builds hang, JNA load deadlock on Windows slave   
 

  
 
 
 
 

 
Change By: 
 Greg Smith  
 
 
Component/s: 
 slave-status-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Sonneveld commented on  JENKINS-39232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave   
 

  
 
 
 
 

 
 I can confirm that changing our slave startup script from 

 
javaws http://jenkins.internal:8080/computer/win-app01.bld/slave-agent.jnlp
 

 to 

 
java -jar slave.jar -jnlpUrl http://jenkins.internal:8080/computer/win-app01.bld/slave-agent.jnlp
 

 seems to allow our slaves to connect now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38566) Unexpected break statement hangs the build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38566  
 
 
  Unexpected break statement hangs the build   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 workflow-cps-plugin  
 
 
Component/s: 
 pipeline-build-step-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38798) Dynamic node names for parallel branches in Jenkins pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Use jenkinsci-users or StackOverflow for questions.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38798  
 
 
  Dynamic node names for parallel branches in Jenkins pipeline   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38855) fileExists to support file globbing

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38855  
 
 
  fileExists to support file globbing   
 

  
 
 
 
 

 
 Will not implement in fileExists. Could be in the Utility Steps plugin. Generally if you find yourself needing things like this, consider moving all the logic into an external script.  
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 pipeline-utility-steps-plugin  
 
 
Component/s: 
 pipeline-build-step-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this

[JIRA] (JENKINS-38856) BasicStep - dirExists

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-38856  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BasicStep - dirExists
 

  
 
 
 
 

 
 Probably simpler (untested): 

 

def dirExists(path) {sh(script: "[ -d '${path}' ]", returnStatus: true) == 0}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith commented on  JENKINS-39179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All builds hang, JNA load deadlock on Windows slave   
 

  
 
 
 
 

 
 Adding another full stack track of all slaves and threads. If you look at windows slave : Windows10Slave-2_bb5c6f6e-b2c7-47bf-b390-be39091dcb21 You can see the JNA deadlock situation again.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39179  
 
 
  All builds hang, JNA load deadlock on Windows slave   
 

  
 
 
 
 

 
Change By: 
 Greg Smith  
 
 
Attachment: 
 JenkinsHungThreadStack4.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38887) support launching multibranch pipeline (branch indexing)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-38887  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: support launching multibranch pipeline (branch indexing)   
 

  
 
 
 
 

 
 More generally, allow job to refer to any Queue.Task, allowing Queue.schedule2 to be called, so long as there are no parameters.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38856) BasicStep - dirExists

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38856  
 
 
  BasicStep - dirExists
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 workflow-basic-steps-plugin  
 
 
Component/s: 
 pipeline-build-step-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38887) support launching multibranch pipeline (branch indexing)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38887  
 
 
  support launching multibranch pipeline (branch indexing)   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 multibranch  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39145) add support to pass actions list besides the parameters list to the build step

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-39145  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: add support to pass actions list besides the parameters list to the build step   
 

  
 
 
 
 

 
 Are you talking about hudson.plugins.parameterizedtrigger.NodeAction? I am missing an explanation for the intended use case. If you just want to force a downstream freestyle project to run on a specific node, then it would be better to use LabelParameterDefinition downstream.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37823) Pipeline Model: Add a "wrappers" section

2016-11-01 Thread andrew.ba...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-37823  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37823  
 
 
  Pipeline Model: Add a "wrappers" section   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37823) Pipeline Model: Add a "wrappers" section

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37823  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Model: Add a "wrappers" section   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPipelineDef.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStep.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTWrapper.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTWrappers.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidator.java pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Root.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Wrappers.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/WrappersToMap.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ClosureModelTranslator.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/WrappersToMapTranslator.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/WrappersTest.java pipeline-model-definition/src/test/resources/errors/invalidWrapperType.groovy pipeline-model-definition/src/test/resources/json/errors/invalidWrapperType.json pipeline-model-definition/src/test/resources/json/multipleWrappers.json pipeline-model-definition/src/test/resources/json/simpleWrapper.json pipeline-model-definition/src/test/resources/multipleWrappers.groovy pipeline-model-definition/src/test/resources/simpleWrapper.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/b01db8aa6e692e06c8228e0891ca8f06aac4aa02 Log: [FIXED JENKINS-37823] Added "wrappers" section.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-37771) "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.

2016-11-01 Thread m...@caspar.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Caspar commented on  JENKINS-37771  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.   
 

  
 
 
 
 

 
 I don't know if it helps or hinders, but this Seems to be related (or similar) to this old issue... https://issues.jenkins-ci.org/browse/JENKINS-38145 Hope it helps.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave

2016-11-01 Thread eric...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Kim updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39232  
 
 
  unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave   
 

  
 
 
 
 

 
Change By: 
 Eric Kim  
 
 
Comment: 
 Not sure if this is the same issue for you, but for me, I am running Windows 2012 Server Edition for my slaves. When I download the slave-agent.jnlp file, Windows automatically tags something to the file that says its unsafe. If you Right-Click on slave-agent.jnlp and click on "properties", you might see a button that says "Unblock". This means the file was tagged by Windows as unsafe because it came from outside, and so you need to click on the "Unblock" button. Then it will start working.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave

2016-11-01 Thread eric...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Kim commented on  JENKINS-39232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave   
 

  
 
 
 
 

 
 Not sure if this is the same issue for you, but for me, I am running Windows 2012 Server Edition for my slaves. When I download the slave-agent.jnlp file, Windows automatically tags something to the file that says its unsafe. If you Right-Click on slave-agent.jnlp and click on "properties", you might see a button that says "Unblock". This means the file was tagged by Windows as unsafe because it came from outside, and so you need to click on the "Unblock" button. Then it will start working.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-35370) Workflow shell step ERROR: script returned exit code -1

Title: Message Title

Jesse Glick commented on JENKINS-35370

Re: Workflow shell step ERROR: script returned exit code -1

Ben Mathews Hmm, does not sound like a familiar issue. The fake exit status -1 means that Jenkins cannot find the PID of the controller sh script which tracks the output and exit code of your actual script (also sh, unless you specified a #!/bin/command). The typical reason for the failure to find this PID when using Image.inside is that the container does not share the right mount with the agent, for example because --volumes-from was not passed when it should have been. But in your case it was, and you say other shell scripts work, so something trickier is happening. If you can narrow it down to a reproducible test case, that would help a lot of course. Otherwise you will need to inspect the process tree inside the container, to see if the wrapper script is really still running or not; and inspect the …job@tmp sibling workspace that holds the control directory with the PID, output, and exit code.

Add Comment

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

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

[JIRA] (JENKINS-39422) Anchore plugin fails if input image is specified with a string containing a '/'

2016-11-01 Thread nu...@anchore.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Nurmi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39422  
 
 
  Anchore plugin fails if input image is specified with a string containing a '/'   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Nurmi  
 
 
Components: 
 anchore-container-scanner-plugin  
 
 
Created: 
 2016/Nov/01 9:43 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Daniel Nurmi  
 

  
 
 
 
 

 
 The anchore plugin reads input images from a file that is setup as an input pre-req before the anchore plugin runs - currently the plugin works with either imageIds or a string (repo/tag), but there is a bug that is triggering when an image is specified using a repo/tag string that contains a '/' character. See below for output when this occurs: 2016-11-01 21:30:33,900 DEBUG analyzer.py _init_ analyzer initialization: begin 2016-11-01 21:30:33,901 DEBUG analyzer.py _init_ init input processed, loading input images: [u'jenk_anchoretest/meh'] Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/anchore/anchore_utils.py", line 957, in image_context_add newimage = anchore_image.AnchoreImage(i, anchore_datadir, docker_cli=docker_cli, allimages=allimages, dockerfile=dockerfile, tmpdirroot=tmproot, usertype=usertype, anchore_db=anchore_db, docker_images=docker_images) File "/usr/lib/python2.7/site-packages/anchore/anchore_image.py", line 102, in _init_ if dockerfile and (os.stat(dockerfile).st_size <= 0 or not os.path.exists(dockerfile) or not os.path.isfile(dockerfile)): OSError: [Errno 2] No such file or directory: '/root/anchore.jenkinsplugin_227/dfile.jenk_anchoretest/meh' 2016-11-01 21:30:33,909 ERROR common.py anchore_print_err failed to run analyzer Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/anchore/cli/analyzer.py", line 304, in analyze success = analyzer.Analyzer(anchore_config=anchore_config, imagelist=inlist, allimages=allimages, force=force, args=args).run() File "/usr/lib/python2.7/site-packages/anchore/analyzer.py", line 52, in _init_ self.images = anchore_utils.image_context_add(imagelist, allimages,

[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39179  
 
 
  All builds hang, JNA load deadlock on Windows slave   
 

  
 
 
 
 

 
Change By: 
 Greg Smith  
 
 
Environment: 
 Jenkins 2.19.1 LTS  and Jenkins 2.19.2 LTS Jenkins 2.26Durable Task Plugin 1.12  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith commented on  JENKINS-39179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All builds hang, JNA load deadlock on Windows slave   
 

  
 
 
 
 

 
 Recreated again on the just release Jenkins 2.19.2 LTS version. Attached the thread dump from that slave. The locked slave is stuck, trying to load the SwapSpaceMonitor: 

 
"pool-1-thread-5 for channel" Id=23 Group=main RUNNABLE
	at com.sun.jna.Pointer.(Pointer.java:41)
	at com.sun.jna.Structure.(Structure.java:2078)
	at org.jvnet.hudson.Windows.monitor(Windows.java:42)
	at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:124)
	at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:114)
	at hudson.remoting.UserRequest.perform(UserRequest.java:153)
	at hudson.remoting.UserRequest.perform(UserRequest.java:50)
	at hudson.remoting.Request$2.run(Request.java:332)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

	Number of locked synchronizers = 1
	- java.util.concurrent.ThreadPoolExecutor$Worker@5edc0c11
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39179  
 
 
  All builds hang, JNA load deadlock on Windows slave   
 

  
 
 
 
 

 
Change By: 
 Greg Smith  
 
 
Attachment: 
 JenkinsHungThreadStack3.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave

2016-11-01 Thread smithesh.purushotham...@merck.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39179  
 
 
  All builds hang, JNA load deadlock on Windows slave   
 

  
 
 
 
 

 
Change By: 
 Greg Smith  
 
 
Summary: 
 All builds hang,  hung FileMonitoringTask.cleanup / get attributes  JNA load deadlock  on Windows  10  slave  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39421) Pipeline job HTTP Post

Title: Message Title


 
 
 
 

 
 
 

 
   
 Smithesh Purushothaman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39421  
 
 
  Pipeline job HTTP Post   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2016/Nov/01 9:22 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Smithesh Purushothaman  
 

  
 
 
 
 

 
 Is it possible to expose a pipeline job as HTTP POST API  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-39420) Search box - Width should auto adjust to he length of the search result

2016-11-01 Thread k...@fortinet.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Yu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39420  
 
 
  Search box - Width should auto adjust to he length of the search result   
 

  
 
 
 
 

 
Change By: 
 Kevin Yu  
 
 
Environment: 
 Chrome Version 50.0.2661.102 (64-bit)Ubuntu 15.10Jenkins 2.17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39420) Search box - Width should auto adjust to he length of the search result

2016-11-01 Thread k...@fortinet.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Yu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39420  
 
 
  Search box - Width should auto adjust to he length of the search result   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 searchbox.png  
 
 
Components: 
 core  
 
 
Created: 
 2016/Nov/01 9:15 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Kevin Yu  
 

  
 
 
 
 

 
 please see attached screenshot.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-35370) Workflow shell step ERROR: script returned exit code -1

2016-11-01 Thread b...@mathews2000.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Mathews commented on  JENKINS-35370  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Workflow shell step ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 The workspace is getting mounted (--volumes-from param is present) and is being interacted with. I've got a shell script that should take a couple minutes to complete. But within a couple seconds, the script will terminate and jenkins returns the above mentioned  

 

ERROR: script returned exit code -1
Finished: FAILURE
 

 The Jenkins log has the call stack 

 

hudson.AbortException: script returned exit code -1
	at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:285)
	at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:234)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	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)
 

 Looking at the pipeline code in the call stack, it appears that Jenkins thinks my process is exiting. But (a) it never fails when I launch the process directly w/ "docker run ..." and (b) it fails at a different spot every time. I've replaced my script w/ "for i in `seq 1 20`; do echo $i;date;sleep 5;done" and it never fails. So, it is apparent that something in the interaction between jenkins and my script is failing. FWIW, the script is a series of "python setup.py develop" commands.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39419) Environment variables empty for pipeline job

2016-11-01 Thread af...@plumgrid.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 fahd arshad created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39419  
 
 
  Environment variables empty for pipeline job   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 ownership-plugin  
 
 
Created: 
 2016/Nov/01 8:55 PM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 fahd arshad  
 

  
 
 
 
 

 
 I am trying to use the ownership plugin, however i notice environment variable is not being injected to be used in the groovy code itself.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-35453) Allow disabling the default commit status notifier

2016-11-01 Thread alex.eh...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Ehlke commented on  JENKINS-35453  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow disabling the default commit status notifier   
 

  
 
 
 
 

 
 Just to chime in with one use case: we're incrementally rolling out Jenkinsfile for CI, and so we'd prefer to disable the commit status update while we're still prototyping. We want to be able to have Jenkinsfile run in parallel with our existing CI to build all branches, to test it at scale, but since it's still unproven for us we wouldn't want any issues to result in GitHub pull requests being marked as failed as we roll it out. We have workarounds, just wanted to provide one use case since you seemed uncertain about the value of this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39404) Actionable should have methods for removing actions

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39404  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Actionable should have methods for removing actions   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerListener.java http://jenkins-ci.org/commit/pipeline-build-step-plugin/e03e4a2d6ed2417bfe4537dcc62fc4ea9d35fb78 Log: Noting a use case for JENKINS-39404.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39418) Throws error when scm syncing

2016-11-01 Thread li...@lmb.co.il (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liora Milbaum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39418  
 
 
  Throws error when scm syncing   
 

  
 
 
 
 

 
Change By: 
 Liora Milbaum  
 
 
Labels: 
 scm-sync-conifguration  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39418) Throws error when scm syncing

2016-11-01 Thread li...@lmb.co.il (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liora Milbaum created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39418  
 
 
  Throws error when scm syncing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Frédéric Camblor  
 
 
Components: 
 scm-sync-configuration-plugin  
 
 
Created: 
 2016/Nov/01 7:34 PM  
 
 
Priority: 
  Trivial  
 
 
Reporter: 
 Liora Milbaum  
 

  
 
 
 
 

 
 Errors from the log file: Nov 01, 2016 3:29:56 PM FINEST hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness Queuing commit Commit hudson.plugins.scm_sync_configuration.model.Commit@600d4ef0 :  Author : avi tal Comment : avi3tal: Job [Release] configuration updated Change performed by avi tal  Changeset :  A jobs/Release/config.xml  to SCM ... Nov 01, 2016 3:29:56 PM FINEST hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness Processing commit : Commit hudson.plugins.scm_sync_configuration.model.Commit@4acb073d :  Author : Liora Milbaum Comment : lioramilbaum: Job [Build-Liora] hierarchy deleted Change performed by Liora Milbaum  Changeset :  D jobs/Build-Liora/ Nov 01, 2016 3:29:56 PM FINE hudson.plugins.scm_sync_configuration.SCMManipulator Deleting SCM hierarchy [/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs/Build-Liora] from SCM ... Nov 01, 2016 3:29:56 PM FINER org.apache.maven.scm.manager.ScmManager remove THROW org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(AbstractGitScmProvider.java:291) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.remove(AbstractGitScmProvider.java:255) at org.apache.maven.scm.provider.AbstractScmProvider.remove(AbstractScmProvider.java:773) at org.apache.maven.scm.manager.AbstractScmManager.remove(AbstractScmManager.java:553) at hudson.plugins.scm_sync_configuration.SCMManipulator.deleteHierarchy(SCMManipulator.java:127) at

[JIRA] (JENKINS-26137) Mysterious serialization errors

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-26137  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Mysterious serialization errors   
 

  
 
 
 
 

 
 Can still observe some random test failures such as 

 

restartDuringDelay(org.jenkinsci.plugins.workflow.steps.WaitForConditionStepTest)  Time elapsed: 6.845 sec  <<< FAILURE!
java.lang.AssertionError: 
Started
[Pipeline] waitUntil
[Pipeline] {
[Pipeline] semaphore
[Pipeline] }
Will try again after 0.25 sec
[Pipeline] {
[Pipeline] semaphore
[Pipeline] }
Will try again after 29,247,120 yr
Resuming build
[Pipeline] {
[Pipeline] }
[Pipeline] // waitUntil
[Pipeline] End of Pipeline
java.lang.IllegalStateException: JENKINS-26137: Jenkins is shutting down
	at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.(RiverWriter.java:92)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:431)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:412)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:357)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:78)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:236)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:224)
	at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63)
	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

	at org.jenkinsci.plugins.workflow.test.steps.SemaphoreStep.waitForStart(SemaphoreStep.java:144)
	at org.jenkinsci.plugins.workflow.steps.WaitForConditionStepTest$7.evaluate(WaitForConditionStepTest.java:169)
 

 despite running with this precheck from JENKINS-32015, suggesting that some Jenkins.instance is set yet extensions are not loaded. If this happens during shutdown, then keeping a WeakHashMap cache would suffice as a workaround. If during startup, then it would not; that would suggest that flow resumption is happening too early. Hard to tell which, since the failure is not reproducible. At least the precheck should be modified to directly check PickleFactory.all().isEmpty().

[JIRA] (JENKINS-39355) API improvements based on real-world implementation and usage

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39355  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: API improvements based on real-world implementation and usage   
 

  
 
 
 
 

 
 Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/scm/api/SCMNavigator.java src/main/java/jenkins/scm/api/SCMSource.java http://jenkins-ci.org/commit/scm-api-plugin/14cb4225cb17e251019d996f7e925167728778e8 Log: JENKINS-39355 Fetching actions refinements  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39179) All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10

Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Smith commented on  JENKINS-39179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10   
 

  
 
 
 
 

 
 I can now confirm that this same lockup is happening on all versions of Windows 10, on both jre 7 and 8. This is killing us. The problem seems to be the loading of the jna libraries from both the getWin32FileAttributes call and the check of swap space at the same time, causing a deadlock on the slave, and then a deadlock from all pipeline builds.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39416) NTLM Authentication Support

2016-11-01 Thread developer.go...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Goran Sarenkapa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39416  
 
 
  NTLM Authentication Support   
 

  
 
 
 
 

 
Change By: 
 Goran Sarenkapa  
 
 
Comment: 
 test to see if i am getting email notifications.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39416) NTLM Authentication Support

2016-11-01 Thread developer.go...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Goran Sarenkapa commented on  JENKINS-39416  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NTLM Authentication Support   
 

  
 
 
 
 

 
 test to see if i am getting email notifications.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39417) JobDSL "configure" block can be called multiple times

2016-11-01 Thread ch...@puppet.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Price created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39417  
 
 
  JobDSL "configure" block can be called multiple times   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2016/Nov/01 6:31 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Chris Price  
 

  
 
 
 
 

 
 When using a configure block within a with block, it seems that the configure block may be executed multiple times. For example, I have a job that looks basically like this: 

 

def job = workflowJob(job_prefix) {
parameters {
  ...
}
definition {
cpsScm {
scm {
git {
remote {
url(git_repo)
}
branch(git_branch)
}
}
scriptPath(relative_jenkinsfile)
}
}
logRotator {
numToKeep(50)
}
}

job.with {
out.println("IN JOB.WITH BLOCK")
triggers {
scm('H H(21-22) * * 1')
}
configure { Node project ->
out.println("EXECUTING JOB CONFIGURE")
}
}
 

 When I run the seed job, I see the IN JOB.WITH BLOCK message only once, but the EXECUTING JOB CONFIGURE message is printed three times.

[JIRA] (JENKINS-39416) NTLM Authentication Support

2016-11-01 Thread developer.go...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Goran Sarenkapa created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39416  
 
 
  NTLM Authentication Support   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Goran Sarenkapa  
 
 
Components: 
 zaproxy-plugin  
 
 
Created: 
 2016/Nov/01 6:30 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Goran Sarenkapa  
 

  
 
 
 
 

 
 Add NTLM authentication support so that it can be configured via the plugin?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-39414) Cannot edit Job Configuration anymore after installing version 2.28

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39414  
 
 
  Cannot edit Job Configuration anymore after installing version 2.28   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 stapler  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39266) Timeout occurence inside a retry step wont cancel the latter

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 As of JENKINS-39072, if the body fails to terminate within a given period of time—for example, because you have caught the timeout exception and decided to continue—after a grace period the body will be forcibly killed. In this case it is better to put retry outside timeout rather than inside.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39266  
 
 
  Timeout occurence inside a retry step wont cancel the latter   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message

[JIRA] (JENKINS-39414) Cannot edit Job Configuration anymore after installing version 2.28

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39414  
 
 
  Cannot edit Job Configuration anymore after installing version 2.28   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39414) Cannot edit Job Configuration anymore after installing version 2.28

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39414  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot edit Job Configuration anymore after installing version 2.28   
 

  
 
 
 
 

 
 This is a regression in Stapler CC Vivek Pandey and Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-28385) Step to obtain raw contextual objects

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-28385  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-28385  
 
 
  Step to obtain raw contextual objects   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-28385) Step to obtain raw contextual objects

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-28385  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Step to obtain raw contextual objects   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/steps/GetContextStep.java src/main/java/org/jenkinsci/plugins/workflow/steps/WithContextStep.java src/main/resources/org/jenkinsci/plugins/workflow/steps/GetContextStep/config.jelly src/main/resources/org/jenkinsci/plugins/workflow/steps/GetContextStep/help.html src/main/resources/org/jenkinsci/plugins/workflow/steps/WithContextStep/config.jelly src/main/resources/org/jenkinsci/plugins/workflow/steps/WithContextStep/help.html src/test/java/org/jenkinsci/plugins/workflow/steps/WithContextStepTest.java http://jenkins-ci.org/commit/workflow-basic-steps-plugin/bf17f230386b6441e93807e92b155a2a93f219a3 Log: Merge pull request #25 from jglick/context-step-JENKINS-28385 JENKINS-28385 getContext & withContext steps Compare: https://github.com/jenkinsci/workflow-basic-steps-plugin/compare/7d6d99660008...bf17f230386b  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-28385) Step to obtain raw contextual objects

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-28385  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Step to obtain raw contextual objects   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/steps/GetContextStep.java src/main/java/org/jenkinsci/plugins/workflow/steps/WithContextStep.java http://jenkins-ci.org/commit/workflow-basic-steps-plugin/72f7e2a99398367d36670424f2e072c3f981ac13 Log: JENKINS-28385 Initial implementation of getContext & withContext steps.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39337) error step has no log output

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 As designed. It throws up an exception. Whoever catches that exception may choose to log it, or not. If the exception terminates the build, the build log shows it. ErrorAction can be used to determine which steps terminated with this exception.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39337  
 
 
  error step has no log output   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To

[JIRA] (JENKINS-39266) Timeout occurence inside a retry step wont cancel the latter

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39266  
 
 
  Timeout occurence inside a retry step wont cancel the latter   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 

  
 
 
 
 

 
 having a code such as: {code} node('master') {  timeout (10) {retry(2) {  try {sh "while true; do; sleep 2; done"  } catch (e) {echo "wont ever run as theres no exception coming out from the timeout"  }}  }} {code}   leds to the first retry to end due a (supposedly) internal exception being thrown but go on with the second one.Shouldnt timeouts forbid retrying? Besides, timeouts won't throw an exception as the last echo won't ever happen   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38134) Generate checksums for war, Windows and OS X distributables

2016-11-01 Thread giuseppe.ianne...@brokenloop.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Generate checksums for war, Windows and OS X distributables   
 

  
 
 
 
 

 
 Code changed in jenkins User: Kohsuke Kawaguchi Path: Makefile toolAvailability.sh http://jenkins-ci.org/commit/packaging/6bb93ed19b0ed8809f92ee7a6f06d46b4d268179 Log: Revert "JENKINS-38134 Check sha256sum tool availability." This reverts commit 4563dc4186d7075bdc6d84817670d2edc43332b1. The publish rule doesn't work with my make, and AFAIK this is simply invalid syntax. I don't think make has a provision for running a command prior to attaining other rules. 
 

 
 
 + make WAR=... JENKINS_URL=... BRAND=... BUILDENV=... CREDENTIAL=... publish 
 
 
 bash ./toolAvailability.sh 
 
 
 war.publish msi.publish osx.publish deb.publish rpm.publish suse.publish 
 
 
 make: war.publish: Command not found 
 
 
 make: *** [publish] Error 127 
 

 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39415) Xvfb in a parallel pipeline doesn't use the executor number as display name

Title: Message Title


 
 
 
 

 
 
 

 
   
 Giuseppe Iannello commented on  JENKINS-39415  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Xvfb in a parallel pipeline doesn't use the executor number as display name   
 

  
 
 
 
 

 
 Creating a freestyle job, enabling Xvfb with default options and triggering two concurrent runs of the job has the expected behavior - the screen name matches the executor number.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39356) EC2 Plugin Fails to give list of regions after key pair in cloud creation

2016-11-01 Thread ryan.wall...@clusterhq.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan Wallner closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39356  
 
 
  EC2 Plugin Fails to give list of regions after key pair in cloud creation   
 

  
 
 
 
 

 
Change By: 
 Ryan Wallner  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39356) EC2 Plugin Fails to give list of regions after key pair in cloud creation

2016-11-01 Thread ryan.wall...@clusterhq.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan Wallner commented on  JENKINS-39356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Plugin Fails to give list of regions after key pair in cloud creation   
 

  
 
 
 
 

 
 not sure what caused this to happen for the versions i described above, but updated the EC2 Plugin to 1.36 and AWS SDK to 1.11.37 and it started to work again.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-20670) Plugin does not show all defects

2016-11-01 Thread matthew.potter...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Potterton commented on  JENKINS-20670  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin does not show all defects   
 

  
 
 
 
 

 
 I have opened JENKINS-38694 which documents an updated version of this behavior in the later versions of the plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39415) Xvfb in a parallel pipeline doesn't use the executor number as display name

2016-11-01 Thread giuseppe.ianne...@brokenloop.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Giuseppe Iannello created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39415  
 
 
  Xvfb in a parallel pipeline doesn't use the executor number as display name   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 zregvart  
 
 
Components: 
 xvfb-plugin  
 
 
Created: 
 2016/Nov/01 4:57 PM  
 
 
Environment: 
 Jenkins 2.28  Xvfb plugin 1.1.3  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Giuseppe Iannello  
 

  
 
 
 
 

 
 Using the following example pipeline 

 

stage('stage_1') {
  parallel (
's_1_1': {
  node() {
wrap([$class: 'Xvfb']) {
sh 'sleep 10'
}
  }
},
's_1_2': {
  node() {
wrap([$class: 'Xvfb']) {
sh 'sleep 10'
}
  }
}
  )
}
 

 the Xvfb binary is always invoked with ":0" as screen name, even if the documentation suggests the screen name should match the executor number + offset. Manually specifying displayNameOffset has no effect. The only way to make it work in parallel is by setting autoDisplayName, but we've experienced random failures with that option too. It would be great for the default behavior to allow parallel jobs without any manual configuration.

[JIRA] (JENKINS-39414) Cannot edit Job Configuration anymore after installing version 2.28

2016-11-01 Thread flabrie (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Labrie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39414  
 
 
  Cannot edit Job Configuration anymore after installing version 2.28   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Nov/01 4:38 PM  
 
 
Environment: 
 Jenkins 2.28  Mac OS X El Capitan 10.11.6  Java SE 1.8.0_05-b13  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Francis Labrie  
 

  
 
 
 
 

 
 Cannot edit Job Configuration anymore after installing version 2.28. The configuration page loads, but an exception is thrown and the stacktrace is displayed: 

 

nov. 01, 2016 12:17:58 PM hudson.ExpressionFactory2$JexlExpression evaluate
AVERTISSEMENT: Caught exception evaluating: d.helpFile in /view/Android%20Applications/job/AQT%20Big%20Bang%20Android%20Application/configure. Reason: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
	at sun.reflect.GeneratedMethodAccessor470.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
	at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
	at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
	at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
	at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
	at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
	at

[JIRA] (JENKINS-39413) Errors in LR Scenario set build status to UNSTABLE

2016-11-01 Thread mikhail.boyc...@hpe.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikhail Boychuk created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39413  
 
 
  Errors in LR Scenario set build status to UNSTABLE   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Yafim Kazak  
 
 
Attachments: 
 build.xml, config.xml, log  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2016/Nov/01 4:37 PM  
 
 
Environment: 
 Jenkins 2.19.1  Master and slave: Win 10  
 
 
Labels: 
 loadrunner  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Mikhail Boychuk  
 

  
 
 
 
 

 
 Errors occured in the scenario set build status to "Unstable" even if all SLA's passed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39409) Reword "Block inheritance..." to "Do NOT inherit..."

2016-11-01 Thread will.berr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Will Berriss updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39409  
 
 
  Reword "Block inheritance..." to "Do NOT inherit..."   
 

  
 
 
 
 

 
Change By: 
 Will Berriss  
 

  
 
 
 
 

 
 I got caught out by this text when configuring a project:"Block inheritance of global authorization matrix" because I thought it meant, 'Inherit the block of authorization permissions"I should have read the help text first I know, but at a glance I thought of the block of permissions, i.e. the matrix of permissions.  A different meaning of the word 'block'.So, could this be reworded to something like,"Do NOT inherit the global authorization matrix" As that is  unamiguous  unambiguous  and clear and I would not tick/check that box in a hurry.Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39412) Rebuild

2016-11-01 Thread pberr...@securitymetrics.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Berrett updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39412  
 
 
  Rebuild   
 

  
 
 
 
 

 
Change By: 
 Paul Berrett  
 
 
Summary: 
 Webhook - java.lang.AbstractMethodError Rebuild  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39376) StackOverflowError involving CpsTransformer$_visitWithSafepoint_closure6.doCall