@alexmedia A release definition can require multiple artifacts / inputs, and one of the types allows to pull the contents from a source code repository (Git is likely the easiest one). Once you have those files you can still run Maven, MSBuild or whatever you require as part of your release definition. Note though that I sometimes employ a trick where I download extra files and scripts from a Nuget feed. To do so, I have an inline Powershell script which spits out a package.config, then add a Nuget downloading task which reads that and stores the result in a specific folder. VSTS does have a nicer way to do it with deep integration with VSTS-hosted feeds, but those features require a separate "Package Management" user license. The trick above can instead pull Nuget packages from any feed AND it doesn't require you to pay for VSTS package management (the latter is a bit of a WTF: you can state that your release def requires a Nuget package as artifact but somebody who has no license for Package Management cannot run that release).