[JIRA] (JENKINS-54982) Using Java8 Streams evaluates whole expression to Boolean

2018-12-18 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey assigned an issue to Andrew Bayer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54982  
 
 
  Using Java8 Streams evaluates whole _expression_ to Boolean   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Assignee: 
 Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-52011) workflow-cps: Illegal reflective access to java.io.ObjectStreamClass when cleaning up object streams

2018-12-18 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52011  
 
 
  workflow-cps: Illegal reflective access to java.io.ObjectStreamClass when cleaning up object streams   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Assignee: 
 Sam Van Oort  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54982) Using Java8 Streams evaluates whole expression to Boolean

2018-12-18 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54982  
 
 
  Using Java8 Streams evaluates whole _expression_ to Boolean   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 pipeline  pipeline-triaged  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54998) Stash and archive should resolve symlinks

2018-12-18 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54998  
 
 
  Stash and archive should resolve symlinks   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 archive pipeline  pipeline-triaged  stash  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55235) demo1

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please do not use Jenkins Jira for the demos, it is a production Jira for Jenkins users  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55235  
 
 
  demo1   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-43814) Password parameters should be hidden in pipeline logs by default

2018-12-18 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-43814  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Password parameters should be hidden in pipeline logs by default   
 

  
 
 
 
 

 
 HOSTING-679 claims to implement something like this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55236  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0   
 

  
 
 
 
 

 
 Please provide a full configugation XML for the plugin after the change  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs

2018-12-18 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55024  
 
 
  Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 pipeline  pipeline-triaged  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

2018-12-18 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54929  
 
 
  Some final output is missing in Jenkins Pipeline when using the Ansible Plugin   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 ansible ansible-plugin jenkins pipeline  pipeline-triaged  playbook  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-51998) Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller

2018-12-18 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51998  
 
 
  Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 java10_hackathon java11  pipeline-triaged  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-18 Thread david.aldr...@emea.nec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Aldrich commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 Hopefully this is what you wanted: 

 

# cat /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/*.xml | grep fileName
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/NemeSys/LTE/RRM/../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h
  "../../issue[2]/fileName"/>
  "../../issue[2]/fileName"/>
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/BitTrue/StarAltTurboDecoder.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/BitTrue/StarAltTurboDecoder.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/Alterautil.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarAltTurboDecoder.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarAltTurboDecoder.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  

[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-18 Thread david.aldr...@emea.nec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Aldrich commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 Hopefully this is what you wanted: 

 

# cat /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/*.xml | grep fileName
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/NemeSys/LTE/RRM/../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h
  "../../issue[2]/fileName"/>
  "../../issue[2]/fileName"/>
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/BitTrue/StarAltTurboDecoder.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/BitTrue/StarAltTurboDecoder.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/Alterautil.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarAltTurboDecoder.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarAltTurboDecoder.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h
  

[JIRA] (JENKINS-55185) Jenkinsfile pipeline job no longer creating an IPA

2018-12-18 Thread hazmeis...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Harry King closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 buildIpa: true is now required.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55185  
 
 
  Jenkinsfile pipeline job no longer creating an IPA   
 

  
 
 
 
 

 
Change By: 
 Harry King  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55185) Jenkinsfile pipeline job no longer creating an IPA

2018-12-18 Thread hazmeis...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Harry King commented on  JENKINS-55185  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkinsfile pipeline job no longer creating an IPA   
 

  
 
 
 
 

 
 Brill, that seems to have been the property I was missing. Thanks for the help!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-41813) bitbucket branch source folder no longer can have views

2018-12-18 Thread ja...@howeswho.co.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Howe commented on  JENKINS-41813  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: bitbucket branch source folder no longer can have views   
 

  
 
 
 
 

 
 There's no way to customise the columns in the folders then? You have to recreate the whole structure manually with views instead?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55242) AzureVMCloud: createProvisionedAgent: Deployment failed with timeout

2018-12-18 Thread faiz...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Muhammad Faizan ul haq created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55242  
 
 
  AzureVMCloud: createProvisionedAgent: Deployment failed with timeout   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-slave-plugin, azure-vm-agents-plugin  
 
 
Created: 
 2018-12-18 14:33  
 
 
Environment: 
 Jenkins: 2.138.1  Azure-Vm-Agents (Plugin) 0.7.5   Region: Nort Europe  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Muhammad Faizan ul haq  
 

  
 
 
 
 

 
 There are lot of failures happened today on multiple different occassions. The deployment, which was smooth previously, is now failing with the following error: com.microsoft.azure.vmagent.exceptions.AzureCloudException: AzureVMCloud: createProvisionedAgent: Deployment wautoscalingconfig1-1218120554742 failed, max timeout reached (1200 seconds) {{ at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:37)}} {{ at com.microsoft.azure.vmagent.AzureVMCloud.createProvisionedAgent(AzureVMCloud.java:630)}} {{ at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:843)}} {{ at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:821)}} {{ at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)}} {{ at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)}} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266)}} {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}} {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}} {{ at java.lang.Thread.run(Thread.java:748)}}     It has worked in between though. Has there been something change today !!      
 

 

[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-18 Thread david.aldr...@emea.nec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Aldrich commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 Regarding the second part of your question, there are 8 files in files-with-issues (2 mentioned twice): StarLibs\Camelot\ScBitTrue\AlterafpCompiler.cpp StarLibs\Camelot\ScBitTrue\AlteraDspBuilderFFT\csl\stimulus_file.h StarLibs\Camelot\ScBitTrue\AlterafpCompiler.cpp StarLibs\Camelot\ScBitTrue\AlteraDspBuilderFFT\csl\post_steps.h StarLibs\Camelot\ScBitTrue\StarUlPhyRxCommonCamelot.h StarLibs\Camelot\ScBitTrue\Alterautil.cpp StarLibs\Camelot\ScBitTrue\AlteraDspBuilderFFT\csl\stimulus_file.h StarLibs\Camelot\ScBitTrue\StarAltTurboDecoder.cpp Can you explain further what I need to do for the first part of your request?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished

2018-12-18 Thread cmamigon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Camden Mamigonian commented on  JENKINS-53816  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [Blue Ocean] Completed stages appear to be skipped instead of finished   
 

  
 
 
 
 

 
 Olivier Lamy is there a plan to get this worked?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54700) Findbugs SAXParser not found

2018-12-18 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-54700  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Findbugs SAXParser not found   
 

  
 
 
 
 

 
 Hmm, that is strange. I hoped that something else would show up. That message means that the JDK default SAX parser is used and not the Xerces bundled library. But maybe the message changes later on if another tool changes the property.  Is anyone else getting such messages?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55220) Multibranch Pipeline jobs get randomly lost

2018-12-18 Thread jenk...@cornr.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonas Büth commented on  JENKINS-55220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
 Thank you so much!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-18 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 Ok, let us check again to find the problem.  
 
Resolving absolute file names for all issues -> affected files for all issues already have absolute paths (resolving real path only)
 Seems that all files have an absolute path. This looks fine! 
 
Copying affected files to Jenkins' build folder /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/14 -> 5 copied, 0 not in workspace, 6 not-found, 0 with I/O error
 Here we have a problem: 6 Files have not been found. Here we need to investigate what the problem is.  Can you please cat again in the build folder the xml of warnings plugin and grep for filename so we see all actual filenames? And then open manually in the subfolder files-with-issues/ of a build the 6 files *.tmp and see which files have been resolved. Then we can make a mapping of which files have been resolved and which ones not. Maybe we can see a pattern for the broken files...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54700) Findbugs SAXParser not found

2018-12-18 Thread christian.asselme...@faktorzehn.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Asselmeyer commented on  JENKINS-54700  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Findbugs SAXParser not found   
 

  
 
 
 
 

 
 I updated to 1.0.0-beta8 and now the agent log shows these messages: 

 
Dec 18, 2018 1:35:07 PM edu.hm.hafner.analysis.parser.FindBugsParser logSaxProperties
WARNING: Default SAX parser will be used to parse FindBugs/SpotBugs file.
Dec 18, 2018 1:35:10 PM edu.hm.hafner.analysis.parser.FindBugsParser logSaxProperties
WARNING: Default SAX parser will be used to parse FindBugs/SpotBugs file.
Dec 18, 2018 1:35:10 PM edu.hm.hafner.analysis.parser.FindBugsParser logSaxProperties
WARNING: Default SAX parser will be used to parse FindBugs/SpotBugs file.
Dec 18, 2018 1:35:10 PM edu.hm.hafner.analysis.parser.FindBugsParser logSaxProperties
WARNING: Default SAX parser will be used to parse FindBugs/SpotBugs file.
... 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54767) Global variables are overriding local variables

2018-12-18 Thread fhajred...@luxoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 fisnik hajredini commented on  JENKINS-54767  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Global variables are overriding local variables   
 

  
 
 
 
 

 
 Jan Bottek Thanks for you reply. We are currently following a different approach to fixing this, because of some other issues the pipeline job might cause. We decided to include the variables in the Jenkinsfile script as a temporary approach until this issue is resolved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55241) sshagent + sshCommand: connector is not available

2018-12-18 Thread sebastian.ben...@t-systems.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastian Benner created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55241  
 
 
  sshagent + sshCommand: connector is not available   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Naresh Rayapati  
 
 
Components: 
 ssh-steps-plugin  
 
 
Created: 
 2018-12-18 12:53  
 
 
Environment: 
 SSH Agent Plugin 1.17  SSH Pipeline Steps 1.1.1  Jenkins 2.121.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Sebastian Benner  
 

  
 
 
 
 

 
 Even though SSH_AGENT_SOCK is available as environment variable, it is not used by sshCommand Pipline script [...] sshagent (credentials: ['abn']) { sh "env|grep SSH_AUTH_SOCK"  script  { def remote = [:] remote.name = 'abn' remote.user = 'user' remote.allowAnyHosts = true remote.agent = true remote.host = 'testserver' sshCommand remote: remote, command: "id" } }   Log output SSH_AUTH_SOCK=/tmp/ssh-0echbSIofhgV/agent.1971 com.jcraft.jsch.agentproxy.AgentProxyException: connector is not available:  at com.jcraft.jsch.agentproxy.ConnectorFactory.createConnector(ConnectorFactory.java:120) at com.jcraft.jsch.agentproxy.ConnectorFactory$createConnector.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117) at org.hidetake.groovy.ssh.connection.UserAuthentication$RemoteIdentityRepositoryLocator.get(UserAuthentication.groovy:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at 

[JIRA] (JENKINS-55240) Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55240  
 
 
  Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 jenkins-test-harness  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55240) Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons

2018-12-18 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55240  
 
 
  Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-12-18 12:33  
 
 
Labels: 
 JEP-200  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Carlos Sanchez  
 

  
 
 
 
 

 
 https://ci.jenkins.io/job/Plugins/job/kubernetes-plugin/job/PR-409/1/testReport/org.csanchez.jenkins.plugins.kubernetes/KubernetesSlaveTest/windows_8___Archive__windows_8testGetPodRetention/ Discussion in https://github.com/jenkinsci/kubernetes-plugin/pull/409 

 

java.lang.RuntimeException: java.io.IOException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#clouds for class hudson.model.Hudson
	at hudson.util.PersistedList._onModified(PersistedList.java:183)
	at hudson.util.PersistedList.add(PersistedList.java:72)
	at org.csanchez.jenkins.plugins.kubernetes.KubernetesSlaveTest.testGetPodRetention(KubernetesSlaveTest.java:93)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at 

[JIRA] (JENKINS-55239) FilesystemSCM is not annotated properly in JFR

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55239  
 
 
  FilesystemSCM is not annotated properly in JFR   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 [https://github.com/jenkinsci/jenkinsfile-runner/blob/master/payload/src/main/java/io/jenkins/jenkinsfile/runner/FileSystemSCM.java]  {noformat}org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class java.lang.String{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55239) FilesystemSCM is not annotated properly in JFR

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55239  
 
 
  FilesystemSCM is not annotated properly in JFR   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Summary: 
 FilesystemSCM is not annotated properly  in JFR  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55239) FilesystemSCM is not annotated properly

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55239  
 
 
  FilesystemSCM is not annotated properly   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 jenkinsfile-runner  
 
 
Created: 
 2018-12-18 12:02  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55238) Jenkins will discard subsequent request when Gitlab sends request concurrently.

2018-12-18 Thread 1498472...@qq.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Xu hui created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55238  
 
 
  Jenkins will discard subsequent request when Gitlab sends request concurrently.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-12-18 11:54  
 
 
Environment: 
 jenkins version: 2.138.3  plugins: envinject:2.1.6, GitLab Plugin 1.5.11  os: CentOS Linux release 7.2.1511 (Core)  java version: OpenJDK 1.8.0_161  How you installed Jenkins: rpm  Whether Jenkins is accessed through a reverse proxy: No  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Xu hui  
 

  
 
 
 
 

 
 Hi, all: I have a Jenkins pipeline project using Gitlab plugin, and I use Gitlab's webhook to trigger his build. Recently, I found that when I tried to trigger the build concurrently, the first arrival request will be processed. But during the pending state that the first arrived job in, Jenkins would discard the subsequent Gitlab request. I don't have any current limiting and concurrency control on my Jenkins project.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

[JIRA] (JENKINS-54353) Jenkinsfile Runner: Replace the JUnit implementation but something production-focused

2018-12-18 Thread fjfernan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández assigned an issue to Francisco Fernández  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54353  
 
 
  Jenkinsfile Runner: Replace the JUnit implementation but something production-focused   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54353) Jenkinsfile Runner: Replace the JUnit implementation but something production-focused

2018-12-18 Thread fjfernan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández started work on  JENKINS-54353  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Francisco Fernández  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54375) Setup a release flow for Jenkinsfile Runner

2018-12-18 Thread m.vilaci...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Isa Vilacides edited a comment on  JENKINS-54375  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Setup a release flow for Jenkinsfile Runner   
 

  
 
 
 
 

 
 Ensure Missing test: ensure  that class loading happens from the bundle of Jenkins core and not from the version that Jenkinsfile runner provides  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54375) Setup a release flow for Jenkinsfile Runner

2018-12-18 Thread m.vilaci...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Isa Vilacides commented on  JENKINS-54375  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Setup a release flow for Jenkinsfile Runner   
 

  
 
 
 
 

 
 Ensure that class loading happens from the bundle of Jenkins core and not from the version that Jenkinsfile runner provides  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54452) Allow a user to install their own set of plugins

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54452  
 
 
  Allow a user to install their own set of plugins   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 jenkinsfile-runner  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54452) Allow a user to install their own set of plugins

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54452  
 
 
  Allow a user to install their own set of plugins   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 custom-war-packager  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54452) Allow a user to install their own set of plugins

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54452  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow a user to install their own set of plugins   
 

  
 
 
 
 

 
 Notes from the discussion: 
 
It would be nice to have a basic list of plugins, which can be extended by the user 
There is a base configuration in a single repository, and a separate user configuration stored by the user somewhere 
It is not clear how it has to be defined, e.g. in https://github.com/jenkins-x/jenkins-x-serverless  
In the Jenkins X side it could be a build pack. It defines a base configuration and other common stuff so that Jenkins X users follow the JX flow to deliver their images 
 What is requested: 
 
It is possible to define multiple plugin sources in Custom WAR Packager 
Users can override versions defined in the base version. In such case CWP should show warnings 
Nice2Have: detect incompatible plugins somehow 
 How it could be implemented? 
 
Custom WAR Packager YAML is updated to support multiple source inputs 
There is a plugin list merge logic in https://github.com/jenkinsci/custom-war-packager/blob/master/custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/impl/Builder.java#L82-L97  
There is a demo demonstrating the behavior 
There is some documentation for it 
    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

  

[JIRA] (JENKINS-55237) Broken link when trying to open UFT report from Octane

2018-12-18 Thread radislav.berkov...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55237  
 
 
   Broken link when trying to open UFT report from Octane   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Labels: 
 5.6-beta1 5.7 Octane  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55232) regarding Authentication response is not success message

2018-12-18 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo edited a comment on  JENKINS-55232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: regarding Authentication response is not success message   
 

  
 
 
 
 

 
 The first exception is not related to SAML, it seems something in the K8s plugin{code}org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$SaveableListenerImpl.onChange(KubernetesClientProvider.java:164) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at jenkins.model.Jenkins.save(Jenkins.java:3242) at hudson.BulkChange.commit(BulkChange.java:98) at hudson.security.GlobalSecurityConfiguration.doConfigure(GlobalSecurityConfiguration.java:106) at {code}Check your configuration seem is not correct, Jenkins Jira is not a support site [How to report an issue|https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription][Configure Guide|https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md ) ]   [Troubleshooting Guide ](  | https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md]{code}2018 3:05:48 AM org.jenkinsci.plugins.saml.SamlSecurityRealm doFinishLoginWARNING: Unable to validate the SAML Response: Authentication response is not success ; actual urn:oasis:names:tc:SAML:2.0:status:Responder; nested exception is org.pac4j.saml.exceptions.SAMLException: Authentication response is not success ; actual urn:oasis:names:tc:SAML:2.0:status:ResponderFor more info check 'Maximum Authentication Lifetime' at https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md#configuring-plugin-settingsIf you have issues check the troubleshoting guide at https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55237) Broken link when trying to open UFT report from Octane

2018-12-18 Thread radislav.berkov...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55237  
 
 
   Broken link when trying to open UFT report from Octane   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55237) Broken link when trying to open UFT report from Octane

2018-12-18 Thread radislav.berkov...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55237  
 
 
   Broken link when trying to open UFT report from Octane   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Radi Berkovich  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-12-18 10:58  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Radi Berkovich  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55232) regarding Authentication response is not success message

2018-12-18 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo edited a comment on  JENKINS-55232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: regarding Authentication response is not success message   
 

  
 
 
 
 

 
 The first exception is not related to SAML, it seems something in the K8s plugin{code}org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$SaveableListenerImpl.onChange(KubernetesClientProvider.java:164) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at jenkins.model.Jenkins.save(Jenkins.java:3242) at hudson.BulkChange.commit(BulkChange.java:98) at hudson.security.GlobalSecurityConfiguration.doConfigure(GlobalSecurityConfiguration.java:106) at {code}Check your configuration seem is not correct, Jenkins Jira is not a support site [How to report an issue ]( | https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription ) ] [Configure Guide ]( | https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md)[Troubleshooting Guide](https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md ) ] {code}2018 3:05:48 AM org.jenkinsci.plugins.saml.SamlSecurityRealm doFinishLoginWARNING: Unable to validate the SAML Response: Authentication response is not success ; actual urn:oasis:names:tc:SAML:2.0:status:Responder; nested exception is org.pac4j.saml.exceptions.SAMLException: Authentication response is not success ; actual urn:oasis:names:tc:SAML:2.0:status:ResponderFor more info check 'Maximum Authentication Lifetime' at https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md#configuring-plugin-settingsIf you have issues check the troubleshoting guide at https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55232) regarding Authentication response is not success message

2018-12-18 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55232  
 
 
  regarding Authentication response is not success message   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55232) regarding Authentication response is not success message

2018-12-18 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo edited a comment on  JENKINS-55232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: regarding Authentication response is not success message   
 

  
 
 
 
 

 
 The first exception is not related to SAML, it seems something in the K8s plugin ``` {code} org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$SaveableListenerImpl.onChange(KubernetesClientProvider.java:164) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at jenkins.model.Jenkins.save(Jenkins.java:3242) at hudson.BulkChange.commit(BulkChange.java:98) at hudson.security.GlobalSecurityConfiguration.doConfigure(GlobalSecurityConfiguration.java:106) at  ``` {code}  Check your configuration seem is not correct, Jenkins Jira is not a support site [How to report an issue](https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription)[Configure Guide](https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md)[Troubleshooting Guide](https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md){code}2018 3:05:48 AM org.jenkinsci.plugins.saml.SamlSecurityRealm doFinishLoginWARNING: Unable to validate the SAML Response: Authentication response is not success ; actual urn:oasis:names:tc:SAML:2.0:status:Responder; nested exception is org.pac4j.saml.exceptions.SAMLException: Authentication response is not success ; actual urn:oasis:names:tc:SAML:2.0:status:ResponderFor more info check 'Maximum Authentication Lifetime' at https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md#configuring-plugin-settingsIf you have issues check the troubleshoting guide at https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55232) regarding Authentication response is not success message

2018-12-18 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-55232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: regarding Authentication response is not success message   
 

  
 
 
 
 

 
 The first exception is not related to SAML, it seems something in the K8s plugin ``` org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$SaveableListenerImpl.onChange(KubernetesClientProvider.java:164) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at jenkins.model.Jenkins.save(Jenkins.java:3242) at hudson.BulkChange.commit(BulkChange.java:98) at hudson.security.GlobalSecurityConfiguration.doConfigure(GlobalSecurityConfiguration.java:106) at  ```  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54305  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free   
 

  
 
 
 
 

 
 https://github.com/jenkins-infra/crawler/pull/79 removes listing of Java 10 in the tool installer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-51998) Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller

2018-12-18 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51998  
 
 
  Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Labels: 
 java10_hackathon  java11  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0

2018-12-18 Thread harry0...@163.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 harry king created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55236  
 
 
  jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Attachments: 
 1.png, 2.png  
 
 
Components: 
 role-strategy-plugin  
 
 
Created: 
 2018-12-18 10:01  
 
 
Environment: 
 centos7.4 / jenkins-2.138.2 rpm  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 harry king  
 

  
 
 
 
 

 
 I added a project role and a filter with "test-.", after changing the user, all jobs are still there including "test-." and "dev-.*". Seems to be a bug there, could you please take a look?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

[JIRA] (JENKINS-55235) demo1

2018-12-18 Thread shivam.chho...@infosys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 shivam chhouda created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55235  
 
 
  demo1   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Technical Support  
 
 
Components: 
 absint-a3-plugin  
 
 
Created: 
 2018-12-18 09:46  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 shivam chhouda  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55222) JDK Installer certificate expiry

2018-12-18 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Actually an infra issue tracked at INFRA-1944.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55222  
 
 
  JDK Installer certificate expiry   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-49142) Be able to customize checkout as "options" in declarative pipeline

2018-12-18 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada commented on  JENKINS-49142  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Be able to customize checkout as "options" in declarative pipeline   
 

  
 
 
 
 

 
 Hi Leandro Lucarella,  I'm working in this ticket, would you mind to take a look into it? Github  PR: https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/307  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54018) Exception on UI after Manually uploading Plugins

2018-12-18 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams commented on  JENKINS-54018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Exception on UI after Manually uploading Plugins   
 

  
 
 
 
 

 
 OP listed active-choices-plugin. I added ssh-slaves-plugin, as that is the plugin at play, and jdk-tool-plugin as that was reflected in error and adding it made the problem go away.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55233) PowerMock is not compatible with Java 11

2018-12-18 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier edited a comment on  JENKINS-55233  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PowerMock is not compatible with Java 11   
 

  
 
 
 
 

 
 Updating to {{3.30}} is not enough. {{powermock-reflect}} depends on {{ objenesis3 objenesis:3 .0.1}} but the {{parent-pom}} set the version to {{2.0.6}} and the version {{3.0.1}} is blacklisted. It requires more in-depth search.Here is the log of the build with Parent POM {{3.30}} or {{3.31}}:{noformat}[WARNING] Rule 4: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with message:Failed while enforcing RequireUpperBoundDeps. The error(s) are [Require upper bound dependencies error for org.objenesis:objenesis:2.6 paths to dependency are:+-org.jenkins-ci.plugins:email-ext:2.64-SNAPSHOT  +-org.mockito:mockito-core:2.23.4+-org.objenesis:objenesis:2.6and+-org.jenkins-ci.plugins:email-ext:2.64-SNAPSHOT  +-org.powermock:powermock-module-junit4:2.0.0-RC.4+-org.powermock:powermock-module-junit4-common:2.0.0-RC.4  +-org.powermock:powermock-reflect:2.0.0-RC.4+-org.objenesis:objenesis:2.6 (managed) <-- org.objenesis:objenesis:3.0.1]{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55234) Mockito is not compatible with Java 11

2018-12-18 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier started work on  JENKINS-55234  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55234) Mockito is not compatible with Java 11

2018-12-18 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier updated  JENKINS-55234  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55234  
 
 
  Mockito is not compatible with Java 11   
 

  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55185) Jenkinsfile pipeline job no longer creating an IPA

2018-12-18 Thread kazuhid...@linux-powered.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kazuhide Takahashi commented on  JENKINS-55185  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkinsfile pipeline job no longer creating an IPA   
 

  
 
 
 
 

 
 Harry King I'm sorry! In order to generate an IPA file after building the application, ’buildIpa: true’ is required as a parameter of the pipeline script section 'xcodeBuild'. Since the default value of buildIpa is false, IPA files are not output unless this setting is made.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55234) Mockito is not compatible with Java 11

2018-12-18 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55234  
 
 
  Mockito is not compatible with Java 11   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2018-12-18 08:32  
 
 
Environment: 
 Jenkins 2.155  Java 11  PCT  
 
 
Labels: 
 java11 java11-compatibility  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Adrien Lecharpentier  
 

  
 
 
 
 

 
 The version of Mockito used for testing is not compatible with Java 11. Updating the Parent POM to 3.31 should help fix that.  Example of error: 

 
org.mockito.exceptions.base.MockitoException: 

Mockito cannot mock this class: class org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave.

Mockito can only mock non-private & non-final classes.
If you're not sure why you're getting this error, please report to the mailing list.


Java   : 11
JVM vendor name: Oracle Corporation
JVM vendor version : 11+28
JVM name   : Java HotSpot(TM) 64-Bit Server VM
JVM version: 11+28
JVM info   : mixed mode
OS name: Linux
OS version : 4.15.0-39-generic


Underlying exception : java.lang.UnsupportedOperationException: Cannot define class using reflection
	at org.mockito.internal.junit.JUnitRule$1.evaluate(JUnitRule.java:42)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at 

[JIRA] (JENKINS-55233) PowerMock is not compatible with Java 11

2018-12-18 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55233  
 
 
  PowerMock is not compatible with Java 11   
 

  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 
 
Labels: 
 java11 java11- devtools- compatibility  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55233) PowerMock is not compatible with Java 11

2018-12-18 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier commented on  JENKINS-55233  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PowerMock is not compatible with Java 11   
 

  
 
 
 
 

 
 Oleg Nenashev that would be odd but I can try that.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54018) Exception on UI after Manually uploading Plugins

2018-12-18 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-54018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Exception on UI after Manually uploading Plugins   
 

  
 
 
 
 

 
 Gokulendra Panda, among the components you assigned, you added active-choices-plugin, but there is no mention of it in your description, stack trace, or in the issues. Just checking, do you believe this issue is related to active-choices?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55233) PowerMock is not compatible with Java 11

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55233  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PowerMock is not compatible with Java 11   
 

  
 
 
 
 

 
 Adrien Lecharpentier OK, so we need to upgrade the Plugin POM. I didn't catch this issue, but I believe it depends on the dependency declaration order.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55233) PowerMock is not compatible with Java 11

2018-12-18 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier edited a comment on  JENKINS-55233  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PowerMock is not compatible with Java 11   
 

  
 
 
 
 

 
 Updating to {{3.30}} is not enough. {{powermock-reflect}} depends on {{objenesis3.0.1}} but the {{parent-pom}} set the version to {{2.0.6}} and the version {{3.0.1}} is blacklisted. It requires more in-depth search. Here is the log of the build with Parent POM {{3.30}} or {{3.31}}:{noformat}[WARNING] Rule 4: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with message:Failed while enforcing RequireUpperBoundDeps. The error(s) are [Require upper bound dependencies error for org.objenesis:objenesis:2.6 paths to dependency are:+-org.jenkins-ci.plugins:email-ext:2.64-SNAPSHOT  +-org.mockito:mockito-core:2.23.4+-org.objenesis:objenesis:2.6and+-org.jenkins-ci.plugins:email-ext:2.64-SNAPSHOT  +-org.powermock:powermock-module-junit4:2.0.0-RC.4+-org.powermock:powermock-module-junit4-common:2.0.0-RC.4  +-org.powermock:powermock-reflect:2.0.0-RC.4+-org.objenesis:objenesis:2.6 (managed) <-- org.objenesis:objenesis:3.0.1]{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55233) PowerMock is not compatible with Java 11

2018-12-18 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier commented on  JENKINS-55233  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PowerMock is not compatible with Java 11   
 

  
 
 
 
 

 
 Updating to 3.30 is not enough. powermock-reflect depends on objenesis3.0.1 but the parent-pom set the version to 2.0.6 and the version 3.0.1 is blacklisted. It requires more in-depth search.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55233) PowerMock is not compatible with Java 11

2018-12-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55233  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PowerMock is not compatible with Java 11   
 

  
 
 
 
 

 
 For the record, it's better to pick up 3.31 with the "hpi:run" fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-55233) PowerMock is not compatible with Java 11

2018-12-18 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55233  
 
 
  PowerMock is not compatible with Java 11   
 

  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 

  
 
 
 
 

 
 Current version of PowerMock used for testing is not compatible with Java 11.  So tests are failing with {noformat}Caused by: java.lang.IllegalAccessError: class jdk.internal.reflect.ConstructorAccessorImpl loaded by org.powermock.core.classloader.MockClassLoader @7cd1ec54 cannot access jdk/internal/reflect superclass jdk.internal.reflect.MagicAccessorImpl {noformat} Updating Parent POM to {{3.30}} to benefit from new versions of the libraries should be sufficient.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


<    1   2