I was playing with workflow plugin, thought will share my notes. My test
script is based on cd.groovy
<https://github.com/jenkinsci/workflow-plugin/blob/master/aggregator/cd.groovy>
script from workflow-plugin repo. My notes at:
*https://gist.github.com/vivek/8f3ba9e4cfce8ba5e3f6
<https://gist.github.com/vivek/8f3ba9e4cfce8ba5e3f6>*

Instead of building the workflow-plugin from source you can also download
it's experimental beta version that Jesse  released this afternoon..

Testing with master and slave running on the same host was almost straight
forward, *almost*  incase you are new to docker. Although I ended up
spending some time trying to get port forwarding to work between host and
guest vm with Docker 1.0 on Mac. I gave up after realizing it's busted, see
https://github.com/boot2docker/boot2docker/issues/395. So I ended up
running Jetty on the docker VM on my ubuntu box which was pretty easy.

In another setup I ran Jenkins slave on a remote host on a docker a VM. Had
to have my Dockerfile based off evarga/jenkins-slave, primarily to install
curl package and generate ssh keys. SSH keys are important for the portion
of your job running on this remote slave to deploy the war to staging and
production endpoint on the Jetty - that is running on another VM.

If you are planning to experiment on running remote slave, use this
workflow script: https://gist.github.com/vivek/c3767376f714e794455d.

Pretty cool stuff!

vivek.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to