See <http://jenkins.buildacloud.org/job/cloudstack-4.3-maven-build/633/changes>

Changes:

[Daan Hoogland] CLOUDSTACK-7752: Fixed deployment planner stuck in infinite 
loop. If we create VM with shared service offering and attach disk with local 
disk offering, and one of storage pool is full(cannot be allocated) and other 
is not full then we are not putting the cluster in avoid list which is causing 
this infinite loop.

------------------------------------------
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-383 
(cloudstack-buildslave-centos6) in workspace 
<http://jenkins.buildacloud.org/job/cloudstack-4.3-maven-build/ws/>
Cloning the remote Git repository
Cloning repository git://git.apache.org/cloudstack.git
 > /usr/bin/git init 
 > <http://jenkins.buildacloud.org/job/cloudstack-4.3-maven-build/ws/> # 
 > timeout=400
Fetching upstream changes from git://git.apache.org/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress git://git.apache.org/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
 > /usr/bin/git config remote.origin.url git://git.apache.org/cloudstack.git # 
 > timeout=400
 > /usr/bin/git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* 
 > # timeout=400
 > /usr/bin/git config remote.origin.url git://git.apache.org/cloudstack.git # 
 > timeout=400
Fetching upstream changes from git://git.apache.org/cloudstack.git
 > /usr/bin/git fetch --tags --progress git://git.apache.org/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
 > /usr/bin/git rev-parse origin/4.3^{commit} # timeout=400
Checking out Revision 14e048dadabba67d09f85d12019fcd39b8b47db1 (origin/4.3)
 > /usr/bin/git config core.sparsecheckout # timeout=400
 > /usr/bin/git checkout -f 14e048dadabba67d09f85d12019fcd39b8b47db1
 > /usr/bin/git rev-list e6d00bcc6670d77144e6d423091808877eaa610f # timeout=400
FATAL: Couldn’t find any executable in /opt/apache-maven-3.0.5
Build step 'Invoke top-level Maven targets' marked build as failure

Reply via email to