Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
wants to merge 1 commit into from

Conversation

nickboldt
Copy link
Member

No description provided.

@nickboldt nickboldt restored the JBIDE-17536 branch June 9, 2014 15:25
@@ -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/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)
@maxandersen
Copy link
Member

this is outdated - no point in changing the public urls.

@maxandersen maxandersen closed this Jul 4, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants