Thanks Stephen, very helpful.
On Fri, Apr 13, 2012 at 15:42, Stephen Connolly <
[email protected]> wrote:
> ProminentProjectAction is I think the extension point you are looking for.
>
> There is a jelly view that gets rendered on the project page for each of
> those.
>
> That jelly view can use something like
>
> <st:include page="ajax.jelly"/>
> <script defer="true">
> refreshPart("${it.reportsDivId}", "${rootUrl}${it.url}/ajax");
> </script>
>
> and you'd add a getReportsDivId() method to your action.
>
> you also create a side ajax.jelly view that contains a div with the
> defined id:
>
> <j:jelly xmlns:j="jelly:core" xmlns:st="jelly:stapler"
> xmlns:d="jelly:define" xmlns:l="/lib/layout" xmlns:t="/lib/hudson"
> xmlns:f="/lib/form" xmlns:i="jelly:fmt">
> <l:ajax>
> <div id="${it.reportsDivId}">
> ...
> </div>
> </l:ajax>
> </j:jelly>
>
> Note you could just use a static id... but safer to have something
> consistently unique in case the action gets added multiple times.
>
> HTH
>
>
> On 13 April 2012 14:37, Stephen Connolly
> <[email protected]>wrote:
>
>> You need to write your own report widget and then it can do the ajax
>> refresh
>>
>>
>> On 13 April 2012 14:34, Simone Busoli <[email protected]> wrote:
>>
>>> Hi Stephen, is the report widget something which is provided out of the
>>> box by Jenkins? How would I send those parts of reports from the agent
>>> running the build to the server so they can be displayed?
>>>
>>> On Fri, Apr 13, 2012 at 15:33, Stephen Connolly <
>>> [email protected]> wrote:
>>>
>>>> If the report widget is always present and updates periodically by an
>>>> ajax call, then you should be ok.
>>>>
>>>>
>>>> On 13 April 2012 13:42, crashingdaily <[email protected]> wrote:
>>>>
>>>>>
>>>>> I recently wrote a plugin to display a single HTML report on the build
>>>>> summary page. The report is not display until the build is complete. I
>>>>> think it could be updated to handle multiple reports, but I don't know how
>>>>> to do active display during the build.
>>>>>
>>>>> https://github.com/crashingdaily/show-build-notes/wiki/Getting-Started
>>>>>
>>>>> (I haven't yet submitted a request to add this to the Jenkins repo)
>>>>>
>>>>> -C
>>>>>
>>>>> On Apr 13, 2012, at 7:22 AM, Simone Busoli wrote:
>>>>>
>>>>> > Hi Fred, thanks for your reply. The builder would simply run C# code
>>>>> and provide a way to output data in HTML format that I would like to
>>>>> display on the Web UI incrementally while the build is running. My plugin
>>>>> already produces those HTML fragments and TeamCity provides a feature to
>>>>> publish so called artifacts from an agent to the server while the build is
>>>>> running so that they can be displayed/downloaded.
>>>>> >
>>>>> > Regardless of whether Jenkins supports doing that during the build
>>>>> is there a way to display HTML reports generated by the build on the Web
>>>>> UI? Or are all artifacts assumed to be downloadable stuff and hence simply
>>>>> listed as files?
>>>>> >
>>>>> > With regard to progress/errors, does Jenkins parse what is printed
>>>>> on the std out/err in any way? For instance TeamCity supports what they
>>>>> call service messages, which are just text formatted in a certain way that
>>>>> the server can interpret and lets you interact with it, for example to
>>>>> report test count, build statistics, explicitly fail or succeed the build,
>>>>> and so on.
>>>>> >
>>>>> > Thanks for your help
>>>>> >
>>>>> > On Apr 13, 2012 11:45 AM, "FredG" <[email protected]> wrote:
>>>>> > Hi,
>>>>> >
>>>>> > displaying artifacts in the UI after a build is a built-in
>>>>> functionality, it just needs to be configured. I'm not sure what you mean
>>>>> with "during the build".
>>>>> > Maybe you can describe your builder plugin a bit more detailed.
>>>>> >
>>>>> > Progress or errors are normally reported in the console output.
>>>>> Every plugin can write to the console.
>>>>> >
>>>>> > Hth,
>>>>> >
>>>>> > Fred
>>>>> >
>>>>> > On Thursday, April 12, 2012 7:01:09 PM UTC+2, Simone wrote:
>>>>> > Anyone?
>>>>> >
>>>>> > On Friday, April 6, 2012 6:14:43 PM UTC+2, Simone wrote:
>>>>> > Hello, I would like to port a builder plugin originally built for
>>>>> TeamCity to Jenkins. I have followed the very good plugin development
>>>>> tutorial and it appears it should not be hard to do but being a newbie to
>>>>> Jenkins I am not sure how it deals with a couple other things.
>>>>> > Is it possible, during the build, to produce "artifacts" which can
>>>>> be displayed in the web UI either during the build or after the build
>>>>> completes? Also, is there a way to report progress/errors of the build?
>>>>> >
>>>>> > Thank you
>>>>>
>>>>>
>>>>
>>>
>>
>
