Indeed we are focusing on the same use case. What kind of collaboration did you have in mind?
BTW, i already checked and my plugin is compatible with yours:
You can define a build flow job - mark it as a template and place someparameter pattern => you'll get a nice UI with my plugin to create build flow jobs:
interesting. So your plugin is more about creating templates to simplify
workflow configuration, with few parameters and UI candy.
I'd be pleased to look how you manage jobs orchestration, as this is the
most annoying part of build flow plugin today. I'd like it to be
"continuable", so a flow can restart after some job have completed, either
due to jenkins restart, or manual re-trigger after some step failure, etc.
Today this is only a basic Job.schedule() orchestrator. Maybe will require
me to improve my groovy skills :)
> Indeed we are focusing on the same use case. What kind of collaboration
> did you have in mind?
> BTW, i already checked and my plugin is compatible with yours:
> You can define a build flow job - mark it as a template and place someparameter pattern => you'll get a nice UI with my plugin to create build
> flow jobs:
> Shai
> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
My plugin is all about "template workflow" definitions and how easy it is to create and manage a workflow from a template. The plugin uses jenkins existing plugins in order to do that, so whatever can be accomplished using a regular jobs chaining and plugins configuration can be placed under a "template workflow" and could be created/ edit/ deleted/ execute all using custom parameters.
Sounds interesting this "continuable" concept... I'm not handling it simply cause its not supported in jenkins core and no one wrote a plugin to do that.
I will create the repo and upload my code later, so you could have a look.
On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loof wrote:
> interesting. So your plugin is more about creating templates to simplify > workflow configuration, with few parameters and UI candy. > I'd be pleased to look how you manage jobs orchestration, as this is the > most annoying part of build flow plugin today. I'd like it to be " > continuable", so a flow can restart after some job have completed, either > due to jenkins restart, or manual re-trigger after some step failure, > etc. Today this is only a basic Job.schedule() orchestrator. Maybe will > require me to improve my groovy skills :)
>> Indeed we are focusing on the same use case. What kind of collaboration >> did you have in mind?
>> BTW, i already checked and my plugin is compatible with yours:
>> You can define a build flow job - mark it as a template and place someparameter pattern => you'll get a nice UI with my plugin to create build >> flow jobs:
>> Shai >> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com> wrote:
> My plugin is all about "template workflow" definitions and how easy it is
> to create and manage a workflow from a template.
> The plugin uses jenkins existing plugins in order to do that, so whatever
> can be accomplished using a regular jobs chaining and plugins
> configuration can be placed under a "template workflow" and could be
> created/ edit/ deleted/ execute all using custom parameters.
> Sounds interesting this "continuable" concept... I'm not handling it
> simply cause its not supported in jenkins core and no one wrote a plugin
> to do that.
> I will create the repo and upload my code later, so you could have a look.
> Shai
> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loof wrote:
>> interesting. So your plugin is more about creating templates to simplify
>> workflow configuration, with few parameters and UI candy.
>> I'd be pleased to look how you manage jobs orchestration, as this is the
>> most annoying part of build flow plugin today. I'd like it to be "
>> continuable", so a flow can restart after some job have completed,
>> either due to jenkins restart, or manual re-trigger after some step
>> failure, etc. Today this is only a basic Job.schedule() orchestrator.
>> Maybe will require me to improve my groovy skills :)
>>> Indeed we are focusing on the same use case. What kind of collaboration
>>> did you have in mind?
>>> BTW, i already checked and my plugin is compatible with yours:
>>> You can define a build flow job - mark it as a template and place someparameter pattern => you'll get a nice UI with my plugin to create build
>>> flow jobs:
>>> Shai
>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com> wrote:
>> My plugin is all about "template workflow" definitions and how easy it is
>> to create and manage a workflow from a template.
>> The plugin uses jenkins existing plugins in order to do that, so
>> whatever can be accomplished using a regular jobs chaining and plugins
>> configuration can be placed under a "template workflow" and could be
>> created/ edit/ deleted/ execute all using custom parameters.
>> Sounds interesting this "continuable" concept... I'm not handling it
>> simply cause its not supported in jenkins core and no one wrote a plugin
>> to do that.
>> I will create the repo and upload my code later, so you could have a
>> look.
>> Shai
>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loof wrote:
>>> interesting. So your plugin is more about creating templates to simplify
>>> workflow configuration, with few parameters and UI candy.
>>> I'd be pleased to look how you manage jobs orchestration, as this is the
>>> most annoying part of build flow plugin today. I'd like it to be "
>>> continuable", so a flow can restart after some job have completed,
>>> either due to jenkins restart, or manual re-trigger after some step
>>> failure, etc. Today this is only a basic Job.schedule() orchestrator.
>>> Maybe will require me to improve my groovy skills :)
>>>> Indeed we are focusing on the same use case. What kind of collaboration
>>>> did you have in mind?
>>>> BTW, i already checked and my plugin is compatible with yours:
>>>> You can define a build flow job - mark it as a template and place someparameter pattern => you'll get a nice UI with my plugin to create build
>>>> flow jobs:
>>>> Shai
>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
Thanks for that Nicolas.
When I'm trying to release my plugin in hangs on the maven release with
this line:
[INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
github.com/jenkinsci/template-workflows-plugin.git master:master"
[INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
any idea?
On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof
<nicolas.del...@gmail.com>wrote:
>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com>wrote:
>>> My plugin is all about "template workflow" definitions and how easy it
>>> is to create and manage a workflow from a template.
>>> The plugin uses jenkins existing plugins in order to do that, so
>>> whatever can be accomplished using a regular jobs chaining and plugins
>>> configuration can be placed under a "template workflow" and could be
>>> created/ edit/ deleted/ execute all using custom parameters.
>>> Sounds interesting this "continuable" concept... I'm not handling it
>>> simply cause its not supported in jenkins core and no one wrote a
>>> plugin to do that.
>>> I will create the repo and upload my code later, so you could have a
>>> look.
>>> Shai
>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loof wrote:
>>>> interesting. So your plugin is more about creating templates to
>>>> simplify workflow configuration, with few parameters and UI candy.
>>>> I'd be pleased to look how you manage jobs orchestration, as this is
>>>> the most annoying part of build flow plugin today. I'd like it to be "
>>>> continuable", so a flow can restart after some job have completed,
>>>> either due to jenkins restart, or manual re-trigger after some step
>>>> failure, etc. Today this is only a basic Job.schedule() orchestrator.
>>>> Maybe will require me to improve my groovy skills :)
>>>>> Indeed we are focusing on the same use case. What kind of
>>>>> collaboration did you have in mind?
>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>> You can define a build flow job - mark it as a template and place someparameter pattern => you'll get a nice UI with my plugin to create build
>>>>> flow jobs:
>>>>> Shai
>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
Hey Nicolas, I need some help uploading my plugin...
I'm using windows (don't ask...) and the maven release fails on
githubauthentication.
Im getting the same behavior from my shell (cmd):
C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
Hi shaibe! You've successfully authenticated, but GitHub does not provide
shell access.
E:\gitHub\template-workflows-jenkins-plugin>git push ssh://shaibe:shai***@
github.com/jenkinsci/template-workflows-plugin.git master:master
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Which user and pw should I use? the github or the jenkins?
Do you have any suggestions (besides switching to unix)?
On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com> wrote:
> Thanks for that Nicolas.
> When I'm trying to release my plugin in hangs on the maven release with
> this line:
> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
> github.com/jenkinsci/template-workflows-plugin.git master:master"
> [INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
> any idea?
> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <nicolas.del...@gmail.com
> > wrote:
>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com>wrote:
>>>> My plugin is all about "template workflow" definitions and how easy it
>>>> is to create and manage a workflow from a template.
>>>> The plugin uses jenkins existing plugins in order to do that, so
>>>> whatever can be accomplished using a regular jobs chaining and plugins
>>>> configuration can be placed under a "template workflow" and could be
>>>> created/ edit/ deleted/ execute all using custom parameters.
>>>> Sounds interesting this "continuable" concept... I'm not handling it
>>>> simply cause its not supported in jenkins core and no one wrote a
>>>> plugin to do that.
>>>> I will create the repo and upload my code later, so you could have a
>>>> look.
>>>> Shai
>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loof wrote:
>>>>> interesting. So your plugin is more about creating templates to
>>>>> simplify workflow configuration, with few parameters and UI candy.
>>>>> I'd be pleased to look how you manage jobs orchestration, as this is
>>>>> the most annoying part of build flow plugin today. I'd like it to be "
>>>>> continuable", so a flow can restart after some job have completed,
>>>>> either due to jenkins restart, or manual re-trigger after some step
>>>>> failure, etc. Today this is only a basic Job.schedule() orchestrator.
>>>>> Maybe will require me to improve my groovy skills :)
>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>> collaboration did you have in mind?
>>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>>> You can define a build flow job - mark it as a template and place
>>>>>> some parameter pattern => you'll get a nice UI with my plugin to
>>>>>> create build flow jobs:
>>>>>> Shai
>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
> Hey Nicolas, I need some help uploading my plugin...
> I'm using windows (don't ask...) and the maven release fails on githubauthentication.
> Im getting the same behavior from my shell (cmd):
> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
> Hi shaibe! You've successfully authenticated, but GitHub does not provide
> shell access.
> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://shaibe:shai***@
> github.com/jenkinsci/template-workflows-plugin.git master:master
> Permission denied (publickey).
> fatal: The remote end hung up unexpectedly
> Which user and pw should I use? the github or the jenkins?
> Do you have any suggestions (besides switching to unix)?
> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com> wrote:
>> Thanks for that Nicolas.
>> When I'm trying to release my plugin in hangs on the maven release with
>> this line:
>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>> [INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
>> any idea?
>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com>wrote:
>>>>> My plugin is all about "template workflow" definitions and how easy it
>>>>> is to create and manage a workflow from a template.
>>>>> The plugin uses jenkins existing plugins in order to do that, so
>>>>> whatever can be accomplished using a regular jobs chaining and
>>>>> plugins configuration can be placed under a "template workflow" and could
>>>>> be created/ edit/ deleted/ execute all using custom parameters.
>>>>> Sounds interesting this "continuable" concept... I'm not handling it
>>>>> simply cause its not supported in jenkins core and no one wrote a
>>>>> plugin to do that.
>>>>> I will create the repo and upload my code later, so you could have a
>>>>> look.
>>>>> Shai
>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loof wrote:
>>>>>> interesting. So your plugin is more about creating templates to
>>>>>> simplify workflow configuration, with few parameters and UI candy.
>>>>>> I'd be pleased to look how you manage jobs orchestration, as this is
>>>>>> the most annoying part of build flow plugin today. I'd like it to be "
>>>>>> continuable", so a flow can restart after some job have completed,
>>>>>> either due to jenkins restart, or manual re-trigger after some step
>>>>>> failure, etc. Today this is only a basic Job.schedule() orchestrator.
>>>>>> Maybe will require me to improve my groovy skills :)
>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>> collaboration did you have in mind?
>>>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>>>> You can define a build flow job - mark it as a template and place
>>>>>>> some parameter pattern => you'll get a nice UI with my plugin to
>>>>>>> create build flow jobs:
>>>>>>> Shai
>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
Thanks for the quick response, now i'm getting this:
E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
g...@github.com/jenkinsci/template-workflows-plugin.git master:master
ERROR: Permission to jenkinsci/template-workflows-plugin.git denied to
shaibe.
fatal: The remote end hung up unexpectedly
also, the maven release generated the ssh with my user and pw, should i remove
the user and pw parameters?
Shai
On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof
<nicolas.del...@gmail.com>wrote:
> don't use ssh://shaibe:shai***@
> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
> github.com/jenkinsci/template-workflows-plugin.git
> you're identified/authenticated on github by your ssh key, and all git
> commands connect as "git"
>> Hey Nicolas, I need some help uploading my plugin...
>> I'm using windows (don't ask...) and the maven release fails on githubauthentication.
>> Im getting the same behavior from my shell (cmd):
>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>> Hi shaibe! You've successfully authenticated, but GitHub does not
>> provide shell access.
>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://shaibe:shai***@
>> github.com/jenkinsci/template-workflows-plugin.git master:master
>> Permission denied (publickey).
>> fatal: The remote end hung up unexpectedly
>> Which user and pw should I use? the github or the jenkins?
>> Do you have any suggestions (besides switching to unix)?
>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com> wrote:
>>> Thanks for that Nicolas.
>>> When I'm trying to release my plugin in hangs on the maven release with
>>> this line:
>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>>> [INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
>>> any idea?
>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com>wrote:
>>>>>> My plugin is all about "template workflow" definitions and how easy
>>>>>> it is to create and manage a workflow from a template.
>>>>>> The plugin uses jenkins existing plugins in order to do that, so
>>>>>> whatever can be accomplished using a regular jobs chaining and
>>>>>> plugins configuration can be placed under a "template workflow" and could
>>>>>> be created/ edit/ deleted/ execute all using custom parameters.
>>>>>> Sounds interesting this "continuable" concept... I'm not handling it
>>>>>> simply cause its not supported in jenkins core and no one wrote a
>>>>>> plugin to do that.
>>>>>> I will create the repo and upload my code later, so you could have a
>>>>>> look.
>>>>>> Shai
>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loof wrote:
>>>>>>> interesting. So your plugin is more about creating templates to
>>>>>>> simplify workflow configuration, with few parameters and UI candy.
>>>>>>> I'd be pleased to look how you manage jobs orchestration, as this is
>>>>>>> the most annoying part of build flow plugin today. I'd like it to be "
>>>>>>> continuable", so a flow can restart after some job have completed,
>>>>>>> either due to jenkins restart, or manual re-trigger after some step
>>>>>>> failure, etc. Today this is only a basic Job.schedule() orchestrator.
>>>>>>> Maybe will require me to improve my groovy skills :)
>>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>>> collaboration did you have in mind?
>>>>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>>>>> You can define a build flow job - mark it as a template and place
>>>>>>>> some parameter pattern => you'll get a nice UI with my plugin to
>>>>>>>> create build flow jobs:
>>>>>>>> Shai
>>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
> Thanks for the quick response, now i'm getting this:
> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
> g...@github.com/jenkinsci/template-workflows-plugin.git master:master
> ERROR: Permission to jenkinsci/template-workflows-plugin.git denied to
> shaibe.
> fatal: The remote end hung up unexpectedly
> also, the maven release generated the ssh with my user and pw, should i remove
> the user and pw parameters?
> Shai
> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
> nicolas.del...@gmail.com> wrote:
>> don't use ssh://shaibe:shai***@
>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>> github.com/jenkinsci/template-workflows-plugin.git
>> you're identified/authenticated on github by your ssh key, and all git
>> commands connect as "git"
>>> Hey Nicolas, I need some help uploading my plugin...
>>> I'm using windows (don't ask...) and the maven release fails on githubauthentication.
>>> Im getting the same behavior from my shell (cmd):
>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>> Hi shaibe! You've successfully authenticated, but GitHub does not
>>> provide shell access.
>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>> ssh://shaibe:shai...@github.com/jenkinsci/template-workflows-plugin.gitmaster:master
>>> Permission denied (publickey).
>>> fatal: The remote end hung up unexpectedly
>>> Which user and pw should I use? the github or the jenkins?
>>> Do you have any suggestions (besides switching to unix)?
>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com> wrote:
>>>> Thanks for that Nicolas.
>>>> When I'm trying to release my plugin in hangs on the maven release with
>>>> this line:
>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>>>> [INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
>>>> any idea?
>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>> nicolas.del...@gmail.com> wrote:
>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com>wrote:
>>>>>>> My plugin is all about "template workflow" definitions and how easy
>>>>>>> it is to create and manage a workflow from a template.
>>>>>>> The plugin uses jenkins existing plugins in order to do that, so
>>>>>>> whatever can be accomplished using a regular jobs chaining and
>>>>>>> plugins configuration can be placed under a "template workflow" and could
>>>>>>> be created/ edit/ deleted/ execute all using custom parameters.
>>>>>>> Sounds interesting this "continuable" concept... I'm not handling
>>>>>>> it simply cause its not supported in jenkins core and no one wrote
>>>>>>> a plugin to do that.
>>>>>>> I will create the repo and upload my code later, so you could have
>>>>>>> a look.
>>>>>>> Shai
>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loof wrote
>>>>>>> :
>>>>>>>> interesting. So your plugin is more about creating templates to
>>>>>>>> simplify workflow configuration, with few parameters and UI candy.
>>>>>>>> I'd be pleased to look how you manage jobs orchestration, as this
>>>>>>>> is the most annoying part of build flow plugin today. I'd like it to be "
>>>>>>>> continuable", so a flow can restart after some job have completed,
>>>>>>>> either due to jenkins restart, or manual re-trigger after some
>>>>>>>> step failure, etc. Today this is only a basic Job.schedule()
>>>>>>>> orchestrator. Maybe will require me to improve my groovy skills :)
>>>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>>>> collaboration did you have in mind?
>>>>>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>>>>>> You can define a build flow job - mark it as a template and place
>>>>>>>>> some parameter pattern => you'll get a nice UI with my plugin to
>>>>>>>>> create build flow jobs:
>>>>>>>>> Shai
>>>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
E:\gitHub\template-workflows-jenkins-plugin>git push jenkins master
ERROR: Permission to jenkinsci/template-workflows-plugin.git denied to
shaibe.
fatal: The remote end hung up unexpectedly
On Wed, Aug 15, 2012 at 1:24 PM, nicolas de loof
<nicolas.del...@gmail.com>wrote:
>> Thanks for the quick response, now i'm getting this:
>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>> g...@github.com/jenkinsci/template-workflows-plugin.git master:master
>> ERROR: Permission to jenkinsci/template-workflows-plugin.git denied to
>> shaibe.
>> fatal: The remote end hung up unexpectedly
>> also, the maven release generated the ssh with my user and pw, should i remove
>> the user and pw parameters?
>> Shai
>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>> don't use ssh://shaibe:shai***@
>>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>>> github.com/jenkinsci/template-workflows-plugin.git
>>> you're identified/authenticated on github by your ssh key, and all git
>>> commands connect as "git"
>>>> Hey Nicolas, I need some help uploading my plugin...
>>>> I'm using windows (don't ask...) and the maven release fails on githubauthentication.
>>>> Im getting the same behavior from my shell (cmd):
>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>> Hi shaibe! You've successfully authenticated, but GitHub does not
>>>> provide shell access.
>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>> ssh://shaibe:shai...@github.com/jenkinsci/template-workflows-plugin.gitmaster:master
>>>> Permission denied (publickey).
>>>> fatal: The remote end hung up unexpectedly
>>>> Which user and pw should I use? the github or the jenkins?
>>>> Do you have any suggestions (besides switching to unix)?
>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com>wrote:
>>>>> Thanks for that Nicolas.
>>>>> When I'm trying to release my plugin in hangs on the maven release
>>>>> with this line:
>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>>>>> [INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
>>>>> any idea?
>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com>wrote:
>>>>>>>> My plugin is all about "template workflow" definitions and how easy
>>>>>>>> it is to create and manage a workflow from a template.
>>>>>>>> The plugin uses jenkins existing plugins in order to do that, so
>>>>>>>> whatever can be accomplished using a regular jobs chaining and
>>>>>>>> plugins configuration can be placed under a "template workflow" and could
>>>>>>>> be created/ edit/ deleted/ execute all using custom parameters.
>>>>>>>> Sounds interesting this "continuable" concept... I'm not handling
>>>>>>>> it simply cause its not supported in jenkins core and no one wrote
>>>>>>>> a plugin to do that.
>>>>>>>> I will create the repo and upload my code later, so you could have
>>>>>>>> a look.
>>>>>>>> Shai
>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loofwrote
>>>>>>>> :
>>>>>>>>> interesting. So your plugin is more about creating templates to
>>>>>>>>> simplify workflow configuration, with few parameters and UI candy.
>>>>>>>>> I'd be pleased to look how you manage jobs orchestration, as this
>>>>>>>>> is the most annoying part of build flow plugin today. I'd like it to be "
>>>>>>>>> continuable", so a flow can restart after some job have completed,
>>>>>>>>> either due to jenkins restart, or manual re-trigger after some
>>>>>>>>> step failure, etc. Today this is only a basic Job.schedule()
>>>>>>>>> orchestrator. Maybe will require me to improve my groovy skills :)
>>>>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>>>>> collaboration did you have in mind?
>>>>>>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>>>>>>> You can define a build flow job - mark it as a template and place
>>>>>>>>>> some parameter pattern => you'll get a nice UI with my plugin to
>>>>>>>>>> create build flow jobs:
>>>>>>>>>> Shai
>>>>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
> for maven release, remove user / password from URL and delete related commits from your git history before pushing
> 2012/8/15 shai bhur <shai.b...@gmail.com>
> Thanks for the quick response, now i'm getting this:
> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://...@github.com/jenkinsci/template-workflows-plugin.git master:master
> ERROR: Permission to jenkinsci/template-workflows-plugin.git denied to shaibe.
> fatal: The remote end hung up unexpectedly
> also, the maven release generated the ssh with my user and pw, should i remove the user and pw parameters?
> Shai
> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <nicolas.del...@gmail.com> wrote:
> don't use ssh://shaibe:shai...@github.com/jenkinsci/template-workflows-plugin.git but ssh://...@github.com/jenkinsci/template-workflows-plugin.git
> you're identified/authenticated on github by your ssh key, and all git commands connect as "git"
> 2012/8/15 shai bhur <shai.b...@gmail.com>
> Hey Nicolas, I need some help uploading my plugin...
> I'm using windows (don't ask...) and the maven release fails on github authentication.
> Im getting the same behavior from my shell (cmd):
> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
> Hi shaibe! You've successfully authenticated, but GitHub does not provide shell access.
> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://shaibe:shai...@github.com/jenkinsci/template-workflows-plugin.git master:master
> Permission denied (publickey).
> fatal: The remote end hung up unexpectedly
> Which user and pw should I use? the github or the jenkins?
> Do you have any suggestions (besides switching to unix)?
> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com> wrote:
> Thanks for that Nicolas.
> When I'm trying to release my plugin in hangs on the maven release with this line:
> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:*...@github.com/jenkinsci/template-workflows-plugin.git master:master"
> [INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com> wrote:
> My plugin is all about "template workflow" definitions and how easy it is to create and manage a workflow from a template.
> The plugin uses jenkins existing plugins in order to do that, so whatever can be accomplished using a regular jobs chaining and plugins configuration can be placed under a "template workflow" and could be created/ edit/ deleted/ execute all using custom parameters.
> Sounds interesting this "continuable" concept... I'm not handling it simply cause its not supported in jenkins core and no one wrote a plugin to do that.
> I will create the repo and upload my code later, so you could have a look.
> Shai
> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loof wrote:
> interesting. So your plugin is more about creating templates to simplify workflow configuration, with few parameters and UI candy.
> I'd be pleased to look how you manage jobs orchestration, as this is the most annoying part of build flow plugin today. I'd like it to be "continuable", so a flow can restart after some job have completed, either due to jenkins restart, or manual re-trigger after some step failure, etc. Today this is only a basic Job.schedule() orchestrator. Maybe will require me to improve my groovy skills :)
> Indeed we are focusing on the same use case. What kind of collaboration did you have in mind?
> BTW, i already checked and my plugin is compatible with yours:
> You can define a build flow job - mark it as a template and place some parameter pattern => you'll get a nice UI with my plugin to create build flow jobs:
> Shai
> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
> Hi,
>> Thanks for the quick response, now i'm getting this:
>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>> g...@github.com/jenkinsci/template-workflows-plugin.git master:master
>> ERROR: Permission to jenkinsci/template-workflows-plugin.git denied to
>> shaibe.
>> fatal: The remote end hung up unexpectedly
>> also, the maven release generated the ssh with my user and pw, should i remove
>> the user and pw parameters?
>> Shai
>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>> don't use ssh://shaibe:shai***@
>>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>>> github.com/jenkinsci/template-workflows-plugin.git
>>> you're identified/authenticated on github by your ssh key, and all git
>>> commands connect as "git"
>>>> Hey Nicolas, I need some help uploading my plugin...
>>>> I'm using windows (don't ask...) and the maven release fails on githubauthentication.
>>>> Im getting the same behavior from my shell (cmd):
>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>> Hi shaibe! You've successfully authenticated, but GitHub does not
>>>> provide shell access.
>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>> ssh://shaibe:shai...@github.com/jenkinsci/template-workflows-plugin.gitmaster:master
>>>> Permission denied (publickey).
>>>> fatal: The remote end hung up unexpectedly
>>>> Which user and pw should I use? the github or the jenkins?
>>>> Do you have any suggestions (besides switching to unix)?
>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com>wrote:
>>>>> Thanks for that Nicolas.
>>>>> When I'm trying to release my plugin in hangs on the maven release
>>>>> with this line:
>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>>>>> [INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
>>>>> any idea?
>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com>wrote:
>>>>>>>> My plugin is all about "template workflow" definitions and how easy
>>>>>>>> it is to create and manage a workflow from a template.
>>>>>>>> The plugin uses jenkins existing plugins in order to do that, so
>>>>>>>> whatever can be accomplished using a regular jobs chaining and
>>>>>>>> plugins configuration can be placed under a "template workflow" and could
>>>>>>>> be created/ edit/ deleted/ execute all using custom parameters.
>>>>>>>> Sounds interesting this "continuable" concept... I'm not handling
>>>>>>>> it simply cause its not supported in jenkins core and no one wrote
>>>>>>>> a plugin to do that.
>>>>>>>> I will create the repo and upload my code later, so you could have
>>>>>>>> a look.
>>>>>>>> Shai
>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loofwrote
>>>>>>>> :
>>>>>>>>> interesting. So your plugin is more about creating templates to
>>>>>>>>> simplify workflow configuration, with few parameters and UI candy.
>>>>>>>>> I'd be pleased to look how you manage jobs orchestration, as this
>>>>>>>>> is the most annoying part of build flow plugin today. I'd like it to be "
>>>>>>>>> continuable", so a flow can restart after some job have completed,
>>>>>>>>> either due to jenkins restart, or manual re-trigger after some
>>>>>>>>> step failure, etc. Today this is only a basic Job.schedule()
>>>>>>>>> orchestrator. Maybe will require me to improve my groovy skills :)
>>>>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>>>>> collaboration did you have in mind?
>>>>>>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>>>>>>> You can define a build flow job - mark it as a template and place
>>>>>>>>>> some parameter pattern => you'll get a nice UI with my plugin to
>>>>>>>>>> create build flow jobs:
>>>>>>>>>> Shai
>>>>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur wrote:
ok... now it worked and i was able to connect to github - thanks!!!
BUT - the maven release failed with:
[INFO]
------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] Error deploying artifact: Failed to transfer file:
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
Return code is: 401
[INFO]
i'm starting to think that it was easier to write the plugin than uploading
it :)
Shai
On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof
<nicolas.del...@gmail.com>wrote:
>>> Thanks for the quick response, now i'm getting this:
>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:master
>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git denied to
>>> shaibe.
>>> fatal: The remote end hung up unexpectedly
>>> also, the maven release generated the ssh with my user and pw, should i remove
>>> the user and pw parameters?
>>> Shai
>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>> don't use ssh://shaibe:shai***@
>>>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>>>> github.com/jenkinsci/template-workflows-plugin.git
>>>> you're identified/authenticated on github by your ssh key, and all git
>>>> commands connect as "git"
>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>> I'm using windows (don't ask...) and the maven release fails on githubauthentication.
>>>>> Im getting the same behavior from my shell (cmd):
>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>> Hi shaibe! You've successfully authenticated, but GitHub does not
>>>>> provide shell access.
>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>> ssh://shaibe:shai***@
>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>> Permission denied (publickey).
>>>>> fatal: The remote end hung up unexpectedly
>>>>> Which user and pw should I use? the github or the jenkins?
>>>>> Do you have any suggestions (besides switching to unix)?
>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com>wrote:
>>>>>> Thanks for that Nicolas.
>>>>>> When I'm trying to release my plugin in hangs on the maven release
>>>>>> with this line:
>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>>>>>> [INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
>>>>>> any idea?
>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com>wrote:
>>>>>>>>> My plugin is all about "template workflow" definitions and how
>>>>>>>>> easy it is to create and manage a workflow from a template.
>>>>>>>>> The plugin uses jenkins existing plugins in order to do that, so
>>>>>>>>> whatever can be accomplished using a regular jobs chaining and
>>>>>>>>> plugins configuration can be placed under a "template workflow" and could
>>>>>>>>> be created/ edit/ deleted/ execute all using custom parameters.
>>>>>>>>> Sounds interesting this "continuable" concept... I'm not handling
>>>>>>>>> it simply cause its not supported in jenkins core and no
>>>>>>>>> one wrote a plugin to do that.
>>>>>>>>> I will create the repo and upload my code later, so you could
>>>>>>>>> have a look.
>>>>>>>>> Shai
>>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loofwrote
>>>>>>>>> :
>>>>>>>>>> interesting. So your plugin is more about creating templates to
>>>>>>>>>> simplify workflow configuration, with few parameters and UI
>>>>>>>>>> candy.
>>>>>>>>>> I'd be pleased to look how you manage jobs orchestration, as this
>>>>>>>>>> is the most annoying part of build flow plugin today. I'd like it to be "
>>>>>>>>>> continuable", so a flow can restart after some job have completed,
>>>>>>>>>> either due to jenkins restart, or manual re-trigger after some
>>>>>>>>>> step failure, etc. Today this is only a basic Job.schedule()
>>>>>>>>>> orchestrator. Maybe will require me to improve my groovy skills
>>>>>>>>>> :)
>>>>>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>>>>>> collaboration did you have in mind?
>>>>>>>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>>>>>>>> You can define a build flow job - mark it as a template and
>>>>>>>>>>> place some parameter pattern => you'll get a nice UI with my
>>>>>>>>>>> plugin to create build flow jobs:
>>>>>>>>>>> Shai
>>>>>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur
>>>>>>>>>>> wrote:
> ok... now it worked and i was able to connect to github - thanks!!!
> BUT - the maven release failed with:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [ERROR] BUILD ERROR
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
> Return code is: 401
> [INFO]
> i'm starting to think that it was easier to write the plugin than
> uploading it :)
> Shai
> On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof <nicolas.del...@gmail.com
> > wrote:
>>>> Thanks for the quick response, now i'm getting this:
>>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:master
>>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git denied to
>>>> shaibe.
>>>> fatal: The remote end hung up unexpectedly
>>>> also, the maven release generated the ssh with my user and pw, should i remove
>>>> the user and pw parameters?
>>>> Shai
>>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>>> nicolas.del...@gmail.com> wrote:
>>>>> don't use ssh://shaibe:shai***@
>>>>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>>>>> github.com/jenkinsci/template-workflows-plugin.git
>>>>> you're identified/authenticated on github by your ssh key, and all git
>>>>> commands connect as "git"
>>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>>> I'm using windows (don't ask...) and the maven release fails on
>>>>>> github authentication.
>>>>>> Im getting the same behavior from my shell (cmd):
>>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>>> Hi shaibe! You've successfully authenticated, but GitHub does not
>>>>>> provide shell access.
>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>>> ssh://shaibe:shai***@
>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>>> Permission denied (publickey).
>>>>>> fatal: The remote end hung up unexpectedly
>>>>>> Which user and pw should I use? the github or the jenkins?
>>>>>> Do you have any suggestions (besides switching to unix)?
>>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com>wrote:
>>>>>>> Thanks for that Nicolas.
>>>>>>> When I'm trying to release my plugin in hangs on the maven release
>>>>>>> with this line:
>>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>>>>>>> [INFO] Working directory: E:\gitHub\template-workflows-jenkins-plugin
>>>>>>> any idea?
>>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <shai.b...@gmail.com
>>>>>>>>> > wrote:
>>>>>>>>>> My plugin is all about "template workflow" definitions and how
>>>>>>>>>> easy it is to create and manage a workflow from a template.
>>>>>>>>>> The plugin uses jenkins existing plugins in order to do that, so
>>>>>>>>>> whatever can be accomplished using a regular jobs chaining and
>>>>>>>>>> plugins configuration can be placed under a "template workflow" and could
>>>>>>>>>> be created/ edit/ deleted/ execute all using custom parameters.
>>>>>>>>>> Sounds interesting this "continuable" concept... I'm not
>>>>>>>>>> handling it simply cause its not supported in jenkins core and
>>>>>>>>>> no one wrote a plugin to do that.
>>>>>>>>>> I will create the repo and upload my code later, so you could
>>>>>>>>>> have a look.
>>>>>>>>>> Shai
>>>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loofwrote
>>>>>>>>>> :
>>>>>>>>>>> interesting. So your plugin is more about creating templates to
>>>>>>>>>>> simplify workflow configuration, with few parameters and UI
>>>>>>>>>>> candy.
>>>>>>>>>>> I'd be pleased to look how you manage jobs orchestration, as
>>>>>>>>>>> this is the most annoying part of build flow plugin today. I'd like it to
>>>>>>>>>>> be "continuable", so a flow can restart after some job have
>>>>>>>>>>> completed, either due to jenkins restart, or manual re-trigger
>>>>>>>>>>> after some step failure, etc. Today this is only a basic Job.
>>>>>>>>>>> schedule() orchestrator. Maybe will require me to improve my
>>>>>>>>>>> groovy skills :)
>>>>>>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>>>>>>> collaboration did you have in mind?
>>>>>>>>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>>>>>>>>> You can define a build flow job - mark it as a template and
>>>>>>>>>>>> place some parameter pattern => you'll get a nice UI with my
>>>>>>>>>>>> plugin to create build flow jobs:
>>>>>>>>>>>> Shai
>>>>>>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur
>>>>>>>>>>>> wrote:
Finally... I was able to successfully run the maven release - THANKS a lot
for your help!
Few questions:
1) during the attempt to release the plugin i had to increase the plugin
version and its currently at v:1.2, is there a way to delete tags 1.0, 1.1,
1.2 so i can re-release it with its real version -1.0?
2) when will it be available to download and installation from the update
center?
3) who is responsible to update the wiki and announce that this plugin is
released?
4) when will the wiki page be updated with the plugin info header?
5) if you could find the time to install this plugin, i will really
appreciate your feedback on it.
Again,
Thanks a lot
Shai
On Wed, Aug 15, 2012 at 6:13 PM, nicolas de loof
<nicolas.del...@gmail.com>wrote:
>> ok... now it worked and i was able to connect to github - thanks!!!
>> BUT - the maven release failed with:
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [ERROR] BUILD ERROR
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
>> Return code is: 401
>> [INFO]
>> i'm starting to think that it was easier to write the plugin than
>> uploading it :)
>> Shai
>> On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>>>> Thanks for the quick response, now i'm getting this:
>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git denied
>>>>> to shaibe.
>>>>> fatal: The remote end hung up unexpectedly
>>>>> also, the maven release generated the ssh with my user and pw, should
>>>>> i remove the user and pw parameters?
>>>>> Shai
>>>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>>>> nicolas.del...@gmail.com> wrote:
>>>>>> don't use ssh://shaibe:shai***@
>>>>>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>>>>>> github.com/jenkinsci/template-workflows-plugin.git
>>>>>> you're identified/authenticated on github by your ssh key, and all
>>>>>> git commands connect as "git"
>>>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>>>> I'm using windows (don't ask...) and the maven release fails on
>>>>>>> github authentication.
>>>>>>> Im getting the same behavior from my shell (cmd):
>>>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>>>> Hi shaibe! You've successfully authenticated, but GitHub does not
>>>>>>> provide shell access.
>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>>>> ssh://shaibe:shai***@
>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>>>> Permission denied (publickey).
>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>> Which user and pw should I use? the github or the jenkins?
>>>>>>> Do you have any suggestions (besides switching to unix)?
>>>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com>wrote:
>>>>>>>> Thanks for that Nicolas.
>>>>>>>> When I'm trying to release my plugin in hangs on the maven release
>>>>>>>> with this line:
>>>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>>>>>>>> [INFO] Working directory:
>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin
>>>>>>>> any idea?
>>>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <
>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>> My plugin is all about "template workflow" definitions and how
>>>>>>>>>>> easy it is to create and manage a workflow from a template.
>>>>>>>>>>> The plugin uses jenkins existing plugins in order to do that,
>>>>>>>>>>> so whatever can be accomplished using a regular jobs chaining
>>>>>>>>>>> and plugins configuration can be placed under a "template workflow" and
>>>>>>>>>>> could be created/ edit/ deleted/ execute all using custom
>>>>>>>>>>> parameters.
>>>>>>>>>>> Sounds interesting this "continuable" concept... I'm not
>>>>>>>>>>> handling it simply cause its not supported in jenkins core and
>>>>>>>>>>> no one wrote a plugin to do that.
>>>>>>>>>>> I will create the repo and upload my code later, so you could
>>>>>>>>>>> have a look.
>>>>>>>>>>> Shai
>>>>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loofwrote
>>>>>>>>>>> :
>>>>>>>>>>>> interesting. So your plugin is more about creating templates to
>>>>>>>>>>>> simplify workflow configuration, with few parameters and UI
>>>>>>>>>>>> candy.
>>>>>>>>>>>> I'd be pleased to look how you manage jobs orchestration, as
>>>>>>>>>>>> this is the most annoying part of build flow plugin today. I'd like it to
>>>>>>>>>>>> be "continuable", so a flow can restart after some job have
>>>>>>>>>>>> completed, either due to jenkins restart, or manual re-trigger
>>>>>>>>>>>> after some step failure, etc. Today this is only a basic Job.
>>>>>>>>>>>> schedule() orchestrator. Maybe will require me to improve my
>>>>>>>>>>>> groovy skills :)
>>>>>>>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>>>>>>>> collaboration did you have in mind?
>>>>>>>>>>>>> BTW, i already checked and my plugin is compatible with yours:
>>>>>>>>>>>>> You can define a build flow job - mark it as a template and
>>>>>>>>>>>>> place some parameter pattern => you'll get a nice UI with my
>>>>>>>>>>>>> plugin to create build flow jobs:
>>>>>>>>>>>>> Shai
>>>>>>>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur
>>>>>>>>>>>>> wrote:
> Finally... I was able to successfully run the maven release - THANKS a lot
> for your help!
> Few questions:
> 1) during the attempt to release the plugin i had to increase the plugin
> version and its currently at v:1.2, is there a way to delete tags 1.0,
> 1.1, 1.2 so i can re-release it with its real version -1.0?
>>> ok... now it worked and i was able to connect to github - thanks!!!
>>> BUT - the maven release failed with:
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [ERROR] BUILD ERROR
>>> [INFO] [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
>>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
>>> Return code is: 401
>>> [INFO]
>>> i'm starting to think that it was easier to write the plugin than
>>> uploading it :)
>>> Shai
>>> On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>>>> Thanks for the quick response, now i'm getting this:
>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>>>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git denied
>>>>>> to shaibe.
>>>>>> fatal: The remote end hung up unexpectedly
>>>>>> also, the maven release generated the ssh with my user and pw, should
>>>>>> i remove the user and pw parameters?
>>>>>> Shai
>>>>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>> don't use ssh://shaibe:shai***@
>>>>>>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>>>>>>> github.com/jenkinsci/template-workflows-plugin.git
>>>>>>> you're identified/authenticated on github by your ssh key, and all
>>>>>>> git commands connect as "git"
>>>>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>>>>> I'm using windows (don't ask...) and the maven release fails on
>>>>>>>> github authentication.
>>>>>>>> Im getting the same behavior from my shell (cmd):
>>>>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>>>>> Hi shaibe! You've successfully authenticated, but GitHub does not
>>>>>>>> provide shell access.
>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>>>>> ssh://shaibe:shai***@
>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>>>>> Permission denied (publickey).
>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>> Which user and pw should I use? the github or the jenkins?
>>>>>>>> Do you have any suggestions (besides switching to unix)?
>>>>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com>wrote:
>>>>>>>>> Thanks for that Nicolas.
>>>>>>>>> When I'm trying to release my plugin in hangs on the maven release
>>>>>>>>> with this line:
>>>>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>>>>>>>>> [INFO] Working directory:
>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin
>>>>>>>>> any idea?
>>>>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <
>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>> My plugin is all about "template workflow" definitions and how
>>>>>>>>>>>> easy it is to create and manage a workflow from a template.
>>>>>>>>>>>> The plugin uses jenkins existing plugins in order to do that,
>>>>>>>>>>>> so whatever can be accomplished using a regular jobs chaining
>>>>>>>>>>>> and plugins configuration can be placed under a "template workflow" and
>>>>>>>>>>>> could be created/ edit/ deleted/ execute all using custom
>>>>>>>>>>>> parameters.
>>>>>>>>>>>> Sounds interesting this "continuable" concept... I'm not
>>>>>>>>>>>> handling it simply cause its not supported in jenkins core and
>>>>>>>>>>>> no one wrote a plugin to do that.
>>>>>>>>>>>> I will create the repo and upload my code later, so you could
>>>>>>>>>>>> have a look.
>>>>>>>>>>>> Shai
>>>>>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loofwrote
>>>>>>>>>>>> :
>>>>>>>>>>>>> interesting. So your plugin is more about creating templates
>>>>>>>>>>>>> to simplify workflow configuration, with few parameters and
>>>>>>>>>>>>> UI candy.
>>>>>>>>>>>>> I'd be pleased to look how you manage jobs orchestration, as
>>>>>>>>>>>>> this is the most annoying part of build flow plugin today. I'd like it to
>>>>>>>>>>>>> be "continuable", so a flow can restart after some job have
>>>>>>>>>>>>> completed, either due to jenkins restart, or manual
>>>>>>>>>>>>> re-trigger after some step failure, etc. Today this is only a basic Job
>>>>>>>>>>>>> .schedule() orchestrator. Maybe will require me to improve my
>>>>>>>>>>>>> groovy skills :)
>>>>>>>>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>>>>>>>>> collaboration did you have in mind?
>>>>>>>>>>>>>> BTW, i already checked and my plugin is compatible with
>>>>>>>>>>>>>> yours:
>>>>>>>>>>>>>> You can define a build flow job - mark it as a template and
>>>>>>>>>>>>>> place some parameter pattern => you'll get a nice UI with my
>>>>>>>>>>>>>> plugin to create build flow jobs:
>>>>>>>>>>>>>> Shai
>>>>>>>>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur
>>>>>>>>>>>>>> wrote:
>> Finally... I was able to successfully run the maven release - THANKS a
>> lot for your help!
>> Few questions:
>> 1) during the attempt to release the plugin i had to increase the plugin
>> version and its currently at v:1.2, is there a way to delete tags 1.0,
>> 1.1, 1.2 so i can re-release it with its real version -1.0?
>>>> ok... now it worked and i was able to connect to github - thanks!!!
>>>> BUT - the maven release failed with:
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] [ERROR] BUILD ERROR
>>>> [INFO] [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
>>>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
>>>> Return code is: 401
>>>> [INFO]
>>>> i'm starting to think that it was easier to write the plugin than
>>>> uploading it :)
>>>> Shai
>>>> On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof <
>>>> nicolas.del...@gmail.com> wrote:
>>>>>>> Thanks for the quick response, now i'm getting this:
>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>>>>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git denied
>>>>>>> to shaibe.
>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>> also, the maven release generated the ssh with my user and pw, should
>>>>>>> i remove the user and pw parameters?
>>>>>>> Shai
>>>>>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>> don't use ssh://shaibe:shai***@
>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git
>>>>>>>> you're identified/authenticated on github by your ssh key, and all
>>>>>>>> git commands connect as "git"
>>>>>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>>>>>> I'm using windows (don't ask...) and the maven release fails on
>>>>>>>>> github authentication.
>>>>>>>>> Im getting the same behavior from my shell (cmd):
>>>>>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>>>>>> Hi shaibe! You've successfully authenticated, but GitHub does not
>>>>>>>>> provide shell access.
>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>>>>>> ssh://shaibe:shai***@
>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>>>>>> Permission denied (publickey).
>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>> Which user and pw should I use? the github or the jenkins?
>>>>>>>>> Do you have any suggestions (besides switching to unix)?
>>>>>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com>wrote:
>>>>>>>>>> Thanks for that Nicolas.
>>>>>>>>>> When I'm trying to release my plugin in hangs on the maven
>>>>>>>>>> release with this line:
>>>>>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master"
>>>>>>>>>> [INFO] Working directory:
>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin
>>>>>>>>>> any idea?
>>>>>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <
>>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>>> My plugin is all about "template workflow" definitions and how
>>>>>>>>>>>>> easy it is to create and manage a workflow from a template.
>>>>>>>>>>>>> The plugin uses jenkins existing plugins in order to do that,
>>>>>>>>>>>>> so whatever can be accomplished using a regular jobs chaining
>>>>>>>>>>>>> and plugins configuration can be placed under a "template workflow" and
>>>>>>>>>>>>> could be created/ edit/ deleted/ execute all using custom
>>>>>>>>>>>>> parameters.
>>>>>>>>>>>>> Sounds interesting this "continuable" concept... I'm not
>>>>>>>>>>>>> handling it simply cause its not supported in jenkins core
>>>>>>>>>>>>> and no one wrote a plugin to do that.
>>>>>>>>>>>>> I will create the repo and upload my code later, so you could
>>>>>>>>>>>>> have a look.
>>>>>>>>>>>>> Shai
>>>>>>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de loofwrote
>>>>>>>>>>>>> :
>>>>>>>>>>>>>> interesting. So your plugin is more about creating templates
>>>>>>>>>>>>>> to simplify workflow configuration, with few parameters and
>>>>>>>>>>>>>> UI candy.
>>>>>>>>>>>>>> I'd be pleased to look how you manage jobs orchestration, as
>>>>>>>>>>>>>> this is the most annoying part of build flow plugin today. I'd like it to
>>>>>>>>>>>>>> be "continuable", so a flow can restart after some job have
>>>>>>>>>>>>>> completed, either due to jenkins restart, or manual
>>>>>>>>>>>>>> re-trigger after some step failure, etc. Today this is only a basic Job
>>>>>>>>>>>>>> .schedule() orchestrator. Maybe will require me to improve
>>>>>>>>>>>>>> my groovy skills :)
>>>>>>>>>>>>>>> Indeed we are focusing on the same use case. What kind of
>>>>>>>>>>>>>>> collaboration did you have in mind?
>>>>>>>>>>>>>>> BTW, i already checked and my plugin is compatible with
>>>>>>>>>>>>>>> yours:
>>>>>>>>>>>>>>> You can define a build flow job - mark it as a template and
>>>>>>>>>>>>>>> place some parameter pattern => you'll get a nice UI with
>>>>>>>>>>>>>>> my plugin to create build flow jobs:
>>>>>>>>>>>>>>> Shai
>>>>>>>>>>>>>>> On Tuesday, August 14, 2012 12:01:10 PM UTC+3, Shai Ben-Hur
>>>>>>>>>>>>>>> wrote:
>>> Finally... I was able to successfully run the maven release - THANKS a
>>> lot for your help!
>>> Few questions:
>>> 1) during the attempt to release the plugin i had to increase the
>>> plugin version and its currently at v:1.2, is there a way to delete
>>> tags 1.0, 1.1, 1.2 so i can re-release it with its real version -1.0?
>>>>> ok... now it worked and i was able to connect to github - thanks!!!
>>>>> BUT - the maven release failed with:
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] [ERROR] BUILD ERROR
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
>>>>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
>>>>> Return code is: 401
>>>>> [INFO]
>>>>> i'm starting to think that it was easier to write the plugin than
>>>>> uploading it :)
>>>>> Shai
>>>>> On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof <
>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>> I can see that i have "read-only" access to "
>>>>>>> https://github.com/jenkinsci/template-workflows-plugin.git".
>>>>>>> Could this be related to the "permission denied" issue? shouldn't i
>>>>>>> have write access as well?
>>>>>>> I'll really appreciate your help,
>>>>>>> Shai
>>>>>>> On Aug 15, 2012, at 1:24 PM, nicolas de loof <
>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>> Thanks for the quick response, now i'm getting this:
>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>>>>>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>> master
>>>>>>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git
>>>>>>>> denied to shaibe.
>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>> also, the maven release generated the ssh with my user and pw, should
>>>>>>>> i remove the user and pw parameters?
>>>>>>>> Shai
>>>>>>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>> don't use ssh://shaibe:shai***@
>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git
>>>>>>>>> you're identified/authenticated on github by your ssh key, and all
>>>>>>>>> git commands connect as "git"
>>>>>>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>>>>>>> I'm using windows (don't ask...) and the maven release fails on
>>>>>>>>>> github authentication.
>>>>>>>>>> Im getting the same behavior from my shell (cmd):
>>>>>>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>>>>>>> Hi shaibe! You've successfully authenticated, but GitHub does
>>>>>>>>>> not provide shell access.
>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>>>>>>> ssh://shaibe:shai***@
>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>>>>>>> Permission denied (publickey).
>>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>>> Which user and pw should I use? the github or the jenkins?
>>>>>>>>>> Do you have any suggestions (besides switching to unix)?
>>>>>>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com>wrote:
>>>>>>>>>>> Thanks for that Nicolas.
>>>>>>>>>>> When I'm trying to release my plugin in hangs on the maven
>>>>>>>>>>> release with this line:
>>>>>>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>>>>> master"
>>>>>>>>>>> [INFO] Working directory:
>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin
>>>>>>>>>>> any idea?
>>>>>>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <
>>>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>>>> My plugin is all about "template workflow" definitions and
>>>>>>>>>>>>>> how easy it is to create and manage a workflow from a template.
>>>>>>>>>>>>>> The plugin uses jenkins existing plugins in order to do
>>>>>>>>>>>>>> that, so whatever can be accomplished using a regular jobschaining and plugins configuration can be placed under a "template
>>>>>>>>>>>>>> workflow" and could be created/ edit/ deleted/ execute all
>>>>>>>>>>>>>> using custom parameters.
>>>>>>>>>>>>>> Sounds interesting this "continuable" concept... I'm not
>>>>>>>>>>>>>> handling it simply cause its not supported in jenkins core
>>>>>>>>>>>>>> and no one wrote a plugin to do that.
>>>>>>>>>>>>>> I will create the repo and upload my code later, so you
>>>>>>>>>>>>>> could have a look.
>>>>>>>>>>>>>> Shai
>>>>>>>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de
>>>>>>>>>>>>>> loof wrote:
>>>>>>>>>>>>>>> interesting. So your plugin is more about creating templates
>>>>>>>>>>>>>>> to simplify workflow configuration, with few parameters and
>>>>>>>>>>>>>>> UI candy.
>>>>>>>>>>>>>>> I'd be pleased to look how you manage jobs orchestration, as
>>>>>>>>>>>>>>> this is the most annoying part of build flow plugin today. I'd like it to
>>>>>>>>>>>>>>> be "continuable", so a flow can restart after some job have
>>>>>>>>>>>>>>> completed, either due to jenkins restart, or manual
>>>>>>>>>>>>>>> re-trigger after some step failure, etc. Today this is only a basic Job
>>>>>>>>>>>>>>> .schedule() orchestrator. Maybe will require me to improve
>>>>>>>>>>>>>>> my groovy skills :)
>>>> Finally... I was able to successfully run the maven release - THANKS a
>>>> lot for your help!
>>>> Few questions:
>>>> 1) during the attempt to release the plugin i had to increase the
>>>> plugin version and its currently at v:1.2, is there a way to delete
>>>> tags 1.0, 1.1, 1.2 so i can re-release it with its real version -1.0?
>>>>>> ok... now it worked and i was able to connect to github - thanks!!!
>>>>>> BUT - the maven release failed with:
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] [ERROR] BUILD ERROR
>>>>>> [INFO] [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
>>>>>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
>>>>>> Return code is: 401
>>>>>> [INFO]
>>>>>> i'm starting to think that it was easier to write the plugin than
>>>>>> uploading it :)
>>>>>> Shai
>>>>>> On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof <
>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>> I can see that i have "read-only" access to "
>>>>>>>> https://github.com/jenkinsci/template-workflows-plugin.git".
>>>>>>>> Could this be related to the "permission denied" issue? shouldn't i
>>>>>>>> have write access as well?
>>>>>>>> I'll really appreciate your help,
>>>>>>>> Shai
>>>>>>>> On Aug 15, 2012, at 1:24 PM, nicolas de loof <
>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>> Thanks for the quick response, now i'm getting this:
>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>>>>>>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>>> master
>>>>>>>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git
>>>>>>>>> denied to shaibe.
>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>> also, the maven release generated the ssh with my user and pw, should
>>>>>>>>> i remove the user and pw parameters?
>>>>>>>>> Shai
>>>>>>>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>> don't use ssh://shaibe:shai***@
>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git but ssh://git@
>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git
>>>>>>>>>> you're identified/authenticated on github by your ssh key, and
>>>>>>>>>> all git commands connect as "git"
>>>>>>>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>>>>>>>> I'm using windows (don't ask...) and the maven release fails on
>>>>>>>>>>> github authentication.
>>>>>>>>>>> Im getting the same behavior from my shell (cmd):
>>>>>>>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>>>>>>>> Hi shaibe! You've successfully authenticated, but GitHub does
>>>>>>>>>>> not provide shell access.
>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>>>>>>>> ssh://shaibe:shai***@
>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:master
>>>>>>>>>>> Permission denied (publickey).
>>>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>>>> Which user and pw should I use? the github or the jenkins?
>>>>>>>>>>> Do you have any suggestions (besides switching to unix)?
>>>>>>>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <shai.b...@gmail.com
>>>>>>>>>>> > wrote:
>>>>>>>>>>>> Thanks for that Nicolas.
>>>>>>>>>>>> When I'm trying to release my plugin in hangs on the maven
>>>>>>>>>>>> release with this line:
>>>>>>>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>>>>>> master"
>>>>>>>>>>>> [INFO] Working directory:
>>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin
>>>>>>>>>>>> any idea?
>>>>>>>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <
>>>>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>>>>> My plugin is all about "template workflow" definitions and
>>>>>>>>>>>>>>> how easy it is to create and manage a workflow from a template.
>>>>>>>>>>>>>>> The plugin uses jenkins existing plugins in order to do
>>>>>>>>>>>>>>> that, so whatever can be accomplished using a regular jobschaining and plugins configuration can be placed under a "template
>>>>>>>>>>>>>>> workflow" and could be created/ edit/ deleted/ execute all
>>>>>>>>>>>>>>> using custom parameters.
>>>>>>>>>>>>>>> Sounds interesting this "continuable" concept... I'm not
>>>>>>>>>>>>>>> handling it simply cause its not supported in jenkins core
>>>>>>>>>>>>>>> and no one wrote a plugin to do that.
>>>>>>>>>>>>>>> I will create the repo and upload my code later, so you
>>>>>>>>>>>>>>> could have a look.
>>>>>>>>>>>>>>> Shai
>>>>>>>>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de
>>>>>>>>>>>>>>> loof wrote:
>>>>>>>>>>>>>>>> interesting. So your plugin is more about creating
>>>>>>>>>>>>>>>> templates to simplify workflow configuration, with few
>>>>>>>>>>>>>>>> parameters and UI candy.
>>>>>>>>>>>>>>>> I'd be pleased to look how you manage jobs orchestration,
>>>>>>>>>>>>>>>> as this is the most annoying part of build flow plugin today. I'd like it
>>>>>>>>>>>>>>>> to be "continuable", so a flow can restart after some job have
>>>>>>>>>>>>>>>> completed, either due to jenkins restart, or manual
>>>>>>>>>>>>>>>> re-trigger after some step failure, etc. Today this is only a basic Job
>>>>>>>>>>>>>>>> .schedule() orchestrator. Maybe will require me to improve
>>>>>>>>>>>>>>>> my groovy skills :)
Hey Nicolas,
I don't want to be a nagger... but my plugin still not available in the
update center and now it won't show up in the wiki "new releases".
Does it usually take this much time?
>>>>> Finally... I was able to successfully run the maven release - THANKS a
>>>>> lot for your help!
>>>>> Few questions:
>>>>> 1) during the attempt to release the plugin i had to increase the
>>>>> plugin version and its currently at v:1.2, is there a way to delete
>>>>> tags 1.0, 1.1, 1.2 so i can re-release it with its real version -1.0?
>>>>>>> ok... now it worked and i was able to connect to github - thanks!!!
>>>>>>> BUT - the maven release failed with:
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] [ERROR] BUILD ERROR
>>>>>>> [INFO] [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
>>>>>>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
>>>>>>> Return code is: 401
>>>>>>> [INFO]
>>>>>>> i'm starting to think that it was easier to write the plugin than
>>>>>>> uploading it :)
>>>>>>> Shai
>>>>>>> On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof <
>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>> I can see that i have "read-only" access to "
>>>>>>>>> https://github.com/jenkinsci/template-workflows-plugin.git".
>>>>>>>>> Could this be related to the "permission denied" issue? shouldn't
>>>>>>>>> i have write access as well?
>>>>>>>>> I'll really appreciate your help,
>>>>>>>>> Shai
>>>>>>>>> On Aug 15, 2012, at 1:24 PM, nicolas de loof <
>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>> Thanks for the quick response, now i'm getting this:
>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>>>>>>>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>>>> master
>>>>>>>>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git
>>>>>>>>>> denied to shaibe.
>>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>>> also, the maven release generated the ssh with my user and pw, should
>>>>>>>>>> i remove the user and pw parameters?
>>>>>>>>>> Shai
>>>>>>>>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>> don't use ssh://shaibe:shai***@
>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git but
>>>>>>>>>>> ssh://...@github.com/jenkinsci/template-workflows-plugin.git
>>>>>>>>>>> you're identified/authenticated on github by your ssh key, and
>>>>>>>>>>> all git commands connect as "git"
>>>>>>>>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>>>>>>>>> I'm using windows (don't ask...) and the maven release fails on
>>>>>>>>>>>> github authentication.
>>>>>>>>>>>> Im getting the same behavior from my shell (cmd):
>>>>>>>>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>>>>>>>>> Hi shaibe! You've successfully authenticated, but GitHub does
>>>>>>>>>>>> not provide shell access.
>>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>>>>>>>>> ssh://shaibe:shai***@
>>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.gitmaster:master
>>>>>>>>>>>> Permission denied (publickey).
>>>>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>>>>> Which user and pw should I use? the github or the jenkins?
>>>>>>>>>>>> Do you have any suggestions (besides switching to unix)?
>>>>>>>>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <
>>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>>> Thanks for that Nicolas.
>>>>>>>>>>>>> When I'm trying to release my plugin in hangs on the maven
>>>>>>>>>>>>> release with this line:
>>>>>>>>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>>>>>>> master"
>>>>>>>>>>>>> [INFO] Working directory:
>>>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin
>>>>>>>>>>>>> any idea?
>>>>>>>>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <
>>>>>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>>>>>> My plugin is all about "template workflow" definitions and
>>>>>>>>>>>>>>>> how easy it is to create and manage a workflow from a template.
>>>>>>>>>>>>>>>> The plugin uses jenkins existing plugins in order to do
>>>>>>>>>>>>>>>> that, so whatever can be accomplished using a regular jobschaining and plugins configuration can be placed under a "template
>>>>>>>>>>>>>>>> workflow" and could be created/ edit/ deleted/ execute all
>>>>>>>>>>>>>>>> using custom parameters.
>>>>>>>>>>>>>>>> Sounds interesting this "continuable" concept... I'm not
>>>>>>>>>>>>>>>> handling it simply cause its not supported in jenkins core
>>>>>>>>>>>>>>>> and no one wrote a plugin to do that.
>>>>>>>>>>>>>>>> I will create the repo and upload my code later, so you
>>>>>>>>>>>>>>>> could have a look.
>>>>>>>>>>>>>>>> Shai
>>>>>>>>>>>>>>>> On Tuesday, August 14, 2012 12:51:10 PM UTC+3, nicolas de
>>>>>>>>>>>>>>>> loof wrote:
>>>>>>>>>>>>>>>>> interesting. So your plugin is more about creating
>>>>>>>>>>>>>>>>> templates to simplify workflow configuration, with few
>>>>>>>>>>>>>>>>> parameters and UI candy.
Ok. its there now. the wiki still not announcing my plugin though...
On Thu, Aug 16, 2012 at 11:44 AM, shai bhur <shai.b...@gmail.com> wrote:
> Hey Nicolas,
> I don't want to be a nagger... but my plugin still not available in the
> update center and now it won't show up in the wiki "new releases".
> Does it usually take this much time?
>>>> I can see that the plugin info header changed and that the wiki
>>>> announces my plugin. But I can't find it in the update center...
>>>> The plugin is located here:
>>>> http://repo.jenkins-ci.org/releases/org/jenkins/plugin/templateWorkfl... >>>> I can't find it in the update center json file: http://ftp-nyc.osuosl >>>> .org/pub/jenkins/updates/update-center.json
>>>> Who should I contact regarding this issue? Or should I just wait?
>>>> Thanks,
>>>> Shai
>>>> On Wed, Aug 15, 2012 at 10:37 PM, nicolas de loof <
>>>> nicolas.del...@gmail.com> wrote:
>>>>>> Finally... I was able to successfully run the maven release - THANKS
>>>>>> a lot for your help!
>>>>>> Few questions:
>>>>>> 1) during the attempt to release the plugin i had to increase the
>>>>>> plugin version and its currently at v:1.2, is there a way to delete
>>>>>> tags 1.0, 1.1, 1.2 so i can re-release it with its real version -1.0?
>>>>>>>> ok... now it worked and i was able to connect to github - thanks!!!
>>>>>>>> BUT - the maven release failed with:
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>> [INFO] [ERROR] BUILD ERROR
>>>>>>>> [INFO] [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
>>>>>>>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
>>>>>>>> Return code is: 401
>>>>>>>> [INFO]
>>>>>>>> i'm starting to think that it was easier to write the plugin than
>>>>>>>> uploading it :)
>>>>>>>> Shai
>>>>>>>> On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof <
>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>> I can see that i have "read-only" access to "
>>>>>>>>>> https://github.com/jenkinsci/template-workflows-plugin.git".
>>>>>>>>>> Could this be related to the "permission denied" issue? shouldn't
>>>>>>>>>> i have write access as well?
>>>>>>>>>> I'll really appreciate your help,
>>>>>>>>>> Shai
>>>>>>>>>> On Aug 15, 2012, at 1:24 PM, nicolas de loof <
>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>> Thanks for the quick response, now i'm getting this:
>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>>>>>>>>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>>>>> master
>>>>>>>>>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git
>>>>>>>>>>> denied to shaibe.
>>>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>>>> also, the maven release generated the ssh with my user and pw, should
>>>>>>>>>>> i remove the user and pw parameters?
>>>>>>>>>>> Shai
>>>>>>>>>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>>> don't use ssh://shaibe:shai***@
>>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git but
>>>>>>>>>>>> ssh://...@github.com/jenkinsci/template-workflows-plugin.git
>>>>>>>>>>>> you're identified/authenticated on github by your ssh key, and
>>>>>>>>>>>> all git commands connect as "git"
>>>>>>>>>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>>>>>>>>>> I'm using windows (don't ask...) and the maven release fails
>>>>>>>>>>>>> on github authentication.
>>>>>>>>>>>>> Im getting the same behavior from my shell (cmd):
>>>>>>>>>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>>>>>>>>>> Hi shaibe! You've successfully authenticated, but GitHub does
>>>>>>>>>>>>> not provide shell access.
>>>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>>>>>>>>>> ssh://shaibe:shai***@
>>>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.gitmaster:master
>>>>>>>>>>>>> Permission denied (publickey).
>>>>>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>>>>>> Which user and pw should I use? the github or the jenkins?
>>>>>>>>>>>>> Do you have any suggestions (besides switching to unix)?
>>>>>>>>>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <
>>>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>>>> Thanks for that Nicolas.
>>>>>>>>>>>>>> When I'm trying to release my plugin in hangs on the maven
>>>>>>>>>>>>>> release with this line:
>>>>>>>>>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>>>>>>>> master"
>>>>>>>>>>>>>> [INFO] Working directory:
>>>>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin
>>>>>>>>>>>>>> any idea?
>>>>>>>>>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <
>>>>>>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>>>>>>> My plugin is all about "template workflow" definitions and
>>>>>>>>>>>>>>>>> how easy it is to create and manage a workflow from a template.
>>>>>>>>>>>>>>>>> The plugin uses jenkins existing plugins in order to do
>>>>>>>>>>>>>>>>> that, so whatever can be accomplished using a regular jobschaining and plugins configuration can be placed under a "template
>>>>>>>>>>>>>>>>> workflow" and could be created/ edit/ deleted/ execute
>>>>>>>>>>>>>>>>> all using custom parameters.
>>>>>>>>>>>>>>>>> Sounds interesting this "continuable" concept... I'm not
>>>>>>>>>>>>>>>>> handling it simply cause its not supported in jenkins core
>>>>>>>>>>>>>>>>> and no one wrote a plugin to do that.
>>>>>>>>>>>>>>>>> I will create the repo and upload my code
> Ok. its there now. the wiki still not announcing my plugin though...
> On Thu, Aug 16, 2012 at 11:44 AM, shai bhur <shai.b...@gmail.com> wrote:
>> Hey Nicolas,
>> I don't want to be a nagger... but my plugin still not available in the
>> update center and now it won't show up in the wiki "new releases".
>> Does it usually take this much time?
>> Thanks,
> Shai
>> On Thu, Aug 16, 2012 at 9:36 AM, shai bhur <shai.b...@gmail.com> wrote:
>>> Thanks man :)
>>> On Thu, Aug 16, 2012 at 9:23 AM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>>> I can see that the plugin info header changed and that the wiki
>>>>> announces my plugin. But I can't find it in the update center...
>>>>> The plugin is located here:
>>>>> http://repo.jenkins-ci.org/releases/org/jenkins/plugin/templateWorkfl... >>>>> I can't find it in the update center json file: http://ftp-nyc.osuosl >>>>> .org/pub/jenkins/updates/update-center.json
>>>>> Who should I contact regarding this issue? Or should I just wait?
>>>>> Thanks,
>>>>> Shai
>>>>> On Wed, Aug 15, 2012 at 10:37 PM, nicolas de loof <
>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>> Finally... I was able to successfully run the maven release - THANKS
>>>>>>> a lot for your help!
>>>>>>> Few questions:
>>>>>>> 1) during the attempt to release the plugin i had to increase the
>>>>>>> plugin version and its currently at v:1.2, is there a way to delete
>>>>>>> tags 1.0, 1.1, 1.2 so i can re-release it with its real version
>>>>>>> -1.0?
>>>>>>>>> ok... now it worked and i was able to connect to github -
>>>>>>>>> thanks!!!
>>>>>>>>> BUT - the maven release failed with:
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] [ERROR] BUILD ERROR
>>>>>>>>> [INFO] [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
>>>>>>>>> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je....
>>>>>>>>> Return code is: 401
>>>>>>>>> [INFO]
>>>>>>>>> i'm starting to think that it was easier to write the plugin than
>>>>>>>>> uploading it :)
>>>>>>>>> Shai
>>>>>>>>> On Wed, Aug 15, 2012 at 4:27 PM, nicolas de loof <
>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>> I can see that i have "read-only" access to "
>>>>>>>>>>> https://github.com/jenkinsci/template-workflows-plugin.git".
>>>>>>>>>>> Could this be related to the "permission denied" issue?
>>>>>>>>>>> shouldn't i have write access as well?
>>>>>>>>>>> I'll really appreciate your help,
>>>>>>>>>>> Shai
>>>>>>>>>>> On Aug 15, 2012, at 1:24 PM, nicolas de loof <
>>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>>> Thanks for the quick response, now i'm getting this:
>>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push ssh://
>>>>>>>>>>>> g...@github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>>>>>> master
>>>>>>>>>>>> ERROR: Permission to jenkinsci/template-workflows-plugin.git
>>>>>>>>>>>> denied to shaibe.
>>>>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>>>>> also, the maven release generated the ssh with my user and pw, should
>>>>>>>>>>>> i remove the user and pw parameters?
>>>>>>>>>>>> Shai
>>>>>>>>>>>> On Wed, Aug 15, 2012 at 12:16 PM, nicolas de loof <
>>>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>>>> don't use ssh://shaibe:shai***@
>>>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git but
>>>>>>>>>>>>> ssh://...@github.com/jenkinsci/template-workflows-plugin.git
>>>>>>>>>>>>> you're identified/authenticated on github by your ssh key, and
>>>>>>>>>>>>> all git commands connect as "git"
>>>>>>>>>>>>>> Hey Nicolas, I need some help uploading my plugin...
>>>>>>>>>>>>>> I'm using windows (don't ask...) and the maven release fails
>>>>>>>>>>>>>> on github authentication.
>>>>>>>>>>>>>> Im getting the same behavior from my shell (cmd):
>>>>>>>>>>>>>> C:\Documents and Settings\shaib\.ssh>ssh -T g...@github.com
>>>>>>>>>>>>>> Hi shaibe! You've successfully authenticated, but GitHub
>>>>>>>>>>>>>> does not provide shell access.
>>>>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin>git push
>>>>>>>>>>>>>> ssh://shaibe:shai***@
>>>>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.gitmaster:master
>>>>>>>>>>>>>> Permission denied (publickey).
>>>>>>>>>>>>>> fatal: The remote end hung up unexpectedly
>>>>>>>>>>>>>> Which user and pw should I use? the github or the jenkins?
>>>>>>>>>>>>>> Do you have any suggestions (besides switching to unix)?
>>>>>>>>>>>>>> On Wed, Aug 15, 2012 at 10:04 AM, shai bhur <
>>>>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>>>>> Thanks for that Nicolas.
>>>>>>>>>>>>>>> When I'm trying to release my plugin in hangs on the maven
>>>>>>>>>>>>>>> release with this line:
>>>>>>>>>>>>>>> [INFO] Executing: cmd.exe /X /C "git push ssh://shaib:****@
>>>>>>>>>>>>>>> github.com/jenkinsci/template-workflows-plugin.git master:
>>>>>>>>>>>>>>> master"
>>>>>>>>>>>>>>> [INFO] Working directory:
>>>>>>>>>>>>>>> E:\gitHub\template-workflows-jenkins-plugin
>>>>>>>>>>>>>>> any idea?
>>>>>>>>>>>>>>> On Wed, Aug 15, 2012 at 9:25 AM, nicolas de loof <
>>>>>>>>>>>>>>> nicolas.del...@gmail.com> wrote:
>>>>>>>>>>>>>>>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <
>>>>>>>>>>>>>>>>> shai.b...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>> My plugin is all about "template workflow" definitions
>>>>>>>>>>>>>>>>>> and how easy it is to create and manage a workflow from a template.
>>>>>>>>>>>>>>>>>> The plugin uses jenkins existing plugins in order to do
>>>>>>>>>>>>>>>>>> that, so whatever can be accomplished using a regular
>>>>>>>>>>>>>>>>>> jobs chaining and plugins configuration can be placed
>>>>>>>>>>>>>>>>>> under
