As we are moving forward with the product release, this has now become
critical.
cheers
-thomas
Jiri Pechanec wrote:
Hi Thomas,
I think we need to clarify your request a little bit. Right now we are
running internal Hudson that can publish build results to the public
Hudson instance (it does it for jBPM).
But if I understand your request correctly you want us to have a
publicly accessbile machine (environment) where we start another Hudson
instance that will be dedicated to just jBPM?
J.
On Tue, 08 Jul 2008 09:46:47 +0200, Thomas Diesler
<thomas.diesler(a)jboss.com> wrote:
> Hi Len,
>
> we made the Hudson setup an integral part of the jBPM project
>
>
http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3BuildingFromSource#S...
>
>
> It is now a two step process to get the QA environment setup remotely
> or locally. This is important because it will allow us to go back in
> time to any given release and recreate the QA environment that was
> used for that release. Patches can then be applied and verified using
> the tagged QA environment.
>
> Could you please setup a public Hudson instance using the link above?
>
> For the username/password combination I prefer:
>
> username: hudson
> password: deadbeefjboss
>
> cheers
> -thomas
>
> Len DiMaggio wrote:
>> You can start with Jirka and me I guess - you want to make the SOA-P
>> jBPM tests on Hudson public?
>> -- Len
>> Thomas Diesler wrote:
>>> Hi Len,
>>>
>>> do you know who I want to talk to about the jBPM Hudson QA?
>>>
>>>
http://jira.jboss.org/jira/browse/JBPM-1373
>>>
>>> cheers
>>> -thomas
>>>
>>>
>>>
>>
>