install jenkins source no incoming access

9 views
Skip to first unread message

Tim Dunphy

unread,
May 3, 2014, 7:56:37 PM5/3/14
to jenkins...@googlegroups.com
Hey all,

 Well it seems I have what may be a sticky situation here. The only instructions I've been able to find so far on how to install Jenkins onto a host is via the automated installer which I assume means it needs bi-direction (as in incoming and outgoing) connections to the Internet. However I just had this conversation with my boss recently which may pose a problem:

"I am about to send a firewall request

ahh.... we should have opened the firewalls 

anyways they won't get any incoming opened

only outbound..."



So it appears that I'll be installing Jenkins from source on a host that has no incoming access from the net. So my question is, are there any instructions out there regarding how to do this? 


Thank you,

Tim

Mark Waite

unread,
May 3, 2014, 8:15:03 PM5/3/14
to jenkins...@googlegroups.com
You can download the jenkins.war file and execute it directly (java -jar jenkins.war).  No installer needed, and you can carry the jenkins.war file to your computer on a USB memory stick or a CD-R disc.

Alternately, if you prefer one of the installers, you can download the installer and transport it to your computer on physical media.

I recommend you choose the long term support release.  Organizations with computers that do not have internet access are also typically prefer long term stable versions rather than the weekly build versions.

Mark Waite


--
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-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Thanks!
Mark Waite

Daniel Beck

unread,
May 3, 2014, 8:14:47 PM5/3/14
to jenkins...@googlegroups.com
To clarify, are you referring to a host firewall (e.g. single Linux system with restrictive iptables) that doesn't allow incoming connections, or a network firewall/proxy/NAT?

If the latter, some Jenkins features (anonymous usage reports, automatic tool installers, update center, possibly some plugins) require outgoing connections, but Jenkins is perfectly capable of running in a closed-off network.

---

Platform-independent instructions on how to perform a basic installation of Jenkins are available on the "Meet Jenkins" introductory wiki page:
https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins

More detailed instructions are linked from the main "Use Jenkins" wiki page:
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins

It's actually pretty difficult to *not* find these pages!

Tim Dunphy

unread,
May 3, 2014, 9:25:53 PM5/3/14
to jenkins...@googlegroups.com
You can download the jenkins.war file and execute it directly (java -jar jenkins.war).  No installer needed, and you can carry the jenkins.war file to your computer on a USB memory stick or a CD-R disc.
Alternately, if you prefer one of the installers, you can download the installer and transport it to your computer on physical media.
I recommend you choose the long term support release.  Organizations with computers that do not have internet access are also typically prefer long term stable versions rather than the weekly build versions.

Hey! Thanks for the info! This doesn't sound like it'll be too bad after all. I'll give this a shot on monday. But THANK YOU because I am a lot more confident in this task knowing this. However I imagine that downloading to my laptop and scp'ing it up will be just as ok to do. As this is a 'private cloud' machine that I have no physical access to. Maybe I should've mentioned that as well. 

 To clarify, are you referring to a host firewall (e.g. single Linux system with restrictive iptables) that doesn't allow incoming connections, or a network firewall/proxy/NAT?
If the latter, some Jenkins features (anonymous usage reports, automatic tool installers, update center, possibly some plugins) require outgoing connections, but Jenkins is perfectly capable of running in a closed-off network.

It's actually the later. It's an F5 acting as both a firewall and load balancer. Tho we won't need the load balancing capabilities for Jenkins. So if I read you correctly, we should be OK with outgoing, but no incoming access to run it. And to install it, the java -jar method should be fine?!?

Thanks
Tim
 


--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/-xKyhsO-Nhc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages