[JIRA] (JENKINS-58944) Jenkins安装了NodeJS Plugin,但是在全局配置中没有nodeJS

2019-08-14 Thread 18610639...@163.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 peter xu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58944  
 
 
  Jenkins安装了NodeJS Plugin,但是在全局配置中没有nodeJS   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Nikolas Falco  
 
 
Attachments: 
 1565838916(1).jpg, 1565838949(1).jpg  
 
 
Components: 
 nodejs-plugin  
 
 
Created: 
 2019-08-15 03:22  
 
 
Labels: 
 jenkins  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 peter xu  
 

  
 
 
 
 

 
 Jenkins是放在tomcat下进行运行的  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
   

[JIRA] (JENKINS-57918) SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1

2019-08-14 Thread kiyoaki.hosh...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kiyoaki Hoshino commented on  JENKINS-57918  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1   
 

  
 
 
 
 

 
 Dear Devin, I checked http:///log/all . But I cannot find any messages like AtomicFileWriter. (If I need to change Logging Level, please tell me how to configure Log Recoder settings.) Log message when Pipeline: SCM Step (workflow-scm-step) Plugin 2.9 + REPO Plugin 1.10.7 does not work. Aug 15, 2019 1:36:36 AM INFO hudson.plugins.repo.RepoScm checkoutCode Checking out code in: Android Aug 15, 2019 1:36:44 AM INFO hudson.plugins.repo.ChangeLog saveChangeLog No logs found Aug 15, 2019 1:36:46 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish pipeline_checkout_test #22 completed: FAILURE Log message when Pipeline: SCM Step (workflow-scm-step) Plugin 2.7 + REPO Plugin 1.10.7 works OK Aug 15, 2019 1:37:34 AM INFO hudson.plugins.repo.RepoScm checkoutCode Checking out code in: Android Aug 15, 2019 1:37:34 AM INFO hudson.plugins.repo.ChangeLog saveChangeLog No logs found Aug 15, 2019 1:37:37 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish pipeline_checkout_test #23 completed: SUCCESS  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199890.1560007155000.3149.1565836260560%40Atlassian.JIRA.


[JIRA] (JENKINS-56989) Default pty to false for sshCommand

2019-08-14 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati commented on  JENKINS-56989  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default pty to false for sshCommand   
 

  
 
 
 
 

 
 Erik-Jan Rieksen Awesome! thanks for the confirmation.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198683.1555059312000.3146.1565833980258%40Atlassian.JIRA.


[JIRA] (JENKINS-58604) Full Stage View only showing one

2019-08-14 Thread mark.her...@fisglobal.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Hermon commented on  JENKINS-58604  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Full Stage View only showing one   
 

  
 
 
 
 

 
 We're seeing the same sort of behavior on our Jenkins. When we did some debugging, it looked like the '#' symbol is causing some confusion when passed back as part of the url to reload the view. The team across from us change the build number from '#1234' to their svn revision '1234' and they don't see this problem.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200764.1563816065000.3142.1565833500171%40Atlassian.JIRA.


[JIRA] (JENKINS-58937) exception while connecting to remote host (ssh)

2019-08-14 Thread jie...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jie Shen commented on  JENKINS-58937  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: exception while connecting to remote host (ssh)   
 

  
 
 
 
 

 
 Olivier Vernin On the Jenkins server, could you please try to lookup the "ubuntu-jenkinsinfraf4fce1.eastus2.cloudapp.azure.com" domain? It seems to be related with DNS.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201281.1565798345000.3139.1565833440151%40Atlassian.JIRA.


[JIRA] (JENKINS-58937) exception while connecting to remote host (ssh)

2019-08-14 Thread jie...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jie Shen assigned an issue to Jie Shen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58937  
 
 
  exception while connecting to remote host (ssh)   
 

  
 
 
 
 

 
Change By: 
 Jie Shen  
 
 
Assignee: 
 Azure DevOps Jie Shen  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201281.1565798345000.3137.1565832840258%40Atlassian.JIRA.


[JIRA] (JENKINS-58808) Stage View not appearing in Internet Explorer 11

2019-08-14 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy updated  JENKINS-58808  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58808  
 
 
  Stage View not appearing in Internet Explorer 11   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201119.1565002661000.3133.1565831580284%40Atlassian.JIRA.


[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException

2019-08-14 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58940  
 
 
  ActiveDirectory.updateUserCache uncaughtException   
 

  
 
 
 
 

 
Change By: 
 Ian Williams  
 
 
Attachment: 
 active_dir.dump.txt  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201284.1565805612000.3131.1565826780149%40Atlassian.JIRA.


[JIRA] (JENKINS-58943) Kubernets plugin missing dependency on varaint-plugin?

2019-08-14 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58943  
 
 
  Kubernets plugin missing dependency on varaint-plugin?   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2019-08-14 23:27  
 
 
Environment: 
 Jenkins 2.176.2  kubernetes-plugin:1.18.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ian Williams  
 

  
 
 
 
 

 
 Using install_plugins.sh (decker model) to mange plugins. Updated list to include: kubernetes:1.18.1  (assuming all dependencies are pulled in so only lsit top-level plugins) Startup Jenkins, get alert: 
 
Kubernetes plugin version 1.18.1Variant Plugin version 1.2 is older than required. To fix, install version 1.3 or later.
 No record of that dependency for the plugin. https://plugins.jenkins.io/kubernetes-credentials shows dependencies: Apache HttpComponents Client 4.x API v.4.5.5-3.0 (required) Credentials v.2.1.7 (required) Plain Credentials v.1.3 (required) Command Agent Launcher v.1.0 (implied) (what's this?) Oracle Java SE Development Kit Installer v.1.0 (implied) (what's this?) JAXB v.2.3.0 (implied) (what's this?) Trilead API v.1.0.4 (implied) (what's this?) Jenkins.instance.pluginManagerplugins..getDependencies() reports: [apache-httpcomponents-client-4-api (4.5.5-3.0),  credentials (2.1.7),  plain-credentials (1.3),  command-launcher (1.0),  jdk-tool (1.0)]        
 

  
 
 
 
 
   

[JIRA] (JENKINS-58912) error when logging in after upgrade to 2.189

2019-08-14 Thread liam.reim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Reimers commented on  JENKINS-58912  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: error when logging in after upgrade to 2.189   
 

  
 
 
 
 

 
 This looks a lot like the bug I hit, as well: https://issues.jenkins-ci.org/browse/JENKINS-58938  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201253.156571588.3125.1565824080155%40Atlassian.JIRA.


[JIRA] (JENKINS-44142) Step jobDsl can be used at most once in pipeline with DELETE

2019-08-14 Thread daniel.carring...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Carrington commented on  JENKINS-44142  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Step jobDsl can be used at most once in pipeline with DELETE   
 

  
 
 
 
 

 
 I have used the Job DSL plugin in production for over a year with the DISABLE action in place and I hit a similar issue when using multiple job dsl build steps in a single pipeline. The fix for this issue changed the behavior of the job dsl plugin when using multiple job dsl build steps in parallel. Is that (parallel job dsl build steps) a use case which is interesting to anyone else? (The new behavior of the Job DSL plugin ended up disabling many of my jobs. I spent a day with a mostly broken environment because I had to track this down.)  Based on the discussion here, it seems like the correct thing to do is to use the IGNORE behavior on all uses of the job dsl build step except the very last one, which should not run in parallel with any other job dsl build step. Looking at the available hook points in hudson.model.Run and hudson.model.Job, I think that there isn't a great way to solve this. We could register a new hudson.model.listeners.RunListener that disables or deletes jobs after a successful job completes (and runs Job DSL build steps that DISABLE or DELETE jobs). Has that idea already been considered?  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181769.1494322919000.3123.1565823900600%40Atlassian.JIRA.


[JIRA] (JENKINS-58939) Allow skipping pull requests by labels

2019-08-14 Thread stevengfos...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Foster commented on  JENKINS-58939  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow skipping pull requests by labels   
 

  
 
 
 
 

 
 I wrote a plugin to do this for myself a long time ago, never got to publishing it because I couldn't hook up an event subscriber thing for github pull request label events. My use case was for opting-in pull requets based on label but I think I wrote the excluding case as well. I can throw what I have on github tomorrow. https://issues.jenkins-ci.org/browse/JENKINS-50323 somewhat related.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201283.1565801632000.3112.1565823720156%40Atlassian.JIRA.


[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.

2019-08-14 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Shah Chowdhury as above.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54304  
 
 
  Jobs in parallel dont display the variant they are running.   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194952.1540802341000.3095.1565821861068%40Atlassian.JIRA.


[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.

2019-08-14 Thread tuttu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shah Chowdhury reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54304  
 
 
  Jobs in parallel dont display the variant they are running.   
 

  
 
 
 
 

 
Change By: 
 Shah Chowdhury  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194952.1540802341000.3081.1565821081022%40Atlassian.JIRA.


[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.

2019-08-14 Thread tuttu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shah Chowdhury commented on  JENKINS-54304  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jobs in parallel dont display the variant they are running.   
 

  
 
 
 
 

 
 We ended up reverting back to the old (2.25) level. Branch Names in the Raw Logs is critical for us. We have various tools/log-formatters that parse through raw logs. Please put this back.   
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194952.1540802341000.3066.1565821020395%40Atlassian.JIRA.


[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library

2019-08-14 Thread mi...@mikey.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 michael pechner commented on  JENKINS-46394  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: active choices reactive parameter cant load shared library   
 

  
 
 
 
 

 
 Very interested in accessing a  json file in the resources directory as defined from this facility: https://jenkins.io/doc/book/pipeline/shared-libraries/ My use case is to read a json file and present part of the data in a active choice parameter.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184658.1503497167000.3046.1565819940558%40Atlassian.JIRA.


[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves

2019-08-14 Thread tlynch...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Lynch commented on  JENKINS-36544  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow setting environment variables for dynamic ec2 slaves   
 

  
 
 
 
 

 
 Global envvars are unable to have different values depending on the node, for example some nodes FOO=foo and others FOO=bar.   Can 'init script' be used to set envvars?  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172564.1468000478000.3036.1565818500307%40Atlassian.JIRA.


[JIRA] (JENKINS-56217) allow to hide version number

2019-08-14 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-56217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: allow to hide version number   
 

  
 
 
 
 

 
 

Search was done with up to date copies of all repos as of a few minutes ago.
 This should have been done with usage-in-plugins 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3030.1565818320176%40Atlassian.JIRA.


[JIRA] (JENKINS-58932) Unable to Login After Upgrade from 2.176.1 to 2.176.2

2019-08-14 Thread tommyh...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tommy Wan commented on  JENKINS-58932  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to Login After Upgrade from 2.176.1 to 2.176.2   
 

  
 
 
 
 

 
 My problem is similar - after upgrading Jenkins from 2.176.1 to 2.176.2, users are not able to login and error prompted as "invalid user id or password". We are using Active Directory Plugin (v2.16). I rolled back the version to 2.176.1 and login issue vanished.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201276.1565795444000.3028.1565818260097%40Atlassian.JIRA.


[JIRA] (JENKINS-23349) Item names containing an emoji are not accessible

2019-08-14 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-23349  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Item names containing an emoji are not accessible   
 

  
 
 
 
 

 
 See https://github.com/jenkinsci/jenkins/pull/4152  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155495.1402054331000.3020.1565818080295%40Atlassian.JIRA.


[JIRA] (JENKINS-58820) scan Multibranch pipeline does not detect new streams when file is branch

2019-08-14 Thread dai...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Daigneault closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 restoring the duplicate status.  Could not reproduce on development stream, stream at the time could have been task stream.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-58820  
 
 
  scan Multibranch pipeline does not detect new streams when file is branch   
 

  
 
 
 
 

 
Change By: 
 Eric Daigneault  
 
 
Status: 
 Reopened Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201132.1565041263000.3018.1565817420229%40Atlassian.JIRA.


[JIRA] (JENKINS-56217) allow to hide version number

2019-08-14 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-56217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: allow to hide version number   
 

  
 
 
 
 

 
 A complete list of files that refer to Jenkins.VERSION along with the number of occurrences: 

 
metrics-plugin/src/main/java/jenkins/metrics/impl/JenkinsVersionsProviderImpl.java:1
artifactory-plugin/src/main/java/org/jfrog/hudson/util/ExtractorUtils.java:1
artifactory-plugin/src/main/java/org/jfrog/hudson/AbstractBuildInfoDeployer.java:1
anchore-container-scanner-plugin/src/main/java/com/anchore/jenkins/plugins/anchore/BuildWorker.java:1
qtest-plugin/src/main/java/com/qasymphony/ci/plugin/action/PushingResultAction.java:1
qtest-plugin/src/main/java/com/qasymphony/ci/plugin/action/SubmitJUnitStep.java:1
maven-plugin/src/main/java/hudson/maven/reporters/BuildInfoRecorder.java:2
custom-build-properties-plugin/src/main/java/org/jenkinsci/plugins/custombuildproperties/CustomBuildPropertiesAction.java:1
blueocean-plugin/blueocean-config/src/main/java/io/jenkins/blueocean/config/BlueOceanConfigStatePreloader.java:1
blueocean-plugin/blueocean-commons/src/main/java/io/jenkins/blueocean/commons/stapler/Export.java:1
support-core-plugin/src/main/java/com/cloudbees/jenkins/support/impl/AboutJenkins.java:2
support-core-plugin/src/main/java/com/cloudbees/jenkins/support/filter/ContentMappings.java:3
swamp-plugin/src/main/java/org/continuousassurance/swamp/jenkins/SwampPostBuild.java:1
compuware-topaz-for-total-test-plugin/src/main/java/com/compuware/jenkins/totaltest/TotalTestCTRunner.java:1
compuware-topaz-for-total-test-plugin/src/main/java/com/compuware/jenkins/totaltest/TotalTestRunner.java:1
bearychat-plugin/src/main/java/jenkins/plugins/bearychat/StandardBearyChatService.java:1
browserstack-integration-plugin/src/main/java/com/browserstack/automate/ci/common/analytics/Analytics.java:1
jenkins/core/src/main/java/hudson/Functions.java:2
jenkins/core/src/main/java/hudson/PluginManager.java:2
jenkins/core/src/main/java/hudson/cli/VersionCommand.java:1
jenkins/core/src/main/java/hudson/Plugin.java:1
jenkins/core/src/main/java/hudson/UDPBroadcastThread.java:1
jenkins/core/src/main/java/hudson/TcpSlaveAgentListener.java:1
jenkins/core/src/main/java/hudson/model/UsageStatistics.java:1
jenkins/core/src/main/java/hudson/model/DownloadService.java:2
jenkins/core/src/main/java/hudson/model/UpdateSite.java:3
jenkins/core/src/main/java/hudson/model/Api.java:1
jenkins/core/src/main/java/hudson/model/AbstractBuild.java:1
jenkins/core/src/main/java/jenkins/install/InstallUtil.java:6
jenkins/core/src/main/java/jenkins/model/AssetManager.java:1
practitest-integration-plugin/src/main/java/org/jenkinsci/plugins/practitest/PractitestApi.java:1
hpe-application-automation-tools-plugin/src/main/java/com/microfocus/application/automation/tools/octane/CIJenkinsServicesImpl.java:1
oracle-cloud-infrastructure-compute-plugin/src/main/java/com/oracle/cloud/baremetal/jenkins/client/SDKBaremetalCloudClient.java:1
sauce-ondemand-plugin/src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandProjectAction.java:1
sauce-ondemand-plugin/src/main/java/hudson/plugins/sauce_ondemand/JenkinsSauceREST.java:1
sauce-ondemand-plugin/src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java:1
sauce-ondemand-plugin/src/main/java/hudson/plugins/sauce_ondemand/credentials/SauceCredentials.java:1
sysdig-secure-plugin/src/main/java/com/sysdig/jenkins/plugins/sysdig/BuildWorker.java:1
 

  

[JIRA] (JENKINS-58942) Configurable webhook URL

2019-08-14 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-58942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58942  
 
 
  Configurable webhook URL   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201286.1565816327000.3012.1565816760100%40Atlassian.JIRA.


[JIRA] (JENKINS-58942) Configurable webhook URL

2019-08-14 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-58942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201286.1565816327000.3011.1565816700073%40Atlassian.JIRA.


[JIRA] (JENKINS-56217) allow to hide version number

2019-08-14 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-56217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: allow to hide version number   
 

  
 
 
 
 

 
 Some plugins use Functions.advertiseHeaders(): 
 
warnings-ng-plugin: issues/layout.jelly 
kerberos-sso-plugin, negotiatesso-plugin: servlet filters add the header. 
 I don't see any other calls to advertiseHeaders() in any jenkinsci repo. Search was done with up to date copies of all repos as of a few minutes ago. Now that I have an updated set of working copies, I'll perform additional searches for use of Jenkins.VERSION.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3008.1565816640168%40Atlassian.JIRA.


[JIRA] (JENKINS-58942) Configurable webhook URL

2019-08-14 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58942  
 
 
  Configurable webhook URL   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201286.1565816327000.3006.1565816400086%40Atlassian.JIRA.


[JIRA] (JENKINS-58942) Configurable webhook URL

2019-08-14 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58942  
 
 
  Configurable webhook URL   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2019-08-14 20:58  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 One of the common problems with triggering Jenkins builds from webhooks rather than polling is that notifications can be lost because the server is temporarily down or unresponsive, which you might try to address by having an external service queue up hooks for later delivery. Another is that Jenkins may be behind a firewall and need for hooks to be proxied through some sort of service. Whatever the case, something other than Jenkins.rootUrl needs to be used to register the webhook, for example on a GitHub organization. While administrators can remember to do this manually, creating an organization folder does this automatically—but only for the default location. There should be a way to override the Jenkins root URL for purposes of hook registration. This is not something you would want to configure in the GUI; it is a property of the environment in which Jenkins is installed, perhaps managed via code. As an initial step I am just letting the github-branch-source plugin pick up an environment variable for an alternative URL. A possible refinement would be for JenkinsLocationConfiguration to define this (means a newer core dependency), and perhaps for the location to be configurable using JCasC.  
 

  
 
 
 
 

 
 
 
   

[JIRA] (JENKINS-56217) allow to hide version number

2019-08-14 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-56217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: allow to hide version number   
 

  
 
 
 
 

 
 Some initial searches for Jenkins.VERSION in jenkinsci has found some interesting places: 
 
blueocean-plugin seems to include it in its REST API 
Numerous other plugins access this value, though I'm not sure if it exposes it as a header or in the response in general. 
  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3002.1565814720161%40Atlassian.JIRA.


[JIRA] (JENKINS-56217) allow to hide version number

2019-08-14 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-56217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: allow to hide version number   
 

  
 
 
 
 

 
 Ok, time for some fun. I've done some digging in Jenkins and found several places where the version number is exposed in situations with no permission checks. 
 
HudsonAuthenticationEntryPoint exposes the version in a header. This class is used for handling permission errors to redirect the user to login in the first place, so clearly there are no permission checks involved. 
TcpSlaveAgentListener exposes that header when you send a "GET /" request to it. 
UDPBroadcastThread exposes the version number as an XML tag in the metadata included in the multicast packet sent for autodiscovery. I'm not sure how important the version number is to include here, though it might be required. 
VersionCommand only requires Overall/Read to execute. 
Api instances include setting the version header, though typically, these objects are already guarded by other permission checks. However, if even a single API endpoint is unsecured, this would leak the version number. 
AbstractBuild tracks the version of Jenkins that build was executed in. 
DownloadService adds a script to the footer of any page that includes the version number in the body of an Ajax request as long as the user has Overall/Read permissions. 
IncompatibleVMDetected shows information about the running JVM as well, but no Jenkins version other than the footer that's not specific to this error page. 
l:layout and l:html both include the version number as a header, and l:layout includes the version number in the footer itself. 
Jenkins/login.jelly exposes the version in headers. 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
  

[JIRA] (JENKINS-23349) Item names containing an emoji are not accessible

2019-08-14 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-23349  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Item names containing an emoji are not accessible   
 

  
 
 
 
 

 
 I was about to say that it was a newer emoji, but it appears as though it's not new at all. Strange. I know that we use XML 1.1 instead of 1.0 in order to allow for better Unicode support, though that's likely irrelevant here unless you're trying to use an emoji in an XML tag name.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155495.1402054331000.2990.1565812860293%40Atlassian.JIRA.


[JIRA] (JENKINS-56217) allow to hide version number

2019-08-14 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-56217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: allow to hide version number   
 

  
 
 
 
 

 
 Too many things directly access the static field, nevermind.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.2986.1565810580139%40Atlassian.JIRA.


[JIRA] (JENKINS-56217) allow to hide version number

2019-08-14 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-56217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: allow to hide version number   
 

  
 
 
 
 

 
 Could we add that permission check in Jenkins.getVersion() and return null when unauthorized? I'm going to try that out and see what breaks.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.2982.1565810460176%40Atlassian.JIRA.


[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook

2019-08-14 Thread parichay.barpa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda started work on  JENKINS-58919  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201262.156577292.2980.1565808720353%40Atlassian.JIRA.


[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook

2019-08-14 Thread parichay.barpa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58919  
 
 
  DateTimeParseException on MR web hook   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Labels: 
 gsoc-2019  
 
 
Sprint: 
 GSoC 2019. Coding Phase 3  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201262.156577292.2978.1565808720322%40Atlassian.JIRA.


[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root

2019-08-14 Thread j.sp...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jay Spang commented on  JENKINS-50975  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Concurrent Groovy Shared Library syncs on different jobs use same workspace root   
 

  
 
 
 
 

 
 To be extra clear, it only repros for me with dynamically loaded libraries. If you import your library with...  

 
library 'static-global-library@now' 

  it doesn't happen. But if you load your library with...  

 
library(identifier: 'dynamically-loaded-library@now', retriever: legacySCM( // ... ) )` 

  it happens. Just click "Build Now" as rapidly as you you can 4-5 times. I can still send you a library if you'd like, but the failure happens before it even loads, so its contents don't matter.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190124.1524607256000.2963.1565807100661%40Atlassian.JIRA.


[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root

2019-08-14 Thread j.sp...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jay Spang edited a comment on  JENKINS-50975  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Concurrent Groovy Shared Library syncs on different jobs use same workspace root   
 

  
 
 
 
 

 
 To be extra clear, it only repros for me with _dynamically_ loaded libraries.If you import your library with... {code}library 'static-global-library@now'{code} it doesn't happen. But if you load your library with... {code}library(identifier: 'dynamically-loaded-library@now', retriever: legacySCM( // ... ) ) ` {code} it happens. Just click "Build Now" as rapidly as you you can 4-5 times.I can still send you a library if you'd like, but the failure happens before it even loads, so its contents don't matter.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190124.1524607256000.2971.1565807100811%40Atlassian.JIRA.


[JIRA] (JENKINS-58941) Missing Overall/Read permission when authenticating with LDAP user with a long UID

2019-08-14 Thread flabrie (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Labrie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58941  
 
 
  Missing Overall/Read permission when authenticating with LDAP user with a long UID
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 core, ldap-plugin, role-strategy-plugin  
 
 
Created: 
 2019-08-14 18:20  
 
 
Environment: 
 * macOS Mojave 10.14.6  * Jenkins 2.189  * Latest plugins installed  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Francis Labrie  
 

  
 
 
 
 

 
 This is a really strange bug: we do use a LDAP server to give access to our Jenkins users for years. But for the first time, a user can authenticate successfully, but even if we give him all the rights and permission, he cannot get access to the console nor jobs and projects. The only difference with other users is the length of his uid: it's 27 characters long, with only basic letters and one dot. It's something like this (it's not the real one, of course): abcdefg.hijklmnopqrstuvwxyz When he login, he gets that message: abcdefg.hijklmnopqrstuvwxyz is missing the Overall/Read permission We cannot change his uid. So we need a fix in Jenkins or in the related plugin.   Thanks!   
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-58352) Issues related to the EC2 plugins

2019-08-14 Thread parkinson.jer...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy Parkinson commented on  JENKINS-58352  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Issues related to the EC2 plugins   
 

  
 
 
 
 

 
 We are having this issue as well and it is a priority one for us. Everything was working fine until yesterday.   
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200467.1562291397000.2956.1565806200426%40Atlassian.JIRA.


[JIRA] (JENKINS-58352) Issues related to the EC2 plugins

2019-08-14 Thread parkinson.jer...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy Parkinson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58352  
 
 
  Issues related to the EC2 plugins   
 

  
 
 
 
 

 
Change By: 
 Jeremy Parkinson  
 
 
Priority: 
 Major Blocker  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200467.1562291397000.2958.1565806200452%40Atlassian.JIRA.


[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException

2019-08-14 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58940  
 
 
  ActiveDirectory.updateUserCache uncaughtException   
 

  
 
 
 
 

 
Change By: 
 Ian Williams  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201284.1565805612000.2954.1565805840234%40Atlassian.JIRA.


[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException

2019-08-14 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58940  
 
 
  ActiveDirectory.updateUserCache uncaughtException   
 

  
 
 
 
 

 
Change By: 
 Ian Williams  
 

  
 
 
 
 

 
 Updated plugins using install_plugins.sh (the docker model). Upon startup, seeing the following the in the logs when user logs in. Login is successful however. {{hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException}}{{SEVERE: A thread (ActiveDirectory.updateUserCache [#1]/332) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.}}{{java.lang.NullPointerException}}{{   at hudson.Util.fileToPath(Util.java:1501)}}{{   at hudson.model.UserIdMapper.createDirectoryForNewUser(UserIdMapper.java:145)}}{{   at hudson.model.UserIdMapper.putIfAbsent(UserIdMapper.java:92)}}{{   at hudson.model.User.putUserFolderIfAbsent(User.java:806)}}{{   at hudson.model.User.constructUserConfigFile(User.java:802)}}{{   at hudson.model.User.save(User.java:796)}}{{   at hudson.model.User.addProperty(User.java:336)}}{{   at hudson.plugins.active_directory.ActiveDirectoryUserDetail.updateUserInfo(ActiveDirectoryUserDetail.java:213)}}{{   at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$2.run(ActiveDirectoryUnixAuthenticationProvider.java:462)}}{{   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) }}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException

2019-08-14 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58940  
 
 
  ActiveDirectory.updateUserCache uncaughtException   
 

  
 
 
 
 

 
Change By: 
 Ian Williams  
 

  
 
 
 
 

 
 Updated plugins using install_plugins.sh (the docker model). Upon startup, seeing the following the in the logs when user logs in. Login is successful however.  {{ hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException }}   {{ SEVERE: A thread (ActiveDirectory.updateUserCache [#1]/332) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. }}   {{java.lang.NullPointerException}}  {{      at hudson.Util.fileToPath(Util.java:1501)}}  {{      at hudson.model.UserIdMapper.createDirectoryForNewUser(UserIdMapper.java:145)}}  {{      at hudson.model.UserIdMapper.putIfAbsent(UserIdMapper.java:92)}}  {{      at hudson.model.User.putUserFolderIfAbsent(User.java:806)}}  {{      at hudson.model.User.constructUserConfigFile(User.java:802)}}  {{      at hudson.model.User.save(User.java:796)}}  {{      at hudson.model.User.addProperty(User.java:336)}}  {{      at hudson.plugins.active_directory.ActiveDirectoryUserDetail.updateUserInfo(ActiveDirectoryUserDetail.java:213)}}  {{      at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$2.run(ActiveDirectoryUnixAuthenticationProvider.java:462)}}  {{      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)   }}    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 

[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException

2019-08-14 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58940  
 
 
  ActiveDirectory.updateUserCache uncaughtException   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Félix Belzunce Arcos  
 
 
Components: 
 active-directory-plugin  
 
 
Created: 
 2019-08-14 18:00  
 
 
Environment: 
 Jenkins 2.176.2  active-directory:2.16  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ian Williams  
 

  
 
 
 
 

 
 Updated plugins using install_plugins.sh (the docker model).   Upon startup, seeing the following the in the logs when user logs in. Login is successful however.  hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException SEVERE: A thread (ActiveDirectory.updateUserCache 1/332) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException    at hudson.Util.fileToPath(Util.java:1501)    at hudson.model.UserIdMapper.createDirectoryForNewUser(UserIdMapper.java:145)    at hudson.model.UserIdMapper.putIfAbsent(UserIdMapper.java:92)    at hudson.model.User.putUserFolderIfAbsent(User.java:806)    at hudson.model.User.constructUserConfigFile(User.java:802)    at hudson.model.User.save(User.java:796)    at hudson.model.User.addProperty(User.java:336)    at hudson.plugins.active_directory.ActiveDirectoryUserDetail.updateUserInfo(ActiveDirectoryUserDetail.java:213)    at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$2.run(ActiveDirectoryUnixAuthenticationProvider.java:462)    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)    
 

[JIRA] (JENKINS-19887) Allow time zone to be set on a per user basis

2019-08-14 Thread jon.herman...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon Hermansen commented on  JENKINS-19887  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow time zone to be set on a per user basis   
 

  
 
 
 
 

 
 Thank you Morgan Kobeissi for the userscript!  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151407.1380890121000.2946.1565805121852%40Atlassian.JIRA.


[JIRA] (JENKINS-58932) Unable to Login After Upgrade from 2.176.1 to 2.176.2

2019-08-14 Thread jim.duffi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Duffield updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58932  
 
 
  Unable to Login After Upgrade from 2.176.1 to 2.176.2   
 

  
 
 
 
 

 
Change By: 
 Jim Duffield  
 

  
 
 
 
 

 
 The following stack trace is displayed within the Jenkins UI when Jenkins is restarted after the upgrade from 2.176.1 to 2.176.2:{{com.thoughtworks.xstream.mapper.CannotResolveClassException: com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategycom.thoughtworks.xstream.mapper.CannotResolveClassException: com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper.java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:379) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:48) at hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:459) at 

[JIRA] (JENKINS-58939) Allow skipping pull requests by labels

2019-08-14 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-58939  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow skipping pull requests by labels   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/github-branch-source-plugin/pull/239    
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201283.1565801632000.2889.1565802660108%40Atlassian.JIRA.


[JIRA] (JENKINS-58939) Allow skipping pull requests by labels

2019-08-14 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58939  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow skipping pull requests by labels   
 

  
 
 
 
 

 
 This can be done in a separate plugin implementing a BranchBuildStrategy, I think. Perhaps better done in scm-trait-commit-skip-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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201283.1565801632000.2887.1565802360136%40Atlassian.JIRA.


[JIRA] (JENKINS-58939) Allow skipping pull requests by labels

2019-08-14 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-58939  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201283.1565801632000.2879.1565801700214%40Atlassian.JIRA.


[JIRA] (JENKINS-58939) Allow skipping pull requests by labels

2019-08-14 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58939  
 
 
  Allow skipping pull requests by labels   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201283.1565801632000.2878.1565801640314%40Atlassian.JIRA.


[JIRA] (JENKINS-58939) Allow skipping pull requests by labels

2019-08-14 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58939  
 
 
  Allow skipping pull requests by labels   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2019-08-14 16:53  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 See INFRA-1633 for a real use-case on ci.jenkins.io. Some pull requests are stale OR contain no content to rebuild, and it does not make sense to run CI against them and to consume resources each time builds are retriggered. I suggest adding a new trait which allows skipping pull requests if they are labeled by "skip-ci" or such labels  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root

2019-08-14 Thread msme...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Smeeth commented on  JENKINS-50975  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Concurrent Groovy Shared Library syncs on different jobs use same workspace root   
 

  
 
 
 
 

 
 Hi Jay,  I'm currently trying to reproduce your issue, so far I have been unable to. If possible could you share your library file? Thanks, Matthew  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190124.1524607256000.2859.1565800380308%40Atlassian.JIRA.


[JIRA] (JENKINS-58938) Exception "org.kohsuke.stapler.ScriptLoadException: org.apache.commons.jelly.JellyException: Failed to load message from org.kohsuke.stapler.jelly.groovy.GroovyFacet@1374c13d" a

2019-08-14 Thread liam.reim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Reimers commented on  JENKINS-58938  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Exception "org.kohsuke.stapler.ScriptLoadException: org.apache.commons.jelly.JellyException: Failed to load message from org.kohsuke.stapler.jelly.groovy.GroovyFacet@1374c13d" after upgrade to 2.189   
 

  
 
 
 
 

 
 Attached full page source (including full stacktrace) as jenkins-58938.txt  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201282.1565799462000.2856.1565799601165%40Atlassian.JIRA.


[JIRA] (JENKINS-58938) Exception "org.kohsuke.stapler.ScriptLoadException: org.apache.commons.jelly.JellyException: Failed to load message from org.kohsuke.stapler.jelly.groovy.GroovyFacet@1374c13d" a

2019-08-14 Thread liam.reim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Reimers updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58938  
 
 
  Exception "org.kohsuke.stapler.ScriptLoadException: org.apache.commons.jelly.JellyException: Failed to load message from org.kohsuke.stapler.jelly.groovy.GroovyFacet@1374c13d" after upgrade to 2.189   
 

  
 
 
 
 

 
Change By: 
 Liam Reimers  
 
 
Attachment: 
 jenkins-58938.txt  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201282.1565799462000.2855.1565799600997%40Atlassian.JIRA.


[JIRA] (JENKINS-58938) Exception "org.kohsuke.stapler.ScriptLoadException: org.apache.commons.jelly.JellyException: Failed to load message from org.kohsuke.stapler.jelly.groovy.GroovyFacet@1374c13d" a

2019-08-14 Thread liam.reim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Reimers created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58938  
 
 
  Exception "org.kohsuke.stapler.ScriptLoadException: org.apache.commons.jelly.JellyException: Failed to load message from org.kohsuke.stapler.jelly.groovy.GroovyFacet@1374c13d" after upgrade to 2.189   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-08-14 16:17  
 
 
Environment: 
 Jenkins 2.189 with these plugins:   org.jenkins-ci:crypto-util:1.1  commons-httpclient:commons-httpclient:3.1-jenkins-1  aopalliance:aopalliance:1.0  com.google.code.findbugs:annotations:3.0.0  commons-beanutils:commons-beanutils:1.9.3  com.google.inject:guice:4.0  org.jenkins-ci.modules:slave-installer:1.6  org.springframework:spring-dao:1.2.9  org.codehaus.groovy:groovy-all:2.4.12  org.jenkins-ci.main:jenkins-core:2.187  org.jenkins-ci:constant-pool-scanner:1.2  org.connectbot.jbcrypt:jbcrypt:1.0.0  org.ow2.asm:asm-commons:5.0.3  org.jenkins-ci:symbol-annotation:1.1  org.slf4j:slf4j-api:1.7.26  commons-digester:commons-digester:2.1  org.kohsuke:libpam4j:1.11  com.github.jnr:jnr-posix:3.0.45  org.jvnet.winp:winp:1.28  org.jenkins-ci.modules:instance-identity:2.2  org.kohsuke:asm6:6.2  net.sf.kxml:kxml2:2.3.0  org.kohsuke:libzfs:0.8  org.jenkins-ci.modules:windows-slave-installer:1.11  org.jenkins-ci.modules:sshd:2.6  org.kohsuke.stapler:stapler:1.257.2  org.jenkins-ci.main:cli:2.187  org.jenkins-ci.ui:jquery-detached:1.2  org.kohsuke.stapler:json-lib:2.4-jenkins-2  org.slf4j:slf4j-jdk14:1.7.26  org.jvnet.robust-http-client:robust-http-client:1.2  org.ow2.asm:asm:5.0.3  com.github.jnr:jnr-ffi:2.1.8  com.github.jnr:jnr-constants:0.9.9  org.kohsuke.stapler:stapler-adjunct-timeline:1.5  org.kohsuke.stapler:stapler-groovy:1.257.2  org.kohsuke.stapler:stapler-jelly:1.257.2  org.jvnet.hudson:commons-jelly-tags-define:1.0.1-hudson-20071021  commons-lang:commons-lang:2.6  org.springframework:spring-jdbc:1.2.9  org.codehaus.woodstox:wstx-asl:3.2.9  org.springframework:spring-core:2.5.6.SEC03  org.springframework:spring-aop:2.5.6.SEC03  org.samba.jcifs:jcifs:1.3.17-kohsuke-1  net.java.dev.jna:jna:5.3.1  net.i2p.crypto:eddsa:0.3.0  com.sun.solaris:embedded_su4j:1.1  com.github.jnr:jffi:1.2.17  javax.inject:javax.inject:1  org.jenkins-ci.modules:upstart-slave-installer:1.1  args4j:args4j:2.33  org.apache.commons:commons-compress:1.10  org.fusesource.jansi:jansi:1.11  org.springframework:spring-beans:2.5.6.SEC03  net.java.sezpoz:sezpoz:1.13  javax.xml.stream:stax-api:1.0-2  org.jvnet.hudson:activation:1.1.1-hudson-1  commons-jelly:commons-jelly-tags-fmt:1.0  jfree:jfreechart:1.0.9  org.slf4j:log4j-over-slf4j:1.7.26  oro:oro:2.0.8  

[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com

2019-08-14 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated  JENKINS-58862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58862  
 
 
  Github Branch Source Plugin always references https://api.github.com   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.2853.1565798820486%40Atlassian.JIRA.


[JIRA] (JENKINS-58937) exception while connecting to remote host (ssh)

2019-08-14 Thread oliv...@vernin.me (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Vernin created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58937  
 
 
  exception while connecting to remote host (ssh)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-vm-agents-plugin  
 
 
Created: 
 2019-08-14 15:59  
 
 
Environment: 
 Jenkins 2.176.2  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Olivier Vernin  
 

  
 
 
 
 

 
 AzureVMAgentSSHLauncher: getRemoteSession: Got exception while connecting to remote host ubuntu-jenkinsinfraf4fce1.eastus2.cloudapp.azure.com:22 java.net.UnknownHostException: ubuntu-jenkinsinfraf4fce1.eastus2.cloudapp.azure.com at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:220) at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403) at java.base/java.net.Socket.connect(Socket.java:591) at java.base/java.net.Socket.connect(Socket.java:540) at java.base/java.net.Socket.(Socket.java:436) at java.base/java.net.Socket.(Socket.java:213) at com.jcraft.jsch.Util$1.run(Util.java:362) Caused: com.jcraft.jsch.JSchException at com.jcraft.jsch.Util.createSocket(Util.java:394) at com.jcraft.jsch.Session.connect(Session.java:215) at com.jcraft.jsch.Session.connect(Session.java:183) at com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.getRemoteSession(AzureVMAgentSSHLauncher.java:307) at com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.connectToSsh(AzureVMAgentSSHLauncher.java:453) at com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.launch(AzureVMAgentSSHLauncher.java:115) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at 

[JIRA] (JENKINS-58935) For pipeline context, devise a way to generalize the config options and notification steps for all IM protocols

2019-08-14 Thread ch...@orr.me.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Orr commented on  JENKINS-58935  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: For pipeline context, devise a way to generalize the config options and notification steps for all IM protocols   
 

  
 
 
 
 

 
 I'm going to remove myself as assignee, as gcm-notification-plugin no longer exists. I don't know whether you intend to work on this or not, but either way I think it would be useful to have some examples of what you think the syntax should look like. e.g. How would it deal with custom targets or options per Pipeline, or there being multiple "IM providers" configured on a given Jenkins instance?  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201279.1565796457000.2844.1565797560476%40Atlassian.JIRA.


[JIRA] (JENKINS-42973) User cannot create new Pipeline and locate it in a specific folder

2019-08-14 Thread jonat...@jonathanfoster.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Foster commented on  JENKINS-42973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User cannot create new Pipeline and locate it in a specific folder   
 

  
 
 
 
 

 
 James Dumay: I'm a huge fan of Blue Ocean. I'm coming to Jenkins from GitLab CI and I was really disappointed with the experience. That is until I came across Blue Ocean. Now I'm running into an issue though. I have the same use case as Matt Aizcorbe, we use folders to isolate different teams and products. How can I use Blue Ocean with this structure? What's the different path you referred to above and is it functional?  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179986.1490121108000.2840.1565797560411%40Atlassian.JIRA.


[JIRA] (JENKINS-58935) For pipeline context, devise a way to generalize the config options and notification steps for all IM protocols

2019-08-14 Thread ch...@orr.me.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Orr assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58935  
 
 
  For pipeline context, devise a way to generalize the config options and notification steps for all IM protocols   
 

  
 
 
 
 

 
Change By: 
 Christopher Orr  
 
 
Assignee: 
 Christopher Orr  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201279.1565796457000.2847.1565797560521%40Atlassian.JIRA.


[JIRA] (JENKINS-58936) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jell

2019-08-14 Thread bvajj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 balaji vajjala created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58936  
 
 
  javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jelly:46:53:
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jenkinswalldisplay  
 
 
Created: 
 2019-08-14 15:30  
 
 
Environment: 
 Jenkins 2.189-1  
 
 
Priority: 
  Major  
 
 
Reporter: 
 balaji vajjala  
 

  
 
 
 
 

 
 Keep getting this exception after upgrading Jenkins to Jenkins 2.189-1 javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jelly:46:53:  org.kohsuke.stapler.ScriptLoadException: org.apache.commons.jelly.JellyException: Failed to load message from org.kohsuke.stapler.jelly.groovy.GroovyFacet@25877865 at org.kohsuke.stapler.Facet$1.dispatch(Facet.java:247) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at 

[JIRA] (JENKINS-58935) For pipeline context, devise a way to generalize the config options and notification steps for all IM protocols

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58935  
 
 
  For pipeline context, devise a way to generalize the config options and notification steps for all IM protocols   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Christopher Orr  
 
 
Components: 
 gcm-notification-plugin, instant-messaging-plugin, ircbot-plugin, jabber-plugin, skype-plugin  
 
 
Created: 
 2019-08-14 15:27  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jim Klimov  
 

  
 
 
 
 

 
 The instant-messaging-plugin since release 1.37 provides the shareable core functionality for pipeline integration, used by step implementations in ircbot-plugin (since 2.31) and jabber-plugin (merge and release pending). Hopefully over time other protocol plugins would catch up. It sounds reasonable to implement a generic notification step (and `options{}` support eventually) that would send messages with a single command in the pipeline script without worries about which IM protocols are set up in a particular build farm, making the codebase and recipes for it more portable.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
  

[JIRA] (JENKINS-58934) For pipeline context, add an "options{...}" or similar clause trigger for IM notifications without an explicit step

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58934  
 
 
  For pipeline context, add an "options{...}" or similar clause trigger for IM notifications without an explicit step   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 kutzi  
 
 
Components: 
 instant-messaging-plugin, ircbot-plugin  
 
 
Created: 
 2019-08-14 15:21  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jim Klimov  
 

  
 
 
 
 

 
 In order to be feature-equivalent to freestyle jobs IRC Post-build step (which in fact also hooks into pre-build setup), allow to specify once in a pipeline that we want notifications about both start and complete events of this job.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
 

[JIRA] (JENKINS-58933) For pipeline context, add an "options{...}" preset for ircNotify (or generalize for imNotify?)

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58933  
 
 
  For pipeline context, add an "options{...}" preset for ircNotify (or generalize for imNotify?)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 kutzi  
 
 
Components: 
 instant-messaging-plugin, ircbot-plugin  
 
 
Created: 
 2019-08-14 15:19  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jim Klimov  
 

  
 
 
 
 

 
 In order to be feature-equivalent to freestyle jobs, allow to preset this job's notification strategy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira 

[JIRA] (JENKINS-58932) Unable to Login After Upgrade from 2.176.1 to 2.176.2

2019-08-14 Thread jim.duffi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Duffield updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58932  
 
 
  Unable to Login After Upgrade from 2.176.1 to 2.176.2   
 

  
 
 
 
 

 
Change By: 
 Jim Duffield  
 

  
 
 
 
 

 
 The following stack trace is displayed within the Jenkins UI when Jenkins is restarted after the upgrade from 2.176.1 to 2.176.2:{{com.thoughtworks.xstream.mapper.CannotResolveClassException: com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategycom.thoughtworks.xstream.mapper.CannotResolveClassException: com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper.java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:379) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:48) at hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:459) at 

[JIRA] (JENKINS-58932) Unable to Login After Upgrade from 2.176.1 to 2.176.2

2019-08-14 Thread jim.duffi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Duffield updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58932  
 
 
  Unable to Login After Upgrade from 2.176.1 to 2.176.2   
 

  
 
 
 
 

 
Change By: 
 Jim Duffield  
 

  
 
 
 
 

 
 The following stack trace is displayed within the Jenkins UI when Jenkins is restarted after the upgrade from 2.176.1 to 2.176.2:{{com.thoughtworks.xstream.mapper.CannotResolveClassException: com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategycom.thoughtworks.xstream.mapper.CannotResolveClassException: com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper.java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:379) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:48) at hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:459) at 

[JIRA] (JENKINS-56882) java.lang.NullPointerException after the build successfull

2019-08-14 Thread michael.l.wald...@nasa.gov (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Waldorf commented on  JENKINS-56882  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException after the build successfull   
 

  
 
 
 
 

 
 I encountered this issue using Jenkins 2.150.3, Accurev plugin 0.7.20, and Ant plugin 1.9.  The issue traced back in my case to RunWithSCM.super.getCulprits returning null when it shouldn't be able to.  I was able to roll back to 0.7.13 of the Accurev plugin and the issue went 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198553.1554383499000.2825.1565795940227%40Atlassian.JIRA.


[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script

2019-08-14 Thread eplot...@drivenets.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 efo plo commented on  JENKINS-37984  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script   
 

  
 
 
 
 

 
 Carsten Mück If one can't define a pipeline inside `DoYourWork()` function — which I suspect is not the case, though I haven't tried it — this does not solve the original issue.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.2765.1565795581245%40Atlassian.JIRA.


[JIRA] (JENKINS-58932) Unable to Login After Upgrade from 2.176.1 to 2.176.2

2019-08-14 Thread jim.duffi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Duffield created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58932  
 
 
  Unable to Login After Upgrade from 2.176.1 to 2.176.2   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 config.xml  
 
 
Components: 
 core  
 
 
Created: 
 2019-08-14 15:10  
 
 
Environment: 
 Upgrading from 2.176.1 to 2.176.2   | Plugin | Version | Enabled |  |---|---|---|  |apache-httpcomponents-client-4-api|4.5.5-3.0|true  |bouncycastle-api|2.17|true  |build-timestamp|1.0.3|true  |command-launcher|1.3|true  |conditional-buildstep|1.3.6|true  |credentials|2.2.1|true  |display-url-api|2.3.2|true  |email-ext|2.66|true  |git| 3.11.0|true  |git-client|2.8.0|true  |greenballs|1.15|true  |jackson2-api|2.9.9.1|true  |javadoc|1.5|true  |jdk-tool|1.3|true  |job-dsl|1.75|true  |jquery|1.12.4-0|true  |jquery-ui|1.0.2|true  |jsch|0.1.55.1|true  |junit|1.28|true  |ldap|1.20|true  |mailer|1.24|true  |matrix-auth|2.4.2|true  |matrix-project|1.14|true  |maven-plugin|3.4| true  |mesos|0.18.1|true  |metrics|4.0.2.5|true  |monitoring|1.79.0|true  |parameterized-trigger|2.35.2|true  |postbuildscript|2.8.1|true  |role-strategy|2.13| true  |run-condition|1.2|true  |saferestart|0.3|true  |scm-api|2.6.3|true  |script-security|1.62|true  |ssh-credentials|1.17.1|true  |strict-crumb-issuer|2.0.1|true  |structs|1.20|true  |token-macro|2.8|true  |variant|1.3|true  |workflow-api|2.36|true  |workflow-job|2.33|true  |workflow-scm-step|2.9|true  |workflow-step-api|2.20|true  |workflow-support|3.3|true  
 
 
Labels: 
 jenkins  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jim Duffield  
 

  
 
 
 
 
   

[JIRA] (JENKINS-56300) New step or option that does not block on individual job completion

2019-08-14 Thread john.westcott...@redhat.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John Westcott resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please see the 0.10.0 version which now adds an async option to pipeline invocation. Examples of how to use this can be found on the plugin wiki: https://wiki.jenkins.io/display/JENKINS/Ansible+Tower+Plugin  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-56300  
 
 
  New step or option that does not block on individual job completion   
 

  
 
 
 
 

 
Change By: 
 John Westcott  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 0.10.0  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this 

[JIRA] (JENKINS-58931) move the `InjectedTest` out to a separate dependency

2019-08-14 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58931  
 
 
  move the `InjectedTest` out to a separate dependency   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 jenkins-test-harness  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201275.1565793009000.2760.1565793120155%40Atlassian.JIRA.


[JIRA] (JENKINS-58931) move the `InjectedTest` out to a separate dependency

2019-08-14 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58931  
 
 
  move the `InjectedTest` out to a separate dependency   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 maven-hpi-plugin, plugin-pom  
 
 
Created: 
 2019-08-14 14:30  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Nord  
 

  
 
 
 
 

 
 Surefire has a way to scan dependencies for Tests in order to execute. This sounds like a good thing to replace the `InjectedTest` with (and move to junit4 at the same time). http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#dependenciesToScan    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-58924) job.allBuilds points to wrong URL when called from a job inside a folderJob

2019-08-14 Thread niclas.lindb...@nillsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Niclas Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58924  
 
 
  job.allBuilds points to wrong URL when called from a job inside a folderJob   
 

  
 
 
 
 

 
Change By: 
 Niclas Lindberg  
 

  
 
 
 
 

 
 When a job is residing in a folderJob then the API url to the job in job.allBuilds() points to /job/SIMPLE_JOB_NAME/api/json which causes a 404. Instead the job.allBuilds() should point to /job/FOLDER_JOB_NAME/job/SIMPLE_JOB_NAME/api/json.Code: JobWithDetails#127 Fix:private String getJobPath() {   String[] nameParts = this.getFullName().split("\\/");   for(int i=0;i      nameParts[i] = EncodingUtils.encode(nameParts[i]);   }   return "/job/" + String.join("/job/",nameParts);}public List getAllBuilds() throws IOException {   String path = getJobPath();   try {      List builds = client.get(path + "?tree=allBuilds[number[*],url[*],queueId[*]]", AllBuilds.class).getAllBuilds();      if (builds == null) {          return Collections.emptyList();      } else {         return transform(builds, new Function() {            @Override            public Build apply(Build from) {               return buildWithClient(from);           }        });      }   } catch (HttpResponseException e) {              // TODO: Thinks about a better handling if the job does not exist?         if (e.getStatusCode() == HttpStatus.SC_NOT_FOUND) {            // TODO: Check this if this is necessary or a good idea?           return null;        }        throw e;   }}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-58920) Jenkins Katalon integration: javascript fails to execute in Windows Server (execute Windows batch command)

2019-08-14 Thread yolanda.m...@arhs-consulting.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Y M updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58920  
 
 
  Jenkins Katalon integration: _javascript_ fails to execute in Windows Server (execute Windows batch command)   
 

  
 
 
 
 

 
Change By: 
 Y M  
 

  
 
 
 
 

 
 Hi,I have a master - slave architecture, where the master is Linux Red Hat, and the slave is a Windows Server 2016.In the Windows server, I have installed Katalon 6.2.1.I made an integration test to run one simple script in the slave, but using Jenkins master. This is done by restricting in which node can the script be executed. As build step, I use "execute Windows batch command".My script needs to execute _javascript_. I could execute it successfully in the slave, using Katalon Studio, but when I executed it through Jenkins, this is the exception I got:---2019-08-13 14:46:32.531 ERROR c.k.k.core.keyword.internal.KeywordMain  - ? Unable to execute _javascript_. (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to execute _javascript_. at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.stepFailed(WebUIKeywordMain.groovy:64) at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:26) at com.kms.katalon.core.webui.keyword.builtin.ExecuteJavaScriptKeyword.executeJavascript(ExecuteJavascriptKeyword.groovy:42) at com.kms.katalon.core.webui.keyword.builtin.ExecuteJavaScriptKeyword.execute(ExecuteJavascriptKeyword.groovy:37) at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:56) at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.executeJavaScript(WebUiBuiltInKeywords.groovy:3787) at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$executeJavaScript$2.call(Unknown Source) at create new client.run(create new client:25) at com.kms.katalon.core.main.ScriptEngine.run(ScriptEngine.java:194) at com.kms.katalon.core.main.ScriptEngine.runScriptAsRawText(ScriptEngine.java:119) at com.kms.katalon.core.main.TestCaseExecutor.runScript(TestCaseExecutor.java:337) at com.kms.katalon.core.main.TestCaseExecutor.doExecute(TestCaseExecutor.java:328) at com.kms.katalon.core.main.TestCaseExecutor.processExecutionPhase(TestCaseExecutor.java:307) at com.kms.katalon.core.main.TestCaseExecutor.accessMainPhase(TestCaseExecutor.java:299) at com.kms.katalon.core.main.TestCaseExecutor.execute(TestCaseExecutor.java:233) at com.kms.katalon.core.main.TestSuiteExecutor.accessTestCaseMainPhase(TestSuiteExecutor.java:133) at com.kms.katalon.core.main.TestSuiteExecutor.accessTestSuiteMainPhase(TestSuiteExecutor.java:116) at com.kms.katalon.core.main.TestSuiteExecutor.execute(TestSuiteExecutor.java:83) at com.kms.katalon.core.main.TestCaseMain.startTestSuite(TestCaseMain.java:157) at com.kms.katalon.core.main.TestCaseMain$startTestSuite$0.call(Unknown Source) at TempTestSuite1565700365710.run(TempTestSuite1565700365710.groovy:35)Caused by: org.openqa.selenium._javascript_Exception: _javascript_ errorBuild 

[JIRA] (JENKINS-58930) need to create dashboard

2019-08-14 Thread jeevanjyoth...@terralogic.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeevanjyoti Jena created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58930  
 
 
  need to create dashboard
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Jeevanjyoti Jena  
 
 
Components: 
 dashboard-view-plugin  
 
 
Created: 
 2019-08-14 14:06  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jeevanjyoti Jena  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201274.1565791576000.2753.1565791620182%40Atlassian.JIRA.


[JIRA] (JENKINS-58686) Syncing to revision 0 runs an invalid command

2019-08-14 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth commented on  JENKINS-58686  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Syncing to revision 0 runs an invalid command   
 

  
 
 
 
 

 
 Hi William Brode - Thanks.  Paul has already pulled in the code but I wanted to pass on the background to our QA team.      
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200969.1564174442000.2751.1565790960267%40Atlassian.JIRA.


[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script

2019-08-14 Thread mueck.cars...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carsten Mück commented on  JENKINS-37984  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script   
 

  
 
 
 
 

 
 Workaround: Move your code into different scripts inside an extra Jenkinsfile Repository (or in your Build-Repository), check those files out, load them into variables and call the code as function. Example Jenkinsfile (Main executed) 

 

node(){
checkout Jenkinsfile-repo
def HelperScript = load("path/to/helperscript.groovy")
Helperscript.DoYourWork()
} 

 helperscript.groovy 

 

#!groovy
def DoYourWork(){
 //Do something that doesn't work because too much to load in initial script
}
//Important statement for loading the script!!!
return this 

 As the script is not loaded initially it can compile the main Jenkinsfile. Hope that works for more people then just me   
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.2688.1565789401998%40Atlassian.JIRA.


[JIRA] (JENKINS-56639) when viewing a pipeline in blue ocean, please stop auto opening console log of failed step

2019-08-14 Thread david3bizza...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Davide Bizzarri commented on  JENKINS-56639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: when viewing a pipeline in blue ocean, please stop auto opening console log of failed step   
 

  
 
 
 
 

 
 I agree, it's really annoying  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198268.1553093515000.2683.1565789340816%40Atlassian.JIRA.


[JIRA] (JENKINS-4623) Use build parameter/variable for IM notification recipient

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov edited a comment on  JENKINS-4623  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use build parameter/variable for IM notification recipient   
 

  
 
 
 
 

 
 Partially duplicated  by  JENKINS-18947 (in the part that both issues ask to notify the user who started a build).With a look at this from 2019, note also that recently there were Jenkins core changes to promote running jobs as different Jenkins accounts, not just as "System". In relation to this story, make sure to NOT notify jobs started automatically, perhaps whether as System or not (the BuildCause's should probably allow to differentiate that), probably including non-human re-runs of such, although should probably it should notify a person who started a parent job that triggered this one with IM notifications enabled.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.134696.125497952.2679.1565787720206%40Atlassian.JIRA.


[JIRA] (JENKINS-4623) Use build parameter/variable for IM notification recipient

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov commented on  JENKINS-4623  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use build parameter/variable for IM notification recipient   
 

  
 
 
 
 

 
 Partially duplicated JENKINS-18947 (in the part that both issues ask to notify the user who started a build). With a look at this from 2019, note also that recently there were Jenkins core changes to promote running jobs as different Jenkins accounts, not just as "System". In relation to this story, make sure to NOT notify jobs started automatically, perhaps whether as System or not (the BuildCause's should probably allow to differentiate that), probably including non-human re-runs of such, although should probably it should notify a person who started a parent job that triggered this one with IM notifications enabled.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.134696.125497952.2677.1565787600234%40Atlassian.JIRA.


[JIRA] (JENKINS-58922) Support for App Bundles, .aab files

2019-08-14 Thread ch...@orr.me.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Orr closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58922  
 
 
  Support for App Bundles, .aab files   
 

  
 
 
 
 

 
Change By: 
 Christopher Orr  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201265.1565778913000.2673.1565787540325%40Atlassian.JIRA.


[JIRA] (JENKINS-5031) instant-messaging plugin notifications with custom messages

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov commented on  JENKINS-5031  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: instant-messaging plugin notifications with custom messages   
 

  
 
 
 
 

 
 See also https://issues.jenkins-ci.org/browse/JENKINS-34903?focusedCommentId=373370=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-373370 about concerns on the greater configurability  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.135115.1260200449000.2663.1565787120928%40Atlassian.JIRA.


[JIRA] (JENKINS-11815) Jenkins IRC bot should send help message in private chat

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov commented on  JENKINS-11815  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins IRC bot should send help message in private chat   
 

  
 
 
 
 

 
 I believe this issue is multi-fold and currently: 
 
requesting "help" in a private chat with the jenkins IRC user works and does not spam shared room channels (so the declared goal of this issue is achievable for "good actors") 
requesting "help" in a shared room channel indeed does not cause a private-chat reply, so the "spamming" problem is still there 
very long lines posted by the jenkins IM client, e.g. a "queue" request with many agents listed as unable to pick up a job due to label constraints, to a private chat can still get it disconnected from all chats (will come back in a few seconds) 
  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142058.1321823874000.2660.1565786880400%40Atlassian.JIRA.


[JIRA] (JENKINS-58929) Bulk API for shelving projects

2019-08-14 Thread carsten.pfeif...@gebit.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carsten Pfeiffer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58929  
 
 
  Bulk API for shelving projects   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Pierre Beitz  
 
 
Components: 
 shelve-project-plugin  
 
 
Created: 
 2019-08-14 12:42  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Carsten Pfeiffer  
 

  
 
 
 
 

 
 It would be nice if there was a bulk API for shelving projects in batch. This would be used by seed jobs (via the job-dsl plugin) when unneeded jobs are automatically discarded and shelved. The bulk API would avoid avoid flooding the build queue with shelve tasks when there are many jobs to be discarded. See https://github.com/jenkinsci/job-dsl-plugin/pull/1174#discussion_r292322461 for the request.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

[JIRA] (JENKINS-33922) Pipeline support for IRC Notifier

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33922  
 
 
  Pipeline support for IRC Notifier   
 

  
 
 
 
 

 
Change By: 
 Jim Klimov  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 kutzi Jim Klimov  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 instant-messaging-plugin-1.38 ircbot-plugin-2.31  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169411.1459418187000.2646.1565786160973%40Atlassian.JIRA.


[JIRA] (JENKINS-33922) Pipeline support for IRC Notifier

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov commented on  JENKINS-33922  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline support for IRC Notifier   
 

  
 
 
 
 

 
 Thanks to work done by Alexander Komarov for JENKINS-36826 and my subsequent tinkering, this month's releases of instant-messaging-plugin and ircbot-plugin together deliver the `ircNotify` step capability, documented at http://wiki.jenkins-ci.org/display/HUDSON/Instant+Messaging+Plugin and https://wiki.jenkins.io/display/JENKINS/IRC+Plugin respectively.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169411.1459418187000.2634.1565786100470%40Atlassian.JIRA.


[JIRA] (JENKINS-58928) IRC messages prefixed with priority level by default

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58928  
 
 
  IRC messages prefixed with priority level by default   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Jim Klimov  
 
 
Components: 
 instant-messaging-plugin, ircbot-plugin  
 
 
Created: 
 2019-08-14 12:10  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jim Klimov  
 

  
 
 
 
 

 
 Notifications from our Jenkins bot on an IRC channel and in a private chat are prefixed by "(notice)" string. See if it can be removed (perhaps optionally, kept in place by default - maybe someone else relied on it and possibly its other values to filter, highlight, etc. in their IM clients. Not sure at the moment if this applies only to IRC or to other IM protocols as well.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
   

[JIRA] (JENKINS-58921) Extremly slow build after connection to network

2019-08-14 Thread michal.za...@bhge.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michal Zajac updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58921  
 
 
  Extremly slow build after connection to network   
 

  
 
 
 
 

 
Change By: 
 Michal Zajac  
 

  
 
 
 
 

 
 Hi, When I changed network settings of my Virtual Machine to "Bridged: Connected directly to the physical network", jobs is done extremely slow.I have Jenkins server which is installed on Virtual Machine, when the IP of virtual machine is "local" (e.g. 192.168.1.20) jobs are done quite OK (~6minutes per build).But when I changed IP to domain IP (e.g. 3.194.15.23) build are s slow (up to 15 hours!). I changed IP due to fact, that I want to connect with server (from web browser) from every computer in network (not only from VM host computer)I tried almost everything, changed proxy setting, changed Java proxy settings, increase Java buffers, turn off the antyvirus and still nothing.This is not compiler/computer issue, because when I start compiling from command prompt (directly where the Makefile is), clean is perform quick, via Jenkins it stuck first time at:_mkdir -p XmlConfig_and take ~3minutes when in "normal" build it take ~100msany ideas where is the bug?  UPDATE: When I change the IP settings in windows, and when there is no communication to e.g. SVN, compilation works fine  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-49133) dropbox plugin issue

2019-08-14 Thread ond...@amarulasolutions.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ondrej Pik edited a comment on  JENKINS-49133  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: dropbox plugin issue   
 

  
 
 
 
 

 
 Issue reproduced on[Jenkins ver. 2.176.2|https://jenkins.io/][Publish Over Dropbox   |https://wiki.jenkins.io/display/JENKINS/Publish+over+Dropbox+Plugin] [ 1.2.5 |https://jenkins.amarulasolutions.com/pluginManager/plugin/publish-over-dropbox/thirdPartyLicenses]  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187968.1516793809000.2629.1565783942310%40Atlassian.JIRA.


[JIRA] (JENKINS-58927) IRC interaction with the bot in a private chat still requires a nickname prefix

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58927  
 
 
  IRC interaction with the bot in a private chat still requires a nickname prefix   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Jim Klimov  
 
 
Components: 
 instant-messaging-plugin, ircbot-plugin  
 
 
Created: 
 2019-08-14 11:57  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jim Klimov  
 

  
 
 
 
 

 
 It is reasonable to spell out e.g. "jenkins: jobs" in a channel, but just tedious in a private chat already established with the "jenkins" user in a dedicated IRC client window.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-58926) Refactor bot command CLI and results processing (regex filter, line counts) into a single implementation to be shared by different commands

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58926  
 
 
  Refactor bot command CLI and results processing (regex filter, line counts) into a single implementation to be shared by different commands   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Jim Klimov  
 
 
Components: 
 instant-messaging-plugin, ircbot-plugin  
 
 
Created: 
 2019-08-14 11:55  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jim Klimov  
 

  
 
 
 
 

 
 By now there are two copies of CLI loop for argument processing and a regex filter of output lines (and of counting them), in "currentlyBuilding" and "queue" bot commands. With more commands on the plate that could be improved with these features, it makes sense to rearrange the codebase so this filtering and counting can be implemented in one place, with only the command-specific logic preparing a multiline buffer of text - that is then postprocessed and sent to a IM channel(s) by the common code.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 

[JIRA] (JENKINS-58925) Revise interaction with user-based permissions to access (list) jobs, builds, queue items...

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58925  
 
 
  Revise interaction with user-based permissions to access (list) jobs, builds, queue items...   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 kutzi  
 
 
Components: 
 instant-messaging-plugin, ircbot-plugin  
 
 
Created: 
 2019-08-14 11:43  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jim Klimov  
 

  
 
 
 
 

 
 I am not sure whether there is much awareness in the IM plugins about users being not allowed to see some jobs (either for multi-tenancy security, or grouped into teams just to limit the visibility and not be overwhelmed). In order to decide whether some development in this area is worth planning, makes sense to check the code and test behaviors first, on setups with different authorization strategies (e.g. added via extra plugins).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
   

[JIRA] (JENKINS-30124) IRC Plugin bot does not see the Folder (CloudBees Folders Plugin) jobs

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov commented on  JENKINS-30124  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IRC Plugin bot does not see the Folder (CloudBees Folders Plugin) jobs   
 

  
 
 
 
 

 
 Also, with pipelines (MultiBranch jobs, with configs generated for many branches and PRs across many repos in several organizations our local Jenkins master tracks), a full "jobs" listing for us would be impractical at several thousand lines long (and throttled IIRC to 0.5sec per line posting to an IRC server to avoid flood controls killing the session) so it was not a priority for me to address in our deployment.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164706.1440502741000.2623.1565782800198%40Atlassian.JIRA.


[JIRA] (JENKINS-30124) IRC Plugin bot does not see the Folder (CloudBees Folders Plugin) jobs

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30124  
 
 
  IRC Plugin bot does not see the Folder (CloudBees Folders Plugin) jobs   
 

  
 
 
 
 

 
Change By: 
 Jim Klimov  
 
 
Component/s: 
 instant-messaging-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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164706.1440502741000.2618.1565782620597%40Atlassian.JIRA.


[JIRA] (JENKINS-58924) job.allBuilds points to wrong URL when called from a job inside a folderJob

2019-08-14 Thread niclas.lindb...@nillsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Niclas Lindberg created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58924  
 
 
  job.allBuilds points to wrong URL when called from a job inside a folderJob   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Karl-Heinz Marbaise  
 
 
Components: 
 java-client-api  
 
 
Created: 
 2019-08-14 11:36  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Niclas Lindberg  
 

  
 
 
 
 

 
 When a job is residing in a folderJob then the API url to the job in job.allBuilds() points to /job/SIMPLE_JOB_NAME/api/json which causes a 404. Instead the job.allBuilds() should point to /job/FOLDER_JOB_NAME/job/SIMPLE_JOB_NAME/api/json. Code: JobWithDetails#127  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
   

[JIRA] (JENKINS-30124) IRC Plugin bot does not see the Folder (CloudBees Folders Plugin) jobs

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov commented on  JENKINS-30124  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IRC Plugin bot does not see the Folder (CloudBees Folders Plugin) jobs   
 

  
 
 
 
 

 
 This month new versions of ircbot and instant-messaging-plugin were released, which in particular added awareness about pipeline jobs to the "queue" and "currentlyBuilding" commands, and essence the Java-side change for the plugin code was that the inheritance tree of classes was different so new `import` clauses to add awareness and `instanceof` calls to match a job type were the key to list e.g. pipeline jobs and not only the legacy freestyle ones. I did not use the folder plugin yet so can't say if its classes are part of the newly added tree (can you please check it out?), or if a similar and relatively simple change has to be made in a subsequent release. Also, by now only those two commands were changed, so the issue of adding such support to "jobs" (or other mass-management commands, for that matter) still stands indeed. And a counter of output hits too, and a regex filter, like in these two commands  Maybe some refactoring is due to share such 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 jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164706.1440502741000.2615.1565782620392%40Atlassian.JIRA.


[JIRA] (TEST-173) Automation

2019-08-14 Thread thulasy.mai...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thulasy R created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 test /  TEST-173  
 
 
  Automation   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 foo14  
 
 
Created: 
 2019-08-14 11:34  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Thulasy R  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201267.1565782466000.2612.1565782500199%40Atlassian.JIRA.


[JIRA] (JENKINS-58923) Cannot browse result of tests when publishing several fitnesse result files on Windows

2019-08-14 Thread johannm...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Johann Moro updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58923  
 
 
  Cannot browse result of tests when publishing several fitnesse result files on Windows   
 

  
 
 
 
 

 
Change By: 
 Johann Moro  
 

  
 
 
 
 

 
 When you publish more than one fitnesse xml results in this way (pipeline):{code}step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml']){code}On a linux agent, if you go to _FitNesse Results_, you get the links for the two results and you can click on them to browse them.The link resolves correctly to:http://localhost:8080/job/MyJob/5/fitnesseReport/fitnesse_linux.xml  !linux.png!  But on a Windows agent, the link points to a local disk folder as opposed to a http URLC:\jenkins\workspaces\MyJob\fitnesseReport/fitnesse_linux.xml  !windows.png!This means that the link does not resolve when Jenkins is running (as expected) on a remote machine.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201266.1565782125000.2610.1565782200403%40Atlassian.JIRA.


[JIRA] (JENKINS-58923) Cannot browse result of tests when publishing several fitnesse result files on Windows

2019-08-14 Thread johannm...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Johann Moro created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58923  
 
 
  Cannot browse result of tests when publishing several fitnesse result files on Windows   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 linux.png, windows.png  
 
 
Components: 
 fitnesse-plugin  
 
 
Created: 
 2019-08-14 11:28  
 
 
Labels: 
 plugin  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Johann Moro  
 

  
 
 
 
 

 
 When you publish more than one fitnesse xml results in this way (pipeline): 

 
step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml']) 

 On a linux agent, if you go to FitNesse Results, you get the links for the two results and you can click on them to browse them. The link resolves correctly to: http://localhost:8080/job/MyJob/5/fitnesseReport/fitnesse_linux.xml But on a Windows agent, the link points to a local disk folder as opposed to a http URL C:\jenkins\workspaces\MyJob\fitnesseReport/fitnesse_linux.xml This means that the link does not resolve when Jenkins is running (as expected) on a remote machine.  
 

  
 
 
 
 
 

[JIRA] (JENKINS-34903) IRC plugin: custom post-build message

2019-08-14 Thread jimkli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Klimov commented on  JENKINS-34903  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IRC plugin: custom post-build message   
 

  
 
 
 
 

 
 In this month's release of the two plugins, there are a couple of features that can help: 
 
adding an "extra message" that should work in the legacy and pipeline invocations, which is a string you can provide and will be attached to the standard build starting/completed notifications. Your job could generate it somehow (easier in a scripted pipeline). Not sure if it supports groovy variable expansion like many other plugins do, but I'd assume that is relatively easy to research and implement if needed. This might be flexible enough for passing the extra data. 
more for the pipeline context, calling `ircNotify customMessage:"Some text"` should just post that message verbatim (which again you can create in the pipeline) at that point in execution 
  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170569.1463533039000.2608.1565781780164%40Atlassian.JIRA.


[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook

2019-08-14 Thread christian.koeb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Köberl commented on  JENKINS-58919  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: DateTimeParseException on MR web hook   
 

  
 
 
 
 

 
 Yes it worked with GitLab 12.0.x. Anyway the ISO date "2018-03-12T10:16:46+07:00"  is valid and should be accepted.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201262.156577292.2605.1565781720239%40Atlassian.JIRA.


  1   2   >