Triggers builds based on incoming DeployDB webhooks, and reports the results back to DeployDB.
Your DeployDB installation should be configured to send all webhook events to
$JENKINS_BASE_URL/deploydb/trigger
Jenkins should be configured with the base URL to your DeployDB instance, so that it knows where build results should be reported to: Manage Jenkins โ Configure System โ DeployDB.
This plugin is built with the Jenkins Gradle plugin.
To start an instance of Jenkins at http://localhost:8080/ with the plugin installed:
./gradlew server
To run the test cases:
./gradlew test
To build the plugin, ready for installation into Jenkins:
./gradlew jpi
The plugin will be written to build/libs/deploydb-jenkins.hpi
.
- You must have a Jenkins account
- Add your credentials to
~/.jenkins-ci.org
in the following form:
userName=...
password=...
To publish a plugin update to the Jenkins update centre:
- Update the top-level
version
property inbuild.gradle
- Commit:
git commit -am "Preparing for release ${VERSION}."
- Tag:
git tag deploydb-jenkins-plugin-${VERSION}
- Push:
git push && git push --tags
- Release:
./gradlew clean publish
Assuming the Gradle build went well, you can confirm here that the release was uploaded correctly: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/deploydb/
The plugin update should appear in the Jenkins update centre within four to eight hours.