[JIRA] (JENKINS-50856) Cannot connect to bitbucket server from Blueocean.

2018-04-18 Thread manaswinee.moha...@unilever.com (JIRA)
<<< text/html; charset="UTF-8": Unrecognized >>>


[JIRA] (JENKINS-50842) command-launcher terminates the process

2018-04-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-50842  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: command-launcher terminates the process
 

  
 
 
 
 

 
 For me it looks like a feature request, not as a defect. It could be preferable to use Cloud API for such operations. There is https://wiki.jenkins.io/display/JENKINS/Scripted+Cloud+plugin, but I am not sure it supports such use-case (and the plugin is outdated for sure)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50857) Docker agent on windows with Cannot run program "id"

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50857  
 
 
  Docker agent on windows with Cannot run program "id"   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-04-18 07:42  
 
 
Labels: 
 pipeline declarative docker  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jonathan Kuleff  
 

  
 
 
 
 

 
 I'm trying to use a docker agent on windows in declarative pipeline. I can see the image is pulled but then fails as below 

 

[ply-widgets-project-pipelin-GORWBIPVPM5EWBJECA7BVJBSR5OVNCYISONJIELJYMXAG4YTMWPQ] Running shell script
sh: sleep: command not found
sh: sleep: command not found
sh: sleep: command not found
sh: sleep: command not found
sh: sleep: command not found
+ docker inspect -f . 1234567.dkr.ecr.us-west-2.amazonaws.com/builds/jenkins-agent-node:windows-npm-5.8.0
.
Cannot run program "id": CreateProcess error=2, The system cannot find the file specified
 

   I'm using the following in my jenkinsfile for a stage 

 

agent {
docker { 
image '1234567.dkr.ecr.us-west-2.amazonaws.com/builds/jenkins-agent-node:windows-npm-5.8.0' 
label 'windows&&docker' 
}
}
 

 While I don't think it matters in this case my registry is actually AWS ECR and the agent is a windows s

[JIRA] (JENKINS-50773) Pipline script for vSphere ExposeGuestInfo generates . Pipeline DSL ExposeGuestInfo Build fails

2018-04-18 Thread vmarjun...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits assigned an issue to Jason Swager  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50773  
 
 
  Pipline script for vSphere ExposeGuestInfo generates . Pipeline DSL ExposeGuestInfo Build fails
 

  
 
 
 
 

 
Change By: 
 vassil marjunits  
 
 
Assignee: 
 Jason Swager  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50773) Pipline script for vSphere ExposeGuestInfo generates . Pipeline DSL ExposeGuestInfo Build fails

2018-04-18 Thread vmarjun...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits commented on  JENKINS-50773  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipline script for vSphere ExposeGuestInfo generates . Pipeline DSL ExposeGuestInfo Build fails
 

  
 
 
 
 

 
 Jason Swager and Eric Lordahl is there any recomendetion or workaround according to this https://issues.jenkins-ci.org/browse/JENKINS-50773?focusedCommentId=335473&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-335473?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50477) Subversion Plugin 2.10.5 Login to SVN Server broken.

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50477  
 
 
  Subversion Plugin 2.10.5 Login to SVN Server broken.   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Reopened Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50477) Subversion Plugin 2.10.5 Login to SVN Server broken.

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50477  
 
 
  Subversion Plugin 2.10.5 Login to SVN Server broken.   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50857) Docker agent on windows fails with Cannot run program "id"

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50857  
 
 
  Docker agent on windows fails with Cannot run program "id"   
 

  
 
 
 
 

 
Change By: 
 Jonathan Kuleff  
 
 
Summary: 
 Docker agent on windows  fails  with Cannot run program "id"  
 
 
Environment: 
 Windows 2016, Jenkins 2.89.4  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-50638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
 if it does not generate any files on D:\CI\jenkins-ssh try to execute the slave.jar process manually to see if we see something else, follow these steps 
 
enter on the Agent by SSH with the same user you use in Jenkins 
execure "D:\CI\jenkins-ssh" && java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt" 
Copy the output and paste it here 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-50327  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest   
 

  
 
 
 
 

 
 I tested it on Jenkins core 2.7.3 and 2.89.4 with Subversion plugin 2.10.5 and the bundled version of other plugins, I was not able to replicate it, I will upgrade all plugins to the latest version to see if I could replicate it. 

 

node(){
checkout changelog: true, poll: true, scm:
[
$class: 'SubversionSCM',
additionalCredentials: [],
excludedCommitMessages: '',
excludedRegions: '',
excludedRevprop: '',
excludedUsers: '',
filterChangelog: false,
ignoreDirPropChanges: false,
includedRegions: '',
locations: [[credentialsId: "SVN_CREDENTIALS",
 depthOption: 'empty',
 ignoreExternalsOption: true,
 local: '.',
 remote: "http://127.0.0.1/svn/new-repo/"]],
quietOperation: true,
workspaceUpdater: [$class: 'UpdateUpdater']
]
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jen

[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally

2018-04-18 Thread slawo...@ezono.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Slawomir Czarko commented on  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
 The way I have been using as-it-is so far is by doing a full checkout first then running my own script which was pruning the working copy using svn up --set-depth. Starting with 'files' as depth is not good enough for that case since the script I use for pruning the working copy is in a subdirectory. What is the reason for this change in behaviour of as-it-is?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
 see JENKINS-50287  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0

2018-04-18 Thread he...@geekware.co.za (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henti Smith commented on  JENKINS-50850  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0   
 

  
 
 
 
 

 
 Morning Chenyang Liu  I'm terribly sorry, I seem to copy and pasted the wrong set of logs. Tho the logs above does indeed show up, and you're right it's a quota limit.    Please see the below logs for the relevant information.  

 

Apr 17, 2018 12:54:02 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeployment
INFO: AzureVMManagementServiceDelegate: createDeployment: Creating a new deployment jenkins-linux-8-core-build-slave0417125402381 with VM base name jenkins-linux-8-core-build-slaveb939d
Apr 17, 2018 12:55:10 PM com.microsoft.azure.vmagent.AzureVMCloud$4 call
SEVERE: Failure creating provisioned agent 'jenkins-linux-8-core-build-slaveb939d7'
com.microsoft.azure.vmagent.exceptions.AzureCloudException: AzureVMCloud: createProvisionedAgent: Deployment Failed: Microsoft.Compute/virtualMachines:jenkins-linux-8-core-build-slaveb939d7 - Conflict - {status=Failed, error={code=ResourceDeploymentFailure, message=The resource operation completed with terminal provisioning state 'Failed'., details=[{code=AllocationFailed, message=Allocation failed. Please try reducing the VM size or number of VMs, retry later, or try deploying to a different Availability Set or different Azure location.}]}}
at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:37)
at com.microsoft.azure.vmagent.AzureVMCloud.createProvisionedAgent(AzureVMCloud.java:612)
at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:854)
at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:832)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Apr 17, 2018 12:55:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate terminateVirtualMachine
INFO: AzureVMManagementServiceDelegate: terminateVirtualMachine: Removing virtual machine jenkins-linux-8-core-build-slaveb939d7
 

 We had 862 such failures in a space of 50 minutes while the plugin was active and trying to diagnose the problem. The original logs is likely as a result of this mass failures, so please consider it as such.    I "disabled" the plugin by changing the label to a non existant one so VMs stopped being created as the race condition was in play. We had jobs that would trigger azure resources, but since the provisioning failed, was never met, which in turn kept triggering provisioning.    Again I'm sorry for the mistake regarding the logs.   
 

  
 
 
 
 

 
 
 
 

[JIRA] (JENKINS-50507) withMaven must not trigger its own project

2018-04-18 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50507  
 
 
  withMaven must not trigger its own project   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 
 
Attachment: 
 JENKINS-50507.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50507) withMaven must not trigger its own project

2018-04-18 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc commented on  JENKINS-50507  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: withMaven must not trigger its own project   
 

  
 
 
 
 

 
 Visualisation glitch reproduced with https://github.com/cyrille-leclerc/JENKINS-50507.git BUT the I don't get the trigger problem. The visualization glitch being that the pipeline JENKINS-50507/master is displayed as an upstream pipeline of JENKINS-50507/master and as a downstream job as well when it should NOT because we don't trigger "myself".> Is it safe for me to wipe out the H2 database at /var/jenkins_home/jenkins-jobs/jenkins-jobs, and restart Jenkins to see if this helps? It is safe but I don't think it will change anything.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value

2018-04-18 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50525  
 
 
  Error When Provisioning Slave: mountPath: Required value   
 

  
 
 
 
 

 
Change By: 
 Carlos Sanchez  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value

2018-04-18 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50525  
 
 
  Error When Provisioning Slave: mountPath: Required value   
 

  
 
 
 
 

 
Change By: 
 Carlos Sanchez  
 
 
Assignee: 
 Carlos Sanchez  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50801) Cannot provision Slave Pod: mountPath: Required value

2018-04-18 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50801  
 
 
  Cannot provision Slave Pod: mountPath: Required value   
 

  
 
 
 
 

 
Change By: 
 Carlos Sanchez  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50858) CannotResolveClassException if jobfilters with regex is used

2018-04-18 Thread juergen_thom...@linfre.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jürgen Thomann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50858  
 
 
  CannotResolveClassException if jobfilters with regex is used   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2018-04-18 08:51  
 
 
Environment: 
 Jenkins ver. 2.117  Job DSL 1.69  View Job Filters 1.27  java version "1.8.0_121"  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jürgen Thomann  
 

  
 
 
 
 

 
 I try to use the following DSL to create a view with a jobfilter 

 

listView('Test') {
    columns {
    status()
    weather()
    name()
    cronTrigger()
    lastSuccess()
    lastFailure()
    lastDuration()
    buildButton()
    }
  jobFilters {
    regex {
    matchType(MatchType.INCLUDE_MATCHED)
    matchValue(RegexMatchValue.EMAIL)
    regex('.*loremipsum.*')
    }
    }
} 

 The Job runs without any problems, but I get an old data warning with the following warning: 

 

Type  Name  Error
hudson.model.ListView Test  CannotResolveClassException: hudson.views.RegExJobFilter 

 Also the view jobFilters in the jenkins config.xml is empty. If I create a view manually with this filter conditions it works and looks in the config like the f

[JIRA] (JENKINS-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0

2018-04-18 Thread che...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chenyang Liu commented on  JENKINS-50850  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0   
 

  
 
 
 
 

 
 Seems it's also a problem in Azure side. AllocationFailed I don't know how large the size you chose. But you can do some tests to verify whether it's a plugin's problem or not. You can create the same size vm  through Azure Portal directly, and try to use plugin to provision VMs on the another region.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50781) Shiro Plugin - Refusing to marshal org.apache.shiro.authc.credential.AllowAllCredentialsMatcher for security reasons

2018-04-18 Thread yomo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 angel liang commented on  JENKINS-50781  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shiro Plugin - Refusing to marshal org.apache.shiro.authc.credential.AllowAllCredentialsMatcher for security reasons   
 

  
 
 
 
 

 
 thanks a lot, it worked with this workaround, bypass the classes(like AllowAllCredentialsMatcher), i am doing further testing on my Jenkins, cheers.  java -Dhudson.remoting.ClassFilter=some.pkg.and.ClassName,some.pkg.and.OtherClassName -jar jenkins.war  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50842) command-launcher terminates the process

2018-04-18 Thread alexandru.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandru Băluț updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50842  
 
 
  command-launcher terminates the process
 

  
 
 
 
 

 
Change By: 
 Alexandru Băluț  
 

  
 
 
 
 

 
 The command launcher is difficult to use for powering on and off instances as they are needed.As can be seen in [https://groups.google.com/forum/?nomobile=true#!topic/jenkinsci-users/EckKCU1rg9o] users might want to have a script which: powers on a remote computer,  starts the remote agent, power off the remote computer. This can be useful when the instance is in the cloud, used rarely, and it's very expensive to keep it on.Currently the powering off is very difficult to do because the command-launcher-plugin  terminates  kills   the process (when running the remote agent), so the "power-off" command is not executed.Maybe you can use  KILL  TERM  instead of  TERM  KILL  to stop the process, in which case the  users could use "trap power-off-method EXIT" to be able to power off the machine when the    script  is killed  can handle the event . Best would be if the script is not killed at all, and instead leave the remote agent  and the script  to stop by  itself  themselves . Then it would be possible to run the remaining commands in the script ,  as expected. This would also eliminate the need to detail this  termination  behaviour in the plugin documentation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

  

[JIRA] (JENKINS-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0

2018-04-18 Thread he...@geekware.co.za (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henti Smith commented on  JENKINS-50850  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0   
 

  
 
 
 
 

 
 Chenyang Liu Thank you for that link, when restarting Jenkins was trying to start up a max of 40 VMs of size Standard_F8s_v2 which is 8 vcpus and 16GB Ram.  We have 2 Standard_D2_v3 VM running for windows workers, which is 8 vcpus, 32 GB Ram.  So that should have only been 336 vcpus. I'll play around with this.  I'd also like to reitterate, that once I rolled back to 1.6.2, the problem went away and the plugin is working, so saying it's a resource limit issue does not make sense. The old verison of the plugin has exactly the same configuration (actually it's limited to 20 vms, not 40 like before) but still not seeing the issue above.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48905) SSL Connection to Rocket failes if Rocket host uses SNI

2018-04-18 Thread chrischild...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Childs commented on  JENKINS-48905  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSL Connection to Rocket failes if Rocket host uses SNI   
 

  
 
 
 
 

 
 Hello.  I am getting the exact same issue at the moment.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40387) Tag build from multibranch pipeline throws E200015

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 wrong credentials  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40387  
 
 
  Tag build from multibranch pipeline throws E200015   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/opto

[JIRA] (JENKINS-36356) Checkout error occurs randomly: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 wrong credentials  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36356  
 
 
  Checkout error occurs randomly: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you 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-25070) Subversion fails to update externals once after external is changed.

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-25070  
 
 
  Subversion fails to update externals once after external is changed.   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-35227) Multi-Branch-Job with Subversion repo which contains externals fails on checkout

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35227  
 
 
  Multi-Branch-Job with Subversion repo which contains externals fails on checkout   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50859) locked java.io.BufferedInputStream

2018-04-18 Thread ka...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 kay van der Zander created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50859  
 
 
  locked java.io.BufferedInputStream   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-04-18 09:40  
 
 
Environment: 
 Jenkisn 2.107.1 LTS   
 
 
Priority: 
  Critical  
 
 
Reporter: 
 kay van der Zander  
 

  
 
 
 
 

 
 Jenkins job build hangs, dead lock for pipline process. No other build can be build when it hangs. see job console, It stays like this until you abort the job build. below you can see that the same bat script calls hangs on a locked java.io.BufferedInputStream@a92403.    This happens 7 out of 10 builds. It is really a pain in the ass. job console: [Workspace] $ cmd /c call C:\Users\KZ\AppData\Local\Temp\jenkins7011635632695808959.bat c:\JenkinsJobs\test_054EB_build\Workspace>cd Product.054EB/Workdir/  — Building project in Release mode —  IAR Command Line Build Utility V6.4.4.0 Copyright 2002-2012 IAR Systems AB. Deleting outputs for configuration Release Updating build tree... 110 file(s) deleted.  ThreadDump: cmd /c call C:\Users\KZ\AppData\Local\Temp\jenkins7011635632695808959.bat: stdout copier "cmd /c call C:\Users\KZ\AppData\Local\Temp\jenkins7011635632695808959.bat: stdout copier" Id=40731 Group=main RUNNABLE (in native) at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) 
 
locked java.io.BufferedInputStream@a92403 
 at java.io.FilterInputStream.read(Unknown Source) at hudson.util.StreamCopyThread.run(StreamCopyThread.java:60)  
   

[JIRA] (JENKINS-37642) SVN Checkout with external fails only after new commit

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37642  
 
 
  SVN Checkout with external fails only after new commit   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-35227) Multi-Branch-Job with Subversion repo which contains externals fails on checkout

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35227  
 
 
  Multi-Branch-Job with Subversion repo which contains externals fails on checkout   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-35227) Multi-Branch-Job with Subversion repo which contains externals fails on checkout

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35227  
 
 
  Multi-Branch-Job with Subversion repo which contains externals fails on checkout   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Reopened Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50860) Multiple SSH connection using ssh key

2018-04-18 Thread pmis...@aurusinc.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prasanta Mishra created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50860  
 
 
  Multiple SSH connection using ssh key
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screenshot.png  
 
 
Components: 
 ssh-plugin  
 
 
Created: 
 2018-04-18 09:42  
 
 
Environment: 
 Linux  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Prasanta Mishra  
 

  
 
 
 
 

 
 My requirement is like this: The jenkins is installed in one server(say server A). I have 3 script in this server for deployment of war into different server say B and C. There is a main script say JenkinsMainScript.sh . Inside this script I have copied the deployment script(say serverB.sh/serverC.sh) from server A to the Corresponding server serverB or serverC based on parameter passed when execute the shell like : /root/Pictures/JenkinsTesting/JenkinsBuildMain.sh B in the jenkins's "Execute shell" under "Build" section of jenkins of a job where B is the server Name to deploy. i.e if I again pass C as parameter in the above statement then the main script will copy serverC.sh from server A to server C and deploy the war into that server Note:-All the deployment steps are written inside serverC.sh for server C and serverB.sh for Server B. Again My deployment is of two steps in jenkins, Job1 and Job2. 1.Create war file by taking source as git repository which is access using SSH(say server D) 2.After Successful execution of Job1 it will trigger Job2. Inside Job2 I am executing the JenkinsBuildMain.sh file under Build section. The Problem is If I add id_rsa and id_rsa.pub file inside .ssh directory of jenkins to access git server(server D) at the same time I can't access other se

[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31455  
 
 
  Build instability with "ISVNAuthentication provider did not provide credentials"   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50503) Jenkins job does not list latest SVN change

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50503  
 
 
  Jenkins job does not list latest SVN change   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50860) Multiple SSH connection using ssh key

2018-04-18 Thread pmis...@aurusinc.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prasanta Mishra updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50860  
 
 
  Multiple SSH connection using ssh key
 

  
 
 
 
 

 
Change By: 
 Prasanta Mishra  
 

  
 
 
 
 

 
 My requirement is like this: The jenkins is installed in one server(say server A). I have 3 script in this server for deployment of war into different server say *B and C*.There is a main script say *JenkinsMainScript.sh* . Inside this script I have copied the deployment script(say *serverB.sh/serverC.sh*) from server A to the Corresponding server serverB or serverC based on parameter passed when execute the shell like :/root/Pictures/JenkinsTesting/JenkinsBuildMain.sh Bin the jenkins's "*Execute shell*" under "*Build*" section of *jenkins* of a job where B is the server Name to deploy. i.e if I again pass C as parameter in the above statement then the main script will copy serverC.sh from server A to server C and deploy the war into that server Note:-All the deployment steps are written inside serverC.sh for server C and serverB.sh for Server B.Again My deployment is of two steps in jenkins, *Job1 and Job2.*1.Create war file by taking source as git repository which is access using SSH(say server D) 2.After Successful execution of Job1 it will trigger Job2.Inside Job2 I am executing the JenkinsBuildMain.sh file under *Build* section.The Problem is If I add id_rsa and id_rsa.pub file inside .ssh directory of jenkins to access git server(server D) at the same time I can't access other server like server B for deployment via SSH connection. Again if I add id_rsa and id_rsa.pub file inside .ssh for deployment server(server B) then Git server is unable to access at the same time. That means only one server is accessible using SSH connection at a time.Is there any way to access both server using same key or different key?Or can we add multiple key for ssh connection so that it can access to both server, *server D* for git clone and server B for copying the script file from jenkins server to *server B*.When I do this I got Bellow Message: *"Host key verification failed. lost connection"*Current I am able connect one server at a time. If It connect to Git server the shell script file is not able to copy ,saying above error, and if I able set up for copying the file the git Server is unable to access saying*Return status code 128. Permission denied (PublicKey,gssapi-keyex,gssapi-mic,password)**Is There any way to add multiple keys for ssh connection for different server using Jenkins?*Bellow is my script Code to copy the deploy script to remote server.*_JenkinsMainScript.sh:_*{{if [ $serverId = 'B' ] then scp $scriptSourcePath/serverB.sh $serverBPathToCopyTheFile/ ssh -l $serverBUserName $IpAddr $serverBPathToExecuteTheFile/serverB.sh else echo " No Matching condition found..." fi}}Here is the screen shot of Configuration in the Jenkins for job2: [Jenkins Config for job2|https://i.stack.imgur.com/qzf9I.png]   Can anyone help me on this. Thanks in advance  
 

  

[JIRA] (JENKINS-45801) Fetching changes fails with SVNAuthenticationException due many svn:externals

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45801  
 
 
  Fetching changes fails with SVNAuthenticationException due many svn:externals   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Reopened Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-15374) hudson.util.IOException2: remote file operation failed at hudson.remoting.Channel@

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-15374  
 
 
  hudson.util.IOException2: remote file operation failed at hudson.remoting.Channel@   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50603) Rename a build make it favorite for everyone

2018-04-18 Thread deep.alexan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Nordlund commented on  JENKINS-50603  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rename a build make it favorite for everyone   
 

  
 
 
 
 

 
 I've sent a pull-request with a fix for this. https://github.com/jenkinsci/favorite-plugin/pull/22  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50603) Rename a build make it favorite for everyone

2018-04-18 Thread deep.alexan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Nordlund started work on  JENKINS-50603  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Alex Nordlund  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50638  
 
 
  windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
Change By: 
 Zack Snyder  
 
 
Attachment: 
 image-2018-04-18-11-55-42-400.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50638  
 
 
  windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
Change By: 
 Zack Snyder  
 
 
Attachment: 
 image-2018-04-18-11-55-31-400.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder commented on  JENKINS-50638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
 No files were created.
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder edited a comment on  JENKINS-50638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
 No files were created.!image-2018-04-18-11-55- 42 31 -400.png!!image-2018-04-18-11-55- 31 42 -400.png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50603) Rename a build make it favorite for everyone

2018-04-18 Thread deep.alexan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Nordlund updated  JENKINS-50603  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50603  
 
 
  Rename a build make it favorite for everyone   
 

  
 
 
 
 

 
Change By: 
 Alex Nordlund  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50859) locked java.io.BufferedInputStream

2018-04-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-50859  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: locked java.io.BufferedInputStream   
 

  
 
 
 
 

 
 Please provide a full thread dump  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-29592) JS errors in Build Pipeline plugin, some buttons not working

2018-04-18 Thread antony.gelb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antony Gelberg closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This went away at some point...  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-29592  
 
 
  JS errors in Build Pipeline plugin, some buttons not working   
 

  
 
 
 
 

 
Change By: 
 Antony Gelberg  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://grou

[JIRA] (JENKINS-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0

2018-04-18 Thread che...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chenyang Liu commented on  JENKINS-50850  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0   
 

  
 
 
 
 

 
 You said "This happened for all VMs being provisioned". Is it means the plugin can't provision any VMs since restart? After restarting, are there already a lot of VMs in Azure? Actually we only change the way to create storage account in the 0.7.0. We didn't change the ARM template. So I can't give you a clear reason why it happened now. But you can try to catch full ARM template in the deployment in portal. If there's something different, it may give me some hint.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50638  
 
 
  windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
Change By: 
 Zack Snyder  
 
 
Attachment: 
 config.zip  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder commented on  JENKINS-50638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
 Here is my output of the console: 

 
BuildUser@W10x64-BuildSrv /cygdrive/c/Users/BuildUser
$ D:
bash: D:: command not found

BuildUser@W10x64-BuildSrv /cygdrive/c/Users/BuildUser
$ cd d:

BuildUser@W10x64-BuildSrv /cygdrive/d
$ cd CI/jenkins-ssh/

BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins-ssh
$ d:
bash: d:: command not found

BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins-ssh
$ cd ..

BuildUser@W10x64-BuildSrv /cygdrive/d/CI
$ cd ..

BuildUser@W10x64-BuildSrv /cygdrive/d
$ cd C:

BuildUser@W10x64-BuildSrv /cygdrive/c
$ cls
bash: cls: command not found

BuildUser@W10x64-BuildSrv /cygdrive/c
$ clear
bash: clear: command not found

BuildUser@W10x64-BuildSrv /cygdrive/c
$ cls
bash: cls: command not found

BuildUser@W10x64-BuildSrv /cygdrive/c
$ "D:\CI\jenkins-ssh" && java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt"
> pwd
> ls
>

BuildUser@W10x64-BuildSrv /cygdrive/c
$ d:
bash: d:: command not found

BuildUser@W10x64-BuildSrv /cygdrive/c
$ cd D:

BuildUser@W10x64-BuildSrv /cygdrive/d
$ cd CI/jenkins

BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins
$ java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt"
>

BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins
$ java -jar slave.jar
WARNING: Are you running agent from an interactive console?
If so, you are probably using it incorrectly.
See https://wiki.jenkins.io/display/JENKINS/Launching+agent+from+console
<===[JENKINS REMOTING CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQABAgABSgAEbWFza3hwAP4=
 

 Only when I execute java.jar directly, (like you can see on the last cmd) I could start the agent, otherwise it was not returning from execution. See attached now the correct config.xml  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011

[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50638  
 
 
  windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
Change By: 
 Zack Snyder  
 
 
Attachment: 
 config.xml..zip  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50638  
 
 
  windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
Change By: 
 Zack Snyder  
 
 
Attachment: 
 config.xml.zip  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50638  
 
 
  windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
Change By: 
 Zack Snyder  
 
 
Attachment: 
 config.xml..zip  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48905) SSL Connection to Rocket failes if Rocket host uses SNI

2018-04-18 Thread hyper...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Reinhardt commented on  JENKINS-48905  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSL Connection to Rocket failes if Rocket host uses SNI   
 

  
 
 
 
 

 
 sorry to say, but I don't have time to investigate further  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-50327  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest   
 

  
 
 
 
 

 
 I was unable to replicate the issue with the following configuration, Could you please install the support plugin in your instance and generate a support bundle with only the "About Jenkins" check marked and attach it to this Jira? you can change all the sensible info in the About.md I only want to have the same set of plugins to tested it. 

 

Jenkins
===

Version details
---

  * Version: `2.107.1.2`

Active Plugins
--
  * ace-editor:1.1 '_javascript_ GUI Lib: ACE Editor bundle plugin'
  * apache-httpcomponents-client-4-api:4.5.3-2.1 'Jenkins Apache HttpComponents Client 4.x API Plugin'
  * async-http-client:1.7.24.1 'Async Http Client'
  * authentication-tokens:1.3 'Authentication Tokens API Plugin'
  * blueocean:1.5.0 'Blue Ocean'
  * blueocean-autofavorite:1.2.2 'Autofavorite for Blue Ocean'
  * blueocean-bitbucket-pipeline:1.5.0 'Bitbucket Pipeline for Blue Ocean'
  * blueocean-commons:1.5.0 'Common API for Blue Ocean'
  * blueocean-config:1.5.0 'Config API for Blue Ocean'
  * blueocean-core-js:1.5.0 'Blue Ocean Core JS'
  * blueocean-dashboard:1.5.0 'Dashboard for Blue Ocean'
  * blueocean-display-url:2.2.0 'Display URL for Blue Ocean'
  * blueocean-events:1.5.0 'Events API for Blue Ocean'
  * blueocean-git-pipeline:1.5.0 'Git Pipeline for Blue Ocean'
  * blueocean-github-pipeline:1.5.0 'GitHub Pipeline for Blue Ocean'
  * blueocean-i18n:1.5.0 'i18n for Blue Ocean'
  * blueocean-jira:1.5.0 'JIRA Integration for Blue Ocean'
  * blueocean-jwt:1.5.0 'JWT for Blue Ocean'
  * blueocean-personalization:1.5.0 'Personalization for Blue Ocean'
  * blueocean-pipeline-api-impl:1.5.0 'Pipeline implementation for Blue Ocean'
  * blueocean-pipeline-editor:1.5.0 'Blue Ocean Pipeline Editor'
  * blueocean-pipeline-scm-api:1.5.0 'Pipeline SCM API for Blue Ocean'
  * blueocean-rest:1.5.0 'REST API for Blue Ocean'
  * blueocean-rest-impl:1.5.0 'REST Implementation for Blue Ocean'
  * blueocean-web:1.5.0 'Web for Blue Ocean'
  * bouncycastle-api:2.16.2 'bouncycastle API Plugin'
  * branch-api:2.0.19 'Branch API Plugin'
  * command-launcher:1.2 'Command Agent Launcher Plugin'
  * config-file-provider:2.18 'Config File Provider Plugin'
  * credentials:2.1.16 'Credentials Plugin'
  * credentials-binding:1.16 'Credentials Binding Plugin'
  * display-url-api:2.2.0 'Display URL API'
  * docker-commons:1.11 'Docker Commons Plugin'
  * docker-workflow:1.15.1 'Docker Pipeline'
  * durable-task:1.22 'Durable Task Plugin'
  * favorite:2.3.1 'Favorite'
  * git:3.8.0 'Jenkins Git plugin'
  * git-client:2.7.1 'Jenkins Git client plugin'
  * git-server:1.7 'Jenkins GIT server Plugin'
  * github:1.29.0 'GitHub plugin'
  * github-api:1.90 'GitHub API Plugin'
  * github-branch-source:2.3.3 'GitHub Branch Source Plugin'
  * handy-uri-templates-2-api:2.1.6-1.0 'Handy Uri Templates 2.x API Plugin'
  * htmlpublisher:1.16 'HTML Publisher plugin'
  * jackson2-api:2.8.11.1 'Jackson 2 API Plugin'
  * jenkins-design-language:1.5.0 'Jenkins Design Language'
  * jira:2.5 'Jenkins JIRA plugin'
  * jquery-detached:1.2.1 '_javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin'
  * jsch:0.1.54.2 'Jenkins JSch dependency plugin'
  * junit:1.24 'JUnit Plugin'
  * mailer:1.21 'Jenkins Mailer Plugin'
  * mapdb-api:1.0.9.0 'MapDB API Plugin'
  * matrix-project:1.13 'Matrix Project Plugin'
  * mercuria

[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50287  
 
 
  Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Comment: 
 see JENKINS-50287  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
 this is the PR https://github.com/jenkinsci/subversion-plugin/pull/200  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49105) Can't send data to influx

2018-04-18 Thread peter.dank...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Danko commented on  JENKINS-49105  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't send data to influx   
 

  
 
 
 
 

 
 I am able to send the data to influx nerveless i see this kind of error in Jenkins log:   INFO: [InfluxDB Plugin] Publishing data to: [url="" description=influxDB, username=jenkins, password=*, database=jenkins] Apr 18, 2018 12:23:36 PM org.jenkinsci.plugins.structs.describable.DescribableModel uninstantiate2 WARNING: Cannot create control version of class jenkinsci.plugins.influxdb.InfluxDbPublisher using {target=[url="" description=influxDB, username=jenkins, password=*, database=jenkins]} java.lang.IllegalArgumentException: Could not instantiate {target=[url="" description=influxDB, username=jenkins, password=*, database=jenkins]} for InfluxDbPublisher(target: String, customData?: java.lang.UnsupportedOperationException: do not know how to categorize attributes of type java.util.Map, customDataMap?: java.lang.UnsupportedOperationException: do not know how to categorize attributes of type java.util.Map>, customPrefix?: String, customProjectName?: String): java.lang.ClassCastException: jenkinsci.plugins.influxdb.InfluxDbPublisher.target expects class java.lang.String but received class jenkinsci.plugins.influxdb.models.Target     at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:286)     at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2(DescribableModel.java:572)     at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2_(DescribableModel.java:646)     at org.jenkinsci.plugins.structs.describable.DescribableParameter.uncoerce(DescribableParameter.java:196)     at org.jenkinsci.plugins.structs.describable.DescribableParameter.inspect(DescribableParameter.java:142)     at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2(DescribableModel.java:555)     at org.jenkinsci.plugins.workflow.actions.ArgumentsAction.resolve(ArgumentsAction.java:308)     at org.jenkinsci.plugins.workflow.actions.ArgumentsAction.getResolvedArguments(ArgumentsAction.java:295)     at org.jenkinsci.plugins.workflow.cps.nodes.StepAtomNode.getDelegateType(StepAtomNode.java:134)     at org.jenkinsci.plugins.workflow.cps.nodes.StepAtomNode.effectiveFunctionName(StepAtomNode.java:111)     at org.jenkinsci.plugins.workflow.cps.nodes.StepAtomNode.getTypeFunctionName(StepAtomNode.java:123)     at org.jenkinsci.plugins.workflow.graph.FlowNode.getDisplayFunctionName(FlowNode.java:261)     at org.jenkinsci.plugins.workflow.job.WorkflowRun.logNodeMessage(WorkflowRun.java:1113)     at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1000(WorkflowRun.java:142)     at org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:1092)     at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1413)     at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:412)     at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35)     at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)     at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)     at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)     at java.util.concurrent.FutureTask.run(FutureTask.java:266)     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)     

[JIRA] (JENKINS-50861) Update core and Pipeline SCM step dependencies

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50861  
 
 
  Update core and Pipeline SCM step dependencies   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ivan Fernandez Calvo  
 
 
Components: 
 subversion-plugin  
 
 
Created: 
 2018-04-18 10:47  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ivan Fernandez Calvo  
 

  
 
 
 
 

 
 Update Pipeline SCM step to 2.3 version this implies to upgrade core to 2.60 and java version to 8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
  

[JIRA] (JENKINS-50862) Failure to provision GCE nodes with new Images which no longer contain the deprecated key "archiveSizeBytes"

2018-04-18 Thread m...@pi-top.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Simons created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50862  
 
 
  Failure to provision GCE nodes with new Images which no longer contain the deprecated key "archiveSizeBytes"   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Fritz Elfert  
 
 
Components: 
 jclouds-plugin  
 
 
Created: 
 2018-04-18 10:49  
 
 
Environment: 
 Jenkins version 2.117  jclouds version 2.14  
 
 
Labels: 
 jclouds  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Matt Simons  
 

  
 
 
 
 

 
 When trying to create any new nodes, which use an image that does not contain the json key archiveSizeBytes in its metadata the following exception gets thrown and the node is not created. I believe this key has been deprecated. e.g.  {{ {}} {{ "creationTimestamp": "2018-04-17T05:56:22.471-07:00",}} {{ "description": "",}} {{ "diskSizeGb": "100",}} {{ "id": "2363603295000875034",}} {{ "kind": "compute#image",}} {{ "labelFingerprint": "42WmSpB8rSM=",}} {{ "licenseCodes": [}} {{ "1000204"}} {{ ],}} {{ "licenses": [}} {{ "https://www.googleapis.com/compute/v1/projects/debian-cloud/global/licenses/debian-8-jessie"}} {{ ],}} {{ "name": "debian-8-jessie-v20171020-rpi-cross-compile-qt-5-9-1",}} {{ "selfLink": "https://www.googleapis.com/compute/v1/projects/pt-builds/global/images/debian-8-jessie-v20171020-rpi-cross-compile-qt-5-9-1",}} {{ "sourceImage": "https://www.googleapis.com/compute/v1/projects/pt-builds/global/images/debian-8-jessie-v20171020-java8-100gb-1",}} {{ "sourceImageId": "7885706136937541931",}} {{ "sourceType": "RAW",}} {{ "status": "READY"}} {{ },}} {{ "selfLink": "https://www.googleapis.com/compute/v1/projects/debian-cloud/global/images/debian-8-jessie-v20180401",}} {{ "

[JIRA] (JENKINS-50862) Failure to provision GCE nodes with new Images which no longer contain the deprecated key "archiveSizeBytes"

2018-04-18 Thread m...@pi-top.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Simons updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50862  
 
 
  Failure to provision GCE nodes with new Images which no longer contain the deprecated key "archiveSizeBytes"   
 

  
 
 
 
 

 
Change By: 
 Matt Simons  
 

  
 
 
 
 

 
 When trying to create any new nodes, which use an image that does not contain the json key archiveSizeBytes in its metadata the following exception gets thrown and the node is not created. I believe this key has been deprecated.e.g. {{    \{}}{{ "creationTimestamp": "2018-04-17T05:56:22.471-07:00",}}{{ "description": "",}}{{ "diskSizeGb": "100",}}{{ "id": "2363603295000875034",}}{{ "kind": "compute#image",}}{{ "labelFingerprint": "42WmSpB8rSM=",}}{{ "licenseCodes": [}}{{ "1000204"}}{{ ],}}{{ "licenses": [}}{{ "https://www.googleapis.com/compute/v1/projects/debian-cloud/global/licenses/debian-8-jessie"}}{{ ],}}{{ "name": "debian-8-jessie-v20171020-rpi-cross-compile-qt-5-9-1",}}{{ "selfLink": "https://www.googleapis.com/compute/v1/projects/pt-builds/global/images/debian-8-jessie-v20171020-rpi-cross-compile-qt-5-9-1",}}{{ "sourceImage": "https://www.googleapis.com/compute/v1/projects/pt-builds/global/images/debian-8-jessie-v20171020-java8-100gb-1",}}{{ "sourceImageId": "7885706136937541931",}}{{ "sourceType": "RAW",}}{{ "status": "READY"}}{{ } , }} {{ "selfLink": "https://www.googleapis.com/compute/v1/projects/debian-cloud/global/images/debian-8-jessie-v20180401",}}  {{ "sourceType": "RAW",}}{{ "status": "READY"}}{{ }}}     {{ }}{{ java.lang.NullPointerException: Null archiveSizeBytes at org.jclouds.googlecomputeengine.domain.AutoValue_Image.(AutoValue_Image.java:67) at org.jclouds.googlecomputeengine.domain.Image.create(Image.java:100) at sun.reflect.GeneratedMethodAccessor410.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at shaded.com.google.common.reflect.Invokable$MethodInvokable.invokeInternal(Invokable.java:197) at shaded.com.google.common.reflect.Invokable.invoke(Invokable.java:102) at org.jclouds.json.internal.DeserializationConstructorAndReflectiveTypeAdapterFactory$DeserializeIntoParameterizedConstructor.newInstance(DeserializationConstructorAndReflectiveTypeAdapterFactory.java:224) at org.jclouds.json.internal.DeserializationConstructorAndReflectiveTypeAdapterFactory$DeserializeIntoParameterizedConstructor.read(DeserializationConstructorAndReflectiveTypeAdapterFactory.java:204) at org.jclouds.googlecloud.config.ListPageAdapterFactory$ListPageAdapter.readItems(ListPageAdapterFactory.java:73) at org.jclouds.googlecloud.config.ListPageAdapterFactory$ListPageAdapter.read(ListPageAdapterFactory.java:56) at org.jclouds.googlecloud.config.ListPageAdapterFactory$ListPageAdapter.read(ListPageAdapterFactory.java:36) at com.google.gson.Gson.fromJson(Gson.java:861) at com.google.gson.Gson.fromJson(Gson.java:826) at org.jclouds.json.internal.GsonWrapper.fromJson(GsonWrapper.java:55) at org.jclouds.http.functions.ParseJson.apply(ParseJson.java:82) at org.jclouds.http.functions.Par

[JIRA] (JENKINS-50861) Update core and Pipeline SCM step dependencies

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-50861  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update core and Pipeline SCM step dependencies   
 

  
 
 
 
 

 
 
 
Update Pipeline SCM step to 2.3 
Update Pipeline to 2.5 for test 
Update core to 2.60 
Update Java to 8 
Update SCM API to 2.2.6 
Update credentials to 2.1.16 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder edited a comment on  JENKINS-50638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
 Here is my output of the console  (logged in from the master agent, where jenkins is running) :{noformat}BuildUser@W10x64-BuildSrv /cygdrive/c/Users/BuildUser$ D:bash: D:: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c/Users/BuildUser$ cd d:BuildUser@W10x64-BuildSrv /cygdrive/d$ cd CI/jenkins-ssh/BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins-ssh$ d:bash: d:: command not foundBuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins-ssh$ cd ..BuildUser@W10x64-BuildSrv /cygdrive/d/CI$ cd ..BuildUser@W10x64-BuildSrv /cygdrive/d$ cd C:BuildUser@W10x64-BuildSrv /cygdrive/c$ clsbash: cls: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c$ clearbash: clear: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c$ clsbash: cls: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c$ "D:\CI\jenkins-ssh" && java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt"> pwd> ls>BuildUser@W10x64-BuildSrv /cygdrive/c$ d:bash: d:: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c$ cd D:BuildUser@W10x64-BuildSrv /cygdrive/d$ cd CI/jenkinsBuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins$ java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt">BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins$ java -jar slave.jarWARNING: Are you running agent from an interactive console?If so, you are probably using it incorrectly.See https://wiki.jenkins.io/display/JENKINS/Launching+agent+from+console<===[JENKINS REMOTING CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQABAgABSgAEbWFza3hwAP4={noformat}  Only when I execute java.jar directly, (like you can see on the last cmd) I could start the agent, otherwise it was not returning from execution.See attached now the correct config.xml   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
   

[JIRA] (JENKINS-50676) Jenkins does not recognize "Jenkinsfile"

2018-04-18 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder commented on  JENKINS-50676  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins does not recognize "Jenkinsfile"   
 

  
 
 
 
 

 
 The problem was happening, because I disable the master agent (where jenkins) is running. It was for me unclear, that I cannot disable this agent, otherwise not build will be performed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50861) Update core and Pipeline SCM step dependencies

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo started work on  JENKINS-50861  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo updated  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50287  
 
 
  Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Reopened Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo started work on  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo started work on  JENKINS-50638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo started work on  JENKINS-50327  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-50638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: windows agent via SSH - Slave JVM has terminated. Exit code   
 

  
 
 
 
 

 
 >Only when I execute java.jar directly, (like you can see on the last cmd) I could start the agent, otherwise it was not returning from execution. That it is ok, it should not return, I wanted to check that you can execute the java -jar slave.jar and it does not return errors.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40387) Tag build from multibranch pipeline throws E200015

2018-04-18 Thread marc.jegliew...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marc Jegliewski commented on  JENKINS-40387  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Tag build from multibranch pipeline throws E200015   
 

  
 
 
 
 

 
 If the credentials weren't correct, wouldn't Jenkins be unable to checkout the repository in the first place?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50863) list.empty broken in pipeline scripts

2018-04-18 Thread hans-jakob.ho...@tracetronic.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hans-Jakob Holtz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50863  
 
 
  list.empty broken in pipeline scripts   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-cps-plugin  
 
 
Created: 
 2018-04-18 11:39  
 
 
Environment: 
 Ubuntu 16.04.3 64bit  OpenJDK 1.8.0_151  Jenkins 2.89.4  Pipeline:Groovy 2.48  
 
 
Labels: 
 regression  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Hans-Jakob Holtz  
 

  
 
 
 
 

 
 Since upgrading to Pipeline:Groovy 2.48, the .empty property of List objects gives very strange results, whose boolean value in particular is the reverse of the expected. When executing the following script as a pipeline (testet via "Replay" and replacing the existing script by this) gives weird output:  Script 

 

x = [] as List
println x
println x.isEmpty()
println x.empty
x<<"hello"
println x
println x.isEmpty()
println x.empty
 

 Expected output 

 

[Pipeline] echo
[]
[Pipeline] echo
true
[Pipeline] echo
true
[Pipeline] echo
[hello]
[Pipeline] echo
false
[Pipeline] echo
false
[Pipeline] End of Pipeline
 

 Actual outp

[JIRA] (JENKINS-43440) Support for pipeline jobs?

2018-04-18 Thread lucamilane...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 lucamilanesio commented on  JENKINS-43440  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for pipeline jobs?   
 

  
 
 
 
 

 
 Fixed in: https://github.com/jenkinsci/statistics-gatherer-plugin/pull/7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50746) statistics-gatherer-plugin should be able to feed data into mongodb

2018-04-18 Thread lucamilane...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 lucamilanesio resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50746  
 
 
  statistics-gatherer-plugin should be able to feed data into mongodb   
 

  
 
 
 
 

 
Change By: 
 lucamilanesio  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-43440) Support for pipeline jobs?

2018-04-18 Thread lucamilane...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 lucamilanesio resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43440  
 
 
  Support for pipeline jobs?   
 

  
 
 
 
 

 
Change By: 
 lucamilanesio  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50459) 401 when trying to update the build status in gitea

2018-04-18 Thread james.strac...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Strachan commented on  JENKINS-50459  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 401 when trying to update the build status in gitea   
 

  
 
 
 
 

 
 this could maybe be related to the kind of Credential it is and its format/data - we hit a similar issue with Bitbucket on Jenkins X: https://github.com/jenkins-x/jx/issues/665  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo updated  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50287  
 
 
  Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50773) Pipline script for vSphere ExposeGuestInfo generates . Pipeline DSL ExposeGuestInfo Build fails

2018-04-18 Thread pjdar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 pjdarton commented on  JENKINS-50773  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipline script for vSphere ExposeGuestInfo generates . Pipeline DSL ExposeGuestInfo Build fails
 

  
 
 
 
 

 
 FYI Jason ceased to be the plugin maintainer some time ago, and Eric's involvement on this is equally minimal. They both have day jobs that does not include supporting this plugin (as do I). You might get somewhere by looking at the https://wiki.jenkins.io/display/JENKINS/Team+Concert+Plugin page's explanation of how to access their environment variables.  e.g. if you substituted org.jenkinsci.plugins.vsphere.builders.ExposeGuestInfo.VSphereEnvAction for com.ibm.team.build.internal.hjplugin.RTCBuildResultAction Neither that plugin nor this one was written with pipeline support in mind, so workarounds for one (or other similarly aged plugins) might well work for others.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48905) SSL Connection to Rocket failes if Rocket host uses SNI

2018-04-18 Thread chrischild...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Childs commented on  JENKINS-48905  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSL Connection to Rocket failes if Rocket host uses SNI   
 

  
 
 
 
 

 
 Andreas Bauer were you able to find work around for this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36356) Checkout error occurs randomly: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials

2018-04-18 Thread joachim.h...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joachim Herb commented on  JENKINS-36356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Checkout error occurs randomly: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Why is this (and also all related bugs) closed? It is a real problem/bug, that every second build is broken due to a failed checkout. I know that there is a work around (somewhere described in one of the bugs), but this should not be the solution.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50858) CannotResolveClassException if jobfilters with regex is used

2018-04-18 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-50858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CannotResolveClassException if jobfilters with regex is used   
 

  
 
 
 
 

 
 Can you try to restart Jenkins and see if the problem persists?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50858) CannotResolveClassException if jobfilters with regex is used

2018-04-18 Thread juergen_thom...@linfre.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jürgen Thomann commented on  JENKINS-50858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CannotResolveClassException if jobfilters with regex is used   
 

  
 
 
 
 

 
 Seems like a restart of Jenkins fixed this problem. It it still a bit strange for me, why this would happen without knowing what Jenkins is internally doing, but thanks for the fast response.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50858) CannotResolveClassException if jobfilters with regex is used

2018-04-18 Thread juergen_thom...@linfre.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jürgen Thomann commented on  JENKINS-50858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CannotResolveClassException if jobfilters with regex is used   
 

  
 
 
 
 

 
 Seems like a restart of Jenkins fixed this problem. It it still a bit strange for me, why this would happen without knowing what Jenkins is internally doing, but thanks for the fast response.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50809) error: "executeRequest exception: Exception of type 'HP.PC.API.Common.Exceptions.InvalidAuthenticationDataException' was thrown. Error code: 1100 Login failed"

2018-04-18 Thread svetlana.stoyn...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Svetlana Stoynova commented on  JENKINS-50809  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: error: "executeRequest exception: Exception of type 'HP.PC.API.Common.Exceptions.InvalidAuthenticationDataException' was thrown. Error code: 1100 Login failed"   
 

  
 
 
 
 

 
 Hello, Is it possible to have an update on this as this is a very critical issue for the customer? Thank you in advance! Best Regards, Svetlana Stoynova  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46182) java.lang.AssertionError: InstanceIdentity is missing its singleton

2018-04-18 Thread akshaymohangu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Akshay Gupta updated  JENKINS-46182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46182  
 
 
  java.lang.AssertionError: InstanceIdentity is missing its singleton   
 

  
 
 
 
 

 
Change By: 
 Akshay Gupta  
 
 
Status: 
 Resolved In Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value

2018-04-18 Thread deiwin.sar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Deiwin Sarjas commented on  JENKINS-50525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error When Provisioning Slave: mountPath: Required value   
 

  
 
 
 
 

 
 This is marked with a priority "Minor", which is defined as "Minor loss of function, or other problem where easy workaround is present.". Not being able to provision pods feels pretty major to me and as far as I can see there's no known workaround.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50858) CannotResolveClassException if jobfilters with regex is used

2018-04-18 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-50858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CannotResolveClassException if jobfilters with regex is used   
 

  
 
 
 
 

 
 I think it's a problem with the class loaders, but I'll just add a warning to the console log when the seed job runs after installing plugins without a restart.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47227) failed to uncoerce hudson.plugins.robot.RobotPublisher@1f5a660a java.lang.UnsupportedOperationException: no public field ‘enableCache’ (or getter method) found in class hudson.p

2018-04-18 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-47227  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: failed to uncoerce hudson.plugins.robot.RobotPublisher@1f5a660a java.lang.UnsupportedOperationException: no public field ‘enableCache’ (or getter method) found in class hudson.plugins.robot.RobotPublisher   
 

  
 
 
 
 

 
 Code changed in jenkins User: Robby Pocase Path: src/main/java/hudson/plugins/robot/RobotPublisher.java http://jenkins-ci.org/commit/robot-plugin/ef719349b999ba7e8319fb71b992cc84615e7257 Log: [FIXED JENKINS-47227] Add public getEnableCache  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50864) kubernetes-cli-plugin is not working.

2018-04-18 Thread sunilchau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sunil Chauraha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50864  
 
 
  kubernetes-cli-plugin is not working.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Max Laverse  
 
 
Attachments: 
 error-log.txt  
 
 
Components: 
 kubernetes-cli-plugin  
 
 
Created: 
 2018-04-18 13:20  
 
 
Labels: 
 pipeline kuberenetes-plugin  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Sunil Chauraha  
 

  
 
 
 
 

 
 I have configured kubernetes-cli plugin on my Jenkins to deploy my docker image on Kubernetes cluster. But when I run my job, I am getting error as below. Detailed error is attached as error-log.txterror-log.txterror-log.txt.   Caused: java.io.IOException: Cannot run program "kubectl": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:245) at hudson.Proc$LocalProc.(Proc.java:214)   Jenkins Pipeline stage: 

 

node {
label ''
script {
git (url: 'git@gitlab..com:***/kubectl-cli.git', branch: 'master', credentialsId: 'sousr'
}
stage('List pods') {

withKubeConfig(
credentialsId: 'token-g88c9:sklnbp7rktcf4b99vg2vzbh7t66v7rbrp7rk6js6pcv6dmmb5jlr92', 
serverUrl: 'https://maui1.*.com/v3') {
sh 'kubectl get pods' 
}
}
}

 

    
 

  
 

[JIRA] (JENKINS-50786) Implement pathRestriction to job DSL extension context

2018-04-18 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50786  
 
 
  Implement pathRestriction to job DSL extension context   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50786) Implement pathRestriction to job DSL extension context

2018-04-18 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-50786  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Implement pathRestriction to job DSL extension context   
 

  
 
 
 
 

 
 This is already supported by the Dynamic DSL: 

 

pipelineJob('example') {
  definition {
cpsScm {
  scm {
git {
  extensions {
pathRestriction {
  includedRegions('includedFiles')
  excludedRegions('excludedFiles')
}
  }
}
  }
}
  }
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50327  
 
 
  Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Attachment: 
 logger.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-50327  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest   
 

  
 
 
 
 

 
 You could try to enable verbose log over the plugin an SVNKit library, to do that add a logger to those loggers with log level ALL , it is really verbose so just after configure it make the test and change the log level again to ERROR or INFO. 
 
svnkit 
svnkit-network 
svnkit-wc 
hudson.scm.SubversionSCM 
Also, I found this one https://community.atlassian.com/t5/Bitbucket-questions/NullPointerException-when-setting-up-SVN-Mirror/qaq-p/762818 , it suggests that it is related to the response from the server, a possible solution could be to add `-Dsvnkit.http.methods=Basic,Digest,NTLM,Negotiate` to the Jenkins JVM options.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest

2018-04-18 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo edited a comment on  JENKINS-50327  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest   
 

  
 
 
 
 

 
  You could try to enable verbose log over the plugin an SVNKit library, to do that add a logger to those loggers with log level ALL , it is really verbose so just after configure it make the test and change the log level again to ERROR or INFO.* svnkit* svnkit-network* svnkit-wc* hudson.scm.SubversionSCM !logger.png| thumbnail width=600px ! Also, I found this one https://community.atlassian.com/t5/Bitbucket-questions/NullPointerException-when-setting-up-SVN-Mirror/qaq-p/762818 , it suggests that it is related to the response from the server, a possible solution could be to add `-Dsvnkit.http.methods=Basic,Digest,NTLM,Negotiate` to the Jenkins JVM options.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31810) Publish over SSH plugin : cannot use build parameters filters in transfer set fields

2018-04-18 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl assigned an issue to Alex Earl  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31810  
 
 
  Publish over SSH plugin : cannot use build parameters filters in transfer set fields   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Assignee: 
 bap Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-29596) Always publish option is needed

2018-04-18 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl assigned an issue to Alex Earl  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-29596  
 
 
  Always publish option is needed   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Assignee: 
 bap Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-27979) PublishOverSSHPlugin stops at 130MB on MacOS

2018-04-18 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl assigned an issue to Alex Earl  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27979  
 
 
  PublishOverSSHPlugin stops at 130MB on MacOS   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Assignee: 
 bap Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49211) Build gets stuck on Publish Over CIFS

2018-04-18 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl assigned an issue to Alex Earl  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49211  
 
 
  Build gets stuck on Publish Over CIFS   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Assignee: 
 bap Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-26246) Publish over ssh on multiple nodes

2018-04-18 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl assigned an issue to Alex Earl  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26246  
 
 
  Publish over ssh on multiple nodes   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Assignee: 
 bap Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49119) Support suppression of SSH server inactivity timeouts

2018-04-18 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl assigned an issue to Alex Earl  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49119  
 
 
  Support suppression of SSH server inactivity timeouts   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Assignee: 
 bap Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


  1   2   3   >