I am unable to do this method. The powers that be won't allow any machine with source code or access to source code direct access to any external internet sites. It took 3 months just to get approval to allow Jenkins to send build status emails to an internal server, but only after the Jenkins Master was locked down even further.
On Sun, Dec 25, 2016 at 12:51 PM, Baptiste Mathus <[email protected]> wrote: > IIUC what you say. No. Don't install a clean one and drop it, that will > overwrite existing files and probably just screw up everything. > > But what you say makes me think of an intermediate way: you can use the > typical process to move a master to another machine, but then kind of "move > it back". > > Roughly: > 1. Set up a server with Internet access > 2. Stop the old server > 3. Copy things from the existing one to the Internet ready one > 4. Upgrade it following the standard docs > 5. Move it back (rsync --delete) > > Search the list about it. There's been plenty of discussions about it. > > BTW makes me think we should create a page about that on jenkins.io (if > there is not already one) > > HTH > > Le 22 déc. 2016 4:37 PM, "Jeff" <[email protected]> a écrit : > > Our Jenkins build server is in a secure (no internet) environment and I'd > like to upgrade it. > > Can I install a clean 2.0 with all the plugins (from outside) and then > just zip it up, transfer the archive and extract it over the top of the 1.x > folder structure (except for the jobs/config.xml) along with dropping in a > new .WAR? > > Or are there other considerations I need to be aware of? I haven't found > much relating to the upgrade process for this type of scenario. > > Thanks. > > -- > 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/ms > gid/jenkinsci-users/CAPJK9%3D%2Bih2XFM0CQOzQBN6_4hxKoCR3Ss7r > 2BkbA6Vtt5%3Dc9kw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAPJK9%3D%2Bih2XFM0CQOzQBN6_4hxKoCR3Ss7r2BkbA6Vtt5%3Dc9kw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > 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/CANWgJS7w2kRQKxmDDxz7mVcXXDG4B > cD5NccSjM36Mp4uVHotJw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7w2kRQKxmDDxz7mVcXXDG4BcD5NccSjM36Mp4uVHotJw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPJK9%3DLbg79GeYfEkHMqK-Pex1DFWDka%2Be4xYiqCeq-5XjSYuA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
