alitheg commented on issue #613: URL: https://github.com/apache/tooling-trusted-releases/issues/613#issuecomment-3835631696
Ok, so I think we probably want m5.xlarge. That's 4 vCPU and 16GB RAM, which is equivalent to what the Github hosted runners provide. We can always go for more if required in future but since we're not actually doing any compiling on our runners (at present at least) they probably don't need to be any bigger (we could maybe even go smaller for this reason - m5.large is 2 vCPU and 8GB). In terms of software, I'm not sure how much we want to preinstall. The testbed I've been using, which I've replicated in our existing builds is Java 17 (Temurin) and Maven 3.9. I had some problems with Njord on Maven 3.8 (which I either got from apt or from the docker image I'm testing with), and 4 is in preview still. Other than those, we need jq, curl bash and rsync. I can't find any specific guidance on what naming/labelling we should follow - but we should probably label by what's on it so that we know it's got Java. Or, perhaps we want to label as ATR specifically? As a side note - I read a note on Github that pointed out we should make sure we don't ever run builds on these runners that are PR-triggered (for public repos at least) because someone could fork your repo and run malicious code by creating a PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
