Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Hudson CI (Deploying bundles to Virgo via Hudson Jobs)
Hudson CI [message #638435] Thu, 11 November 2010 09:59 Go to next message
AA  is currently offline AA
Messages: 2
Registered: November 2010
Junior Member
Hi All,

I am just wondering if it is possible to deploy bundles to Virgo server via configured Hudson jobs and Maven. Similar to tomcat Maven plugin by which we can deploy artifacts to tomcat container.

Regards,
AA

[Updated on: Thu, 11 November 2010 10:00]

Report message to a moderator

Re: Hudson CI [message #638440 is a reply to message #638435] Thu, 11 November 2010 10:20 Go to previous messageGo to next message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
That's not supported. This sounds similar to bug 329886, but feel free to raise a separate enhancement bug if the function you would like to see is not covered by that bug.
Re: Hudson CI [message #640008 is a reply to message #638435] Thu, 18 November 2010 16:25 Go to previous messageGo to next message
Ivar Suisalu is currently offline Ivar Suisalu
Messages: 3
Registered: November 2010
Junior Member
Hi.

Actually we are doing this - Hudson copies built by maven bundles into dm server usr repository and later on we copy plan file into pickup folder.
Mostly works, but i am not 100% satisfied, so i decided to do another way
around:

I have kind of plan file, which beside of artefacts, defines dependencies between them. This plan (i call it provisioning spec) is processed by provisioning service, which works together with maven local repo and remote ones and if it finds new updates to artifacts then it deployes them into
dm server(i am talking about version 2.0.4 - i couldn't find virgo deps in repos),
using JMX deployer.

Now problem is, that after some deployments in a raw server tells, me that:
--------
[2010-11-18 17:03:07.556] service-monitor-thread-1 <KE0100W> Reference '&org.springframework.osgi.service.importer.support.Osgi ServiceProxyFactoryBean#0' in bundle 'com.springsource.kernel.deployer' version '2.0.4.RELEASE' is waiting for service with filter '(objectClass=com.springsource.kernel.osgi.region.Region)'.
[2010-11-18 17:03:07.558] service-monitor-thread-1 <KE0100W> Reference '&bundleStarter' in bundle 'com.springsource.kernel.deployer' version '2.0.4.RELEASE' is waiting for service with filter '(objectClass=com.springsource.kernel.core.BundleStarter)'.
---------------
and after a while the timeout occurs:
----------------------
[2010-11-18 17:08:02.624] Thread-3 <AG0000E> Application context creation failure for bundle 'com.springsource.kernel.deployer' version '2.0.4.RELEASE'. org.springframework.context.ApplicationContextException: Application context initialization for 'com.springsource.kernel.deployer' has timed out
at org.springframework.osgi.extender.internal.dependencies.star tup.DependencyWaiterApplicationContextExecutor.timeout(Depen dencyWaiterApplicationContextExecutor.java:454)
-----------------------------
Actually the bundles are deployed, but the message is annoying.
Anybody can comment, what could be wrong?
From admin console the 'com.springsource.kernel.deployer' bundle looks 'active' all the time.

Regards
Ivar
Re: Hudson CI [message #640146 is a reply to message #640008] Fri, 19 November 2010 10:36 Go to previous messageGo to next message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
It looks like your changes broke the user region as the RegionManager is failing to initialise properly.
Re: Hudson CI [message #640327 is a reply to message #638435] Sat, 20 November 2010 17:00 Go to previous messageGo to next message
Ivar Suisalu is currently offline Ivar Suisalu
Messages: 3
Registered: November 2010
Junior Member
I did some testing at it seems that the import of 'com.springsource.kernel.deployer' kills the whale.
I used virgin installation of dm-server version 2.0.4 and i modified the
provisioning service bundle this way that it actually doesn't use deployer over JMX,
but copies properties files into pickup dir. And the server showed again:
--------------------------
[2010-11-20 17:49:48.552] fs-watcher <HD0001I> Hot deployer processing 'MODIFIED' event for file 'runtime.properties'.
[2010-11-20 17:49:48.558] fs-watcher <DE0007I> Refreshing configuration 'runtime' version '0.0.0'.
[2010-11-20 17:49:48.565] fs-watcher <DE0008I> Refreshed configuration 'runtime' version '0.0.0'.
[2010-11-20 17:49:48.571] fs-watcher <DE0004I> Starting configuration 'runtime' version '0.0.0'.
[2010-11-20 17:49:48.577] fs-watcher <DE0005I> Started configuration 'runtime' version '0.0.0'.
[2010-11-20 17:49:48.586] fs-watcher <HD0001I> Hot deployer processing 'MODIFIED' event for file 'runtime0.properties'.
[2010-11-20 17:49:48.593] fs-watcher <DE0007I> Refreshing configuration 'runtime0' version '0.0.0'.
[2010-11-20 17:49:48.617] fs-watcher <DE0008I> Refreshed configuration 'runtime0' version '0.0.0'.
[2010-11-20 17:49:48.626] fs-watcher <DE0004I> Starting configuration 'runtime0' version '0.0.0'.
[2010-11-20 17:49:48.635] fs-watcher <DE0005I> Started configuration 'runtime0' version '0.0.0'.
[2010-11-20 17:49:48.647] fs-watcher <HD0001I> Hot deployer processing 'MODIFIED' event for file 'runtime1.properties'.
[2010-11-20 17:49:48.663] fs-watcher <DE0007I> Refreshing configuration 'runtime1' version '0.0.0'.
[2010-11-20 17:49:48.671] fs-watcher <DE0008I> Refreshed configuration 'runtime1' version '0.0.0'.
[2010-11-20 17:49:48.681] fs-watcher <DE0004I> Starting configuration 'runtime1' version '0.0.0'.
[2010-11-20 17:49:48.693] fs-watcher <DE0005I> Started configuration 'runtime1' version '0.0.0'.
[2010-11-20 17:50:02.474] service-monitor-thread-1 <KE0100W> Reference '&org.springframework.osgi.service.importer.support.Osgi ServiceProxyFactoryBean#0' in bundle 'com.springsource.kernel.deployer' version '2.0.4.RELEASE' is waiting for service with filter '(objectClass=com.springsource.kernel.osgi.region.Region)'.
[2010-11-20 17:50:02.486] service-monitor-thread-1 <KE0100W> Reference '&bundleStarter' in bundle 'com.springsource.kernel.deployer' version '2.0.4.RELEASE' is waiting for service with filter '(objectClass=com.springsource.kernel.core.BundleStarter)'.
---------
When i removed the import from MANIFEST and code the warning didn't show up.
I started this bundle form ext repository and kernel/lib, but the result was the same. And the RegionManager started OK as i saw in debugger. Any ideas, what could be wrong?
Re: Hudson CI [message #640364 is a reply to message #640327] Sun, 21 November 2010 04:54 Go to previous messageGo to next message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
When you say the region manager started ok, do you mean the bundle goes to ACTIVE state? This may be so, but the warning messages show that the region manager has not published its service, so Spring DM has not finished processing the region manager.

You may like to read the documentation for Spring DM 1.2.1 to understand how/when Spring DM does its processing - basically it's triggered by the bundle becoming ACTIVE (actually when the STARTED event it fired).

In general, I would recommend putting your bundles in repository/usr and leaving repository/ext and kernel/lib unmodified. Modifying the kernel requires a good understanding of the design of Virgo which will take some time to acquire.

To debug your problem, I would back off and make incremental changes to pin down the problem. That way you will find out what is causing the region manager trouble. The chances are that at least one of the services is requires is delayed, but it is puzzling why you don't see more warning messages saying which other services are delayed, so it feels like something more serious is wrong.

Hope that helps.
Re: Hudson CI [message #640372 is a reply to message #638435] Sun, 21 November 2010 08:27 Go to previous messageGo to next message
AA  is currently offline AA
Messages: 2
Registered: November 2010
Junior Member
Guys,

I am very new to Virgo server world. Based on your discussion it appears that there is a workaround for my issue. Could you please lead me through the steps needed to deploy bundles (built by maven) to Virgo.


Many Thanks,
AA
Re: Hudson CI [message #640463 is a reply to message #640372] Mon, 22 November 2010 08:45 Go to previous messageGo to next message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
The basic approach is to put your bundles in repository/usr and then deploy one or more plans either by dropping them in the pickup directory or by using the admin console. The plans should refer to the bundles in the normal way - see this section of the programmer guide.
Re: Hudson CI [message #640484 is a reply to message #640364] Mon, 22 November 2010 10:04 Go to previous messageGo to next message
Ivar Suisalu is currently offline Ivar Suisalu
Messages: 3
Registered: November 2010
Junior Member
If i am right the region manager sits in "com.springsource.kernel.osgi" bundle and this bundle is started by kernel:

file:lib/kernel/com.springsource.kernel.osgi-2.0.4.RELEASE.jar@start,\

in kernel.launch.properties.

During server start this bundle lifecycle is not shown in medic event messages and i can't see this bundle state nor in admin console or ssh console. Perhaps
i shouldn't see it anyway. But when i debugged RegionManager initializiation and the debugger hits the breakpoint, the same message appeared:
-----------
[2010-11-22 11:48:15.941] service-monitor-thread-1 <KE0100W> Reference '&org.springframework.osgi.service.importer.support.Osgi ServiceProxyFactoryBean#0' in bundle 'com.springsource.kernel.deployer' version '2.0.4.RELEASE' is waiting for service with filter '(objectClass=com.springsource.kernel.osgi.region.Region)'.
---------------
when i continued the execution, the reference was satisfied.
As i sayed, i did incremental changes in my provisioning service and the warning messages appeared, when my bundle wanted to import
'com.springsource.kernel.deployer'

Ivar.
Re: Hudson CI [message #640489 is a reply to message #640484] Mon, 22 November 2010 10:20 Go to previous message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
Hi Ivar

Everything you describe looks normal except I can't say why your provisioning service should cause the kernel initialisation to be fouled up. I suggest you debug the RegionManager initialisation in the case where the provisioning manager is causing problems.
Previous Topic:An Import-Package could not be resolved. constraint: <Import-Package: javax.validation; version=
Next Topic:Best practice question?
Goto Forum:
  


Current Time: Fri Oct 31 04:11:21 GMT 2014

Powered by FUDForum. Page generated in 0.03991 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software