So not knowing what your requirements are, it seems that you either need to
lock the jobs down to only build on specific slaves or use a central maven
repository, making sure your branches (assuming multiple branches building
similar artifacts) have unique versions. Otherwise it seems you are
I should note that I'm using Jenkins v1.605 currently.
On Friday, April 17, 2015 at 4:32:16 PM UTC-6, Jeff Vincent wrote:
>
> A number of months ago, we had to put our Jenkins servers/slaves into a
> secure dev environment with limited external access but I have pointed
> Jen
A number of months ago, we had to put our Jenkins servers/slaves into a
secure dev environment with limited external access but I have pointed
Jenkins updates to a proxy server that has been working.
I hadn't checked for updates in a while, but noticed today that about 28
days ago it stopped
I've read that some issues were seen for which fixes were targeted for
Jenkins 1.450 for issues with upgrading Subversion from 1.34 to 1.37 but my
clean install on Tomcat 6.0.35 (Windows Server 2008 R2 64-bit installer
running as service) doesn't seem to work.
I exploded a manually downloaded s
