[JIRA] (JENKINS-51242) Jenkins doesn't take configured JDK

2018-08-01 Thread narayanaba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 uday reddy edited a comment on  JENKINS-51242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins doesn't take configured JDK   
 

  
 
 
 
 

 
 yes, slave machine are forcefully running on java8,  i tried to launch slave machines with java7 but master expecting to run slave machine  on java 8 only.slave machines are not supporting to java7  while running java7 Projects, it failing to execute the java7 commands  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

2018-08-01 Thread dinaa....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dinesh commented on  JENKINS-52810  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins   
 

  
 
 
 
 

 
 I have validated the configurations and all are proper. When i executed the build i am facing the below issue without a configuration change : fail to accquire lock because of timeout, skip locking... CSRF protection is disabled on the remote server. fail to accquire lock because of timeout, skip locking... Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/,  parameters: Retry attempt #1 out of 5 Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/  parameters: Retry attempt #2 out of 5 Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/,  parameters:  Retry attempt #3 out of 5 Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/,  parameters:  Retry attempt #4 out of 5 Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/,  parameters:  Retry attempt #5 out of 5 ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'. ERROR: ExceedRetryLimitException: Max number of connection retries have been exeeded. BTW, in the error "view/All/queue/item/81305/api/json/" is automatically getting added. If that is added in URL the same path will not be present. Kindly can you provide your inputs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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

[JIRA] (JENKINS-51242) Jenkins doesn't take configured JDK

2018-08-01 Thread narayanaba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 uday reddy commented on  JENKINS-51242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins doesn't take configured JDK   
 

  
 
 
 
 

 
 yes, slave machine are forcefully running on java8,  i tried to launch slave machines with java7 but master expecting to run slave machine  on java 8 only. slave machines are not supporting to java7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-49796) git fetch timeout

2018-08-01 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-49796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git fetch timeout
 

  
 
 
 
 

 
 Sergey Smirnov you'll need to provide much more detail before I'm persuaded that the problem you're seeing is related to this report. For example, here are some questions to consider in your investigation: 
 
If you clone with JGit using that same passphrase protected private key, does the fetch succeed? 
if you use a private key that is not protected by a passphrase, does the fetch succeed? 
if you use a username / password with http (or https) does the fetch succeed? 
If you clone the same repository from a Freestyle job using the same passphrase protected private key, does the fetch succeed? 
Is your Jenkins server running as a foreground process with access to a controlling terminal (for example, from a Docker command line)? If so, then you may need the USE_SETSID change that was implemented to handle cases where passphrase prompting from ssh detects the controlling terminal and prompts for data entry 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-46231) hidden parameter type is not supported by Blue Ocean

2018-08-01 Thread andrew.pia...@nzxt.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Piatek commented on  JENKINS-46231  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: hidden parameter type is not supported by Blue Ocean   
 

  
 
 
 
 

 
 Did this get resolved? Anders, I see your PR is still open.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-40395) Support for file input parameter type

2018-08-01 Thread andrew.pia...@nzxt.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Piatek commented on  JENKINS-40395  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for file input parameter type   
 

  
 
 
 
 

 
 Hi Henry, where was this resolved?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52844) java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps

2018-08-01 Thread alby (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 tang alby created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52844  
 
 
  java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 error_log1.png, error_log2.png, jenkinsfile.png  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-08-02 02:07  
 
 
Environment: 
 jenkins.war 2.134   Pipeline: Declarative 1.3.1  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 tang alby  
 

  
 
 
 
 

 
 It show ellor_log.png when checkout jenkinsfile form scm . Write it directly in the script and won't get an error. Looking forward to answer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

[JIRA] (JENKINS-44197) Support Perforce in Blue Ocean

2018-08-01 Thread jc.imbea...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christian Imbeault commented on  JENKINS-44197  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support Perforce in Blue Ocean   
 

  
 
 
 
 

 
 We upgraded our Jenkins to get Blue Ocean but were disappointed to find out that it did not support Perforce. I'd love for our company to use git but for legacy reason it's just not possible.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-36724) Branch indexing hangs

2018-08-01 Thread olivier.dagen...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Dagenais commented on  JENKINS-36724  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Branch indexing hangs
 

  
 
 
 
 

 
 FYI, posted PR #135: Restore timeouts in BitbucketServerAPIClient, in case it helps the diagnosis of what appears to be a similar issue in the github-branch-source-plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-2734) JUnit reports - setting threshold of failed tests to mark build as stable/unstable/failed

2018-08-01 Thread jh...@gcpud.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Hyry commented on  JENKINS-2734  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JUnit reports - setting threshold of failed tests to mark build as stable/unstable/failed   
 

  
 
 
 
 

 
 I think it is still really important to keep this issue alive. This is a really good feature to have, and people are still thinking about this 10 years after the ticket was created. Are there any plans to add this feature yet?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-49804) Multibranch Helix Branches: support exclusionary mapping?

2018-08-01 Thread jbr...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown commented on  JENKINS-49804  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Helix Branches: support exclusionary mapping?   
 

  
 
 
 
 

 
 Important recommendations is now at https://github.com/jenkinsci/p4-plugin/blob/master/docs/WORKFLOW.md#important-recommendations-1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-32510) SSHD relying on NativePRNG

2018-08-01 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum assigned an issue to Devin Nusbaum  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32510  
 
 
  SSHD relying on NativePRNG   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Assignee: 
 Devin Nusbaum  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-32510) SSHD relying on NativePRNG

2018-08-01 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-32510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSHD relying on NativePRNG   
 

  
 
 
 
 

 
 SSHD's BouncyCastleRandom class only uses the SecureRandom instance to generate an 8-byte seed using SecureRandom#generateSeed for a pure-Java PRNG from BouncyCastle, and the constructed BouncyCastleRandom instance is used as a singleton in SSHD, so that call should only block once. The most likely explanation is that it is using /dev/random, which is blocking occasionally when running tests. We could change the SecureRandom instance to use the NativePRNGNonBlocking provider, which will use /dev/urandom for engineGenerateSeed.  Notably, it looks like SHA1PRNG's generateSeed and nextBytes methods use either /dev/random or /dev/urandom as their source based on the values of java.security.egd and securerandom.source, which we don't want to modify, so SHA1PRNG seems like a bad choice here. We could still use SHA1PRNG's engineNextBytes method, since the seed that it uses to initialize the state is computed statically, and so may already be ready by the time we want to use if if someone else initialized it. Since NativePRNGNonBlocking always uses /dev/urandom, and unlike in JENKINS-20108 we don't care about SHA1PRNG's increased throughput, I think switching to NativePRNGNonBlocking is the best option.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52819) "update/create" events not pushed to evergreen-client

2018-08-01 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy started work on  JENKINS-52819  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-49804) Multibranch Helix Branches: support exclusionary mapping?

2018-08-01 Thread dwhitfi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Doug Whitfield commented on  JENKINS-49804  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Helix Branches: support exclusionary mapping?   
 

  
 
 
 
 

 
 Karl Wirth Dead link on "Important Recommendations  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52823) HP Performance Center Certificate and Integration Errors

2018-08-01 Thread jasonk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Als commented on  JENKINS-52823  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HP Performance Center Certificate and Integration Errors   
 

  
 
 
 
 

 
 Thanks Oleg Nenashev will do  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52843) Push SPRP specific YAML syntax to sub-element

2018-08-01 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52843  
 
 
  Push SPRP specific YAML syntax to sub-element   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Abhishek Gautam  
 
 
Components: 
 simple-pull-request-job-plugin  
 
 
Created: 
 2018-08-01 21:33  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Martin d'Anjou  
 

  
 
 
 
 

 
 In consultation with Andrew Bayer, we determined that the syntax specific to the SPRP plugin should be pushed down to a sub-element of the YAML syntax. This will increase the changes for future compatibility with an official (core) Declarative Pipeline YAML offering. 
 
Link to discussion 
 Code example: 

 

simplePullRequest:
archiveArtifacts: ...
configuration: ...
reports: 
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-52843) Push SPRP specific YAML syntax to sub-element

2018-08-01 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52843  
 
 
  Push SPRP specific YAML syntax to sub-element   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Sprint: 
 GSoC - Coding Phase  3  2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's

2018-08-01 Thread walli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anders Wallin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52804  
 
 
  Jenkins web GUI hangs when using a computer with more then 70 CPU's   
 

  
 
 
 
 

 
Change By: 
 Anders Wallin  
 
 
Attachment: 
 docker_test64.out  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's

2018-08-01 Thread walli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anders Wallin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52804  
 
 
  Jenkins web GUI hangs when using a computer with more then 70 CPU's   
 

  
 
 
 
 

 
Change By: 
 Anders Wallin  
 
 
Attachment: 
 docker_test70.out  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's

2018-08-01 Thread walli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anders Wallin commented on  JENKINS-52804  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins web GUI hangs when using a computer with more then 70 CPU's   
 

  
 
 
 
 

 
 With better logs; I run the following script; $cat docker_test #!/bin/bash set -x : ${TAG:=2.135} : ${MAXCPU:=64} cat data/jul.properties docker rm myjenkins docker run -name myjenkins --cpuset-cpus=0$MAXCPU -p 8080:8080 -p 5:5 --env JAVA_OPTS="-Djava.util.logging.config.file=/var/jenkins_home/jul.properties" -v `pwd`/data:/var/jenkins_home jenkins/jenkins:$TAG $MAXCPU=70 ./docker_test 2>&1 | tee docker_test70.out and when it's started I run "wget localhost:8080" from another shell        
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-49796) git fetch timeout

2018-08-01 Thread snsmirnov1...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergey Smirnov commented on  JENKINS-49796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git fetch timeout
 

  
 
 
 
 

 
 Hi i'm reproduces this bug. When pipeline script running git command 

 

> git fetch --tags --progress ssh://.../project.git +refs/heads/:refs/remotes/origin/
 

 in server console i see   

 

Aug 01, 2018 11:41:43 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn
WARNING: Attempt to (de-)serialize anonymous class com.cloudbees.plugins.credentials.CredentialsScope$2 in file:/.../.jenkins/plugins/credentials/WEB-INF/lib/credentials.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/

Enter passphrase for key '/.../.jenkins/workspace/testJob/Folder@tmp/ssh5372262008927789840.key':
 

 after writing password to server console pipiline runs ok      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-42723) Fix form fields for active choices parameters when triggering builds via the parameterized trigger plugin

2018-08-01 Thread sebastien.bon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastien Bonami commented on  JENKINS-42723  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix form fields for active choices parameters when triggering builds via the parameterized trigger plugin   
 

  
 
 
 
 

 
 Hi, I have the exact same problem. Have you find a solution / workaround Kevin Phillips or Bruno P. Kinoshita?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52842) xUnit plugin blocks PingThread responses

2018-08-01 Thread direct...@apebox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jo Shields created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52842  
 
 
  xUnit plugin blocks PingThread responses   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Nikolas Falco  
 
 
Components: 
 xunit-plugin  
 
 
Created: 
 2018-08-01 19:02  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jo Shields  
 

  
 
 
 
 

 
 If your xUnit parsing takes a long time (don't ask), the entire build agent can be kicked offline, by passing the timeout threshhold on pings (default 4 minutes).     Agent: 12:39:02 [xUnit] [INFO] - [NUnit-2 (default)] - 110 test report file(s) were found with the pattern '*/TestResult.xml' relative to '/home/builder/jenkins/workspace/foo' for the testing framework 'NUnit-2 (default)'. 12:44:28 [xUnit] [ERROR] - The plugin hasn't been performed correctly: Remote call on JNLP4-connect connection from 1.1.1.1/1.1.1.1:1880 failed Server: INFO: Ping failed. Terminating the channel JNLP4-connect connection from 1.1.1.1/1.1.1.1:7468. java.util.concurrent.TimeoutException: Ping started at 1532979041327 hasn't completed by 1532979281327 {{ at hudson.remoting.PingThread.ping(PingThread.java:134)}} {{ at hudson.remoting.PingThread.run(PingThread.java:90)}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
  

[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses

2018-08-01 Thread direct...@apebox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jo Shields updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52842  
 
 
  xUnit plugin blocks PingThread responses   
 

  
 
 
 
 

 
Change By: 
 Jo Shields  
 

  
 
 
 
 

 
 If your xUnit parsing takes a long time (don't ask), the entire build agent can be kicked offline, by passing the timeout threshhold on pings (default 4 minutes).  Agent:{{12:39:02 [xUnit] [INFO] - [NUnit-2 (default)] - 110 test report file(s) were found with the pattern '**/TestResult*.xml' relative to '/home/builder/jenkins/workspace/foo' for the testing framework 'NUnit-2 (default)'.}}{{12:44:28 [xUnit] [ERROR] - The plugin hasn't been performed correctly: Remote call on JNLP4-connect connection from 1.1.1.1/1.1.1.1:1880 failed}}Server:{{INFO: Ping failed. Terminating the channel JNLP4-connect connection from 1.1.1.1/1.1.1.1:7468.}}{{java.util.concurrent.TimeoutException: Ping started at 1532979041327 hasn't completed by 1532979281327}}{{ at hudson.remoting.PingThread.ping(PingThread.java:134)}}{{ at hudson.remoting.PingThread.run(PingThread.java:90)}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52841) RFE: restrict message body output to be JSON

2018-08-01 Thread ktdre...@ktdreyer.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ken Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52841  
 
 
  RFE: restrict message body output to be JSON   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Scott Hebert  
 
 
Components: 
 jms-messaging-plugin  
 
 
Created: 
 2018-08-01 18:22  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ken Dreyer  
 

  
 
 
 
 

 
 Would you consider making the JMS Messaging plugin only publish JSON bodies? Many different clients could consume these messages. Most clients generally assume that the message bodies will be well-formatted JSON. Enforcing this at the Jenkins plugin level will reduce the proliferation of non-JSON messages on the bus.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
  

[JIRA] (JENKINS-38280) M2 release plugin not showing release option

2018-08-01 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 no steps to reproduce.  PLugin has been seen working in CLoudBees Jenkins Enterprise.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38280  
 
 
  M2 release plugin not showing release option   
 

  
 
 
 
 

 
Change By: 
 James Nord  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52468) Change name of variables in Credential.java

2018-08-01 Thread gautam.abhishe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhishek Gautam updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52468  
 
 
  Change name of variables in Credential.java   
 

  
 
 
 
 

 
Change By: 
 Abhishek Gautam  
 

  
 
 
 
 

 
 Maybe it makes sense to reconsider the name. in some cases it is just a variable name prefix.  Support "variablePrefix" and "variable" both.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52491) Detach snippet generator to extensions.

2018-08-01 Thread gautam.abhishe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhishek Gautam updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52491  
 
 
  Detach snippet generator to extensions.   
 

  
 
 
 
 

 
Change By: 
 Abhishek Gautam  
 

  
 
 
 
 

 
 Acceptance Criteria  # Root level configurators ( like agent, configuration, reports, etc) extension points (need for these implementations). # Move sections to extension point implementation (agent, configuration, reports, etc) (need to implement these). # Symbol definition for extension points.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-37575) Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely

2018-08-01 Thread krout...@ea.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Routley commented on  JENKINS-37575  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely   
 

  
 
 
 
 

 
 Sam Van Oort Just want to clarify from comment, fix was made in 1.23 and not 2.23? https://plugins.jenkins.io/durable-task  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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