Git Topic Branches and CI

When using a branch-per-issue, it's not so easy to define #development a la Metacello. How are you handling this? Are you somehow dynamically doing a CI-build-per-branch?

Le 5 août 2015 7:55 PM, "Sean P. DeNigris" <[hidden email]> a écrit :
>
> When using a branch-per-issue, it's not so easy to define #development a la
> Metacello. How are you handling this? Are you somehow dynamically doing a
> CI-build-per-branch?

If you use Travis as CI as in filetree on github, you get one CI build per branch.

I don't know how to do the same with Jenkins.

Thierry

>
>
> -----
> Cheers,
> Sean
> --
> View this message in context: http://forum.world.st/Git-Topic-Branches-and-CI-tp4841141.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>

Thierry Goubier wrote

I don't know how to do the same with Jenkins.

This sounds promising: https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin