[Amdatu-developers] [JIRA] (AMDATU-607) Provisioning itest integration

[Bram de Kruijff (JIRA)]

Bram de Kruijff commented on AMDATU-607 Provisioning itest integration Correction! I assumed it would succeed cause it did on bamboo. Locally I still get the following testfailure. Might be windows related? Not sure at this point. It is now windows friendly Passing in a file:///c.. uri to the file constructor was throwing IllegalArgumentExceptions... I added an example that shows how to provision multiple bundles, a resource processor and a configuration. It adds a second test case to our one class. Looks good. Works for me. We could define helpers that define standard deployment package builder configurations to get you started, but as you can see, listing what you need already is pretty straightforward. Maybe we could add something like: CoreDeploymentPackage.createAll() : DeploymentPackageBuilder -> that contains all the "standard" bundles and configurations (with the same optional exclude list) ? The idea was allowing not to know what to need as long as you are happy with mostly defaults. Yes, something like this. Ultimately we could switch provisioning on/of and tests keep working. But that mught be a followup issue Quite frankly, I could use a bit of help to replace that SNAPSHOT with a specific version. Never did that. Can you briefly explain how and why? We only want hardcoded versions in pom files so they are easily/automagically updatable in one place. For extenal deps we like them to be non SNAPSHOT asap. We must resolve them before release as maven wont allow a release with SNAPSHOT deps cause its non deterministic. So if you put in an external SNAPSHOT dependency and I am doing a release next week I'll bump my nose at that 1 minute to deadline time. The how id documented at http://www.amdatu.org/confluence/display/Amdatu/Build+infrastructure but you'll probably still run into th webdav authorization issue (only gx personal can deploy). I agree we can move ManagementAgent to "base". I was pondering about whether we should add these new things (ManagementAgent, CoreDeploymentPackage, etc.) to the existing base bundle, or if we should create a new one. That is why I initially didn't do either yet. Good question. See my earlier comment. Do we still want to support the old mechanism? Or force a move to the new provisioning setup? Let's do some more pondering.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________
Amdatu-developers mailing list
Amdatu-developers@amdatu.org
http://lists.amdatu.org/mailman/listinfo/amdatu-developers