Searching around on the Net, I find many people who have had trouble getting a headless Eclipse/Buckminster build to work when the builder is located behind a proxy that requires authentication. But I haven't found any real solutions. I'd really like to see a step-by-step guide.
Most suggestions involve running Eclipse to set the username/password. If I have to, I might be able to do that, but we don't actually run Eclipse on the builder box at this time. In fact, no one actually sits at that box; access is via SSH. I can easily put the correct proxy server name and port into /var/lib/jenkins/tools/hudson.plugins.buckminster.BuckminsterInstallation/Buckminster/director/configuration/.settings/org.eclipse.core.net.prefs. But no one suggests putting the user/password there, though I'd be happy to do so. Instead, I see hints that Eclipse wants this information to go into some sort of keyring. If true, then I'd like to see a way to do that without using Eclipse itself. If I have to set this up using Eclipse, then a few additional questions arise. Which user, Jenkins? Where should the project files be located? (Maybe its obvious but I'm not actually an Eclipse user and I'd prefer not to have to become one to make this work.) -- Dave Close I don't send HTML email and I prefer not to receive it. HTML email is ugly and a significant security exposure. -- 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. For more options, visit https://groups.google.com/groups/opt_out.