buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antoine Toulme (JIRA)" <j...@apache.org>
Subject [jira] Updated: (BUILDR-456) Create an integration testing harness for Buildr
Date Sun, 25 Jul 2010 18:47:50 GMT

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

Antoine Toulme updated BUILDR-456:
----------------------------------

    Summary: Create an integration testing harness for Buildr  (was: Create a functional testing
harness for Buildr)

Renaming the bug, got my naming wrong.

> Create an integration 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.2
>
>         Attachments: functional.zip
>
>
> 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.


Mime
View raw message