[JIRA] (JENKINS-51459) Define a way to test incompatible configurations as code in essentials

2018-09-28 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51459  
 
 
  Define a way to test incompatible configurations as code in essentials   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Labels: 
 essentials  evergreen  
 

  
 
 
 
 

 
 
 

 
 
 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-51459) Define a way to test incompatible configurations as code in essentials

2018-09-28 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51459  
 
 
  Define a way to test incompatible configurations as code in essentials   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Labels: 
 essentials  evergreen  
 

  
 
 
 
 

 
 
 

 
 
 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-51459) Define a way to test incompatible configurations as code in essentials

2018-09-24 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51459  
 
 
  Define a way to test incompatible configurations as code in essentials   
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Sprint: 
 Evergreen - Milestone 1 , Evergreen - Milestone 2  
 

  
 
 
 
 

 
 
 

 
 
 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-51459) Define a way to test incompatible configurations as code in essentials

2018-05-21 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51459  
 
 
  Define a way to test incompatible configurations as code in essentials   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Raul Arabaolaza  
 
 
Components: 
 essentials  
 
 
Created: 
 2018-05-21 15:27  
 
 
Labels: 
 essentials  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Raul Arabaolaza  
 

  
 
 
 
 

 
 We need to define how does Evergreen plan to approach the compatibility concerns of the Configuration-as-Code engine.  Currently, it does not guarantee YAML compatibility when switching between LTS baselines E.g. 2.60.x config for agents will fail to load in 2.73+ If Evergreen plans to let users set their configs for Essentials, then the instance may go south once Essentials picks a new baseline.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment