-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use :latest task definition instead of registering a new one every time. #263
Comments
For those who come across this in the future, the following log lines are most relevant to determine why a task definition is being created
In my deployment the Match on network was always false when I utilized "default" for the "Network mode" (this is for a Fargate deployment) Looking at amazon-ecs-plugin/src/main/java/com/cloudbees/jenkins/plugins/amazonecs/ECSService.java Line 281 in a3cffcb
Setting the "Network mode" to the appropriate network type instead of default solved the issue in my deployment. This may or may not be the cause for the OP. |
Same issue. The task definition is created every time for each job though there is no change in the definition.
|
I notice two other cases where the matching fails, falsely:
|
Actually, checking the code, the second of the above cases isn't actually effective, because although the tags are checked and difference (incorrectly) reported, no further reference to that difference is made in the code afterwards. ( |
Hey, we have created aws/aws-sdk-java#3043 for it and also opened a support case with AWS. First saw https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html "Revisions per task definition family: 1,000,000" and thought....Pff...And then
Oh... 😄 (or 😱 - depends)... BR |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
OS: Linux - 4.14.275-207.503.amzn2.x86_64
Reproduction steps
Expected Results
Plugin reuse the same task definition on ECS
Actual Results
The plugin creates one task definition per Job, which starts to increase the number of task definitions for the aws account. Currently we have thousands of revisions of the same task definition.
Anything else?
We tried Task Definition Override option but it seems to work for that purpose but Jobs don't run in parallel. Is there another way?
The text was updated successfully, but these errors were encountered: