TeamCity NodeJS Plugin and EC2

Hi everyone,

I was wondering if anyone is using the TeamCity Nodej Plugin with an EC2 agent and is having success.  I am running into issues where the plugin isn't detecting the environment which is set in both the .profile and the .bash_profile file to set nvm to use the correct node version.  I have filed a ticket here https://github.com/jonnyzzz/TeamCity.Node/issues/18 but the plugin is preventing my agent from running build since it says it doesn't find node in the path.  The strange thing is that if I used the command line build runner to run the same command that the plugin does 'node --version' it returns a value.  Any tips to get this working correctly with a teamcity ec2 agent?  I tried updating the plugin but teamcity keeps having issues with the built plugin not sure what is going on there.  Any help would be much appreciated on getting this working as it is a blocker at the moment.

teamcity server log error loading my version of the plugin:

[2013-07-26 14:14:47,145]  ERROR - gins.spring.SpringPluginLoader - Failed to initialize spring context for plugin jonnyzzz.node
org.springframework.beans.factory.CannotLoadBeanClassException: Error loading class [com.jonnyzzz.teamcity.plugins.node.server.RunTypesRegistrar] for bean with name 'com.jonnyzzz.teamcity.plugins.node.server.RunTypesRegistrar#0' defined in URL [file:/home/tcadmin/TeamCity-7.1.3/temp/spring-jonnyzzz.node1531800308534870611-spring.config.tmp.xml]: problem with class file or dependent class; nested exception is java.lang.NoClassDefFoundError: jet/JetObject
        at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1253)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:576)
        at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1319)

Thanks,
Jay

Please sign in to leave a comment.