Tarmac

Should have some way to distribute configuration

Bug #630252 reported by James Westby
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tarmac
Triaged
Wishlist
Unassigned

Bug Description

Hi,

There are some bits of configuration, such as verify_command, that I
don't really want to have every user have to specify, as it is basically
going to be the same for every user.

It would be great if there was some way for tarmac to pick options up
from the branch, with the ability for local overrides.

Thanks,

James

Revision history for this message
dobey (dobey) wrote :

Can you clarify this a big? How many users are going to be running tarmac? and how many different branches are going to have the exact same test command? Perhaps some simple examples to show what you mean?

Revision history for this message
James Westby (james-w) wrote : Re: [Bug 630252] Re: Should have some way to distribute configuration

On Tue, 07 Sep 2010 20:11:37 -0000, Rodney Dawes <email address hidden> wrote:
> Can you clarify this a big? How many users are going to be running
> tarmac? and how many different branches are going to have the exact same
> test command? Perhaps some simple examples to show what you mean?

Several users may run it.

If you don't have a centralised daemon, then you may have developers do
reviews, then run tarmac to land all the branches.

Currently this requires them each to have the verify_command for a
particular project in their config, which makes changing it a pain, as
they all have to update it.

Thanks,

James

Paul Hummer (rockstar)
Changed in tarmac:
status: New → Triaged
importance: Undecided → Low
dobey (dobey)
Changed in tarmac:
importance: Low → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.