You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Will Stevens <wi...@gmail.com> on 2016/05/18 15:00:32 UTC
How to fix Jenkins git workspace issues
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...
Re: How to fix Jenkins git workspace issues
Posted by Will Stevens <ws...@cloudops.com>.
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 <da...@gmail.com>
wrote:
> On Thu, May 19, 2016 at 7:22 AM, Rajani Karuturi <ra...@apache.org>
> 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
Posted by Daan Hoogland <da...@gmail.com>.
On Thu, May 19, 2016 at 7:22 AM, Rajani Karuturi <ra...@apache.org> 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
Posted by Rajani Karuturi <ra...@apache.org>.
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 <ws...@cloudops.com> 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&entity=method
> >
> at
> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch&entity=method
> >
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch&entity=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)
> 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
> 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)
>
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Wed, May 18, 2016 at 12:26 PM, Rafael Weingärtner <
> rafaelweingartner@gmail.com> wrote:
>
> > 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 <daan.hoogland@gmail.com
> >
> > 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 <
> > > rafaelweingartner@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 <
> > daan.hoogland@gmail.com
> > > >
> > > > 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 <
> > > > > rafaelweingartner@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 <
> > > > williamstevens@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
Posted by Rafael Weingärtner <ra...@gmail.com>.
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 <da...@gmail.com>
wrote:
> Here it is I haven't checked it yet
>
>
> <?xml version='1.0' encoding='UTF-8'?><project> <actions/>
> <description><h1>cloudstack Build</h1>
<ul>
> <li>Checks out Pull requests to Apache CloudStack from
> <code>github</code></li>
 <li>Does a
> license check against it</li>
 <li>Builds the target
> branch with Maven and runs unit tests</li>
 <li>runs
> analysis tools on the
> code</li>
</ul>
</description>
> <keepDependencies>false</keepDependencies> <properties>
> <jenkins.model.BuildDiscarderProperty> <strategy
> class="hudson.tasks.LogRotator"> <daysToKeep>30</daysToKeep>
> <numToKeep>30</numToKeep>
> <artifactDaysToKeep>-1</artifactDaysToKeep>
> <artifactNumToKeep>-1</artifactNumToKeep> </strategy>
> </jenkins.model.BuildDiscarderProperty>
> <com.cloudbees.jenkins.plugins.git.vmerge.JobPropertyImpl
> plugin="git-validated-merge@3.20"> <postBuildPushFailureHandler
>
> class="com.cloudbees.jenkins.plugins.git.vmerge.pbph.PushFailureIsFailure"/>
> </com.cloudbees.jenkins.plugins.git.vmerge.JobPropertyImpl>
> <com.coravy.hudson.plugins.github.GithubProjectProperty
> plugin="github@1.15.0">
> <projectUrl>http://github.com/apache/cloudstack/</projectUrl>
> <displayName></displayName>
> </com.coravy.hudson.plugins.github.GithubProjectProperty>
> <org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty
> plugin="maven-repo-cleaner@1.2">
> <notOnThisProject>false</notOnThisProject>
> </org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty>
> <com.sonyericsson.rebuild.RebuildSettings plugin="rebuild@1.25">
> <autoRebuild>false</autoRebuild>
> <rebuildDisabled>false</rebuildDisabled>
> </com.sonyericsson.rebuild.RebuildSettings>
> <hudson.plugins.throttleconcurrents.ThrottleJobProperty
> plugin="throttle-concurrents@1.8.4">
> <maxConcurrentPerNode>1</maxConcurrentPerNode>
> <maxConcurrentTotal>0</maxConcurrentTotal>
> <throttleEnabled>true</throttleEnabled>
> <throttleOption>project</throttleOption>
> </hudson.plugins.throttleconcurrents.ThrottleJobProperty>
> </properties> <scm class="hudson.plugins.git.GitSCM"
> plugin="git@2.4.1"> <configVersion>2</configVersion>
> <userRemoteConfigs> <hudson.plugins.git.UserRemoteConfig>
> <url>https://github.com/apache/cloudstack</url>
> </hudson.plugins.git.UserRemoteConfig> </userRemoteConfigs>
> <branches> <hudson.plugins.git.BranchSpec> <name>**</name>
> </hudson.plugins.git.BranchSpec> </branches>
>
> <doGenerateSubmoduleConfigurations>false</doGenerateSubmoduleConfigurations>
> <submoduleCfg class="list"/> <extensions>
> <hudson.plugins.git.extensions.impl.BuildChooserSetting>
> <buildChooser
> class="com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl"
> plugin="git-validated-merge@3.20"/>
> </hudson.plugins.git.extensions.impl.BuildChooserSetting>
> </extensions> </scm> <assignedNode>ubuntu</assignedNode>
> <canRoam>false</canRoam> <disabled>false</disabled>
> <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
> <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
> <jdk>latest1.8</jdk> <triggers>
> <com.cloudbees.jenkins.plugins.github__pull.PullRequestBuildTrigger
> plugin="github-pull-request-build@1.7"> <spec></spec>
> </com.cloudbees.jenkins.plugins.github__pull.PullRequestBuildTrigger>
> </triggers> <concurrentBuild>true</concurrentBuild> <builders>
> <hudson.tasks.Shell> <command>if [ -f target/reat.txt ]then rm
> target/rat.txtfi</command> </hudson.tasks.Shell>
> <hudson.tasks.Maven> <targets>clean
> --projects='org.apache.cloudstack:cloudstack'
> org.apache.rat:apache-rat-plugin:0.10:check</targets>
> <mavenName>maven-3.3.3</mavenName>
> <usePrivateRepository>false</usePrivateRepository> <settings
> class="jenkins.mvn.DefaultSettingsProvider"/> <globalSettings
> class="jenkins.mvn.DefaultGlobalSettingsProvider"/>
> </hudson.tasks.Maven> <hudson.tasks.Maven>
> <targets>-Penablefindbugs install cobertura:cobertura</targets>
> <mavenName>maven-3.3.3</mavenName>
> <usePrivateRepository>false</usePrivateRepository> <settings
> class="jenkins.mvn.DefaultSettingsProvider"/> <globalSettings
> class="jenkins.mvn.DefaultGlobalSettingsProvider"/>
> </hudson.tasks.Maven> </builders> <publishers>
> <hudson.plugins.checkstyle.CheckStylePublisher
> plugin="checkstyle@3.43"> <healthy></healthy>
> <unHealthy></unHealthy> <thresholdLimit>low</thresholdLimit>
> <pluginName>[CHECKSTYLE] </pluginName>
> <defaultEncoding></defaultEncoding>
> <canRunOnFailed>false</canRunOnFailed>
> <usePreviousBuildAsReference>false</usePreviousBuildAsReference>
> <useStableBuildAsReference>false</useStableBuildAsReference>
> <useDeltaValues>false</useDeltaValues> <thresholds
> plugin="analysis-core@1.74">
> <unstableTotalAll></unstableTotalAll>
> <unstableTotalHigh></unstableTotalHigh>
> <unstableTotalNormal></unstableTotalNormal>
> <unstableTotalLow></unstableTotalLow>
> <unstableNewAll></unstableNewAll>
> <unstableNewHigh></unstableNewHigh>
> <unstableNewNormal></unstableNewNormal>
> <unstableNewLow></unstableNewLow>
> <failedTotalAll></failedTotalAll>
> <failedTotalHigh></failedTotalHigh>
> <failedTotalNormal></failedTotalNormal>
> <failedTotalLow></failedTotalLow> <failedNewAll></failedNewAll>
> <failedNewHigh></failedNewHigh>
> <failedNewNormal></failedNewNormal>
> <failedNewLow></failedNewLow> </thresholds>
> <shouldDetectModules>false</shouldDetectModules>
> <dontComputeNew>true</dontComputeNew>
> <doNotResolveRelativePaths>false</doNotResolveRelativePaths>
> <pattern></pattern>
> </hudson.plugins.checkstyle.CheckStylePublisher>
> <hudson.plugins.findbugs.FindBugsPublisher plugin="findbugs@4.62">
> <healthy></healthy> <unHealthy></unHealthy>
> <thresholdLimit>low</thresholdLimit> <pluginName>[FINDBUGS]
> </pluginName> <defaultEncoding></defaultEncoding>
> <canRunOnFailed>false</canRunOnFailed>
> <usePreviousBuildAsReference>false</usePreviousBuildAsReference>
> <useStableBuildAsReference>false</useStableBuildAsReference>
> <useDeltaValues>false</useDeltaValues> <thresholds
> plugin="analysis-core@1.74">
> <unstableTotalAll></unstableTotalAll>
> <unstableTotalHigh></unstableTotalHigh>
> <unstableTotalNormal></unstableTotalNormal>
> <unstableTotalLow></unstableTotalLow>
> <unstableNewAll></unstableNewAll>
> <unstableNewHigh></unstableNewHigh>
> <unstableNewNormal></unstableNewNormal>
> <unstableNewLow></unstableNewLow>
> <failedTotalAll></failedTotalAll>
> <failedTotalHigh></failedTotalHigh>
> <failedTotalNormal></failedTotalNormal>
> <failedTotalLow></failedTotalLow> <failedNewAll></failedNewAll>
> <failedNewHigh></failedNewHigh>
> <failedNewNormal></failedNewNormal>
> <failedNewLow></failedNewLow> </thresholds>
> <shouldDetectModules>false</shouldDetectModules>
> <dontComputeNew>true</dontComputeNew>
> <doNotResolveRelativePaths>false</doNotResolveRelativePaths>
> <pattern></pattern> <isRankActivated>false</isRankActivated>
> <excludePattern></excludePattern>
> <includePattern></includePattern>
> </hudson.plugins.findbugs.FindBugsPublisher>
> <hudson.plugins.pmd.PmdPublisher plugin="pmd@3.42">
> <healthy></healthy> <unHealthy></unHealthy>
> <thresholdLimit>low</thresholdLimit> <pluginName>[PMD]
> </pluginName> <defaultEncoding></defaultEncoding>
> <canRunOnFailed>false</canRunOnFailed>
> <usePreviousBuildAsReference>false</usePreviousBuildAsReference>
> <useStableBuildAsReference>false</useStableBuildAsReference>
> <useDeltaValues>false</useDeltaValues> <thresholds
> plugin="analysis-core@1.74">
> <unstableTotalAll></unstableTotalAll>
> <unstableTotalHigh></unstableTotalHigh>
> <unstableTotalNormal></unstableTotalNormal>
> <unstableTotalLow></unstableTotalLow>
> <unstableNewAll></unstableNewAll>
> <unstableNewHigh></unstableNewHigh>
> <unstableNewNormal></unstableNewNormal>
> <unstableNewLow></unstableNewLow>
> <failedTotalAll></failedTotalAll>
> <failedTotalHigh></failedTotalHigh>
> <failedTotalNormal></failedTotalNormal>
> <failedTotalLow></failedTotalLow> <failedNewAll></failedNewAll>
> <failedNewHigh></failedNewHigh>
> <failedNewNormal></failedNewNormal>
> <failedNewLow></failedNewLow> </thresholds>
> <shouldDetectModules>false</shouldDetectModules>
> <dontComputeNew>true</dontComputeNew>
> <doNotResolveRelativePaths>false</doNotResolveRelativePaths>
> <pattern></pattern> </hudson.plugins.pmd.PmdPublisher>
> <hudson.plugins.dry.DryPublisher plugin="dry@2.42">
> <healthy></healthy> <unHealthy></unHealthy>
> <thresholdLimit>low</thresholdLimit> <pluginName>[DRY]
> </pluginName> <defaultEncoding></defaultEncoding>
> <canRunOnFailed>false</canRunOnFailed>
> <usePreviousBuildAsReference>false</usePreviousBuildAsReference>
> <useStableBuildAsReference>false</useStableBuildAsReference>
> <useDeltaValues>false</useDeltaValues> <thresholds
> plugin="analysis-core@1.74">
> <unstableTotalAll></unstableTotalAll>
> <unstableTotalHigh></unstableTotalHigh>
> <unstableTotalNormal></unstableTotalNormal>
> <unstableTotalLow></unstableTotalLow>
> <unstableNewAll></unstableNewAll>
> <unstableNewHigh></unstableNewHigh>
> <unstableNewNormal></unstableNewNormal>
> <unstableNewLow></unstableNewLow>
> <failedTotalAll></failedTotalAll>
> <failedTotalHigh></failedTotalHigh>
> <failedTotalNormal></failedTotalNormal>
> <failedTotalLow></failedTotalLow> <failedNewAll></failedNewAll>
> <failedNewHigh></failedNewHigh>
> <failedNewNormal></failedNewNormal>
> <failedNewLow></failedNewLow> </thresholds>
> <shouldDetectModules>false</shouldDetectModules>
> <dontComputeNew>true</dontComputeNew>
> <doNotResolveRelativePaths>false</doNotResolveRelativePaths>
> <pattern></pattern> <highThreshold>50</highThreshold>
> <normalThreshold>25</normalThreshold>
> </hudson.plugins.dry.DryPublisher> <hudson.tasks.ArtifactArchiver>
> <artifacts>target/rat.txt</artifacts>
> <allowEmptyArchive>false</allowEmptyArchive>
> <onlyIfSuccessful>false</onlyIfSuccessful>
> <fingerprint>false</fingerprint>
> <defaultExcludes>true</defaultExcludes>
> <caseSensitive>true</caseSensitive>
> </hudson.tasks.ArtifactArchiver>
> <hudson.plugins.cobertura.CoberturaPublisher plugin="cobertura@1.9.7">
>
> <coberturaReportFile>**/target/site/cobertura/coverage.xml</coberturaReportFile>
> <onlyStable>false</onlyStable>
> <failUnhealthy>false</failUnhealthy>
> <failUnstable>false</failUnstable>
> <autoUpdateHealth>false</autoUpdateHealth>
> <autoUpdateStability>false</autoUpdateStability>
> <zoomCoverageChart>false</zoomCoverageChart>
> <maxNumberOfBuilds>0</maxNumberOfBuilds>
> <failNoReports>true</failNoReports> <healthyTarget>
> <targets class="enum-map"
> enum-type="hudson.plugins.cobertura.targets.CoverageMetric">
> <entry>
>
> <hudson.plugins.cobertura.targets.CoverageMetric>METHOD</hudson.plugins.cobertura.targets.CoverageMetric>
> <int>8000000</int> </entry> <entry>
>
> <hudson.plugins.cobertura.targets.CoverageMetric>LINE</hudson.plugins.cobertura.targets.CoverageMetric>
> <int>8000000</int> </entry> <entry>
>
> <hudson.plugins.cobertura.targets.CoverageMetric>CONDITIONAL</hudson.plugins.cobertura.targets.CoverageMetric>
> <int>7000000</int> </entry> </targets>
> </healthyTarget> <unhealthyTarget> <targets
> class="enum-map"
> enum-type="hudson.plugins.cobertura.targets.CoverageMetric">
> <entry>
>
> <hudson.plugins.cobertura.targets.CoverageMetric>METHOD</hudson.plugins.cobertura.targets.CoverageMetric>
> <int>0</int> </entry> <entry>
>
> <hudson.plugins.cobertura.targets.CoverageMetric>LINE</hudson.plugins.cobertura.targets.CoverageMetric>
> <int>0</int> </entry> <entry>
>
> <hudson.plugins.cobertura.targets.CoverageMetric>CONDITIONAL</hudson.plugins.cobertura.targets.CoverageMetric>
> <int>0</int> </entry> </targets>
> </unhealthyTarget> <failingTarget> <targets
> class="enum-map"
> enum-type="hudson.plugins.cobertura.targets.CoverageMetric">
> <entry>
>
> <hudson.plugins.cobertura.targets.CoverageMetric>METHOD</hudson.plugins.cobertura.targets.CoverageMetric>
> <int>0</int> </entry> <entry>
>
> <hudson.plugins.cobertura.targets.CoverageMetric>LINE</hudson.plugins.cobertura.targets.CoverageMetric>
> <int>0</int> </entry> <entry>
>
> <hudson.plugins.cobertura.targets.CoverageMetric>CONDITIONAL</hudson.plugins.cobertura.targets.CoverageMetric>
> <int>0</int> </entry> </targets>
> </failingTarget> <sourceEncoding>ASCII</sourceEncoding>
> </hudson.plugins.cobertura.CoberturaPublisher>
> <hudson.plugins.clover.CloverPublisher plugin="clover@4.4.0">
> <cloverReportDir>clover</cloverReportDir>
> <cloverReportFileName>clover.xml</cloverReportFileName>
> <healthyTarget> <methodCoverage>70</methodCoverage>
> <conditionalCoverage>80</conditionalCoverage>
> <statementCoverage>80</statementCoverage> </healthyTarget>
> <unhealthyTarget/> <failingTarget/>
> </hudson.plugins.clover.CloverPublisher> </publishers>
> <buildWrappers> <hudson.plugins.build__timeout.BuildTimeoutWrapper
> plugin="build-timeout@1.15.1"> <strategy
> class="hudson.plugins.build_timeout.impl.ElasticTimeOutStrategy">
> <timeoutPercentage>400</timeoutPercentage>
> <numberOfBuilds>3</numberOfBuilds>
> <timeoutMinutesElasticDefault>180</timeoutMinutesElasticDefault>
> </strategy> <operationList/>
> </hudson.plugins.build__timeout.BuildTimeoutWrapper>
> <hudson.plugins.clover.CloverBuildWrapper plugin="clover@4.4.0">
> <historical>false</historical> <json>false</json>
> <licenseCert></licenseCert>
> </hudson.plugins.clover.CloverBuildWrapper>
> </buildWrappers></project>
>
>
>
> On Wed, May 18, 2016 at 8:56 PM, Daan Hoogland <da...@gmail.com>
> 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 <
> > rafaelweingartner@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 <ws...@cloudops.com>
> >> 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&entity=method
> >> > >
> >> > at
> >> >
> >>
> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
> >> > <
> >> >
> >>
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch&entity=method
> >> > >
> >> > at
> >> >
> >>
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
> >> > <
> >> >
> >>
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch&entity=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)
> >> > 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
> >> >
> >>
> 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)
> >> >
> >> >
> >> > *Will STEVENS*
> >> > Lead Developer
> >> >
> >> > *CloudOps* *| *Cloud Solutions Experts
> >> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >> > w cloudops.com *|* tw @CloudOps_
> >> >
> >> > On Wed, May 18, 2016 at 12:26 PM, Rafael Weingärtner <
> >> > rafaelweingartner@gmail.com> wrote:
> >> >
> >> > > 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 <
> >> daan.hoogland@gmail.com
> >> > >
> >> > > 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 <
> >> > > > rafaelweingartner@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 <
> >> > > daan.hoogland@gmail.com
> >> > > > >
> >> > > > > 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 <
> >> > > > > > rafaelweingartner@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 <
> >> > > > > williamstevens@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
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Rafael Weingärtner
> >>
> >
> >
> >
> > --
> > Daan
> >
>
>
>
> --
> Daan
>
--
Rafael Weingärtner
Re: How to fix Jenkins git workspace issues
Posted by Daan Hoogland <da...@gmail.com>.
Here it is I haven't checked it yet
<?xml version='1.0' encoding='UTF-8'?><project> <actions/>
<description><h1>cloudstack Build</h1>
<ul>
<li>Checks out Pull requests to Apache CloudStack from
<code>github</code></li>
 <li>Does a
license check against it</li>
 <li>Builds the target
branch with Maven and runs unit tests</li>
 <li>runs
analysis tools on the
code</li>
</ul>
</description>
<keepDependencies>false</keepDependencies> <properties>
<jenkins.model.BuildDiscarderProperty> <strategy
class="hudson.tasks.LogRotator"> <daysToKeep>30</daysToKeep>
<numToKeep>30</numToKeep>
<artifactDaysToKeep>-1</artifactDaysToKeep>
<artifactNumToKeep>-1</artifactNumToKeep> </strategy>
</jenkins.model.BuildDiscarderProperty>
<com.cloudbees.jenkins.plugins.git.vmerge.JobPropertyImpl
plugin="git-validated-merge@3.20"> <postBuildPushFailureHandler
class="com.cloudbees.jenkins.plugins.git.vmerge.pbph.PushFailureIsFailure"/>
</com.cloudbees.jenkins.plugins.git.vmerge.JobPropertyImpl>
<com.coravy.hudson.plugins.github.GithubProjectProperty
plugin="github@1.15.0">
<projectUrl>http://github.com/apache/cloudstack/</projectUrl>
<displayName></displayName>
</com.coravy.hudson.plugins.github.GithubProjectProperty>
<org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty
plugin="maven-repo-cleaner@1.2">
<notOnThisProject>false</notOnThisProject>
</org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty>
<com.sonyericsson.rebuild.RebuildSettings plugin="rebuild@1.25">
<autoRebuild>false</autoRebuild>
<rebuildDisabled>false</rebuildDisabled>
</com.sonyericsson.rebuild.RebuildSettings>
<hudson.plugins.throttleconcurrents.ThrottleJobProperty
plugin="throttle-concurrents@1.8.4">
<maxConcurrentPerNode>1</maxConcurrentPerNode>
<maxConcurrentTotal>0</maxConcurrentTotal>
<throttleEnabled>true</throttleEnabled>
<throttleOption>project</throttleOption>
</hudson.plugins.throttleconcurrents.ThrottleJobProperty>
</properties> <scm class="hudson.plugins.git.GitSCM"
plugin="git@2.4.1"> <configVersion>2</configVersion>
<userRemoteConfigs> <hudson.plugins.git.UserRemoteConfig>
<url>https://github.com/apache/cloudstack</url>
</hudson.plugins.git.UserRemoteConfig> </userRemoteConfigs>
<branches> <hudson.plugins.git.BranchSpec> <name>**</name>
</hudson.plugins.git.BranchSpec> </branches>
<doGenerateSubmoduleConfigurations>false</doGenerateSubmoduleConfigurations>
<submoduleCfg class="list"/> <extensions>
<hudson.plugins.git.extensions.impl.BuildChooserSetting>
<buildChooser class="com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl"
plugin="git-validated-merge@3.20"/>
</hudson.plugins.git.extensions.impl.BuildChooserSetting>
</extensions> </scm> <assignedNode>ubuntu</assignedNode>
<canRoam>false</canRoam> <disabled>false</disabled>
<blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
<blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
<jdk>latest1.8</jdk> <triggers>
<com.cloudbees.jenkins.plugins.github__pull.PullRequestBuildTrigger
plugin="github-pull-request-build@1.7"> <spec></spec>
</com.cloudbees.jenkins.plugins.github__pull.PullRequestBuildTrigger>
</triggers> <concurrentBuild>true</concurrentBuild> <builders>
<hudson.tasks.Shell> <command>if [ -f target/reat.txt ]then rm
target/rat.txtfi</command> </hudson.tasks.Shell>
<hudson.tasks.Maven> <targets>clean
--projects='org.apache.cloudstack:cloudstack'
org.apache.rat:apache-rat-plugin:0.10:check</targets>
<mavenName>maven-3.3.3</mavenName>
<usePrivateRepository>false</usePrivateRepository> <settings
class="jenkins.mvn.DefaultSettingsProvider"/> <globalSettings
class="jenkins.mvn.DefaultGlobalSettingsProvider"/>
</hudson.tasks.Maven> <hudson.tasks.Maven>
<targets>-Penablefindbugs install cobertura:cobertura</targets>
<mavenName>maven-3.3.3</mavenName>
<usePrivateRepository>false</usePrivateRepository> <settings
class="jenkins.mvn.DefaultSettingsProvider"/> <globalSettings
class="jenkins.mvn.DefaultGlobalSettingsProvider"/>
</hudson.tasks.Maven> </builders> <publishers>
<hudson.plugins.checkstyle.CheckStylePublisher
plugin="checkstyle@3.43"> <healthy></healthy>
<unHealthy></unHealthy> <thresholdLimit>low</thresholdLimit>
<pluginName>[CHECKSTYLE] </pluginName>
<defaultEncoding></defaultEncoding>
<canRunOnFailed>false</canRunOnFailed>
<usePreviousBuildAsReference>false</usePreviousBuildAsReference>
<useStableBuildAsReference>false</useStableBuildAsReference>
<useDeltaValues>false</useDeltaValues> <thresholds
plugin="analysis-core@1.74">
<unstableTotalAll></unstableTotalAll>
<unstableTotalHigh></unstableTotalHigh>
<unstableTotalNormal></unstableTotalNormal>
<unstableTotalLow></unstableTotalLow>
<unstableNewAll></unstableNewAll>
<unstableNewHigh></unstableNewHigh>
<unstableNewNormal></unstableNewNormal>
<unstableNewLow></unstableNewLow>
<failedTotalAll></failedTotalAll>
<failedTotalHigh></failedTotalHigh>
<failedTotalNormal></failedTotalNormal>
<failedTotalLow></failedTotalLow> <failedNewAll></failedNewAll>
<failedNewHigh></failedNewHigh>
<failedNewNormal></failedNewNormal>
<failedNewLow></failedNewLow> </thresholds>
<shouldDetectModules>false</shouldDetectModules>
<dontComputeNew>true</dontComputeNew>
<doNotResolveRelativePaths>false</doNotResolveRelativePaths>
<pattern></pattern>
</hudson.plugins.checkstyle.CheckStylePublisher>
<hudson.plugins.findbugs.FindBugsPublisher plugin="findbugs@4.62">
<healthy></healthy> <unHealthy></unHealthy>
<thresholdLimit>low</thresholdLimit> <pluginName>[FINDBUGS]
</pluginName> <defaultEncoding></defaultEncoding>
<canRunOnFailed>false</canRunOnFailed>
<usePreviousBuildAsReference>false</usePreviousBuildAsReference>
<useStableBuildAsReference>false</useStableBuildAsReference>
<useDeltaValues>false</useDeltaValues> <thresholds
plugin="analysis-core@1.74">
<unstableTotalAll></unstableTotalAll>
<unstableTotalHigh></unstableTotalHigh>
<unstableTotalNormal></unstableTotalNormal>
<unstableTotalLow></unstableTotalLow>
<unstableNewAll></unstableNewAll>
<unstableNewHigh></unstableNewHigh>
<unstableNewNormal></unstableNewNormal>
<unstableNewLow></unstableNewLow>
<failedTotalAll></failedTotalAll>
<failedTotalHigh></failedTotalHigh>
<failedTotalNormal></failedTotalNormal>
<failedTotalLow></failedTotalLow> <failedNewAll></failedNewAll>
<failedNewHigh></failedNewHigh>
<failedNewNormal></failedNewNormal>
<failedNewLow></failedNewLow> </thresholds>
<shouldDetectModules>false</shouldDetectModules>
<dontComputeNew>true</dontComputeNew>
<doNotResolveRelativePaths>false</doNotResolveRelativePaths>
<pattern></pattern> <isRankActivated>false</isRankActivated>
<excludePattern></excludePattern>
<includePattern></includePattern>
</hudson.plugins.findbugs.FindBugsPublisher>
<hudson.plugins.pmd.PmdPublisher plugin="pmd@3.42">
<healthy></healthy> <unHealthy></unHealthy>
<thresholdLimit>low</thresholdLimit> <pluginName>[PMD]
</pluginName> <defaultEncoding></defaultEncoding>
<canRunOnFailed>false</canRunOnFailed>
<usePreviousBuildAsReference>false</usePreviousBuildAsReference>
<useStableBuildAsReference>false</useStableBuildAsReference>
<useDeltaValues>false</useDeltaValues> <thresholds
plugin="analysis-core@1.74">
<unstableTotalAll></unstableTotalAll>
<unstableTotalHigh></unstableTotalHigh>
<unstableTotalNormal></unstableTotalNormal>
<unstableTotalLow></unstableTotalLow>
<unstableNewAll></unstableNewAll>
<unstableNewHigh></unstableNewHigh>
<unstableNewNormal></unstableNewNormal>
<unstableNewLow></unstableNewLow>
<failedTotalAll></failedTotalAll>
<failedTotalHigh></failedTotalHigh>
<failedTotalNormal></failedTotalNormal>
<failedTotalLow></failedTotalLow> <failedNewAll></failedNewAll>
<failedNewHigh></failedNewHigh>
<failedNewNormal></failedNewNormal>
<failedNewLow></failedNewLow> </thresholds>
<shouldDetectModules>false</shouldDetectModules>
<dontComputeNew>true</dontComputeNew>
<doNotResolveRelativePaths>false</doNotResolveRelativePaths>
<pattern></pattern> </hudson.plugins.pmd.PmdPublisher>
<hudson.plugins.dry.DryPublisher plugin="dry@2.42">
<healthy></healthy> <unHealthy></unHealthy>
<thresholdLimit>low</thresholdLimit> <pluginName>[DRY]
</pluginName> <defaultEncoding></defaultEncoding>
<canRunOnFailed>false</canRunOnFailed>
<usePreviousBuildAsReference>false</usePreviousBuildAsReference>
<useStableBuildAsReference>false</useStableBuildAsReference>
<useDeltaValues>false</useDeltaValues> <thresholds
plugin="analysis-core@1.74">
<unstableTotalAll></unstableTotalAll>
<unstableTotalHigh></unstableTotalHigh>
<unstableTotalNormal></unstableTotalNormal>
<unstableTotalLow></unstableTotalLow>
<unstableNewAll></unstableNewAll>
<unstableNewHigh></unstableNewHigh>
<unstableNewNormal></unstableNewNormal>
<unstableNewLow></unstableNewLow>
<failedTotalAll></failedTotalAll>
<failedTotalHigh></failedTotalHigh>
<failedTotalNormal></failedTotalNormal>
<failedTotalLow></failedTotalLow> <failedNewAll></failedNewAll>
<failedNewHigh></failedNewHigh>
<failedNewNormal></failedNewNormal>
<failedNewLow></failedNewLow> </thresholds>
<shouldDetectModules>false</shouldDetectModules>
<dontComputeNew>true</dontComputeNew>
<doNotResolveRelativePaths>false</doNotResolveRelativePaths>
<pattern></pattern> <highThreshold>50</highThreshold>
<normalThreshold>25</normalThreshold>
</hudson.plugins.dry.DryPublisher> <hudson.tasks.ArtifactArchiver>
<artifacts>target/rat.txt</artifacts>
<allowEmptyArchive>false</allowEmptyArchive>
<onlyIfSuccessful>false</onlyIfSuccessful>
<fingerprint>false</fingerprint>
<defaultExcludes>true</defaultExcludes>
<caseSensitive>true</caseSensitive>
</hudson.tasks.ArtifactArchiver>
<hudson.plugins.cobertura.CoberturaPublisher plugin="cobertura@1.9.7">
<coberturaReportFile>**/target/site/cobertura/coverage.xml</coberturaReportFile>
<onlyStable>false</onlyStable>
<failUnhealthy>false</failUnhealthy>
<failUnstable>false</failUnstable>
<autoUpdateHealth>false</autoUpdateHealth>
<autoUpdateStability>false</autoUpdateStability>
<zoomCoverageChart>false</zoomCoverageChart>
<maxNumberOfBuilds>0</maxNumberOfBuilds>
<failNoReports>true</failNoReports> <healthyTarget>
<targets class="enum-map"
enum-type="hudson.plugins.cobertura.targets.CoverageMetric">
<entry>
<hudson.plugins.cobertura.targets.CoverageMetric>METHOD</hudson.plugins.cobertura.targets.CoverageMetric>
<int>8000000</int> </entry> <entry>
<hudson.plugins.cobertura.targets.CoverageMetric>LINE</hudson.plugins.cobertura.targets.CoverageMetric>
<int>8000000</int> </entry> <entry>
<hudson.plugins.cobertura.targets.CoverageMetric>CONDITIONAL</hudson.plugins.cobertura.targets.CoverageMetric>
<int>7000000</int> </entry> </targets>
</healthyTarget> <unhealthyTarget> <targets
class="enum-map"
enum-type="hudson.plugins.cobertura.targets.CoverageMetric">
<entry>
<hudson.plugins.cobertura.targets.CoverageMetric>METHOD</hudson.plugins.cobertura.targets.CoverageMetric>
<int>0</int> </entry> <entry>
<hudson.plugins.cobertura.targets.CoverageMetric>LINE</hudson.plugins.cobertura.targets.CoverageMetric>
<int>0</int> </entry> <entry>
<hudson.plugins.cobertura.targets.CoverageMetric>CONDITIONAL</hudson.plugins.cobertura.targets.CoverageMetric>
<int>0</int> </entry> </targets>
</unhealthyTarget> <failingTarget> <targets
class="enum-map"
enum-type="hudson.plugins.cobertura.targets.CoverageMetric">
<entry>
<hudson.plugins.cobertura.targets.CoverageMetric>METHOD</hudson.plugins.cobertura.targets.CoverageMetric>
<int>0</int> </entry> <entry>
<hudson.plugins.cobertura.targets.CoverageMetric>LINE</hudson.plugins.cobertura.targets.CoverageMetric>
<int>0</int> </entry> <entry>
<hudson.plugins.cobertura.targets.CoverageMetric>CONDITIONAL</hudson.plugins.cobertura.targets.CoverageMetric>
<int>0</int> </entry> </targets>
</failingTarget> <sourceEncoding>ASCII</sourceEncoding>
</hudson.plugins.cobertura.CoberturaPublisher>
<hudson.plugins.clover.CloverPublisher plugin="clover@4.4.0">
<cloverReportDir>clover</cloverReportDir>
<cloverReportFileName>clover.xml</cloverReportFileName>
<healthyTarget> <methodCoverage>70</methodCoverage>
<conditionalCoverage>80</conditionalCoverage>
<statementCoverage>80</statementCoverage> </healthyTarget>
<unhealthyTarget/> <failingTarget/>
</hudson.plugins.clover.CloverPublisher> </publishers>
<buildWrappers> <hudson.plugins.build__timeout.BuildTimeoutWrapper
plugin="build-timeout@1.15.1"> <strategy
class="hudson.plugins.build_timeout.impl.ElasticTimeOutStrategy">
<timeoutPercentage>400</timeoutPercentage>
<numberOfBuilds>3</numberOfBuilds>
<timeoutMinutesElasticDefault>180</timeoutMinutesElasticDefault>
</strategy> <operationList/>
</hudson.plugins.build__timeout.BuildTimeoutWrapper>
<hudson.plugins.clover.CloverBuildWrapper plugin="clover@4.4.0">
<historical>false</historical> <json>false</json>
<licenseCert></licenseCert>
</hudson.plugins.clover.CloverBuildWrapper>
</buildWrappers></project>
On Wed, May 18, 2016 at 8:56 PM, Daan Hoogland <da...@gmail.com>
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 <
> rafaelweingartner@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 <ws...@cloudops.com>
>> 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&entity=method
>> > >
>> > at
>> >
>> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
>> > <
>> >
>> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch&entity=method
>> > >
>> > at
>> >
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
>> > <
>> >
>> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch&entity=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)
>> > 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
>> >
>> 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)
>> >
>> >
>> > *Will STEVENS*
>> > Lead Developer
>> >
>> > *CloudOps* *| *Cloud Solutions Experts
>> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> > w cloudops.com *|* tw @CloudOps_
>> >
>> > On Wed, May 18, 2016 at 12:26 PM, Rafael Weingärtner <
>> > rafaelweingartner@gmail.com> wrote:
>> >
>> > > 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 <
>> daan.hoogland@gmail.com
>> > >
>> > > 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 <
>> > > > rafaelweingartner@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 <
>> > > daan.hoogland@gmail.com
>> > > > >
>> > > > > 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 <
>> > > > > > rafaelweingartner@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 <
>> > > > > williamstevens@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
>> > >
>> >
>>
>>
>>
>> --
>> Rafael Weingärtner
>>
>
>
>
> --
> Daan
>
--
Daan
Re: How to fix Jenkins git workspace issues
Posted by Rafael Weingärtner <ra...@gmail.com>.
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 <da...@gmail.com>
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 <
> rafaelweingartner@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 <ws...@cloudops.com>
> > 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&entity=method
> > > >
> > > at
> > >
> >
> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
> > > <
> > >
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch&entity=method
> > > >
> > > at
> > >
> >
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
> > > <
> > >
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch&entity=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)
> > > 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
> > >
> >
> 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)
> > >
> > >
> > > *Will STEVENS*
> > > Lead Developer
> > >
> > > *CloudOps* *| *Cloud Solutions Experts
> > > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > > w cloudops.com *|* tw @CloudOps_
> > >
> > > On Wed, May 18, 2016 at 12:26 PM, Rafael Weingärtner <
> > > rafaelweingartner@gmail.com> wrote:
> > >
> > > > 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 <
> > daan.hoogland@gmail.com
> > > >
> > > > 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 <
> > > > > rafaelweingartner@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 <
> > > > daan.hoogland@gmail.com
> > > > > >
> > > > > > 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 <
> > > > > > > rafaelweingartner@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 <
> > > > > > williamstevens@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
> > > >
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Daan
>
--
Rafael Weingärtner
Re: How to fix Jenkins git workspace issues
Posted by Daan Hoogland <da...@gmail.com>.
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 <
rafaelweingartner@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 <ws...@cloudops.com>
> 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&entity=method
> > >
> > at
> >
> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
> > <
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch&entity=method
> > >
> > at
> >
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
> > <
> >
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch&entity=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)
> > 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
> >
> 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)
> >
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> > On Wed, May 18, 2016 at 12:26 PM, Rafael Weingärtner <
> > rafaelweingartner@gmail.com> wrote:
> >
> > > 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 <
> daan.hoogland@gmail.com
> > >
> > > 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 <
> > > > rafaelweingartner@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 <
> > > daan.hoogland@gmail.com
> > > > >
> > > > > 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 <
> > > > > > rafaelweingartner@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 <
> > > > > williamstevens@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
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>
--
Daan
Re: How to fix Jenkins git workspace issues
Posted by Rafael Weingärtner <ra...@gmail.com>.
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 <ws...@cloudops.com> 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&entity=method
> >
> at
> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch&entity=method
> >
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
> <
> http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch&entity=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)
> 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
> 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)
>
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Wed, May 18, 2016 at 12:26 PM, Rafael Weingärtner <
> rafaelweingartner@gmail.com> wrote:
>
> > 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 <daan.hoogland@gmail.com
> >
> > 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 <
> > > rafaelweingartner@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 <
> > daan.hoogland@gmail.com
> > > >
> > > > 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 <
> > > > > rafaelweingartner@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 <
> > > > williamstevens@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
> >
>
--
Rafael Weingärtner
Re: How to fix Jenkins git workspace issues
Posted by Will Stevens <ws...@cloudops.com>.
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&entity=method>
at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
<http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch&entity=method>
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
<http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch&entity=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)
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 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)
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_
On Wed, May 18, 2016 at 12:26 PM, Rafael Weingärtner <
rafaelweingartner@gmail.com> wrote:
> 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 <da...@gmail.com>
> 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 <
> > rafaelweingartner@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 <
> daan.hoogland@gmail.com
> > >
> > > 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 <
> > > > rafaelweingartner@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 <
> > > williamstevens@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
Posted by Rafael Weingärtner <ra...@gmail.com>.
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 <da...@gmail.com>
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 <
> rafaelweingartner@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 <daan.hoogland@gmail.com
> >
> > 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 <
> > > rafaelweingartner@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 <
> > williamstevens@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
Posted by Daan Hoogland <da...@gmail.com>.
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 <
rafaelweingartner@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 <da...@gmail.com>
> 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 <
> > rafaelweingartner@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 <
> williamstevens@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
Posted by Rafael Weingärtner <ra...@gmail.com>.
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 <da...@gmail.com>
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 <
> rafaelweingartner@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 <williamstevens@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
Re: How to fix Jenkins git workspace issues
Posted by Daan Hoogland <da...@gmail.com>.
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 <
rafaelweingartner@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 <wi...@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
Re: How to fix Jenkins git workspace issues
Posted by Rafael Weingärtner <ra...@gmail.com>.
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 <wi...@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