4 ms·

I believe referring to it should be in the repository along with code, versioned, and sycned with the repository - like travis.yml. I actually think he/she made

I believe referring to it should be in the repository along with code, versioned, and sycned with the repository - like travis.yml. I actually think he/she made that pretty clear with the use case of referring to previous commits and previous build steps. Most non clicknext developers will forget the extra step of uploading it in the web ui, and/or won't care to version the microsftvisualstudioteamfoundationservices.json seperately

scarface74 9y ago
It's not about "should", it's s preference. I hardly ever need to redo my builds once they are created. Releases on the other hand, I could see a need to change more frequently. If that's your desire, there is nothing stopping you from having one release step that runs a Powershell script, Cake script, etc that is run from your repo.