[bradrydzewski]

The workflow is pretty basic right now, however, we plan on adding matrix and parallel builds in the near future. Could you elaborate a bit more on your workflow? I definitely want to make sure Drone supports more than just simple use cases.

[oblio]

From my experience with Jenkins, as a build/deployment/release engineer the past 6 years, you probably want to:

- chain jobs - needed for larger projects; ideally this should even allow composing jobs to have nice, modular jobs which can be launched standalone or chained

- some kind of powerful templating system - needed for reducing configuration duplication; ideally this would keep track of all the "children" in case of updates

- you also probably need enterprisey features later on, like SSO using AD/LDAP, fine grained ACLs based on groups, etc

But job chaining and job templating should be higher priorities for the workflows since they affect the overall architecture. Jenkins has been struggling for a while to re-architect to allow this, not entirely successfully.

You also want a plugin system if you don't have one, especially one with dependencies (i.e. the Git plugin can server as a dependency for the Github plugin).

My 2 € cents :)

[cpsaltis]

Chaining jobs and parallel ones are both very important. Especially the last one since it saves you a lot of time waiting the tests to complete. Also a big plus is to be able to run certain set of tests only when a specific event is fired eg ran test A when somebody pushes to branch X