Fw: Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose?
Dear OpenWhiskers, I will bring this question and the current solution to the dev list. Our Travis build of openwhisk-release, it will import the public key( https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_pub.gpg ) and the private key( https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_sec.gpg.enc ), available in openwhisk-release repo. Private key is encrypted. The public key has already uploaded to the SVN repo as well: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS, so it can be used to verify the signature of each artifact. The name of this pair of keys is OpenWhisk Release Bot, and the email I used is openwhisk-release-...@apache.org. They are used to indicate that the Travis build is the guy which pushes the release artifacts. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States - Forwarded by Vincent S Hou/Raleigh/IBM on 03/13/2018 05:17 PM - From: "Vincent S Hou" To: priv...@openwhisk.apache.org Date: 03/08/2018 11:13 AM Subject:Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose? Dear OpenWhisk mentors, So far we have been automating the release process of OpenWhisk, and already created a repository dedicated to it: https://github.com/apache/incubator-openwhisk-release We are now able to release the source code artifacts in manual mode and automated mode, and Travis build is used in the automated mode to sign the artifacts and push them to the SVN. We try to avoid using some private accounts to generate the PGP keys and update the SVN repository. I am wondering what can be the proper credentials I can use to generate the PGP keys and access the apache SVN. Do we have a general account for the build purpose? Thank you. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
Fw: Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose?
Dear OpenWhiskers, I will bring this question and the current solution to the dev list. Our Travis build of openwhisk-release, it will import the public key( https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_pub.gpg ) and the private key( https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_sec.gpg.enc ), available in openwhisk-release repo. Private key is encrypted. The public key has already uploaded to the SVN repo as well: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS, so it can be used to verify the signature of each artifact. The name of this pair of keys is OpenWhisk Release Bot, and the email I used is openwhisk-release-...@apache.org. They are used to indicate that the Travis build is the guy which pushes the release artifacts. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States - Forwarded by Vincent S Hou/Raleigh/IBM on 03/13/2018 05:17 PM - From: "Vincent S Hou" To: priv...@openwhisk.apache.org Date: 03/08/2018 11:13 AM Subject:Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose? Dear OpenWhisk mentors, So far we have been automating the release process of OpenWhisk, and already created a repository dedicated to it: https://github.com/apache/incubator-openwhisk-release We are now able to release the source code artifacts in manual mode and automated mode, and Travis build is used in the automated mode to sign the artifacts and push them to the SVN. We try to avoid using some private accounts to generate the PGP keys and update the SVN repository. I am wondering what can be the proper credentials I can use to generate the PGP keys and access the apache SVN. Do we have a general account for the build purpose? Thank you. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
