So our builds failed again yesterday due to this automatic update kicking in. I checked, there was indeed a JDK security update so no complaints, but I need a better system of updating Jenkins.
Given Packer can search for and filter down AMIs, I thought the EC2 plugin should be able to, too. Solves our issue. Ticket if anyone is interested: https://issues.jenkins-ci.org/browse/JENKINS-59180 On Thu, 29 Aug 2019 at 10:17, James Green <[email protected]> wrote: > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMH6%2BayeuwT7N5pAuRy0ORsw4oCHk0nBhT5O1Ktvb-Ng_4WvWQ%40mail.gmail.com.
