How to register deployable built by other tool using ctl? Always getting "No matched nodes: NodeSet{}". Not possible with ctier?

[Oliver Kuntze]

Hi,
I have a deployable myDeploybale.zip created by another build tool.
Now I'd like to register this deployable with ControlTier. Please note that I don't want to upload the deployable to the ControlTier repository, since it already resides in my Nexus repository.
Executing ctl -p myProject -t zip -r myDeployable -c register -- -version 1.0.0 -filename myDeployable.zip -installroot myDeploymentTarget -url myNexusUrlPointingToDeployable always results in the error message "No matched nodes: NodeSet{}".
Executing ctl -p myProject -m zip -c register -- -name myDeployable -version 1.0.0 -filename myDeployable.zip -installroot myDeploymentTarget -url myNexusUrlPointingToDeployable yields no error at all, but I don't want to register a type, I want to register an instance of a type.
Any ideas?
Cheers
Oliver

[Oliver Kuntze]

Found out one thing:
If I provide a corresponding xml project file with the deployable, then ctl -p myProject -m zip -c register -- -filename myDeployable.zip -myDeployable.zip.xml works like a charm.
So, no chance doing it without the xml?
And what about using the ctier maven plugin? Do I have to provide a temporary myDeployable.xml to be able to register a deployable from within my maven lifecycle?

[Oliver Kuntze]

Ok, can live with the extra xml file.
A shame that ctier development is discontinued. The integrated solution with Jenkins, Nexus and CntrolTier has quite some appeal. Clean, automated interface between dev and ops.

[Moses Lei]

On Thu, Sep 6, 2012 at 12:55 AM, Oliver Kuntze <oliver...@web.de> wrote:

Executing ctl -p myProject -m zip -c register -- -name myDeployable -version 1.0.0 -filename myDeployable.zip -installroot myDeploymentTarget -url myNexusUrlPointingToDeployable yields no error at all, but I don't want to register a type, I want to register an instance of a type.

Oliver, did you try this? It *should* register a zip resource of name "myDeployable". This is in effect doing the same thing as using an xml file, but with command line arguments. (That said, I would recommend using resourcename "myDeployable.zip", IOW the full filename.)

In the end though, using xml is more flexible. I usually just call load-objects on the xml file directly (which is what the zip#register command does anyway if you specify an xml file).

--
Moses Lei
[ Professional Services | DTO Solutions, Inc. ]
[ mobile: +1 703.901.5969 | e-mail: ml...@dtosolutions.com | aim/gtalk: ml...@controltier.com | yahoo: moseslei | windows live (msn): ml...@dtosolutions.com ]

 

[Anthony Shortland]

Have you looked at Rundeck, Oliver? It's a ControlTier spin-off that people are combining with Jenkins and Nexus in the way you propose below with great success. If you add in Rerun for modular automation and Yana2 for a resource model you have all the elements of the ControlTier framework in a loosely-coupled tool-chain.

Anthony.

On Sep 7, 2012, at 1:36 AM, Oliver Kuntze <oliver...@web.de> wrote:

Ok, can live with the extra xml file.
A shame that ctier development is discontinued. The integrated solution with Jenkins, Nexus and CntrolTier has quite some appeal. Clean, automated interface between dev and ops.

--
You received this message because you are subscribed to the Google Groups "ControlTier" group.
To post to this group, send email to contr...@googlegroups.com
To unsubscribe from this group, send email to controltier...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/controltier?hl=en
http://wiki.controltier.org