Skip to content
Browse files

JENKINS-23908 - created external invoker

Creation of additional type of build step.
added docs explaining difference.
many classes moved between packages
  • Loading branch information
prospero238 committed Jul 25, 2014
1 parent ceb9be7 commit b4ce4089dc5e9e06bbd2f33538ce01f093340d2c
@@ -1,20 +1,39 @@
Jenkins Liquibase Plugin
# Jenkins Liquibase Plugin

# About

Adds Liquibase as an available build step. See Liquibase documentation at

# Installation

* Install the liquibase-runner plugin.
* Create an empty version of your database on the target server (if applicable).

# Configuration

## "Execute" versus "Invoke"

There are two ways of using this plugin, distinguished by "Execute Liquibase" versus "Invoke Liquibase"


Use this build step if you have an existing liquibase installation and wish to have it run just as if you were doing so
from command line. The build's console log will contain the stdout/stderr output of liquibase.


The "Invoke Liquibase" build step runs liquibase internally and doesn't require an existing installation. Furthermore,
any changesets executed during the build are reported.

# The Future

I'd like to minimize the difference between "Invoke" and "Execute" and have changesets be reported in both types of
build steps.

* Select "Invoke Liquibase" as the step for any Jenkins Job.

@@ -43,7 +43,7 @@
@@ -16,6 +16,7 @@
import java.util.Arrays;
import java.util.List;

import org.jenkinsci.plugins.liquibase.common.Util;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

@@ -7,6 +7,7 @@
import java.util.List;

import org.apache.commons.lang.StringUtils;
import org.jenkinsci.plugins.liquibase.common.Util;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

This file was deleted.

0 comments on commit b4ce408

Please sign in to comment.
You can’t perform that action at this time.