[WG: Sakai QA] Sakai QA] QA Server Confusion

[Matthew Jones]

I remember Pete suggesting this to me back at one time, and I offered
to write a jsp that we could put on the QA's, but he never gave me
what details he wanted from so it never got off the ground. This would
be something that would be a good idea and would make it easier to
manage. I still have access to sakaiproject.org so I can write some
php as well to keep this these external sources cached and checked
centrally.

Let me know if you want any help with this, or minimally let me know
what details you'd want from the QA servers (sakai property values,
system variables, etc)

It looks like you can minimally pull all of this stuff from
getProperties as well as other Properties easily.

http://java.sun.com/j2se/1.5.0/docs/api/java/lang/System.html#getProperties()

-Matthew

On Wed, Jan 13, 2010 at 10:11 AM, Berg, A.M. <A.M.Berg at uva.nl> wrote:
> Hi,
>
> All good points. I was thinking of a small web service per QA server which
> if pinged will give the details needed. A script could then generate an HTML
> page every day or so. Comments welcomed.
>
> Alan
>
> Alan Berg
> Interim QA Director - The Sakai Foundation
>
> Senior Developer / Quality Assurance
> Group Education and Research Services
> Central Computer Services
> University of Amsterdam
>
> http://home.uva.nl/a.m.berg
>
>
>
>
> -----Original Message-----
> From: Noah Botimer [mailto:botimer at umich.edu]
> Sent: Wed 1/13/2010 15:30
> To: Berg, A.M.
> Cc: Beth Kirschner; Sakai QA
> Subject: Re: [WG: Sakai QA] Sakai QA] QA Server Confusion
>
> Is it possible to manage the hostnames/ports such that this doesn't
> happen transiently?
>
> If a hostname/port is to be decommissioned or changed to a different
> release line, I should imagine that this would be a part of the gross
> release cycle or due to hardware additions/subtractions.
>
> Being down temporarily to double-dip on hardware (though not ideal)
> is tolerable, but someone should get what they expect (same release
> line, maybe a different tag) or nothing when they use, e.g., a
> bookmark. Consulting Confluence to figure out what you're going to
> get is a lot of overhead. Stuff from .x branches should really only
> be on "nightly" servers, saving the QA moniker for metered iteration.
>
> Specifically, if we need a 2-5-x-qa in NL, can we get a new hostname
> for this or run on a separate port?
>
> Thanks,
> -Noah
>
> On Jan 13, 2010, at 1:52 AM, Berg, A.M. wrote:
>
>> Hi Beth,
>>
>> Whoopes, thank you for your attention Beth. My mistake, qa1-nl is
>> running 2-5-x-qa. I should of updated confluence. No doubt, David
>> will do so today as well. I intend to move back to the 2-7 series
>> as soon as the next tag is out. If anyone other QA admin has
>> forgotten can they please update as well.
>>
>> Alan
>>
>> Alan Berg
>> Interim QA Director - The Sakai Foundation
>>
>> Senior Developer / Quality Assurance
>> Group Education and Research Services
>> Central Computer Services
>> University of Amsterdam
>>
>> http://home.uva.nl/a.m.berg
>>
>>
>>
>>
>> -----Original Message-----
>> From: sakai-qa-bounces at collab.sakaiproject.org on behalf of Beth
>> Kirschner
>> Sent: Tue 1/12/2010 22:39
>> To: Sakai QA
>> Subject: [WG: Sakai QA] QA Server Confusion
>>
>> There seems to be a couple QA servers that aren't what they claim to
>> be :-(
>>
>> http://qa1-za.sakaiproject.org is listed under Sakai 2.7 test servers
>> in confluence, but its build date is 10/23/09 and svn revision is
>> 69819 (and it behaves differently than other QA servers -- generating
>> errors that cannot be reproduced elsewhere).
>>
>> http://qa1-nl.sakaiproject.org is listed under the Sakai 2.7 test
>> servers in confluence, but the footer says it's running Sakai 2.5.6
>> (which appears to be true)
>>
>> Does anyone know more about these two qa servers? For now, I've
>> updated confluence with my suspicions (http://
>> confluence.sakaiproject.org//x/dwvtAw
>> ).
>>
>> Thanks,
>> - Beth
>>
>> _______________________________________________
>> sakai-qa mailing list
>> sakai-qa at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>>
>> TO UNSUBSCRIBE: send email to sakai-qa-
>> unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>
>>
>> _______________________________________________
>> sakai-qa mailing list
>> sakai-qa at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>>
>> TO UNSUBSCRIBE: send email to sakai-qa-
>> unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
>
>
> _______________________________________________
> sakai-qa mailing list
> sakai-qa at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>
> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"
>