[JIRA] (JENKINS-38942) Stopped EC2 agents not waking up if the number of stopped EC2 agents equals the global Instance Cap

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38942  
 
 
  Stopped EC2 agents not waking up if the number of stopped EC2 agents equals the global Instance Cap   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 1.44.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175358.1476309458000.670.1565468580873%40Atlassian.JIRA.


[JIRA] (JENKINS-23864) Environment variables are not set in init script

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-23864  
 
 
  Environment variables are not set in init script   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Issue Type: 
 Bug New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156328.1405652221000.664.1565468460585%40Atlassian.JIRA.


[JIRA] (JENKINS-31323) When testing connection, "problem creating RSA private key" exception is raised

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31323  
 
 
  When testing connection, "problem creating RSA private key" exception is raised   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166111.1446250902000.661.1565468400488%40Atlassian.JIRA.


[JIRA] (JENKINS-53928) ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04)

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53928  
 
 
  ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04)   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194527.1538762383000.653.1565468280399%40Atlassian.JIRA.


[JIRA] (JENKINS-55158) Hanging builds after completion after update from 1.40.1 to 1.41

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Reduced pressure on the queue that slow down the finalize process of the job  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55158  
 
 
  Hanging builds after completion after update from 1.40.1 to 1.41   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 1.45  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

[JIRA] (JENKINS-55158) Hanging builds after completion after update from 1.40.1 to 1.41

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-55158  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196225.1544637239000.645.1565468160261%40Atlassian.JIRA.


[JIRA] (JENKINS-54232) Jenkins worker unable to start SPOT instance.

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54232  
 
 
  Jenkins worker unable to start SPOT instance.   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194873.1540418478000.643.1565468101348%40Atlassian.JIRA.


[JIRA] (JENKINS-54232) Jenkins worker unable to start SPOT instance.

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-54232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins worker unable to start SPOT instance.   
 

  
 
 
 
 

 
 Should be fixed in the 1.45  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194873.1540418478000.632.1565468101185%40Atlassian.JIRA.


[JIRA] (JENKINS-54329) Jenkins Does Not Use Private IP Address by Default For VPC+PublicIP Slaves

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-54329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Does Not Use Private IP Address by Default For VPC+PublicIP Slaves   
 

  
 
 
 
 

 
 Some fix has been release in the 1.44 and last patch will be in the 1.46: https://github.com/jenkinsci/ec2-plugin/pull/387  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194982.1540871819000.619.1565468040297%40Atlassian.JIRA.


[JIRA] (JENKINS-55108) Ec2-stuck while provisioning new spot instances

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55108  
 
 
  Ec2-stuck while provisioning new spot instances   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 1.45  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196169.1544459151000.621.1565468040329%40Atlassian.JIRA.


[JIRA] (JENKINS-55483) ec2-plugin Wrong order of workers termination

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55483  
 
 
  ec2-plugin Wrong order of workers termination   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 1.45  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196613.1547045034000.615.1565467920666%40Atlassian.JIRA.


[JIRA] (JENKINS-55625) ec2 agent launching broken in 1.42

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-55625  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196798.1547654869000.608.1565467860745%40Atlassian.JIRA.


[JIRA] (JENKINS-55625) ec2 agent launching broken in 1.42

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55625  
 
 
  ec2 agent launching broken in 1.42   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196798.1547654869000.610.1565467860773%40Atlassian.JIRA.


[JIRA] (JENKINS-56435) Spot instance requests use entirely different instance

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56435  
 
 
  Spot instance requests use entirely different instance   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 1.45  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198030.1551870002000.598.1565467681389%40Atlassian.JIRA.


[JIRA] (JENKINS-56435) Spot instance requests use entirely different instance

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-56435  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198030.1551870002000.596.1565467681367%40Atlassian.JIRA.


[JIRA] (JENKINS-56435) Spot instance requests use entirely different instance

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-56435  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Spot instance requests use entirely different instance   
 

  
 
 
 
 

 
 Some fix has been introduced in the 1.45 for the spot instace ID  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198030.1551870002000.589.1565467681163%40Atlassian.JIRA.


[JIRA] (JENKINS-56782) EBS encryption support

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-56782  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EBS encryption support   
 

  
 
 
 
 

 
 Per the documentation, "If you are creating a volume from a snapshot, you can't specify an encryption value. This is because only blank volumes can be encrypted on creation. "   That means the volume has been encrypted before creation for the root, for additional disk, different story  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198427.1553701734000.581.1565467620132%40Atlassian.JIRA.


[JIRA] (JENKINS-55473) ec2-cloud provision getting error

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-55473  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ec2-cloud provision getting error   
 

  
 
 
 
 

 
 Has been solved in the  1.44.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196602.1547030898000.565.1565467279078%40Atlassian.JIRA.


[JIRA] (JENKINS-55473) ec2-cloud provision getting error

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55473  
 
 
  ec2-cloud provision getting error   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196602.1547030898000.575.1565467320394%40Atlassian.JIRA.


[JIRA] (JENKINS-55473) ec2-cloud provision getting error

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-55473  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196602.1547030898000.573.1565467279295%40Atlassian.JIRA.


[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55618  
 
 
  When using spot instances, requests 3-4 nodes when one is needed   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Issue Type: 
 Bug New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196789.1547639731000.559.1565467202079%40Atlassian.JIRA.


[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-56927  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Request: EC2 plugin should use SSH keys via credentials plugin   
 

  
 
 
 
 

 
 With the new release the private key is no longer visible. For the integration with secret manager i don't have an ETA  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198606.1554663571000.539.1565467080131%40Atlassian.JIRA.


[JIRA] (JENKINS-57731) Enable to register aws ec2 slave

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-57731  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Enable to register aws ec2 slave   
 

  
 
 
 
 

 
 I never tested Jenkins master on windows machine. I am checking, probably there are more the one things not working on windows.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199674.1559111787000.537.1565466960108%40Atlassian.JIRA.


[JIRA] (JENKINS-57392) AWS API timeout

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-57392  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AWS API timeout   
 

  
 
 
 
 

 
 I believe we can pass as global var on the startup of jenkins   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199174.1557437303000.535.1565466840118%40Atlassian.JIRA.


[JIRA] (JENKINS-58573) 100% CPU remoting.jar or slave.jar on EC2 (connection refused)

2019-08-10 Thread gun...@grodotzki.co.za (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gunter Grodotzki commented on  JENKINS-58573  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 100% CPU remoting.jar or slave.jar on EC2 (connection refused)   
 

  
 
 
 
 

 
 If you can give me documentation on how to do this that would be great    I am running master off docker jenkins/jenkins:lts-slim - but I am guessing the CPU issues with master are only a symptom. I haven't tried it with something non EC2. But given that the issue is on Ubuntu + Debian AMIs its probably not EC2.   It would be really great if remoting.jar could have better support for newrelic so I can see 100% on what is consuming 100% cpu. Will be super easy to figure out whats going on. Right now there is no helpful data.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200725.1563549166000.530.1565466780316%40Atlassian.JIRA.


[JIRA] (JENKINS-58155) Quicker slave start-up

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-58155  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Quicker slave start-up   
 

  
 
 
 
 

 
 With the structure that we have we are not able to reduce the startup time, already we start parallel node base on the queue size. More operation will result in a deadlock of the queue.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200203.1561310632000.525.1565466720364%40Atlassian.JIRA.


[JIRA] (JENKINS-58155) Quicker slave start-up

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58155  
 
 
  Quicker slave start-up   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200203.1561310632000.527.1565466720390%40Atlassian.JIRA.


[JIRA] (JENKINS-58155) Quicker slave start-up

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-58155  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200203.1561310632000.521.156540244%40Atlassian.JIRA.


[JIRA] (JENKINS-57756) Unable to save config: No enum constant hudson.plugins.ec2.ConnectionStrategy.Private IP

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-57756  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199701.1559163338000.517.1565466541881%40Atlassian.JIRA.


[JIRA] (JENKINS-56066) EC2 nodes fail to start after jenkins restart

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56066  
 
 
  EC2 nodes fail to start after jenkins restart   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197490.1549713993000.515.1565466541818%40Atlassian.JIRA.


[JIRA] (JENKINS-57756) Unable to save config: No enum constant hudson.plugins.ec2.ConnectionStrategy.Private IP

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57756  
 
 
  Unable to save config: No enum constant hudson.plugins.ec2.ConnectionStrategy.Private IP   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199701.1559163338000.519.1565466542056%40Atlassian.JIRA.


[JIRA] (JENKINS-56066) EC2 nodes fail to start after jenkins restart

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-56066  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197490.1549713993000.507.1565466541629%40Atlassian.JIRA.


[JIRA] (JENKINS-58578) Public IP can still be assigned when Associate Public IP is disabled, depending on subnet(s)

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-58578  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200731.1563593184000.496.1565465880323%40Atlassian.JIRA.


[JIRA] (JENKINS-58578) Public IP can still be assigned when Associate Public IP is disabled, depending on subnet(s)

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-58578  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Public IP can still be assigned when Associate Public IP is disabled, depending on subnet(s)   
 

  
 
 
 
 

 
 You are right we don't force tho disable the ip in case of false, that results in the behavior that you have seen in case the public subnet. Patch created : https://github.com/jenkinsci/ec2-plugin/pull/387      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200731.1563593184000.494.1565465880294%40Atlassian.JIRA.


[JIRA] (JENKINS-58576) How do I setup a delay before new instances are launched?

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58576  
 
 
  How do I setup a delay before new instances are launched?   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Issue Type: 
 Task New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200729.1563561199000.491.1565464800249%40Atlassian.JIRA.


[JIRA] (JENKINS-58573) 100% CPU remoting.jar or slave.jar on EC2 (connection refused)

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-58573  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 100% CPU remoting.jar or slave.jar on EC2 (connection refused)   
 

  
 
 
 
 

 
 can you dump make a flight recording ? or a memdump of the master to check in the status of the master?  Are the Master and slave  with the same jdk ?  Is it happen only with ec2 ?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200725.1563549166000.486.1565464740215%40Atlassian.JIRA.


[JIRA] (JENKINS-58651) Add the ability to support M5.metal instance type

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58651  
 
 
  Add the ability to support M5.metal instance type   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200924.1564001508000.483.1565464380624%40Atlassian.JIRA.


[JIRA] (JENKINS-58788) EC2 Plugin throwing NullPointer exception when connecting to Windows agent.

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-58788  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Plugin throwing NullPointer exception when connecting to Windows agent.   
 

  
 
 
 
 

 
 It should be fixed in the 1.45, the problem is related to the working dir calculation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201098.1564760186000.478.1565464380537%40Atlassian.JIRA.


[JIRA] (JENKINS-58651) Add the ability to support M5.metal instance type

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-58651  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200924.1564001508000.481.1565464380593%40Atlassian.JIRA.


[JIRA] (JENKINS-58788) EC2 Plugin throwing NullPointer exception when connecting to Windows agent.

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-58788  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201098.1564760186000.476.1565464320271%40Atlassian.JIRA.


[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-57795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Orphaned EC2 instances after Jenkins restart   
 

  
 
 
 
 

 
 Can you test the 1.45 ?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.474.1565464320251%40Atlassian.JIRA.


[JIRA] (JENKINS-58856) No Authorization Header for WinRM connection

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-58856  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No Authorization Header for WinRM connection   
 

  
 
 
 
 

 
 If you are using the generated admin password from AWS, it is supported only from the 1.45, pay attention that you have to update the IAM role. If the password is pre define in the ami, I need to debug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201171.1565246564000.471.1565464080097%40Atlassian.JIRA.


[JIRA] (JENKINS-58879) EC2 plugin queue locks have resurfaced

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-58879  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 plugin queue locks have resurfaced   
 

  
 
 
 
 

 
 Some  improvement has been released in the 1.45 to reduce the query and the locking of the queue, can you test ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201212.1565377068000.467.1565463840267%40Atlassian.JIRA.


[JIRA] (JENKINS-58879) EC2 plugin queue locks have resurfaced

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI updated  JENKINS-58879  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58879  
 
 
  EC2 plugin queue locks have resurfaced   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201212.1565377068000.469.1565463840323%40Atlassian.JIRA.


[JIRA] (JENKINS-58879) EC2 plugin queue locks have resurfaced

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-58879  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201212.1565377068000.465.1565463781386%40Atlassian.JIRA.


[JIRA] (JENKINS-53952) Linux slaves are not starting anymore

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI edited a comment on  JENKINS-53952  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux slaves are not starting anymore   
 

  
 
 
 
 

 
 merged in the 1.45 , can you confirm that is fixed ?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194555.1539041035000.463.1565463781329%40Atlassian.JIRA.


[JIRA] (JENKINS-53952) Linux slaves are not starting anymore

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-53952  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux slaves are not starting anymore   
 

  
 
 
 
 

 
 merged in the 1.45  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194555.1539041035000.425.1565463721772%40Atlassian.JIRA.


[JIRA] (JENKINS-53952) Linux slaves are not starting anymore

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-53952  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194555.1539041035000.427.1565463721794%40Atlassian.JIRA.


[JIRA] (JENKINS-57215) Plugin starts a worked and might immediately stop it, because of cached EC2Computer.getUptime()

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in the 1.45  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57215  
 
 
  Plugin starts a worked and might immediately stop it, because of cached EC2Computer.getUptime()   
 

  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 1.45  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198972.1556526924000.403.1565463660942%40Atlassian.JIRA.


[JIRA] (JENKINS-57215) Plugin starts a worked and might immediately stop it, because of cached EC2Computer.getUptime()

2019-08-10 Thread fabrizio.manfr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-57215  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198972.1556526924000.401.1565463660872%40Atlassian.JIRA.


[JIRA] (JENKINS-58882) Update plugin dependencies

2019-08-10 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58882  
 
 
  Update plugin dependencies   
 

  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 

  
 
 
 
 

 
 The workflow-aggregator plugin appears to depend on many of Update  the  plugins that we do  dependencies for this project .  See if we can replace the workflow-* plugins with the aggregator. Acceptance criteria:#  The POM is rationalised as above  Dependencies are reordered .  Jenkins at the top.# Dependencies are bumped where possible.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201215.1565452904000.396.1565454300069%40Atlassian.JIRA.


[JIRA] (JENKINS-58882) Depend on workflow-aggregator plugin

2019-08-10 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan commented on  JENKINS-58882  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Depend on workflow-aggregator plugin   
 

  
 
 
 
 

 
 sigh  Jenkins documentation is wrong / out of date / misleading. Since I originally reviewed this testing page there has been a change to the guidance brought about by this change. See further discussion here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201215.1565452904000.393.1565454180112%40Atlassian.JIRA.


[JIRA] (JENKINS-58882) Update plugin dependencies

2019-08-10 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan commented on  JENKINS-58882  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update plugin dependencies   
 

  
 
 
 
 

 
 Instead we'll update the plugin dependencies in this change  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201215.1565452904000.395.1565454180167%40Atlassian.JIRA.


[JIRA] (JENKINS-58882) Update plugin dependencies

2019-08-10 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58882  
 
 
  Update plugin dependencies   
 

  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 
 
Summary: 
 Depend on workflow-aggregator Update  plugin  dependencies  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201215.1565452904000.394.1565454180151%40Atlassian.JIRA.


[JIRA] (JENKINS-53800) Whitelisting misc. methods

2019-08-10 Thread harid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara commented on  JENKINS-53800  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Whitelisting misc. methods   
 

  
 
 
 
 

 
 I guess I just couldn't figure out how to do it, thanks for pointing it out. However, how would I know what to enter for "Released As"?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194313.1537981345000.390.1565454060133%40Atlassian.JIRA.


[JIRA] (JENKINS-58883) Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin

2019-08-10 Thread abhishek_agrah...@mentor.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 abhishek Agrahari created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58883  
 
 
  Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Wisen Tanasa  
 
 
Attachments: 
 Jira_Trigger_Issue.JPG  
 
 
Components: 
 jira-trigger-plugin  
 
 
Created: 
 2019-08-10 16:14  
 
 
Environment: 
 Hi .   I have installed the JIRA Plugins as "JIRA trigger plugins", " Jira issue updater", And " Jira integration for Jenkin"    Few weeks earlier , While I was making any status change in the JIRA issue, it was triggering the build in Jenkin and parallely i could see the update in the "comment" in JIRA.   but from few days , while having a status change of bug in JIRA , it does not allow to trigger the build in Jenkin and also there is no comment update in JIRA. but other options , like activity, user statistics , history get updated.   during this execution i am facing licensing issue.  "TESTAA-1 test_jenkin - 2019-08-10  The license key is expired or invalid. Click here if you are Jira administrator.Digest generated on Aug 10 at 8:14 AM  Configure Powered by Email Notifications Digest add-on for Jira"   Please help me   i am using jenkin : 2.89.2  Test JIRA server : 7.13.0   Regards  Abhishek   
 
 
Priority: 
  Major  
 
 
Reporter: 
 abhishek Agrahari  
 

  
 
 
 
 

 
 
 

 
 
 

[JIRA] (JENKINS-58882) Depend on workflow-aggregator plugin

2019-08-10 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan started work on  JENKINS-58882  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201215.1565452904000.386.1565453040089%40Atlassian.JIRA.


[JIRA] (JENKINS-58882) Depend on workflow-aggregator plugin

2019-08-10 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58882  
 
 
  Depend on workflow-aggregator plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Mez Pahlan  
 
 
Components: 
 appcenter-plugin  
 
 
Created: 
 2019-08-10 16:01  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mez Pahlan  
 

  
 
 
 
 

 
 The workflow-aggregator plugin appears to depend on many of the plugins that we do. See if we can replace the workflow-* plugins with the aggregator. Acceptance criteria: 
 
The POM is rationalised as above. 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
  

[JIRA] (JENKINS-58650) Support proxy for App Center uploads

2019-08-10 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58650  
 
 
  Support proxy for App Center uploads   
 

  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 
 
Released As: 
 0 .3.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200923.156451000.384.1565451660157%40Atlassian.JIRA.


[JIRA] (JENKINS-58650) Support proxy for App Center uploads

2019-08-10 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan updated  JENKINS-58650  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58650  
 
 
  Support proxy for App Center uploads   
 

  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200923.156451000.382.1565451600231%40Atlassian.JIRA.


[JIRA] (JENKINS-58339) Support new types of credentials

2019-08-10 Thread chris+jenk...@chriskilding.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Kilding started work on  JENKINS-58339  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Chris Kilding  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.377.1565449680350%40Atlassian.JIRA.


[JIRA] (JENKINS-58339) Support new types of credentials

2019-08-10 Thread chris+jenk...@chriskilding.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Kilding assigned an issue to Chris Kilding  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58339  
 
 
  Support new types of credentials   
 

  
 
 
 
 

 
Change By: 
 Chris Kilding  
 
 
Assignee: 
 Enrique Fernández-Polo Chris Kilding  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.379.1565449680408%40Atlassian.JIRA.


[JIRA] (JENKINS-46204) Github oauth cli delete-builds broken

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske closed an issue as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 User didn't report back and my own testing of using GitHub OAuth with Jenkins CLI seems fine.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-46204  
 
 
  Github oauth cli delete-builds broken   
 

  
 
 
 
 

 
Change By: 
 Sam Gleske  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184447.1502799432000.374.1565448480280%40Atlassian.JIRA.


[JIRA] (JENKINS-47950) 0.28.1 update breaks GHE auth - javax.net.ssl.SSLHandshakeException

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I'm not able to reproduce the issue. If you can, provide exact steps to reproduce from scratch so that I can help determine if there's an issue in the plugin.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47950  
 
 
  0.28.1 update breaks GHE auth - javax.net.ssl.SSLHandshakeException   
 

  
 
 
 
 

 
Change By: 
 Sam Gleske  
 
 
Status: 
 Reopened Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186479.1510404865000.372.1565448240195%40Atlassian.JIRA.


[JIRA] (JENKINS-47950) 0.28.1 update breaks GHE auth - javax.net.ssl.SSLHandshakeException

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske commented on  JENKINS-47950  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 0.28.1 update breaks GHE auth - javax.net.ssl.SSLHandshakeException   
 

  
 
 
 
 

 
 This is an SSL certificates issue and not something specific to the GitHub OAuth plugin. I have SSL in my own production setups of Jenkins. I'm not able to reproduce this issue myself.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186479.1510404865000.370.1565448180103%40Atlassian.JIRA.


[JIRA] (JENKINS-52099) jenkins-cli requires Overall/Read permission on anonymous user

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing as can't reproduce. If you give me steps to reproduce the issue I can look into it further. Feel free to re-open if you give reproduction steps.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52099  
 
 
  jenkins-cli requires Overall/Read permission on anonymous user   
 

  
 
 
 
 

 
Change By: 
 Sam Gleske  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191695.1529575282000.365.1565448060522%40Atlassian.JIRA.


[JIRA] (JENKINS-52099) jenkins-cli requires Overall/Read permission on anonymous user

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske commented on  JENKINS-52099  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jenkins-cli requires Overall/Read permission on anonymous user   
 

  
 
 
 
 

 
 I can't reproduce this issue. GitHub personal access tokens work in all tests I perform with Jenkins CLI. In all of my testing platforms Anonymous Read access is always revoked so I've tested this scenario several times without issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191695.1529575282000.360.1565448000217%40Atlassian.JIRA.


[JIRA] (JENKINS-52528) Update github-api plugin from 1.77 to 1.93

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske commented on  JENKINS-52528  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update github-api plugin from 1.77 to 1.93   
 

  
 
 
 
 

 
 Plugins reference older versions of plugins as being "compatible since". This plugin is compatible with the latest release of the github-api plugin. Is there something specific in a newer version of the plugin that you need surfaced here? Bear in mind github-api is a backend plugin and not really reflected in the frontend where users interact.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192362.153142827.358.1565447880105%40Atlassian.JIRA.


[JIRA] (JENKINS-52956) GitHub Commiter Authorization Strategy - allow users with WRITE to stop builds

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Work done to resolve this issue should be tracked in JENKINS-27844 with a better, more generic rewrite of how permissions in GitHub OAuth are handled.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52956  
 
 
  GitHub Commiter Authorization Strategy - allow users with WRITE to stop builds   
 

  
 
 
 
 

 
Change By: 
 Sam Gleske  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192934.153380777.355.1565447760334%40Atlassian.JIRA.


[JIRA] (JENKINS-53364) github-oauth-plugin -Simpler 403 page

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53364  
 
 
  github-oauth-plugin -Simpler 403 page   
 

  
 
 
 
 

 
Change By: 
 Sam Gleske  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193450.1535710636000.352.1565447640508%40Atlassian.JIRA.


[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Since I'm not able to reproduce the issue on 0.32 (originally reported) and 0.33 (recently released) version of the plugin I'm going to close this. However, if you can provide reproduction steps I'll look into it further.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57143  
 
 
  JNLP4 error: "Connection closed before acknowledgement sent"   
 

  
 
 
 
 

 
Change By: 
 Sam Gleske  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 Sam Gleske  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you 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-58479) Failing to retrieve teams

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske commented on  JENKINS-58479  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failing to retrieve teams   
 

  
 
 
 
 

 
 Kote Mushegiani I also forgot to mention that you need to upgrade to github-outh 0.33 because plugin version 0.32 suffers from a critical bug in matrix auth. See JENKINS-57154 for details  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200615.1562956253000.345.1565446920156%40Atlassian.JIRA.


[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske commented on  JENKINS-57154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page   
 

  
 
 
 
 

 
 Jon Cormier Steve Ims no problem; thanks for reporting back your own testing results since it helps me validate the solution was a fix.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.308.1565446801015%40Atlassian.JIRA.


[JIRA] (JENKINS-58479) Failing to retrieve teams

2019-08-10 Thread sam.mxra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Gleske commented on  JENKINS-58479  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failing to retrieve teams   
 

  
 
 
 
 

 
 Kote Mushegiani if you visit https://[you Jenkins instance]/whoAmI all known authorities for your user will be there. If the name you have in matrix auth does not match the name in granted authorities then users will not have access. Find a user who's in the Engineering GitHub team and see what authorities they have granted. I can't reproduce this issue myself. Juha Tiensyrjä can you describe in more detail what, specifically, stopped working? There were definite issues with the 0.32 version of the plugin that were fixed in 0.33. However, the fix was only to backend code on the globalSecurity page and should not have made a difference your configuration itself. Without more detail and steps to reproduce I don't know how else to approach this issue. It passes all of my local testing when trying to reproduce what this issue describes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200615.1562956253000.305.1565446620178%40Atlassian.JIRA.


[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job

2019-08-10 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-58860  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Skipped parameter which is defined in a job   
 

  
 
 
 
 

 
 Which version of Jenkins were you running before? When you add a shell/batch build step to the downstream job, and have it output the value of the artifactVersion environment variable ( echo "$artifactVersion" or echo %artifactVersion% respectively), what happens?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201175.1565270296000.302.1565438820264%40Atlassian.JIRA.


[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job

2019-08-10 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58860  
 
 
  Skipped parameter which is defined in a job   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201175.1565270296000.299.1565438700269%40Atlassian.JIRA.


[JIRA] (JENKINS-54154) [Custom Tools Plugin] - JCasC compatibility

2019-08-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [Custom Tools Plugin] - JCasC compatibility   
 

  
 
 
 
 

 
 René Scheibe it would be better to create a new issue for that so that we can add the compatibility incrementally  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194783.1539929296000.297.1565432700147%40Atlassian.JIRA.


[JIRA] (JENKINS-54154) [Custom Tools Plugin] - JCasC compatibility

2019-08-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe edited a comment on  JENKINS-54154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [Custom Tools Plugin] - JCasC compatibility   
 

  
 
 
 
 

 
 With Jenkins 2.176.2, custom-tools-plugin 0.6, configuration-as-code 1.27 installed and a configured custom tool with only "Name = tool1" set, the following stacktrace is shown :  when exporting the configuration. {code:java}tool:  customTool:installations: |-  FAILED TO EXPORT  com.cloudbees.jenkins.plugins.customtools.CustomTool$DescriptorImpl#installations: java.lang.IllegalArgumentException: argument type mismatchat sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)at java.lang.reflect.Constructor.newInstance(Constructor.java:423)at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:300)at io.jenkins.plugins.casc.Attribute._describe(Attribute.java:260)at io.jenkins.plugins.casc.Attribute.describe(Attribute.java:235)at io.jenkins.plugins.casc.Configurator.describe(Configurator.java:161)at io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.java:106)at io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.lambda$describe$3(GlobalConfigurationCategoryConfigurator.java:99)at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)at java.util.Iterator.forEachRemaining(Iterator.java:116)at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)at io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.java:99)at io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.jav{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[JIRA] (JENKINS-54154) [Custom Tools Plugin] - JCasC compatibility

2019-08-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 With Jenkins 2.176.2, custom-tools-plugin 0.6, configuration-as-code 1.27 installed and a configured custom tool with only "Name = tool1" set, the following stacktrace is shown: 

 

tool:
  customTool:
installations: |-
  FAILED TO EXPORT
  com.cloudbees.jenkins.plugins.customtools.CustomTool$DescriptorImpl#installations: java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:300)
at io.jenkins.plugins.casc.Attribute._describe(Attribute.java:260)
at io.jenkins.plugins.casc.Attribute.describe(Attribute.java:235)
at io.jenkins.plugins.casc.Configurator.describe(Configurator.java:161)
at io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.java:106)
at io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.lambda$describe$3(GlobalConfigurationCategoryConfigurator.java:99)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.java:99)
at io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.jav
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54154  
 
 
  [Custom Tools Plugin] - JCasC compatibility   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 

[JIRA] (JENKINS-32662) Extended Choice Parameter Plugin Incompatibility

2019-08-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32662  
 
 
  Extended Choice Parameter Plugin Incompatibility   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 stalled-pr  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167814.1453941961000.287.1565431140439%40Atlassian.JIRA.


[JIRA] (JENKINS-18771) Add descriptions for custom tools

2019-08-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated  JENKINS-18771  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-18771  
 
 
  Add descriptions for custom tools   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Status: 
 Reopened Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150121.1373981439000.278.1565430960846%40Atlassian.JIRA.


[JIRA] (JENKINS-32662) Extended Choice Parameter Plugin Incompatibility

2019-08-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe stopped work on  JENKINS-32662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167814.1453941961000.281.1565430960885%40Atlassian.JIRA.


[JIRA] (JENKINS-26683) Get rid of dependency on Extended Choice Parameter plugin

2019-08-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe stopped work on  JENKINS-26683  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160356.1422526297000.271.1565430900296%40Atlassian.JIRA.


[JIRA] (JENKINS-52785) Multi Architecture Docker image

2019-08-10 Thread imdurga...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Durgadas Kamath commented on  JENKINS-52785  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multi Architecture Docker image
 

  
 
 
 
 

 
 Alex Earl yup, this is great. Next milestone would be when it really makes it into jenkins/jenkins instead of jenkins4eval.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192700.1532781509000.269.1565427720188%40Atlassian.JIRA.


[JIRA] (JENKINS-58881) Support Java 11

2019-08-10 Thread marco.stef...@gmx.at (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marco Steffan stopped work on  JENKINS-58881  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Marco Steffan  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201214.1565425821000.261.1565427000619%40Atlassian.JIRA.


[JIRA] (JENKINS-58881) Support Java 11

2019-08-10 Thread marco.stef...@gmx.at (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marco Steffan started work on  JENKINS-58881  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Marco Steffan  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201214.1565425821000.263.1565427000644%40Atlassian.JIRA.


[JIRA] (JENKINS-58881) Support Java 11

2019-08-10 Thread marco.stef...@gmx.at (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marco Steffan started work on  JENKINS-58881  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Marco Steffan  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201214.1565425821000.259.1565427000592%40Atlassian.JIRA.


[JIRA] (JENKINS-58881) Support Java 11

2019-08-10 Thread marco.stef...@gmx.at (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marco Steffan updated  JENKINS-58881  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58881  
 
 
  Support Java 11   
 

  
 
 
 
 

 
Change By: 
 Marco Steffan  
 
 
Status: 
 In Progress Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201214.1565425821000.265.1565427000667%40Atlassian.JIRA.


[JIRA] (JENKINS-58881) Support Java 11

2019-08-10 Thread marco.stef...@gmx.at (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marco Steffan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58881  
 
 
  Support Java 11   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Marco Steffan  
 
 
Components: 
 cppcheck-plugin  
 
 
Created: 
 2019-08-10 08:30  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marco Steffan  
 

  
 
 
 
 

 
 Support for Java 11  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this 

[JIRA] (JENKINS-58659) ZipExtractionInstaller should ignore timestamp if URL changes

2019-08-10 Thread and...@hammar.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anders Hammar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58659  
 
 
  ZipExtractionInstaller should ignore timestamp if URL changes   
 

  
 
 
 
 

 
Change By: 
 Anders Hammar  
 
 
Component/s: 
 core  
 
 
Component/s: 
 customtools-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200940.1564060967000.255.1565418840131%40Atlassian.JIRA.