I have worked in the past on software for facilities that were truly offline (military, literal ships in the navy etc) and they have a lot of their own techniques for bundling software as even off the shelf things that claim to work offline dont. For a class of advanced user I don't think this would be a problem at least.
On Fri, Sep 4, 2015 at 7:32 AM James Nord <[email protected]> wrote: > > > On Wednesday, September 2, 2015 at 9:57:28 PM UTC+1, Tom Fennelly wrote: >> >> On 2 September 2015 at 15:04, James Nord <[email protected]> wrote: >> >>> Lets get something working and then see how we can evolve it to fill >>>> gaps. >>>> >>> >>> Well I can see the headlines now if you release with that in mind >>> "Jenkins, marketed as the leading CI/CD software, no longer >>> supports JUnit the tool used in 99.9% of all development" <snip>out of >>> the box </snip> <- cos you know journalists like to make good headlines >>> >> >> Oh come on James, this is so overly dramatic :) >> > > Yes it was intended to be:) > > > >> >> 1. What percentage of Jenkins install locations do you expect have no >> internet connection? >> >> > I don't know - we don't collect statistics from those types of machines :-/ > > >> 1. Of the percentage from #1, what percentage do you percentage do >> you think would involve a total newbie to Jenkins, such that they would >> not >> be capable of working the kinds of tactics normally employed in these >> kinds >> of situations (whatever they are - pre-defined archives, Juseppe etc) ? >> >> I would think the percentage would be high - but thats a gut feeling > based on nothing... > > > >> For version 1 of this, can't we just document some possible solutions to >> this problem and point the user to these solutions from inside the wizard >> on detecting the fact that there's no internet connection? This seems easy >> enough and we can test it over a period of time. If it's a big issue we'll >> at least have some real data to work with. >> > > For v1 all I am saying is we need to have *a* solution to the problem > (not *what* that solution needs to be). If the chosen solution is > pointing users to a document that explains some workarounds (possibly > provides links to scripts or juseppe etc) then a solution exists and I am > happy. > If the solution is telling users they need an internet connection then I > am not happy (as that's not a solution). > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/kRobm-cxFw8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/9a802d09-be04-4b07-9f21-6404870c9b21%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/9a802d09-be04-4b07-9f21-6404870c9b21%40googlegroups.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 Developers" 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-dev/CAKVMTi5304VGoYV5mLJnBMcAMLfRSiFT6qmX6ws%3DXGs8yB_tBA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
