Hello, I'm toying with the idea that each job will have commands to install dependencies and update the /opt/qa folder. This will make the whole process of adding a new node in the testing pool trivial requiring not a lot of effort from the infrastructure team.
However, if we break the /opt/qa repo, we'll spread the breakage everywhere. The fallback for errors would be to push a revert. Thoughts on this idea? -- nigelb _______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
