[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option

2018-11-14 Thread duanshiqia...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shiqiang Duan commented on  JENKINS-48556  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: timestamps() randomly not recognized as a valid option   
 

  
 
 
 
 

 
 1.3.3 is still unreleased and all our pipeline build is failing after upgrading to 1.3.2. How come this issue can be marked as resolved?!  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option

2018-11-14 Thread duanshiqia...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shiqiang Duan reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48556  
 
 
  timestamps() randomly not recognized as a valid option   
 

  
 
 
 
 

 
Change By: 
 Shiqiang Duan  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50472) Doesn't work with AWS Beijing Region (cn-north-1)

2018-03-28 Thread duanshiqia...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shiqiang Duan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50472  
 
 
  Doesn't work with AWS Beijing Region (cn-north-1)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Francis Upton  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2018-03-29 02:25  
 
 
Environment: 
 Amazon EC2 plugin version: 1.39  Jenkins version: 2.107.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Shiqiang Duan  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 
  

[JIRA] (JENKINS-50310) Support stop GCE instance instead of Termination

2018-03-28 Thread duanshiqia...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shiqiang Duan commented on  JENKINS-50310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support stop GCE instance instead of Termination   
 

  
 
 
 
 

 
 Any update on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50310) Support stop GCE instance instead of Termination

2018-03-21 Thread duanshiqia...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shiqiang Duan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50310  
 
 
  Support stop GCE instance instead of Termination   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Evan Brown  
 
 
Components: 
 google-compute-engine-plugin  
 
 
Created: 
 2018-03-21 07:33  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Shiqiang Duan  
 

  
 
 
 
 

 
 Currently the google-compute-engine-plugin creates jenkins node and terminates them if idle. Instead of terminate, it's better to support stop the instance when idle. Amazon EC2 Plugin supports this and we build our main CI farm using EC2 slaves.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment