Eclipse Community Forums: Hudson » Build Publisher 1.11

Home » Archived » Hudson » Build Publisher 1.11(Build publisher problems with Hudson 3.1.2)

Fri, 25 April 2014 07:41

Eclipse User

We are in the process of upgrading from Hudson 2.2.1 to Hudson 3.1.2 and are having problems with the build publisher in Hudson 3.1.2.

The builds are received but the project build history is not updated. The first time a build is published to the project it appears in the build history but subsequent builds do not. I have noticed a new file call _RunMap.xml in the project configuration directory is not updated after the first build.

Is this a known issue?

Regards,

Terry Wright

Re: Build Publisher 1.11 [message #1314907 is a reply to message #1314464]

Fri, 25 April 2014 13:32

Eclipse User

What do you mean by build publisher?

Can you please take a look at this public Hudson instance and let us know if you have configured Hudson differently. Build history is shown correctly here.

Do you see any exception in the Hudson log. Wondering if any plugin is misbehaving. Can you list the plugins you have installed.

_RunMap.xml is for caching mechanism to reduce Hudson memory foot print. You can check the XML file and see if the entries are there correctly. If doesn't exist it is recreate on startup.

Re: Build Publisher 1.11 [message #1314945 is a reply to message #1314907]

Fri, 25 April 2014 14:01

Eclipse User

I'm referring to the build-publisher plugin (version 1.11). We use it to publish build results of jobs from several Hudson servers to a central one, used as a dashboard more than anything else (We can't use a master/slave configuration due to having to use VSS as our SCM).

The build history is correct on the originating server but the build history on the server receiving the build results does not get updated unless the RunMap.xml file does not exist or has been deleted. The xml file does seem to contain relevant entries but only for a single build. The build results are received by the receiving server correctly and are put into the project builds directory.

I won't have access to the servers until Monday but from memory there are no exception entries as such. The system log on the receiving server says something like it accepted the published build and that is has renamed the build directory (to the same name).

We have been using this successfully with Hudson 2.2.1.

Re: Build Publisher 1.11 [message #1315024 is a reply to message #1314945]

Fri, 25 April 2014 15:00

Eclipse User

Terry, thanks for the explanation. We will try to reproduce on or side.

Just curious, why can't you use a master/slave configuration due to having to use VSS as your SCM? Wondering if plugins like
http://wiki.hudson-ci.org/display/HUDSON/Clone+Workspace+SCM+Plugin
is of useful to you in this situation.

Re: Build Publisher 1.11 [message #1315055 is a reply to message #1315024]

Fri, 25 April 2014 15:29

Eclipse User

Thanks Winston.

I'll have a look at the clone plugin. I think the issue with VSS is that the plugin was written before the SCM remoting interface was developed. We would probably have licensing issues anyway as VSS is no longer sold. We have plans to move to another SCM but it won't be anytime soon.

Re: Build Publisher 1.11 [message #1315130 is a reply to message #1315055]

Fri, 25 April 2014 16:30

Eclipse User

Highly recommend git, since it is my favorite Smile

and very widely used. It works on windows too.

Re: Build Publisher 1.11 [message #1322156 is a reply to message #1315130]

Tue, 29 April 2014 14:17

Eclipse User

Here is a log from a minimal install. The only plugin I added in addition to the default plugins was the build-publisher. The log shows 6 builds and although they are accepted by the public facing server (hudson-dashboard) the build history does not get updated on this server. The RunMap.xml file does not get updated after the first published build (build #1 did not have publishing enabled).

Hudson log from building server:
Apr 27, 2014 1:52:23 PM hudson.plugins.build_publisher.PublisherThread run
INFO: Build #6 of project test was published.

Apr 27, 2014 1:52:23 PM hudson.model.Run run
INFO: Build test #6 main build action completed: SUCCESS

Apr 27, 2014 1:52:11 PM hudson.plugins.build_publisher.PublisherThread run
INFO: Build #5 of project test was published.

Apr 27, 2014 1:52:11 PM hudson.model.Run run
INFO: Build test #5 main build action completed: SUCCESS

Apr 27, 2014 1:51:34 PM hudson.plugins.build_publisher.PublisherThread run
INFO: Build #4 of project test was published.

Apr 27, 2014 1:51:34 PM hudson.model.Run run
INFO: Build test #4 main build action completed: SUCCESS

Apr 27, 2014 1:51:16 PM hudson.plugins.build_publisher.PublisherThread run
INFO: Build #3 of project test was published.

Apr 27, 2014 1:51:16 PM hudson.model.Run run
INFO: Build test #3 main build action completed: SUCCESS

Apr 27, 2014 1:50:48 PM hudson.plugins.build_publisher.PublisherThread run
INFO: Build #2 of project test was published.

Apr 27, 2014 1:50:46 PM hudson.model.Run run
INFO: Build test #2 main build action completed: SUCCESS

Apr 27, 2014 1:49:59 PM hudson.model.Run run
INFO: Build test #1 main build action completed: SUCCESS

Hudson log from server receiving build:
Apr 27, 2014 1:52:23 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Renaming: D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-52-23 to D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-52-23

Apr 27, 2014 1:52:23 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Got remote timezone Europe/London

Apr 27, 2014 1:52:11 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Renaming: D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-52-11 to D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-52-11

Apr 27, 2014 1:52:11 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Got remote timezone Europe/London

Apr 27, 2014 1:51:34 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Renaming: D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-51-34 to D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-51-34

Apr 27, 2014 1:51:34 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Got remote timezone Europe/London

Apr 27, 2014 1:51:16 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Renaming: D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-51-16 to D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-51-16

Apr 27, 2014 1:51:16 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Got remote timezone Europe/London

Apr 27, 2014 1:50:48 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Renaming: D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-50-46 to D:\hudson-dashboard\jobs\test\builds\2014-04-27_13-50-46

Apr 27, 2014 1:50:48 PM hudson.plugins.build_publisher.ExternalProjectProperty doAcceptBuild
INFO: Got remote timezone Europe/London

RunMap.xml file:
<?xml version='1.0' encoding='UTF-8'?>
<buildHistory>
<builds>
<build>
<number>2</number>
<displayName>#2</displayName>
<fullDisplayName>test #2</fullDisplayName>
<buildDir>2014-04-27_13-50-46/</buildDir>
<state>COMPLETED</state>
<result>SUCCESS</result>
<building>false</building>
<logUpdated>false</logUpdated>
<timestamp>1398603046000</timestamp>
<duration>218</duration>
<url>job/test/2/</url>
<builtOn></builtOn>
</build>
</builds>
<markers>
<LAST__STABLE>2</LAST__STABLE>
<LAST__COMPLETED>2</LAST__COMPLETED>
<LAST__SUCCESSFUL>2</LAST__SUCCESSFUL>
</markers>
</buildHistory>

Previous Topic:	Problems installing and using Hudson 3.1.2
Next Topic:	Team based Authentication:Perform maven release link is not visible

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 13:33:29 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter