date:20191205

Title: Message Title


 
 
 
 

 
 
 

 
   
 Will Wagner commented on  JENKINS-60383  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remote nodes unable to checkout code   
 

  
 
 
 
 

 
 I believe I am using the correct stored credentials, they work fine if I downgrade the module to 0.3.5. They are https username and password that work everywhere else. Do they need to be something special?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60297) Jenkins could not read from remote repository

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Not a defect in the git plugin. Command line git or the remote git server are the most likely places to look  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-60297  
 
 
  Jenkins could not read from remote repository   
 

  
 
 
 
 

 
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-58736) Accessing "/assets" without asset name throws a 500

2019-12-05 Thread jthomp...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58736  
 
 
  Accessing "/assets" without asset name throws a 500   
 

  
 
 
 
 

 
Change By: 
 Jeff Thompson  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 2.190  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-6334  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for displaying changesets in submodule updates   
 

  
 
 
 
 

 
 Usually the best way for me to create tests is to open the source code in the Netbeans integrated development environment, select the class or classes that need tests, then select "Tools" and "Create / Update Tests". It will generate JUnit stubs to test the specific class. The IDE also provides a way to run individual tests and to run all the tests in a specific class.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60260) Serialisation issue while trying to report status to Gerrit

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luca Domenico Milanesio closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60260  
 
 
  Serialisation issue while trying to report status to Gerrit   
 

  
 
 
 
 

 
Change By: 
 Luca Domenico Milanesio  
 
 
Status: 
 Resolved 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.203247.1574664892000.1846.1575585480198%40Atlassian.JIRA.

[JIRA] (JENKINS-60260) Serialisation issue while trying to report status to Gerrit

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luca Domenico Milanesio resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60260  
 
 
  Serialisation issue while trying to report status to Gerrit   
 

  
 
 
 
 

 
Change By: 
 Luca Domenico Milanesio  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 gerrit-code-review-0.3.7  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60362) Gerrit Behaviours not executed

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luca Domenico Milanesio commented on  JENKINS-60362  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gerrit Behaviours not executed   
 

  
 
 
 
 

 
 Apologies for that, it was unexpected. It could be a side-effect of adding a special behaviour for the fetch operation on the SCM. Will try to reproduce the problem and fix in the next release.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60364) Environment variables not being set when Gerrit 2.14

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luca Domenico Milanesio commented on  JENKINS-60364  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables not being set when Gerrit 2.14   
 

  
 
 
 
 

 
 Gerrit v2.14 is EOL (see https://www.gerritcodereview.com/support.html). Have you considered upgrading? Do you see any error on the Gerrit logs? Or on the Jenkins logs?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60365) Environment variables not being set on post-submit

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luca Domenico Milanesio commented on  JENKINS-60365  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables not being set on post-submit   
 

  
 
 
 
 

 
 True, change-related variables on a regular branch are not set. That is due to the fact that Gerrit doesn't know what is the associated change because the branch is not pointing to a change ref. Jenkins is typically used with Gerrit for allowing pre-commit validation. What is your use-case on a regular branch?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60383) Remote nodes unable to checkout code

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luca Domenico Milanesio commented on  JENKINS-60383  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remote nodes unable to checkout code   
 

  
 
 
 
 

 
 Have you checked which credentials are used and what are the ones you were expecting to use?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates

2019-12-05 Thread timbla...@gmail.com (JIRA)

Title: Message Title

Tim Black commented on JENKINS-6334

Re: Support for displaying changesets in submodule updates

Thanks for your attention, Mark Waite. I am not a Java developer, but I've got the experience to make a positive contribution here, at least from the test and integration angle. I looked through the [Beginners Guide To Contributing|https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing], but I'm having trouble finding information on best practices for authoring such tests and for what resources to use for running the tests. The best lead I could find there was mention of [the jenkins-infra project|https://github.com/jenkins-infra/jenkins-infra], which contains configuration management tools that I'm guessing is how tests are expected to be run. Am I on the right track? Can you point me to any better docs, or your personal suggestions?

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

[JIRA] (JENKINS-54479) androidApkMove not moving Release Notes between Tracks

2019-12-05 Thread dathorn...@sinclairdigital.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David T commented on  JENKINS-54479  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: androidApkMove not moving Release Notes between Tracks   
 

  
 
 
 
 

 
 Christopher Orr Any chance this can be looked at? It's a pretty major thing that is missing.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60383) Remote nodes unable to checkout code

Title: Message Title


 
 
 
 

 
 
 

 
   
 Will Wagner commented on  JENKINS-60383  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remote nodes unable to checkout code   
 

  
 
 
 
 

 
 The output from the pipeline job that fails on a node is: using credential 6e96f729-8440-40bf-8710-88689c791d3b Cloning the remote Git repository Cloning repository https://code.office.carallon.com/pharos/magpie > C:\Program Files\Git\bin\git.exe init c:\jenkins\workspace\magpie-verify_01_8301_2 # timeout=10 Fetching upstream changes from https://code.office.carallon.com/pharos/magpie > C:\Program Files\Git\bin\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials  > C:\Program Files\Git\bin\git.exe fetch --tags --force --progress – https://code.office.carallon.com/pharos/magpie +refs/heads/:refs/remotes/origin/ # timeout=10 > C:\Program Files\Git\bin\git.exe config remote.origin.url https://code.office.carallon.com/pharos/magpie # timeout=10 > C:\Program Files\Git\bin\git.exe config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10 > C:\Program Files\Git\bin\git.exe config remote.origin.url https://code.office.carallon.com/pharos/magpie # timeout=10 Fetching upstream changes from https://code.office.carallon.com/pharos/magpie using GIT_ASKPASS to set credentials  > C:\Program Files\Git\bin\git.exe fetch --tags --force --progress – https://code.office.carallon.com/pharos/magpie refs/changes/01/8301/2:refs/remotes/origin/01/8301/2 # timeout=10 Checking out Revision 787879583e36f6e3afc5b60d35d15409d2c6a11a (refs/remotes/origin/01/8301/2) > C:\Program Files\Git\bin\git.exe rev-parse "01/8301/2^ {commit}" # timeout=10 > C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/01/8301/2^{commit} " # timeout=10 > C:\Program Files\Git\bin\git.exe config core.sparsecheckout # timeout=10 > C:\Program Files\Git\bin\git.exe checkout -f 787879583e36f6e3afc5b60d35d15409d2c6a11a # timeout=10 ERROR: Timeout after 10 minutes    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-59433) git clone fails on osx client with lfs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Will Wagner updated  JENKINS-59433  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59433  
 
 
  git clone fails on osx client with lfs   
 

  
 
 
 
 

 
Change By: 
 Will Wagner  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly

2019-12-05 Thread kmsche...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Konrad Scherer edited a comment on  JENKINS-52593  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support EKS authentication, or specifying a kubeconfig directly   
 

  
 
 
 
 

 
 I recently got Jenkins working with EKS and I feel your pain. Here is what I ended up cobbling together.I also installed python3, pip and awscli into my Jenkins container. I put the aws credentials directly in /home/jenkins/.aws/config though I read later you can have a Role on the EC2 instance and awscli can be configured to retrieve temp credentials for that role so no credentials need to stored on the instance.I was able to create the kubeconfig file and run the 'aws eks get-token' command but I couldn't figure out how to configure Jenkins. I was saved by a mailing list post and Google: [https://groups.google.com/d/msg/jenkinsci-users/8YpQL3eG-Zg/tznSHvkYAQAJ]I also added "{{-Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=60"}} to the Jenkins Master startup options as mentioned in [https://github.com/jenkinsci/kubernetes-plugin#running-with-a-remote-kubernetes-cloud-in-aws-eks]The kubeconfig needs to added to Jenkins as a "File Secret" in the Credentials section. Then in the Kubernetes plugin configuration, the credentials option must be set to that secret. The rest of the fields can be ignored. I hope this  will  helps  
 

  
 
 
 
 

 
 
 

 
 
 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-60383) Remote nodes unable to checkout code

Title: Message Title


 
 
 
 

 
 
 

 
   
 Will Wagner created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60383  
 
 
  Remote nodes unable to checkout code   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Luca Domenico Milanesio  
 
 
Components: 
 gerrit-code-review-plugin  
 
 
Created: 
 2019-12-05 20:33  
 
 
Environment: 
 jenkins 2.190.3  gerrit code review plugin 0.3.7  
 
 
Labels: 
 slave  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Will Wagner  
 

  
 
 
 
 

 
 Moving to 0.3.7 has broken checkout on remote nodes. They fail reporting unable to checkout the code after a 10 minute timeout. In the log on the gerrit server are hundreds of lines saying: WARN com.google.gerrit.httpd.ProjectBasicAuthFilter : Authentication failed for Username for 'https: account inactive or not provisioned in Gerrit So it appears that the remote node is using the wrong credentials to try to do the checkout.   Reverting to .03.5 and everything works fine  
 

  
 
 
 
 

 
 
 

 
 
 Add

[JIRA] (JENKINS-59196) List annotated tags with an extract of their respective annotated message.

2019-12-05 Thread rodrigotroncos...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rodrigo Troncoso commented on  JENKINS-59196  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: List annotated tags with an extract of their respective annotated message.   
 

  
 
 
 
 

 
 Any news on this, please it's been 3 months sisnce I upload this new feature. cloud you please give me some feedwack maibe. we really need this new functionality  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly

2019-12-05 Thread kmsche...@gmail.com (JIRA)

Title: Message Title

Konrad Scherer commented on JENKINS-52593

Re: Support EKS authentication, or specifying a kubeconfig directly

I recently got Jenkins working with EKS and I feel your pain. Here is what I ended up cobbling together. I also installed python3, pip and awscli into my Jenkins container. I put the aws credentials directly in /home/jenkins/.aws/config though I read later you can have a Role on the EC2 instance and awscli can be configured to retrieve temp credentials for that role so no credentials need to stored on the instance. I was able to create the kubeconfig file and run the 'aws eks get-token' command but I couldn't figure out how to configure Jenkins. I was saved by a mailing list post and Google: https://groups.google.com/d/msg/jenkinsci-users/8YpQL3eG-Zg/tznSHvkYAQAJ I also added "-Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=60" to the Jenkins Master startup options as mentioned in https://github.com/jenkinsci/kubernetes-plugin#running-with-a-remote-kubernetes-cloud-in-aws-eks The kubeconfig needs to added to Jenkins as a "File Secret" in the Credentials section. Then in the Kubernetes plugin configuration, the credentials option must be set to that secret. The rest of the fields can be ignored. I hope this will helps

Add Comment

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

[JIRA] (JENKINS-60382) withDockerRegistry only allows one registry

2019-12-05 Thread frechett...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Frechette created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60382  
 
 
  withDockerRegistry only allows one registry   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2019-12-05 18:38  
 
 
Environment: 
 Jenkins v2.176.3  docker-workflow plugin v1.21  
 
 
Labels: 
 docker docker-workflow-plugin plugin registry  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Eric Frechette  
 

  
 
 
 
 

 
 I have a script that requires two Docker registries (build image1, push to registry 1, build image2 that relies on image1, push to registry 2). I am unable to authenticate with two registries at once using withDockerRegistry. withDockerRegistry only takes one registry argument and if you attempt to nest withDockerRegistry steps, only the innermost registry is authenticated with. This doesn't work (only registry2 works): 

 

withDockerRegistry() {
    withDockerRegistry() {
        sh `my-script.sh`
    }
}
 

 withDockerRegistry should take an arbitrary amount of registries as arguments: 

 

withDockerRegistry([, ]) {
sh 'my-script.sh'
}

[JIRA] (JENKINS-12803) Installing plugin (without restarting) is broken with other non-refreshable extension.

2019-12-05 Thread jason.jard...@pega.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Jardina reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-12803  
 
 
  Installing plugin (without restarting) is broken with other non-refreshable extension.   
 

  
 
 
 
 

 
Change By: 
 Jason Jardina  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 
 
Assignee: 
 sogabe  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-12803) Installing plugin (without restarting) is broken with other non-refreshable extension.

2019-12-05 Thread jason.jard...@pega.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Jardina commented on  JENKINS-12803  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Installing plugin (without restarting) is broken with other non-refreshable extension.   
 

  
 
 
 
 

 
 Can this be reopened, possible regression?  I just had this happen to me: I'm running Jenkins 2.190.3, following instructions here: https://help.veracode.com/reader/PgbNZUD7j8aY7iG~hQZWxQ/_4G8gT1rhWMgVVtCI1C57A  I downloaded the Veracode Jenkins Plugin, custom hpi plugin.  When I get to step 5, upload the plugin, it starts to install and I get the following error:  veracode-jenkins-plugin [http://10.0.3.131:8080/static/ed09d5fa/images/24x24/red.png Failure - jenkins.ExtensionRefreshException: org.jvnet.hudson.test.TestExtensionLoader@9ac9542> doesn't support refresh at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2670) at hudson.PluginManager.start(PluginManager.java:951) at hudson.PluginManager.dynamicLoad(PluginManager.java:935) Caused: java.io.IOException: Failed to install veracode-jenkins-plugin plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:942) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:2052) Caused: java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:2056) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1740) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:112) at java.lang.Thread.run(Thread.java:748)  Even though the error presented itself and showed failure for install of plugin.  I rebooted the Jenkins server and it showed installed in the plugin section.  I then was able to use the plugin successfully.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth edited a comment on  JENKINS-60066  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "when changeset" not working in P4 multibranch pipeline   
 

  
 
 
 
 

 
 Just for anyone watching/finding this. Worked with Jesse and could not get  '  {code:java} **/Jenkinsfile ' {code}  to work, but did get  ' {code:java} //DEPOT_NAME/**/Jenkinsfile ' {code}  working. Windows Jenkins master connected to Linux P4d.+Note+ - Reason for using this - attempting to implement polling exclusions so (for example) artifact submits do not trigger the job.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth commented on  JENKINS-60066  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "when changeset" not working in P4 multibranch pipeline   
 

  
 
 
 
 

 
 Just for anyone watching/finding this. Worked with Jesse and could not get '*/Jenkinsfile' to work, but did get '//DEPOT_NAME/*/Jenkinsfile' working. Windows Jenkins master connected to Linux P4d. Note - Reason for using this - attempting to implement polling exclusions so (for example) artifact submits do not trigger the job.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-45962) GIT_BRANCH variable is not populated in jenkins pipeline

2019-12-05 Thread allan.le...@youview.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45962  
 
 
  GIT_BRANCH variable is not populated in jenkins pipeline   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 With Jenkins file below, it shows error that {{GIT_BRANCH}} is not recognized{noformat}stages  \ {   stage('checkout')  \ {       steps  \ {            git credentialsId: 'jenkins',                 url: 'g...@git.xxx.com:jianjing/jenkinspipeline.git',                branch: "test"         }    }    stage('test')  \ {        steps  \ {            sh "echo $\{GIT_BRANCH}"        }    }{noformat}{noformat} groovy.lang.MissingPropertyException: No such property: GIT_BRANCH for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:232) at org.kohsuke.groovy.sandbox.impl.Checker$5.call(Checker.java:255) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:259) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:19) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:172) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:438) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:188) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:186) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:437) at

[JIRA] (JENKINS-45962) GIT_BRANCH variable is not populated in jenkins pipeline

2019-12-05 Thread allan.le...@youview.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45962  
 
 
  GIT_BRANCH variable is not populated in jenkins pipeline   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 With Jenkins file below, it shows error that  {{  GIT_BRANCH }}  is not recognized {noformat} stages \{   stage('checkout') \{       steps \{            git credentialsId: 'jenkins',                 url: 'g...@git.xxx.com:jianjing/jenkinspipeline.git',                branch: "test"         }    }    stage('test') \{        steps \{            sh "echo $\{GIT_BRANCH}"        }    } {noformat}  {noformat}  groovy.lang.MissingPropertyException: No such property: GIT_BRANCH for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:232) at org.kohsuke.groovy.sandbox.impl.Checker$5.call(Checker.java:255) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:259) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:19) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:172) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:438) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:188) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:186) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:437) at

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

2019-12-05 Thread w...@akimbo.be (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wim Coenen commented on  JENKINS-58604  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Full Stage View only showing one   
 

  
 
 
 
 

 
 I have this problem only while parallel stages are executing. When the pipeline advances to the next stage without parallelism, I suddenly see past builds again. When the pipeline then advances to a stage containing parallel stages, the past builds disappear again, etc.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60381) Remove old, deprecated remoting protocols

2019-12-05 Thread jthomp...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60381  
 
 
  Remove old, deprecated remoting protocols   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Jeff Thompson  
 
 
Components: 
 core, remoting  
 
 
Created: 
 2019-12-05 16:48  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jeff Thompson  
 

  
 
 
 
 

 
 For historical reasons, Jenkins still ships with old, deprecated protocols, JNLP1-connect, JNLP2-connect, and JNLP3-connect. These all have fundamental issues and known bugs. They were all superseded by the JNLP4-connect protocol released in Jenkins 2.27 over three years ago (October 2016). They have all been deprecated and unsupported since Jenkins 2.75 over two years ago. Since then there have been UI messages and an administrative monitor strongly discouraging their use. (See more information about the protocols at https://github.com/jenkinsci/remoting/blob/master/docs/protocols.md ) These protocols should be removed as part of cleaning up technical debt. See the discussion at https://groups.google.com/forum/#!topic/jenkinsci-users/s90MVVdFDyU  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted

2019-12-05 Thread cbopardi...@perforce.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charusheela Bopardikar assigned an issue to Charusheela Bopardikar  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60144  
 
 
  Cant delete Jenkins job if the perforce template client has been deleted   
 

  
 
 
 
 

 
Change By: 
 Charusheela Bopardikar  
 
 
Assignee: 
 Charusheela Bopardikar  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth commented on  JENKINS-51552  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot replay pipelines - files are read-only   
 

  
 
 
 
 

 
 Hi Erez Arbell - I confirm that the problem is still seen in p4-plugin 1.10.7. However setting allwrite:true still solves it for me. I raised this to the developers and they suggested that the underlying problem could be that the old 'legacySCM' is being used. Can you please check if you are using 'modernSCM' and if not, try it to see if it solves the problem.:  https://jenkins.io/doc/pipeline/steps/workflow-cps-global-lib  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-39287) Ability to select from existing credentials list at runtime

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-39287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to select from existing credentials list at runtime   
 

  
 
 
 
 

 
 There is no benefit for implicit checkout; however if you set `options { skipDefaultCheckout() }` then for subsequent checkout steps you could change the credential.  You would need your own logic to look up the credential or specify them with the agent/label.     
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55214) NullPointerException when starting a pipeline in a multibranch project

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing.  Plugin cannot read invalid pipeline script.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55214  
 
 
  NullPointerException when starting a pipeline in a multibranch project   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 Open Closed  
 
 
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

[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55985  
 
 
  Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Priority: 
 Blocker Minor  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55985  
 
 
  Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-56248  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false)   
 

  
 
 
 
 

 
 TODO: retest this issue after updating plugin dependencies.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56248  
 
 
  P4Plugin Polls Workspaces With Disabled Polling (poll: false)   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Priority: 
 Blocker Major  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-56286) Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56286  
 
 
  Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Priority: 
 Blocker Major  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58958) Use the same Jenkins workspace on a Change basis

2019-12-05 Thread andr...@unjo.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Fritiofson commented on  JENKINS-58958  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use the same Jenkins workspace on a Change basis   
 

  
 
 
 
 

 
 How Gerrit internally stores and references Patchsets should be orthogonal to how we want to handle them in Jenkins/BlueOcean.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-56290) Impossible to Add Streams with Exact Names to Multibranch Pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56290  
 
 
  Impossible to Add Streams with Exact Names to Multibranch Pipeline   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Priority: 
 Blocker Major  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60221) Copy artifact on agent sometimes hangs while copying

2019-12-05 Thread stefan.dris...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Drissen commented on  JENKINS-60221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Copy artifact on agent sometimes hangs while copying   
 

  
 
 
 
 

 
 Right - back again - during copying build artifacts an agent went offline, upon being brought online again, the job is still hanging on the copy build artifact job. The threadDump from the master - for this build / agent - is: Executor #0 for nlc1dprm020 : executing 7.28/work/report_12.1-sql2017 #68 "Executor #0 for nlc1dprm020 : executing 7.28/work/report_12.1-sql2017 #68" Id=79412 Group=main TIMED_WAITING on hudson.remoting.PipeWindow$Real@75b811f2 at java.lang.Object.wait(Native Method) - waiting on hudson.remoting.PipeWindow$Real@75b811f2 at hudson.remoting.PipeWindow$Real.get(PipeWindow.java:225) at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:124) - locked hudson.remoting.ProxyOutputStream@4cfc2a8b at hudson.remoting.RemoteOutputStream.write(RemoteOutputStream.java:108) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2315) at org.apache.commons.io.IOUtils.copy(IOUtils.java:2270) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2291) at org.apache.commons.io.IOUtils.copy(IOUtils.java:2246) at hudson.FilePath.copyFrom(FilePath.java:984) at hudson.plugins.copyartifact.CopyArtifact.copyOne(CopyArtifact.java:617) at hudson.plugins.copyartifact.CopyArtifact.copy(CopyArtifact.java:577) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:537) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:475) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1853) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427)   I have saved the rest of the (rather large) threadDump - so can provide more if required.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-49897) gerrit-plugin pr branch names are incorrectly name

2019-12-05 Thread andr...@unjo.com (JIRA)

Title: Message Title

Andreas Fritiofson commented on JENKINS-49897

Re: gerrit-plugin pr branch names are incorrectly name

I would also vote for having only the Change number field as the PR name. Having the Patchset number as part of the branch/PR makes Jenkins forget the history of the change. All PRs only get one build because Patchsets are seen as different PRs, so the statistics provided by plugins such as Warnings are meaningless. I don't really buy the motivation for the Patchset number quoted above; that it's needed to retrigger a build of a Patchset. If a newer Patchset is uploaded, it obsoletes all previous Patchsets of that Change. They cannot be submitted, so what is the point of building them at all? In fact in a comment to JENKINS-60301, it's even discussed to abort ongoing builds of older Patchsets when a new one is uploaded. Besides, since the job for the current Patchset is removed when a new is uploaded, you can't even retrigger a build.

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

[JIRA] (JENKINS-58119) Cant run P4Groovy sync on multiple executors

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58119  
 
 
  Cant run P4Groovy sync on multiple executors   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Priority: 
 Blocker Major  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58196) UTF8 BOM override issue in 1.10.0

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen assigned an issue to Karl Wirth  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58196  
 
 
  UTF8 BOM override issue in 1.10.0   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Assignee: 
 Karl Wirth  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58949  
 
 
  If job fails in cleanup further triggering fails   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Priority: 
 Blocker Minor  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58878) withCredentials hangs

2019-12-05 Thread r.fuere...@xortex.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder commented on  JENKINS-58878  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: withCredentials hangs   
 

  
 
 
 
 

 
 Thanks, this is very promising/good news!  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60380) Job without label builds on slaves with labels

2019-12-05 Thread gertjanko...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gert Jan Koorn created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60380  
 
 
  Job without label builds on slaves with labels   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-12-05 14:38  
 
 
Environment: 
 2.150.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Gert Jan Koorn  
 

  
 
 
 
 

 
 Jenkins Jobs without a label also builds on slaves that do have labels and have the setting 'Only build jobs with label expressions matching this node'. Since there are slaves available with the setting 'Use this node as much as possible', it is strange the slaves with explicit restrictions are used. Is it possible to fix this?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-58878) withCredentials hangs

2019-12-05 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-58878  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: withCredentials hangs   
 

  
 
 
 
 

 
 Reinhold Füreder Yes, if you were running Docker Pipeline 1.19 or newer, in which case those steps use GeneralizedNonBlockingStepExecution (see docker-workflow PR 158), then they could have been affected by the bug and should be fixed now.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60363) Include TLSv1.2 instruction in P4-Plugin Doc

2019-12-05 Thread kwilliam...@perforce.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Williamson updated  JENKINS-60363  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60363  
 
 
  Include TLSv1.2 instruction in P4-Plugin Doc   
 

  
 
 
 
 

 
Change By: 
 Kevin Williamson  
 
 
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.203386.1575459106000.1569.157480383%40Atlassian.JIRA.

[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth edited a comment on  JENKINS-51552  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot replay pipelines - files are read-only   
 

  
 
 
 
 

 
 Hi [~erez_arbell] - Thanks for all your help. I have been able to reproduce the problem with the following setup: (1) Submit //depot/lib_autoload/libs/src/com/f/v/Utils.groovy {code:java}#!groovypackage com.f.vclass Utils implements Serializable { static void main() { println("This is in Utils Library") }static void test() { println("This is test in Utils in the Library") }}{code}  (2) Define a pipeline job with groovy code in GUI editor:{code:java}// Define globalsdef  fLibts  fLibts {try {node ('master') {Lib = loadFLib()def buildData = Lib.com.f.v.Utils.test();}}catch (e) {throw e}echo "Running some tests here..."}// Load a specific Librarydef loadFLib() {def p4ClientFormat = "jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-flib"return loadLibrary(identifier: 'f@1',clientFormat: p4ClientFormat,p4Mapping: "//depot/lib_autoload/libs/src/com/f/v/... //${p4ClientFormat}/src/com/f/v/...\n")}// Generic Library Loaderdef loadLibrary(args) {def lib = library(identifier: args.identifier,retriever: legacySCM([$class: 'PerforceScm',credential: 'JenkinsMaster',populate: [$class: 'AutoCleanImpl',delete: true,modtime: false,pin: '',quiet: false,replace: true],workspace: manualSpec(charset: 'none',name: args.clientFormat,pinHost: false,spec: clientSpec(allwrite: false, backup: false, clobber: true, compress: false, line: 'LOCAL',locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE',view: args.p4Mapping))]))return lib}{code}   (3) Run the job.(4) When you use the 'Replay' option for the same job you see:{code:java}11:21:41 P4: saving built changes.11:21:41 ... p4 client -o jenkins-master-JENKINS-57314-ExplicitLocalLib-Replay-2-flib +11:21:41 ... p4 info +11:21:41 ... p4 info +11:21:41 ... p4 client -o jenkins-master-JENKINS-57314-ExplicitLocalLib-Replay-2-flib +11:21:41 ... done11:21:41 11:21:41 Replacing contents of src/com/f/v/Utils.groovy[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // timestamps[Pipeline] End of Pipelinejava.nio.file.AccessDeniedException: /var/lib/jenkins/jobs/JENKINS-57314-ExplicitLocalLib-Replay/builds/25/libs/f/src/com/f/v/Utils.groovy at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434) at java.nio.file.Files.newOutputStream(Files.java:216) at hudson.FilePath$Write.invoke(FilePath.java:2100) at hudson.FilePath$Write.invoke(FilePath.java:2089) at hudson.FilePath.act(FilePath.java:1076) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.write(FilePath.java:2087) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:168) at org.jenkinsci.plugins.workflow.libs.LibraryStep$Execution.run(LibraryStep.java:207) at org.jenkinsci.plugins.workflow.libs.LibraryStep$Execution.run(LibraryStep.java:156) at

[JIRA] (JENKINS-60349) User credentials not usable by Git plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60349  
 
 
  User credentials not usable by Git plugin   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Attachment: 
 personal-access-token-on-my-userid.png  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60349) User credentials not usable by Git plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-60349  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User credentials not usable by Git plugin   
 

  
 
 
 
 

 
 Can you provide guidance on how to confirm that the credential can be used after I attached it to my Jenkins user account from my user name drop down like this:  That dropdown allowed me to add a new GitHub personal access token to my Jenkins server, but then I am unable to see it in other contexts. 
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60373) Permit to inject file credential from master filesystem

2019-12-05 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-60373  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permit to inject file credential from master filesystem   
 

  
 
 
 
 

 
 

it "creates" the credentials at the time they are being used in the pipeline code. Any way to use it for system config or from non-pipeline jobs?
 Has nothing to do with Pipeline that I know of. When the credentials APIs to look up credentials are called, it loads them from a cache which is updated by a K8s watch. 

there does not seem to be a way to get JCasC to do the encoding of individual variable value
 Perhaps the simplest solution would be to just patch configuration-as-code to allow some special syntax for reading named files (optionally as Base64) in place of a literal string value. Lots of configuration systems have something like this, for example treating values starting with @ as a file load. E.g. amending plain-credentials-plugin/src/test/resources/org/jenkinsci/plugins/plaincredentials/ConfigurationAsCode.yaml: 

 

credentials:
  system:
domainCredentials:
- credentials:
  - file:
  id: secret-file
  scope: SYSTEM
  description: "Some secret file"
  fileName: my-secret-file
  secretBytes: "$base64file(/run/secrets/whatever)"
 

 IIUC JCasC is only available to administrators, so it is safe to allow file reads.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-48452) GitHub Org Folders Discard Old Items settings do not seem to have any effect

2019-12-05 Thread rsand...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 rsandell updated  JENKINS-48452  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48452  
 
 
  GitHub Org Folders Discard Old Items settings do not seem to have any effect   
 

  
 
 
 
 

 
Change By: 
 rsandell  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 6.9  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60349) User credentials not usable by Git plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60349  
 
 
  User credentials not usable by Git plugin   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Attachment: 
 mark-waite-credentials-dropdown.png  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60373) Permit to inject file credential from master filesystem

2019-12-05 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-60373  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permit to inject file credential from master filesystem   
 

  
 
 
 
 

 
 

Btw, would not simply requesting Administer permission in the @DataBoundSetter for the secretPath field get us secure with minimal implementation changes and minimal user-visible / automation irregularities?
 CLI commands create-credentials-by-xml and import-credentials-as-xml bypass all of that. As does POST config.xml to folder stores. Again, please read the old conversations around past issues.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-6334  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for displaying changesets in submodule updates   
 

  
 
 
 
 

 
 The recent submodule additions were done with specific attention to test automation. I'm still deeply attached to test automation to allow the plugin to be safely released to the 250 000 installations of Jenkins. For me, a pull request to allow inclusion of submodule changes in the changeset would need to: 
 
Include tests that confirm the current behavior of not including submodule changes in the changeset (or confirm that there are already tests which verify that) 
Include tests that confirm the default behavior is to not include submodule changes in the changeset 
Include tests that enable inclusion of submodule changes in the changeset, including tests for: 
 
Repository with no submodules 
Repository with 1 submodule 
Repository with more than 1 submodule 
Repository with 1 submodule which includes another submodule (recursive) 
  
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-60373) Permit to inject file credential from master filesystem

2019-12-05 Thread ogon...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža commented on  JENKINS-60373  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permit to inject file credential from master filesystem   
 

  
 
 
 
 

 
 Btw, would not simply requesting Administer permission in the @DataBoundSetter for the secretPath field get us secure with minimal implementation changes and minimal user-visible / automation irregularities?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60373) Permit to inject file credential from master filesystem

2019-12-05 Thread ogon...@gmail.com (JIRA)

Title: Message Title

Oliver Gondža commented on JENKINS-60373

Re: Permit to inject file credential from master filesystem

Thanks for suggesting kubernetes-credentials-provider. The way I understand it, it "creates" the credentials at the time they are being used in the pipeline code. Any way to use it for system config or from non-pipeline jobs?

Using an init container?
It is not the problem to intercept container creation, but adding another layer of processing between container creation and JCasC execution. As there does not seem to be a way to get JCasC to do the encoding of individual variable value, it either have do be baked in to container build (so the automation that creates container needs to be aware which secrets happens to be later used as file type secrets which wires things I am glad that are separate) or done somehow inbetween. I like the idea of using CredentialsProvider to implement JCasC only credentials (that would be safe to read from filesystem, I presume), though that would impose changes to JCasC format (I understood it will not be in system store anymore). Meaning, all credentials are ok to be in system section, but the one that refers to master FS needs to be in different section. Thank you both for your inputs. I will dig deeper to see, which of these is reasonable feasible.

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

[JIRA] (JENKINS-55987) Use of when buildingTag does not work in Declarative pipeline

2019-12-05 Thread dominique.tron...@atos.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tronche Dominique commented on  JENKINS-55987  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use of when buildingTag does not work in Declarative pipeline   
 

  
 
 
 
 

 
 OK now I understand why it does not work but do we agree that this limitation is clearly not documented ? I remembered I tried to do it myself but I had quite some trouble implementing it and it was very frustrating when there is supposed to be a function that do it for you. Personally I don't really understand why this function, which is probably needed by a lot of people, is restricted to multibranch. Especially since multibranch does not allow project dependency which is a bit one of the main reason Jenkins is used for... Thanks for your help anyway  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404

2019-12-05 Thread vkuk...@joom.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vladimir Kuklin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60353  
 
 
  Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404   
 

  
 
 
 
 

 
Change By: 
 Vladimir Kuklin  
 

  
 
 
 
 

 
 How to reproduce:Use multibranch-pipeline workflow with merge PR strategy # Create a branch, develop it and make it nonmergable into the target branch # Push the branch and open the Pull Request in GH # Find out that the branch is not-mergeable # Fix the code, push the newer revisionExpected Result:The pipeline is triggered.Actual Result: # On step #2 Jenkins gets the 404 in the request to ...refs/pull//merge/contents # The 404 is cached # On the step 4 it does not query GH but rather returns a cryptic error of 'Jenkins File not found' although it does not check for it at allProposed solution: do not check for the contents of the "refs.//merge" URL if the PR is not mergable.  Versions:Jenkins 2.190.1GitHub Branch Source Plugin 2.5.8+ (some irrelevant local patches) Here is how we figured out what was happening: # Get the repro of the bug # Jump to the jenkins master node and create a copy of github cache dir, namely "${JENKINS_HOME}/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache" # grep for the pull request id in the *.0 files to figure out the  request id (prefix before the '.0') of the exchange with Github  # zcat the file of the exchange (.1) and see that Jenkins checks the refs/pull//merge/contents and gets 404 # Jenkins never consults anything after getting this response until the cache entry with 404 is purged, but writes a cryptic message like 'Jenkinsfile not found' and (possibly) the lines saying that the PR branch is dead, thus being removed from the list of branches to run the build against,While surfing looking for the similar bugs, I noticed several that might be related to those ones, especially the first one.https://issues.jenkins-ci.org/browse/JENKINS-48571https://issues.jenkins-ci.org/browse/JENKINS-46290https://issues.jenkins-ci.org/browse/JENKINS-54126https://issues.jenkins-ci.org/browse/JENKINS-57206https://issues.jenkins-ci.org/browse/JENKINS-57411    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-60373) Permit to inject file credential from master filesystem

2019-12-05 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-60373  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permit to inject file credential from master filesystem   
 

  
 
 
 
 

 
 This indeed sounds rather dangerous and I would not advise it. 

require to intercept container creation
 Using an init container? You can also use the kubernetes-credentials-provider plugin, though that has a different access control model: Jenkins requires a role binding to get secrets by name, rather than having specific secrets be injected. If you feel the need for an enhancement of this type, rather than patching Credentials implementations, it would be more appropriate to supply a CredentialsProvider which is able to load secrets from well-known locations in the container’s filesystem, or from locations configurable only by “administrators” (thus JCasC but not project developers).  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55987) Use of when buildingTag does not work in Declarative pipeline

2019-12-05 Thread rasp...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Krzysztof Malinowski commented on  JENKINS-55987  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use of when buildingTag does not work in Declarative pipeline   
 

  
 
 
 
 

 
 Technically this condition checks for existence of environment variable called TAG_NAME. This is normally contributed by Branch API, for multibranch approach. If you don't use multibranching, you can try to populate TAG_NAME yourself before the condition, or just rework the condition.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60379) Sometimes Git line enricher is failing if checkout was done on slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60379  
 
 
  Sometimes Git line enricher is failing if checkout was done on slave   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Labels: 
 6.0.1-BETA Octane  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60379) Sometimes Git line enricher is failing if checkout was done on slave

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60379  
 
 
  Sometimes Git line enricher is failing if checkout was done on slave   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Radi Berkovich  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-12-05 12:50  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Radi Berkovich  
 

  
 
 
 
 

 
 28112019 094916,540 ERROR Executor #2 for UFT_VM_02_6Y  executing StableEdpay_Instructions_API_Cancel_Tests #490 GitSCMProcessor                  Line enricher FAILED. could not enrich lines on SCM Data  java.lang.NullPointerException null     at com.microfocus.application.automation.tools.octane.model.processors.scm.GitSCMProcessor.getBlameData(GitSCMProcessor.java427) ~[hp-application-automation-tools-plugin.jar5.9]     at com.microfocus.application.automation.tools.octane.model.processors.scm.GitSCMProcessor.access$300(GitSCMProcessor.java71) ~[hp-application-automation-tools-plugin.jar5.9]     at com.microfocus.application.automation.tools.octane.model.processors.scm.GitSCMProcessor$LineEnricherCallable.invoke(GitSCMProcessor.java361) ~[hp-application-automation-tools-plugin.jar5.9]     at com.microfocus.application.automation.tools.octane.model.processors.scm.GitSCMProcessor$LineEnricherCallable.invoke(GitSCMProcessor.java336) ~[hp-application-automation-tools-plugin.jar5.9]     at hudson.FilePath$FileCallableWrapper.call(FilePath.java3042) ~[jenkins-core-2.164.2.jar]     at hudson.remoting.UserRequest.perform(UserRequest.java212) ~[remoting-3.29.jar]     at hudson.remoting.UserRequest.perform(UserRequest.java54) ~[remoting-3.29.jar]     at hudson.remoting.Request$2.run(Request.java369) ~[remoting-3.29.jar]     at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java72) ~[remoting-3.29.jar]     at java.util.concurrent.FutureTask.run(Unknown Source) ~[1.8.0_222]     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[1.8.0_222]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[1.8.0_222]

[JIRA] (JENKINS-60378) Simplify user impersonation

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich assigned an issue to Radi Berkovich  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60378  
 
 
  Simplify user impersonation   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Assignee: 
 Maria Narcisa Galan Radi Berkovich  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60378) Simplify user impersonation

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60378  
 
 
  Simplify user impersonation   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Maria Narcisa Galan  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-12-05 12:47  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Radi Berkovich  
 

  
 
 
 
 

 
 User impersonation is failing as customer is using custom UserDetailsService that does not have implementation of loadUserByUsername.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-60378) Simplify user impersonation

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60378  
 
 
  Simplify user impersonation   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Labels: 
 6.0.1-BETA Octane  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60374) Support Code Coverage injection to ALM Octane via pipeline as a code

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60374  
 
 
  Support Code Coverage injection to ALM Octane via pipeline as a code   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Labels: 
 6.0.1-BETA Octane  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60377) Support cucumber test-runnner converter for ALM Octane testing framework

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60377  
 
 
  Support cucumber test-runnner converter for ALM Octane testing framework   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Labels: 
 6.0.1-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.203424.1575549869000.1438.1575549960899%40Atlassian.JIRA.

[JIRA] (JENKINS-60376) Support vulnerabilities injection to ALM Octane via Pipeline as code (Fortify SSC)

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60376  
 
 
  Support vulnerabilities injection to ALM Octane via Pipeline as code (Fortify SSC)   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Labels: 
 6.0.1-BETA Octane  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60377) Support cucumber test-runnner converter for ALM Octane testing framework

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60377  
 
 
  Support cucumber test-runnner converter for ALM Octane testing framework   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Labels: 
 6.0.1-BETA  Octane  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60377) Support cucumber test-runnner converter for ALM Octane testing framework

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60377  
 
 
  Support cucumber test-runnner converter for ALM Octane testing framework   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Radi Berkovich  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-12-05 12:44  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Radi Berkovich  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this

[JIRA] (JENKINS-60336) Add support for logging to Elastic Search

2019-12-05 Thread alexander.russ...@sap.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Russell assigned an issue to Alex Russell  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60336  
 
 
  Add support for logging to Elastic Search   
 

  
 
 
 
 

 
Change By: 
 Alex Russell  
 
 
Assignee: 
 Alex Russell  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60376) Support vulnerabilities injection to ALM Octane via Pipeline as code (Fortify SSC)

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60376  
 
 
  Support vulnerabilities injection to ALM Octane via Pipeline as code (Fortify SSC)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Radi Berkovich  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-12-05 12:42  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Radi Berkovich  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You

[JIRA] (JENKINS-60375) Unable trigger build , getting an error

2019-12-05 Thread sm3...@att.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Samidha More created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60375  
 
 
  Unable trigger build , getting an error   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Victor Martinez  
 
 
Components: 
 jenkinslint-plugin  
 
 
Created: 
 2019-12-05 12:42  
 
 
Environment: 
 http://zlt07784.vci.att.com:8080/  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Samidha More  
 

  
 
 
 
 

 
 please check logs - http://zlt07784.vci.att.com:8080/job/olamstatusdev/build?delay=0sec   A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang.NullPointerException at smartjenkins.SmartJenkinsQueueDecisionHandler.shouldSchedule(SmartJenkinsQueueDecisionHandler.java:24) at hudson.model.Queue.schedule2(Queue.java:589) at hudson.model.Queue.schedule2(Queue.java:712) at hudson.model.Queue.schedule(Queue.java:705) at hudson.model.ParametersDefinitionProperty._doBuild(ParametersDefinitionProperty.java:161) at jenkins.model.ParameterizedJobMixIn.doBuild(ParameterizedJobMixIn.java:212) at jenkins.model.ParameterizedJobMixIn$ParameterizedJob.doBuild(ParameterizedJobMixIn.java:408) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at

[JIRA] (JENKINS-60374) Support Code Coverage injection to ALM Octane via pipeline as a code

2019-12-05 Thread radislav.berkov...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60374  
 
 
  Support Code Coverage injection to ALM Octane via pipeline as a code   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Radi Berkovich  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-12-05 12:41  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Radi Berkovich  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this

[JIRA] (JENKINS-55987) Use of when buildingTag does not work in Declarative pipeline

2019-12-05 Thread dominique.tron...@atos.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tronche Dominique edited a comment on  JENKINS-55987  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use of when buildingTag does not work in Declarative pipeline   
 

  
 
 
 
 

 
 Thanks for the update. This bug is really blocking for our team since I cannot use Declarative pipeline in our project due to itI have attached a log file with the detail  start  scm part  of the jenkins log file. The Checking out Revision indicates we are on a tag, yet the stage is skippedI am not using a multibranch pipeline but a simple pipeline project. I did not see any limitation on the documentation on this subject. We are not planning to use multibranch pipelines since this item does not offer the "Build after other projects are built" option and we need it  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55987) Use of when buildingTag does not work in Declarative pipeline

2019-12-05 Thread dominique.tron...@atos.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tronche Dominique commented on  JENKINS-55987  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use of when buildingTag does not work in Declarative pipeline   
 

  
 
 
 
 

 
 Thanks for the update. This bug is really blocking for our team since I cannot use Declarative pipeline in our project due to it I have attached a log file with the detail start of the jenkins log file. The Checking out Revision indicates we are on a tag, yet the stage is skipped I am not using a multibranch pipeline but a simple pipeline project. I did not see any limitation on the documentation on this subject. We are not planning to use multibranch pipelines since this item does not offer the "Build after other projects are built" option and we need it  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55987) Use of when buildingTag does not work in Declarative pipeline

2019-12-05 Thread dominique.tron...@atos.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tronche Dominique updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55987  
 
 
  Use of when buildingTag does not work in Declarative pipeline   
 

  
 
 
 
 

 
Change By: 
 Tronche Dominique  
 
 
Attachment: 
 jenkins-console-output-scm.log  
 

  
 
 
 
 

 
 
 

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

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

2019-12-05 Thread pete.n...@sepura.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 pete neal commented on  JENKINS-57918  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 I have repo plugin 1.11.1 on Jenkins 2.201 and can confirm it has fixed the issue for me.  (previously I was using a private build of Simon Williams fix)  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-60371) Azure App Service plugin deploy via docker error

2019-12-05 Thread jie...@microsoft.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jie Shen commented on  JENKINS-60371  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Azure App Service plugin deploy via docker error   
 

  
 
 
 
 

 
 Thanks for reporting 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.201594.1567194345000.1402.1575546120132%40Atlassian.JIRA.

[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only