我们在Jenkins有一个构建工作,一旦手动触发就会持续构建。 (当前构建开始时,总会有一个新构建添加到队列中。)没有配置构建触发器,因此它只应在手动触发时启动。
有关工作的一些细节:
无其他配置。
Git配置也很简单: 已填写Git URL,包括凭据。所有其他都是默认设置。
版本信息:
config.xml中
<?xml version='1.0' encoding='UTF-8'?>
<maven2-moduleset plugin="maven-plugin@2.9">
<actions/>
<description></description>
<logRotator class="hudson.tasks.LogRotator">
<daysToKeep>30</daysToKeep>
<numToKeep>20</numToKeep>
<artifactDaysToKeep>30</artifactDaysToKeep>
<artifactNumToKeep>5</artifactNumToKeep>
</logRotator>
<keepDependencies>false</keepDependencies>
<properties>
<jenkins.plugins.maveninfo.config.MavenInfoJobConfig plugin="maven-info@0.2.0">
<mainModulePattern></mainModulePattern>
<dependenciesPattern></dependenciesPattern>
<assignName>false</assignName>
<nameTemplate></nameTemplate>
<assignDescription>false</assignDescription>
<descriptionTemplate></descriptionTemplate>
</jenkins.plugins.maveninfo.config.MavenInfoJobConfig>
<hudson.plugins.disk__usage.DiskUsageProperty plugin="disk-usage@0.25"/>
<org.jvnet.hudson.plugins.shelveproject.ShelveProjectProperty plugin="shelve-project-plugin@1.5"/>
</properties>
<scm class="hudson.plugins.git.GitSCM" plugin="git@2.3.5">
<configVersion>2</configVersion>
<userRemoteConfigs>
<hudson.plugins.git.UserRemoteConfig>
<name>origin</name>
<url>ssh://user@server:29418/project</url>
<credentialsId>creds-here</credentialsId>
</hudson.plugins.git.UserRemoteConfig>
</userRemoteConfigs>
<branches>
<hudson.plugins.git.BranchSpec>
<name>**</name>
</hudson.plugins.git.BranchSpec>
</branches>
<doGenerateSubmoduleConfigurations>false</doGenerateSubmoduleConfigurations>
<browser class="hudson.plugins.git.browser.GitWeb">
<url></url>
</browser>
<submoduleCfg class="list"/>
<extensions/>
</scm>
<canRoam>true</canRoam>
<disabled>false</disabled>
<blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
<blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
<jdk>Java 7 (Update 21)</jdk>
<triggers/>
<concurrentBuild>false</concurrentBuild>
<rootModule>
<groupId>com.example</groupId>
<artifactId>artifactId</artifactId>
</rootModule>
<goals>clean install</goals>
<mavenName>Maven 3.1</mavenName>
<aggregatorStyleBuild>true</aggregatorStyleBuild>
<incrementalBuild>false</incrementalBuild>
<ignoreUpstremChanges>true</ignoreUpstremChanges>
<archivingDisabled>false</archivingDisabled>
<siteArchivingDisabled>false</siteArchivingDisabled>
<fingerprintingDisabled>false</fingerprintingDisabled>
<resolveDependencies>false</resolveDependencies>
<processPlugins>false</processPlugins>
<mavenValidationLevel>-1</mavenValidationLevel>
<runHeadless>false</runHeadless>
<disableTriggerDownstreamProjects>true</disableTriggerDownstreamProjects>
<settings class="jenkins.mvn.DefaultSettingsProvider"/>
<globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/>
<reporters/>
<publishers/>
<buildWrappers/>
<prebuilders/>
<postbuilders/>
<runPostStepsIfResult>
<name>UNSTABLE</name>
<ordinal>1</ordinal>
<color>YELLOW</color>
<completeBuild>true</completeBuild>
</runPostStepsIfResult>
</maven2-moduleset>
有任何想法如何解决这个问题?
答案 0 :(得分:0)
This other (duplicate?) question表明,这是Jenkins中的一个微妙的错误,当发生配置更改时,无需重新启动Jenkins。虽然我们还没有科学证明它,但有趣的是,这似乎也是我们的经验。在周末重新开始我们的Jenkins服务之后,我们现在再也无法重现这个问题了。如果问题回来并且我们能够了解更多信息,那么会在此处发布更多信息。