done, welcome a board! Domi
On 06.10.2014, at 07:49, Krishna Kishore <[email protected]> wrote: > Hi Domi, > > Thanks for creating the repository. I just signed up in the issue tracker > and my userid in JIRA is "clkkishore", please created the required component. > > Thanks, > Kishore > > On Friday, 3 October 2014 11:08:05 UTC+5:30, Dominik Bartholdi wrote: > done: https://github.com/jenkinsci/teamconcert-git-plugin > but creating a component for you in the issue tracker failed, what is your > userid in JIRA? > > ...I don't have permission to create a CI job, can someone else create one? > Domi > > > On 03.10.2014, at 06:19, Krishna Kishore <[email protected]> wrote: > >> Hi Jenkins Dev Team, >> >> Any update on my request to host a new plugin. >> >> Thanks, >> Kishore >> >> >> On Monday, 29 September 2014 14:46:39 UTC+5:30, Krishna Kishore wrote: >> Due to different dependencies we decided not to extend the functionality of >> the existing plugin but write a new plugin. The existing plugin implements >> the SCM extension point of Jenkins and the new plugin is much more lighter >> and uses the Build extension point. The target audience for the two plugins >> is also different. Their are some common aspects and we are looking a best >> ways to create a common layer that can be used by the two plugins. >> >> Thanks, >> Kishore >> >> On Monday, 29 September 2014 11:03:54 UTC+5:30, Dominik Bartholdi wrote: >> How about extending the existing one with your functionality? >> From a users point of view this is what I would love to see - as I guess you >> would provite of some of the existing features too >> Or maybe extract the parts the two plugins would have in common and create a >> base plugin which can be extended by implementing EPs >> Domi >> >> On 28.09.2014, at 16:01, Krishna Kishore <[email protected]> wrote: >> >>> Hi, >>> >>> The existing plugin woks with the RTC Source control, it helps teams which >>> use RTC as SCC and Jenkins as CI engine. The new plugin will work with >>> projects which use Git as source control and integrate (i.e create >>> traceability links) Jenkins builds with RTC Work Items and Builds. This >>> plugin is for teams which use Git as Source control and want to use RTC for >>> Tracking and Planning. >>> >>> Thanks, >>> Kishore >>> >>> On Sunday, 28 September 2014 12:37:47 UTC+5:30, Dominik Bartholdi wrote: >>> How is this one different to the existing teamconcert plugin? [1] >>> It seems very active. >>> Domi >>> >>> [1] https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin >>> >>> Am 28.09.2014 um 06:09 schrieb Krishna Kishore <[email protected]>: >>> >>>> Hi Jenkins Dev team, >>>> >>>> I am with the Rational Team Concert(RTC) Development team in IBM >>>> (www.ibm.com, www.jazz.net). We are developing a plugin which will >>>> integrate Jenkins Builds using Git as Source control to RTC Work items and >>>> builds. We would like to publish the plugin at jenkins-ci.org. Here are >>>> the details related to plugin >>>> >>>> Plugin Name: Team Concert Git Plugin >>>> Github Repository: https://github.com/clkkishore/teamconcert-git-plugin >>>> Github id: clkkishore >>>> Plugin Description: Integrates Jenkins with Rational Team Concert for >>>> Jenkins Builds which use Git as source control. This plugin will create >>>> traceability links from a Jenkins build to RTC work items and build result. >>>> >>>> Can someone please clone this to jenkinsci and provide me access for the >>>> same. >>>> >>>> Thanks In advance, >>>> >>>> Regards, >>>> Kishore >>>> >>>> PS: Currently the project >>>> https://github.com/clkkishore/teamconcert-git-plugin contains only a >>>> readme file will add the sources once the repository is cloned into >>>> jenkinssci space. >>>> >>>> >>>> -- >>>> 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/d/optout. >>> >>> >>> -- >>> 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/d/optout. >> >> >> -- >> 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/d/optout. > > > -- > 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/d/optout. -- 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/d/optout.
