[jira] [Updated] (INFRA-3948) Reconfigure Tomcat buildbots

["Konstantin Kolinko (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Kolinko updated INFRA-3948:
--------------------------------------

    Comment: was deleted

(was: 1. There is one important issue that is still unresolved:

We still do not have access to JUnit reports generating by testing ("compile_1" step in tomcat-trunk builder [1]).
All we have is stdout file. That is not enough to properly diagnose the test failures.

[1] http://ci.apache.org/builders/tomcat-trunk


In Gump configuration we have those files. They are listed in [2] and they are configured in project/tomcat-trunk.xml as <report nested="output/build/logs" />

[2] http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/

If it is hard or impossible to publish those files (a separate set of files for each buildbot run), there is an alternative:
Add the following property when running the "test" target of our build.xml in the "compile_1" step:

junit.formatter.usefile=false

If that property is set to "false" the Junit reports will be printed to the same stdout file.


2. I would like the same testing configuration ("compile_1" step) to be configured for
tomcat-7-trunk builder. [3]

[3] http://ci.apache.org/builders/tomcat-7-trunk

Configuration there is the same as for tomcat-trunk.
)
    
> Reconfigure Tomcat buildbots
> ----------------------------
>
>                 Key: INFRA-3948
>                 URL: https://issues.apache.org/jira/browse/INFRA-3948
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Buildbot
>            Reporter: Konstantin Kolinko
>            Assignee: Gavin
>            Priority: Minor
>
> Currently the following Build bots for Apache Tomcat project are running:
> http://ci.apache.org/builders/tomcat-trunk
> http://ci.apache.org/builders/tomcat-6-trunk
> Thy publish their output (documentation and RAT reports) here:
> http://ci.apache.org/projects/tomcat/
> 1. In August 2011 the stable "Tomcat 7" branch has been created (/tomcat/tc7.0.x/trunk) and /tomcat/trunk is now named "Tomcat 8".
> The following changes are needed:
> - Split the current "tomcat-trunk" builder into two, "tomcat-trunk" and "tomcat-7-trunk"
> - "tomcat-7-trunk" should use svn from /tomcat/tc7.0.x/trunk instead of /tomcat/trunk
> - "tomcat-trunk" should publish its results as "tomcat8". Update descriptions as needed.
> 2. As INFRA-2435 mentions, RAT reports are currently generated for Tomcat trunk only.
> They can be generated for both Tomcat 7 and trunk now, but they will have to use different file names.
> How are we supposed to configure exclusions list for the RAT tool?
> At least it should be configured to skip *.html files in output/build/webapps/docs/**, because those are generated at build time and do not have license headers and should not have them.
> 3. It would be nice to configure build bot to run testsuites as well. Currently only Gump is configured to run them.
> The testsuite does exist for Tomcat 7 and Tomcat trunk, but does not exist for Tomcat 6.
> To run it you execute the "test" target in the default build.xml
> 1) It would be nice if Documentation were published before running the test suite, so that test failures do not affect it.
> 2) To diagnose the test failures we need access to
>  - stdout/stderr of Ant
>  - log files generated in output/build/logs
> In Gump the testing is performed by "tomcat-tc7.0.x-test" and "tomcat-trunk-test" projects. The list of log files generated by tests can be seen here:
> http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira