+1 and thanks if you want to spend the time to get something temporary
up to unblock QA.
Different credentials would seem like a good thing re: security, but as
long as we can discern between "official" and "temporary replacement", I
don't mind much.
Bonus points if you can also document how you did it (since I would
guess it will be beneficial down the road).
On 8/30/18 11:10 AM, Sean Busbey wrote:
On Thu, Aug 30, 2018 at 9:44 AM Misty Linville <[email protected]> wrote:
I'm concerned that getting the logs will take a lot of your time. Is there
a way to have the automation put them somewhere where the patch author can
get to them when needed? Also how much time will this take to set up? Will
it be worth it? Will this initial setup be useful long-term in any way?
I don't know of a public-facing storage place I can dump the logs, so
I don't think automating the logs is feasible short term.
It'll probably take me, on the outside, an hour longer than getting
the stuff I'm going to do for myself done. Probably a lot less now
that the logic of the "pull suitable issues out of JIRA" job is
something maintained in source control over in the Yetus project.
I guess long term it'd be useful because I'd have a run guide for
doing it again if ASF jenkins goes down?
