use composite site of multiple versions of JBT instead of single latest site as it's more resilient to frequent builds (JBIDE-17536) >> master #144
Conversation
| @@ -278,7 +278,7 @@ jbt_core: | |||
| url: http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/zz_Release_Notes_4.2.0.Alpha1.readme.html | |||
| 4.2.0.Nightly: | |||
| build_type: nightly | |||
| update_site_url: http://download.jboss.org/jbosstools/updates/nightly/core/master/ | |||
| update_site_url: http://download.jboss.org/jbosstools/builds/nightly/core/master/ | |||
There was a problem hiding this comment.
why do we need to change our public default url for this ?
why doesn't updates/nighlty/core/master not just point to this behind the scenes if it is better ?
There was a problem hiding this comment.
/builds/ is a composite of many builds' update sites
/updates/ is a single (latest) update site
As YMMV, we produce both because every year or two, someone complains loudly about needing one or the other solution. If we make /updates/ a composite for /master/ then it would be a different paradigm for /4.2.luna/, and that would be even more confusing and prone to people complaining it's inconsistent.
Make sense?
There was a problem hiding this comment.
builds have always been a temporary place.
I don't see why anyone (outside of releng) would be confused/worried about wether a nightly site is an aggregate or composite since the nightly site under updates/ exist solely for having a stable url to point to that will get updates when new nightly (somewhat tested) builds are available.
But of course there could be some techinical reason. Do you know any for why we have an aggregate in /updates/nightly and not just a composite ?
…st site as it's more resilient to frequent builds (JBIDE-17536)
|
this is outdated - no point in changing the public urls. |
No description provided.