Other Triggers - Like Nuget Web service

Continua CI Discussion
1

Guys,

I was just thinking about how to manage Nuget package updates and CI.  I had a quick look around and there didn't seem to be anything that would allow you to trigger a set of builds based on alternate types of triggers without doing a kludge.  If I had a simple repo and an app which checked all the Nuget packages I use and then monitor changes to those packages and push something into a Monitoring repository, could I then trigger off a series of Builds of other projects, configuration compile testing build. Does this sound sensible? 

I've got another similar situation with code generation templates, where I want to be able to change a template and then use Continua to "test" if those changes cause compile issues across a range of Visual Studio Solutions. Any guidance welcome.

2

Hi Jamie

What you are asking sounds like Dependencies to me (unless I’m misunderstanding your post). Dependencies is a feature we have yet to implement, but it’s high on the list of features for post v1 updates.

What you can do is use the Build Completion trigger, ie your Template repo triggers a Template config build, when that finishes, any other configurations with a Build Completion Trigger on the Template config will start.

3

Sounds like that’s what I’m after, will look into that feature.