|
On 01/04/2013 04:35 AM, Glyn Normington
wrote:
If the remote build machine is behind a corporate firewall, it is not accessible anonymously by everyone on the planet and is being actively maintained by IT staff, then that gets my two thumbs up. By all means, put your committer ID's private key there and push all you want. On the other hand, if your remote build machine is running a publicly web-accessible CI system with an open-to-the-world SSH port, I don't feel that the private key to your shell-enabled eclipse.org account is in a safe location. This is consistent with my position regarding committer private keys on our own publicly web-accessible Hudson instance. If committers really feel that the our CI system should have the ability to push commits to Git and push builds to the downloads area via a committer's account (and I agree, this would be immensely convenient), then we could perhaps consider closing hudson.eclipse.org to the anonymous users, thus requiring a committer account and authentication to access Hudson? Denis
--
Denis Roy Director, IT Services Eclipse Foundation, Inc. -- http://www.eclipse.org/ Office: 613.224.9461 x224 (Eastern time) [email protected] |
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
