You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Antoine Toulme (JIRA)" <ji...@apache.org> on 2010/06/21 17:47:23 UTC
[jira] Updated: (BUILDR-456) Create a functional testing harness
for Buildr
[ https://issues.apache.org/jira/browse/BUILDR-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme updated BUILDR-456:
----------------------------------
Fix Version/s: 1.4.1
(was: 1.4)
> Create a functional testing harness for Buildr
> ----------------------------------------------
>
> Key: BUILDR-456
> URL: https://issues.apache.org/jira/browse/BUILDR-456
> Project: Buildr
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Antoine Toulme
> Fix For: 1.4.1
>
>
> I want to create a functional testing harness on Hudson.
> * use the latest trunk (polling it every day)
> * check out code from svn repos that use Buildr as build system using release tags (to avoid breakage if their trunk don't work).
> * using $JRUBY_HOME, we start jruby and run:
> ** rake setup
> ** gem build buildr.gemspec
> ** gem install buildr-${version}-java.gem
> For each of the checkouts, we run:
> buildr clean
> buildr compile
> buildr test
> buildr package
> Each of the checkout is treated as a test, and we use ci_reporter to do the job of reporting progress in hudson.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.