On 07/04/18 20:49, Jan Lahoda wrote:
On Fri, Apr 6, 2018 at 11:35 PM, Antonio <anto...@vieiro.net> wrote:
[...]
Or is there any way we could do some "non official" distribution through
the mirrors just for testing?


I don't know how trusty the mirror system will be. Will a certain mirror contain our binaries? Will those binaries be corrupt?

Maybe we can enhance the update center to allow the user select a mirror. We can fetch a list of closest mirrors, as JSON, with [1].


None that I'd know of, unfortunately. As a workaround, we could try to
release a limited set of modules; but maybe we could use another release
(like beta 2 or RC) before the final 9.0 release? Not sure.


What's the benefit of a limited set of modules? Won't that be more work (selecting a proper subset of modules) instead of going with the full list?

I think we should do a release just for this feature. I wouldn't feel comfortable releasing 9.0 with an Apache-mirror based system without prior testing.

Cheers,
Antonio


[1]
https://www.apache.org/dyn/closer.cgi/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip&as_json=1

Jan



Cheers,
Antonio


On 06/04/18 21:32, Jan Lahoda wrote:

FWIW, the incubator-netbeans-linux build now prepares the NBMs and catalog
as well:
https://builds.apache.org/view/Incubator%20Projects/job/incu
bator-netbeans-linux/lastSuccessfulBuild/artifact/nbbuild/nbms/

Needs some tweaks (like adding LICENSE/NOTICE/DISCLAIMER to the NBMs)
before it could be part of a release.

Jan

On Thu, Apr 5, 2018 at 8:42 PM, Antonio <anto...@vieiro.net> wrote:

Hi,

I've set up some example redirects (PR #31, [1]), see examples a-c)
below.

I think that we can host the big catalog.xml.gz file in the mirror
system,
and have a redirection at netbeans.apache.org pointing to the
catalog.xml.gz file in the closest mirror.

Cheers,
Antonio

a) Catalog file
The catalog file for 8.2, hosted at updates.netbeans.org.

http://netbeans.apache.org/updates/8.2/uc/final/certified/catalog.xml.gz

now points to

http://updates.netbeans.org/netbeans/updates/8.2/uc/final/ce
rtified/catalog.xml.gz


b) 9.0 sources
This url redirects to the closest Apache mirror for NB 9.0-beta sources.
Note that this redirects (on purpose) to a web page, not to the zip file
itself.

http://netbeans.apache.org/download/9.0-beta/source

now points to

https://www.apache.org/dyn/closer.cgi/incubator/netbeans/inc
ubating-netbeans-java/incubating-9.0-beta/incubating-
netbeans-java-9.0-beta-source.zip

c) 9.0 binaries
This url redirects to the closest Apache mirror for NB 9.0-beta binaries
Note that this redirects (on purpose) to a web page, not to the zip file
itself.

http://netbeans.apache.org/download/9.0-beta/binary

pointing to

https://www.apache.org/dyn/closer.cgi/incubator/netbeans/inc
ubating-netbeans-java/incubating-9.0-beta/incubating-
netbeans-java-9.0-beta-bin.zip





[1]

https://github.com/apache/incubator-netbeans-website/pull/31

On 05/04/18 19:13, Jan Lahoda wrote:

On Thu, Apr 5, 2018 at 6:57 PM, Antonio <anto...@vieiro.net> wrote:

Hi,


Some comments/ideas:

1. I think we should open an issue with INFRA so they are aware ouf our
~3TB/month load requirements. I imagine they'll prefer we use the
mirror
network.

2. We can make http://netbeans.apache.org/updates/9.0/ redirect to
wherever we want (we _don't need a specific domain_ for that) by using
a
simple .htaccess file (much like [1]). We can do this ourselves, today.
Let
me know if you want to try it out with, say, the 9.0-beta files. I
think
Infra should validate that our web server is going to hold the load,
though.


That would surely be a nicer URL.



3. If we use the mirror system we'll be losing statistics. AFAIK the
mirror network does not consolidate server logs.


Do we have logs from the webserver? We don't need the statistics from
the
mirrors, but statistics from the redirects would be nice.

Jan



4. Now that we're talking about releasing NBMs maybe we should start
thinking on releasing stuff to Maven central (as NetCAT required). How
are
maven central artifacts generated? I don't think we have this tooling
under
the Apache umbrella, have we?

Cheers,
Antonio


[1]
https://github.com/apache/incubator-netbeans-website/blob/
master/netbeans.apache.org/src/content/.htaccess



On 05/04/18 16:15, Jan Lahoda wrote:

I believe this is about NBMs built from the standard distribution. Good

among others for dot-dot updates, where the users could just download
updated modules, not the whole distro.

I think the current overall idea (based on ideas by many other people,
like
Jarda):
-release the NBMs and the catalog as part of the convenience binaries
(this
will probably need a little tweaking)
-have a (NetBeans 9.0-specific) URL setup on the netbeans-vm, like
e.g.:
http://netbeans-vm.apache.org/updates/9.0
which would do a redirect to the Apache release using:
http://www.apache.org/dyn/closer.lua?action=download&filename=<path>

this should automatically redirect to mirrors.

Not sure if we can fully test this without doing a release, but my
plan
for
a near future was to change our continuous build (one of them) to
produce
the NBMs and then ask to have the redirect setup - then we could do at
least some testing.

Jan


On Thu, Apr 5, 2018 at 2:38 PM, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

Hi all,


We need to nail down this one and I think the key blocker is that
there
are
different ideas about what this is about:

https://issues.apache.org/jira/browse/NETBEANS-330

The above is not about the Plugin Portal.

If I understand it correctly, this is about where the NBMs (which
ones?
how
many? do we know?) and the related XML file (a.k.a. update center)
will
be
hosted.

AFAIK, the XML file and the NBMs could be put onto our Apache
NetBeans
VM
just like Synergy:

http://netbeans-vm.apache.org/synergy

The key question remains, which NBMs are we talking about here,
applicable
to the 9.0 release, I think.

Thanks,

Gj



------------------------------------------------------------
---------

To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.ap
ache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Reply via email to