date:20200311

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-20445  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin timeout is too small   
 

  
 
 
 
 

 
 [~cowlinator] you'll need to use the {{checkout step}} rather than the {{git step}}.  The documentation for the {{[git command|https://jenkins.io/doc/pipeline/steps/git/]}} in pipeline says:{quote}The git step is a simplified shorthand for a subset of the more powerful checkout step: {{ checkout([$class: 'GitSCM', branches: [[name: '*/master']],userRemoteConfigs: [[url: 'http://git-server/user/repository.git']]]) }} *NOTE*: The checkout step is the *preferred SCM checkout method*. It provides significantly more functionality than the git step.Use the [Pipeline Snippet Generator|https://jenkins.io/doc/book/pipeline/getting-started/#snippet-generator] to generate a sample pipeline script for the checkout step.The checkout step can be used in many cases where the git step cannot be used. Refer to the git plugin documentation for detailed descriptions of options available to the checkout step. For example, the git step does not support:* SHA-1 checkout* Tag checkout* Submodule checkout* Sparse checkout* Large file checkout (LFS)* Reference repositories* Branch merges* Repository tagging* Custom refspecs* *Timeout configuration** Changelog calculation against a non-default reference* Stale branch pruning{quote}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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

[JIRA] (JENKINS-20445) Git plugin timeout is too small

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-20445  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin timeout is too small   
 

  
 
 
 
 

 
 p cowlinator you'll need to use the checkout step rather than the git step. The documentation for the git command in pipeline says: 

The git step is a simplified shorthand for a subset of the more powerful checkout step: 
{{checkout([$class: 'GitSCM', branches: [[name: '*/master']], userRemoteConfigs: [[url: 'http://git-server/user/repository.git']]])}} 
NOTE: The checkout step is the preferred SCM checkout method. It provides significantly more functionality than the git step. 
Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step. 
The checkout step can be used in many cases where the git step cannot be used. Refer to the git plugin documentation for detailed descriptions of options available to the checkout step. For example, the git step does not support: 
 
SHA-1 checkout 
Tag checkout 
Submodule checkout 
Sparse checkout 
Large file checkout (LFS) 
Reference repositories 
Branch merges 
Repository tagging 
Custom refspecs 
Timeout configuration 
Changelog calculation against a non-default reference 
Stale branch pruning 
 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it

2020-03-11 Thread ramesh...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramesh Menon commented on  JENKINS-61007  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pipeline-model-definition is using findbugs without providing / depending on it   
 

  
 
 
 
 

 
 Facing the same issue in 2.225  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204477.1581032748000.6060.1583976540188%40Atlassian.JIRA.

[JIRA] (JENKINS-61446) Improve setup docs for kubernetes-plugin

2020-03-11 Thread rodr...@freebsd.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues commented on  JENKINS-61446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve setup docs for kubernetes-plugin   
 

  
 
 
 
 

 
 The work done in JENKINS-61170 is a good start, but doesn't go far enough, because it doesn't detail the steps needed to create the necessary Jenkins Credentials needed to access the kubernetes cluster. The blog post I mentioned above is much better.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205124.1583975203000.6057.158397655%40Atlassian.JIRA.

[JIRA] (JENKINS-61446) Improve setup docs for kubernetes-plugin

2020-03-11 Thread rodr...@freebsd.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61446  
 
 
  Improve setup docs for kubernetes-plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2020-03-12 01:06  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Craig Rodrigues  
 

  
 
 
 
 

 
 This plugin is very useful. However, the README that comes with the kubernetes-plugin doesn't clearly list all the steps needed to set this plugin up. This blog post is much better: https://illya-chekrygin.com/2017/08/26/configuring-certificates-for-jenkins-kubernetes-plugin-0-12/ I would suggest pasting that entire blog post into the README of this plugin, so that users do not have to search random web pages to set this plugin up.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 lee benhart edited a comment on  JENKINS-61433  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
 Mark, I would be inclined to agree with you however we have the develop branch and the master branch on two separate pipelines, so the branch is not being changed.  I also updated the branch spec to use refs/head/${branch}.  Could the issue be related to deleting the workspace in the post, after we have tagged? Could it be because we are tagging using git command line within the pipeline?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205111.1583935218000.6054.1583973960132%40Atlassian.JIRA.

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 lee benhart edited a comment on  JENKINS-61433  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
 Mark, I  I  would be inclined to agree with you however we have  a  the  develop  in  branch and  the master branch on two separate  pipe lines just to alleviate this  pipelines, so the branch is not being changed. Could the  issue  be related to deleting the workspace in the post, after we have tagged? Could it be because we are tagging using git command line within the pipeline?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205111.1583935218000.6052.1583973840253%40Atlassian.JIRA.

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 lee benhart commented on  JENKINS-61433  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
 Mark, I I would be inclined to agree with you however we have a develop in the master branch on two separate pipe lines just to alleviate this issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205111.1583935218000.6050.1583973600193%40Atlassian.JIRA.

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-11 Thread charles.l.sm...@uscis.dhs.gov (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charles Smith commented on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 Matt Sicker Thank you for providing the information and direction. I'll work on cloning the repo and try running the maven test.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204941.158343741.6048.1583971982263%40Atlassian.JIRA.

[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes

2020-03-11 Thread w.male...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Waldek M edited a comment on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes   
 

  
 
 
 
 

 
 [~jinzoo] Have you given the example you wanted here? The Jenkinsfile you posted doesn't use dir () . Also, did you mean to use `sh "echo $PWD"` ?  Also, you did specify "-u root" in run args, which is exactly what you got.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.168928.1457906095000.5976.1583971981289%40Atlassian.JIRA.

[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes

2020-03-11 Thread w.male...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Waldek M commented on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes   
 

  
 
 
 
 

 
 john dow Have you given the example you wanted here? The Jenkinsfile you posted doesn't use dir () . Also, did you mean to use `sh "echo $PWD"` ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.168928.1457906095000.5899.1583971801425%40Atlassian.JIRA.

[JIRA] (JENKINS-57727) ConcurrentModificationException from lock step

2020-03-11 Thread tobias-jenk...@23.gs (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Gruetzmacher updated  JENKINS-57727  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Should be fixed in the next release, see https://github.com/jenkinsci/lockable-resources-plugin/pull/191  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57727  
 
 
  ConcurrentModificationException from lock step   
 

  
 
 
 
 

 
Change By: 
 Tobias Gruetzmacher  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61441) Move alert buttons below warnings

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref assigned an issue to Josh Soref  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61441  
 
 
  Move alert buttons below warnings   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Assignee: 
 Josh Soref  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205119.158395120.5891.1583966580056%40Atlassian.JIRA.

[JIRA] (JENKINS-61445) Broken plugin description

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61445  
 
 
  Broken plugin description   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Brad Kimmel  
 
 
Attachments: 
 image-2020-03-11-18-28-10-820.png  
 
 
Components: 
 google-cloudbuild-plugin  
 
 
Created: 
 2020-03-11 22:28  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Soref  
 

  
 
 
 
 

 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61444) GitHub should be spelled as such

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61444  
 
 
  GitHub should be spelled as such   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Steven Foster  
 
 
Attachments: 
 image-2020-03-11-18-20-01-368.png  
 
 
Components: 
 github-scm-trait-notification-context-plugin  
 
 
Created: 
 2020-03-11 22:20  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Soref  
 

  
 
 
 
 

 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-20445) Git plugin timeout is too small

2020-03-11 Thread cowlina...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator commented on  JENKINS-20445  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin timeout is too small   
 

  
 
 
 
 

 
 The fix mentioned here requires the user to change the "Git plugin section in the job configuration page".  However, this information is not useful for pipeline jobs.  How do you change the timeout value when using the `git()` command in a pipeline?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.151966.1383751667000.5862.1583965020653%40Atlassian.JIRA.

[JIRA] (JENKINS-61443) Plugin description renders poorly

2020-03-11 Thread christopher.sim...@verizonwireless.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61443  
 
 
  Plugin description renders poorly   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Phuong Huynh  
 
 
Attachments: 
 image-2020-03-11-18-12-59-780.png  
 
 
Components: 
 aws-codecommit-trigger-plugin  
 
 
Created: 
 2020-03-11 22:14  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Soref  
 

  
 
 
 
 

 
 The code in question assumes that https://github.com/jenkinsci/aws-codecommit-jobs-plugin/edit/develop/src/main/resources/index.jelly renders with distinct lines: 

 


 
  foo
  bar
 
  

   It does not:   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-43826) Exclude skipped stages from estimated duration calculation

2020-03-11 Thread jess...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 jessebs commented on  JENKINS-43826  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Exclude skipped stages from estimated duration calculation   
 

  
 
 
 
 

 
 When only works if the stage was skipped because of a foreseen reason.  If the stage is skipped because a previous stage failed, then the skipped stages are on the order of a few milliseconds and are considered during the average stage time calculation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.181344.1493132114000.5844.1583964422246%40Atlassian.JIRA.

[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)

2020-03-11 Thread matthew.pigr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Pigram commented on  JENKINS-59907  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: sh steps stuck indefinitely on uncommon architectures (e.g. s390x)   
 

  
 
 
 
 

 
 I'm still running into this same issue, whilst trying to run a pyinstaller docker image. The Sh command gives me the following: ``` ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements). Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`. [Pipeline]  { [Pipeline] sh process apparently never started in /var/jenkins_home/workspace/simple-python-pyinstaller-app@tmp/durable-87eb5f90 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) [Pipeline] } $ docker stop --time=1 0d2e194b04bb5a12016da7f4dd92019127837debf082d18ba9fdf4cbbf6abbd7 $ docker rm -f 0d2e194b04bb5a12016da7f4dd92019127837debf082d18ba9fdf4cbbf6abbd7 [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] End of Pipeline ERROR: script returned exit code -2 Finished: FAILURE ``` Running latest jenkins/blueocean image and I'm currently using the following set up for my Jenkinsfile.   ``` 
 

 
 
pipeline { 
 

 
 
 

 
 
agent none 
 

 
 
 

 
 
options {| |skipStagesAfterUnstable()| |} 
 

 
 
 

 
 
stages {

[JIRA] (JENKINS-61424) Missing french translation on main page

2020-03-11 Thread jb.ledui...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Baptiste Le Duigou commented on  JENKINS-61424  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing french translation on main page   
 

  
 
 
 
 

 
 The other translation is within the Lockable Resources plugin. I am not sure how to tackle this. From what I can see there are no translations right now. Should I create a new file name Messages_fr.properties in the same directory as https://github.com/jenkinsci/lockable-resources-plugin/blob/master/src/main/resources/org/jenkins/plugins/lockableresources/Messages.properties?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205087.1583914912000.5826.1583961420116%40Atlassian.JIRA.

[JIRA] (JENKINS-61424) Missing french translation on main page

2020-03-11 Thread jb.ledui...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Baptiste Le Duigou commented on  JENKINS-61424  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing french translation on main page   
 

  
 
 
 
 

 
 Fixed the first translation with PR https://github.com/jenkinsci/jenkins/pull/4566  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205087.1583914912000.5822.1583961180289%40Atlassian.JIRA.

[JIRA] (JENKINS-61424) Missing french translation on main page

2020-03-11 Thread jb.ledui...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Baptiste Le Duigou started work on  JENKINS-61424  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jean-Baptiste Le Duigou  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205087.1583914912000.5823.1583961180304%40Atlassian.JIRA.

[JIRA] (JENKINS-61405) Stage post conditions doomed by build result becoming unstable

2020-03-11 Thread jdo...@iso-ne.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim D commented on  JENKINS-61405  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stage post conditions doomed by build result becoming unstable   
 

  
 
 
 
 

 
 Please note, right now I'm testing a workaround that's based on the code in pipeline-model-extensions/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/model/BuildCondition.java. That's the code that seems to return a counter-intuitive result that mixes some stage-specific things with non-stage-specific things. I can create a global pipeline library method that basically pulls out the 3 components that BuildCondition uses, errorResult, execResult, and prevResult, and inspect and use them directly: 

 

@NonCPS
Map getStageConditionResults () {
Map results = [:]
String stageName = env.STAGE_NAME
WorkflowRun run = currentBuild.getRawBuild()
Result errorResult = Result.SUCCESS;
List startAndEnd = CommonUtils.findPossiblyUnfinishedEndNodeForCurrentStage(stageName, run.getExecution());
if (startAndEnd.size() == 2 && startAndEnd.get(0) != null && startAndEnd.get(1) != null) {
DepthFirstScanner scanner = new DepthFirstScanner();
if (scanner.setup(startAndEnd.get(1), Collections.singletonList(startAndEnd.get(0 {
WarningAction warningAction = StreamSupport.stream(scanner.spliterator(), false)
.map({node -> node.getPersistentAction(WarningAction.class)})
.filter(Objects.)
.max(Comparator.comparing({warning -> warning.getResult().ordinal}))
.orElse(null);
if (warningAction != null) {
errorResult = warningAction.getResult();
}
}
}
Result execResult = run.getExecution().getResult()
Result prevResult = run.getResult();
if (prevResult == null) {
prevResult = Result.SUCCESS;
}
if (execResult == null) {
execResult = Result.SUCCESS;
}
results['errorResult'] = errorResult.toString()
results['execResult'] = execResult.toString()
results['prevResult'] = prevResult.toString()
return results
}
 

 What I notice is that unstable stages have UNSTABLE errorResult and successful stages have SUCCESS errorResult. But once one stage has UNSTABLE prevResult, all subsequent stages have UNSTABLE prevResult. It looks like in the BuildCondition code, that UNSTABLE prevResult will trump the SUCCESS errorResult and return UNSTABLE as the overall Result for a successful stage, firing stage post conditions like "unsuccessful". Really what would be good is a pair of stage post conditions like success/unsuccessful that ignores the UNSTABLE prevResult. In any case, I'm going to try using this pipeline library method in our stage post sections to detect when a stage is unstable and requires notifications. Is there any chance similar logic could be implemented by the existing post conditions, or added as new post conditions?

[JIRA] (JENKINS-60909) Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Simon edited a comment on  JENKINS-60909  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used   
 

  
 
 
 
 

 
 Hi Daniel, I  changed  had it working in one environment, but I had to change  the environment, and now I am seeing a General Exception: null. Any thoughts on what environment changes could cause this exception, or what I should be looking for? !image-2020-03-11-15-55-58-904.png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204300.1580327343000.5816.1583956740155%40Atlassian.JIRA.

[JIRA] (JENKINS-60909) Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used

2020-03-11 Thread christopher.sim...@verizonwireless.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Simon edited a comment on  JENKINS-60909  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used   
 

  
 
 
 
 

 
 Hi Daniel, I had it working in one environment, but I had to change the environment, and now I am seeing a General Exception: null.  Same settings as before, same LRE instance.  Any thoughts on what environment changes could cause this exception, or what I should be looking for? !image-2020-03-11-15-55-58-904.png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204300.1580327343000.5818.1583956740180%40Atlassian.JIRA.

[JIRA] (JENKINS-60909) Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used

2020-03-11 Thread christopher.sim...@verizonwireless.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Simon commented on  JENKINS-60909  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used   
 

  
 
 
 
 

 
 Hi Daniel,   I changed the environment, and now I am seeing a General Exception: null. Any thoughts on what environment changes could cause this exception, or what I should be looking for?     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204300.1580327343000.5814.1583956680120%40Atlassian.JIRA.

[JIRA] (JENKINS-60909) Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used

2020-03-11 Thread christopher.sim...@verizonwireless.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Simon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60909  
 
 
  Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used   
 

  
 
 
 
 

 
Change By: 
 Chris Simon  
 
 
Attachment: 
 image-2020-03-11-15-55-58-904.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204300.1580327343000.5812.1583956620130%40Atlassian.JIRA.

[JIRA] (JENKINS-60909) Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used

2020-03-11 Thread christopher.sim...@verizonwireless.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Simon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60909  
 
 
  Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used   
 

  
 
 
 
 

 
Change By: 
 Chris Simon  
 
 
Comment: 
 Hi Daniel, I switched Jenkins environments, and now I am getting "General Excception: Null" when it tries uploading the scripts. Any idea what changes in the environment could cause this exception? !image-2020-03-11-15-53-48-589.png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204300.1580327343000.5810.1583956560167%40Atlassian.JIRA.

[JIRA] (JENKINS-60909) Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used

2020-03-11 Thread christopher.sim...@verizonwireless.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Simon commented on  JENKINS-60909  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used   
 

  
 
 
 
 

 
 Hi Daniel,  I switched Jenkins environments, and now I am getting "General Excception: Null" when it tries uploading the scripts. Any idea what changes in the environment could cause this exception?     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204300.1580327343000.5806.1583956500207%40Atlassian.JIRA.

[JIRA] (JENKINS-60909) Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used

2020-03-11 Thread christopher.sim...@verizonwireless.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Simon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60909  
 
 
  Not Seeing Script Synced into Micro Focus Performance Center with Micro Focus Plugin Used   
 

  
 
 
 
 

 
Change By: 
 Chris Simon  
 
 
Attachment: 
 image-2020-03-11-15-53-48-589.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204300.1580327343000.5804.1583956440183%40Atlassian.JIRA.

[JIRA] (JENKINS-61439) Independent git operations share singular JVM lock

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-61439  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Independent git operations share singular JVM lock   
 

  
 
 
 
 

 
 I'm not sure what you mean by "remote name".  Can you explain further?I would assume that the lock is being acquired on the URL of the remote repository.  A single remote repository URL has a single cache directory on the Jenkins master.  That cache is locked for the duration of an update to retrieve the Jenkinsfile for each branch.If your repository has grown significantly or if the git cache on the Jenkins master has not recently been garbage collected, you might try performing a {{git gc}} on the specific cache directory on the master, just as an exploration to see if that would improve performance.We could consider multiple copies of the cache on the Jenkins master with some way of choosing one of the pool of caches.  That seems more complicated and has different challenges in trying to decide how deep to make the pool of caches and how to avoid disc space bloat in the pool of caches.You might also confirm that you are using the best branch source for your git provider.  If you're using GitHub, then you should use the GitHub branch source rather than the branch source provided by the git plugin.  The GitHub branch source can use REST API calls to retrieve the Jenkinsfile.  Likewise for Bitbucket, Gitea, and GitLab.  Use their higher level branch source if you're using one of those git providers. If your multibranch job definition has a "lightweight checkout" option, you might also compare the results when it is enabled and when it is disabled.  We've seen cases with large repositories where enabling lightweight checkout makes the operations slower.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-61439) Independent git operations share singular JVM lock

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-61439  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Independent git operations share singular JVM lock   
 

  
 
 
 
 

 
 I'm not sure what you mean by "remote name".  Can you explain further?I would assume that the lock is being acquired on the URL of the remote repository.  A single remote repository URL has a single cache directory on the Jenkins master.  That cache is locked for the duration of an update to retrieve the Jenkinsfile for each branch.If your repository has grown significantly or if the git cache on the Jenkins master has not recently been garbage collected, you might try performing a {{git gc}} on the specific cache directory on the master, just as an exploration to see if that would improve performance.We could consider multiple copies of the cache on the Jenkins master with some way of choosing one of the pool of caches.  That seems more complicated and has different challenges in trying to decide how deep to make the pool of caches and how to avoid disc space bloat in the pool of caches. You might also confirm that you are using the best branch source for your git provider.  If you're using GitHub, then you should use the GitHub branch source rather than the branch source provided by the git plugin.  The GitHub branch source can use REST API calls to retrieve the Jenkinsfile.  Likewise for Bitbucket, Gitea, and GitLab.  Use their higher level branch source if you're using one of those git providers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61439) Independent git operations share singular JVM lock

Title: Message Title

Mark Waite commented on JENKINS-61439

Re: Independent git operations share singular JVM lock

I'm not sure what you mean by "remote name". Can you explain further? I would assume that the lock is being acquired on the URL of the remote repository. A single remote repository URL has a single cache directory on the Jenkins master. That cache is locked for the duration of an update to retrieve the Jenkinsfile for each branch. If your repository has grown significantly or if the git cache on the Jenkins master has not recently been garbage collected, you might try performing a git gc on the specific cache directory on the master, just as an exploration to see if that would improve performance. We could consider multiple copies of the cache on the Jenkins master with some way of choosing one of the pool of caches. That seems more complicated and has different challenges in trying to decide how deep to make the pool of caches and how to avoid disc space bloat in the pool of caches.

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

--
You received this message because you are subscribed to the Google 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.205117.1583948832000.5798.1583955060148%40Atlassian.JIRA.

[JIRA] (JENKINS-61442) Issues column popup outside visible area

2020-03-11 Thread andipabs...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Pabst created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61442  
 
 
  Issues column popup outside visible area   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ulli Hafner  
 
 
Attachments: 
 issues_column_popup.png  
 
 
Components: 
 warnings-ng-plugin  
 
 
Created: 
 2020-03-11 18:27  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Andreas Pabst  
 

  
 
 
 
 

 
 When hovering over the "# Issues" Column in the project list, the popup containing the details for all tools is outside the visible area. See the attached screenshot for a demonstration.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61441) Move alert buttons below warnings

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61441  
 
 
  Move alert buttons below warnings   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2020-03-11-14-24-44-740.png  
 
 
Components: 
 core  
 
 
Created: 
 2020-03-11 18:26  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Soref  
 

  
 
 
 
 

 
 Currently:  Preferred: 
 

 
 
New version ... available 
 
 
Warnings have been published... 
 
 
Plugins... 
 
 
Go to plugin manager | Configure which of these warnings are shown

[JIRA] (JENKINS-61440) EC2 plugin fails to recognise instance terminated on spot

2020-03-11 Thread m...@anatwine.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt T updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61440  
 
 
  EC2 plugin fails to recognise instance terminated on spot   
 

  
 
 
 
 

 
Change By: 
 Matt T  
 

  
 
 
 
 

 
 We are using the EC2 plugin to automatically launch instances on spot, and this generally works OK. One of the biggest problems, however, is that if AWS terminates the instance half way through a build due to spot price change or they need the capacity back, the pipeline spits out an error along the lines of "The channel is closing down or has closed down," and sits there forever, never recognising that the instance has gone and it will never complete. This means that you manually have to stop the build, and re-run it.In an ideal world, the job would be put back on the queue to run on another instance, however I'd settle for it simply dying peacefully and the job failing or getting cancelled automatically.I've done a search on here but can't find any issues that match this description. We're using Jenkins version 2.150.2, and EC2 plugin version 1.49.1.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-61440) EC2 plugin fails to recognise instance terminated on spot

2020-03-11 Thread m...@anatwine.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt T created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61440  
 
 
  EC2 plugin fails to recognise instance terminated on spot   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 FABRIZIO MANFREDI  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2020-03-11 18:14  
 
 
Environment: 
 Jenkins version 2.150.2  EC2 plugin version 1.49.1  CentOS 7.7.1908  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Matt T  
 

  
 
 
 
 

 
 We are using the EC2 plugin to automatically launch instances on spot, and this generally works OK. One of the biggest problems, however, is that if AWS terminates the instance half way through a build due to spot price change or they need the capacity back, the pipeline spits out an error along the lines of "The channel is closing down or has closed down," and sits there forever, never recognising that the instance has gone and it will never complete. This means that you manually have to stop the build, and re-run it. In an ideal world, the job would be put back on the queue to run on another instance, however I'd settle for it simply dying peacefully and the job failing or getting cancelled automatically. I've done a search on here but can't find any issues that match this description. We're using Jenkins version 2.150.2, and EC2 plugin version 1.49.1.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

2020-03-11 Thread matthew.ell...@soprabanking.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-61438  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
 Changes to the RequestImpl are not so wrong, you do not really need a converter to convert something to Object, agree?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205116.158394316.5789.1583949180172%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

2020-03-11 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-61438  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
 Not sure offhand. Study JENKINS-26143.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205116.158394316.5787.1583948940139%40Atlassian.JIRA.

[JIRA] (JENKINS-61439) Independent git operations share singular JVM lock

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Ellams created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61439  
 
 
  Independent git operations share singular JVM lock   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Attachments: 
 threaddump.txt  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2020-03-11 17:47  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Matthew Ellams  
 

  
 
 
 
 

 
 On our project we have a large number of feature builds across several versions that run as separate builds on Jenkins. We have noticed that our multibranch builds for this have been creeping up in run times, with no immediately obvious cause in the code changes, and after some digging, it seems that even though each build is running independently, there is a singular lock for each unique remote name that each git process waits to acquire. Even though each fetch and checkout is relatively fast, this seems to lead to a huge backlog of builds in contention over the lock as the multibranch pipeline starts each build on dev before requisitioning a slave and executing the specific tasks needed. I have been digging and not found anyone who seems to have hit the same issue so it is likely that we have some unusual setup that doesn't match with standard usage, but it also seems strange that we are locking on the remote name rather than the directory (which is more likely to have synchronisation issues). The specific bit of the plugin that is acquiring the lock seems to be AbstractGitSCMSource.getCacheLock(). I've attached a thread dump illustrating the various threads all stacked up on the singular lock.

[JIRA] (JENKINS-59448) Distinct jenkins userids for same AD user

2020-03-11 Thread williambr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Brode stopped work on  JENKINS-59448  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 William Brode  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.202033.1568905412000.5779.1583948520599%40Atlassian.JIRA.

[JIRA] (JENKINS-59448) Distinct jenkins userids for same AD user

2020-03-11 Thread williambr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Brode commented on  JENKINS-59448  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Distinct jenkins userids for same AD user   
 

  
 
 
 
 

 
 Unassinging and moving back to TODO based on no recent updates.  Would be great if someone is willing to take it on!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.202033.1568905412000.5777.1583948520540%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco edited a comment on  JENKINS-61438  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
 The [~jglick]  possible solutions are  or : *  change the ChoiceParameterDefinition.setChoice from Object to String but seems there are a lot of point where they use different value to be interpreted in the setter method.  Or  *  change the RequestImpl to not throw exception if the coverter loopup is for Object. Everything is Object this mean there is no needs convertion.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205116.158394316.5771.1583948460602%40Atlassian.JIRA.

[JIRA] (JENKINS-59448) Distinct jenkins userids for same AD user

2020-03-11 Thread williambr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Brode assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59448  
 
 
  Distinct jenkins userids for same AD user   
 

  
 
 
 
 

 
Change By: 
 William Brode  
 
 
Assignee: 
 Félix  Belzunce Arcos  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.202033.1568905412000.5766.1583948460533%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-61438  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
 The actual workaround is register a new ObjectConverter to bean utils like this: 

 

private static final class ObjectConverter implements Converter {
@Override
public Object convert(@SuppressWarnings("rawtypes") Class type, Object value) {
return value;
}
}
 

 Although this has unknown impacts in the whole application.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205116.158394316.5759.1583948400049%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco assigned an issue to Nikolas Falco  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61438  
 
 
  IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Assignee: 
 Nikolas Falco  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205116.158394316.5756.1583948280172%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61438  
 
 
  IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205116.158394316.5758.1583948280262%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco started work on  JENKINS-61438  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205116.158394316.5757.1583948280247%40Atlassian.JIRA.

[JIRA] (JENKINS-59776) workflow-basic-steps-plugin "waitUntil" should have a quiet mode

2020-03-11 Thread pue...@puetzk.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Puetz commented on  JENKINS-59776  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: workflow-basic-steps-plugin "waitUntil" should have a quiet mode   
 

  
 
 
 
 

 
 Just to update the status here: https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/100 is now merged (not by me, I just got notified by github and see the status isn't updated here)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.202500.1571053928000.5747.1583947560254%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder steps within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-61429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to move/reorder steps within a job   
 

  
 
 
 
 

 
 A workaround would be to delete build steps and recreate them, as newly created steps can be reordered. That's only really feasible with simple build steps like shell/batch though, as they're basically one big textarea can can be copied easily into a new step.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5736.1583946660149%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder steps within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-61429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to move/reorder steps within a job   
 

  
 
 
 
 

 
 Folders are affected too, and they use the 2.0 config page style, just like freestyle jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5732.1583946300323%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder steps within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-61429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to move/reorder steps within a job   
 

  
 
 
 
 

 
 I confirmed system config and view config are unaffected (and they use the pre-2.0 config page style).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5722.1583946120205%40Atlassian.JIRA.

[JIRA] (JENKINS-52264) Error while running pipeline job in docker

2020-03-11 Thread timbla...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Black commented on  JENKINS-52264  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error while running pipeline job in docker   
 

  
 
 
 
 

 
 This can manifest in various ways - for me it first appeared to be this bug, and only after enabling LAUNCH_DIAGNOSTICS did we see evidence that lead us here, which was the actual culprit.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.192029.153025197.5713.1583946000263%40Atlassian.JIRA.

[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container

2020-03-11 Thread timbla...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Black commented on  JENKINS-60039  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container   
 

  
 
 
 
 

 
 For me, this issue turned out to be an empty environment variable set in Jenkins global properties. This.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.202866.1572877026000.5708.1583945881080%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder steps within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61429  
 
 
  Unable to move/reorder steps within a job   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Summary: 
 Unable to move/reorder  items  steps  within a job  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5703.1583945580203%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder items within a job

2020-03-11 Thread fqueir...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Queiruga Balado commented on  JENKINS-61429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to move/reorder items within a job   
 

  
 
 
 
 

 
 Ill take a look  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5697.1583944800128%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61438  
 
 
  IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 

  
 
 
 
 

 
 I'm had implement a jenkins.branch.BranchProperty that list all available ParameterDefinition. !image-2020-03-11-17-00-27-616.png|thumbnail! It normally works but when I select a ChoiceParameter I got the following Exception on save:{noformat}java.lang.IllegalArgumentException: Unable to convert to class java.lang.Object at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:738) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.injectSetters(RequestImpl.java:834) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678)Caused: java.lang.IllegalArgumentException: Failed to instantiate class hudson.model.ParameterDefinition from {"name":"SCENARIO","choices":"1\n2\n3","description":"","":"","stapler-class":"hudson.model.ChoiceParameterDefinition","$class":"hudson.model.ChoiceParameterDefinition"} at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:681) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:717) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:778)Caused: java.lang.IllegalArgumentException: Failed to convert the parameterDefinitions parameter of the constructor public com.thedigitalstack.jenkins.plugins.parametricrun.ParameterBranchProperty(java.lang.String,boolean,java.lang.String,java.util.List) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:780) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678)Caused: java.lang.IllegalArgumentException: Failed to instantiate class jenkins.branch.BranchProperty from {"actionLabel":"Action Label","useBadge":false,"badgeTemplate":"Run with #$PARAMETER","parameterDefinitions":{"name":"SCENARIO","choices":"1\n2\n3","description":"","":"","stapler-class":"hudson.model.ChoiceParameterDefinition","$class":"hudson.model.ChoiceParameterDefinition"},"stapler-class":"com.thedigitalstack.jenkins.plugins.parametricrun.ParameterBranchProperty","$class":"com.thedigitalstack.jenkins.plugins.parametricrun.ParameterBranchProperty"}   ...{noformat}  The RequestImpl instantiate a ChoiceParameterDefinition  class  and than using reflection lookup a setter  {{ @DataBoundSetter }}  annotated for "choice" property. It takes the  method  parameter type  from method  (in  this unlikely  case  unlike case  Object) and than use apache  beanutil  beanutils  to convert the actual value "v1\n2\n3" (String) to Object.  There  Since there  are no converter  registere  registered  for Object  and  it fails  on [RequestImpl .

[JIRA] (JENKINS-61429) Unable to move/reorder items within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-61429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to move/reorder items within a job   
 

  
 
 
 
 

 
 Félix Queiruga Balado Could you please take a look at this? Given https://github.com/jenkinsci/jenkins/compare/jenkins-2.215...jenkins-2.217 it's likely to be related to your JS rework.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5694.1583944620403%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder items within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61429  
 
 
  Unable to move/reorder items within a job   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 

  
 
 
 
 

 
 Recently noticed, whilst trying to diagnose another issue, that we are now unable to move/reorder items within a job.  Attempting to move/reorder items in the build or post-build  section results in the browser scrolling upwards with no ability to move item.  Tried on multiple browsers and computers. *Steps to reproduce:* # Create a freestyle project # Add multiple build steps # Apply changes # Reload the page (it only affects steps that were present when the page was loaded) # Try to drag/drop build steps with the handle in the top left to change their order*Expected result:* It works*Actual result:* It doesn't*Notes:* The "placeholder" rectangle appears further up the page.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61429) Unable to move/reorder items within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-61429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to move/reorder items within a job   
 

  
 
 
 
 

 
 Seems to have been broken in 2.217. 2.216 wasn't released, so "between 2.215 and 2.217".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5687.1583944380199%40Atlassian.JIRA.

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-11 Thread msic...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 You'll need to git clone the repo, edit that file to change the key to your key, then you can run mvn test -Dtest=TrileadSSHPublicKeyAuthenticatorTest to run just that test.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204941.158343741.5685.1583944260089%40Atlassian.JIRA.

[JIRA] (JENKINS-61331) Make the header "Jenkins" open the main menu, instead of the tiny arrow icon

2020-03-11 Thread fqueir...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Queiruga Balado commented on  JENKINS-61331  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make the header "Jenkins" open the main menu, instead of the tiny arrow icon   
 

  
 
 
 
 

 
 You're right. I'm still having trouble thinking of a good solution. Leaving the icon on at all times may give the impression that it's a purely dropdown button, not a link. It would also affect uses across the whole application. The downside with just making it bigger is that it would cause a rather big empty space next to the breadcrumb link.  Cannot think of a good solution for this tbh  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204849.1582926952000.5681.1583944080339%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-61438  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
 The possible solutions are or change the ChoiceParameterDefinition.setChoice from Object to String but seems there are a lot of point where they use different value to be interpreted in the setter method. Or change the RequestImpl to not throw exception if the coverter loopup is for Object. Everything is Object this mean there is no needs convertion.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205116.158394316.5679.1583943780044%40Atlassian.JIRA.

[JIRA] (JENKINS-61331) Make the header "Jenkins" open the main menu, instead of the tiny arrow icon

2020-03-11 Thread jenk...@juliohm.com.br (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Julio Morimoto commented on  JENKINS-61331  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make the header "Jenkins" open the main menu, instead of the tiny arrow icon   
 

  
 
 
 
 

 
 This is even more cumbersome with the fact that there are actually two drop down menus in the breadcrumb. Very small icons, very close to each other.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204849.1582926952000.5605.1583943601516%40Atlassian.JIRA.

[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes

2020-03-11 Thread jinzoo2...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 john dow commented on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes   
 

  
 
 
 
 

 
 I am still seeing this issue with Docker Pipeline v 1.22 and Docker v 19.03 Jenkinfile: 

 

pipeline {
   agent { docker { 
 image 'ruby'
 args '-u root'
    } 
 }
 stages {
   stage('build') {
 steps {
   sh '$PWD'
   sh 'ruby --version'
 }
   }
 } 

 I get the following error: 

 

 $ docker run -t -d -u 1000:996 -u root -w /var/jenkins_home/workspace/build-chef-pkgs --volumes-from 0d3a069ee976a6e027b7605d0b4d3abada6bcc9c1b1afcaf5ffa0610e4e83b76 -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  -e  ruby cat $ docker top c9b3ddcd8df5ea3e447f163006cd42a057ca55eea49f6df1c806d0e010459bfc -eo pid,comm [Pipeline] { [Pipeline] stage [Pipeline] { (build) [Pipeline] sh + /var/jenkins_home/workspace/build-chef-pkgs /var/jenkins_home/workspace/build-chef-pkgs@tmp/durable-e13f4856/script.sh: 1: /var/jenkins_home/workspace/build-chef-pkgs@tmp/durable-e13f4856/script.sh: /var/jenkins_home/workspace/build-chef-pkgs: Permission denied 

   The working directory is mounted as root and I cannot override the default user or working directory arguments passed to the docker run command  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira

[JIRA] (JENKINS-49331) IllegalArgumentException unhandled for Illegal choice in parameter

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49331  
 
 
  IllegalArgumentException unhandled for Illegal choice in parameter   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Attachment: 
 payload.json  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.188194.1517531442000.5596.1583943540385%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61438  
 
 
  IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Attachment: 
 payload.json  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205116.158394316.5601.1583943540584%40Atlassian.JIRA.

[JIRA] (JENKINS-49331) IllegalArgumentException unhandled for Illegal choice in parameter

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49331  
 
 
  IllegalArgumentException unhandled for Illegal choice in parameter   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Attachment: 
 payload.json  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.188194.1517531442000.5600.1583943540527%40Atlassian.JIRA.

[JIRA] (JENKINS-61331) Make the header "Jenkins" open the main menu, instead of the tiny arrow icon

2020-03-11 Thread jenk...@juliohm.com.br (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Julio Morimoto commented on  JENKINS-61331  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make the header "Jenkins" open the main menu, instead of the tiny arrow icon   
 

  
 
 
 
 

 
 Aboslutely. In my experience, the first item of the breadcrum "Jenkins" is a hotspot. I find myself always expecting it to open the menu, instead of taking me back to the main screen. Would it make sense to at least make the icon for the drop down a bit larger? It's really difficult to aim for it, especially in high resolution monitors.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204849.1582926952000.5592.1583943480735%40Atlassian.JIRA.

[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61438  
 
 
  IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2020-03-11-17-00-27-616.png  
 
 
Components: 
 core  
 
 
Created: 
 2020-03-11 16:12  
 
 
Environment: 
 Jenkins 2.204.2  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nikolas Falco  
 

  
 
 
 
 

 
 I'm had implement a jenkins.branch.BranchProperty that list all available ParameterDefinition.   It normally works but when I select a ChoiceParameter I got the following Exception on save: 

 
java.lang.IllegalArgumentException: Unable to convert to class java.lang.Object
	at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:738)
	at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478)
	at org.kohsuke.stapler.RequestImpl.injectSetters(RequestImpl.java:834)
	at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784)
	at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83)
	at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678)
Caused: java.lang.IllegalArgumentException: Failed to instantiate class hudson.model.ParameterDefinition from {"name":"SCENARIO","choices":"1\n2\n3","description":"","":"","stapler-class":"hudson.model.ChoiceParameterDefinition","$class":"hudson.model.ChoiceParameterDefinition"}
	at

[JIRA] (JENKINS-61429) Unable to move/reorder items within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61429  
 
 
  Unable to move/reorder items within a job   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 lts-candidate regression  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5584.1583942940240%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder items within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-61429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to move/reorder items within a job   
 

  
 
 
 
 

 
 Affects 2.222, too.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5586.1583942940266%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder items within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck edited a comment on  JENKINS-61429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to move/reorder items within a job   
 

  
 
 
 
 

 
 Confirmed.  Only affects (post)build steps that have been there since before the page loaded.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5580.1583942880202%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder items within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-61429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to move/reorder items within a job   
 

  
 
 
 
 

 
 Confirmed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5578.1583942825687%40Atlassian.JIRA.

[JIRA] (JENKINS-61424) Missing french translation on main page

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61424  
 
 
  Missing french translation on main page   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 newbie-friendly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205087.1583914912000.5575.1583942700199%40Atlassian.JIRA.

[JIRA] (JENKINS-61429) Unable to move/reorder items within a job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61429  
 
 
  Unable to move/reorder items within a job   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 regression  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205106.1583931628000.5573.1583942640218%40Atlassian.JIRA.

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-61433  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
 My suspicion is that the tag is unrelated to the decision being made by the git plugin to start another build. Sometimes, jobs that are building on every poll will stop building on every poll when the branch name being built is changed from */master to refs/heads/master. The more specific reference avoids inadvertent detection of other changes which are unrelated to the specific branch.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205111.1583935218000.5569.1583941620132%40Atlassian.JIRA.

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 lee benhart commented on  JENKINS-61433  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
 Thanks Mark, I will do so, however we were seeing this with the earlier versions as well. I had to disable polling altogether about a year ago.  I had first thought it was purely related to bitbucket.  I re-enabled polling after we migrated our repositories to github, the issue persists.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205111.1583935218000.5566.1583940540649%40Atlassian.JIRA.

[JIRA] (JENKINS-61437) Kubernetes and vault-credential plugins results in too many open files

2020-03-11 Thread l...@trifork.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lasse Højgaard updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61437  
 
 
  Kubernetes and vault-credential plugins results in too many open files
 

  
 
 
 
 

 
Change By: 
 Lasse Højgaard  
 

  
 
 
 
 

 
 Hi,Provisioning build agents on kubernetes somehow results in "Too Many Open Files". {code:java}  ```  $ ps auxUSER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMANDjenkins 1 0.0 0.0 1148 4 ? Ss Mar06 0:11 /sbin/tini  --  –  /usr/local/bin/jenkins.sh --argumentsRealm.passwd.admin=${MASTER_ADMIN_PASSWORD} --argumentsRealm.roles.admin=admin --httpPort=8080jenkins 7 1.1 7.1 3841028 1167032 ? Sl Mar06 82:21 java -Duser.home=/var/jenkins_home -Dpermissive-script-security.enabled=true -Xms512m -Xmx1024m -XX:MaxMetaspaceSize=200m -XX:CompressedClassSpaceSize=100m -Djenkins.model.Jenkins.slaveAgentPort=5 -jar /jenkins 15138 0.0 0.0 19976 3656 pts/0 Ss+ 14:46 0:00 bashjenkins 15922 0.1 0.0 19972 3436 pts/1 Ss 14:57 0:00 bashjenkins 15927 0.0 0.0 38384 3264 pts/1 R+ 14:58 0:00 ps aux  $ ls -la /proc/7/fd | head -n 20total 0dr-x--. 2 jenkins jenkins 0 Mar 11 14:46 .dr-xr-xr-x. 9 jenkins jenkins 0 Mar 11 14:46 ..lrwx--. 1 jenkins jenkins 64 Mar 11 14:46 0 -> /dev/nulll-wx--. 1 jenkins jenkins 64 Mar 11 14:46 1 -> pipe:[295935440]lr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10 -> /dev/urandomlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 100 -> /var/jenkins_home/war/WEB-INF/lib/localizer-1.26.jarlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 1000 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 1 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10001 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10002 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10003 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10004 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10005 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10006 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10007 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10008 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 10009 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46 1001 -> /run/secrets/kubernetes.io/serviceaccount/..2020_03_06_12_39_51.580529302/tokenlr-x--. 1 jenkins jenkins 64 Mar 11 14:46

[JIRA] (JENKINS-61437) Kubernetes and vault-credential plugins results in too many open files

2020-03-11 Thread l...@trifork.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lasse Højgaard commented on  JENKINS-61437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Kubernetes and vault-credential plugins results in too many open files
 

  
 
 
 
 

 
 I've done more digging: Even running a scan on a multibranch pipeline leaks file descriptors:   

 

$ # before
$ ls -la /proc/6/fd  | cut -d ' ' -f11 | grep -i token | wc -l
233

$ # after
$ ls -la /proc/6/fd  | cut -d ' ' -f11 | grep -i token | wc -l
458 

 I've installed the plugin file-leak-detector v 1.6 but it reporting 0 open file descriptors: 

 

0 descriptors are open


 

 So now I'm not so sure that it's related to the hashicorp-vault-plugin but more to the kubernetes plugin.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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

[JIRA] (JENKINS-61428) Control chars in Git commit messages cause invalid JSON

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61428  
 
 
  Control chars in Git commit messages cause invalid JSON   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Component/s: 
 core  
 
 
Component/s: 
 git-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205104.1583929621000.5559.1583939640289%40Atlassian.JIRA.

[JIRA] (JENKINS-61428) Control chars in Git commit messages cause invalid JSON

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-61428  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Control chars in Git commit messages cause invalid JSON   
 

  
 
 
 
 

 
 I believe this is an issue in Jenkins core rather than a specific issue in the git plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205104.1583929621000.5557.1583939640256%40Atlassian.JIRA.

[JIRA] (JENKINS-61428) Control chars in Git commit messages cause invalid JSON from REST API

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61428  
 
 
  Control chars in Git commit messages cause invalid JSON from REST API   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Summary: 
 Control chars in Git commit messages cause invalid JSON  from REST API  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205104.1583929621000.5561.1583939640313%40Atlassian.JIRA.

[JIRA] (JENKINS-61435) Jenkins is trying to build remotely when want master

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-61435  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins is trying to build remotely when want master   
 

  
 
 
 
 

 
 Please don't use issues for question and answer.  The chat systems and mailing lists are much better suited to question and answer. To restrict a job to run only on master, PIpeline jobs can require the label 'master'.  Freestyle jobs can use the "Restrict where this job can run" setting to limit the job to run on master.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205113.1583937581000..1583939520311%40Atlassian.JIRA.

[JIRA] (JENKINS-61435) Jenkins is trying to build remotely when want master

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please don't use issues for question and answer. The chat systems and mailing lists are much better suited to question and answer.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-61435  
 
 
  Jenkins is trying to build remotely when want master   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61433  
 
 
  Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205111.1583935218000.5551.1583939280194%40Atlassian.JIRA.

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

2020-03-11 Thread ssand...@nycopportunity.nyc.gov (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-61433  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
 Please update your git plugin and git client plugin to the released versions instead of the release candidate. Those release candidates are not being maintained since the official release of git plugin 4.0.0 and git client 3.0.0. May not resolve the issue but will avoid a number of other serious problems in those release candidates.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205111.1583935218000.5549.1583939280153%40Atlassian.JIRA.

[JIRA] (JENKINS-61437) Kubernetes and vault-credential plugins results in too many open files

2020-03-11 Thread l...@trifork.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lasse Højgaard created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61437  
 
 
  Kubernetes and vault-credential plugins results in too many open files
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Peter Tierno  
 
 
Components: 
 hashicorp-vault-plugin, kubernetes-plugin  
 
 
Created: 
 2020-03-11 15:04  
 
 
Environment: 
 Jenkins 2.204.5  Installed via helm chart version "1.9.21"  Installed plugins:  - blueocean:1.22.0  - command-launcher:1.4  - config-file-provider:3.6.3  - configuration-as-code:1.36  - credentials-binding:1.21  - file-leak-detector:1.6  - git:4.2.0  - hashicorp-vault-plugin:3.2.0  - jdk-tool:1.4  - job-dsl:1.76  - kubernetes:1.24.1  - matrix-auth:2.5  - oic-auth:1.7  - pipeline-aws:1.39  - pipeline-github-lib:1.0  - pipeline-utility-steps:2.5.0  - workflow-aggregator:2.6   Running on AWS EKS. Kubernetes version: v1.14.8  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Lasse Højgaard  
 

  
 
 
 
 

 
 Hi, Provisioning build agents on kubernetes somehow results in "Too Many Open Files". ``` $ ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jenkins 1 0.0 0.0 1148 4 ? Ss Mar06 0:11 /sbin/tini – /usr/local/bin/jenkins.sh --argumentsRealm.passwd.admin=${MASTER_ADMIN_PASSWORD} --argumentsRealm.roles.admin=admin --httpPort=8080 jenkins 7 1.1 7.1 3841028 1167032 ? Sl Mar06 82:21 java -Duser.home=/var/jenkins_home -Dpermissive-script-security.enabled=true -Xms512m -Xmx1024m -XX:MaxMetaspaceSize=200m -XX:CompressedClassSpaceSize=100m -Djenkins.model.Jenkins.slaveAgentPort=5 -jar / jenkins 15138 0.0 0.0 19976 3656 pts/0 Ss+ 14:46 0:00 bash jenkins 15922 0.1 0.0 19972 3436 pts/1 Ss 14:57 0:00 bash jenkins 15927 0.0 0.0 38384 3264 pts/1 R+ 14:58 0:00 ps aux $ ls -la /proc/7/fd | head -n 20 total 0 dr-x--. 2 jenkins jenkins 0 Mar 11 14:46 . dr-xr-xr-x. 9

[JIRA] (JENKINS-61436) Make wfapi endpoints support tree filtering

2020-03-11 Thread matthew.bren...@lenel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Brenner created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61436  
 
 
  Make wfapi endpoints support tree filtering   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Sam Van Oort  
 
 
Components: 
 pipeline-stage-view-plugin  
 
 
Created: 
 2020-03-11 14:50  
 
 
Environment: 
 Stage view 2.13  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Matthew Brenner  
 

  
 
 
 
 

 
 Per best practices for Jenkins' REST API all API requests should use the tree query string to filter the returned data and reduce load on Jenkins. Unfortunately the /wfapi endpoints (which in our use cases return the most data) appear to simply ignore this query string and return all data in every case. If we could filter the data returned by using the same tree=... query string as is available for Jenkins' /api endpoints that would be fantastic.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-47259) Support StreamAtChange for stream clients

2020-03-11 Thread jbot...@perforce.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jen Bottom commented on  JENKINS-47259  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support StreamAtChange for stream clients   
 

  
 
 
 
 

 
 A customer is currently requesting this functionality via Perforce Support channels.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.185674.1507056825000.5541.1583938020118%40Atlassian.JIRA.

[JIRA] (JENKINS-61435) Jenkins is trying to build remotely when want master

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sholom Sanders created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61435  
 
 
  Jenkins is trying to build remotely when want master   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 envinject-plugin, git-plugin  
 
 
Created: 
 2020-03-11 14:39  
 
 
Environment: 
 Jenkins version 2.204.1 on Windows Server 2012 R2  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Sholom Sanders  
 

  
 
 
 
 

 
 I have a job whose source code is in git. I have run this job previously and always stated at the beginning of log "Building on master in workspace D:\jenkins\workspace\CCI_MDM_BUILD1". All of a sudden it now says "Building remotely on 2-MTC-MDM-PRD-IM in workspace /export/local/mdmadmin/jenkins/workspace/CCI_MDM_BUILD1" How do i get it to build on master ONLY?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 lee benhart updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61433  
 
 
  Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
Change By: 
 lee benhart  
 
 
Environment: 
 Jenkins ver 2.204.2 git 4.0.0-rcgit-changelog 2.17git-client 3.0.0-rcgit-server 1.7github 1.29.4github-api 1.95github-branch-source 2.5.5github-organization-folder 1.6scm-api 2.6.3workflow-scm-step 2.9os.arch amd64os.name Linuxos.version 3.10.0-1062.9.1.el7.x86_64  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205111.1583935218000.5536.1583936880167%40Atlassian.JIRA.

[JIRA] (JENKINS-52374) Issue with unclosed LDAP connections

2020-03-11 Thread n...@ridgworld.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Ridgway commented on  JENKINS-52374  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Issue with unclosed LDAP connections   
 

  
 
 
 
 

 
 I am also seeing this issue.  Switching STARTTLS off isn't an option for me, is there any information I can provide to help diagnose/fix the issue?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.192168.1530728155000.5531.1583936220501%40Atlassian.JIRA.

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 lee benhart updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61433  
 
 
  Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
Change By: 
 lee benhart  
 
 
Component/s: 
 git-client-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.205111.1583935218000.5526.1583935980156%40Atlassian.JIRA.

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 lee benhart updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61433  
 
 
  Manual SCM Polling for pipeline starts even though no changes on branch   
 

  
 
 
 
 

 
Change By: 
 lee benhart  
 

  
 
 
 
 

 
 Manually setting a pipeline job to poll SCM is resulting in a build being triggered each and every time polling starts.In reviewing logs, the only change I see is the TAG created by the build itself.  No other commits are in place.Typical pipeline configuration is to poll SCM for change, build component, TAG the commit of the successful build, and post step will deleteDir() after each build.While a tag is not seen as a commit, it is clear that in GIT, a tag is given a unique hash.I have tried ignoring commits by the build user, but since the tag is not a code change, this does not work.I have tried ignoring commits with messages, but since the tag is not seen as a commit, this does not work.I have tried using a REGEX to ignore tags, however I am getting errors with the regex and illegal characters, so this has not worked either.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-61357) every time I click the Save button in Configure System Jenkins Crashes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-61357  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: every time I click the Save button in Configure System Jenkins Crashes   
 

  
 
 
 
 

 
 Thanks. Can you provide more details of the current working state? For instance, would you be willing to upload a "support bundle" with the support-core plugin. That will provide plugin versions, Jenkins version, etc.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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.204942.1583438464000.5522.1583935800118%40Atlassian.JIRA.

[JIRA] (JENKINS-61434) hudson/tasks/junit/TestResult : Unsupported major.minor version 52.0

2020-03-11 Thread vbor...@marinformatica.com.br (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vitor S. created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61434  
 
 
  hudson/tasks/junit/TestResult : Unsupported major.minor version 52.0   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2020-03-11-11-01-02-670.png, jkk.jpg  
 
 
Components: 
 maven-plugin  
 
 
Created: 
 2020-03-11 14:05  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Vitor S.  
 

  
 
 
 
 

 
 Hello, I'm having trouble compiling my java project (which it was and compiled in made and compiled in java 7), I tried to update and downgrade jenkins and plugins but without success about 10 days ago everything was working normally when I decided to update the maven so that every problem started, locally the project is being compiled normally My jenkins version: 1.651.3 Installed on Centos 7 My maven is in version 2.1.1 and the JDK is version 7_80 Error log trying to build the service: 

 

Parsing POMs
[workspace] $ /opt/jenkins/tools/hudson.model.JDK/JDK7/bin/java -cp /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.5.jar:/opt/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_2.0.7/boot/classworlds-1.1.jar hudson.maven.agent.Main /opt/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_2.0.7 /var/cache/jenkins/war/WEB-INF/lib/remoting-2.59.jar /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.5.jar 41171
<===[JENKINS REMOTING CAPACITY]===>channel started
ERROR: Failed to parse POMs
java.io.IOException: Remote call on Channel to Maven [/opt/jenkins/tools/hudson.model.JDK/JDK7/bin/java, -cp,

[JIRA] (JENKINS-61433) Manual SCM Polling for pipeline starts even though no changes on branch