www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy <ol...@apache.org>
Subject Re: Publishing snapshot jars with jenkins
Date Sat, 04 Aug 2012 18:38:08 GMT
2012/8/4 Travis Crawford <traviscrawford@gmail.com>:
> Hey Olivier -
>
> Thanks for the quick response! The job is:
>
>     https://builds.apache.org/job/Hcatalog-trunk-build/
>
> Its build system is ant, and publishes using the maven ant plugins.
> This means ~/.m2/settings.xml must have credentials for the snapshots
> repo.
All nodes have correct settings.xml (normally :-) )
>
> We're still in the process of adding support to publish these
> artifacts, so any requirements to publish from CI can be incorporated.
>
> Our working branch is
> https://github.com/traviscrawford/hcatalog/compare/HCATALOG-132_publish_to_maven
> if you're interested in seeing specifics about how we're publishing.

For snapshots, IMHO gpg is not needed. And that will be a bit
complicated for installing key... on jenkins slaves.
You're in the good way to use maven ant task !

>
> --travis
>
>
>
> On Sat, Aug 4, 2012 at 10:15 AM, Olivier Lamy <olamy@apache.org> wrote:
>> 2012/8/4 Travis Crawford <travis@apache.org>:
>>> Hey build gurus -
>>>
>>> In HCATALOG-132 we're getting ready to publish jars in maven, and
>>> would like to automatically publish snapshot jars after each
>>> successful CI build.
>>>
>>> This would require permissions on the CI machine to publish artifacts,
>>> as well as gpg credentials to sign them.
>> Other builds do not publish gpg for snapshots.
>>>
>>> Is publishing snapshot jars to maven from CI something we can setup?
>>> If so, any pointers in the right direction?
>> Which build tool are you using ? Which job do you want to setup ?
>>
>>>
>>> Thanks!
>>> Travis
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Mime
View raw message