> It would be on transient hosts that essentially only I had access to (and I guess my employer?). So we'd get results posted to JIRA but getting to actual logs would be a bit more of a pain.
For your consideration, and probably not for this specific instance... Setting something up in AWS that can be launched from an AMI with keys shared among project PMC would allow multiple interested parties to chip in for hosting. Perhaps we could launch instances with such an AMI, and would automatically contribute to hosting test resources for the project simply by doing so. On Thu, Aug 30, 2018 at 7:36 AM Sean Busbey <[email protected]> wrote: > Hi folks! > > As background, the ASF jenkins master (what you see when you go to > builds.apache.org) went down Tuesday night[1]. ASF Infra is dutifully > working to restore it to full capabilities without losing information > on prior builds. Their most recent estimate has a return to normal > sometime tonight or early tomorrow morning. > > I have a few patches I'd like to still see precommit results for > before they get signed off on. I was going to set up checking them > with test-patch myself, but it would only be marginally more work for > me to automate it. > > What do folks think about me doing this as a stop-gap while ASF Jenkins is > down? > > It would be on transient hosts that essentially only I had access to > (and I guess my employer?). So we'd get results posted to JIRA but > getting to actual logs would be a bit more of a pain. > > Does anyone feel strongly about me using the existing QABot JIRA > credentials vs making a "I'm a placeholder QABot" account with its own > credentials? > > [1]: https://status.apache.org/incidents/4zl6mkyrg8qt > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
