You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by "Milos Kleint (JIRA)" <ji...@codehaus.org> on 2006/01/05 21:53:09 UTC

[jira] Created: (CONTINUUM-545) allow xmlrpc access to build results log

allow xmlrpc access to build results log
----------------------------------------

         Key: CONTINUUM-545
         URL: http://jira.codehaus.org/browse/CONTINUUM-545
     Project: Continuum
        Type: New Feature

  Components: XMLRPC Interface  
    Reporter: Milos Kleint
    Priority: Critical


currently the xmlrpc access cannot read build results, it's not included for performance reasons. But without means of accessing it, the netbeans integration is just half as useful. Providing an URL on the server for the build should be enough.

irc log:

another Q: will it be possible to get the build results/output from rpc? currently I didn't figure how..
	evenisse	method is missing in rpc server
	trygvis	yeah, that was deliberate
	evenisse	you can add it DefaultContinum.getBuildResult(id).getOutput()
	trygvis	we should make a special servlet for returning the build output
	evenisse	why? due to output length?
	trygvis	yep
	trygvis	useful for the web UI anyway
	trygvis	I'm afraid that giving the xml-rpc stuff 20MB of logs will give a OutOfMemoryException
	evenisse	20MB for an build output, pff
	trygvis	hehe, the geronimo build is at least that!
	evenisse	ok, so mkleint, don't use rpc for output ;-)
	mkleint	can have at least the ending portion of the output log?
	mkleint	evenisse: kind of sucks, the IDE integration not usefule much then.. I assumed it will be added someday..
	mkleint	or produce an URL that can be opened on request..
	trygvis	you can do a simple HTTP GET to get it
	trygvis	right :)
	mkleint	how to construct the URL?
	trygvis	it's not implemented, but probably <continuum root>/build-output/<build id>
	mkleint	btw I'm also not getting the list of builds in rpc at all.. a bug or not implemented either?
	evenisse	with 1.0.* http://server/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=BUILD_RESULT_I&id=PROJECT_ID
	evenisse	and get on it only what you need
	<--|	jsisson has left #continuum (jsisson)
	trygvis	won't that give you an entire html page=
	trygvis	?
	evenisse	yes :)
	evenisse	but output is after "<h4>Output</h4>"


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-545) allow xmlrpc access to build results log

Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-545?page=comments#action_57014 ] 

Milos Kleint commented on CONTINUUM-545:
----------------------------------------

the output files just need to be linked somehow from the webapp, they reside currently in the apps/continuum/build-results-directory, i've tried adding a symbolic link from the webapp dir, but that din't work somehow.. 

> allow xmlrpc access to build results log
> ----------------------------------------
>
>          Key: CONTINUUM-545
>          URL: http://jira.codehaus.org/browse/CONTINUUM-545
>      Project: Continuum
>         Type: New Feature

>   Components: XMLRPC Interface
>     Reporter: Milos Kleint
>     Priority: Critical

>
>
> currently the xmlrpc access cannot read build results, it's not included for performance reasons. But without means of accessing it, the netbeans integration is just half as useful. Providing an URL on the server for the build should be enough.
> irc log:
> another Q: will it be possible to get the build results/output from rpc? currently I didn't figure how..
> 	evenisse	method is missing in rpc server
> 	trygvis	yeah, that was deliberate
> 	evenisse	you can add it DefaultContinum.getBuildResult(id).getOutput()
> 	trygvis	we should make a special servlet for returning the build output
> 	evenisse	why? due to output length?
> 	trygvis	yep
> 	trygvis	useful for the web UI anyway
> 	trygvis	I'm afraid that giving the xml-rpc stuff 20MB of logs will give a OutOfMemoryException
> 	evenisse	20MB for an build output, pff
> 	trygvis	hehe, the geronimo build is at least that!
> 	evenisse	ok, so mkleint, don't use rpc for output ;-)
> 	mkleint	can have at least the ending portion of the output log?
> 	mkleint	evenisse: kind of sucks, the IDE integration not usefule much then.. I assumed it will be added someday..
> 	mkleint	or produce an URL that can be opened on request..
> 	trygvis	you can do a simple HTTP GET to get it
> 	trygvis	right :)
> 	mkleint	how to construct the URL?
> 	trygvis	it's not implemented, but probably <continuum root>/build-output/<build id>
> 	mkleint	btw I'm also not getting the list of builds in rpc at all.. a bug or not implemented either?
> 	evenisse	with 1.0.* http://server/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=BUILD_RESULT_I&id=PROJECT_ID
> 	evenisse	and get on it only what you need
> 	<--|	jsisson has left #continuum (jsisson)
> 	trygvis	won't that give you an entire html page=
> 	trygvis	?
> 	evenisse	yes :)
> 	evenisse	but output is after "<h4>Output</h4>"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-545) allow xmlrpc access to build results log

Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-545?page=comments#action_57162 ] 

Milos Kleint commented on CONTINUUM-545:
----------------------------------------

in that case, can the default location be within the webapp directory?


> allow xmlrpc access to build results log
> ----------------------------------------
>
>          Key: CONTINUUM-545
>          URL: http://jira.codehaus.org/browse/CONTINUUM-545
>      Project: Continuum
>         Type: New Feature

>   Components: XMLRPC Interface
>     Reporter: Milos Kleint
>     Priority: Critical

>
>
> currently the xmlrpc access cannot read build results, it's not included for performance reasons. But without means of accessing it, the netbeans integration is just half as useful. Providing an URL on the server for the build should be enough.
> irc log:
> another Q: will it be possible to get the build results/output from rpc? currently I didn't figure how..
> 	evenisse	method is missing in rpc server
> 	trygvis	yeah, that was deliberate
> 	evenisse	you can add it DefaultContinum.getBuildResult(id).getOutput()
> 	trygvis	we should make a special servlet for returning the build output
> 	evenisse	why? due to output length?
> 	trygvis	yep
> 	trygvis	useful for the web UI anyway
> 	trygvis	I'm afraid that giving the xml-rpc stuff 20MB of logs will give a OutOfMemoryException
> 	evenisse	20MB for an build output, pff
> 	trygvis	hehe, the geronimo build is at least that!
> 	evenisse	ok, so mkleint, don't use rpc for output ;-)
> 	mkleint	can have at least the ending portion of the output log?
> 	mkleint	evenisse: kind of sucks, the IDE integration not usefule much then.. I assumed it will be added someday..
> 	mkleint	or produce an URL that can be opened on request..
> 	trygvis	you can do a simple HTTP GET to get it
> 	trygvis	right :)
> 	mkleint	how to construct the URL?
> 	trygvis	it's not implemented, but probably <continuum root>/build-output/<build id>
> 	mkleint	btw I'm also not getting the list of builds in rpc at all.. a bug or not implemented either?
> 	evenisse	with 1.0.* http://server/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=BUILD_RESULT_I&id=PROJECT_ID
> 	evenisse	and get on it only what you need
> 	<--|	jsisson has left #continuum (jsisson)
> 	trygvis	won't that give you an entire html page=
> 	trygvis	?
> 	evenisse	yes :)
> 	evenisse	but output is after "<h4>Output</h4>"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-545) allow xmlrpc access to build results log

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-545?page=comments#action_57019 ] 

Emmanuel Venisse commented on CONTINUUM-545:
--------------------------------------------

You can configure the build output directory in Configuration screen under Administration

> allow xmlrpc access to build results log
> ----------------------------------------
>
>          Key: CONTINUUM-545
>          URL: http://jira.codehaus.org/browse/CONTINUUM-545
>      Project: Continuum
>         Type: New Feature

>   Components: XMLRPC Interface
>     Reporter: Milos Kleint
>     Priority: Critical

>
>
> currently the xmlrpc access cannot read build results, it's not included for performance reasons. But without means of accessing it, the netbeans integration is just half as useful. Providing an URL on the server for the build should be enough.
> irc log:
> another Q: will it be possible to get the build results/output from rpc? currently I didn't figure how..
> 	evenisse	method is missing in rpc server
> 	trygvis	yeah, that was deliberate
> 	evenisse	you can add it DefaultContinum.getBuildResult(id).getOutput()
> 	trygvis	we should make a special servlet for returning the build output
> 	evenisse	why? due to output length?
> 	trygvis	yep
> 	trygvis	useful for the web UI anyway
> 	trygvis	I'm afraid that giving the xml-rpc stuff 20MB of logs will give a OutOfMemoryException
> 	evenisse	20MB for an build output, pff
> 	trygvis	hehe, the geronimo build is at least that!
> 	evenisse	ok, so mkleint, don't use rpc for output ;-)
> 	mkleint	can have at least the ending portion of the output log?
> 	mkleint	evenisse: kind of sucks, the IDE integration not usefule much then.. I assumed it will be added someday..
> 	mkleint	or produce an URL that can be opened on request..
> 	trygvis	you can do a simple HTTP GET to get it
> 	trygvis	right :)
> 	mkleint	how to construct the URL?
> 	trygvis	it's not implemented, but probably <continuum root>/build-output/<build id>
> 	mkleint	btw I'm also not getting the list of builds in rpc at all.. a bug or not implemented either?
> 	evenisse	with 1.0.* http://server/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=BUILD_RESULT_I&id=PROJECT_ID
> 	evenisse	and get on it only what you need
> 	<--|	jsisson has left #continuum (jsisson)
> 	trygvis	won't that give you an entire html page=
> 	trygvis	?
> 	evenisse	yes :)
> 	evenisse	but output is after "<h4>Output</h4>"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira