Skip to content

synyx/nexus-step-plugins

 
 

Repository files navigation

Toolchain Example

The vagrant sub folder contains a multi-machine configuration using Nexus, Jenkins and Rundeck as a pipeline infrastructure.

The toolchain moves an simple webapp from build (jenkins), to publish (nexus), then deploy (rundeck).

Rundeck contains a set of plugins and jobs that check for artifacts in the nexus repo and deploys them, recording their locations to the Rundeck resource model.

See some screenshots.

Configuration properties

The plugin requires several configuration properties defined so it knows how to access the nexus server. Rundeck can be configured globally via the framework.properties or per project using project.properties.

Nexus: Nexus server URL. eg, http://repository.example.com:8081/nexus and without a nexus context http://repository.example.com,

  • configure project: project.plugin.WorkflowStep.nexus-deliver-artifact-step.nexus=value
  • configure framework: framework.plugin.WorkflowStep.nexus-deliver-artifact-step.nexus=value

Nexus User: Nexus login name

  • configure project: project.plugin.WorkflowStep.nexus-deliver-artifact-step.nexusUser=value
  • configure framework: framework.plugin.WorkflowStep.nexus-deliver-artifact-step.nexusUser=value

Nexus Password: Nexus login password

  • configure project: project.plugin.WorkflowStep.nexus-deliver-artifact-step.nexusPassword=value
  • configure framework: framework.plugin.WorkflowStep.nexus-deliver-artifact-step.nexusPassword=value

Model Source Directory: Directory where model source data is stored.

  • configure project: project.plugin.WorkflowStep.nexus-register-delivery-step.modelDirPath=value
  • configure framework: framework.plugin.WorkflowStep.nexus-register-delivery-step.modelDirPath=value

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Groovy 52.0%
  • Shell 44.9%
  • Ruby 3.1%