[JIRA] (JENKINS-50198) node config gets overridden when spinning up node via Ec2 plugin

2018-03-15 Thread daniel.marsh...@argos.co.uk (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Marshall commented on  JENKINS-50198  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: node config gets overridden when spinning up node via Ec2 plugin   
 

  
 
 
 
 

 
 Yes, every job has either the ‘general’ or ‘devops’ label, but because we share this jenkins instance with developers who shouldn’t be able to run on the ‘devops’ node we need to restrict it at the node level.  
 

  
 
 
 
 

 
 
 

 
 
 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-50198) node config gets overridden when spinning up node via Ec2 plugin

2018-03-15 Thread daniel.marsh...@argos.co.uk (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Marshall created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50198  
 
 
  node config gets overridden when spinning up node via Ec2 plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Francis Upton  
 
 
Attachments: 
 image-2018-03-15-17-09-26-148.png  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2018-03-15 17:18  
 
 
Environment: 
 Jenkins v2.73.3  ec2 1.38  job-restrictions 0.6  
 
 
Labels: 
 ec2-plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Dan Marshall  
 

  
 
 
 
 

 
 We have ephemeral nodes created by the EC2 plugin when needed by jobs. Since some jobs require elevated AWS permissions, we have created 2 cloud configurations ('general' and 'devops') with the latter having permissions to carry out actions such as create AMI etc. The problem we are trying to solve is that any of the other users can tell their job to use these nodes. The aim is to restrict the jobs that can be run on this node by using the job restrictions plugin to only allow jobs in a particular directory. The issue we are facing is that there doesn't appear to be a way to easily integrate the EC2 and Job Restrictions plugins with each other such that the necessary config is applied to the node as it is spun up. The workaround is currently an init script (on the node) which utilises jenkins-cli.jar to manipulate the node's config on the master. This works perfectly when the node is spun up manually via the configure nodes page (as seen below), but does not when a trigge