Groovy Plugin Will Not Load

Plugin does not seem to work with TC 4.5.1.  Receive the following error and server does not start:

ERROR -   jetbrains.buildServer.SERVER - Failed to initialize TeamCity server, due to error (enable debug to see the whole stacktrace):org/codehaus/groovy/control/CompilationFailedException

10 comments
Comment actions Permalink

Does anyone know the latest on this? We are also trying to get the Groovy Plugin to work with Team City 4.5.x. So far no luck. If anyone has found an acceptable workaround or knows the possible release date on an updated plugin I would be eternally grateful

Thanks

0
Comment actions Permalink

Steven,

Did you put additional groovy libs into WEB-INF/lib ?

If yes, please post the full log.

UPD: Sorry, missed the date of the post

0
Comment actions Permalink

Grant,

The plugin works fine for me. Could you provide any details like server logs, errors, etc. ?
Please doublecheck you performed all the installation steps correctly.

0
Comment actions Permalink

Yes. My problem was all about not putting the correct files into the proper location.

I installed the libraries into \TeamCity\webapps\ROOT\WEB-INF\lib
and the groovyPlug.zip into \Documents and Settings\TeamCity\.BuildServer\plugins

Once I did that the plugin loaded successfully.

0
Comment actions Permalink

Don't know why, when I checked the logs again last time the server did not restart correctly. I restarted again and behold the Groovy-Plug worked! Thanks for taking time out of your day to answer my question.

Grant-

0
Comment actions Permalink

Upgraded to TC 5.x and installed latest Groovy Plug. TC server starts fine, however, the build will not execute becuase TC says there are no compatible agents found. The project shows the following message under the Compatible Agents tab.

Unmet requirements: system.build.vcs.lastIncluded.revision                  exists

0
Comment actions Permalink

Steven,

Seems, there is an issue with references to GroovyPlug-provided params from build configuration settings.

Sorry for the inconvenience.

Actually, due to TW-4527 fix, TeamCity 5.0 provides last affected revision in the standard "build.vcs.number.*" properties.

0
Comment actions Permalink

Steven,

The issue is in fact in the way the plugin provides lastIncluded* properties, not the core of TeamCity.

Can you please try updated GroovyPropertiesProvider.groovy script from build #28?
You can install the new build. If you modified the file yourself, you will need to use updated verison. If you did not modified the scripts, just installing a new build should help.

0
Comment actions Permalink

Yegor,

To be honest with you, the only thing I was using the Groovy plug for was the last build revision number. Now that TC supplies the revision number for the affected check-in and not the entire repository I currently do not have a need for the plug-in.

Thanks,
Steve

0
Comment actions Permalink

Steven,

NP : )
Actually we do try to make TeamCity contain all the necessary functionality without need to install extra plugins as a kind of workaround.

0

Please sign in to leave a comment.