When using hudson-sync-plugin to get the latest version of jbpm component:
<plugin> <groupId>org.jboss.maven.plugin</groupId> <artifactId>hudson-job-sync-plugin</artifactId> <version>0.0.1-SNAPSHOT</version> <executions> <execution> <phase>install</phase> <goals> <goal>run</goal> </goals> </execution> </executions> <configuration> <!-- more output w/ verbose; default: false --> <verbose>true</verbose> <!-- server and connection details --> <hudsonURL>https://hudson.qa.jboss.com/hudson/</hudsonURL> <username>admin</username> <password>#############</password> <!-- to select a subset of jobs, use these filters; default: view/myViewName/ --> <viewFilter>view/DevStudio/view/DevStudio_Trunk/</viewFilter> <regexFilter>jbosstools-3.3_trunk.component--jbpm</regexFilter> <!-- if there's an existing config.xml (not config.$timestamp.xml) then overwrite it if true; default false --> <overwriteExistingConfigXMLFile>true</overwriteExistingConfigXMLFile> <operation>pull</operation> </configuration>
I get
[INFO] --- hudson-job-sync-plugin:0.0.1-SNAPSHOT:run (default) @ sync --- [INFO] Hudson URL: https://hudson.qa.jboss.com/hudson/ [INFO] Operation: pull [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS
However my config.xml is not updated (when existing), or not created in case it's not existing.
Something is wrong with this component. SOA jobs often loose sync between cache and Hudson. It could because they belong to several views.
This bug in hudson-sync-plugin is the cause of several weird cases in Jenkins.