fenics team mailing list archive

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

So, will we do something like this?

- checkout topic branch from master
- work on topic
- test locally

- merge topic into next
- test locally

- push to fenics/dolfin/next
- wait for green buildbot and allow time for others to (pro)test

- merge topic into master
- test locally

- push to fenics/dolfin/master
- wait for green buildbot

- breathe out relieved

Would it also be possible (in due time) to point the buildbot to e.g.
my personal martinal/<project>/next branches? I miss being able to
test changes to ufl/ufc/ffc/dolfin together on buildbot before
integrating.

Martin


On 17 April 2013 14:42, Johannes Ring <johannr@xxxxxxxxx> wrote:
> On Wed, Apr 17, 2013 at 2:08 PM, Anders Logg <logg@xxxxxxxxx> wrote:
>> One thing though is that it perhaps doesn't make sense to create the
>> 'next' branch at this point, until it is being tested by the buildbot?
>>
>> I think Johannes is working on getting it running.
>
> The buildbot is running again now, although I have currently only
> enabled a few of the buildslaves since I have had some problems
> getting polling of changes from Bitbucket to work. It looks like it is
> working now, so I will enable the rest of the buildslaves soon.
>
> Johannes
>
> _______________________________________________
> Mailing list: https://launchpad.net/~fenics
> Post to     : fenics@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fenics
> More help   : https://help.launchpad.net/ListHelp