On Jun 2, 11:41 am, Roger Oberholtzer
wrote:
> On Tue, 2009-06-02 at 05:33 -0700, Steve Povilaitis wrote:
> > I'm sure Bitten and Buildbot are fine tools, but I haven't used them,
> > so I won't compare them to Hudson. What I like about Hudson is the
> > large number of plugins, tight integrati
On Tue, 2009-06-02 at 05:33 -0700, Steve Povilaitis wrote:
> I'm sure Bitten and Buildbot are fine tools, but I haven't used them,
> so I won't compare them to Hudson. What I like about Hudson is the
> large number of plugins, tight integration with SVN and Trac, ease of
> installation, and confi
On Jun 1, 12:10 pm, Olemis Lang wrote:
> On Mon, Jun 1, 2009 at 7:08 AM, Steve Povilaitis wrote:
>
> >> Date: Sun, May 31 2009 6:52 pm
> >> From: Johnny Chang
>
> >> Hello, I just started using trac with svn and it is very nice. I
> >> wanted to implement some build and test automation into it
Quoting "Olemis Lang" :
> - How stable is Bitten ? Is it ok to try it out right now or should I
> wait a little ?
Despite some minor points at installation time (I had to change some
database table field types), bitten runs fine.
--~--~-~--~~~---~--~~
You receive
On Mon, Jun 1, 2009 at 7:08 AM, Steve Povilaitis wrote:
>
>> Date: Sun, May 31 2009 6:52 pm
>> From: Johnny Chang
>>
>> Hello, I just started using trac with svn and it is very nice. I
>> wanted to implement some build and test automation into it and was
>> looking for these features:
>>
>> -che
> == 1 of 2 ==
> Date: Sun, May 31 2009 6:52 pm
> From: Johnny Chang
>
>
> Hello, I just started using trac with svn and it is very nice. I
> wanted to implement some build and test automation into it and was
> looking for these features:
>
> -checks out code
> -builds and checks for errors
> -ru
Matthew Gillen wrote:
> Mike wrote:
>> Matthew Gillen wrote:
>>> site up for my project, that's it. I leverage my department's sys-admins by
>>> using (via mod_pam) the user-database that they have to maintain anyway (on
>>> their own budget). etc, etc.
>>>
>> Do you have a recipe or a link on h
Mike wrote:
>
> Matthew Gillen wrote:
>> site up for my project, that's it. I leverage my department's sys-admins by
>> using (via mod_pam) the user-database that they have to maintain anyway (on
>> their own budget). etc, etc.
>>
> Do you have a recipe or a link on how to set up mod_pam with A
Matthew Gillen wrote:
> site up for my project, that's it. I leverage my department's sys-admins by
> using (via mod_pam) the user-database that they have to maintain anyway (on
> their own budget). etc, etc.
>
Do you have a recipe or a link on how to set up mod_pam with Apache 2.2
by any chanc
On Friday 03 November 2006 09:17, Christian Boos wrote:
> James Mohr wrote:
> > ...
> > What is the antecedent and what is the conclusion?
> > - I need this application so I will write it in Python
> > - Python is better than PHP so I need to write a bug tracker in Python
>
> Well, I see where you
James Mohr wrote:
> ...
> What is the antecedent and what is the conclusion?
> - I need this application so I will write it in Python
> - Python is better than PHP so I need to write a bug tracker in Python
>
Well, I see where you're heading to here, but no, Trac is not written by
Python zea
> Do you have to use them?
I need a bug tracker. I could not work without it, we have too many
issues and features to track down. Obviously, it has to be somewhat
integrated with the source control management system. SVN+Trac is a
really great couple for medium-sized projects.
> What is the ante
James Mohr wrote:
> On Wednesday 01 November 2006 15:08, Emmanuel Blot wrote:
>>> As far as I can see, you can. If "restrict_owner=false", then I can put
>>> any user into the "assign to" field I want and a ticket is created.
>> Perhaps I misunderstood what you were looking for.
>> Trac is an open
On Thursday 02 November 2006 14:37, Emmanuel Blot wrote:
> > Perhaps it would be better to have asked what Trac brings you that an
> > intergration of existing tools does not. For example, there is already an
> > integration of Bugzilla, MediaWiki and various CVS packages.
>
> Well, from my perspe
On Thu, Nov 02, 2006 at 10:18:07AM -0500, Matthew Gillen wrote:
> coordinate three user databases, etc. One of the key features of Trac for me
> is that I, as a developer on a project, can spend 5 minutes getting a trac
> site up for my project, that's it. I leverage my department's sys-admins
James Mohr wrote:
> There are enough open source projects with there own authentication, so you
> would not be re-inventing the wheel. Further, most of the problems lie not in
> the authentication mechanism, but failures in the rest of the code (i.e. SQL
> injection, assuming that if particular
> My assumption was that since there is an Emmanuel Blot on the development team
> you are he and that being part of the development team you would consider it
> "your" project. (Whether or not you started it)
Indeed, "we" are the same person, I try to participate, but I do not
consider the proje
James Mohr wrote:
> On Wednesday 01 November 2006 15:08, Emmanuel Blot wrote:
> The question is whether or not I can *assign* a ticket to a non existant
> user.
> Although allowing anonymous users to add tickets or leaving the assignment
> field blank might be a good thing in certain circumstan
On Thursday 02 November 2006 12:34, Emmanuel Blot wrote:
> > It's your project. You develop it the way you see it. Just as I write the
> > way I see it.
>
> There's a misunderstanding here: it is not "my" project, I'm just
> another *user* of Trac.
My assumption was that since there is an Emmanu
> The question is whether or not I can *assign* a ticket to a non existant user.
For now, there are only two settings available:
1/ prefilled-list of existing user (in this case, the answer to your
question is no)
2/ free text (in this case, the answer to your question is yes)
I don't know w
On Wednesday 01 November 2006 15:08, Emmanuel Blot wrote:
> > As far as I can see, you can. If "restrict_owner=false", then I can put
> > any user into the "assign to" field I want and a ticket is created.
>
> Perhaps I misunderstood what you were looking for.
> Trac is an open system: the default
You can restrict_ticket_owner in trac.ini and it will show a dropdown of users
that have previously logged in in the assign to field.
As far as user authentication, what are you looking for? Whatever it is, there
is probably a way to implement it with apache...
Russ
Sent wirelessly via BlackBe
> As far as I can see, you can. If "restrict_owner=false", then I can put any
> user into the "assign to" field I want and a ticket is created.
Perhaps I misunderstood what you were looking for.
Trac is an open system: the default behaviour is to allow any user -
even unknown users - to create or
On Wednesday 01 November 2006 12:13, Emmanuel Blot wrote:
> > As far as I get tell, the only understanding Trac has in terms of users
> > is for authorization to various functions. That is, there is no list of
> > user to which you can assign a ticket. As a result, one could assign the
> > ticket
On Wednesday 01 November 2006 12:01, Rainer Sokoll wrote:
> On Wed, Nov 01, 2006 at 12:45:55PM +0100, James Mohr wrote:
> > As far as I get tell, the only understanding Trac has in terms of users
> > is for authorization to various functions. That is, there is no list of
> > user to which you can
> As far as I get tell, the only understanding Trac has in terms of users is for
> authorization to various functions. That is, there is no list of user to
> which you can assign a ticket. As a result, one could assign the ticket to
> Anyone, even people who do not have access to the system.
Not
On Wed, Nov 01, 2006 at 12:45:55PM +0100, James Mohr wrote:
> As far as I get tell, the only understanding Trac has in terms of users is
> for
> authorization to various functions. That is, there is no list of user to
> which you can assign a ticket. As a result, one could assign the ticket to
27 matches
Mail list logo
