building and running hudson with NetBeans

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

building and running hudson with NetBeans

Sven Reimers
I tried this using Mevenide-2 for Maven2. Despite a problem concerning
antlr not working correctly from inside netbeans due to some
securtiy-violation, i can build hudson without problems.

But, trying to run/debug hudson i keep getting

[netbeans-deploy:deploy]
[INFO]Deployment started
[INFO]Deploying on Bundled Tomcat (5.5.17)
[INFO]    debugMode=true
[INFO]    clientModuleuri=null
[INFO]    clientUrlPart=
[INFO]    forcedeploy=true
[INFO]Starting debug server Bundled Tomcat (5.5.17)
[INFO]Starting Tomcat process...
[INFO]Waiting for Tomcat...
[INFO]Tomcat server started.
[INFO]In-place deployment at
C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson
[INFO]C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson\META-INF\context.xml
(Das System kann die angegebene Datei nicht finden)
[INFO]------------------------------------------------------------------------
[ERROR]BUILD FAILURE
[INFO]------------------------------------------------------------------------
[INFO]Failed Deployment:Deployment error:


Anyone any ideas???

Thx

-Sven

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: building and running hudson with NetBeans

Kohsuke Kawaguchi-2
Sven Reimers wrote:
> I tried this using Mevenide-2 for Maven2. Despite a problem concerning
> antlr not working correctly from inside netbeans due to some
> securtiy-violation, i can build hudson without problems.

I recommend you run "mvn jetty:run" in the war module.
The POM has a setting for jetty plugin to do the right thing.


> But, trying to run/debug hudson i keep getting
>
> [netbeans-deploy:deploy]
> [INFO]Deployment started
> [INFO]Deploying on Bundled Tomcat (5.5.17)
> [INFO]    debugMode=true
> [INFO]    clientModuleuri=null
> [INFO]    clientUrlPart=
> [INFO]    forcedeploy=true
> [INFO]Starting debug server Bundled Tomcat (5.5.17)
> [INFO]Starting Tomcat process...
> [INFO]Waiting for Tomcat...
> [INFO]Tomcat server started.
> [INFO]In-place deployment at
> C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson
> [INFO]C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson\META-INF\context.xml
> (Das System kann die angegebene Datei nicht finden)
> [INFO]------------------------------------------------------------------------
> [ERROR]BUILD FAILURE
> [INFO]------------------------------------------------------------------------
> [INFO]Failed Deployment:Deployment error:
>
>
> Anyone any ideas???
>
> Thx
>
> -Sven
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: building and running hudson with NetBeans

Sven Reimers
On 11/14/06, Kohsuke Kawaguchi <[hidden email]> wrote:
> Sven Reimers wrote:
> > I tried this using Mevenide-2 for Maven2. Despite a problem concerning
> > antlr not working correctly from inside netbeans due to some
> > securtiy-violation, i can build hudson without problems.
>
> I recommend you run "mvn jetty:run" in the war module.
> The POM has a setting for jetty plugin to do the right thing.
>
Ok. But still would be nice if this could work. Will look into it some
more and keep you posted on any discvery I can come up with....

>
> > But, trying to run/debug hudson i keep getting
> >
> > [netbeans-deploy:deploy]
> > [INFO]Deployment started
> > [INFO]Deploying on Bundled Tomcat (5.5.17)
> > [INFO]    debugMode=true
> > [INFO]    clientModuleuri=null
> > [INFO]    clientUrlPart=
> > [INFO]    forcedeploy=true
> > [INFO]Starting debug server Bundled Tomcat (5.5.17)
> > [INFO]Starting Tomcat process...
> > [INFO]Waiting for Tomcat...
> > [INFO]Tomcat server started.
> > [INFO]In-place deployment at
> > C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson
> > [INFO]C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson\META-INF\context.xml
> > (Das System kann die angegebene Datei nicht finden)
> > [INFO]------------------------------------------------------------------------
> > [ERROR]BUILD FAILURE
> > [INFO]------------------------------------------------------------------------
> > [INFO]Failed Deployment:Deployment error:
> >
> >
> > Anyone any ideas???
> >
> > Thx
> >
> > -Sven
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: building and running hudson with NetBeans

Kohsuke Kawaguchi-2
Sven Reimers wrote:
> Ok. But still would be nice if this could work. Will look into it some
> more and keep you posted on any discvery I can come up with....

OK. I guess a part of the problem for me is that I can't read German (is
that it?) so I don't understand what the error message is.

Is it saying that the system cannot find the file? If so, context.xml is
not mandatory in Tomcat, so I don't know why it's complaining. But you
might be able to have some dummy file in there to make it happy.

Just a suggestion.

>>
>> > But, trying to run/debug hudson i keep getting
>> >
>> > [netbeans-deploy:deploy]
>> > [INFO]Deployment started
>> > [INFO]Deploying on Bundled Tomcat (5.5.17)
>> > [INFO]    debugMode=true
>> > [INFO]    clientModuleuri=null
>> > [INFO]    clientUrlPart=
>> > [INFO]    forcedeploy=true
>> > [INFO]Starting debug server Bundled Tomcat (5.5.17)
>> > [INFO]Starting Tomcat process...
>> > [INFO]Waiting for Tomcat...
>> > [INFO]Tomcat server started.
>> > [INFO]In-place deployment at
>> > C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson
>> > [INFO]C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson\META-INF\context.xml
>> > (Das System kann die angegebene Datei nicht finden)
>> > [INFO]------------------------------------------------------------------------
>> > [ERROR]BUILD FAILURE
>> > [INFO]------------------------------------------------------------------------
>> > [INFO]Failed Deployment:Deployment error:
>> >
>> >
>> > Anyone any ideas???
>> >
>> > Thx
>> >
>> > -Sven
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
>> >
>> >
>>
>>
>> --
>> Kohsuke Kawaguchi
>> Sun Microsystems                   [hidden email]
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: building and running hudson with NetBeans

Jesse Glick
In reply to this post by Sven Reimers
Sven Reimers wrote:
> Despite a problem concerning antlr not working correctly from inside
> netbeans due to some securtiy-violation

There is a bug filed about this already for the ANTLR plug-in (unwisely
tries to set its own security manager).

> [INFO]Tomcat server started.
> [INFO]In-place deployment at
> C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson
> [INFO]C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson\META-INF\context.xml
>
> (Das System kann die angegebene Datei nicht finden)

"(The system cannot find the abovementioned file)" I guess. No idea what
would cause that. (I haven't tried deploying Hudson using the standard
targets since I send it to a remote server anyway using a custom shell
script.)

-J.

--
[hidden email]  x22801  netbeans.org  ant.apache.org
       http://google.com/search?q=e%5E%28pi*i%29%2B1

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Build timeout feature?

Michael Nenashev
How difficult would it be to add a timeout feature?
Our CVS is hosted and it uses locks and it gets locked
every so often. It would be better to cancel the job
in that case and to send a failure message.

Thank you,
Michael


 
____________________________________________________________________________________
Sponsored Link

Mortgage rates near 39yr lows.
$420k for $1,399/mo. Calculate new payment!
www.LowerMyBills.com/lre

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: building and running hudson with NetBeans

Sven Reimers
In reply to this post by Jesse Glick
Ups. Sorry to give you the localized message. But you are right with
the translation anyway. The antlr is not that problematic, I just do
this from the command-line once..

I will keep you posted if I can find out more about the tomcat issue.

Thx

-Sven

On 11/15/06, Jesse Glick <[hidden email]> wrote:

> Sven Reimers wrote:
> > Despite a problem concerning antlr not working correctly from inside
> > netbeans due to some securtiy-violation
>
> There is a bug filed about this already for the ANTLR plug-in (unwisely
> tries to set its own security manager).
>
> > [INFO]Tomcat server started.
> > [INFO]In-place deployment at
> > C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson
> > [INFO]C:\source\remote\dev.java.net\hudson\hudson\main\war\target\hudson\META-INF\context.xml
> >
> > (Das System kann die angegebene Datei nicht finden)
>
> "(The system cannot find the abovementioned file)" I guess. No idea what
> would cause that. (I haven't tried deploying Hudson using the standard
> targets since I send it to a remote server anyway using a custom shell
> script.)
>
> -J.
>
> --
> [hidden email]  x22801  netbeans.org  ant.apache.org
>        http://google.com/search?q=e%5E%28pi*i%29%2B1
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Wolfram Kroll-2
In reply to this post by Michael Nenashev
Michael Nenashev schrieb:
> How difficult would it be to add a timeout feature?
> Our CVS is hosted and it uses locks and it gets locked
> every so often. It would be better to cancel the job
> in that case and to send a failure message.
>  
I would second that feature request. We want to use Hudson for some
testing scripts, which sometimes stall or deadlock. We had to put the
timeout guard stuff into the ant build files or shell scripts. Would be
nice, if Hudson had this right built in.

-wolfram

> Thank you,
> Michael
>
>
>  
> ____________________________________________________________________________________
> Sponsored Link
>
> Mortgage rates near 39yr lows.
> $420k for $1,399/mo. Calculate new payment!
> www.LowerMyBills.com/lre
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Kohsuke Kawaguchi-2
Wolfram Kroll wrote:

> Michael Nenashev schrieb:
>> How difficult would it be to add a timeout feature?
>> Our CVS is hosted and it uses locks and it gets locked
>> every so often. It would be better to cancel the job
>> in that case and to send a failure message.
>>  
> I would second that feature request. We want to use Hudson for some
> testing scripts, which sometimes stall or deadlock. We had to put the
> timeout guard stuff into the ant build files or shell scripts. Would be
> nice, if Hudson had this right built in.
Thanks for filing an issue for this. I do have this kind of problems in
my environment, too, so it sounds like useful.

The trick is how to figure out the stall/deadlock, though. I have
master/slave set up, so depending on the slave it runs (and the other
builds that happen to run on the same machine, or network, etc), the
time it takes to build is very different. It would be really nice if
Hudson could automatically detect a stall/deadlock.

But I suppose it might be just too difficult?

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Michael Nenashev
I think even a straightforward timeout and job abort
after a predefined period would be really useful. No
need to get fancy ;) Just have a field in the Job
Configure page that takes a number (seconds, minutes,
does not matter), and if that number is exceeded than
stop the job and mail a failure message.

Thank you!
--Mike

--- Kohsuke Kawaguchi <[hidden email]>
wrote:

> Wolfram Kroll wrote:
> > Michael Nenashev schrieb:
> >> How difficult would it be to add a timeout
> feature?
> >> Our CVS is hosted and it uses locks and it gets
> locked
> >> every so often. It would be better to cancel the
> job
> >> in that case and to send a failure message.
> >>  
> > I would second that feature request. We want to
> use Hudson for some
> > testing scripts, which sometimes stall or
> deadlock. We had to put the
> > timeout guard stuff into the ant build files or
> shell scripts. Would be
> > nice, if Hudson had this right built in.
>
> Thanks for filing an issue for this. I do have this
> kind of problems in
> my environment, too, so it sounds like useful.
>
> The trick is how to figure out the stall/deadlock,
> though. I have
> master/slave set up, so depending on the slave it
> runs (and the other
> builds that happen to run on the same machine, or
> network, etc), the
> time it takes to build is very different. It would
> be really nice if
> Hudson could automatically detect a stall/deadlock.
>
> But I suppose it might be just too difficult?
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                  
> [hidden email]
>



 
____________________________________________________________________________________
The all-new Yahoo! Mail beta
Fire up a more powerful email and get things done faster.
http://new.mail.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Wolfram Kroll-2
In reply to this post by Kohsuke Kawaguchi-2
Am 16.11.2006 um 02:08 schrieb Kohsuke Kawaguchi:

> Wolfram Kroll wrote:
>> Michael Nenashev schrieb:
>>> How difficult would it be to add a timeout feature? Our CVS is
>>> hosted and it uses locks and it gets locked
>>> every so often. It would be better to cancel the job
>>> in that case and to send a failure message.
>>>
>> I would second that feature request. We want to use Hudson for some
>> testing scripts, which sometimes stall or deadlock. We had to put the
>> timeout guard stuff into the ant build files or shell scripts. Would
>> be nice, if Hudson had this right built in.
>
> Thanks for filing an issue for this. I do have this kind of problems
> in my environment, too, so it sounds like useful.
>
> The trick is how to figure out the stall/deadlock, though. I have
> master/slave set up, so depending on the slave it runs (and the other
> builds that happen to run on the same machine, or network, etc), the
> time it takes to build is very different. It would be really nice if
> Hudson could automatically detect a stall/deadlock.

"The Buildbot" CI system as an example just watches for output on
stdout/stderr and when nothing happens, it kills the job after a user
defined time.

---wolfram

>
> But I suppose it might be just too difficult?
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Kohsuke Kawaguchi-2
Wolfram Kroll wrote:
> "The Buildbot" CI system as an example just watches for output on
> stdout/stderr and when nothing happens, it kills the job after a user
> defined time.

Yeah, I guess something like that is the best we could do, probably.

Some of the jobs at my deployment runs the performance test, and they
can easily go off an hour or two without producing a single line.

If we could somehow combine it with CPU usage monitoring...

Oh well, I think Michael is right --- no need to get fancy, I guess.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Michael Nenashev
I would be content with just 'kill if not finished in
xx minutes' feature. No log, no CPU, no I/O
monitoring, nothing ;) But then again our builds are
very consistent, time-wise ...

Thank you,
Michael

--- Kohsuke Kawaguchi <[hidden email]>
wrote:

> Wolfram Kroll wrote:
> > "The Buildbot" CI system as an example just
> watches for output on
> > stdout/stderr and when nothing happens, it kills
> the job after a user
> > defined time.
>
> Yeah, I guess something like that is the best we
> could do, probably.
>
> Some of the jobs at my deployment runs the
> performance test, and they
> can easily go off an hour or two without producing a
> single line.
>
> If we could somehow combine it with CPU usage
> monitoring...
>
> Oh well, I think Michael is right --- no need to get
> fancy, I guess.
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                  
> [hidden email]
>



 
____________________________________________________________________________________
Sponsored Link

Rates near historic lows -
$200,000 mortgage for $660/ month -
http://yahoo.ratemarketplace.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Vladimir Sizikov
In reply to this post by Kohsuke Kawaguchi-2
On Thu, Nov 16, 2006 at 09:13:42AM -0800, Kohsuke Kawaguchi wrote:

> Wolfram Kroll wrote:
> >"The Buildbot" CI system as an example just watches for output on
> >stdout/stderr and when nothing happens, it kills the job after a user
> >defined time.
>
> Yeah, I guess something like that is the best we could do, probably.
>
> Some of the jobs at my deployment runs the performance test, and they
> can easily go off an hour or two without producing a single line.
>
> If we could somehow combine it with CPU usage monitoring...

But then again, the build could hang somewhere in busy-loop consuming
entire CPU, and how to distinguish between that and performance tests? :)

> Oh well, I think Michael is right --- no need to get fancy, I guess.

Yeah, even basic timeout would be a very good improvement. I'm actually
surprised that nobody requested this before :)

The problem with Java, of course, is that there is no reliable way to
kill offending thread for sure (if the thread is not cooperating). We
could interrupt, but if the thread is stuck somewhere in blocked IO,
it's not guaranteed that we ever can kill it.

Thanks,
  --Vladimir

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Curt Cox
"The problem with Java, of course, is that there is no reliable way to
kill offending thread for sure (if the thread is not cooperating). We
could interrupt, but if the thread is stuck somewhere in blocked IO,
it's not guaranteed that we ever can kill it."

This is the problem isolates solve.  I hope they make it into Dolphin.
 They are available in a very limited sense right now.

https://mvm.dev.java.net/

ProcessBuilder is awkward and error-prone, but freely available now.
If someone had a week to spare, they could probably use the JSR-121
TCK to build a fully compliant isolate implementation using
ProcessBuilder.  Of course there is no need to implement JSR-121 to do
this using ProcessBuilder.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Kohsuke Kawaguchi-2
In reply to this post by Vladimir Sizikov
Vladimir Sizikov wrote:
>> Oh well, I think Michael is right --- no need to get fancy, I guess.
>
> Yeah, even basic timeout would be a very good improvement. I'm actually
> surprised that nobody requested this before :)

OK, I guess we have an action plan then.

> The problem with Java, of course, is that there is no reliable way to
> kill offending thread for sure (if the thread is not cooperating). We
> could interrupt, but if the thread is stuck somewhere in blocked IO,
> it's not guaranteed that we ever can kill it.

Yep.


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Kohsuke Kawaguchi-2
In reply to this post by Michael Nenashev
Michael Nenashev wrote:
> How difficult would it be to add a timeout feature?
> Our CVS is hosted and it uses locks and it gets locked
> every so often. It would be better to cancel the job
> in that case and to send a failure message.

I implemented a plugin "build-timeout" for this feature.
It will be available with the next 1.64 release.


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Michael Nenashev
I pray plugin works with JDK 1.4 ... ;)
I look forward to checking it out!

Thank you,
Mike

--- Kohsuke Kawaguchi <[hidden email]>
wrote:

> Michael Nenashev wrote:
> > How difficult would it be to add a timeout
> feature?
> > Our CVS is hosted and it uses locks and it gets
> locked
> > every so often. It would be better to cancel the
> job
> > in that case and to send a failure message.
>
> I implemented a plugin "build-timeout" for this
> feature.
> It will be available with the next 1.64 release.
>
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                  
> [hidden email]
>



 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Build timeout feature?

Kohsuke Kawaguchi-2
Michael Nenashev wrote:
> I pray plugin works with JDK 1.4 ... ;)
> I look forward to checking it out!

Good point. I'll set up retrotranslator for it.

>
> Thank you,
> Mike
>
> --- Kohsuke Kawaguchi <[hidden email]>
> wrote:
>
>> Michael Nenashev wrote:
>> > How difficult would it be to add a timeout
>> feature?
>> > Our CVS is hosted and it uses locks and it gets
>> locked
>> > every so often. It would be better to cancel the
>> job
>> > in that case and to send a failure message.
>>
>> I implemented a plugin "build-timeout" for this
>> feature.
>> It will be available with the next 1.64 release.
>>
>>
>> --
>> Kohsuke Kawaguchi
>> Sun Microsystems                  
>> [hidden email]
>>
>
>
>
>  
> ____________________________________________________________________________________
> Do you Yahoo!?
> Everyone is raving about the all-new Yahoo! Mail beta.
> http://new.mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment