Re: request in job

Really nice idea... and what about security? Does Hudson have its own user who is logged in before execution? BR, Jan On Thu, 01 Aug 2013 13:59:21 +0200, Barry Books wrote: All my jobs are Tapestry pages and I call them with Hudson (curl). The benefits are: 1. Easier to develop (It's j

Re: request in job

All my jobs are Tapestry pages and I call them with Hudson (curl). The benefits are: 1. Easier to develop (It's just a web page) 2. More control over running jobs 3. Hudson keeps statistics 4. No problems when load balanced The only draw back is Hudson has 1 minute scheduling resolution. I've onl

Re: request in job

I had this same problem with tapestry-cometd where I needed to render components asynchronously outside of a normal request / response. I solved this problem with the ComponentJSONRenderer which spoofs a request and response in order to run the tapestry template rendering. Code here: https://githu

request in job

Hi guys,i've run into terrible issue with jobs. I need to generate link which is afterwards sent to user, but issue is... Job is not executed with http request so that i haven't informations about request to generate the link, so it throws NullPointerException.Is there any other option then having