[jbosstools-issues] [JBoss JIRA] (JBIDE-11778) Hudson-sync-plugin fails silently
Mickael Istria (JIRA)
jira-events at lists.jboss.org
Fri May 4 05:21:18 EDT 2012
Mickael Istria created JBIDE-11778:
--------------------------------------
Summary: Hudson-sync-plugin fails silently
Key: JBIDE-11778
URL: https://issues.jboss.org/browse/JBIDE-11778
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
When using hudson-sync-plugin to get the latest version of jbpm component:
{code:xml}
<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>
{code}
I get
{code}
[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
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list