date:20200103

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-60630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is   
 

  
 
 
 
 

 
 Can you explain further why you have a single pipeline job that switches from one branch to another and reads its Jenkinsfile from SCM?  That will cause the change history for the job to be a mixture of many different branches.  As far as I've seen, that makes the changelog unusable.That seems like it would be much better suited to use a multibranch pipeline or an organization folder so that each job is created and destroyed automatically when a branch is created or destroyed.I won't be able to attempt to duplicate this report for several days.  I'm on vacation now and am unlikely to investigate further until after I return from vacation. Can you provide more details on the last configuration that was working?  You indicate git plugin 3.0.0.  That version was released over 3 years ago.  Has it worked on any versions newer than 3.0.0?  If so, what is the most recent version where it worked the way you expected?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closed since it is not a defect in the git plugin but in command line git 2.24.0(2) for Windows  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-60632  
 
 
  git plugin no longer clones repositories with backslashes   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you 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-60632) git plugin no longer clones repositories with backslashes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-60632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git plugin no longer clones repositories with backslashes   
 

  
 
 
 
 

 
 Once command line git for Windows has been updated to allow fetch of repositories which contain backslash directory names, the git plugin will work. Alternatives you can use until then: 
 
Use command line git for Windows prior to the protectNTFS change (like git for windows 2.23.x or earlier) 
Use the config file provider plugin to deliver a $HOME/.gitconifg file to the agent which includes core.protectNTFS=false 
Integrate the proposed change into your own build of command line git for Windows and use it on all Windows machines that need to do this.  
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-60630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is   
 

  
 
 
 
 

 
 Can you explain further why you have a single pipeline job that switches from one branch to another and reads its Jenkinsfile from SCM?  That  will cause the change history for the job to be a mixture of many different branches.  As far as I've seen, that makes the changelog unusable.That  seems like it would be much better suited to use a multibranch pipeline or an organization folder so that each job is created and destroyed automatically when a branch is created or destroyed.I won't be able to attempt to duplicate this report for several days.  I'm on vacation now and am unlikely to investigate further until after I return from vacation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is

2020-01-03 Thread alex.martynenko.prese...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-60630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is   
 

  
 
 
 
 

 
 Can you explain further why you have a single pipeline job that switches from one branch to another and reads its Jenkinsfile from SCM?  That seems like it would be much better suited to use a multibranch pipeline or an organization folder so that each job is created and destroyed automatically when a branch is created or destroyed. I won't be able to attempt to duplicate this report for several days.  I'm on vacation now and am unlikely to investigate further until after I return from vacation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60602) Bitbucket integration with Jenkins

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Martynenko commented on  JENKINS-60602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket integration with Jenkins   
 

  
 
 
 
 

 
 Hi Christian Del Monte and dear sirs! Do you have any updates in case? Thanks in advance.    Regards, Alexander  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60637) plugin downloads are not retried

2020-01-03 Thread slide.o....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60637  
 
 
  plugin downloads are not retried   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Natasha Stopa  
 
 
Components: 
 plugin-installation-manager-tool  
 
 
Created: 
 2020-01-03 22:43  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Alex Earl  
 

  
 
 
 
 

 
 In the install-plugins.sh script, it retries up to 3 times to download a file. It would be nice to have a similar retry mechanism in this tool.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[JIRA] (JENKINS-60636) Using method pointers results in warning

2020-01-03 Thread bruce.brou...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Brouwer updated  JENKINS-60636  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Sorry, didn't see the previous issue in my search.   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-60636  
 
 
  Using method pointers results in warning   
 

  
 
 
 
 

 
Change By: 
 Bruce Brouwer  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-60636) Using method pointers results in warning

2020-01-03 Thread bruce.brou...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Brouwer updated  JENKINS-60636  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60636  
 
 
  Using method pointers results in warning   
 

  
 
 
 
 

 
Change By: 
 Bruce Brouwer  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60636) Using method pointers results in warning

2020-01-03 Thread bruce.brou...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Brouwer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60636  
 
 
  Using method pointers results in warning   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-cps-plugin  
 
 
Created: 
 2020-01-03 22:21  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Bruce Brouwer  
 

  
 
 
 
 

 
 When invoking a closure created from a method pointer, the following warning is printed in the log: 

 

expected to call org.codehaus.groovy.runtime.MethodClosure.call but wound up catching my.method; see:
https://jenkins.io/redirect/pipeline-cps-method-mismatches/  

 The code works correctly, but produces this warning: 

 

def method() {
  // do stuff
}
def runIt(Closure closure) {
  closure.call()
}
runIt(this.) 

 The workaround gets rid of the warning: 

 

def method() {
  // do stuff
}
def runIt(Closure closure) {
  closure.call()
}
runIt({ method() })  

 I would prefer to not have to create this extra closure. My situation is a little more complex than this as the method is from another vars script, but it should be the same situation.

[JIRA] (JENKINS-60354) Updated pipeline build step does not work with retry, catchError, or warnError

2020-01-03 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated  JENKINS-60354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 A fix for this issue has been released in Pipeline: Basic Steps Plugin 2.19 and Pipeline: Build Step Plugin 2.11. Both plugins must be updated for the fix to take effect. Thanks Jonathan B for reporting the issue!  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-60354  
 
 
  Updated pipeline build step does not work with retry, catchError, or warnError   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 workflow-basic-steps 2.19, pipeline-build-step 2.11, workflow-step-api 2.22  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[JIRA] (JENKINS-57260) git blame fails for out-of-tree builds

2020-01-03 Thread ullrich.haf...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-57260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git blame fails for out-of-tree builds   
 

  
 
 
 
 

 
 You need to use different IDs when using two recordIssues steps with the same tool.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60473) Docker pipeline: 'absolute path' error when running linux container under windows host

2020-01-03 Thread roberthec...@googlemail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Hecker edited a comment on  JENKINS-60473  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker pipeline: 'absolute path' error when running linux container under windows host   
 

  
 
 
 
 

 
 Hi Eric,Thank you very much for your effort, and the upload of the modified source code of the docker plugin.1.) I managed to get the plugin on my pc compiled.2.) I used  fro  for  a test following pipeline as example:  (From: [https://jenkins.io/doc/book/pipeline/docker/]) {code:java}pipeline {agent {docker { image 'node:7-alpine' }}stages {stage('Test') {steps {sh 'node --version'}}}}{code}3)Test execution is resulting in a failure (Exit Code -2):{code:java}C:\Program Files (x86)\Jenkins\workspace\docker-jenkins-test_master>docker inspect -f . node:7-alpine .[Pipeline] withDockerContainerJenkins does not seem to be running inside a container$ docker run -d -t -w "/c/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/" -v "C:/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/:/c/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/" -v "C:/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master@tmp/:/c/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master@tmp/" -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  -e  node:7-alpine cat$ docker top ee78f93ed896282757e96f87cc6c73210b63e14f4a6bdc94f229db4468721db1[Pipeline] {[Pipeline] stage[Pipeline] { (Test)[Pipeline] shprocess apparently never started in C:\Program Files (x86)\Jenkins\workspace\docker-jenkins-test_master@tmp\durable-275a00eb(running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)[Pipeline] }[Pipeline] // stage[Pipeline] }$ docker stop --time=1 ee78f93ed896282757e96f87cc6c73210b63e14f4a6bdc94f229db4468721db1$ docker rm -f ee78f93ed896282757e96f87cc6c73210b63e14f4a6bdc94f229db4468721db1[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -2Finished: FAILURE{code}4) Is the docker option "-v" correct? (-v "C:/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/:*/c/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/*") The bold marked path looks like an windows path, but does this path work inside a linux container ?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-60473) Docker pipeline: 'absolute path' error when running linux container under windows host

2020-01-03 Thread roberthec...@googlemail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Hecker commented on  JENKINS-60473  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker pipeline: 'absolute path' error when running linux container under windows host   
 

  
 
 
 
 

 
 Hi Eric, Thank you very much for your effort, and the upload of the modified source code of the docker plugin. 1.) I managed to get the plugin on my pc compiled. 2.) I used fro a test following pipeline as example: 

 

pipeline {
agent {
docker { image 'node:7-alpine' }
}
stages {
stage('Test') {
steps {
sh 'node --version'
}
}
}
}
 

 3)Test execution is resulting in a failure (Exit Code -2): 

 

C:\Program Files (x86)\Jenkins\workspace\docker-jenkins-test_master>docker inspect -f . node:7-alpine 
.
[Pipeline] withDockerContainer
Jenkins does not seem to be running inside a container
$ docker run -d -t -w "/c/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/" -v "C:/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/:/c/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/" -v "C:/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master@tmp/:/c/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master@tmp/" -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  -e  node:7-alpine cat
$ docker top ee78f93ed896282757e96f87cc6c73210b63e14f4a6bdc94f229db4468721db1
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Test)
[Pipeline] sh
process apparently never started in C:\Program Files (x86)\Jenkins\workspace\docker-jenkins-test_master@tmp\durable-275a00eb
(running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
$ docker stop --time=1 ee78f93ed896282757e96f87cc6c73210b63e14f4a6bdc94f229db4468721db1
$ docker rm -f ee78f93ed896282757e96f87cc6c73210b63e14f4a6bdc94f229db4468721db1
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code -2
Finished: FAILURE
 

 4) Is the docker option "-v" correct? (-v "C:/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/:/c/Program Files (x86)/Jenkins/workspace/docker-jenkins-test_master/") The bold marked path looks like an windows path, but does this path work inside a linux container ?

[JIRA] (JENKINS-60635) Build periodically help should offer timezones as a pop out

2020-01-03 Thread jsoref+jenk...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60635  
 
 
  Build periodically help should offer timezones as a pop out   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2020-01-03 20:38  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Soref  
 

  
 
 
 
 

 
 Go to a classic job and check Build periodically. Then click the  next to the schedule. You'll get an incredibly long box: 

 

Time zone specification
Periodic tasks are normally executed at the scheduled time in the time zone of the Jenkins master JVM (currently America/Toronto). This behavior can optionally be changed by specifying an alternative time zone in the first line of the field. Time zone specification starts with TZ=, followed by the ID of a time zone.Complete example of a schedule with a time zone specification:TZ=Europe/London
# This job needs to be run in the morning, London time
H 8 * * *
# Butlers do not have a five o'clock, so we run the job again
H(0-30) 17 * * *
  
The supported time zones depend on the Java runtime Jenkins is running on. The list of supported time zone IDs on this instance is:
Africa/Abidjan
Africa/Accra
Africa/Addis_Ababa
Africa/Algiers
Africa/Asmara
Africa/Asmera
Africa/Bamako
Africa/Bangui
Africa/Banjul
Africa/Bissau
Africa/Blantyre
Africa/Brazzaville
Africa/Bujumbura
Africa/Cairo
Africa/Casablanca
Africa/Ceuta
Africa/Conakry
Africa/Dakar
Africa/Dar_es_Salaam
Africa/Djibouti
Africa/Douala
Africa/El_Aaiun
Africa/Freetown
Africa/Gaborone
Africa/Harare
Africa/Johannesburg
Africa/Juba
Africa/Kampala
Africa/Khartoum
Africa/Kigali
Africa/Kinshasa
Africa/Lagos
Africa/Libreville
Africa/Lome
Africa/Luanda
Africa/Lubumbashi
Africa/Lusaka
Africa/Malabo
Africa/Maputo
Africa/Maseru
Africa/Mbabane
Africa/Mogadishu
Africa/Monrovia
Africa/Nairobi
Africa/Ndjamena
Africa/Niamey
Africa/Nouakchott

[JIRA] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders

2020-01-03 Thread anku...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ankur commented on  JENKINS-24767  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Role-based Authorization Strategy not working with sub-folders   
 

  
 
 
 
 

 
 Is there a way I can give access to child folder directly without specifically giving access to Parent folder ? I have following structure: FolderA -> FolderB -> FolderC -> jobs It works fine if I give specific read permissions to Folder A first, then another role for giving read access to Folder B and then another role giving read access to Folder C, which means four roles to get access to jobs. Role 1 -> ^FolderA Role 2 -> ^FolderA/FolderB Role 3 -> ^FolderA/FolderB/FolderC Role 4 -> ^FolderA/FolderB/FolderC/.* Can the number of roles be reduced somehow by defining a pattern which can give direct access to Folder C , which internally would mean access granted to Folder A and B ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60634) Define WORKSPACE_TMP=.../workspace/jobname@tmp

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-60634  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60634  
 
 
  Define WORKSPACE_TMP=.../workspace/jobname@tmp   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult

2020-01-03 Thread ullrich.haf...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-57566  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default security prohibits ResultAction's getResult   
 

  
 
 
 
 

 
 Thanks for the details, I think I can write a test case with the ideas used in the script and add the corresponding whitelisting information.  
 
I do have a question regarding this though: Is there a reason why recordIssues returns void? I.e. would it be possible to return a result for this step as well?
 It returns void because the step may create several actions. I can return a list of actions or an aggregation of all actions. What makes more sense to you?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60634) Define WORKSPACE_TMP=.../workspace/jobname@tmp

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60634  
 
 
  Define WORKSPACE_TMP=.../workspace/jobname@tmp   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 

  
 
 
 
 

 
 {{WorkspaceList.createTempDir}} (JENKINS-27152) is used by various plugins, and from Pipeline builds you can even use {{pwd tmp: true}} to use this location for custom purposes, but this is awkward. In practice many scripts wind up just binding this to a variable ([example|https://github.com/jenkinsci/kubernetes-plugin/blob/281d296f9a5945094a59b0f6f7362cbceede762a/Jenkinsfile#L10]). We should define it out of the box. {{$WORKSPACE}} is used for the main workspace (though not frequently needed as this is also the default working directory). {{$WORKSPACE_TMP}} seems like an intuitive name for the new property and matches the style of the {{@tmp}} suffix. [Standard practice in Linux|https://en.wikipedia.org/wiki/TMPDIR] is to allow {{$TMPDIR}} to define a temporary directory, but using this variable name would result in a behavioral change for some existing scripts that may be unwanted, for example if {{/tmp}} is a RAM filesystem while the Jenkins workspace is persistent; we would like to offer a facility that users can opt in to where it makes sense (for example for project-specific caches) but not where it does not make sense (temporary files that are soon after deleted).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[JIRA] (JENKINS-60634) Define WORKSPACE_TMP=.../workspace/jobname@tmp

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-60634  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60634) Define WORKSPACE_TMP=.../workspace/jobname@tmp

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60634  
 
 
  Define WORKSPACE_TMP=.../workspace/jobname@tmp   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 core, workflow-durable-task-step-plugin  
 
 
Created: 
 2020-01-03 19:50  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 WorkspaceList.createTempDir (JENKINS-27152) is used by various plugins, and from Pipeline builds you can even use pwd tmp: true to use this location for custom purposes, but this is awkward. In practice many scripts wind up just binding this to a variable (example). We should define it out of the box.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-30600) git isn't run inside build container

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-30600  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git isn't run inside build container   
 

  
 
 
 
 

 
 At least adding a warning in git #811.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command

2020-01-03 Thread rene.sche...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe commented on  JENKINS-45228  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command   
 

  
 
 
 
 

 
 I would like to ask everybody interested to test the beta version Mark Waite just released - see https://github.com/jenkinsci/git-client-plugin/releases/tag/git-client-3.1.0-beta  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command

2020-01-03 Thread rene.sche...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated  JENKINS-45228  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45228  
 
 
  Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60143) Behavior SSH Checkout not working after Jenkins restart

2020-01-03 Thread alv...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Alvizu commented on  JENKINS-60143  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Behavior SSH Checkout not working after Jenkins restart   
 

  
 
 
 
 

 
 It looks like this was also an issue in github branch source plugin fixed here: https://github.com/jenkinsci/github-branch-source-plugin/pull/205/files  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed

2020-01-03 Thread manuelramonleonjime...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 neelima devana edited a comment on  JENKINS-57695  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jira issue not created when jenkins build failed   
 

  
 
 
 
 

 
  Am  experiencing  the same issue  with null pointer exception, its inconsistent in creating the issues in Jira .+*Work Around:*+ Curl command  works fine in create issue in Jira , make sure about your mandatory Jira fields and add them to txt file . {{curl --D-- -u *username:password* -X POST --data-binary "@/**/*abc.txt*" -H "Content-Type: application/json" [https://*|https://%2A/]*/rest/api/2/issue/}} { "fields": {       "project":     {              {                  "key": "abc"         }             } ,       "summary": "Sample Test ticket from Jenkins.",       "description": "Creating of an issue using project keys and issue type names using the REST API",       "issuetype":  {            {                  "name": "Task"         }         } ,      "customfield_10002":     {       {                  "id": "1"          }           } ,     "components":[  \ {"name":"Jenkins"}  ],     "assignee" :   {           {             "name" :  "abc"       }           }   } {{ } }  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60473) Docker pipeline: 'absolute path' error when running linux container under windows host

2020-01-03 Thread roberthec...@googlemail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Hecker commented on  JENKINS-60473  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker pipeline: 'absolute path' error when running linux container under windows host   
 

  
 
 
 
 

 
 Hi Eric, when you send me a link to your build version of your plugin, i can test it also on my environment. Please let me know, if i can help.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60633) Update maven to 3.6.3 on ATH container

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60633  
 
 
  Update maven to 3.6.3 on ATH container   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ramon Leon  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2020-01-03 16:07  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ramon Leon  
 

  
 
 
 
 

 
 When running ./ath-container.sh it fails with:   

 

curl: (22) The requested URL returned error: 404 Not Found
The command '/bin/sh -c curl -ffSLO https://www.apache.org/dist/maven/maven-3/3.6.1/binaries/apache-maven-3.6.1-bin.tar.gz && tar -xvzf apache-maven-3.6.1-bin.tar.gz -C /opt/ && mv /opt/apache-maven-* /opt/maven' returned a non-zero code: 22
./ath-container.sh: Error 22 on line 13: docker build --build-arg=uid="$uid" --build-arg=gid="$gid" "$DIR/src/main/resources/ath-container" -t "$tag"

 

     The reason is that https://www.apache.org/dist/maven/maven-3/3.6.1/binaries/apache-maven-3.6.1-bin.tar.gz is no longer available. So any new fresh installation of ATH will fail. I will update the URL to use the archive repo: https://archive.apache.org/dist/maven/maven-3/3.6.1/binaries/apache-maven-3.6.1-bin.tar.gz Although we can use the 3.6.3 binaries, I don't want to take any risk as I have no time to check whether the new version may imply any problem (don't seem so but who knows) If someone wants to update and check the 3.6.3 version, I think it is best to use: https://archive.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz  Instead of: https://www.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz To avoid the same issue in the future.

[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed

Title: Message Title


 
 
 
 

 
 
 

 
   
 neelima devana edited a comment on  JENKINS-57695  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jira issue not created when jenkins build failed   
 

  
 
 
 
 

 
  Am  experiencing  the same issue  with null pointer exception, its inconsistent in creating the issues in Jira .+*Work Around:*+ Curl command  works fine in create issue in Jira , make sure about your mandatory Jira fields and add them to txt file . {{curl - - D- -  -u *username:password* -X POST --data-binary "@/**/*abc.txt*" -H "Content-Type: application/json" [https://*|https://%2A/]*/rest/api/2/issue/}} { "fields": {       "project":      {           "key": "abc"        },       "summary": "Sample Test ticket from Jenkins.",       "description": "Creating of an issue using project keys and issue type names using the REST API",       "issuetype":{           "name": "Task"        },      "customfield_10002":      {         "id": "1"         },     "components":[{"name":"Jenkins"}],     "assignee" :     {        "name" :  "abc"      }    }}{{}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed

Title: Message Title


 
 
 
 

 
 
 

 
   
 neelima devana edited a comment on  JENKINS-57695  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jira issue not created when jenkins build failed   
 

  
 
 
 
 

 
  Am  experiencing  the same issue  with null pointer exception, its inconsistent in creating the issues in Jira .+*Work Around:*+ Curl command  works fine in create issue in Jira , make sure about your mandatory Jira fields and add them to txt file . {{curl -D-    -u *username:password* -X POST --data-binary "@/**/*abc.txt*" -H "Content-Type: application/json" [https://*|https://%2A/]*/rest/api/2/issue/}} { "fields": {       "project":      {           "key": "abc"        },       "summary": "Sample Test ticket from Jenkins.",       "description": "Creating of an issue using project keys and issue type names using the REST API",       "issuetype":{           "name": "Task"        },      "customfield_10002":      {         "id": "1"         },     "components":[ \\  {"name":"Jenkins"}  ],     "assignee" :     {        "name" :  "abc"      }    }}{{}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed

Title: Message Title


 
 
 
 

 
 
 

 
   
 neelima devana edited a comment on  JENKINS-57695  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jira issue not created when jenkins build failed   
 

  
 
 
 
 

 
  Am  experiencing  the same issue  with null pointer exception, its inconsistent in creating the issues in Jira .+*Work Around:*+ Curl command  works fine in create issue in Jira , make sure  how your  about your    mandatory Jira fields and add them to txt file . {{curl -D- -u *username:password* -X POST --data-binary "@/**/*abc.txt*" -H "Content-Type: application/json"  [  https://* |https://%2A/] */rest/api/2/issue/}} { "fields": {       "project":        {   {           "key": "abc"         }  ,       "summary": "Sample Test ticket from Jenkins.",       "description": "Creating of an issue using project keys and issue type names using the REST API",       "issuetype":  {  {           "name": "Task"         }  ,      "customfield_10002":        {  {         "id": "1"          }  ,     "components":[\ \ {"name":"Jenkins"}],     "assignee" :       {  {        "name" :  "abc"       }         }}{{}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed

Title: Message Title


 
 
 
 

 
 
 

 
   
 neelima devana commented on  JENKINS-57695  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jira issue not created when jenkins build failed   
 

  
 
 
 
 

 
  Am  experiencing  the same issue  with null pointer exception, its inconsistent in creating the issues in Jira . Work Around:  Curl command  works fine in create issue in Jira , make sure how your about your  mandatory Jira fields and add them to txt file .  curl D -u username:password -X POST --data-binary "@//abc.txt" -H "Content-Type: application/json" https://**/rest/api/2/issue/   {  "fields": {        "project":         {           "key": "abc"        } ,        "summary": "Sample Test ticket from Jenkins.",        "description": "Creating of an issue using project keys and issue type names using the REST API",        "issuetype":  {           "name": "Task"        } ,       "customfield_10002":         {         "id": "1"         } ,      "components":[\{"name":"Jenkins"}],      "assignee" :        {        "name" :  "abc"      }      } } {{}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-57260) git blame fails for out-of-tree builds

2020-01-03 Thread mark.rze...@lovion.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 m l reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 see last comment  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57260  
 
 
  git blame fails for out-of-tree builds   
 

  
 
 
 
 

 
Change By: 
 m l  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-57260) git blame fails for out-of-tree builds

2020-01-03 Thread mark.rze...@lovion.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 m l updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57260  
 
 
  git blame fails for out-of-tree builds   
 

  
 
 
 
 

 
Change By: 
 m l  
 
 
Comment: 
 see last comment  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-57260) git blame fails for out-of-tree builds

2020-01-03 Thread mark.rze...@lovion.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 m l commented on  JENKINS-57260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git blame fails for out-of-tree builds   
 

  
 
 
 
 

 
 After the fixes git blame does not fail when I start analyzing the warnings without dir statement (see comment of 2019-10-18). Thanx! But this works for single git repository only    -  Git blame still fails for multiple git repositories.   An example with two git repositories: My pipeline checks out the source code in separate folders by settings the option 

 

skipDefaultCheckout()
 

 I checkout the sources into ${ws}/Platform and ${ws}/Modules via 

 

stage('Checkout') {
steps {
script {
def gitVarsPlatform = checkout([$class: 'GitSCM', 
branches: [[name: "${env.BRANCH_NAME}"]],
extensions: [[$class: 'CleanCheckout', $class: 'RelativeTargetDirectory', relativeTargetDir: 'Platform']], 
userRemoteConfigs: [[url: 'https://X.git', name: 'Platform', credentialsId: '' ]]
])
lastChanges since: 'LAST_SUCCESSFUL_BUILD', format:'SIDE',matching: 'LINE'

def gitVarsModules = checkout([$class: 'GitSCM',
branches: [[name: "${env.BRANCH_NAME}"]],
extensions: [[$class: 'CleanBeforeCheckout'], [$class: 'RelativeTargetDirectory', relativeTargetDir: 'Modules']],
userRemoteConfigs: [[url: 'https://Y_modules.git', name: 'Modules', credentialsId: '']]
])
}
}
}
 

 When I start analyzing the warnings without dir statement: 

 

post {
always {
recordIssues enabledForFailure: true, sourceCodeEncoding: 'UTF-8', tool: msBuild(reportEncoding: 'UTF-8')
}
 }
 

 Warnings are counted correctly but git blame fails with 

 
[Pipeline] recordIssues
16:05:49  [MSBuild] Sleeping for 5 seconds due to JENKINS-32191...
16:05:54  [MSBuild] Parsing console log (workspace: 'C:\jenkins\w\_platform_feature_jenkins_master')
16:06:11  using credential 
16:06:11  using credential 
16:06:11  using credential 
16:06:11   > git rev-parse "HEAD^{commit}" # timeout=10
16:06:11  using credential 
16:06:11   > git rev-parse "HEAD^{commit}" # timeout=10
16:06:21   > git rev-parse "HEAD^{commit}" # timeout=10
16:10:39  [MSBuild] [-ERROR-] Errors while extracting author and commit information from Git:
16:10:39  [MSBuild] [-ERROR-] - skipping file 'C:/jenkins/w/_platform_feature_jenkins_master/Modules/XXX/AvailabilityCheckFeatures.cs' (outside of work

[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael DeGuzis commented on  JENKINS-60632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git plugin no longer clones repositories with backslashes   
 

  
 
 
 
 

 
 Mark once these two PRs are done, will you need to update your plugin to use the new executable/binary? 
 
https://github.com/git-for-windows/git/pull/2437 
https://github.com/git/git/pull/682 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael DeGuzis edited a comment on  JENKINS-60632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git plugin no longer clones repositories with backslashes   
 

  
 
 
 
 

 
 Ok, at least it's good confirmation for others to note this as being out of your control. Now that the issue is logged and with references, it could be closed and others cna track the git for windows issue.  It's unfortunate I cannot implement the workaround with this plugin, effectively leaving me stranded. Is it not possible to modify the GitSCM class parameters (much like I do already for submodule handling) to implement the workaround?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael DeGuzis commented on  JENKINS-60632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git plugin no longer clones repositories with backslashes   
 

  
 
 
 
 

 
 Ok, at least it's good confirmation for others to note this as being out of your control. Now that the issue is logged and with references, it could be closed and others cna track the git for windows issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-56076) Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Well-known limitation.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-56076  
 
 
  Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-21342) CliGitAPIImpl is hard-coded to use LocalLauncher

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is a bit older but JENKINS-30600 has more activity and is closer to what people are likely to search for.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-21342  
 
 
  CliGitAPIImpl is hard-coded to use LocalLauncher   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you 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-60632) git plugin no longer clones repositories with backslashes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-60632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git plugin no longer clones repositories with backslashes   
 

  
 
 
 
 

 
 That is an issue which the git plugin cannot fix because it is inside command line git for windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael DeGuzis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60632  
 
 
  git plugin no longer clones repositories with backslashes   
 

  
 
 
 
 

 
Change By: 
 Michael DeGuzis  
 

  
 
 
 
 

 
 https://plugins.jenkins.io/gitVersion 4.0.0.0While I no longer have any file (since 2017) in my files on any branch, the git tree is being picked up and  killing  interfering with  the clone  so that Jenkins throws an incorrect exit code .{code}$ rm -rf python-mypkg && git clone https://github.com/org/mypkgCloning into 'python-mypkg'...remote: Enumerating objects: 3, done.remote: Counting objects: 100% (3/3), done.remote: Compressing objects: 100% (2/2), done.error: filename in tree entry contains backslash: '\'remote: Total 7683 (delta 0), reused 2 (delta 0), pack-reused 7680Receiving objects: 100% (7683/7683), 1.34 MiB | 5.39 MiB/s, done.error: filename in tree entry contains backslash: '\'error: filename in tree entry contains backslash: '\'Resolving deltas: 100% (5011/5011), done.{code} Jenkins:{code}Cloning the remote Git repository > git config core.sparsecheckout # timeout=10 > git checkout -f 1bcc1100ab4624b864b3e8072cb8f171a6d08d77 # timeout=10Cloning repository https://github.com/org/mypkg > git init C:\Jenkins\workspace\operations\job\mypkh # timeout=10Fetching upstream changes from https://github.com/GeisingerHealthSystem/python-udaopstools > git --version # timeout=10using GIT_ASKPASS to set credentials Ops team machine account > git fetch --tags --force --progress -- https://github.com/org/mypk +refs/heads/ * :refs/remotes/origin/* # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://github.com/org/mypkg +refs/heads/*:refs/remotes/origin/*" returned status code 1:stdout: stderr: remote: Enumerating objects: 3, done.remote: Counting objects:  33% (1/3)remote: Counting objects:  66% (2/3)remote: Counting objects: 100% (3/3)remote: Counting objects: 100% (3/3), done.remote: Compressing objects:  50% (1/2)remote: Compressing objects: 100% (2/2)remote: Compressing objects: 100% (2/2), done.Receiving objects:   0% (1/7683)Receiving objects:   1% (77/7683)Receiving objects:   2% (154/7683)Receiving objects:   3% (231/7683)Receiving objects:   4% (308/7683)Receiving objects:   5% (385/7683)Receiving objects:   6% (461/7683)Receiving objects:   7% (538/7683)Receiving objects:   8% (615/7683)Receiving objects:   9% (692/7683)Receiving objects:  10% (769/7683)Receiving objects:  11% (846/7683)Receiving objects:  12% (922/7683)Receiving objects:  13% (999/7683)Receiving objects:  14% (1076/7683)Receiving objects:  15% (1153/7683)Receiving objects:  16% (1230/7683)Receiving objects:  17% (1307/7683)Receiving objects:  18% (1383/7683)Receiving objects:  19% (1460/7683)Receiving objects:  20% (1537/7683)Receiving objects:  21% (1614/7683)Receiving objects:  22% (1691/7683)Receiving objects:  23% (1768/7683)Receiving objects:  24% (1844/7683)Receiving objects:  25%

[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes

2020-01-03 Thread manuelramonleonjime...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael DeGuzis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60632  
 
 
  git plugin no longer clones repositories with backslashes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2020-01-03 13:35  
 
 
Environment: 
 Jenkins LTS 2.204.1 (Docker)  
 
 
Labels: 
 git pipline  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael DeGuzis  
 

  
 
 
 
 

 
 https://plugins.jenkins.io/git Version 4.0.0.0 While I no longer have any file (since 2017) in my files on any branch, the git tree is being picked up and killing the clone. 

 

$ rm -rf python-mypkg && git clone https://github.com/org/mypkg
Cloning into 'python-mypkg'...
remote: Enumerating objects: 3, done.
remote: Counting objects: 100% (3/3), done.
remote: Compressing objects: 100% (2/2), done.
error: filename in tree entry contains backslash: '\'
remote: Total 7683 (delta 0), reused 2 (delta 0), pack-reused 7680
Receiving objects: 100% (7683/7683), 1.34 MiB | 5.39 MiB/s, done.
error: filename in tree entry contains backslash: '\'
error: filename in tree entry contains backslash: '\'
Resolving deltas: 100% (5011/5011), done.
 

 Related: 
 
https://github.com/git-for-windows/git/issues/2435

[JIRA] (JENKINS-50401) Checkout resolution misbehaves with local branch and forward slashes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon commented on  JENKINS-50401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Checkout resolution misbehaves with local branch and forward slashes   
 

  
 
 
 
 

 
 Mark Waite I'm a bit confused about this. Is it fixed actually? Which version? I saw this PR but it was closed without merging https://github.com/jenkinsci/branch-api-plugin/pull/47 Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-59396) AWT initialized even with -Djava.awt.headless=true

2020-01-03 Thread s...@morgenlan.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sascha Dierkes commented on  JENKINS-59396  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AWT initialized even with -Djava.awt.headless=true   
 

  
 
 
 
 

 
 May be this helps as work-around:   On Linux systems, the fontconfig.x86_64 package should be installed to avoid a NullPointerException error when the AWT font subsystem is initialized. Work is ongoing at the AdoptOpenJDK project to fix this issue for their OpenJDK binaries.   (https://www.eclipse.org/openj9/docs/adoptopenjdk/)    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60631) How to create shortcutlinks for matrix combination parameters through jenkins job dsl

2020-01-03 Thread srivamsivaddl...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 srivamsi vaddla created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60631  
 
 
  How to create shortcutlinks for matrix combination parameters through jenkins job dsl   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2020-01-03 13:02  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 srivamsi vaddla  
 

  
 
 
 
 

 
 How to create shortcutlinks for matrix combination parameters through jenkins job dsl Hi Team, I have created a matrix job in jenkins which has matrix comibination parameters through jenkins job DSL. But unable to create custom shortcutlinks for my job. For the below configuration:  parameters  { matrixCombinationsParam('Configure Parameters',"",'Choose the Activity') } But i want to create the custom shortcutlinks with following items. All None DEV QA BETA But it is creating the default shortcutlinks as shown below SUCCESS FAILED All None  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult

2020-01-03 Thread david.wri...@bluewin.ch (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David Wright edited a comment on  JENKINS-57566  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default security prohibits ResultAction's getResult   
 

  
 
 
 
 

 
 Initially I was struggling to obtain the result of the warnings-ng quality gates, however thanks to this issue and [~drulli]'s help on Gitter I managed to do so. Since I am one of the admins of the Jenkins instance I was able to whitelist this {{ResultAction::getResult}} access.   I do have a question regarding this though: Is there a reason why {{recordIssues}} returns {{void}}? I.e. would it be possible to return a result for this step as well?Also I believe that people would benefit from this being part of the documentation on [GitHub |[https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md]] and [Jenkins IO | [https://jenkins.io/doc/pipeline/steps/warnings-ng/]]I would be more than happy to do this myself, but to be honest I think my familiarity with the code is too limited. Below is my code, which is part of a groovy script where I created a custom step which executes some closure before running warnings NG and publishes a build badge and feeds the results to gitlab.Unfortunately, I was not able to get the {{QualityGateStatus, which would have helped me to set the build badge and Gitlab commit status to unstable. There was a method not found error if I remember correctly. I will have to perform some further analysis on this.}} {code:java}def runWarningsNGStage(String stageName, analysisTool, int newIssuesThreshold = 1, boolean newIssuesUnstable = false, int totalIssuesThreshold = 0, boolean totalIssuesUnstable = false, Closure body){  def buildBadge = addEmbeddableBadgeConfiguration(id: stageName, subject: stageName)stage(stageName)  {updateGitlabCommitStatus(name: stageName, state: 'running')buildBadge.setStatus('running')body()def foundIssues = scanForIssues(tool: analysisTool)def action = "" [foundIssues], qualityGates: [[threshold: newIssuesThreshold, type: 'NEW', unstable: newIssuesUnstable], [threshold: totalIssuesThreshold, type: 'TOTAL', unstable: totalIssuesUnstable]])// TODO: for some reason action.getQualityGateStatus().getResult() does not work, using this result we could set it to unstable as well.def result = action.isSuccessful()if(result){buildBadge.setStatus('passing')updateGitlabCommitStatus(name: stageName, state: 'success')}else{buildBadge.setStatus('failing')updateGitlabCommitStatus(name: stageName, state: 'failed')}  }}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-55705) Display link to downstream job in Blue Ocean

2020-01-03 Thread timo.s...@iki.fi (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Timo Sand commented on  JENKINS-55705  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Display link to downstream job in Blue Ocean   
 

  
 
 
 
 

 
 This seems to actually work now. But it only appears once the job is out pf the job queue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult

2020-01-03 Thread david.wri...@bluewin.ch (JIRA)

Title: Message Title

David Wright commented on JENKINS-57566

Re: Default security prohibits ResultAction's getResult

Initially I was struggling to obtain the result of the warnings-ng quality gates, however thanks to this issue and Ulli Hafner's help on Gitter I managed to do so. Since I am one of the admins of the Jenkins instance I was able to whitelist this ResultAction::getResult access. I do have a question regarding this though: Is there a reason why recordIssues returns void? I.e. would it be possible to return a result for this step as well? Also I believe that people would benefit from this being part of the documentation on [GitHub |https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md] and [Jenkins IO | https://jenkins.io/doc/pipeline/steps/warnings-ng/] I would be more than happy to do this myself, but to be honest I think my familiarity with the code is too limited.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

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

[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mahantesh Hoolikatti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60630  
 
 
  Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is   
 

  
 
 
 
 

 
Change By: 
 Mahantesh Hoolikatti  
 

  
 
 
 
 

 
 In a pipeline job (not multibranch pipeline job)  from a git repository where the "Branch Specifier" is given as a parameter and Lightweight option is also not checked but still I am getting below error   hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune – origin +refs/heads/${BRANCH}:refs/remotes/origin/${BRANCH}" returned status code 128: stdout:  stderr: fatal: Couldn't find remote ref refs/heads/${BRANCH}at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2372) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:80) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:563) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:348) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:197) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:173) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:101) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:82) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE   I am trying with git parameter as well as string parameter and on both occasions getting same errorI have observed the parameter value work well in fresstyle project  and multibranch pipeline job  but not work in simple pipeline job.I have tested with some git older version 3.0.0 which works will with pipeline job but same thing not works in 4.0.0 version.

[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mahantesh Hoolikatti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60630  
 
 
  Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is   
 

  
 
 
 
 

 
Change By: 
 Mahantesh Hoolikatti  
 

  
 
 
 
 

 
 In a pipeline job from a git repository where the "Branch Specifier" is given as a parameter and Lightweight option is also not checked but still I am getting below errorhudson.plugins.git.GitException: Command "git fetch --tags --progress --prune – origin +refs/heads/${BRANCH}:refs/remotes/origin/${BRANCH}" returned status code 128: stdout:  stderr: fatal: Couldn't find remote ref refs/heads/${BRANCH}at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2372) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:80) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:563) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:348) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:197) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:173) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:101) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:82) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILUREI am trying with git parameter as well as string parameter and on both occasions getting same errorI have observed the parameter value work well in fresstyle project but not work in simple pipeline job.I have tested with some git older version 3.0.0 which works will with pipeline job but same thing not works in  4.0.0  later  version .

[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mahantesh Hoolikatti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60630  
 
 
  Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is   
 

  
 
 
 
 

 
Change By: 
 Mahantesh Hoolikatti  
 

  
 
 
 
 

 
 In a pipeline job(not multibranch pipeline job) from a git repository where the "Branch Specifier" is given as a parameter and Lightweight option is also not checked but still I am getting below error  hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune  --  –  origin +refs/heads/${BRANCH}:refs/remotes/origin/${BRANCH}" returned status code 128:stdout: stderr: fatal: Couldn't find remote ref refs/heads/${BRANCH} at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2372) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:80) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:563) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:348) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:197) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:173) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:101) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:82) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Finished: FAILURE  I am trying with git parameter as well as string parameter and on both occasions getting same errorI have observed the parameter value work well in fresstyle project and multibranch pipeline job but not work in simple pipeline job.I have tested with some git older version 3.0.0 which works will with pipeline job but same thing not works in 4.0.0 version.

[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is