Hi Paul,

I'm glad to hear that Borland is planning to work on the Jenkins plugin for
StarTeam. I've been thinking about updating the plugin to the newest
Jenkins SCM plugin interface, as I've received some internal bug reports
about build change sets being incomplete/incorrect and I am hoping that
using the new interface will help, though I have done very little research
at this point.

I started a branch to update to SDK 13.0 last May. You can see my progress
at https://github.com/patrick-higgins/starteam-plugin/tree/sdk13.0. It has
been long enough that I don't recall the state of that branch. It may or
may not be functioning.

I've been thinking about the best way to handle the SDK upgrade. Do you
have any internal metrics about how many StarTeam installations can use the
new SDK?

The options I have thought of are:


   1. Requiring a new SDK for 0.7.0 (or whatever the next major version
   bump will be).
   2. Forking the plugin to allow parallel development for the old and new
   SDK.
   3. Support both new and old SDK within a single plugin code base.

Option #1 seems like the most straightforward, but without usage numbers
I'm not sure how realistic it is.

Glad to have you!

--Patrick


On Thu, Feb 6, 2014 at 8:56 AM, Paul Adamson <[email protected]> wrote:

> Hi Folks,
>
> I work on starteam at Borland and my team has been given some time (and
> code) to contribute to the jenkins starteam-plugin.
>
> I've been talking to the plugin lead Jan Ruzicka and he's really
> enthusiastic about having us on board - so I want to put out a call for
> anyone else on the list who has an interest in the development of this
> plugin as we get it flying again.
>
> I noticed Patrick Higgins made a rare contribution to the starteam plugin
> recently - so a special 'Hi' to you!
>
> Regards,
> Paul
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to