Re: withAWS step complains about not being able to support closures in the script console

> > > Ok, I think I've solved it. Well, I solved my core issue, which was that the > vars/publishToS3.groovy script was not being properly identified. I couldn't > figure out how to identify publishToS3. It could find neither publishToS3, > nor com.seven10.publishToS3. I think, because there wa

Re: withAWS step complains about not being able to support closures in the script console

Hi Richard, thanks for your response. publishToS3 is called in another custom step that is then called by the pipeline. The reason for the "publish" bit is I kept getting errors along the lines of "duplicate class load attempted" (see my post here

withAWS step complains about not being able to support closures in the script console

I'm having a TON of problems getting the pipeline system setup and working. One issue in particular is troubling me. I have a shared library that has a custom step in vars/publishToS3.groovy. It looks like this: #!/usr/bin/env groovy package com.seven10; def call(hashmap){ def src_file = hashm

Launching a slave as a docker-cloud (formerly tutum) stack

Hello, I am trying to put together a jenkins system that is hosted on AWS through docker-cloud. I have created a few stacks that have the modules that I might want to test against (mongo, rabbit, etc). The Jenkins master is also running on its own stack. I wrote two scripts, one on the master (c