Skip to end of metadata
Go to start of metadata

Plugin Information

Distribution of this plugin has been suspended due to unresolved security vulnerabilities, see below.

The current version of this plugin may not be safe to use. Please review the following warnings before use:

This plugin allows Jenkins to invoke Grails tasks as build steps.

Change Log

Version 1.7 (Sep 24, 2013)
  • [FIXED JENKINS-18235] set PATH with GRAILS_HOME/bin
  • eval properties. (JENKINS-7750)
  • Added Task Note
  • build should be UNSTABLE, if tests failed.
  • added and enhanced integration tests.
  • replace Jenkins default variables. (JENKINS-14345)
  • Added evaluation of variables in grails targets.
  • Added default value for grails.work.dir
  • [FIXED JENKINS-7702] Tomcat sometimes defines a $JAVA_OPTS inappropriate for subprocesses.
  • fixed duplicated args.
  • Add options for --plain-output, --stacktrace, --verbose, and --refresh-dependencies
Version 1.6.3 (Jul 18, 2012)
  • Fixed bug. JENKINS-14345 Grails wrapper doesn't respect "Project Base Directory"
Version 1.6.2 (May 18, 2012)
  • Fixed problem that Grails Wrapper doesn't work, if 'Grails Installation' is selected.
Version 1.6.1 (May 18, 2012)
Version 1.6 (May 16, 2012)
  • Added the support for Grails Wrapper
Version 1.5 (Oct 10, 2011)
  • Fix problem that fails when running on Slave. JENKINS-9649
  • Added Grails auto installer.
Version 1.3 (May 6, 2010)
  • Added explicit support for forcing an upgrade
  • changed project.work.dir to grails.project.work.dir
Version 1.1 (Feb 15, 2010)
  • Update code for more recent Hudson
Version 1.0.5 (Sep 25, 2009)
Version 1.0.2
  • Added evaluation of environment variables in grails targets, e.g. include the BUILD_NUMBER in your app.version:
  • Clean "upgrade -force" "set-version 1.0.${env['BUILD_NUMBER']}" war*
    You can use every Hudson provided variable, BUILD_NUMBER, BUILD_ID, ...
Version 1.0.1
  • Fix problem that caused some configuration information to be lost when the container was restarted
Version 1.0
  • Initial release
Version 0.15
  • Added option to specify base directory if the Grails project is not at the root of the job checkout

2 Comments

  1. Is there any workaround for this plugin and its contributors being MIA?

    Also, I understand why distribution of the plugin may be suspended, but shouldn't people running their servers be able to decide if they want to install and run it? In our environment this issue is irrelevant as all users already have access to execute whatever they want on our build server.  Meanwhile I cannot setup a new build server because all traces of this plugin have been removed because of this.

    Any help appreciated.

  2. @mseelye : 

    To install the insecure version 1.7 of the plugin: 

    git clone https://github.com/jenkinsci/grails-plugin.git

    git checkout 163ddbf86a1268f1482db68ed3ecf766673bc5f9

    mvn package

     

    Upload the target/grails.hpi to your Jenkins (Plugin management > Advance)