Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Coordinator on the plugin site for more information.

This plugin acts like a coordinator that makes other jobs to build in a particular sequence as pre-defined.

There are serial and parallel building patterns, which should have already covered most scenarios.

Why?

I've seen different organizations spending their own effort to customize their CI tools, especially for job running dependency definitions. 

Say first run Job A, then Job B & Job C in parallel, then Job D, then others, etc.

This plugin is meant to make this by drag & drop, and clicks. It would be easy to trace the building histories including the person who triggers the job,

build number, launch time, duration & status in each atomic job.

In a word, it's more like a dash board to keep all relevant information in a page view.

Demo

Live Demo

For a running Jenkins instance with Coordinator plugin installed, go to jenkins.unendedquest.com

Configure Page

Trigger Page

Execution Plan

Parameters Passing To Atomic Jobs

Building Page

Change Log

Version 1.0.0 (Nov 1, 2014)

  • basics
  • No labels

2 Comments

  1. Unknown User (jsirex)

    Getting:

    Atomic Job: TEST-job not found
    Build step 'Coordinator' marked build as failure

    But job exists

    Logs:

    Nov 12, 2014 8:04:11 PM org.jenkinsci.plugins.coordinator.model.CoordinatorBuild doAtomicBuildResultTableRowHtml
    WARNING: Insufficient parameters to retrieve specific build, jobName: TEST-job build #: 0
    

    What I'm missing?

    1. Unknown User (ace_jl_han)

      Hi, there.

      I'm so sorry for this late reply.

      Please fill an issue with detail log at github issue, so that I could follow up, thx.