Home/ Questions/Q 6573029
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T15:04:50+00:00

I am looking to create a three-step process for our internal development, and I

  • 0

I am looking to create a three-step process for our internal development, and I am having some issues with the third step.

Step 1:
A developer will use Jenkins to build/deploy a snapshot release of a project to the Nexus snapshot repository. As a post build step, this project will also deploy the built WAR to Tomcat (Using the DeployArtifact plugin).

Step 2:
Using the Jenkins promoted builds plugin, a developer can nominate a build to be ready for QA. This build is then tagged with an release candidate number, and deployed to the Nexus release repository.

Step 3:
I would like QA to be able to log into Jenkins and be able to deploy the newly created release candidate to Tomcat (a different tomcat instance for QA).

I know I can do all of this via a manual build process with shell scripting, but I was really hoping that there would be a Jenkins plugin to allow QA to find a list of the release candidate plugins and deploy a specific one to Tomcat.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think you’re looking for something like the Jenkins Artifactory plug-in for release management.

    The closest you’ll get, using Nexus, is the Staging suite functionality. I’m not aware of any integration it might have with Hudson or Jenkins. Additionally this is only available with the professional version of Nexus.

    • 0