Re: Travis apache credentials
I was imagining the signing itself would still be manual. (Frankly, I would feel odd having travis sign them for me...) On Mon, Aug 20, 2018 at 10:20 PM Lukasz Cwik wrote: > > If you can't get an answer quickly, its best to read the Apache policy on > release signing: http://www.apache.org/dev/release-signing.html > > On Mon, Aug 20, 2018 at 10:16 AM Pablo Estrada wrote: >> >> This would mean that released artifacts are signed with two different keys >> (wheels with travis / jars and others with release manager's). Is this >> consistent with Apache policy? >> Just checking : ) >> -P. >> >> On Mon, Aug 20, 2018 at 9:47 AM Boyuan Zhang wrote: >>> >>> Hey Robert, >>> >>> I think your idea would be possible if following things are possible: >>> 1. Link beam-wheels into travis-cli. I'm not sure who has the right >>> permission to perform this operation. >>> 2. We have a common svn credential or one of the beam committers would like >>> to put his(or her) credential into beam-wheels. >>> >>> If we can configure these 2 things, then new commit pushed into beam-wheels >>> can trigger a new build. >>> >>> Boyuan >>> >>> On Mon, Aug 20, 2018 at 2:46 AM Robert Bradshaw wrote: Boyaun set up a nice repository for building Python wheels at https://github.com/apache/beam-wheels . Does anyone know if it would be possible to get SVN credentials for travis so every user wouldn't have to fork the repository and put their own in?
Re: Travis apache credentials
If you can't get an answer quickly, its best to read the Apache policy on release signing: http://www.apache.org/dev/release-signing.html On Mon, Aug 20, 2018 at 10:16 AM Pablo Estrada wrote: > This would mean that released artifacts are signed with two different keys > (wheels with travis / jars and others with release manager's). Is this > consistent with Apache policy? > Just checking : ) > -P. > > On Mon, Aug 20, 2018 at 9:47 AM Boyuan Zhang wrote: > >> Hey Robert, >> >> I think your idea would be possible if following things are possible: >> 1. Link beam-wheels into travis-cli. I'm not sure who has the right >> permission to perform this operation. >> 2. We have a common svn credential or one of the beam committers would >> like to put his(or her) credential into beam-wheels. >> >> If we can configure these 2 things, then new commit pushed into >> beam-wheels can trigger a new build. >> >> Boyuan >> >> On Mon, Aug 20, 2018 at 2:46 AM Robert Bradshaw >> wrote: >> >>> Boyaun set up a nice repository for building Python wheels at >>> https://github.com/apache/beam-wheels . Does anyone know if it would >>> be possible to get SVN credentials for travis so every user wouldn't >>> have to fork the repository and put their own in? >>> >>
Re: Travis apache credentials
This would mean that released artifacts are signed with two different keys (wheels with travis / jars and others with release manager's). Is this consistent with Apache policy? Just checking : ) -P. On Mon, Aug 20, 2018 at 9:47 AM Boyuan Zhang wrote: > Hey Robert, > > I think your idea would be possible if following things are possible: > 1. Link beam-wheels into travis-cli. I'm not sure who has the right > permission to perform this operation. > 2. We have a common svn credential or one of the beam committers would > like to put his(or her) credential into beam-wheels. > > If we can configure these 2 things, then new commit pushed into > beam-wheels can trigger a new build. > > Boyuan > > On Mon, Aug 20, 2018 at 2:46 AM Robert Bradshaw > wrote: > >> Boyaun set up a nice repository for building Python wheels at >> https://github.com/apache/beam-wheels . Does anyone know if it would >> be possible to get SVN credentials for travis so every user wouldn't >> have to fork the repository and put their own in? >> >
Re: Travis apache credentials
Hey Robert, I think your idea would be possible if following things are possible: 1. Link beam-wheels into travis-cli. I'm not sure who has the right permission to perform this operation. 2. We have a common svn credential or one of the beam committers would like to put his(or her) credential into beam-wheels. If we can configure these 2 things, then new commit pushed into beam-wheels can trigger a new build. Boyuan On Mon, Aug 20, 2018 at 2:46 AM Robert Bradshaw wrote: > Boyaun set up a nice repository for building Python wheels at > https://github.com/apache/beam-wheels . Does anyone know if it would > be possible to get SVN credentials for travis so every user wouldn't > have to fork the repository and put their own in? >
Travis apache credentials
Boyaun set up a nice repository for building Python wheels at https://github.com/apache/beam-wheels . Does anyone know if it would be possible to get SVN credentials for travis so every user wouldn't have to fork the repository and put their own in?
