Reducing the time to test patches which doesn't modify code

[Amar Tumballi <atumball@xxxxxxxxxx>]

Today, any changes to glusterfs code base (other than 'doc/') triggers the regression runs when +1 Verified is voted. But we noticed that patches which are changes in 'extras/' or just updating README file, need not run regressions.

So, Nigel proposed the idea of a .testignore file (like .gitignore)[1]. Content in which are paths for files to ignore from testing. If a patch has all the files belonging to this file, then the tests wouldn't be triggered.

Anyone sending patches in future, and the patch needs to add a new file, see if you need to update .testignore file too.

[1] - https://review.gluster.org/17522

Regards,

Amar

--

Amar Tumballi (amarts)

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel