CODEWITHSUNDEEP
javamavensvnjbossjenkins
Upen
Upen

Reputation: 1438

Jenkins CI Job Workspace custom changes

I have setup a CI environment for deploying to dev using Jenkins/Maven/SVN. For the deployment to Jboss Eap server, I am using JBoss as maven plugin. Since the project teams does not have the plugin for this the jboss-as:deploy in the respective poms, once I create the job in Jenkins and a local workspace gets created for the project, I manually update the pom.xml with the plugin and the server configuration. Is there any way to automate this process? I dont have the option to ask all project teams to commit the plugin in the pom file. Issues i am facing.

  1. Project teams commit a change at the same line number where I added the jboss as dependency in the pom, caused a svn merge conflict in my Jenkins local workspace and the build fails since pom is corrupted.

  2. For every job, I have to manually update the POM in the Jenkins workspace.

  3. If I have to deploy a project to multiple app servers, I have to create multiple jobs.

Can anyone suggest a solution.

Upvotes: 0

Views: 170

Answers (1)

Mateva
Mateva

Reputation: 812

I would create another distribution-component and keep it separately, e.g. as a component or module. I would update inside its pom.xml the change you mentioned and just support two projects - the developers' one and the one used for other purposes.

Upvotes: 1

Related Questions