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 [email protected]
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 <[email protected]> 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 <[email protected]
> > wrote:
>
>> repo created :
>> https://github.com/jenkinsci/template-workflows-plugin
>> CI job
>> https://jenkins.ci.cloudbees.com/job/plugins/job/template-workflows
>>
>>
>> 2012/8/15 shai bhur <[email protected]>
>>
>>> Hi,
>>>
>>> Created the plugin repo:
>>> https://github.com/shaibe/template-workflows-jenkins-plugin
>>> Guess I can't release it until you fork it to  jenkinsci account -
>>> right?
>>>
>>> Shai
>>>
>>> On Tue, Aug 14, 2012 at 1:18 PM, Shai Ben-Hur <[email protected]>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 :)
>>>>>
>>>>> 2012/8/14 Shai Ben-Hur <[email protected]>
>>>>>
>>>>>  Hi Nicolas,
>>>>>>
>>>>>> 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,
>>>>>>>
>>>>>>> I wrote a new plugin called "Template Workflows", you can read all
>>>>>>> about it here:
>>>>>>> https://wiki.jenkins-ci.org/**di**splay/JENKINS/Template+**Workflo**
>>>>>>> ws+Plugin<https://wiki.jenkins-ci.org/display/JENKINS/Template+Workflows+Plugin>
>>>>>>> I would like to host it in gitHub, here is my id: shaibe
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Shai
>>>>>>>
>>>>>>>
>>>>>
>>>
>>
>

Reply via email to