Followup to this: Do you typically run the entire test suite on changes? Just the suite for a specific sub-project? I noticed that some of the individual test cases take 4+ minutes on my VM so I wanted to see what others do.
- jonathan From: <Halterman>, Jonathan Halterman <[email protected]<mailto:[email protected]>> Date: Thursday, June 25, 2015 at 11:14 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Dev workflow I just wanted to ping the community to get a sense for what dev workflow other developers are using. The wiki hints at a few possibilities – using ambari-vagrant, using the dev-tools' Docker, but since building/installing/running Ambari is a bit different than other projects, I’m curious what the end to end dev workflow looks like. Some specific questions: * What’s your general workflow for deploying and testing changes in an ambari-server? * Do you run ambari-server for development on your local machine? * Do you run ambari-server in a VM or container? If so: * Do you use synced folders or shared volumes? * If so, what kind of synced folders (vagrant, nfs, rsync)? * Are you able to successfully build ambari when using synced folders? * Are you able to successfully build an rpm/deb when using synced folders? * If you don’t use synced folders, what’s your workflow for testing code? * Does the ambari apt/deb package need to be installed in order to start ambari-server for development purposes? * How do you start ambari-server for development purposes (with the ability to attach a debugger)? Cheers, Jonathan
