[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally

[n...@x2systems.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Neil Sleightholm commented on  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
 Ivan Fernandez Calvo - do you know when this fix will be released? It looks like there is an issue with PR2.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51060) Environment variables are not passed to cmake steps when running in pipeline withEnv

[janne.ron...@iki.fi (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janne Rönkkö commented on  JENKINS-51060  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables are not passed to cmake steps when running in pipeline withEnv   
 

  
 
 
 
 

 
 The sh step contains only cmake invocation, i.e. it is like this: sh 'cmake --version' We are not building on the master as we use agents for building. /usr/local/bin is added to path using Node Properties (there is environment variable called PATH+LOCAL_BIN which has value /usr/local/bin). Also our master has /usr/local/bin in it's PATH  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-43135) Error 404 when click "Go to Classic" from Pipeline Editor

[npa...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolae Pascu updated  JENKINS-43135  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43135  
 
 
  Error 404 when click "Go to Classic" from Pipeline Editor   
 

  
 
 
 
 

 
Change By: 
 Nicolae Pascu  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51123) Deadlock in CpsFlowExecution

[laurent.gou...@online.fr (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Laurent Goujon commented on  JENKINS-51123  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock in CpsFlowExecution   
 

  
 
 
 
 

 
 Hopefully the issue can be fixed by changing the order of operations. Here's my attempt at it: https://github.com/jenkinsci/workflow-cps-plugin/pull/225  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41929) Offer "Build with Parameters" on first build when declarative Jenkinsfile found

[dima_...@ukr.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmitry Bondarenko commented on  JENKINS-41929  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Offer "Build with Parameters" on first build when declarative Jenkinsfile found   
 

  
 
 
 
 

 
 In JENKINS 2.107.2 (April 2018) there are some minor problems with parameters. In particular - parameters sometimes are not recognized from pipeline definitions. I need to start build couple of times as-is to make parameters recognized. Also when I added new a "choice" parameter to existing parameters it was not recognized at all. So, I have to add it in UI (separately from pipeline definitions). And pipeline definitions were not sync from UI parameters, so such parameter was defined in UI for pipeline but it was not added to pipeline script. Thus, "pipeline script" and "pipeline parameters" in UI editor can be very different. Also a bad thing - it does not provide a possibility to specify captions for choice-values!  For example I would like to use INI-file format for such purposes, so like this - choise: ['R2010B=Release 2010.2\nR2015=Release 9.0\nR2016=Release 9.1\nR2017=Release 2017.1'] - such format will be much more useful for end-user. So, when calling a build script it should use choice value "R2017" and the "Release 2017.1" text is only to show in UI for user when choosing a parameter value for a build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51058) Upgrade Jira plugin version and httpcomponents-client

[ol...@apache.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy commented on  JENKINS-51058  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Upgrade Jira plugin version and httpcomponents-client
 

  
 
 
 
 

 
 pr https://github.com/jenkinsci/blueocean-plugin/pull/1729   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51123) Deadlock in CpsFlowExecution

[laurent.gou...@online.fr (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Laurent Goujon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51123  
 
 
  Deadlock in CpsFlowExecution   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 jstack.txt  
 
 
Components: 
 workflow-cps-plugin  
 
 
Created: 
 2018-05-04 03:49  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Laurent Goujon  
 

  
 
 
 
 

 
 It seems that a deadlock has been introduced in some recent changes to workflow-cps-plugin. The whole jstack has been attached to the report, but two threads are waiting on each other: 
 
the first thread is calling CpsFlowExecution#subsumeHead, got the lock on the instance, and then trying to acquire the r/w lock on the node storage 
the second thread is calling CpsFlowExecution#getNode, got the r/w lock on the storage, and then is calling close which tries to get the instance lock 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[JIRA] (JENKINS-51122) Compile an error, the word constants too long

[zyf_...@126.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 zz yf created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51122  
 
 
  Compile an error, the word constants too long   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 _unsorted  
 
 
Created: 
 2018-05-04 03:44  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 zz yf  
 

  
 
 
 
 

 
 Compile an error, the word constants too long  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

   

[JIRA] (JENKINS-51121) base64 package Not fount

[zyf_...@126.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 zz yf created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51121  
 
 
  base64 package Not fount
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 _unsorted  
 
 
Created: 
 2018-05-04 03:39  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 zz yf  
 

  
 
 
 
 

 
 Compile an error, unable to find the Base64 package  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 

[JIRA] (JENKINS-51090) Emails no longer sent to developers on build failure

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum commented on  JENKINS-51090  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Emails no longer sent to developers on build failure   
 

  
 
 
 
 

 
 As far as I know nothing has changed recently that would affect this. Can you turn on debugging in global email-ext settings and post the build output of a failure  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51120) Allow uploading of config.xml as another means to import

[gurce.isikyil...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gurce Isikyildiz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51120  
 
 
  Allow uploading of config.xml as another means to import   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 job-import-plugin  
 
 
Created: 
 2018-05-04 01:16  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Gurce Isikyildiz  
 

  
 
 
 
 

 
 Would also be nice to have the ability to upload a config.xml from the local file-system, to be imported into the server, for cases where the config.xml is retrieved from version-control and we wish to push it to the server.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-51119) Permit updating of existing jobs on destination server

[gurce.isikyil...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gurce Isikyildiz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51119  
 
 
  Permit updating of existing jobs on destination server   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 job-import-plugin  
 
 
Created: 
 2018-05-04 01:14  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Gurce Isikyildiz  
 

  
 
 
 
 

 
 Presently, the plugin only permits the addition of new jobs, but could it also (perhaps optionally) permit the updating of existing jobs from one server to the other?   Presently, when I try to do this, I get a "FAILED - Duplicate Job Name" error message.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

[JIRA] (JENKINS-51116) Failed to set Access Control of CollabNet Security Realm

[mrxcas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 mrc updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51116  
 
 
  Failed to set Access Control of CollabNet Security Realm   
 

  
 
 
 
 

 
Change By: 
 mrc  
 

  
 
 
 
 

 
 I tried  to  set Access Control to CollabNet Security Realm in Global Security of Jenkins, but when i apply the changes, show the following error:h2. Stack tracejava.lang.NoClassDefFoundError: javax.mail.internet.MimeMultipart at org.apache.axis.encoding.DefaultTypeMappingImpl.class$(DefaultTypeMappingImpl.java:120) at org.apache.axis.encoding.DefaultTypeMappingImpl.initMappings(DefaultTypeMappingImpl.java:308) at org.apache.axis.encoding.DefaultTypeMappingImpl.(DefaultTypeMappingImpl.java:91) at org.apache.axis.encoding.DefaultTypeMappingImpl.getSingletonDelegate(DefaultTypeMappingImpl.java:85) at org.apache.axis.encoding.TypeMappingRegistryImpl.(TypeMappingRegistryImpl.java:155) at org.apache.axis.encoding.TypeMappingRegistryImpl.(TypeMappingRegistryImpl.java:149) at org.apache.axis.deployment.wsdd.WSDDDeployment.(WSDDDeployment.java:449) at org.apache.axis.deployment.wsdd.WSDDDocument.setDocument(WSDDDocument.java:139) at org.apache.axis.deployment.wsdd.WSDDDocument.(WSDDDocument.java:65) at org.apache.axis.configuration.FileProvider.configureEngine(FileProvider.java:179) at org.apache.axis.AxisEngine.init(AxisEngine.java:172) at org.apache.axis.AxisEngine.(AxisEngine.java:156) at org.apache.axis.client.AxisClient.(AxisClient.java:52) at org.apache.axis.client.Service.getAxisClient(Service.java:104) at org.apache.axis.client.Service.(Service.java:113) at com.collabnet.ce.soap60.webservices.ClientSoapStub.(ClientSoapStub.java:50) at com.collabnet.ce.soap60.webservices.cemain.CollabNetSoapStub.(CollabNetSoapStub.java:21) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at com.collabnet.ce.soap60.webservices.ClientSoapStubFactory.createSoapStub(ClientSoapStubFactory.java:97) Caused: java.lang.RuntimeException at com.collabnet.ce.soap60.webservices.ClientSoapStubFactory.createSoapStub(ClientSoapStubFactory.java:107) at com.collabnet.ce.soap60.webservices.ClientSoapStubFactory.getSoapStub(ClientSoapStubFactory.java:60) at com.collabnet.ce.webservices.CollabNetApp.getICollabNetSoap(CollabNetApp.java:201) at com.collabnet.ce.webservices.CollabNetApp.getICollabNetSoap(CollabNetApp.java:191) at com.collabnet.ce.webservices.CollabNetApp.(CollabNetApp.java:114) at hudson.plugins.collabnet.auth.CollabNetSecurityRealm.(CollabNetSecurityRealm.java:44) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at 

[JIRA] (JENKINS-45614) Activity tab is really slow

[ol...@apache.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy assigned an issue to Olivier Lamy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45614  
 
 
  Activity tab is really slow   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Assignee: 
 Vivek Pandey Olivier Lamy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49231) jira-plugin 2.5.1 throws exception fails build

[ol...@apache.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy assigned an issue to Olivier Lamy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49231  
 
 
  jira-plugin 2.5.1 throws exception fails build   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Assignee: 
 Olivier Lamy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50420) Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4

[de...@ikedam.jp (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam commented on  JENKINS-50420  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4   
 

  
 
 
 
 

 
 Groovy-postbuild-2.4.1 is released. It contains fake GroovyPostbuildAction so that build-monitor not to fail. But the feature of build-monitor to cooperate with groovy-postbuild doesn't work yet. It requires the upcoming version of build-monitor to have it work again.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API

[ol...@apache.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48357  
 
 
  Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Labels: 
 jira-plugin-2.5.2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49975) BasicHttpCache error with JIRA Plugin 2.5.1

[ol...@apache.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49975  
 
 
  BasicHttpCache error with JIRA Plugin 2.5.1   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Labels: 
 jira-plugin-2.5.2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49975) BasicHttpCache error with JIRA Plugin 2.5.1

[ol...@apache.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy assigned an issue to Olivier Lamy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49975  
 
 
  BasicHttpCache error with JIRA Plugin 2.5.1   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Assignee: 
 Olivier Lamy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49231) jira-plugin 2.5.1 throws exception fails build

[ol...@apache.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49231  
 
 
  jira-plugin 2.5.1 throws exception fails build   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Labels: 
 jira-plugin-2.5.2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-25829) Proxy configuration does not work

[ol...@apache.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-25829  
 
 
  Proxy configuration does not work   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Labels: 
 jira-plugin-2.5.2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50087) Integration Test for Table Model (in LabelProvider)

[ullrich.haf...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-50087  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Integration Test for Table Model (in LabelProvider)   
 

  
 
 
 
 

 
 So, jetzt ging es doch schneller als gedacht. Ich habe eine neue Version der Test Bibliothek hochgeladen. Damit Sie diese bekommen müssen Sie im pom.xml des warnings plugins die properties so setzen: 

 

  
6.1.0
2.39-20180503.223048-1
  
 

 Im Testfall kann dann das Setzen von JS auf false unterbleiben.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51118) bat(returnStdout:true , script: cmd).trim() returns error code1 if the output from the command is 0

[rg00352...@techmahindra.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rohit Gagan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51118  
 
 
  bat(returnStdout:true , script: cmd).trim() returns error code1 if the output from the command is 0   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 batch-task-plugin  
 
 
Created: 
 2018-05-03 22:41  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Rohit Gagan  
 

  
 
 
 
 

 
 def checkSvnMergeInfo1(svnMTTrunk,svnMT){ cmd="svn mergeinfo ${svnMTTrunk} ${svnMT} --show-revs eligible| FIND \"\" /v /c" def stdout= bat(returnStdout:true , script: cmd).trim() OUtput expected = 0   Output is  ERROR: script returned exit code 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
 

[JIRA] (JENKINS-41704) Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException

[michael.dou...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Doubez commented on  JENKINS-41704  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException   
 

  
 
 
 
 

 
 I have a fix: I removed all references to old implementation package com.thales... I don't know how exactly the jelly framework locates the included files but I assume the mixing of both packages causes a resolution error. I'll make a pull request once I have restored the unit tests.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50953) Tool to offer incremental updates

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-50953  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Tool to offer incremental updates   
 

  
 
 
 
 

 
 At this point I have a script which, given a current GAV and a target branch (incl. PR!), will dig through Artifactory and GitHub metadata to determine the best available update (whether that be a JEP-305-based incremental version, or simply from MRP). The next step is to embed this in a tool which takes a metadata file and actually edits it to select updates for one or more components. Since I am struggling to find an example of a YAML config file already using incremental versions which could be used as a test bed, and I left some comments in the BOM JEP draft about a suggested modification to the format that would be more amenable to this tool, I am going to start with a Maven POM processor that could be used for JENKINS-47498 as well as simple chained pull requests.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50420) Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50420  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4   
 

  
 
 
 
 

 
 Code changed in jenkins User: ikedam Path: src/main/java/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildAction.java http://jenkins-ci.org/commit/groovy-postbuild-plugin/b27547ca371a06dff224bd4078ec60240b784014 Log: Merge pull request #34 from ikedam/feature/JENKINS-50420_FakeGroovyPostbuildAction JENKINS-50420 Add fake GroovyPostbuildAction Compare: https://github.com/jenkinsci/groovy-postbuild-plugin/compare/f981d02cc968...b27547ca371a *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50420) Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50420  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4   
 

  
 
 
 
 

 
 Code changed in jenkins User: ikedam Path: src/main/java/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildAction.java http://jenkins-ci.org/commit/groovy-postbuild-plugin/03fe5daceeb40630166787ca1873b172cbe02333 Log: JENKINS-50420 Add fake GroovyPostbuildAction not to cause exceptions in build-monitor plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-45614) Activity tab is really slow

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-45614  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Activity tab is really slow   
 

  
 
 
 
 

 
 Sverre Moe Sorry for not getting back on the activity tab HAR. It could be some plugins causing it as well, hard to tell.  Have been busy with other commitments. We hope to make progress on it but can't give you a timeline at the moment.  Thanks for patience.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-25829) Proxy configuration does not work

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-25829  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Proxy configuration does not work   
 

  
 
 
 
 

 
 Code changed in jenkins User: Olivier Lamy Path: .gitignore pom.xml src/main/java/com/atlassian/httpclient/apache/httpcomponents/ApacheAsyncHttpClient.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/ProvidedProxyConfig.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/ProxyConfig.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/ProxyConfigFactory.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/ProxyCredentialsProvider.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/SystemPropertiesProxyConfig.java src/test/java/com/atlassian/httpclient/apache/httpcomponents/ApacheAsyncHttpClientTest.java http://jenkins-ci.org/commit/jira-plugin/f4d936805226aa2f91eb57341d0add3787dd2a72 Log: [WIP][DO NOT MERGE]JENKINS-25829 proxy usage from jenkins (#148) 
 
JENKINS-25829 add support for proxy usage (with basic authz) 
 Signed-off-by: olivier lamy  
 
fix non used import 
 Signed-off-by: olivier lamy  
 
add some unit tests for ApacheAsyncHttpClient 
 Signed-off-by: olivier lamy  
 
reenable coverage as there is now some tests for httpclient 
 Signed-off-by: olivier lamy  
 
remove non used files (should improve coverage  ) 
 Signed-off-by: olivier lamy   *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 

[JIRA] (JENKINS-51117) Having CMake versions 3.11 in Global Tool Configuration cause errors in updating plugins

[henryborch...@yahoo.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Henry Borchers created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51117  
 
 
  Having CMake versions 3.11 in Global Tool Configuration cause errors in updating plugins   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Martin Weber  
 
 
Components: 
 cmakebuilder-plugin  
 
 
Created: 
 2018-05-03 21:37  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Henry Borchers  
 

  
 
 
 
 

 
 If you manually add cmake-3.11.1 to the CMake installations in the Global Tool Configuration, any time you check updates in the Plugins Manager menu, the resulting page is "None of the tool installer metadata passed the signature check"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-50087) Integration Test for Table Model (in LabelProvider)

[ullrich.haf...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-50087  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Integration Test for Table Model (in LabelProvider)   
 

  
 
 
 
 

 
 Sieht schlecht aus mit der JS Unterstützung in HTML Unit. Ich bin auf einige Compile Fehler gestoßen bei der Aktualisierung... Anfrage in der Mailing Liste läuft.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-46809) Allow sequential stages inside parallel in Declarative syntax

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-46809  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow sequential stages inside parallel in Declarative syntax   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.java pipeline-model-api/src/main/resources/ast-schema.json pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.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/parser/RuntimeASTTransformer.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/Messages.properties pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.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/AgentTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/DeclarativeUpgradeTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/EnvironmentTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/PostStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ToolsTest.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/WhenStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ExecuteConvertedTest.java pipeline-model-definition/src/test/resources/agentOnGroup.groovy pipeline-model-definition/src/test/resources/environmentInGroup.groovy pipeline-model-definition/src/test/resources/errors/emptyStagesInGroup.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesAndGroups.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesGroupsDeepNesting.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesStepsAndGroups.groovy pipeline-model-definition/src/test/resources/errors/parallelStepsAndGroups.groovy pipeline-model-definition/src/test/resources/errors/topLevelStageGroupsDeepNesting.groovy pipeline-model-definition/src/test/resources/json/agentOnGroup.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesAndGroups.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesGroupsDeepNesting.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesStepsAndGroups.json pipeline-model-definition/src/test/resources/json/errors/parallelStepsAndGroups.json pipeline-model-definition/src/test/resources/json/errors/topLevelStageGroupsDeepNesting.json pipeline-model-definition/src/test/resources/json/parallelStagesGroupsAndStages.json pipeline-model-definition/src/test/resources/json/topLevelStageGroup.json 

[JIRA] (JENKINS-51060) Environment variables are not passed to cmake steps when running in pipeline withEnv

[fifteenknots...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Weber updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51060  
 
 
  Environment variables are not passed to cmake steps when running in pipeline withEnv   
 

  
 
 
 
 

 
Change By: 
 Martin Weber  
 
 
Summary: 
 Environment variables are not passed to cmake steps whenrunning in pipeline withEnv  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51060) Environment variables are not passed to cmake steps when

[fifteenknots...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Weber updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51060  
 
 
  Environment variables are not passed to cmake steps when
 

  
 
 
 
 

 
Change By: 
 Martin Weber  
 
 
Summary: 
 Environment variables are not passed to cmake  steps  when
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51060) Environment variables are not passed to cmake when

[fifteenknots...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Weber commented on  JENKINS-51060  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables are not passed to cmake when   
 

  
 
 
 
 

 
 

Also, if CMake is installed in /usr/local/bin (and it works in sh step) the CMake builder plugin apparently does not find cmake binary:
 The plugin directly invokes cmake, without any shell. So it will see only the environment variables of the jenkins master process or agent process. My guess is that your sh step adds /usr/local/bin to $PATH. On linux, processes started as a system process during boot inherit fewer environment variables than the processes started by a user`s login shell. AFAIK, a recent SUSE or RHEL does not have /usr/local/bin in $PATH by default. Could you check the Jenkins System Information page for the PATH variable?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51116) Failed to set Access Control of CollabNet Security Realm

[mario.cas...@regional.com.py (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mario Castro created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51116  
 
 
  Failed to set Access Control of CollabNet Security Realm   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 whsu  
 
 
Components: 
 collabnet-plugin  
 
 
Created: 
 2018-05-03 19:30  
 
 
Environment: 
 Jenkins ver. 2.89.2, CollabNet TeamForge Version: 17.11.455  
 
 
Labels: 
 jenkins plugins  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mario Castro  
 

  
 
 
 
 

 
 I tried set Access Control to CollabNet Security Realm in Global Security of Jenkins, but when i apply the changes, show the following error: Stack trace java.lang.NoClassDefFoundError: javax.mail.internet.MimeMultipart at org.apache.axis.encoding.DefaultTypeMappingImpl.class$(DefaultTypeMappingImpl.java:120) at org.apache.axis.encoding.DefaultTypeMappingImpl.initMappings(DefaultTypeMappingImpl.java:308) at org.apache.axis.encoding.DefaultTypeMappingImpl.(DefaultTypeMappingImpl.java:91) at org.apache.axis.encoding.DefaultTypeMappingImpl.getSingletonDelegate(DefaultTypeMappingImpl.java:85) at org.apache.axis.encoding.TypeMappingRegistryImpl.(TypeMappingRegistryImpl.java:155) at org.apache.axis.encoding.TypeMappingRegistryImpl.(TypeMappingRegistryImpl.java:149) at org.apache.axis.deployment.wsdd.WSDDDeployment.(WSDDDeployment.java:449) at org.apache.axis.deployment.wsdd.WSDDDocument.setDocument(WSDDDocument.java:139) at org.apache.axis.deployment.wsdd.WSDDDocument.(WSDDDocument.java:65) at org.apache.axis.configuration.FileProvider.configureEngine(FileProvider.java:179) at org.apache.axis.AxisEngine.init(AxisEngine.java:172) at org.apache.axis.AxisEngine.(AxisEngine.java:156) at 

[JIRA] (JENKINS-48714) Post-Build Action does not show links to downstream builds

[vamsi...@rocketmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Guru Vamsi CHINTALA commented on  JENKINS-48714  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Post-Build Action does not show links to downstream builds
 

  
 
 
 
 

 
 We see the same issue. Couldn't see the the option to trigger parameterized build in post build actions but existing jobs are running fine.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51060) Environment variables are not passed to cmake when

[fifteenknots...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Weber started work on  JENKINS-51060  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Martin Weber  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-42271) run a script defined in package.json scripts

[nfalc...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco closed an issue as Won't Do  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please reopen the issue with reproducible steps to understand exactly what want you do.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42271  
 
 
  run a script defined in package.json scripts   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Do  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-42271) run a script defined in package.json scripts

[nfalc...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco assigned an issue to Nikolas Falco  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42271  
 
 
  run a script defined in package.json scripts   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Assignee: 
 Nikolas Falco  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50920) NPM registry credentials not correctly formatted

[nfalc...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco edited a comment on  JENKINS-50920  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NPM registry credentials not correctly formatted   
 

  
 
 
 
 

 
 Today I have try to use {noformat} //my.private.registry/:_authToken= {noformat}   to authenticate against our artifactory instance without success.I also found a [stackoverflow post|https://stackoverflow.com/questions/49404870/how-to-set-auth-for-a-scoped-registry-in-npmrc] where nexus use the same configuration with username and _password instead of _authToken. More investigation  are  is  needed, I have no a plan to solve this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50920) NPM registry credentials not correctly formatted

[nfalc...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-50920  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NPM registry credentials not correctly formatted   
 

  
 
 
 
 

 
 Today I have try to use //my.private.registry/:_authToken= to authenticate against our artifactory instance without success. I also found a stackoverflow post where nexus use the same configuration with username and _password instead of _authToken.   More investigation are needed, I have no a plan to solve this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51062) JEP-200 issue with plugin Gradle Plugin

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-51062  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51062  
 
 
  JEP-200 issue with plugin Gradle Plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51062) JEP-200 issue with plugin Gradle Plugin

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51062  
 
 
  JEP-200 issue with plugin Gradle Plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 JEP-200 JEP-200-invalid  lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51062) JEP-200 issue with plugin Gradle Plugin

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51062  
 
 
  JEP-200 issue with plugin Gradle Plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51062) JEP-200 issue with plugin Gradle Plugin

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51062  
 
 
  JEP-200 issue with plugin Gradle Plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Francisco Fernández Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51062) JEP-200 issue with plugin Gradle Plugin

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-51062  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51062  
 
 
  JEP-200 issue with plugin Gradle Plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-51057  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM   
 

  
 
 
 
 

 
 Some more events from our logs:   

 
May 03, 2018 1:36:00 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher doDispatch
Error dispatching event to SSE channel. Write failed.
May 03, 2018 1:36:36 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher doDispatch
Error dispatching event to SSE channel. Write failed.
May 03, 2018 1:36:39 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher processRetries
Error dispatching retry event to SSE channel. Write failed. Dispatcher jenkins-blueocean-core-js-1525286577663-o9g92 (1006446612).
May 03, 2018 1:36:39 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher processRetries
Error dispatching retry event to SSE channel. Write failed. Dispatcher jenkins-blueocean-core-js-1525286577663-o9g92 (1006446612).
May 03, 2018 1:36:39 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher processRetries
Error dispatching retry event to SSE channel. Write failed. Dispatcher jenkins-blueocean-core-js-1525286577663-o9g92 (1006446612). 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51115) Quality gate check as a post build action not working - always return TRUE

[me.nicolas.wri...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas Wright created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51115  
 
 
  Quality gate check as a post build action not working - always return TRUE   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Rafael Ramos  
 
 
Components: 
 sonar-quality-gates-plugin  
 
 
Created: 
 2018-05-03 17:37  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Nicolas Wright  
 

  
 
 
 
 

 
 Does not work for me, no matter the current quality gate status, the plugin always return true and won't break my build. using Jenkins 2.119 and sonar 5.6.3.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-51057  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM   
 

  
 
 
 
 

 
   I got further when using the non-alpine openjdk image.  Still doesn't build, but it is due to tests failing.   

 
$ docker run --rm -it -v maven-repo:/root/.m2 -v $PWD:/src:rw -w /src maven:3-jdk-8 mvn verify
...
Results :
Failed tests:
org.jenkinsci.plugins.ssegateway.EventHistoryStoreTest.test_autoDeleteOnExpire(org.jenkinsci.plugins.ssegateway.EventHistoryStoreTest)
 Run 1: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50>
 Run 2: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50>
 Run 3: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50>
 Run 4: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50>
 Run 5: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50>
org.jenkinsci.plugins.ssegateway.EventHistoryStoreTest.test_delete_stale_events(org.jenkinsci.plugins.ssegateway.EventHistoryStoreTest)
 Run 1: EventHistoryStoreTest.test_delete_stale_events:69
 Run 2: EventHistoryStoreTest.test_delete_stale_events:69
 Run 3: EventHistoryStoreTest.test_delete_stale_events:69
 Run 4: EventHistoryStoreTest.test_delete_stale_events:69
 Run 5: EventHistoryStoreTest.test_delete_stale_events:69

Tests run: 12, Failures: 2, Errors: 0, Skipped: 0
...
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project sse-gateway: There are test failures.
...
 

      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
  

[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-51057  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM   
 

  
 
 
 
 

 
 There are a lot of changes/improvements in sse-gateway (mostly by R. Tyler Croy) since 1.15 was released (back in Jan 16th, 2017). In the logs, I see a commit titled message leaks which sounds interesting. I tried compiling the master branch and I get errors: 

 
$ docker run --rm -it -v maven-repo:/root/.m2 -v $PWD:/src:rw -w /src maven:3-jdk-8-alpine mvn verify 
...
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.0:npm (npm install) on project sse-gateway: Failed to run task: 'npm install' failed. java.io.IOException: Cannot run program "/src/node/node" (in directory "/src"): error=2, No such file or directory -> [Help 1]
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51097) Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 github-plugin  
 
 
Component/s: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-51057  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM   
 

  
 
 
 
 

 
 And now its at: 
 

 
 
Class 
 Size (Kb) 
 % size 
 Instances 
 % instances 
 Source 
 
 
org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry 
105,174 
3 
3,365,570 
4 
  
 
 
java.util.concurrent.ConcurrentLinkedQueue$Node 
79,051 
2 
3,372,854 
4 
  
 

 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-51112) Custom WAR Packager - CLI Tool should support installing WAR to the local repository

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-51112  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51114) Plugins installation Error

[abhishek.d.choudh...@accenture.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhishek Choudhary created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51114  
 
 
  Plugins installation Error   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Suresh Kumar  
 
 
Components: 
 all-changes-plugin  
 
 
Created: 
 2018-05-03 16:30  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Abhishek Choudhary  
 

  
 
 
 
 

 
 java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 400" at sun.net.www.protocol.http.HttpURLConnection.doTunneling(Unknown Source) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source) at hudson.model.DownloadService.loadJSON(DownloadService.java:167) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:190) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1640) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:186) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at 

[JIRA] (JENKINS-51113) Add server middleware to normalize redundant slashes in requests

[ty...@monkeypox.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51113  
 
 
  Add server middleware to normalize redundant slashes in requests   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 R. Tyler Croy  
 
 
Components: 
 essentials  
 
 
Created: 
 2018-05-03 16:26  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 

[JIRA] (JENKINS-51112) Custom WAR Packager - CLI Tool should support installing WAR to the local repository

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51112  
 
 
  Custom WAR Packager - CLI Tool should support installing WAR to the local repository   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 custom-war-packager  
 
 
Created: 
 2018-05-03 16:21  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Maven Plugin supports it OOTB, but for Pipeline Library we would rather use a CLI tool instead of a Maven Wrapper (to simplify repositories)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian 

[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-51057  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM   
 

  
 
 
 
 

 
 In our logs, we're see messages like: 

 
May 02, 2018 1:04:41 PM WARNING org.jenkinsci.plugins.ssegateway.sse.EventDispatcher unsubscribe
Invalid SSE unsubscribe configuration. No active subscription matching filter: 
May 02, 2018 1:04:41 PM WARNING org.jenkinsci.plugins.ssegateway.sse.EventDispatcher unsubscribe
Invalid SSE unsubscribe configuration. No active subscription matching filter: 
May 02, 2018 1:04:41 PM WARNING org.jenkinsci.plugins.ssegateway.sse.EventDispatcher unsubscribe
Invalid SSE unsubscribe configuration. No active subscription matching filter: 
May 02, 2018 1:04:41 PM WARNING org.jenkinsci.plugins.ssegateway.sse.EventDispatcher unsubscribe
Invalid SSE unsubscribe configuration. No active subscription matching filter:  

 Could that be related?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51080) Custom WAR Packager - Support of Incremental releases (JEP-305)

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51080  
 
 
  Custom WAR Packager - Support of Incremental releases (JEP-305)   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 essentials  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje edited a comment on  JENKINS-51057  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM   
 

  
 
 
 
 

 
 Our Jenkins server has been up 23 hours and we're already seeing large numbers of the EventDispacher objects: || Class|| Size (Kb)|| % size|| Instances|| % instances|| Source|||[ int[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=int]|1,056,446|26|868,075|1| ||[char[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=char]|447,243|11|2,837,232|4| ||[java.lang.Object[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.lang.Object]|250,560|6|4,813,216|7| ||[java.lang.StackTraceElement|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.lang.StackTraceElement]|239,176|6|7,653,653|11| ||[byte[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=byte]|165,917|4|581,581|0| ||[java.lang.String|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.lang.String]|146,722|3|6,260,161|9| ||[ org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry]|96,964|2|3,102,853|4| ||[java.util.concurrent.ConcurrentLinkedQueue$Node|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.util.concurrent.ConcurrentLinkedQueue$Node]|73,163|1|3,121,633|4| | It isn't a problem (yet) but this is alarming. Our other, Jenkins server has no references to {{EventDispatcher$Retry}} in the memory histogram, even when expanding details.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are 

[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-51057  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM   
 

  
 
 
 
 

 
 Our Jenkins server has been up 23 hours and we're already seeing large numbers of the EventDispacher objects:   
 

 
 
 Class 
 Size (Kb) 
 % size 
 Instances 
 % instances 
 Source 
 
 
[int[] 
https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=int] 
1,056,446 
26 
868,075 
1 
  
 
 
[char[] 
https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=char] 
447,243 
11 
2,837,232 
4 
  
 
 
[java.lang.Object[] 
https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.lang.Object] 
250,560 
6 
4,813,216 
7 
  
 
 
java.lang.StackTraceElement 
239,176 
6 

[JIRA] (JENKINS-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab

[roger.woo...@outlook.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Wooley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-5  
 
 
  Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab   
 

  
 
 
 
 

 
Change By: 
 Roger Wooley  
 

  
 
 
 
 

 
 Steps to reproduce using two jobs:  #  *  First job: triggers the second job (wait = true)  #  *  Second job: record unit tests  #  *  Open Blue Ocean from the first job, click Triggered Builds to access the second job  #  *  The Tests tab will say no results are recorded  #  *  Exit Blue Ocean, and access it again from the second job  #  *  The Tests tab will show resultsI noticed this happening both while the job was running and complete.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab

[roger.woo...@outlook.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Wooley created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-5  
 
 
  Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 01_Job1.png, 02_Job2.png, 03_Job2_Tests_Via_Job1.png, 04_Job2_Direct.png, 05_Job2_Tests.png, 06_Job2_Tests.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-05-03 15:39  
 
 
Environment: 
 Jenkins 2.117  Blue Ocean 1.5  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roger Wooley  
 

  
 
 
 
 

 
 Steps to reproduce using two jobs: 
 
First job: triggers the second job (wait = true) 
Second job: record unit tests 
Open Blue Ocean from the first job, click Triggered Builds to access the second job 
The Tests tab will say no results are recorded 
Exit Blue Ocean, and access it again from the second job 
The Tests tab will show results 
 I noticed this happening both while the job was running and complete.  
 

  
 
 

[JIRA] (JENKINS-50997) java.lang.UnsupportedOperationException in set map with each

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-50997  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.UnsupportedOperationException in set map with each   
 

  
 
 
 
 

 
 This is due to IteratorHack in workflow-cps, which is how we're able to do iteration over map entries without serialization errors. You'll need to work around this - say, with something like: 

 

Map buildStatus = ['a':'C', 'b':'N', 'c':'R', 'd':'R']
List nextBuildBranches = ['c', 'd']

nextBuildBranches.each { b ->
  buildStatus.put(b, "C")
}
println buildStatus
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50997) java.lang.UnsupportedOperationException in set map with each

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50997  
 
 
  java.lang.UnsupportedOperationException in set map with each   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47498) Select compatible plugin versions using a BOM

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-47498  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Select compatible plugin versions using a BOM   
 

  
 
 
 
 

 
 Added to JENKINS-50686 since we might be able to use JENKINS-50953 to update the contents of the BOM.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-34414) Code that raises groovy.lang.MissingMethodException will prevent parallel from finishing

[svano...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-34414  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Code that raises groovy.lang.MissingMethodException will prevent parallel from finishing   
 

  
 
 
 
 

 
 Probably the exception triggers a CPS VM-level error that forces the Flow to end – not sure how viable that is?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50997) java.lang.UnsupportedOperationException in set map with each

[svano...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50997  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.UnsupportedOperationException in set map with each   
 

  
 
 
 
 

 
 Andrew Bayer any notions?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51003) Allow non-administrators to use "Query and Trigger Gerrit Patches"

[matt...@unsolvable.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Webber updated  JENKINS-51003  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51003  
 
 
  Allow non-administrators to use "Query and Trigger Gerrit Patches"   
 

  
 
 
 
 

 
Change By: 
 Matthew Webber  
 
 
Status: 
 Closed In Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51003) Allow non-administrators to use "Query and Trigger Gerrit Patches"

[matt...@unsolvable.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Webber updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51003  
 
 
  Allow non-administrators to use "Query and Trigger Gerrit Patches"   
 

  
 
 
 
 

 
Change By: 
 Matthew Webber  
 
 
Attachment: 
 Manual_Trigger.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51003) Allow non-administrators to use "Query and Trigger Gerrit Patches"

[matt...@unsolvable.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Webber commented on  JENKINS-51003  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow non-administrators to use "Query and Trigger Gerrit Patches"   
 

  
 
 
 
 

 
 

You can give the manual trigger permission to anyone.
 I'm using the Role Strategy plugin, which may be the problem here. The "Manual Trigger" privilege certainly appears as an available option. The attached screenshot shows that I have granted access to all authenticated users. Unfortunately, even with this only administrators can see the option. Is this a problem with Role Strategy, or with the way the Gerrit Trigger plugin does things? Thanks    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51110) no test results visible in blueocean when following link from classic -> BO

[j...@hoblitt.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Hoblitt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51110  
 
 
  no test results visible in blueocean when following link from classic -> BO   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 blueocean-to-classic-to-blueocean-losses-tests-results.webm  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-05-03 15:06  
 
 
Environment: 
 core 2.89.4 LTS  blueocean 1.5.0 (final release)  
 
 
Labels: 
 blueocean junit  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joshua Hoblitt  
 

  
 
 
 
 

 
 When exiting from a BO build view with junit test results (failures or all successful) to the classic UI, then following the link from the classic UI -> BO, the test results disappear.  I noticed this after upgrading from BO 1.5.0-beta-2 -> 1.5.0 but I have not tested prior versions to see when this behavior started.  
 

  
 
 
 
 

 
 
 

 

[JIRA] (JENKINS-51091) Make test results available on currentBuild

[svano...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-51091  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make test results available on currentBuild   
 

  
 
 
 
 

 
 Red flag for me: if we do off-master, this one would add some nontrivial extra complexity to that implementation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information

[svano...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Resolved with the final 2.51 release of workflow-cps.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50888  
 
 
  NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 Reopened Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information

[svano...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50888  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information   
 

  
 
 
 
 

 
 PR link with the final fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50888  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information   
 

  
 
 
 
 

 
 Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java src/test/java/org/jenkinsci/plugins/workflow/cps/PersistenceProblemsTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/9a27f3070805ce189f18ed640bf30cdd8cc07cc7 Log: Fix and test for JENKINS-50888 by supporting serialization of execution before onLoad was called  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50888  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information   
 

  
 
 
 
 

 
 Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java src/test/java/org/jenkinsci/plugins/workflow/cps/PersistenceProblemsTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/54424895869f36d6c7377e167c5c1fa4ca959dc0 Log: Merge pull request #224 from svanoort/fix-final-lazy-load-issue-JENKINS-50888 Fix and test for JENKINS-50888 by supporting serialization of execution before onLoad was called Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/bdab2e1011b0...54424895869f *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin

[rarabaol...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza edited a comment on  JENKINS-51008  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Complete the PCT flow started in JENKINS-50540 for git plugin   
 

  
 
 
 
 

 
 [~oleg_nenashev]  No,  With this and  JENKINS-50953 is enough IMO  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin

[rarabaol...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza commented on  JENKINS-51008  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Complete the PCT flow started in JENKINS-50540 for git plugin   
 

  
 
 
 
 

 
 Oleg Nenashev No, JENKINS-50953 is enough IMO  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50953) Tool to offer incremental updates

[rarabaol...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza commented on  JENKINS-50953  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Tool to offer incremental updates   
 

  
 
 
 
 

 
 With this tool in place allowing to update the incrementals versions easily, I agree to use CWP to implement the missing parts in JENKINS-51008 as there would be a deterministic way to get the proper versions to use to test  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51108) Allow incrementals releases in Remoting

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51108  
 
 
  Allow incrementals releases in Remoting   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Jeff Thompson  
 
 
Components: 
 remoting  
 
 
Created: 
 2018-05-03 14:25  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins 

[JIRA] (JENKINS-51109) Allow incremental releases in Stapler

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51109  
 
 
  Allow incremental releases in Stapler   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-05-03 14:26  
 
 
Labels: 
 stapler  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
  

[JIRA] (JENKINS-51109) Allow incremental releases in Stapler

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51109  
 
 
  Allow incremental releases in Stapler   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51094) Custom WAR Packager - Support building with LATEST versions from Incrementals repo

[rarabaol...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza commented on  JENKINS-51094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Custom WAR Packager - Support building with LATEST versions from Incrementals repo   
 

  
 
 
 
 

 
 IMO this is not blocking JENKINS-51008 as long as JENKINS-50953 is done   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48933) Unstoppable Multibranch Pipeline Scan

[kevin.lan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Lannen edited a comment on  JENKINS-48933  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unstoppable Multibranch Pipeline Scan   
 

  
 
 
 
 

 
 ++ We have used both JGit and the cli git and both have this issue. We would prefer to use cli git as it seems to be more reliable in other areas but it seemed to hang more during branch indexing then JGit does.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48933) Unstoppable Multibranch Pipeline Scan

[kevin.lan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Lannen commented on  JENKINS-48933  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unstoppable Multibranch Pipeline Scan   
 

  
 
 
 
 

 
 ++We have used both JGit and the cli git and both have this issue. We would prefer to use cli git as it seems to be more reliable in other areas but it seemed to hang more during branch indexing then JGit does.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50692) Allow incrementals deployment from core

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50692  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow incrementals deployment from core   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: .gitignore .mvn/extensions.xml .mvn/maven.config Jenkinsfile cli/pom.xml core/pom.xml pom.xml test/pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/3fb17fb0bbb824a6c929af3809022c280cb6270a Log: JENKINS-50692 INFRA-1571 #3394: JEP-305 Incrementals in core  *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50692) Allow incrementals deployment from core

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-50692  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Merged toward 2.120.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50692  
 
 
  Allow incrementals deployment from core   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50408) Highlight difficult to see after clicking on stage

[cber...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chad Bercea commented on  JENKINS-50408  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Highlight difficult to see after clicking on stage   
 

  
 
 
 
 

 
 Nicolae Pascu I am in favor of using the blue we are deploying in the system in a 2px stroke or border, roughly 2px larger than the object "selected" giving a little space. I tried red and orange but it ended up looking like an error and yellow was too low contrast. Blue feels safe and having the line not touch the object creates a visual break. I anticipate this being enough of a touch to show a "selected state" while also not distracting the user from their work.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information

[svano...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50888  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information   
 

  
 
 
 
 

 
 Reinhold Füreder Tom Ghyselinck Reproduced this – having eliminated all the other possibilities made it quick. This enables what should be the final fix, which enables serializing even if the execution was never loaded.  Please try the attached SNAPSHOT – it should be released to the update center soon but that will take a few hours to be publicly available. workflow-cps.hpi   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information

[svano...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50888  
 
 
  NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Attachment: 
 workflow-cps.hpi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50408) Highlight difficult to see after clicking on stage

[cber...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chad Bercea updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50408  
 
 
  Highlight difficult to see after clicking on stage   
 

  
 
 
 
 

 
Change By: 
 Chad Bercea  
 
 
Attachment: 
 Screen Shot 2018-05-03 at 9.49.49 AM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50080) Integration Test for Remote API

[ullrich.haf...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-50080  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Integration Test for Remote API   
 

  
 
 
 
 

 
 Vielleicht können Sie die Methode aus unserer UI Test Suite integrieren.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50434) Misbehaviour of feature: Pin the workspace to the build host

[kwi...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth commented on  JENKINS-50434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Misbehaviour of feature: Pin the workspace to the build host   
 

  
 
 
 
 

 
 Proving very difficult to fix. The concept of a job having different workspaces is alien to Jenkins so the correct information is currently not (and unlikely to ever be) provided to P4Jenkins to clean up properly.   For now we are going to have to recommend that pin at build host is no longer used and {NODE_NAME} is used in workspace name instead.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47427) Poll per change with pipeline jobs

[kwi...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47427  
 
 
  Poll per change with pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Labels: 
 P4_A  P4_SUPPORT  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47427) Poll per change with pipeline jobs

[kwi...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Original fix was released but reports that fix does not build correctly. We are investigating.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47427  
 
 
  Poll per change with pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50434) Misbehaviour of feature: Pin the workspace to the build host

[wb...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 W Basu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50434  
 
 
  Misbehaviour of feature: Pin the workspace to the build host   
 

  
 
 
 
 

 
Change By: 
 W Basu  
 
 
Labels: 
 P4_A P4_B  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51091) Make test results available on currentBuild

[zeratul...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean MacKay commented on  JENKINS-51091  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make test results available on currentBuild   
 

  
 
 
 
 

 
 Interesting, so do none of the test results pages in normal or Blue Ocean UI function without the junit plugin? Or is the way the data is eventually saved into the finished build just even harder to access? I assumed the workaround with AbstractTestResultAction pulled the results from the same final location which both nunit and junit post to, but I haven't tested to confirm so I'm not sure. And that's interesting. I assume you could use it in a scripting pipeline like this. Does the same work in Declarative pipeline? 

 

def results = junit '*.xml';
sh "echo ${results.getFailCount()}"
 

 Unfortunately the `nunit` plugin doesn't seem to behave the same way (I use both). Yet it still posts the results to the same final place, so those results should still be available from one location regardless of which plugin posts there. That's why I assumed there would be a way to read them, but I don't know enough about the architecture in place to really be sure of anything. I'll do some testing and see if I can at least confirm what the behaviour of each approach is.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-44706) Tracking of P4 Credentials is slowing down REST API queries

[wb...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 W Basu closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released in 1.8.10  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-44706  
 
 
  Tracking of P4 Credentials is slowing down REST API queries   
 

  
 
 
 
 

 
Change By: 
 W Basu  
 
 
Status: 
 Resolved Closed  
 
 
Assignee: 
 Paul Allen  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49474) Hash the Perforce ticket when saving it in the Credentials.xml

[wb...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 W Basu closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released in 1.8.10  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49474  
 
 
  Hash the Perforce ticket when saving it in the Credentials.xml   
 

  
 
 
 
 

 
Change By: 
 W Basu  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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