I finally used Packer to build an AMI based on Amazon Linux 2 to act as as agent. Yesterday, the builds began failing with a Java stack trace.
Turns out the EC2 instance starts, and in parallel the Jenkins agent begins and an auto-upgrade of openjdk kicked off. Further instructions failed. Rebuild the AMI and the new agent worked a treat. Is there a way of avoiding this problem by preventing Jenkins from launching the agent until the boot steps are complete? I cannot be the first to encounter this issue :-) Thanks, James -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMH6%2BazGdqPwmrt3U%3Ds7xgXA0v%3DoF3ygv8nxv5DGkMJCc1rCCg%40mail.gmail.com.