strider-cd / drone Goto Github PK

Basically all that plugins need to do is take a config, job data, and interact with the system.

Systems could be inside of docker or some other environment.

I feel like users should be able to reuse gulp, grunt, and npm tasks easily, as well as raw bash or whatever other shell they want.

I can envision plugins exporting an array like:

// ember-cli build
module.exports = {
  name: 'ember-cli',
  droneAPIVersion: '^1.0.0',
  tasks: [{
    name: 'install',
    description: '...', // markdown?
    schema: installConfigJSONSchema,
    // function (jobData, taskConfig, cache, callback)
    action: require('./install')
  }, {
    name: 'test',
    description: '...',
    schema: testConfigJSONSchema,
    action: require('./test')
  }, {
    name: 'run',
    description: '...',
    schema: runConfigJSONSchema,
    action: require('./run')
  }, {
    name: 'cleanup',
    description: '...',
    schema: cleanupConfigJSONSchema,
    action: require('./cleanup')
  }]
]

Now the drone has the following tasks:

• ember-cli.run
• ember-cli.test
• ember-cli.install
• ember-cli.cleanup

Each of these tasks can have config options, with the defaults being sane. What each action does is up to the plugin, it could run straight up bash or use node and do fs.*, etc.

Core will send a workflow as part of the job, which is an array of tasks paired with configs for each task.

I think this is stage one of the plugins, from there we can write different base plugins that allow for easy development of different types of tasks (be extending them, etc.), like ones that run in docker or perform complicated bash stuff with ssh context, etc..

Feeling like it could be simplified with a JWT token. Token has CORE URL, and the drone token that will identify the drone.

This makes it super simple: DRONE_TOKEN=... npm start