date:20190809

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-26354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: First time build does not show changelog   
 

  
 
 
 
 

 
 It is resolved as "Won't Fix".      Refer to [the earlier discussions|https://issues.jenkins-ci.org/browse/JENKINS-26354?focusedCommentId=364445&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-364445] for more details.   There is [this pull request|https://github.com/jenkinsci/git-plugin/pull/637] that attempts to apply heuristics to decide which change should be used as the basis for a changeset.  You're welcome to propose further changes to it to resolve the issues that are discussed in it.  
 

  
 
 
 
 

 
 
 

 
 
 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.160018.1420800265000.206.1565397300389%40Atlassian.JIRA.

[JIRA] (JENKINS-26354) First time build does not show changelog

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-26354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: First time build does not show changelog   
 

  
 
 
 
 

 
 It is resolved as "Won't Fix".  There is this pull request that attempts to apply heuristics to decide which change should be used as the basis for a changeset. You're welcome to propose further changes to it to resolve the issues that are discussed in it.  
 

  
 
 
 
 

 
 
 

 
 
 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.160018.1420800265000.194.1565397180447%40Atlassian.JIRA.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Joel Brown  
 
 
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.201132.1565041263000.188.1565393460371%40Atlassian.JIRA.

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

2019-08-09 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   
 

  
 
 
 
 

 
 I know this issue is old, but I think it's repro'ing for me on Jenkins 2.164.3 with P4 Plugin 1.9.7. The key difference is that I'm loading  both  a  global library and a  DYNAMIC library. I don't know if that's relevant. Near the top of my pipeline, I load a library with this snippet:{code:java} library 'global-library@now' String stream_name = 'stream_name'String client_name = "jenkins-${env.JOB_NAME}-${stream_name}-library"String library_source = "//depot/${stream_name}/Jenkinsfile/lib/..."library(identifier: stream_name + '-library@now', retriever: legacySCM([$class: 'PerforceScm', credential: 'p4creds',populate: [$class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false], workspace: [$class: 'ManualWorkspaceImpl', charset: 'none', name: client_name,pinHost: false, spec: [allwrite: true, clobber: false, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, streamName: '', view: "${library_source} //${client_name}/..."]]]))// rest of the pipeline{code}This works great in isolation. But my job is failing intermittently with this error. It seems to happen most (but not always!) when multiple builds are triggered at the same time.{code:xml}P4 Task: reverting all pending and shelved revisions p4 revert d:\JenkinsHome\jobs\stream_name\workspac___ -p4 revert d:\JenkinsHome\jobs\stream_name\jobs\stream_name-build\workspace_libs\stream_name-library_2/...ERROR: P4: Task Exception: hudson.AbortException: P4JAVA: Error(s):Path 'd:\JenkinsHome\jobs\stream_name\workspace_libs\stream_name-library_2/...' is not under client's root 'd:\JenkinsHome\jobs\stream_name\workspace_libs\stream_name-library'.{code} The global library works fine and never seems to have a problem. The 'stream library' that I  dynamically load occasionally throws an error syncing on the master.I  can't figure out what logic it uses to append "_2" to the folder name, nor why it's failing to update the p4 client accordingly. It also seems like a bug that one path ends with "/..." while the other does not.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown edited a comment on  JENKINS-58820  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: scan Multibranch pipeline does not detect new streams when file is branch   
 

  
 
 
 
 

 
 [~newtopian] What type of Stream is this undetected stream?   Development?  Release?  Task? I can reproduce this with a Task stream.   Please confirm you have the problem with Task Streams - or other.  
 

  
 
 
 
 

 
 
 

 
 
 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.179.1565390520160%40Atlassian.JIRA.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown commented on  JENKINS-58820  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: scan Multibranch pipeline does not detect new streams when file is branch   
 

  
 
 
 
 

 
 Eric Daigneault What type of Stream is this undetected stream?   Development?  Release?  Task?  
 

  
 
 
 
 

 
 
 

 
 
 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.177.1565389620111%40Atlassian.JIRA.

[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

2019-08-09 Thread joshua.berge...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Bergeron edited a comment on  JENKINS-58810  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed   
 

  
 
 
 
 

 
 I have also recently been experiencing this and it has been driving me crazy! It started happening in the last week and has been intermittent  - both on the build notification end and build trigger side of things .  Glad to find others running into similar issues.    
 

  
 
 
 
 

 
 
 

 
 
 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.201122.1565008163000.170.1565388360251%40Atlassian.JIRA.

[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

2019-08-09 Thread joshua.berge...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Bergeron edited a comment on  JENKINS-58810  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed   
 

  
 
 
 
 

 
 I have also recently been experiencing this and it has been driving  be  me  crazy!  It started happening in the last week and has been intermittent. Glad to find others running into similar issues.   
 

  
 
 
 
 

 
 
 

 
 
 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.201122.1565008163000.163.1565388060248%40Atlassian.JIRA.

[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning

2019-08-09 Thread spars...@griddynamics.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergei Parshev edited a comment on  JENKINS-58620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MPL shared library logic execution caused CPS mismatch warning   
 

  
 
 
 
 

 
 I think there is two ways to fix the issue:# Prepare  modification  overload  for  [  evaluate  step  function|https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScript.java#L179]  to be able to execute groovy logic with providing the src path and bindings# Prepare an exception for executing CpsGroovyShell.evaluate https://github.com/cloudbees/groovy-cps/pull/99[~jglick] what do you think will be better? Easier for sure prepare an exception hack, but probably that will be appropriate to modify the evaluate step?Or maybe even prepare `module` step and put such MPL functionality into the Jenkins itself? I'm just not sure that it's a good idea because probably I will need to prepare an additional plugin and I would avoid that and keep minimal requirements for the MPL library.  
 

  
 
 
 
 

 
 
 

 
 
 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.200786.1563913328000.161.1565388000317%40Atlassian.JIRA.

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

2019-08-09 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   
 

  
 
 
 
 

 
 I know this issue is old, but I think it's repro'ing for me on Jenkins 2.164.3 with P4 Plugin 1.9.7. The key difference is that I'm loading a DYNAMIC library. I don't know if that's relevant. Near the top of my pipeline, I load a library with this snippet:{code:java}String stream_name = 'stream_name'String client_name = "jenkins-${env.JOB_NAME}-${stream_name}-library"String library_source = "//depot/${stream_name}/Jenkinsfile/lib/..."library(identifier: stream_name + '-library@now', retriever: legacySCM([$class: 'PerforceScm', credential: 'p4creds',populate: [$class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false], workspace: [$class: 'ManualWorkspaceImpl', charset: 'none', name: client_name,pinHost: false, spec: [allwrite: true, clobber: false, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, streamName: '', view: "${library_source} //${client_name}/..."]]]))// rest of the pipeline{code}This works great in isolation. But my job is failing intermittently with this error. It seems to happen most (but not always!) when multiple builds are triggered at the same time.{code :xml }P4 Task: reverting all pending and shelved revisions p4 revert d:\JenkinsHome\jobs\stream_name\workspac___ -p4 revert d:\JenkinsHome\jobs\stream_name\jobs\stream_name-build\workspace_libs\stream_name-library_2/... ERROR: P4: Task Exception: hudson.AbortException: P4JAVA: Error(s): Path 'd:\JenkinsHome\jobs\stream_name\workspace_libs\stream_name-library_2/...' is not under client's root 'd:\JenkinsHome\jobs\stream_name\workspace_libs\stream_name-library'.{code}I can't figure out what logic it uses to append "_2" to the folder name, nor why it's failing to update the p4 client accordingly. It also seems like a bug that one path ends with "/..." while the other does not.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning

2019-08-09 Thread spars...@griddynamics.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergei Parshev commented on  JENKINS-58620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MPL shared library logic execution caused CPS mismatch warning   
 

  
 
 
 
 

 
 I think there is two ways to fix the issue: 
 
Prepare modification for evaluate step to be able to execute groovy logic with providing the src path and bindings 
Prepare an exception for executing CpsGroovyShell.evaluate https://github.com/cloudbees/groovy-cps/pull/99 
 Jesse Glick what do you think will be better? Easier for sure prepare an exception hack, but probably that will be appropriate to modify the evaluate step? Or maybe even prepare `module` step and put such MPL functionality into the Jenkins itself? I'm just not sure that it's a good idea because probably I will need to prepare an additional plugin and I would avoid that and keep minimal requirements for the MPL library.  
 

  
 
 
 
 

 
 
 

 
 
 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.200786.1563913328000.151.1565387460163%40Atlassian.JIRA.

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

2019-08-09 Thread j.sp...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jay Spang reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I know this issue is old, but I think it's repro'ing for me on Jenkins 2.164.3 with P4 Plugin 1.9.7.  The key difference is that I'm loading a DYNAMIC library. I don't know if that's relevant. Near the top of my pipeline, I load a library with this snippet: 

 

String stream_name = 'stream_name'
String client_name = "jenkins-${env.JOB_NAME}-${stream_name}-library"
String library_source = "//depot/${stream_name}/Jenkinsfile/lib/..."

library(
identifier: stream_name + '-library@now', 
retriever: legacySCM(
[
$class: 'PerforceScm', credential: 'p4creds',
populate: [
$class: 'AutoCleanImpl', 
delete: true, 
modtime: false, 
parallel: [
enable: false, 
minbytes: '1024', 
minfiles: '1', 
threads: '4'
], 
pin: '', 
quiet: true, 
replace: true, 
tidy: false
], 
workspace: [
$class: 'ManualWorkspaceImpl', 
charset: 'none', 
name: client_name,
pinHost: false, 
spec: [
allwrite: true, 
clobber: false, 
compress: false, 
line: 'LOCAL', 
locked: false, 
modtime: false, 
rmdir: false, 
streamName: '', 
view: "${library_source} //${client_name}/..."
]
]
]
)
)

// rest of the pipeline
 

 This works great in isolation. But my job is failing intermittently with this error. It seems to happen most (but not always!) when multiple builds are triggered at the same time. 

 

P4 Task: reverting all pending and shelved revisions.
... p4 revert d:\JenkinsHome\jobs\stream_name\workspac___
 -
p4 revert d:\JenkinsHome\jobs\stream_name\jobs\stream_name-build\workspace_libs\stream_name-library_2/...

Path 'd:\JenkinsHome\jobs\stream_name\workspace_libs\stream_name-library_2/...' is not under client's root 'd:\JenkinsHome\jobs\stream_name\workspace_libs\stream_name-library'.
 

 I can't figure out what logic it uses to append "_2" to the folder name, nor why it's failing to update the p4 client accordingly. It also seems like a bug that one path ends with "/..." while the other does not.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50975  
 
 
  Concurrent Groovy Shared Library syncs on different jobs use same workspace root

[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning

2019-08-09 Thread spars...@griddynamics.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergei Parshev commented on  JENKINS-58620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MPL shared library logic execution caused CPS mismatch warning   
 

  
 
 
 
 

 
 Hi Jesse Glick, ok I got it - if it's not about security, but about a simple example to show that we need an exception in the warning logic: I tested with turned off sandbox - found a minimal implementation to show the issue: 
 
Jenkinsfile: 

 
org.jenkinsci.plugins.workflow.cps.CpsThread.current().getExecution().getShell().evaluate('echo "OK"', 'X.groovy')
 

 
 
 
Output: 

 
Started by user unknown or anonymous
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
expected to call org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.evaluate but wound up catching X.run; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/
[Pipeline] echo
OK
[Pipeline] End of Pipeline
Finished: 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

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown assigned an issue to Joel Brown  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Joel Brown  
 
 
Assignee: 
 Joel Brown  
 

  
 
 
 
 

 
 
 

 
 
 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.129.1565385780140%40Atlassian.JIRA.

[JIRA] (JENKINS-50548) Shared Library should be allowed to declare reusable stages

2019-08-09 Thread alv...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Alvizu commented on  JENKINS-50548  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shared Library should be allowed to declare reusable stages   
 

  
 
 
 
 

 
 For anyone else who runs into this: Andrew closed this as 'FIxed but unreleased' but with a resolution of 'Duplicate'.   The duplicate issue is JENKINS-49135 and track there  
 

  
 
 
 
 

 
 
 

 
 
 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.189617.1522766954000.84.1565385121129%40Atlassian.JIRA.

[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

2019-08-09 Thread joshua.berge...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Bergeron commented on  JENKINS-58810  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed   
 

  
 
 
 
 

 
 I have also recently been experiencing this and it has been driving be crazy!  
 

  
 
 
 
 

 
 
 

 
 
 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.201122.1565008163000.68.1565384040286%40Atlassian.JIRA.

[JIRA] (JENKINS-58880) NPE from support core plugin attaching bundle

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58880  
 
 
  NPE from support core plugin attaching bundle   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Emilio Escobar   
 
 
Components: 
 support-core-plugin  
 
 
Created: 
 2019-08-09 20:21  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mark Waite  
 

  
 
 
 
 

 
 I encountered a support core null pointer exception while evaluating other things.  The null pointer exception stack trace was: 

 
Aug 09, 2019 7:16:52 PM com.cloudbees.jenkins.support.SupportPlugin writeBundle
WARNING: Could not attach ''nodes.md'' to support bundle
java.lang.NullPointerException
at com.cloudbees.jenkins.support.util.Markdown.escapeBacktick(Markdown.java:17)
at com.cloudbees.jenkins.support.impl.AboutJenkins$NodesContent.printTo(AboutJenkins.java:877)
at com.cloudbees.jenkins.support.api.PrintedContent.writeTo(PrintedContent.java:56)
at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:316)
at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:278)
at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl.lambda$doRun$0(SupportPlugin.java:820)
at java.lang.Thread.run(Thread.java:748)

[JIRA] (JENKINS-58853) nexusPublisher hangs when uploading multiple large files to Nexus 3

2019-08-09 Thread xxx...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pbc pbc commented on  JENKINS-58853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: nexusPublisher hangs when uploading multiple large files to Nexus 3   
 

  
 
 
 
 

 
 Hi Justin Young  Opened on Sonatype Jira as per your request at https://issues.sonatype.org/browse/NEXUS-20859 .  Should we close the one we have here?  
 

  
 
 
 
 

 
 
 

 
 
 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.201168.1565216757000.63.1565381160178%40Atlassian.JIRA.

[JIRA] (JENKINS-58879) EC2 plugin queue locks have resurfaced

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joyce Yee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58879  
 
 
  EC2 plugin queue locks have resurfaced   
 

  
 
 
 
 

 
Change By: 
 Joyce Yee  
 

  
 
 
 
 

 
 After upgrading to 1.44.1, we are observing the return of long-standing queue locking as described in this PR ([https://github.com/jenkinsci/ec2-plugin/pull/346]).It looks like the issue is reintroduced within the scope of this  commit ( [ https://github.com/jenkinsci/ec2-plugin/ commit /4973e9f4371b25abdcf78605380e12e57be336aa | #diff-e577be8c21e85e6a1f2ff095f583f5d2R237] ) .I think it's because  since  the `clock` is  now  only  instantiated within  the queue lock `readResolve` , and  therefore halts  not in  the  ability  constructor of `EC2RetentionStrategy`, the problem is re-introduced  for  workers that are being newly created (not for workers that were persisted from XML). The clock may not exist when  the ` EC2RetentionStrategy check `  method is invoked, which prevents the strategy's ability  to  to  skip the `NodeProvisioner.update()` cycle triggered with `internalCheck`, if the last check happened < 1 minute ago.    The solution is probably to instantiate the clock in both the constructor and `readResolve`. Downgrading back down to version `1.42` where we patch in the code introduced in the original commit ([https://github.com/jenkinsci/ec2-plugin/pull/346]) fixes the issue and we no longer observe these frequently occurring queue locks.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-26354) First time build does not show changelog

2019-08-09 Thread tamerl...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 ipleten commented on  JENKINS-26354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: First time build does not show changelog   
 

  
 
 
 
 

 
 Is that really resolved? The problem is really serious  we can't use 'changeset' in when condition with branches at all.  
 

  
 
 
 
 

 
 
 

 
 
 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.160018.1420800265000.38.1565379120444%40Atlassian.JIRA.

[JIRA] (JENKINS-58879) EC2 plugin queue locks have resurfaced

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joyce Yee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58879  
 
 
  EC2 plugin queue locks have resurfaced   
 

  
 
 
 
 

 
Change By: 
 Joyce Yee  
 

  
 
 
 
 

 
 After upgrading to 1.44.1, we are observing the return of long-standing queue locking as described in this PR ([https://github.com/jenkinsci/ec2-plugin/pull/346]).It looks like the issue is reintroduced within the scope of this  commit (  [ https://github.com/jenkinsci/ec2-plugin/ commit | /4973e9f4371b25abdcf78605380e12e57be336aa #diff-e577be8c21e85e6a1f2ff095f583f5d2R237] ) .I think it's because the `clock` is now instantiated within the queue lock, and therefore halts the ability for the `EC2RetentionStrategy` to skip the `NodeProvisioner.update()` cycle triggered with `internalCheck`, if the last check happened < 1 minute ago. Downgrading back down to version `1.42` where we patch in the code introduced in the original commit ([https://github.com/jenkinsci/ec2-plugin/pull/346]) fixes the issue and we no longer observe these frequently occurring queue locks.   
 

  
 
 
 
 

 
 
 

 
 
 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/j

[JIRA] (JENKINS-58879) EC2 plugin queue locks have resurfaced

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joyce Yee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58879  
 
 
  EC2 plugin queue locks have resurfaced   
 

  
 
 
 
 

 
Change By: 
 Joyce Yee  
 

  
 
 
 
 

 
 After upgrading to 1.44.1, we are observing the return of long-standing queue locking as described in this PR ([https://github.com/jenkinsci/ec2-plugin/pull/346]).It looks like the issue is reintroduced within the scope of this [commit|#diff-e577be8c21e85e6a1f2ff095f583f5d2R237] ] .I think it's because the `clock` is now instantiated within the queue lock, and therefore halts the ability for the `EC2RetentionStrategy` to skip the `NodeProvisioner.update()` cycle triggered with `internalCheck`, if the last check happened < 1 minute ago. Downgrading back down to version `1.42` where we patch in the code introduced in the original commit ([https://github.com/jenkinsci/ec2-plugin/pull/346]) fixes the issue and we no longer observe these frequently occurring queue locks.   
 

  
 
 
 
 

 
 
 

 
 
 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.201212.1565377068000.33.1565377200401%40Atlassian.JIRA.

[JIRA] (JENKINS-58879) EC2 plugin queue locks have resurfaced

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joyce Yee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58879  
 
 
  EC2 plugin queue locks have resurfaced   
 

  
 
 
 
 

 
Change By: 
 Joyce Yee  
 

  
 
 
 
 

 
 After upgrading to 1.44.1, we are observing the return of long-standing queue locking as described in this  [ PR |  ( [https://github.com/jenkinsci/ec2-plugin/pull/346] ] ) .It looks like the issue is reintroduced within the scope of this [commit| [https://github.com/jenkinsci/ec2-plugin/commit/4973e9f4371b25abdcf78605380e12e57be336aa #diff-e577be8c21e85e6a1f2ff095f583f5d2R237]].I think it's because the `clock` is now instantiated within the queue lock, and therefore halts the ability for the `EC2RetentionStrategy` to skip the `NodeProvisioner.update()` cycle triggered with `internalCheck`, if the last check happened < 1 minute ago. Downgrading back down to version `1.42` where we patch in the code introduced in the original commit ([https://github.com/jenkinsci/ec2-plugin/pull/346]) fixes the issue and we no longer observe these frequently occurring queue locks.   
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-58879) EC2 plugin queue locks have resurfaced

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joyce Yee created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58879  
 
 
  EC2 plugin queue locks have resurfaced   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 FABRIZIO MANFREDI  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2019-08-09 18:57  
 
 
Environment: 
 Jenkins 2.186 (from the jenkins/jenkins:2.186 docker image)  Amazon EC2 plugin (1.44.1)  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Joyce Yee  
 

  
 
 
 
 

 
 After upgrading to 1.44.1, we are observing the return of long-standing queue locking as described in this [PR|https://github.com/jenkinsci/ec2-plugin/pull/346]. It looks like the issue is reintroduced within the scope of this commit. I think it's because the `clock` is now instantiated within the queue lock, and therefore halts the ability for the `EC2RetentionStrategy` to skip the `NodeProvisioner.update()` cycle triggered with `internalCheck`, if the last check happened < 1 minute ago.  Downgrading back down to version `1.42` where we patch in the code introduced in the original commit (https://github.com/jenkinsci/ec2-plugin/pull/346) fixes the issue and we no longer observe these frequently occurring queue locks.

[JIRA] (JENKINS-58878) withCredentials hangs

2019-08-09 Thread jonat...@riv.al (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan B created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58878  
 
 
  withCredentials hangs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 credentials-binding-plugin  
 
 
Created: 
 2019-08-09 18:10  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jonathan B  
 

  
 
 
 
 

 
 On Jenkins 2.176.2 and credentials-binding-plugin 1.19, the following pipeline will intermittently hang: ``` pipeline { agent any  stages { stage('bug') { steps { script { for (int i = 0; i < 100; i++) { withEnv(['A=b']) { withCredentials([]) { sh "echo hello ${i}" } } } } } } } } ``` The build log looks like this: ``` ... [Pipeline] withEnv [Pipeline] { [Pipeline] withCredentials ``` until the build is aborted. I've seen two independent things that both seem to work around the problem: 
 
flipping so `withCredentials([])` wraps `withEnv([...])` seems to avoid the hang. 
ensuring there's always at least one item in the `withCredentials` list parameter seems to avoid the hang. 
 We run into this in a pipeline where the parameter to withCredentials varies by projects, and sometimes is an empty list.

[JIRA] (JENKINS-58878) withCredentials hangs

2019-08-09 Thread jonat...@riv.al (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan B updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58878  
 
 
  withCredentials hangs   
 

  
 
 
 
 

 
Change By: 
 Jonathan B  
 

  
 
 
 
 

 
 On Jenkins 2.176.2 and credentials-binding-plugin 1.19, the following pipeline will intermittently hang: ``` {code} pipeline {agent anystages {stage('bug') {steps {script {for (int i = 0; i < 100; i++) { withEnv(['A=b']) { withCredentials([]) { sh "echo hello ${i}" } }}}}}}} ``` {code} The build log looks like this: ``` {code} ...[Pipeline] withEnv[Pipeline] {[Pipeline] withCredentials ``` {code} until the build is aborted.I've seen two independent things that both seem to work around the problem:* flipping so `withCredentials([])` wraps `withEnv([...])` seems to avoid the hang.* ensuring there's always at least one item in the `withCredentials` list parameter seems to avoid the hang.We run into this in a pipeline where the parameter to withCredentials varies by projects, and sometimes is an empty list.  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-58863) Builds cannot start after upgrading

2019-08-09 Thread fl...@itnews-bg.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Todorov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58863  
 
 
  Builds cannot start after upgrading   
 

  
 
 
 
 

 
Change By: 
 Steve Todorov  
 
 
Attachment: 
 jenkins.log  
 

  
 
 
 
 

 
 
 

 
 
 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.201178.1565282292000.16.1565372040365%40Atlassian.JIRA.

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

2019-08-09 Thread kshu...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-58862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Branch Source Plugin always references https://api.github.com   
 

  
 
 
 
 

 
 Thanks, William Gillaspy. This is very helpful. The credentials thing is something I noticed as well. That might be a distinct problem from what you originally reported. Both are legit and need to be addresed, so thank you for the detailed report. We'll keep you updated here on this ticket.  
 

  
 
 
 
 

 
 
 

 
 
 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.12.1565371920301%40Atlassian.JIRA.

[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

2019-08-09 Thread joao.admira...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joao Miranda commented on  JENKINS-58810  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed   
 

  
 
 
 
 

 
 Same problem here. It's very inconvenient! Please, anybody got fix this?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201122.1565008163000.6.1565370360355%40Atlassian.JIRA.

[JIRA] (JENKINS-53800) Whitelisting misc. methods

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Hari Dara Updated. Are you sure you don't have access to modify the ticket yourself when logged in? I don't think there is anything special about my account, you just need to be logged in, then click "Workflow", then "Resolved".  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53800  
 
 
  Whitelisting misc. methods   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 script-security 1.47  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-57434) Unable to add or edit roles

2019-08-09 Thread nathan.vahrenb...@cerner.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nathan Vahrenberg commented on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 Thanks for diving into it Nick Johns! I'm glad to know where it was coming from before it mysteriously disappeared I installed the updated github-oauth-plugin today, and it looks like the issue is resolved on my end as well. Oleg Nenashev I think we could close this out at this point and attribute it to JENKINS-57154  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.11425.1565368920359%40Atlassian.JIRA.

[JIRA] (JENKINS-53800) Whitelisting misc. methods

2019-08-09 Thread harid...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara commented on  JENKINS-53800  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Whitelisting misc. methods   
 

  
 
 
 
 

 
 Devin Nusbaum: Could you update the status for this one too?  
 

  
 
 
 
 

 
 
 

 
 
 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.194313.1537981345000.11417.1565368200057%40Atlassian.JIRA.

[JIRA] (JENKINS-58867) Jenkins with proxy doesn't work

2019-08-09 Thread renan-k...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Renan Lopes edited a comment on  JENKINS-58867  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins with proxy doesn't work   
 

  
 
 
 
 

 
 Mr.[~danielbeck]Yes, I'm sure that it is version 2.189. I'm using the .war provided on this link: [http://mirrors.jenkins.io/war/latest/jenkins.war] newSAVECONTINUEview saved words →Don't translate on double-click Don't show floating button Check the localized version of the site  No Internet Connection    
 

  
 
 
 
 

 
 
 

 
 
 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.201184.1565291091000.11409.1565366880193%40Atlassian.JIRA.

[JIRA] (JENKINS-58867) Jenkins with proxy doesn't work

2019-08-09 Thread renan-k...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Renan Lopes edited a comment on  JENKINS-58867  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins with proxy doesn't work   
 

  
 
 
 
 

 
 Mr.[~danielbeck]Yes, I'm sure that it is version 2.189. I'm using the .war provided  from  on  this link: [http://mirrors.jenkins.io/war/latest/jenkins.war] newSAVECONTINUEview saved words →Don't translate on double-click Don't show floating button Check the localized version of the site  No Internet Connection    
 

  
 
 
 
 

 
 
 

 
 
 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.201184.1565291091000.11408.1565366880178%40Atlassian.JIRA.

[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-58595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: rssAll feed doesn't have published field after 2.176.2 upgrade   
 

  
 
 
 
 

 
 Added PR to fix this for both RSS and Atom. There were no other views that removed the h variable in SECURITY-534.  
 

  
 
 
 
 

 
 
 

 
 
 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.200752.1563783758000.11404.1565365020143%40Atlassian.JIRA.

[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker updated  JENKINS-58595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58595  
 
 
  rssAll feed doesn't have published field after 2.176.2 upgrade   
 

  
 
 
 
 

 
Change By: 
 Matt Sicker  
 
 
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.200752.1563783758000.11400.1565364960806%40Atlassian.JIRA.

[JIRA] (JENKINS-56483) Limit local storage utilization

2019-08-09 Thread jenkins-ci....@meneguello.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno Meneguello commented on  JENKINS-56483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Limit local storage utilization   
 

  
 
 
 
 

 
 https://kubernetes.io/docs/concepts/policy/limit-range/  
 

  
 
 
 
 

 
 
 

 
 
 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.198084.1552057119000.11398.1565364600124%40Atlassian.JIRA.

[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker started work on  JENKINS-58595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Matt Sicker  
 
 
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.200752.1563783758000.11394.1565364180825%40Atlassian.JIRA.

[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker assigned an issue to Matt Sicker  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58595  
 
 
  rssAll feed doesn't have published field after 2.176.2 upgrade   
 

  
 
 
 
 

 
Change By: 
 Matt Sicker  
 
 
Assignee: 
 Matt Sicker  
 

  
 
 
 
 

 
 
 

 
 
 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.200752.1563783758000.11392.1565364180796%40Atlassian.JIRA.

[JIRA] (JENKINS-58877) Allow server select in job based on server configuration

2019-08-09 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58877  
 
 
  Allow server select in job based on server configuration   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Parichay Barpanda  
 
 
Components: 
 gitlab-branch-source-plugin  
 
 
Created: 
 2019-08-09 15:05  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Parichay Barpanda  
 

  
 
 
 
 

 
 Suggested by Joseph Petersen. Allow user to have option to select server if there are more than 1 endpoints configured. See Bitbucket Branch Source Plugin.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Gillaspy commented on  JENKINS-58862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Branch Source Plugin always references https://api.github.com   
 

  
 
 
 
 

 
 Karl Shultz I'm using the "Clone or Download" button and copying the "Clone with HTTPS" url of the repository. Example: https://git.company.com/TheOrg/TheProject.git  
 

  
 
 
 
 

 
 
 

 
 
 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.11387.1565363100168%40Atlassian.JIRA.

[JIRA] (JENKINS-58876) System.currentTimeSeconds not found in pipeline

2019-08-09 Thread ja...@howeswho.co.uk (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Howe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58876  
 
 
  System.currentTimeSeconds not found in pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 script-security-plugin  
 
 
Created: 
 2019-08-09 14:59  
 
 
Environment: 
 Jenkins 2.176.2  Script Security Plugin 1.62  Pipeline: Groovy 2.73   
 
 
Labels: 
 pipeline  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Howe  
 

  
 
 
 
 

 
 It works in the global script console but not in a (multi-branch) pipeline. No pending approval appears either. 

 
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: No such static method found: staticMethod java.lang.System currentTimeSeconds
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:182)
	at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:189)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:193)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:100)
	at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
	at WorkflowScript.run(WorkflowScript)
	at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:454)
	at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.callClosureForMapEntry(CpsDefaultGroovyMethods:5226)
	at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.collect(CpsDefaultGroovyMethods:3446)
	at com.cloudbe

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

2019-08-09 Thread kshu...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 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.11379.1565362620362%40Atlassian.JIRA.

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

2019-08-09 Thread kshu...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-58862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Branch Source Plugin always references https://api.github.com   
 

  
 
 
 
 

 
 William Gillaspy - when you supply your remote repository URL via the new UI, are you giving it an API URL (e.g., https://api.your-ghe-server.com/api/v3/...) or the more typical URL that you'd get from the "Clone or download" button from the GitHub Enterprise UI?  There's definitely a problem here. Probably two. Just trying to narrow down the scope of it.  
 

  
 
 
 
 

 
 
 

 
 
 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.11377.1565362560358%40Atlassian.JIRA.

[JIRA] (JENKINS-58866) Splunk plugin not sending json files

2019-08-09 Thread xiao...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ted commented on  JENKINS-58866  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Splunk plugin not sending json files   
 

  
 
 
 
 

 
 could you please add below conf to $SPLUNK_HOME/etc/system/local/limits.conf 

 

[http_input]
# max request content length, bytes
max_content_length = 1000
 

 1.7.2 will send json file in single request instead of line by line so it can be parsed correctly, I guess your splunk http event collector discarded the input for length limit  
 

  
 
 
 
 

 
 
 

 
 
 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.201183.1565289754000.11372.1565362440145%40Atlassian.JIRA.

[JIRA] (JENKINS-58081) Upgrade Kafka version

2019-08-09 Thread vulongv...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen resolved as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58081  
 
 
  Upgrade Kafka version   
 

  
 
 
 
 

 
Change By: 
 Long Nguyen  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 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.200106.1560879624000.11370.1565361840116%40Atlassian.JIRA.

[JIRA] (JENKINS-58867) Jenkins with proxy doesn't work

2019-08-09 Thread renan-k...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Renan Lopes commented on  JENKINS-58867  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins with proxy doesn't work   
 

  
 
 
 
 

 
 Mr.Daniel Beck Yes, I'm sure that it is version 2.189. I'm using the .war provided from this link: http://mirrors.jenkins.io/war/latest/jenkins.war  
 

  
 
 
 
 

 
 
 

 
 
 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.201184.1565291091000.11369.1565361480139%40Atlassian.JIRA.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Gillaspy commented on  JENKINS-58862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Branch Source Plugin always references https://api.github.com   
 

  
 
 
 
 

 
 Devin Nusbaum Yes, it does not seem to be computing the API URI when the local github URL is put into the Repository HTTPS URL field. The only other information I can think to add is that I am using credentials.  Which always fails since it's trying against https://api.github.com instead of https://git.company.com/api/v3/ even when the Repository HTTPS URL is set to https://git.company.com/owner/repo  
 

  
 
 
 
 

 
 
 

 
 
 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.11365.1565360160214%40Atlassian.JIRA.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-58862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Branch Source Plugin always references https://api.github.com   
 

  
 
 
 
 

 
 William Gillaspy Like I mentioned, it's supposed to work automatically if you specify a non-GitHub repository URL, so if it doesn't that's a bug and we'll look into fixing it.  
 

  
 
 
 
 

 
 
 

 
 
 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.11362.1565359200229%40Atlassian.JIRA.

[JIRA] (JENKINS-58803) Script Approval: No such constructor found even so the constructor is defined

Title: Message Title

Devin Nusbaum commented on JENKINS-58803

Re: Script Approval: No such constructor found even so the constructor is defined

Daniel Beck I don't think so, Checker line 599 in Checker.preCheckedCast is a comment in the current version of groovy-sandbox. Adrian Wyssmann I think that your scriptApproval entry is invalid syntax. It should start with method or staticMethod, and also I don't think there is a constructor of String that takes (String, String). Did you add the entry manually or anything? Are you sure the code is failing in String svnURL = this.checkMandatoryParam("svnURL", props["projects"]["${application}"]["svnURL"])? We see the log message from checkMandatoryParam ("Check if mandatory parameter 'svnURL' is defined"), so maybe it is one of the next few lines that has the problem. I don't see anything particular in what you posted that looks like Groovy syntax that the sandbox isn't able to handle.

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.201114.1564990821000.11358.1565359081037%40Atlassian.JIRA.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Gillaspy commented on  JENKINS-58862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Branch Source Plugin always references https://api.github.com   
 

  
 
 
 
 

 
 Devin Nusbaum I didn't put two and two together on the Repository Scan radio button.  That does work.  Since that feature is deprecated, what is the recommendation for setting the API endpoint in the future? Thank y'all for the assistance.  
 

  
 
 
 
 

 
 
 

 
 
 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.11352.1565358540337%40Atlassian.JIRA.

[JIRA] (JENKINS-58875) withRegistry's DOCKER_REGISTRY_URL isn't used by newer Docker versions

2019-08-09 Thread jenk...@soy.se (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Simon Lundstrom created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58875  
 
 
  withRegistry's DOCKER_REGISTRY_URL isn't used by newer Docker versions   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2019-08-09 13:45  
 
 
Environment: 
 $ sw_vers  ProductName: Mac OS X  ProductVersion: 10.14.6  BuildVersion: 18G87  docker-workflow-plugin$ git show --shortstat  commit 38c4a56a3bd2539c9053fb77eeca9a6716950f29 (HEAD -> master, origin/master, origin/HEAD)  Author: Devin Nusbaum   Date: Fri Aug 2 17:32:42 2019 -0400   [maven-release-plugin] prepare for next development iteration    1 file changed, 3 insertions(+), 3 deletions(-)  docker-workflow-plugin$  $ docker --version  Docker version 19.03.1, build 74b1e89  $ java -version  java version "1.8.0_181"  Java(TM) SE Runtime Environment (build 1.8.0_181-b13)  Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)   Started via:  docker-workflow-plugin$ mvn hpi:run  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Simon Lundstrom  
 

  
 
 
 
 

 
 Using a Scripted Pipeline with a private registry: 

 

node {
docker.withRegistry('https://dockerregistry.tld', 'dockerregistry-credentials') {
sh "env"
sh "docker info"
docker.build("private-project")
}
}  

 with this Dockerfile: 


Dockerfile

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-58862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Branch Source Plugin always references https://api.github.com   
 

  
 
 
 
 

 
 William Gillaspy If you enter something like https://git.company.com/owner/repo into the Repository HTTPS URL field, it is supposed to compute the API URI as https://git.company.com/api/v3/. If that doesn't work, you should be able to select "Repository Scan - Deprecated Visualization", and that should have the same "API endpoint" dropdown as before. Is that not working for you either?  
 

  
 
 
 
 

 
 
 

 
 
 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.11347.1565356980218%40Atlassian.JIRA.

[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm with specific authorize project settings

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38126  
 
 
  Credentials dropdown empty on git scm with specific authorize project settings   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Summary: 
 Credentials dropdown empty on git scm  with specific authorize project settings  
 

  
 
 
 
 

 
 
 

 
 
 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.174282.1473669042000.11330.1565355180698%40Atlassian.JIRA.

[JIRA] (JENKINS-45727) Allow to add additional items to multibranch pipeline jobs

2019-08-09 Thread alexej.ismai...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexej Ismailov commented on  JENKINS-45727  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow to add additional items to multibranch pipeline jobs   
 

  
 
 
 
 

 
 Also interested to add custom projects to a multibranch pipeline job. In my scenario I just want to create multiple projects (different names) that build the same branch (master) Current workaround is to create dummy empty branches in git in order to get those projects picked up by multibranch 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.183926.150064752.11318.1565354640133%40Atlassian.JIRA.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Gillaspy commented on  JENKINS-58862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Branch Source Plugin always references https://api.github.com   
 

  
 
 
 
 

 
 Hello Vivek Pandey.  Sorry about that. Steps: New Item > Multi-branch Pipeline > Branch Source > Add source > GitHub 2.5.4 -> Allows user to choose API Endpoint 2.5.5 -> API Endpoint field is missing, defaults to  https://api.github.com in the config.xml I've added some images to illustrate the change. Thanks! And please let me know if I need to clarify further.    
 

  
 
 
 
 

 
 
 

 
 
 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.11316.1565354220195%40Atlassian.JIRA.

[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job

2019-08-09 Thread julien.bred...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Julien Bréda updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58860  
 
 
  Skipped parameter which is defined in a job   
 

  
 
 
 
 

 
Change By: 
 Julien Bréda  
 
 
Attachment: 
 build.xml  
 
 
Attachment: 
 config.xml  
 

  
 
 
 
 

 
 
 

 
 
 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.201175.1565270296000.11312.1565354160217%40Atlassian.JIRA.

[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job

2019-08-09 Thread julien.bred...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Julien Bréda commented on  JENKINS-58860  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Skipped parameter which is defined in a job   
 

  
 
 
 
 

 
 config.xml and build.xml uploaded.  
 

  
 
 
 
 

 
 
 

 
 
 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.201175.1565270296000.11313.1565354160257%40Atlassian.JIRA.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Gillaspy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 William Gillaspy  
 
 
Attachment: 
 GHBS-2.5.4.PNG  
 

  
 
 
 
 

 
 
 

 
 
 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.11308.1565354100299%40Atlassian.JIRA.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Gillaspy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 William Gillaspy  
 
 
Attachment: 
 GHBS-2.5.5.PNG  
 

  
 
 
 
 

 
 
 

 
 
 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.11309.1565354100314%40Atlassian.JIRA.

[JIRA] (JENKINS-57984) hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from ip

2019-08-09 Thread jonas.buett...@spring-media.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonas Büttner commented on  JENKINS-57984  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from ip   
 

  
 
 
 
 

 
 see https://issues.jenkins-ci.org/browse/JENKINS-58766 maybe its the same. change the workingDir, not /home/jenkins  
 

  
 
 
 
 

 
 
 

 
 
 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.199969.1560335869000.11305.1565353680244%40Atlassian.JIRA.

[JIRA] (JENKINS-56483) Limit local storage utilization

2019-08-09 Thread pablo.gomezjime...@dhl.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pablo Gomez commented on  JENKINS-56483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Limit local storage utilization   
 

  
 
 
 
 

 
 Bruno Meneguello and what will happen when the max ephemeral storage is reached?  
 

  
 
 
 
 

 
 
 

 
 
 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.198084.1552057119000.11302.1565353020143%40Atlassian.JIRA.

[JIRA] (JENKINS-58685) Please login to acess job XXX

2019-08-09 Thread naccabbac...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucas Baccan commented on  JENKINS-58685  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Please login to acess job XXX   
 

  
 
 
 
 

 
 Hi I think it's a bug with the "Matrix Authorization Strategy Plugin" and YABV, because in my jenkins, i created roles for the users. If the user don't have a role with permission for the father job or children jobs, they saw the error in the printscreen. If i gave permission in the role, everything works fine. I created this bug report in YABV, because in my vision, that plugin create the div with de visualizer, but if i misunderstood, sorry for that.  My Jenkins version is 2.176.2 and YABV is 1.9.6.  
 

  
 
 
 
 

 
 
 

 
 
 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.200968.1564173978000.11297.1565352720829%40Atlassian.JIRA.

[JIRA] (JENKINS-56483) Limit local storage utilization

2019-08-09 Thread jenkins-ci....@meneguello.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno Meneguello commented on  JENKINS-56483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Limit local storage utilization   
 

  
 
 
 
 

 
 It's possible to use "Raw yaml for the Pod" with "Yaml merge strategy" = "Merge" and something like: 

 

spec:
  containers:
- name: jnlp
resources:
  limits:
ephemeral-storage: "90Gi"
 

    
 

  
 
 
 
 

 
 
 

 
 
 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.198084.1552057119000.11295.1565352420143%40Atlassian.JIRA.

[JIRA] (JENKINS-58854) Cannot configure SonarQube plugin with JCasC

2019-08-09 Thread omamnam...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maria Chugunova commented on  JENKINS-58854  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot configure SonarQube plugin with JCasC   
 

  
 
 
 
 

 
 I think this issue should be fixed, but if someone is blocked when try the following configuration which works for me with plugins sonarqube 2.9 and jcasc 1.26. Probably with jcasc 1.24 it will work too. 

 

unclassified:
  sonarglobalconfiguration:
buildWrapperEnabled: true
installations:
  - name: sonarqube
serverUrl: https://sonarqube
credentialsId: token-sonarqube
serverAuthenticationToken: "" 
additionalAnalysisProperties:
additionalProperties:
mojoVersion:
triggers:
  envVar:
  skipScmCause: false
  skipUpstreamCause: false
 

  
 

  
 
 
 
 

 
 
 

 
 
 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.201169.1565220198000.11285.1565348220186%40Atlassian.JIRA.

[JIRA] (JENKINS-41315) Jira Trigger not triggering jenkins build jobs

2019-08-09 Thread sanoopraj...@in.verizon.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 sanoop raj p s commented on  JENKINS-41315  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jira Trigger not triggering jenkins build jobs   
 

  
 
 
 
 

 
 Can you be more specific on what issue you are facing? I can share some of the debugging steps that I have used! 
 
Make sure Jenkins is running on port 80 or 443 
As a first step, I would say take a packet capture on Jenkins (Port 80 or 443) and look for http/https traffic 
Please share the Jenkins response to the request. If you are getting 302 return code, there is some issue with the URL. In my case, Webhook URL configured in Jira had the problem. I got to give a '/' (forward slash) at the end of URL to get it working! 
  
 

  
 
 
 
 

 
 
 

 
 
 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.178089.1485167014000.11281.1565348100526%40Atlassian.JIRA.

[JIRA] (JENKINS-58685) Please login to acess job XXX

2019-08-09 Thread gustaf.lu...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gustaf Lundh commented on  JENKINS-58685  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Please login to acess job XXX   
 

  
 
 
 
 

 
 Are you sure it is YABV that is the culprit behind the error message? I cannot reproduce this. If I remove read access for a job, that job (and child jobs) are just removed from the Build Flow. Which YABV version are you running? Which 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.200968.1564173978000.11278.1565347860131%40Atlassian.JIRA.

[JIRA] (JENKINS-41315) Jira Trigger not triggering jenkins build jobs

2019-08-09 Thread mrsharmabal...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Balram Sharma commented on  JENKINS-41315  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jira Trigger not triggering jenkins build jobs   
 

  
 
 
 
 

 
 Hi sanoop raj p s I am also facing same issue. Could you please let us know 1) URL where you were able to repro this issue and 2) URL, How did you fix it?    
 

  
 
 
 
 

 
 
 

 
 
 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.178089.1485167014000.11275.1565347440369%40Atlassian.JIRA.

[JIRA] (JENKINS-58874) Regression in Serialization in 2.166 due to localizer

2019-08-09 Thread jn...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58874  
 
 
  Regression in Serialization in 2.166 due to localizer   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-08-09 10:25  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Nord  
 

  
 
 
 
 

 
 The localizer was bumped in Jenkins 2.166 (https://github.com/jenkinsci/jenkins/pull/3896)  but some of its classes are serializable and do not define a `serialVersionUUID`    this causes errors when serializing/deserializing any messages between different versions. 

 
java.io.InvalidClassException: org.jvnet.localizer.ResourceBundleHolder; local class incompatible: stream classdesc serialVersionUID = 8208483812348571464, local class serialVersionUID = 3549398179458166735
   at propriatary code  

    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation

2019-08-09 Thread ol...@apache.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy commented on  JENKINS-58684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux max task resource exhaustion after excessive timer thread creation   
 

  
 
 
 
 

 
 Colin Chapman I understand but THANKS! a lot for the testing. Looking at your log files I can see a lot of 

 

Error dispatching retry event to SSE channel 

 

 but the the reason is not printed and that could help but this need some changes in the code. I will keep you updated here if I need some help for testing  Thanks again!    
 

  
 
 
 
 

 
 
 

 
 
 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.200967.156416397.11261.1565344260351%40Atlassian.JIRA.

[JIRA] (JENKINS-31237) Parameterized Remote Trigger evaluates Credential password for tokens, prints password to log on error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Denis Shvedchenko edited a comment on  JENKINS-31237  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger evaluates Credential password for tokens, prints password to log on error   
 

  
 
 
 
 

 
 [https://github.com/jenkinsci/parameterized-remote-trigger-plugin/blob/ 7b875a62c6d4892324a9d45e53ebbbe89a181a27 master /src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/utils/Base64Utils.java#L50]  
 

  
 
 
 
 

 
 
 

 
 
 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.165942.1446052599000.11258.1565344080317%40Atlassian.JIRA.

[JIRA] (JENKINS-31237) Parameterized Remote Trigger evaluates Credential password for tokens, prints password to log on error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Denis Shvedchenko commented on  JENKINS-31237  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger evaluates Credential password for tokens, prints password to log on error   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/parameterized-remote-trigger-plugin/blob/7b875a62c6d4892324a9d45e53ebbbe89a181a27/src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/utils/Base64Utils.java#L50  
 

  
 
 
 
 

 
 
 

 
 
 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.165942.1446052599000.11254.1565344020254%40Atlassian.JIRA.

[JIRA] (JENKINS-58873) Parameterized Remote Triggers treat credentials value as templated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Denis Shvedchenko commented on  JENKINS-58873  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Triggers treat credentials value as templated   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/parameterized-remote-trigger-plugin/blob/7b875a62c6d4892324a9d45e53ebbbe89a181a27/src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/utils/Base64Utils.java#L50  
 

  
 
 
 
 

 
 
 

 
 
 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.201192.1565343188000.11251.1565343960978%40Atlassian.JIRA.

[JIRA] (JENKINS-58873) Parameterized Remote Triggers treat credentials value as templated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Denis Shvedchenko closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58873  
 
 
  Parameterized Remote Triggers treat credentials value as templated   
 

  
 
 
 
 

 
Change By: 
 Denis Shvedchenko  
 
 
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.201192.1565343188000.11249.1565343840248%40Atlassian.JIRA.

[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation

2019-08-09 Thread apex...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Colin Chapman commented on  JENKINS-58684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux max task resource exhaustion after excessive timer thread creation   
 

  
 
 
 
 

 
 I can't reproduce the issue on our staging jenkins and obviously I can't push a snapshot on production   
 

  
 
 
 
 

 
 
 

 
 
 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.200967.156416397.11239.1565343660319%40Atlassian.JIRA.

[JIRA] (JENKINS-58873) Parameterized Remote Triggers treat credentials value as templated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Denis Shvedchenko commented on  JENKINS-58873  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Triggers treat credentials value as templated   
 

  
 
 
 
 

 
 at this moment we switched to token auth, but log with this error was lost due to cleanup  
 

  
 
 
 
 

 
 
 

 
 
 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.201192.1565343188000.11236.1565343240356%40Atlassian.JIRA.

[JIRA] (JENKINS-58873) Parameterized Remote Triggers treat credentials value as templated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Denis Shvedchenko created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58873  
 
 
  Parameterized Remote Triggers treat credentials value as templated   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 KaiHsiang Chang  
 
 
Components: 
 parameterized-remote-trigger-plugin  
 
 
Created: 
 2019-08-09 09:33  
 
 
Environment: 
 jenkins 1.164.1 , Parametgerized Remote Triggers : 3.0.7  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Denis Shvedchenko  
 

  
 
 
 
 

 
 Remote server specified on global server. Auth done by credential, password contain something xxx$aaa=xxx. it complains that there is no such template aaa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-58747) Parameters: This property type is not supported - Blue Ocean

2019-08-09 Thread ashish.mishra41...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 ashish mishra assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58747  
 
 
  Parameters: This property type is not supported - Blue Ocean   
 

  
 
 
 
 

 
Change By: 
 ashish mishra  
 
 
Assignee: 
 James Dumay  
 

  
 
 
 
 

 
 
 

 
 
 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.201050.1564641236000.11231.1565342760155%40Atlassian.JIRA.

[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58595  
 
 
  rssAll feed doesn't have published field after 2.176.2 upgrade   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 jenkins  lts-candidate  regression security-534  
 

  
 
 
 
 

 
 
 

 
 
 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.200752.1563783758000.11227.1565340181009%40Atlassian.JIRA.

[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58595  
 
 
  rssAll feed doesn't have published field after 2.176.2 upgrade   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 jenkins regression  security-534  
 

  
 
 
 
 

 
 
 

 
 
 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.200752.1563783758000.11225.1565340180700%40Atlassian.JIRA.

[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-58595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: rssAll feed doesn't have published field after 2.176.2 upgrade   
 

  
 
 
 
 

 
 Matt Sicker Regression due to SECURITY-534, we removed the "h" variable from rss20.jelly and atom.jelly. Could you review all views where you did that and restore it in any that use "h"?  
 

  
 
 
 
 

 
 
 

 
 
 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.200752.1563783758000.11221.1565340120174%40Atlassian.JIRA.

[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58595  
 
 
  rssAll feed doesn't have published field after 2.176.2 upgrade   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 jenkins  regression  
 

  
 
 
 
 

 
 
 

 
 
 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.200752.1563783758000.11217.1565339941568%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-09 Thread spin...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alessio Moscatello 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   
 

  
 
 
 
 

 
 Hello, I'm just fiddling with groovy shared libraries, it helped me reducing code size a  bit, but now I'm pretty stuck since I cannot reduce it anymore, so each line I add is causing the issue...maybe I'm not using shared libraries in the correct way? Does anyone have some hints on this?   BR, Alessio  
 

  
 
 
 
 

 
 
 

 
 
 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.11159.1565339826212%40Atlassian.JIRA.

[JIRA] (JENKINS-58431) Icon for disabled jobs and aborted builds should be different

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 We fixed this in May (just not in LTS yet).  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-58431  
 
 
  Icon for disabled jobs and aborted builds should be different   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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.200560.1562775641000.11156.1565339640574%40Atlassian.JIRA.

[JIRA] (JENKINS-58626) the response code of "Authentication required" should be 401

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 We will probably never address this as it breaks too much other stuff. Do the equivalent of wget --auth-no-challenge and send the auth headers early.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-58626  
 
 
  the response code of "Authentication required" should be 401
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200794.156393893.11153.1565339581731%40Atlassian.JIRA.

[JIRA] (JENKINS-58872) Last output line of sh not printed when not terminated with newline

2019-08-09 Thread ogon...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58872  
 
 
  Last output line of sh not printed when not terminated with newline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 durable-task-plugin  
 
 
Created: 
 2019-08-09 08:30  
 
 
Environment: 
 Jenkins ver. 2.164.2  durable task 1.29  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oliver Gondža  
 

  
 
 
 
 

 
 Reproducer: 

 
node() {
  sh "printf 'one\ntwo\nthree'"
}
 

 prints just: 

 
one
two
 

 The workaround is to append EOL at the end of the sh output but it can be pretty confusing before diagnosed. — Printing curl response this way has caused only DOCTYPE line to be printed as the rest of Jenkins markup served was on the last single line and thus not shown at all.

[JIRA] (JENKINS-58781) HTTP Input failure Excpetion while creating job using Jenkins-CLI "HTTP" Mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The "success" scenario is the only supported one. If there is documentation claiming interactive use works, it needs to be changed.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-58781  
 
 
  HTTP Input failure Excpetion while creating job using Jenkins-CLI "HTTP" Mode.   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201091.156474192.11150.1565339460834%40Atlassian.JIRA.

[JIRA] (JENKINS-55150) [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152

2019-08-09 Thread timjaco...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Jacomb commented on  JENKINS-55150  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152   
 

  
 
 
 
 

 
 The workaround doesn't seem to be working for me Daniel Beck it just hangs here: 

 

[INFO] Started o.e.j.m.p.JettyWebAppContext@67b8d45{/,file:///Users/timja/projects/jenkinsci/jenkins/target/webapp-tmp/,AVAILABLE}{file:///Users/timja/projects/jenkinsci/jenkins/target/webapp-tmp/}
[INFO] Started ServerConnector@2e44cb34{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
[INFO] Started @10823ms
[INFO] Started Jetty Server
 

 The regular approach works but no hot reload  

 

mvn jenkins-dev:run
 

 $ mvn --version Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T20:00:29+01:00) Maven home: /usr/local/Cellar/maven/3.6.1/libexec Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/jre Default locale: en_GB, platform encoding: UTF-8 OS name: "mac os x", version: "10.14.5", arch: "x86_64", family: "mac" Jenkins 2.188-SNAPSHOT  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-58860  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Skipped parameter which is defined in a job   
 

  
 
 
 
 

 
 

since the logs are growing quickly
 The log message explains how you can remove it. Please provide the complete config.xml file for the job in question, as well as the build.xml file for a build showing this message.  
 

  
 
 
 
 

 
 
 

 
 
 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.201175.1565270296000.11141.1565338800195%40Atlassian.JIRA.

[JIRA] (JENKINS-58803) Script Approval: No such constructor found even so the constructor is defined

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-58803  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Script Approval: No such constructor found even so the constructor is defined   
 

  
 
 
 
 

 
 Which version of Script Security Plugin is this? Devin Nusbaum Does this look like a regression due to recent security fixes?  
 

  
 
 
 
 

 
 
 

 
 
 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.201114.1564990821000.11139.1565338620319%40Atlassian.JIRA.

[JIRA] (JENKINS-58803) Script Approval: No such constructor found even so the constructor is defined

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58803  
 
 
  Script Approval: No such constructor found even so the constructor is defined   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201114.1564990821000.11136.1565338500303%40Atlassian.JIRA.

[JIRA] (JENKINS-58867) Jenkins with proxy doesn't work