CI/CD Pipeline at Sonatype Technical Guide

What Are You Working On
1

The CI/CD Pipeline at Sonatype technical guide describes the declarative Jenkins pipeline used at Sonatype, and shows you where our products integrate in a modern CI/CD process.

If you’ve read the article, please tell us what you think. Your feedback helps us see how things are going with our current content and also decide what we should work on next. Take a minute to answer the following questions and/or reply to this topic with your thoughts. Thank you!

Scale: 1 = strongly disagree / 5 = strongly agree

  1. This topic was relevant and useful.
  • 1
  • 2
  • 3
  • 4
  • 5

0 voters

  1. This guide answered my questions and provided needed information.
  • 1
  • 2
  • 3
  • 4
  • 5

0 voters

  1. This guide was easy to understand and follow.
  • 1
  • 2
  • 3
  • 4
  • 5

0 voters

2

@bstrozewski

I read your ci/cd pipeline article and found it interesting. We are currently embarking on a similar pipeline.

I have a question around some params you have defined - for example: mavenCommon.mavenVersion and pipelineCommon.downstreamJobName.

Where are these parameters actually defined?

I assume you are using a shared library which is not shown in your pipeline but surely these parameters are different for every project so can not be kept in the shared library?

Are they defined in the Jenkinsfile as well but just not shown?

1 Like
3

@rob.white It’s briefly shown in the video @2:56.
It seems to be a mix of parameters & sharedLibrary that parses the parameters.

I’m also trying to reproduce this example.