Re: How to fix Jenkins git workspace issues

2016-05-19 Thread Will Stevens 
Thanks guys.  I think this will make a big difference.  

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Thu, May 19, 2016 at 5:01 AM, Daan Hoogland 
wrote:

> On Thu, May 19, 2016 at 7:22 AM, Rajani Karuturi 
> wrote:
>
> > untracked
>
>
> ​good call Rajani, it was only doing an ordinary clean in the rat check
> step.​
>
>
>
> --
> Daan
>

Re: How to fix Jenkins git workspace issues

2016-05-19 Thread Daan Hoogland 
On Thu, May 19, 2016 at 7:22 AM, Rajani Karuturi  wrote:

> untracked


​good call Rajani, it was only doing an ordinary clean in the rat check
step.​



-- 
Daan

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Rajani Karuturi 
Can we add git clean -fdx before the the checkout?
That would clean all the untracked files from the git workspace.


On Wed, May 18, 2016 at 10:32 PM Will Stevens  wrote:

> I have seen quite a few situations where tests are failing and they are
> referencing files that are not even included in that PR.
>
> I have also seen situations like this, so the git workspace (index) has
> fragments of previous CI runs and is no longer in a mergeable state.
>
> > git checkout -b master origin/master
> FATAL: Could not checkout master with start point
> origin/masterhudson.plugins.git.GitException
> <
> http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException
> >:
> Could not checkout master with start point origin/master
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1962)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute=method
> >
> at
> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch=method
> >
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch=method
> >
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:608)
> at
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)
> at
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)
> at hudson.remoting.UserRequest.perform(UserRequest.java:120)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:326)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at ..remote call to H10(Native Method)
> at
> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
> at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
> at hudson.remoting.Channel.call(Channel.java:781)
> at
> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)
> at com.sun.proxy.$Proxy131.checkoutBranch(Unknown Source)
> at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:327)
> at
> com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
> at
> hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:951)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1054)
> at hudson.scm.SCM.checkout(SCM.java:485)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
> at
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
> at hudson.model.Run.execute(Run.java:1738)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at
> hudson.model.ResourceController.execute(ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:410)
> Caused by: hudson.plugins.git.GitException: Command "git checkout -b
> master origin/master" returned status code 1:
> stdout:
> plugins/hypervisors/simulator/src/com/cloud/api/commands/SimulatorAddSecondaryAgent.java:
> needs merge
>
> plugins/hypervisors/simulator/src/org/apache/cloudstack/storage/resource/SimulatorSecondaryStorageResource.java:
> needs merge
> plugins/hypervisors/ucs/src/com/cloud/ucs/structure/UcsCookie.java: needs
> merge
> vmware-base/src/com/cloud/hypervisor/vmware/mo/FeatureKeyConstants.java:
> needs merge
>
> stderr: error: you need to resolve your current index first
>
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1693)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:62)
>

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Rafael Weingärtner 
Do you have the plugin [1] installed on Jenkins?
I could not find any entry in your XML relate to any configuration that
would clean up the workspace folder.

[1] https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin

On Wed, May 18, 2016 at 4:02 PM, Daan Hoogland 
wrote:

> Here it is I haven't checked it yet
>
>
>   
> h1cloudstack Build/h1ul
>  liChecks out Pull requests to Apache CloudStack from
> codegithub/code/li  liDoes a
> license check against it/li  liBuilds the target
> branch with Maven and runs unit tests/li  liruns
> analysis tools on the
> code/li/ul
> false  
>class="hudson.tasks.LogRotator">30
> 30
> -1
> -1  
> 
>  plugin="git-validated-merge@3.20">  
> class="com.cloudbees.jenkins.plugins.git.vmerge.pbph.PushFailureIsFailure"/>
>
>  plugin="github@1.15.0">
> http://github.com/apache/cloudstack/
> 
> 
>  plugin="maven-repo-cleaner@1.2">
> false
> 
> 
> false
> false
> 
>  plugin="throttle-concurrents@1.8.4">
> 1
> 0
> true
> project
> 
>plugin="git@2.4.1">2
>   
> https://github.com/apache/cloudstack
> 
>   **
>  
>
> false
>
> 
>  class="com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl"
> plugin="git-validated-merge@3.20"/>
> 
> ubuntu
> false  false
> false
>  false
>  latest1.8  
>  plugin="github-pull-request-build@1.7">  
> 
>   true  
>   if [ -f target/reat.txt ]then  rm
> target/rat.txtfi
>   clean
> --projects=org.apache.cloudstack:cloudstack
> org.apache.rat:apache-rat-plugin:0.10:check
> maven-3.3.3
> false   class="jenkins.mvn.DefaultSettingsProvider"/>   class="jenkins.mvn.DefaultGlobalSettingsProvider"/>
> 
> -Penablefindbugs install cobertura:cobertura
> maven-3.3.3
> false   class="jenkins.mvn.DefaultSettingsProvider"/>   class="jenkins.mvn.DefaultGlobalSettingsProvider"/>
> 
>  plugin="checkstyle@3.43">  
>   low
> [CHECKSTYLE] 
> 
> false
> false
> false
> false   plugin="analysis-core@1.74">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
>   
> false
> true
> false
> 
> 
> 
>
> low  [FINDBUGS]
>   
> false
> false
> false
> false   plugin="analysis-core@1.74">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
>   
> false
> true
> false
>   false
> 
> 
> 
> 
>   
> low  [PMD]
>   
> false
> false
> false
> false   plugin="analysis-core@1.74">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
>   
> false
> true
> false
> 
> 
>   
> low  [DRY]
>   
> false
> false
> false
> false   plugin="analysis-core@1.74">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
>   
> false
> true
> false
>   50
> 25
> 
> target/rat.txt
> false
> false
> false
> true
> true
> 
> 
>
>  
> **/target/site/cobertura/coverage.xml
>  false
> false
> false
> false
> false
> false
> 0
> true  
>  enum-type="hudson.plugins.cobertura.targets.CoverageMetric">
> 
>
> METHOD
>800
>
>  
> LINE
>800
>
>  
> CONDITIONAL
>700  
>class="enum-map"
> enum-type="hudson.plugins.cobertura.targets.CoverageMetric">
> 
>
> METHOD
>0
>
> LINE
>0
>
> CONDITIONAL
>0  
>class="enum-map"
> enum-type="hudson.plugins.cobertura.targets.CoverageMetric">
> 
>
> METHOD
>0
>
> LINE
>0
>
> CONDITIONAL
>0  
>   ASCII
> 
> 
> clover
> clover.xml
> 70
> 80
> 80  
>   
>   
>  plugin="build-timeout@1.15.1">   class="hudson.plugins.build_timeout.impl.ElasticTimeOutStrategy">
>   400
> 3
> 180
>   
> 
> 
> false  false
> 
> 
> 
>
>
>
> On Wed, May 18, 2016 at 8:56 PM, Daan Hoogland 
> wrote:
>
> > Rafael, I think I can access jenkins and download the config.
> > Will, files not included in a PR sticking around "kinda" makes sense as
> > these will not be cleaned by mvn clean on another job
> >
> > On Wed, May 18, 2016 at 8:02 PM, Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> >> Do any of the PMCs have access to those VMs? Or at least admin access to
> >> Jenkins; with admin access we could check the Jenkins Jobs build
> configs.
> >>
> >> On Wed, May 18, 2016 at 2:02 PM, Will Stevens 
> >> wrote:
> >>
> >> > I have seen quite a few situations where tests are failing and they
> are
> >> > referencing files that are not even included in that PR.
> >> >
> >> > I have also seen situations like this, so the git workspace (index)
> has
> >> > fragments of previous CI runs and is no longer in a mergeable state.
> >> >
> >> > > git checkout -b master origin/master
> >> > FATAL: Could not checkout master with start

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Daan Hoogland 
Here it is I haven't checked it yet


  
h1cloudstack Build/h1ul
 liChecks out Pull requests to Apache CloudStack from
codegithub/code/li  liDoes a
license check against it/li  liBuilds the target
branch with Maven and runs unit tests/li  liruns
analysis tools on the
code/li/ul
false  
  30
30
-1
-1  

  
   

http://github.com/apache/cloudstack/



false


false
false


1
0
true
project

  2
  
https://github.com/apache/cloudstack

  **
 
false
   



ubuntu
false  false
false
 false
 latest1.8  
  

  true  
  if [ -f target/reat.txt ]then  rm
target/rat.txtfi
  clean
--projects=org.apache.cloudstack:cloudstack
org.apache.rat:apache-rat-plugin:0.10:check
maven-3.3.3
false

-Penablefindbugs install cobertura:cobertura
maven-3.3.3
false

  
  low
[CHECKSTYLE] 

false
false
false
false  












   

  
false
true
false



   
low  [FINDBUGS]
  
false
false
false
false  












   

  
false
true
false
  false




  
low  [PMD]
  
false
false
false
false  












   

  
false
true
false


  
low  [DRY]
  
false
false
false
false  












   

  
false
true
false
  50
25

target/rat.txt
false
false
false
true
true


 
**/target/site/cobertura/coverage.xml
 false
false
false
false
false
false
0
true  


METHOD
   800
 
LINE
   800
 
CONDITIONAL
   700  
  

METHOD
   0
LINE
   0
CONDITIONAL
   0  
  

METHOD
   0
LINE
   0
CONDITIONAL
   0  
  ASCII


clover
clover.xml
70
80
80  
  
  
  
  400
3
180
  


false  false






On Wed, May 18, 2016 at 8:56 PM, Daan Hoogland 
wrote:

> Rafael, I think I can access jenkins and download the config.
> Will, files not included in a PR sticking around "kinda" makes sense as
> these will not be cleaned by mvn clean on another job
>
> On Wed, May 18, 2016 at 8:02 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
>> Do any of the PMCs have access to those VMs? Or at least admin access to
>> Jenkins; with admin access we could check the Jenkins Jobs build configs.
>>
>> On Wed, May 18, 2016 at 2:02 PM, Will Stevens 
>> wrote:
>>
>> > I have seen quite a few situations where tests are failing and they are
>> > referencing files that are not even included in that PR.
>> >
>> > I have also seen situations like this, so the git workspace (index) has
>> > fragments of previous CI runs and is no longer in a mergeable state.
>> >
>> > > git checkout -b master origin/master
>> > FATAL: Could not checkout master with start point
>> > origin/masterhudson.plugins.git.GitException
>> > <
>> >
>> http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException
>> > >:
>> > Could not checkout master with start point origin/master
>> > at
>> >
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1962)
>> > <
>> >
>> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute=method
>> > >
>> > at
>> >
>> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
>> > <
>> >
>> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch=method
>> > >
>> > at
>> >
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
>> > <
>> >
>> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch=method
>> > >
>> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> > at
>> >
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> > at
>> >
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> > at java.lang.reflect.Method.invoke(Method.java:606)
>> > at
>> >
>> hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:608)
>> > at
>> >
>> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)
>> > at
>> >
>> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)
>> > at hudson.remoting.UserRequest.perform(UserRequest.java:120)
>> > at hudson.remoting.UserRequest.perform(UserRequest.java:48)
>> > at hudson.remoting.Request$2.run(Request.java:326)
>> > at
>> >
>>

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Rafael Weingärtner 
If the files that are causing some problems are out of the “workspace”
folder, then it makes sense; otherwise it does not.

I am a little out of the loop lately (sorry for that), what files are
causing the trouble?

On Wed, May 18, 2016 at 3:56 PM, Daan Hoogland 
wrote:

> Rafael, I think I can access jenkins and download the config.
> Will, files not included in a PR sticking around "kinda" makes sense as
> these will not be cleaned by mvn clean on another job
>
> On Wed, May 18, 2016 at 8:02 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Do any of the PMCs have access to those VMs? Or at least admin access to
> > Jenkins; with admin access we could check the Jenkins Jobs build configs.
> >
> > On Wed, May 18, 2016 at 2:02 PM, Will Stevens 
> > wrote:
> >
> > > I have seen quite a few situations where tests are failing and they are
> > > referencing files that are not even included in that PR.
> > >
> > > I have also seen situations like this, so the git workspace (index) has
> > > fragments of previous CI runs and is no longer in a mergeable state.
> > >
> > > > git checkout -b master origin/master
> > > FATAL: Could not checkout master with start point
> > > origin/masterhudson.plugins.git.GitException
> > > <
> > >
> >
> http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException
> > > >:
> > > Could not checkout master with start point origin/master
> > > at
> > >
> >
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1962)
> > > <
> > >
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute=method
> > > >
> > > at
> > >
> >
> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
> > > <
> > >
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch=method
> > > >
> > > at
> > >
> >
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
> > > <
> > >
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch=method
> > > >
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at
> > >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> > > at
> > >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > > at java.lang.reflect.Method.invoke(Method.java:606)
> > > at
> > >
> >
> hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:608)
> > > at
> > >
> >
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)
> > > at
> > >
> >
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)
> > > at hudson.remoting.UserRequest.perform(UserRequest.java:120)
> > > at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> > > at hudson.remoting.Request$2.run(Request.java:326)
> > > at
> > >
> >
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
> > > at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> > > at
> > >
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > > at
> > >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > > at java.lang.Thread.run(Thread.java:745)
> > > at ..remote call to H10(Native Method)
> > > at
> > > hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
> > > at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
> > > at hudson.remoting.Channel.call(Channel.java:781)
> > > at
> > >
> >
> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)
> > > at com.sun.proxy.$Proxy131.checkoutBranch(Unknown Source)
> > > at
> > >
> >
> org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:327)
> > > at
> > >
> >
> com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
> > > at
> > > hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:951)
> > > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1054)
> > > at hudson.scm.SCM.checkout(SCM.java:485)
> > > at
> > hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
> > > at
> > >
> >
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
> > > at
> > > jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> > > at
> > >
> >
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
> > >

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Daan Hoogland 
Rafael, I think I can access jenkins and download the config.
Will, files not included in a PR sticking around "kinda" makes sense as
these will not be cleaned by mvn clean on another job

On Wed, May 18, 2016 at 8:02 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Do any of the PMCs have access to those VMs? Or at least admin access to
> Jenkins; with admin access we could check the Jenkins Jobs build configs.
>
> On Wed, May 18, 2016 at 2:02 PM, Will Stevens 
> wrote:
>
> > I have seen quite a few situations where tests are failing and they are
> > referencing files that are not even included in that PR.
> >
> > I have also seen situations like this, so the git workspace (index) has
> > fragments of previous CI runs and is no longer in a mergeable state.
> >
> > > git checkout -b master origin/master
> > FATAL: Could not checkout master with start point
> > origin/masterhudson.plugins.git.GitException
> > <
> >
> http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException
> > >:
> > Could not checkout master with start point origin/master
> > at
> >
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1962)
> > <
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute=method
> > >
> > at
> >
> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
> > <
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch=method
> > >
> > at
> >
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
> > <
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch=method
> > >
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:606)
> > at
> >
> hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:608)
> > at
> >
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)
> > at
> >
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)
> > at hudson.remoting.UserRequest.perform(UserRequest.java:120)
> > at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> > at hudson.remoting.Request$2.run(Request.java:326)
> > at
> >
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > at java.lang.Thread.run(Thread.java:745)
> > at ..remote call to H10(Native Method)
> > at
> > hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
> > at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
> > at hudson.remoting.Channel.call(Channel.java:781)
> > at
> >
> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)
> > at com.sun.proxy.$Proxy131.checkoutBranch(Unknown Source)
> > at
> >
> org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:327)
> > at
> >
> com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
> > at
> > hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:951)
> > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1054)
> > at hudson.scm.SCM.checkout(SCM.java:485)
> > at
> hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
> > at
> >
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
> > at
> > jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> > at
> >
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
> > at hudson.model.Run.execute(Run.java:1738)
> > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> > at
> > hudson.model.ResourceController.execute(ResourceController.java:98)
> > at hudson.model.Executor.run(Executor.java:410)
> > Caused by: hudson.plugins.git.GitException: Command "git checkout -b
> > master origin/master" returned status code 1:
> > stdout:
> >
> plugins/hypervisors/simulator/src/com/cloud/api/commands/SimulatorAddSecondaryAgent.java:
> > needs merge
> >
> >
>

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Rafael Weingärtner 
Do any of the PMCs have access to those VMs? Or at least admin access to
Jenkins; with admin access we could check the Jenkins Jobs build configs.

On Wed, May 18, 2016 at 2:02 PM, Will Stevens  wrote:

> I have seen quite a few situations where tests are failing and they are
> referencing files that are not even included in that PR.
>
> I have also seen situations like this, so the git workspace (index) has
> fragments of previous CI runs and is no longer in a mergeable state.
>
> > git checkout -b master origin/master
> FATAL: Could not checkout master with start point
> origin/masterhudson.plugins.git.GitException
> <
> http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException
> >:
> Could not checkout master with start point origin/master
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1962)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute=method
> >
> at
> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch=method
> >
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch=method
> >
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:608)
> at
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)
> at
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)
> at hudson.remoting.UserRequest.perform(UserRequest.java:120)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:326)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at ..remote call to H10(Native Method)
> at
> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
> at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
> at hudson.remoting.Channel.call(Channel.java:781)
> at
> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)
> at com.sun.proxy.$Proxy131.checkoutBranch(Unknown Source)
> at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:327)
> at
> com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
> at
> hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:951)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1054)
> at hudson.scm.SCM.checkout(SCM.java:485)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
> at
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
> at hudson.model.Run.execute(Run.java:1738)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at
> hudson.model.ResourceController.execute(ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:410)
> Caused by: hudson.plugins.git.GitException: Command "git checkout -b
> master origin/master" returned status code 1:
> stdout:
> plugins/hypervisors/simulator/src/com/cloud/api/commands/SimulatorAddSecondaryAgent.java:
> needs merge
>
> plugins/hypervisors/simulator/src/org/apache/cloudstack/storage/resource/SimulatorSecondaryStorageResource.java:
> needs merge
> plugins/hypervisors/ucs/src/com/cloud/ucs/structure/UcsCookie.java: needs
> merge
> vmware-base/src/com/cloud/hypervisor/vmware/mo/FeatureKeyConstants.java:
> needs merge
>
> stderr: error: you need to resolve your current index first
>
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1693)
> at
>

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Will Stevens 
I have seen quite a few situations where tests are failing and they are
referencing files that are not even included in that PR.

I have also seen situations like this, so the git workspace (index) has
fragments of previous CI runs and is no longer in a mergeable state.

> git checkout -b master origin/master
FATAL: Could not checkout master with start point
origin/masterhudson.plugins.git.GitException
:
Could not checkout master with start point origin/master
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1962)

at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:608)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)
at hudson.remoting.UserRequest.perform(UserRequest.java:120)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H10(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
at hudson.remoting.Channel.call(Channel.java:781)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)
at com.sun.proxy.$Proxy131.checkoutBranch(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:327)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:951)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1054)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git checkout -b
master origin/master" returned status code 1:
stdout: 
plugins/hypervisors/simulator/src/com/cloud/api/commands/SimulatorAddSecondaryAgent.java:
needs merge
plugins/hypervisors/simulator/src/org/apache/cloudstack/storage/resource/SimulatorSecondaryStorageResource.java:
needs merge
plugins/hypervisors/ucs/src/com/cloud/ucs/structure/UcsCookie.java: needs merge
vmware-base/src/com/cloud/hypervisor/vmware/mo/FeatureKeyConstants.java:
needs merge

stderr: error: you need to resolve your current index first

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1693)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:62)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1956)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Rafael Weingärtner 
Me neither.
Do we need to open a ticket to infra to check that? Or do we have someone
among the PMCs that have access to those VMs?

On Wed, May 18, 2016 at 12:51 PM, Daan Hoogland 
wrote:

> I hav no access to the nodes so I wouldn't know about that.
>
> On Wed, May 18, 2016 at 5:36 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Parallel builds will use different workspace, so that should not be a
> > problem.
> >
> > Maybe the “@” symbol it uses to differentiate the workspace folders?
> > I mean, when it runs parallel builds, it will use a “@” and then it will
> > append a number to identify the builds.
> >
> > For instance, if we have workspace called “Test”, when running parallel
> > builds we would get something like: “Test@2” , “Test@3”  and so forth.
> > That
> > “@” symbol in a folder may break some scripts.
> >
> > Also, if the scripts that are executed were not prepared to run in
> > parallel, they might use the very same temp folder and files, which can
> > cause problems.
> >
> > On Wed, May 18, 2016 at 12:26 PM, Daan Hoogland  >
> > wrote:
> >
> > > It also does a mvn clean so that should not be an issue. I am thinking
> > more
> > > along the line of parallel builds on the same node.
> > >
> > > On Wed, May 18, 2016 at 5:04 PM, Rafael Weingärtner <
> > > rafaelweingart...@gmail.com> wrote:
> > >
> > > > Is Jenkins configure to clean the workspace before it starts a new
> > build?
> > > >
> > > > It should have an option such as "Delete workspace before build
> > starts".
> > > >
> > > > On Wed, May 18, 2016 at 12:00 PM, Will Stevens <
> > williamstev...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > If Jenkins has problems with fragments being left over in it's
> > > workspace
> > > > > which is causing following runs against other PRs to fail, how do
> we
> > > fix
> > > > > that?
> > > > >
> > > > > Thanks...
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Rafael Weingärtner
> > > >
> > >
> > >
> > >
> > > --
> > > Daan
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Daan
>



-- 
Rafael Weingärtner

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Daan Hoogland 
I hav no access to the nodes so I wouldn't know about that.

On Wed, May 18, 2016 at 5:36 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Parallel builds will use different workspace, so that should not be a
> problem.
>
> Maybe the “@” symbol it uses to differentiate the workspace folders?
> I mean, when it runs parallel builds, it will use a “@” and then it will
> append a number to identify the builds.
>
> For instance, if we have workspace called “Test”, when running parallel
> builds we would get something like: “Test@2” , “Test@3”  and so forth.
> That
> “@” symbol in a folder may break some scripts.
>
> Also, if the scripts that are executed were not prepared to run in
> parallel, they might use the very same temp folder and files, which can
> cause problems.
>
> On Wed, May 18, 2016 at 12:26 PM, Daan Hoogland 
> wrote:
>
> > It also does a mvn clean so that should not be an issue. I am thinking
> more
> > along the line of parallel builds on the same node.
> >
> > On Wed, May 18, 2016 at 5:04 PM, Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > Is Jenkins configure to clean the workspace before it starts a new
> build?
> > >
> > > It should have an option such as "Delete workspace before build
> starts".
> > >
> > > On Wed, May 18, 2016 at 12:00 PM, Will Stevens <
> williamstev...@gmail.com
> > >
> > > wrote:
> > >
> > > > If Jenkins has problems with fragments being left over in it's
> > workspace
> > > > which is causing following runs against other PRs to fail, how do we
> > fix
> > > > that?
> > > >
> > > > Thanks...
> > > >
> > >
> > >
> > >
> > > --
> > > Rafael Weingärtner
> > >
> >
> >
> >
> > --
> > Daan
> >
>
>
>
> --
> Rafael Weingärtner
>



-- 
Daan

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Daan Hoogland 
It also does a mvn clean so that should not be an issue. I am thinking more
along the line of parallel builds on the same node.

On Wed, May 18, 2016 at 5:04 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Is Jenkins configure to clean the workspace before it starts a new build?
>
> It should have an option such as "Delete workspace before build starts".
>
> On Wed, May 18, 2016 at 12:00 PM, Will Stevens 
> wrote:
>
> > If Jenkins has problems with fragments being left over in it's workspace
> > which is causing following runs against other PRs to fail, how do we fix
> > that?
> >
> > Thanks...
> >
>
>
>
> --
> Rafael Weingärtner
>



-- 
Daan

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Rafael Weingärtner 
Parallel builds will use different workspace, so that should not be a
problem.

Maybe the “@” symbol it uses to differentiate the workspace folders?
I mean, when it runs parallel builds, it will use a “@” and then it will
append a number to identify the builds.

For instance, if we have workspace called “Test”, when running parallel
builds we would get something like: “Test@2” , “Test@3”  and so forth. That
“@” symbol in a folder may break some scripts.

Also, if the scripts that are executed were not prepared to run in
parallel, they might use the very same temp folder and files, which can
cause problems.

On Wed, May 18, 2016 at 12:26 PM, Daan Hoogland 
wrote:

> It also does a mvn clean so that should not be an issue. I am thinking more
> along the line of parallel builds on the same node.
>
> On Wed, May 18, 2016 at 5:04 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Is Jenkins configure to clean the workspace before it starts a new build?
> >
> > It should have an option such as "Delete workspace before build starts".
> >
> > On Wed, May 18, 2016 at 12:00 PM, Will Stevens  >
> > wrote:
> >
> > > If Jenkins has problems with fragments being left over in it's
> workspace
> > > which is causing following runs against other PRs to fail, how do we
> fix
> > > that?
> > >
> > > Thanks...
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Daan
>



-- 
Rafael Weingärtner

Re: How to fix Jenkins git workspace issues

2016-05-18 Thread Rafael Weingärtner 
Is Jenkins configure to clean the workspace before it starts a new build?

It should have an option such as "Delete workspace before build starts".

On Wed, May 18, 2016 at 12:00 PM, Will Stevens 
wrote:

> If Jenkins has problems with fragments being left over in it's workspace
> which is causing following runs against other PRs to fail, how do we fix
> that?
>
> Thanks...
>



-- 
Rafael Weingärtner

How to fix Jenkins git workspace issues

2016-05-18 Thread Will Stevens 
If Jenkins has problems with fragments being left over in it's workspace
which is causing following runs against other PRs to fail, how do we fix
that?

Thanks...