Hi, master seems by far enough to me, and I think support for specific other branches should be considered in another future step if it happens to be requested one day. About nightly, I think it's usually not such a good rule. I wrote about it some time ago when I started to deal with release engineering for a bunch of Eclipse projects: https://mickaelistria.wordpress.com/2011/12/07/call-a-spade-a-spade-and-a-nightly-a-snapshot/ . My recommandation would be to use the "Poll SCM" Jenkins feature configured to check SCM @hourly or so. This should overall produce less builds than a nightly (leading to less things to re-download and re-try for clients without actual payload change, so it's more energy-efficient and easier for testing), and also gives more agility by reducing the feedback loop.
Cheers,
