Ah I figured you were running Bamboo on a personal box.
Even still though, if you're running your own instance of Bamboo on a
shared box, it still should be ok to host your ssh key there, right
(i.e. your home dir is still protected)? Plus you can generate a new
key for this purpose so you're not compromising any of your oft-used keys.
--Glen
Dan Diephouse wrote:
> Sure, but do I really want to put my ssh private key and all that on a build
> server where other people have access to it. The answer to that is no in
> case you were wondering :-)
>
> On Tue, May 13, 2008 at 8:02 PM, Glen Daniels <glen@wso2.com> wrote:
>
>> From what I understand, it should be as simple as doing a "mvn deploy" from
>> Bamboo - but you need to make sure that the Bamboo process is running under
>> your username with an appropriate settings.xml in your ~/.m2 dir.
>>
>> --Glen
>>
>>
>> Dan Diephouse wrote:
>>
>>> We have a bamboo instance set up which runs the builds, but I'm not sure
>>> if
>>> I can configure this to deploy the builds or not. I'll check into it.
>>>
>>> In the mean time, I'm happy to push out builds occassionally.
>>>
>>> On Tue, May 13, 2008 at 11:44 AM, Jim Ancona <jim@anconafamily.com>
>>> wrote:
>>>
>>> I know that trunk builds are sometimes deployed to the repository at
>>>> http://people.apache.org/repo/m2-snapshot-repository. I'm pretty sure
>>>> that
>>>> this is a manual process right now, with a developer (thanks, Dan!)
>>>> obliging
>>>> when someone asks. Is there any reason that this process couldn't be
>>>> automated? I realize that "lack of time" is a valid reason, so I'm
>>>> willing
>>>> to volunteer if there's anything I can do to help.
>>>>
>>>> Thanks,
>>>>
>>>> Jim
>>>>
>>>>
>>>
>>>
>
>
|