[Anthill-pro] Step-Execution only by changes

[Eric Minick]

Freddy,

That's fair, the limitation we have though is the decision basis for 
executing a step is based on some fairly simple criteria (what has 
succeeded or failed previously in the job) and doesn't have a script 
selection feature in it. This may be something we could look at adding 
as a feature request, but it would be added complexity for people to 
manage.

We do have that fully dynamic selection of whether to run a job or not, 
and if each build piece was run as a seperate job within the workflow, 
you would be able to do that kind of scripting. My concern there is that 
you would have to configure a seperate job (and script) for each module.

My hope with many projects is that you could use a library job and 
workflow to reuse the same configuration for each sub-project. For 
bringing all the unit test results into one view, my concern would be 
that you would only see the test results for the changing parts which 
might give you a weird view of what's going - especially as more metrics 
make their way into the tool. My suggestion here would be to have the 
lifecycle your modules use have a "test-result" artifact set where you 
publish the unit test xml files.

Your top level project could have a view of all unit test results by 
resolving all the "test-result" artifact set modules into a common 
directory and at the end of the build putting its own files there. You 
would then have a nice view of the unit test results of all your modules 
in a single place where Anthill (or an Ant task report) could process 
them for publishing. A similar approach could be used for the code 
coverage - you wouldn't want to do the code coverage only for the 
changed components I think.

It may be possible to write the creation of every step purely as a 
script. My concern is that it would be difficult for you to maintain. I 
don't think the tool has the facilities though to just add builders and 
pick which ones to run at run-time.

Regards,

Eric

Mockel Frederic wrote:
> Hi all,
>
> this imply for every new module the developer create i have to configure a
> complete project. So i only take a new builder.
> And they want to have collected all unit-test-results in one report, this is
> possible if all builder steps are in one job.
>
> The next one is, they want to have a coverage report for all components. So
> if i take different project i won't get this report.
>
> Is there a way to execute steps in the same job via script ?
>
> Freddy
>
>
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>