How about building and testing a merged version before the changes hit
master?
Mit freundlichen Grüßen
Björn Stabel
data experts gmbh
Niederlassung Berlin
Allee der Kosmonauten 33g
12681 Berlin
Telefon: +49 (0)30 54708 282
E-Mail: bjoern.sta...@data-experts.de
http://www.data-experts.de
Blind, uneducated guess: did you deploy the .war file twice, maybe under
different names?
On 12/02/16 15:48, Peter Berghold wrote:
multi-jenkins.PNG
--
You received this message because you are subscribed to the Google
Groups "Jenkins Users" group.
To unsubscribe from this group and stop recei
e, Nov 24, 2015 at 4:28 AM Björn Stabel
mailto:bjoern.sta...@data-experts.de>>
wrote:
I'm still having this problem. Is anyone aware of a solution, like a
pre-wipe action plugin?
On 10/22/2015 12:49 PM, Björn Stabel wrote:
> Hello,
>
> I have a job th
Maybe you need a plugin dedicated to the task that takes care of things
like snapshotting and such. For vSphere, there's
https://wiki.jenkins-ci.org/display/JENKINS/vSphere+Cloud+Plugin
On 11/24/2015 09:47 AM, Andreas Tscharner wrote:
On 23.11.2015 16:53, Jason Swager wrote:
Is the build runn
I'm still having this problem. Is anyone aware of a solution, like a
pre-wipe action plugin?
On 10/22/2015 12:49 PM, Björn Stabel wrote:
Hello,
I have a job that constructs a Vagrant environment in the workspace
directory.
To that Vagrant environment belongs a VirtualBox VM, s
The error looks like openshift was compiled for java 8 and you're
running jenkins on a lesser java version.
On 11/09/2015 10:40 AM, Krishy wrote:
Never Mind guys.. I was able to solve it..
I had to uninstall the OpenShift Plugin which was giving this issue.
On Monday, November 9, 2015 at 1:
Hello,
I have a job that constructs a Vagrant environment in the workspace
directory.
To that Vagrant environment belongs a VirtualBox VM, stored elsewhere.
Vagrant keeps track of which Vagrant environment belongs to which
VirtualBox VM through a directory named ".vagrant" in the workspace
di
