Great - thanks for the info! When this change is committed we'll try
publishing snapshots from the existing jenkins job.
--travis
On Sat, Aug 4, 2012 at 11:38 AM, Olivier Lamy wrote:
> 2012/8/4 Travis Crawford :
>> Hey Olivier -
>>
>> Thanks for the quick response! The job is:
>>
>> https://
2012/8/4 Travis Crawford :
> 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
> rep
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.
We're still in the process of adding s
2012/8/4 Travis Crawford :
> 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 cred
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.
Is publishing snap
On Sat, Aug 4, 2012 at 1:56 AM, Gavin McDonald wrote:
> I have a theory its my fault, the Jenkins process was down earlier, so I
> started it via jnlc in my
> User account - it could be that the Jenkins user does not have correct perms
> when started via
> Another user ?
That might be it. I conne
