search

viltgroup / jenkins-xcp-ci-plugin

Documentum xCP Plugin for jenkins
Other
3 stars 5 forks source link

Configuration XML File is Missing #8

Open pramodbenda opened 8 years ago

pramodbenda commented 8 years ago

Hi,

Thanks for providing this Jenkins Plugin for xCP, I tried using it and one thing I noticed is it is not generating the Configuration XML (in the target folder) which is used for xCP Deployment. Do you think I am doing something wrong.

Thanks Pramod Benda.

joaori commented 8 years ago

Hello Pramod,

Are you checking inside the target/ folder of the xCP Application?

In the wiki example, it would be src/TestApplication/target/

Regards, João

pramodbenda commented 8 years ago

Thanks for your response. I was able to figure out the problem, the issue is with Maven Version (earlier used 3.2.2 as you shown in wiki example), I changed it to 3.0.2 (like it is used in xCP Designer) everything is working fine. But one thing is my project is getting built in target folder not src//target

joaori commented 8 years ago

Right, that's probably because you haven't defined any Local module directory when setting Source Control for your job, right?

I was able to successfully use the plugin with maven 3.2.2 so it's a bit strange that you are not able to.

pramodbenda commented 8 years ago

Yes, you are right I just realized the Local Module Directory is set ".". Still not sure why it is not working for me with Maven 3.2.2. I have two more questions for you

  1. Were you able to build without running xCP Designer?
  2. In Deploy xCP Application Instructions Step 0 - Prepare SVN Structure, how can we get the deployment Artifacts into SVN using Jenkins.

Thanks Pramod Benda

joaori commented 8 years ago

Hello Pramod,

I'm afraid you're getting way offtopic here.

  1. xCP Designer is mandatory to build a xCP project using maven. As you can see from the pom.xml, there are several plugins dependencies from EMC that depend on it. Please take a look to xCP Designer's help files for more information on how to build an application using maven. (this Jenkins plugins simply tries to facilitate that configuration)
  2. Not sure if I understand your question. What do you mean by "deployment artifacts"? You want to know how to upload the WAR generated in the build into SVN? I guess you could so some (Windows/Unix) script for it, but I wouldn't recommend you to store binaries into SVN.
pramodbenda commented 8 years ago

I am sorry, seems like again I am seeing the same problem that Configuration XML is not getting generated (XIP_xip_2.1.1238_config.xml) is missing, I can see the WAR getting generated. Not sure what should I look at.

joaori commented 8 years ago

Was the WAR generated? Please post jenkins Console Output of the job execution to see if I can figure it out.

pramodbenda commented 8 years ago

Yes, the WAR file is getting generated, I don't the config XML getting generated. I have attached the Job execution Output and Configuration Screenshots for your reference.

Please help me getting this resolved.

Jenkins Build Output.txt Jenkins_Configuration_Screenshots.docx

jahangiranwari commented 8 years ago

@pramodbenda, the config.xml file is not generated when building an xCP application from command line using Maven. The xCP Designer 2.1 user guide pg. 353 mentions that

Maven creates .WAR and .config.xml files for the application created using xCP Designer.

Under the hood this plugin uses Maven to build the application from command line.

If your goal is to get a copy of the config.xml then you can use the "Package Application" feature in xCP Designer which will build the WAR and also the config.xml file. You can then save a copy of this config.xml file and use it during deployments.

Additionally, if you are deploying your application across different environments (i.e. Test, Staging, Production) you may want to consider having different config.xml files for each environment.