On Friday, September 4, 2015 at 5:37:26 PM UTC+1, Daniel Beck wrote: > > >> 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. > > I think we should be able to do this pretty easily. There are several > possible approached to deal with this, and we can point them to it. Even if > we just package the previous bundled plugins into a zip file and make that > available as a separate download, it won't be worse (except for having to > download two things instead of one) than what we have today. But we should > be able to do something much better than that (scripted bundle creation or > script to download selection + depenencies) with a bit of effort. >
This sounds like a practical approach to me +1 -- 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/fea579ab-fa18-4255-908d-1bd5f6f5e01e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
