www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Kolinko (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-3948) Reconfigure Tomcat buildbots
Date Thu, 08 Mar 2012 00:08:58 GMT

    [ https://issues.apache.org/jira/browse/INFRA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224858#comment-13224858

Konstantin Kolinko commented on INFRA-3948:

No progress...
Apparently it is hard to publish those JUnit report files.

Let's simplify the task. We really need access to this information, because buildbot is failing
occasionally and we do not know why.

1. In http://ci.apache.org/builders/tomcat-trunk  builder there is file "build.properties"
in the root of the source tree.

The file is not in SVN, but is created by shell script on Step 2.

The file contains setting for "base.path" property.
Please amend it, adding the following property to the same file:


This will make JUnit to print its reports to stdout instead of separate files, and so we will
be able to see them.

2. Please configure the following builder to also run the testsuite, like tomcat-trunk one

The changes will be
- the same amendment to build.properties file on Step 2,    junit.formatter.usefile=false
- add Step 9 "compile_1" like it is done in tomcat-trunk builder

The "compile_1" steps runs the testsuite.
> 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
> 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
> 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


View raw message