Re: [Gluster-infra] Can I update /opt/qa for NetBSD?

Hello folks, I've been thinking about a different approach here. I'd like to fork the build.sh/regression.sh/smoke.sh scripts for NetBSD until we unify them. This seems to be the approach with most gains at this point. This way, I can make smaller bite sized changes that can be tested in

Re: [Gluster-infra] Can I update /opt/qa for NetBSD?

Nigel Babu wrote: > I'll definitely appreciate any feedback you can have in terms > of code when it's ready for review. No problem. But regresson infrastructure will catch any issue better that I would, anyway. :-) -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz

Re: [Gluster-infra] Can I update /opt/qa for NetBSD?

Nigel Babu wrote: > * A bunch of cleanup scripts are in build.sh. I think they can move into the > Jenkins job itself. That's what we do for linux boxes. Feel free to do it, but is there a benefit? If it is not broken, do not fix it... > * Some test files have been made to

[Gluster-infra] Can I update /opt/qa for NetBSD?

Hello folks, The /opt/qa folder on NetBSD nodes are on quite an old commit[1]. This means the URL to the logs and cores do not work. The script in master generates the correct URL. Is it safe to update this repo to the latest git master? [1]: