Re: Failure with Github Actions from outside of the organization (out of a sudden!)

Hi Matt, You are still also correct:- https://jenkins-ccos.apache.org/job/websites1/ https://jenkins-ccos.apache.org/job/websites2/ both are floating agents available for all client masters. HTH On Mon, Jan 4, 2021 at 8:45 PM Matt Sicker wrote: > Seems as though my information on that websit

Re: Failure with Github Actions from outside of the organization (out of a sudden!)

Seems as though my information on that websites node is out of date. That's no longer a node and is handled separately: https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-WebSiteDeploymentServiceforGitRepositories If I recall correctly, I believe some i

Re: Failure with Github Actions from outside of the organization (out of a sudden!)

Thanks for explaining the Jenkins security model. Matt> which can write to ASF infrastructure that I know of are all in the Matt> websites node which have scripts and such explicitly to secure its use Matt> case (mostly via the .asf.yaml config options for your site branch). I am afraid I do not

Re: Failure with Github Actions from outside of the organization (out of a sudden!)

Couple things about Jenkins credentials: 1. The credentials are stored encrypted in the controller and are dynamically decrypted and bound to jobs over the Jenkins remoting protocol. A malicious dependency would not be able to gain access to other credentials in Jenkins unless you're running your