On Tue, May 14, 2013 at 12:08 PM, CloudBees Support <[email protected]>wrote:
> ## In replies all text above this line is added to the ticket ## > > Update: Re: github wrangling (ticket #9866) > > You are registered as a cc on this help desk request and are thus > receiving email notifications on all updates to the request. > > Reply to this email to add a comment to the request. > > > > ---------------------------------------------- > > Ryan Campbell, May 14 15:08 (EDT) > > I replied on the list. Let me know if the discussion pops up again. I > didn't see any follow ups, and so I unsubscribed from the deluge. > > Ryan Campbell > > CloudBees, Inc > > ---------------------------------------------- > > Adrian Cole, May 11 16:02 (EDT) > > Hi, CB peeps. > > Thanks for the years of help you've given to jclouds! > > We currently are considering CloudBees Dev@Cloud to push snapshots to the > ASF repos instead of Sonatype as we currently operate. I suppose our > current means of just storing creds is perceived as "not safe enough". > Fair point. Someone could grab these credentials if they hacked into > cloudbees and publish a bad snapshot. We don't want that. > > What do you recommend for this? Are there other ASF projects that use > dev@cloud to publish snapshots to the official repos? How do they do it? > > Cheers, > -A > > > > On Sat, May 11, 2013 at 12:47 PM, Andrew Bayer <[email protected] > >wrote: > > > Yup. Exactly that. > > > > A. > > > > > > > > On May 11, 2013, at 12:45 PM, Andrew Phillips <[email protected]> > > wrote: > > > > >> I'm wary of a CB job because we then have to put the deploy key into > > the job > > > > > > Could you explain? You mean the credentials to be able to *push* to the > > jclouds GitHub account? > > > > > > ap > >' > > > > -------------------------------- > This email is a service from CloudBees Support >
