search

aws-games / cloud-game-development-toolkit

A collection of infrastructure as code templates and configurations for deploying game development infrastructure on AWS
https://aws-games.github.io/cloud-game-development-toolkit/
MIT No Attribution
39 stars 8 forks source link

Feature request: Jenkins on ECS - agent deployments #15

Open henrykie opened 6 months ago

henrykie commented 6 months ago

Use case

Currently the Jenkins module provisions ASGs for use with the EC2 Fleet plugin. This requires agents to be manually configured by the end user. If I have jobs that do not require full EC2 instances I should be able to run my pipelines immediately using tasked agents on the same cluster. For example, I am unable to run AWS CLI commands in my pipelines because the Jenkins coordinator does not have the CLI installed. Further, doing these operations on the built-in node is not a best practice.

Solution/User Experience

Users should be able to specify their own agent containers that will be deployed alongside Jenkins. Users should be able to set flags to deploy certain best-practice containers (AWS CLI for example) automatically.

Alternative solutions

We could also add the AWS CLI to the Jenkins orchestration server, but this would not be a best-practice (running job steps on the built-in node).
kylesomers commented 3 weeks ago

Users should be able to specify their own agent containers that will be deployed alongside Jenkins. Users should be able to set flags to deploy certain best-practice containers (AWS CLI for example) automatically.

How were you thinking of addressing this? There's the amazon-ecs Jenkins plugin that could be configured by exposing new configuration in the module that enables the plugin as part of the module.