play-plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID play-autotest-plugin Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
0.0.12
Sep 29, 2011
1.409
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Takafumi Ikeda (id: ikeike443)
Usage Installations 2013-Apr 374
2013-May 389
2013-Jun 406
2013-Jul 430
2013-Aug 440
2013-Sep 425
2013-Oct 464
2013-Nov 459
2013-Dec 461
2014-Jan 473
2014-Feb 511
2014-Mar 523

Play! framework plugin

This plugin integrates Play! framework to Jenkins.
It enables Jenkins to run play commands and to generate test-result view per build looks like Calimoucho – Play! CI server.

code: https://github.com/ikeike443/HudsonPluginForPlay

Getting Started

0. Prepare Play! framework.

Of course you should make sure Play! framework already installed on your Jenkins server.
This plugin works with Play 1.1 or later.

1. Configuration

After installed, indicate the path to Play! script at global configuration.

Select 'Play!' at build configuration. 

And then set play commands each text boxes.

This plugin do each commands in this order you set.

You can set any options supported each commands.
And also you can override play path per jobs like the above.

Check 'Play! auto-test reports' at post-build configuration.

And also make sure your play app will be updated from scm such as cvs, svn or git.

2. Run and see the test results

After configuration, run your job.

Then it will appear 'Play! test result' menu on side panel.

Click 'Play! test result' and you can see the results by Calimoucho - Play! CI Server - style!

If your test case succeed, it's green.

If failed, it's red and build fails, too.

see in japanese: http://d.hatena.ne.jp/ikeike443/20110124/p1

Options

To configure play application path

When your project structure is like below, you might indicate application path.

workspace/
    web/
    somemodule/
    playapp/

You can configure play application path like below:

To use parameterized build

You can also use parameterized build.

It is Jenkins function, play-plugin supported this from ver 0.0.9.

If you would like to know how to use this, please see the link.

Change log

Version 0.0.12 (Sep 29, 2011)
  • Bug fix: ensure job doesn't fail without configuring application path
Version 0.0.11 (Sep 28, 2011)
  • Bug fix: to resolve workspace path when used in slave server
Version 0.0.10 (Sep 21, 2011)
  • Modified supported Jenkins version number for adapting Cloudbees support
Version 0.0.9 (Sep 18, 2011)
  • Supported to allow using parameterized build
  • Enable to configure play application path instead of using the workspace root path as application path
  • Ensure to quote application path when executing
Version 0.0.8 (Jul 27, 2011)
  • Enable to run multiple commands at once with each options
Version 0.0.5 (Jul 3, 2011)
  • Enable to configure play path per job
Version 0.0.4 (Feb 7, 2011)
  • Fixed a bug builder's global.jelly misses its setting after Jenkins restart 
  • Supported unstable build status when some tests failed
Version 0.0.1 (Jan 25, 2011)
  • First release

Labels

Edit
plugin-post-build plugin-post-build Delete
plugin-report plugin-report Delete
plugin-buildwrapper plugin-buildwrapper Delete
plugin-external plugin-external Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment