fenics team mailing list archive

[Martin Sandve Alnæs <martinal@xxxxxxxxx>]

Then if a contributor has a branch that should be tested,
a core developer can quickly and safely push it to the
main repository for testing. I think that's a very nice solution.

Would it be possible to select branch names for each project and test
them together?
I.e. "use */master, ufl/mytopic, ffc/next". That would be very nice :)

Martin

On 24 April 2013 11:54, Johannes Ring <johannr@xxxxxxxxx> wrote:
> On Wed, Apr 24, 2013 at 11:17 AM, Garth N. Wells <gnw20@xxxxxxxxx> wrote:
>> On 23 April 2013 22:10, Johan Hake <hake.dev@xxxxxxxxx> wrote:
>>> Do we have a buildbot testing the next branch?
>>>
>>
>> If we have the resources, it would be good to test both master and
>> next, with the intention that master is almost always green, and next
>> we try to keep green but not minding if it sometimes fails.
>
> This should work fine. I have added next to the buildbot now.
>
> On Tue, Apr 23, 2013 at 10:06 PM, Anders Logg <logg@xxxxxxxxx> wrote:
>>>> One thing I would suggest now is that core developers publish branches
>>>> they intend to merge as part of the main repositories (as opposed to
>>>> storing them in personal repositories). It makes it easier for others
>>>> to follow the development. Note e.g. that PETSc has 66 branches at the
>>>> moment. Examples would be the UFL repository which could have the
>>>> following branches:
>>>>
>>>>   master
>>>>   next
>>>>   martinal/subdomains
>>>>   martinal/signatureopt
>>>>   logg/tuplenotation ;-)
>
> This will make it easy to test a specific branch on the buildbot.
> Simply select a builder, enter the branch name and press the force
> build button.
>
> Johannes
>
> _______________________________________________
> Mailing list: https://launchpad.net/~fenics
> Post to     : fenics@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fenics
> More help   : https://help.launchpad.net/ListHelp