Vinod,

Great point and it crossed my mind too. The argument list to this function call will become longer and longer as new cloud settings fields are added which the scheduler needs. I'm working on adding Docker support which will add more args to the list (enable/disable docker support, docker executor path, etc.). Since the MesosCloud object encapsulates all these fields coming from the cloud config it made sense to simply pass in its reference to the JenkinsScheduler class. It will avoid the startScheduler() and updateScheduler() signature from changing. What do you think?

Thanks.