Daniel, Actually... maybe it *is* a race condition. When the role installs Jenkins, it doesn't pre-create the /etc/default/jenkins file, which is where the -Djenkins.install.runSetupWizard=false flag is. So, the order of operations is this:
1. Install the jenkins package from APT. 2. Jenkins is auto-started by systemd. 3. Add the flag to disable the setup wizard. 4. Restart Jenkins. 5. Do all the other config needed. The race condition would be: how far does Jenkins get on that first boot, before being restarted without the setup wizard? Shoot. That makes a lot of sense. I guess I need to pre-create the /etc/default/jenkins file, with the setup wizard disabled and *then* install Jenkins. Slightly less confusedly yours, Karl M. Davis On Sunday, October 8, 2017 at 11:36:20 AM UTC-4, Karl Davis wrote: > > Heh. Unfortunately, I'm the idiot responsible for the role. And I'm > stumped. > > On Sunday, October 8, 2017 at 11:30:34 AM UTC-4, Daniel Beck wrote: >> >> >> > On 8. Oct 2017, at 17:20, Karl Davis <[email protected]> >> wrote: >> > >> > Just to make this even more confusing, when I'm running this role in a >> different environment (but also a clean install) the config.xml has >> hudson.security.HudsonPrivateSecurityRealm and -- sometimes (?!) -- ends up >> with <version>2.whatever</version>. >> >> To clarify, I answered this from Jenkins' perspective. I don't know what >> the role does, but as it seems to behave inconsistently, perhaps ask over >> there? >> >> -- 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/fedb8725-a961-4af9-93c5-5dc0a347abea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
