Trac Plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Trac Plugin

Lerenc, Vedran
Trac Plugin

Hi,

I installed the Trac plugin and configured the "Trac website". However, I can't select "Trac" as "Repository browser". The problem is that I have not Subversion as SCM, but Perforce. In the Perforce plugin I can only select P4Web and Fisheye.

I am perfectly fine if I can't associate the build with the changelist/set and can't jump into the SCM. What I like is to jump to my Trac issue from the change description. However, since I installed the Trac plugin, Hudson (or the Perforce plugin?) is no longer showing any texts for the changes, i.e. I see my changes, but no text underneath. I guess the thing ran into a problem while parsing the text for my Trac issue number?

Is there a way to make it run for me with Perforce? I'd like to have my change descriptions back and if they contain Trac issue numbers (in the format #123), I'd like them to be hyperlinks to my Trac installation. Is this possible with my setup (Hudson, Trac, Perforce)?

Thank you in advance,
Regards,

Vedran

Reply | Threaded
Open this post in threaded view
|

Re: Trac Plugin

Kohsuke Kawaguchi
Administrator

So, you use Trac as an issue tracker and ignore the repository browser
part of it?

I guess I didn't think about that use case.

Lerenc, Vedran wrote:

> Hi,
>
> I installed the Trac plugin and configured the "Trac website". However, I can't
> select "Trac" as "Repository browser". The problem is that I have not Subversion
> as SCM, but Perforce. In the Perforce plugin I can only select P4Web and Fisheye.
>
> I am perfectly fine if I can't associate the build with the changelist/set and
> can't jump into the SCM. What I like is to jump to my Trac issue from the change
> description. However, since I installed the Trac plugin, Hudson (or the Perforce
> plugin?) is no longer showing any texts for the changes, i.e. I see my changes,
> but no text underneath. I guess the thing ran into a problem while parsing the
> text for my Trac issue number?
>
> Is there a way to make it run for me with Perforce? I'd like to have my change
> descriptions back and if they contain Trac issue numbers (in the format #123),
> I'd like them to be hyperlinks to my Trac installation. Is this possible with my
> setup (Hudson, Trac, Perforce)?
>
> Thank you in advance,
> Regards,
>
> Vedran
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Re: Trac Plugin

Lerenc, Vedran
Hi Kohsuke,

Well, I can't even tell what the repository browser is and there is not
much I can do with the Perforce plugin: It doesn't even offer Trac as an
option for a repository browser. :-(

Do I miss a lot?

Primarily I would like to click on the Trac issue number in the Hudson
change log and then end up in my Trac message. That would be very
helpful. :-)

Do we have to patch the Perforce plugin somehow to make it work for us?
Or does the Trac plugin need some modification?

Regards,

Vedran

-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Dienstag, 15. Juli 2008 19:03
To: [hidden email]
Subject: Re: Trac Plugin


So, you use Trac as an issue tracker and ignore the repository browser
part of it?

I guess I didn't think about that use case.

Lerenc, Vedran wrote:
> Hi,
>
> I installed the Trac plugin and configured the "Trac website".
However, I can't
> select "Trac" as "Repository browser". The problem is that I have not
Subversion
> as SCM, but Perforce. In the Perforce plugin I can only select P4Web
and Fisheye.
>
> I am perfectly fine if I can't associate the build with the
changelist/set and
> can't jump into the SCM. What I like is to jump to my Trac issue from
the change
> description. However, since I installed the Trac plugin, Hudson (or
the Perforce
> plugin?) is no longer showing any texts for the changes, i.e. I see my
changes,
> but no text underneath. I guess the thing ran into a problem while
parsing the
> text for my Trac issue number?
>
> Is there a way to make it run for me with Perforce? I'd like to have
my change
> descriptions back and if they contain Trac issue numbers (in the
format #123),
> I'd like them to be hyperlinks to my Trac installation. Is this
possible with my
> setup (Hudson, Trac, Perforce)?
>
> Thank you in advance,
> Regards,
>
> Vedran
>


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Trac Plugin

Kohsuke Kawaguchi
Administrator

My question was more toward how you use Trac.

When I think of Trac, it's a Subversion repository browser + issue
tracker combined. So that's why in Hudson the Trac support is kinda tied
to Subversion SCM.

I didn't realize that people are using Trac with something other than
Subversion, so I'm just guessing that maybe you use the issue tracker
part and ignore Trac as a repository browser completely.

AIU, Trac isn't capable of working with Perforce. But then, I'm not
really a Trac user, so I could be wrong. Hence my question.

Lerenc, Vedran wrote:

> Hi Kohsuke,
>
> Well, I can't even tell what the repository browser is and there is not
> much I can do with the Perforce plugin: It doesn't even offer Trac as an
> option for a repository browser. :-(
>
> Do I miss a lot?
>
> Primarily I would like to click on the Trac issue number in the Hudson
> change log and then end up in my Trac message. That would be very
> helpful. :-)
>
> Do we have to patch the Perforce plugin somehow to make it work for us?
> Or does the Trac plugin need some modification?
>
> Regards,
>
> Vedran
>
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:[hidden email]]
> Sent: Dienstag, 15. Juli 2008 19:03
> To: [hidden email]
> Subject: Re: Trac Plugin
>
>
> So, you use Trac as an issue tracker and ignore the repository browser
> part of it?
>
> I guess I didn't think about that use case.
>
> Lerenc, Vedran wrote:
>> Hi,
>>
>> I installed the Trac plugin and configured the "Trac website".
> However, I can't
>> select "Trac" as "Repository browser". The problem is that I have not
> Subversion
>> as SCM, but Perforce. In the Perforce plugin I can only select P4Web
> and Fisheye.
>>
>> I am perfectly fine if I can't associate the build with the
> changelist/set and
>> can't jump into the SCM. What I like is to jump to my Trac issue from
> the change
>> description. However, since I installed the Trac plugin, Hudson (or
> the Perforce
>> plugin?) is no longer showing any texts for the changes, i.e. I see my
> changes,
>> but no text underneath. I guess the thing ran into a problem while
> parsing the
>> text for my Trac issue number?
>>
>> Is there a way to make it run for me with Perforce? I'd like to have
> my change
>> descriptions back and if they contain Trac issue numbers (in the
> format #123),
>> I'd like them to be hyperlinks to my Trac installation. Is this
> possible with my
>> setup (Hudson, Trac, Perforce)?
>>
>> Thank you in advance,
>> Regards,
>>
>> Vedran
>>
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Re: Trac Plugin

Lerenc, Vedran
Hi Kohsuke,

I have Trac 10 installed. There is a Perforce plugin for Trac 11, but
since I am still on 10 I don't know how well it works.

Yes, there are some few groups in our company here and there using Trac,
but all of us use Perforce (about 1500 Java developers). So Trac is very
nice and makes also a lot of sense with Perforce. :-)

Hudson is cool! I have to admit that I am pretty impressed by it. We had
to rewrite the Perforce plugin completly (was working ok, but didn't
scale well and our IT folks complained almost immediately about ist
polling behaviour PLUS it had no changelist propagation to downstream
projects, so that you know why a downstream project was built and
possibly now fails), develop some publishers (for some of our own
proprietary stuff), but other than that, we could use Hudson out of the
box. It's really cool! Congratulations!

Thank you,
Cheers,

Vedran



-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Donnerstag, 17. Juli 2008 07:15
To: [hidden email]
Subject: Re: Trac Plugin


My question was more toward how you use Trac.

When I think of Trac, it's a Subversion repository browser + issue
tracker combined. So that's why in Hudson the Trac support is kinda tied

to Subversion SCM.

I didn't realize that people are using Trac with something other than
Subversion, so I'm just guessing that maybe you use the issue tracker
part and ignore Trac as a repository browser completely.

AIU, Trac isn't capable of working with Perforce. But then, I'm not
really a Trac user, so I could be wrong. Hence my question.

Lerenc, Vedran wrote:
> Hi Kohsuke,
>
> Well, I can't even tell what the repository browser is and there is
not
> much I can do with the Perforce plugin: It doesn't even offer Trac as
an
> option for a repository browser. :-(
>
> Do I miss a lot?
>
> Primarily I would like to click on the Trac issue number in the Hudson
> change log and then end up in my Trac message. That would be very
> helpful. :-)
>
> Do we have to patch the Perforce plugin somehow to make it work for
us?

> Or does the Trac plugin need some modification?
>
> Regards,
>
> Vedran
>
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:[hidden email]]
> Sent: Dienstag, 15. Juli 2008 19:03
> To: [hidden email]
> Subject: Re: Trac Plugin
>
>
> So, you use Trac as an issue tracker and ignore the repository browser

> part of it?
>
> I guess I didn't think about that use case.
>
> Lerenc, Vedran wrote:
>> Hi,
>>
>> I installed the Trac plugin and configured the "Trac website".
> However, I can't
>> select "Trac" as "Repository browser". The problem is that I have not
> Subversion
>> as SCM, but Perforce. In the Perforce plugin I can only select P4Web
> and Fisheye.
>>
>> I am perfectly fine if I can't associate the build with the
> changelist/set and
>> can't jump into the SCM. What I like is to jump to my Trac issue from
> the change
>> description. However, since I installed the Trac plugin, Hudson (or
> the Perforce
>> plugin?) is no longer showing any texts for the changes, i.e. I see
my

> changes,
>> but no text underneath. I guess the thing ran into a problem while
> parsing the
>> text for my Trac issue number?
>>
>> Is there a way to make it run for me with Perforce? I'd like to have
> my change
>> descriptions back and if they contain Trac issue numbers (in the
> format #123),
>> I'd like them to be hyperlinks to my Trac installation. Is this
> possible with my
>> setup (Hudson, Trac, Perforce)?
>>
>> Thank you in advance,
>> Regards,
>>
>> Vedran
>>
>
>


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Trac Plugin

digerata-3
Vedran,

I'm very curious to know what the scalability issue was with the  
Perforce plugin and what made you guys have to rewrite it.  The plugin  
is using the command line p4 client.  Also, what do you mean by  
changelist propagation?  Is this a feature you could possibly commit  
back to the hudson code base?

If you could provide some example URLs of how Trac issues are  
accessed, I could put together a Trac Repository Browser that provides  
links for issues but skips everything for the actual repository  
browsing.  I haven't used Trac or have access to one for testing.

Let me know,

-Mike

On Jul 17, 2008, at 3:57 AM, Lerenc, Vedran wrote:

> Hi Kohsuke,
>
> I have Trac 10 installed. There is a Perforce plugin for Trac 11, but
> since I am still on 10 I don't know how well it works.
>
> Yes, there are some few groups in our company here and there using  
> Trac,
> but all of us use Perforce (about 1500 Java developers). So Trac is  
> very
> nice and makes also a lot of sense with Perforce. :-)
>
> Hudson is cool! I have to admit that I am pretty impressed by it. We  
> had
> to rewrite the Perforce plugin completly (was working ok, but didn't
> scale well and our IT folks complained almost immediately about ist
> polling behaviour PLUS it had no changelist propagation to downstream
> projects, so that you know why a downstream project was built and
> possibly now fails), develop some publishers (for some of our own
> proprietary stuff), but other than that, we could use Hudson out of  
> the
> box. It's really cool! Congratulations!
>
> Thank you,
> Cheers,
>
> Vedran
>
>
>
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:[hidden email]]
> Sent: Donnerstag, 17. Juli 2008 07:15
> To: [hidden email]
> Subject: Re: Trac Plugin
>
>
> My question was more toward how you use Trac.
>
> When I think of Trac, it's a Subversion repository browser + issue
> tracker combined. So that's why in Hudson the Trac support is kinda  
> tied
>
> to Subversion SCM.
>
> I didn't realize that people are using Trac with something other than
> Subversion, so I'm just guessing that maybe you use the issue tracker
> part and ignore Trac as a repository browser completely.
>
> AIU, Trac isn't capable of working with Perforce. But then, I'm not
> really a Trac user, so I could be wrong. Hence my question.
>
> Lerenc, Vedran wrote:
>> Hi Kohsuke,
>>
>> Well, I can't even tell what the repository browser is and there is
> not
>> much I can do with the Perforce plugin: It doesn't even offer Trac as
> an
>> option for a repository browser. :-(
>>
>> Do I miss a lot?
>>
>> Primarily I would like to click on the Trac issue number in the  
>> Hudson
>> change log and then end up in my Trac message. That would be very
>> helpful. :-)
>>
>> Do we have to patch the Perforce plugin somehow to make it work for
> us?
>> Or does the Trac plugin need some modification?
>>
>> Regards,
>>
>> Vedran
>>
>> -----Original Message-----
>> From: Kohsuke Kawaguchi [mailto:[hidden email]]
>> Sent: Dienstag, 15. Juli 2008 19:03
>> To: [hidden email]
>> Subject: Re: Trac Plugin
>>
>>
>> So, you use Trac as an issue tracker and ignore the repository  
>> browser
>
>> part of it?
>>
>> I guess I didn't think about that use case.
>>
>> Lerenc, Vedran wrote:
>>> Hi,
>>>
>>> I installed the Trac plugin and configured the "Trac website".
>> However, I can't
>>> select "Trac" as "Repository browser". The problem is that I have  
>>> not
>> Subversion
>>> as SCM, but Perforce. In the Perforce plugin I can only select P4Web
>> and Fisheye.
>>>
>>> I am perfectly fine if I can't associate the build with the
>> changelist/set and
>>> can't jump into the SCM. What I like is to jump to my Trac issue  
>>> from
>> the change
>>> description. However, since I installed the Trac plugin, Hudson (or
>> the Perforce
>>> plugin?) is no longer showing any texts for the changes, i.e. I see
> my
>> changes,
>>> but no text underneath. I guess the thing ran into a problem while
>> parsing the
>>> text for my Trac issue number?
>>>
>>> Is there a way to make it run for me with Perforce? I'd like to have
>> my change
>>> descriptions back and if they contain Trac issue numbers (in the
>> format #123),
>>> I'd like them to be hyperlinks to my Trac installation. Is this
>> possible with my
>>> setup (Hudson, Trac, Perforce)?
>>>
>>> Thank you in advance,
>>> Regards,
>>>
>>> Vedran
>>>
>>
>>
>
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Re: Trac Plugin

Lerenc, Vedran
Hi Mike,

The main issue was about performance, not usability. The plugin runs
each time interval a -m25 and a -workspace query, which is pretty time
consuming. A -m1 is sufficient, fetching then only the descriptions of
the change lists in between the last checked and the latest changelist
number. Furthermore this happens per project. If you have hundreds of
them, the perforce server is under heavy load. One query is sufficient
per server. Furthermore, each project gets its own poller thread which
is also a problem with hundreds of projects. Bundling this into one
thread per perforce server makes it much more applicable. Our perforce
guys adviced us in how to cause the least possible load to the system
while still keeping a very brief check interval of one minute. If they
would have not complained, we wouldn't have done anything about it, but
they said they would close out our perforce users if we don't fix the
problem.

With changelist propagation I mean the following: When B depends on A
and you check something in for A and A is built and then later B is
built but fails, it is nice to see that B was built because of the
change to A and what this change was. This was something we built into
our new plugin: The changes are propagated to the downstream projects.
That's helpful.

There have been some other minor problems, I can't recall anymore. One
about the last changelist number and the archiving, leading the plugin
to believe that there was no latest changelist. With hundreds of
thousands of changes per project it started sending out e-mails to many
people. I remember this "effect" very well, much more than I do the
reason within the plugin anymore. :-(

Trac is open source. URL: http://trac.edgewall.org/. Tickets for Trac
itself in Trac: http://trac.edgewall.org/report/1

Regards,

Vedran



-----Original Message-----
From: K. Michael Wille [mailto:[hidden email]]
Sent: Dienstag, 22. Juli 2008 01:06
To: [hidden email]
Subject: Re: Trac Plugin

Vedran,

I'm very curious to know what the scalability issue was with the  
Perforce plugin and what made you guys have to rewrite it.  The plugin  
is using the command line p4 client.  Also, what do you mean by  
changelist propagation?  Is this a feature you could possibly commit  
back to the hudson code base?

If you could provide some example URLs of how Trac issues are  
accessed, I could put together a Trac Repository Browser that provides  
links for issues but skips everything for the actual repository  
browsing.  I haven't used Trac or have access to one for testing.

Let me know,

-Mike

On Jul 17, 2008, at 3:57 AM, Lerenc, Vedran wrote:

> Hi Kohsuke,
>
> I have Trac 10 installed. There is a Perforce plugin for Trac 11, but
> since I am still on 10 I don't know how well it works.
>
> Yes, there are some few groups in our company here and there using  
> Trac,
> but all of us use Perforce (about 1500 Java developers). So Trac is  
> very
> nice and makes also a lot of sense with Perforce. :-)
>
> Hudson is cool! I have to admit that I am pretty impressed by it. We  
> had
> to rewrite the Perforce plugin completly (was working ok, but didn't
> scale well and our IT folks complained almost immediately about ist
> polling behaviour PLUS it had no changelist propagation to downstream
> projects, so that you know why a downstream project was built and
> possibly now fails), develop some publishers (for some of our own
> proprietary stuff), but other than that, we could use Hudson out of  
> the
> box. It's really cool! Congratulations!
>
> Thank you,
> Cheers,
>
> Vedran
>
>
>
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:[hidden email]]
> Sent: Donnerstag, 17. Juli 2008 07:15
> To: [hidden email]
> Subject: Re: Trac Plugin
>
>
> My question was more toward how you use Trac.
>
> When I think of Trac, it's a Subversion repository browser + issue
> tracker combined. So that's why in Hudson the Trac support is kinda  
> tied
>
> to Subversion SCM.
>
> I didn't realize that people are using Trac with something other than
> Subversion, so I'm just guessing that maybe you use the issue tracker
> part and ignore Trac as a repository browser completely.
>
> AIU, Trac isn't capable of working with Perforce. But then, I'm not
> really a Trac user, so I could be wrong. Hence my question.
>
> Lerenc, Vedran wrote:
>> Hi Kohsuke,
>>
>> Well, I can't even tell what the repository browser is and there is
> not
>> much I can do with the Perforce plugin: It doesn't even offer Trac as
> an
>> option for a repository browser. :-(
>>
>> Do I miss a lot?
>>
>> Primarily I would like to click on the Trac issue number in the  
>> Hudson
>> change log and then end up in my Trac message. That would be very
>> helpful. :-)
>>
>> Do we have to patch the Perforce plugin somehow to make it work for
> us?
>> Or does the Trac plugin need some modification?
>>
>> Regards,
>>
>> Vedran
>>
>> -----Original Message-----
>> From: Kohsuke Kawaguchi [mailto:[hidden email]]
>> Sent: Dienstag, 15. Juli 2008 19:03
>> To: [hidden email]
>> Subject: Re: Trac Plugin
>>
>>
>> So, you use Trac as an issue tracker and ignore the repository  
>> browser
>
>> part of it?
>>
>> I guess I didn't think about that use case.
>>
>> Lerenc, Vedran wrote:
>>> Hi,
>>>
>>> I installed the Trac plugin and configured the "Trac website".
>> However, I can't
>>> select "Trac" as "Repository browser". The problem is that I have  
>>> not
>> Subversion
>>> as SCM, but Perforce. In the Perforce plugin I can only select P4Web
>> and Fisheye.
>>>
>>> I am perfectly fine if I can't associate the build with the
>> changelist/set and
>>> can't jump into the SCM. What I like is to jump to my Trac issue  
>>> from
>> the change
>>> description. However, since I installed the Trac plugin, Hudson (or
>> the Perforce
>>> plugin?) is no longer showing any texts for the changes, i.e. I see
> my
>> changes,
>>> but no text underneath. I guess the thing ran into a problem while
>> parsing the
>>> text for my Trac issue number?
>>>
>>> Is there a way to make it run for me with Perforce? I'd like to have
>> my change
>>> descriptions back and if they contain Trac issue numbers (in the
>> format #123),
>>> I'd like them to be hyperlinks to my Trac installation. Is this
>> possible with my
>>> setup (Hudson, Trac, Perforce)?
>>>
>>> Thank you in advance,
>>> Regards,
>>>
>>> Vedran
>>>
>>
>>
>
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Re: Trac Plugin

Erik Ramfelt
It seems that the problems with hundreds of job polling at the same
time could be solved by commit triggers? Have you looked into if
Perforce supports triggers on commits?


This question made me think that Hudson/SCMs could perhaps help out by
adding a "Commit trigger" trigger that when enabled activates a commit
trigger on the various SCMs. Disabling it would remove the commit
trigger. This requires adding SCM specific implementation but it would
be very nice if Hudson could help making the life for admins easier.
(But then again adding support for such feature for ClearCase is
probably not going to be simple)

//Erik

On Wed, Jul 23, 2008 at 12:18 PM, Lerenc, Vedran <[hidden email]> wrote:

> Hi Mike,
>
> The main issue was about performance, not usability. The plugin runs
> each time interval a -m25 and a -workspace query, which is pretty time
> consuming. A -m1 is sufficient, fetching then only the descriptions of
> the change lists in between the last checked and the latest changelist
> number. Furthermore this happens per project. If you have hundreds of
> them, the perforce server is under heavy load. One query is sufficient
> per server. Furthermore, each project gets its own poller thread which
> is also a problem with hundreds of projects. Bundling this into one
> thread per perforce server makes it much more applicable. Our perforce
> guys adviced us in how to cause the least possible load to the system
> while still keeping a very brief check interval of one minute. If they
> would have not complained, we wouldn't have done anything about it, but
> they said they would close out our perforce users if we don't fix the
> problem.
>
> With changelist propagation I mean the following: When B depends on A
> and you check something in for A and A is built and then later B is
> built but fails, it is nice to see that B was built because of the
> change to A and what this change was. This was something we built into
> our new plugin: The changes are propagated to the downstream projects.
> That's helpful.
>
> There have been some other minor problems, I can't recall anymore. One
> about the last changelist number and the archiving, leading the plugin
> to believe that there was no latest changelist. With hundreds of
> thousands of changes per project it started sending out e-mails to many
> people. I remember this "effect" very well, much more than I do the
> reason within the plugin anymore. :-(
>
> Trac is open source. URL: http://trac.edgewall.org/. Tickets for Trac
> itself in Trac: http://trac.edgewall.org/report/1
>
> Regards,
>
> Vedran
>
>
>
> -----Original Message-----
> From: K. Michael Wille [mailto:[hidden email]]
> Sent: Dienstag, 22. Juli 2008 01:06
> To: [hidden email]
> Subject: Re: Trac Plugin
>
> Vedran,
>
> I'm very curious to know what the scalability issue was with the
> Perforce plugin and what made you guys have to rewrite it.  The plugin
> is using the command line p4 client.  Also, what do you mean by
> changelist propagation?  Is this a feature you could possibly commit
> back to the hudson code base?
>
> If you could provide some example URLs of how Trac issues are
> accessed, I could put together a Trac Repository Browser that provides
> links for issues but skips everything for the actual repository
> browsing.  I haven't used Trac or have access to one for testing.
>
> Let me know,
>
> -Mike
>
> On Jul 17, 2008, at 3:57 AM, Lerenc, Vedran wrote:
>
>> Hi Kohsuke,
>>
>> I have Trac 10 installed. There is a Perforce plugin for Trac 11, but
>> since I am still on 10 I don't know how well it works.
>>
>> Yes, there are some few groups in our company here and there using
>> Trac,
>> but all of us use Perforce (about 1500 Java developers). So Trac is
>> very
>> nice and makes also a lot of sense with Perforce. :-)
>>
>> Hudson is cool! I have to admit that I am pretty impressed by it. We
>> had
>> to rewrite the Perforce plugin completly (was working ok, but didn't
>> scale well and our IT folks complained almost immediately about ist
>> polling behaviour PLUS it had no changelist propagation to downstream
>> projects, so that you know why a downstream project was built and
>> possibly now fails), develop some publishers (for some of our own
>> proprietary stuff), but other than that, we could use Hudson out of
>> the
>> box. It's really cool! Congratulations!
>>
>> Thank you,
>> Cheers,
>>
>> Vedran
>>
>>
>>
>> -----Original Message-----
>> From: Kohsuke Kawaguchi [mailto:[hidden email]]
>> Sent: Donnerstag, 17. Juli 2008 07:15
>> To: [hidden email]
>> Subject: Re: Trac Plugin
>>
>>
>> My question was more toward how you use Trac.
>>
>> When I think of Trac, it's a Subversion repository browser + issue
>> tracker combined. So that's why in Hudson the Trac support is kinda
>> tied
>>
>> to Subversion SCM.
>>
>> I didn't realize that people are using Trac with something other than
>> Subversion, so I'm just guessing that maybe you use the issue tracker
>> part and ignore Trac as a repository browser completely.
>>
>> AIU, Trac isn't capable of working with Perforce. But then, I'm not
>> really a Trac user, so I could be wrong. Hence my question.
>>
>> Lerenc, Vedran wrote:
>>> Hi Kohsuke,
>>>
>>> Well, I can't even tell what the repository browser is and there is
>> not
>>> much I can do with the Perforce plugin: It doesn't even offer Trac as
>> an
>>> option for a repository browser. :-(
>>>
>>> Do I miss a lot?
>>>
>>> Primarily I would like to click on the Trac issue number in the
>>> Hudson
>>> change log and then end up in my Trac message. That would be very
>>> helpful. :-)
>>>
>>> Do we have to patch the Perforce plugin somehow to make it work for
>> us?
>>> Or does the Trac plugin need some modification?
>>>
>>> Regards,
>>>
>>> Vedran
>>>
>>> -----Original Message-----
>>> From: Kohsuke Kawaguchi [mailto:[hidden email]]
>>> Sent: Dienstag, 15. Juli 2008 19:03
>>> To: [hidden email]
>>> Subject: Re: Trac Plugin
>>>
>>>
>>> So, you use Trac as an issue tracker and ignore the repository
>>> browser
>>
>>> part of it?
>>>
>>> I guess I didn't think about that use case.
>>>
>>> Lerenc, Vedran wrote:
>>>> Hi,
>>>>
>>>> I installed the Trac plugin and configured the "Trac website".
>>> However, I can't
>>>> select "Trac" as "Repository browser". The problem is that I have
>>>> not
>>> Subversion
>>>> as SCM, but Perforce. In the Perforce plugin I can only select P4Web
>>> and Fisheye.
>>>>
>>>> I am perfectly fine if I can't associate the build with the
>>> changelist/set and
>>>> can't jump into the SCM. What I like is to jump to my Trac issue
>>>> from
>>> the change
>>>> description. However, since I installed the Trac plugin, Hudson (or
>>> the Perforce
>>>> plugin?) is no longer showing any texts for the changes, i.e. I see
>> my
>>> changes,
>>>> but no text underneath. I guess the thing ran into a problem while
>>> parsing the
>>>> text for my Trac issue number?
>>>>
>>>> Is there a way to make it run for me with Perforce? I'd like to have
>>> my change
>>>> descriptions back and if they contain Trac issue numbers (in the
>>> format #123),
>>>> I'd like them to be hyperlinks to my Trac installation. Is this
>>> possible with my
>>>> setup (Hudson, Trac, Perforce)?
>>>>
>>>> Thank you in advance,
>>>> Regards,
>>>>
>>>> Vedran
>>>>
>>>
>>>
>>
>>
>> --
>> Kohsuke Kawaguchi
>> Sun Microsystems                   [hidden email]
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]