Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326210

Summary:	would be best to alias or redirect old build/hudson URLs
Product:	Community	Reporter:	David Williams <david_williams>
Component:	Servers	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	minor
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description David Williams

2010-09-24 18:34:17 EDT

Now that there is no longer a hudson instance running with a URL of
https://build.eclipse.org/hudson/...

It would be best to either have an alias that mapped request to new one, such as map 
https://build.eclipse.org/hudson/* 
to 
https://hudson.eclipse.org/hudson/...

Or, all requests to 
https://build.eclipse.org/hudson/*
be redirected to one page, that basically would say'hudson has moved" and give the correct, general URL of new instance. 

I thought of this as I went to update the URL in some Sim Rel documents. 
And remembered it is a principle of good "web management" that well known URLs evolve, instead of just disappear. 

I will of course update the URL where I find them but am sure it exists in places, old mailing list posts, etc., that will be overlooked or impossible to change.

Comment 1 Denis Roy

2010-09-24 19:27:52 EDT

I've thought of this, but many people perhaps won't realize this is the 'new' Hudson.  Or perhaps that doesn't matter...

Comment 2 David Williams

2010-09-24 20:47:04 EDT

(In reply to comment #1)
> I've thought of this, but many people perhaps won't realize this is the 'new'
> Hudson.  Or perhaps that doesn't matter...

Well, the deluxe solution is to redirect to one page that gives the info ... "the URL has changed ... we will attempt to automatically direct you to new hudson location in 90 seconds, but the old job or view may no longer exist ... " and then attempt to redirect.  

But ... my main concern is just giving users a 404 type error. Actually, right now, using firefox, when trying an old URL such as  

https://build.eclipse.org/hudson/view/Repository Aggregation/

I get an "unable to connect" message ... 

The site could be temporarily unavailable or too busy. Try again in a few
    moments.

the opposite of helpful :) 

So, I think as long as it goes somewhere to new hudson, even if at top level, that'd be fine. I mostly just thought best to avoid the "no connection" type message. 

I just noticed that giving nu-hudson an invalid URL is not friendly either ... it does result in a true 404 error ... but, at least that is from hudson (and, I'm sure even that could be improved eventually if someone put their mind to it). For example, 

https://hudson.eclipse.org/hudson/view/Repository%20Aggregationzzzz/ 

vs the intended 

https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/


The main use-case I have in mind is where, in old SimRel build documents, we say (or said) "check the status of the job at ... 
https://build.eclipse.org/hudson/view/Repository%20Aggregation/
and that does map well to 
https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/

Hm, I meant to mark this as "minor", may have clicked wrong.

Comment 3 Denis Roy

2011-08-12 16:12:18 EDT

I don't think we have a need for this anymore.