Is it compulsory to use a parent pom >= 2.0 to use ci.jenkins.io?

[Ivo Bellin Salarin]

Hi all,

The MSTest plugin had a Jenkins job on the old CI server. But now it has been disabled.

Thus, I am evaluating the possibility to move to the new CI server. I have read on the official documentation that I should create a Jenkinsfile and use a parent pom > 2.0.

My questions concern the compulsory minimum version and the available plugins on ci.jenkins.io: for example, I would like to integrate a sonarcloud step. Is this possible?

Many thanks in advance,

Ivo BS

[Slide]

The parent version in the pom must be > 2.0 (and should be at least 2.32 in practice). This does NOT mean that your plugin requires that version of Jenkins. The parent pom version and Jenkins version were decoupled. You can specify a minimum version of Jenkins that your plugin supports via the <jenkins.version></jenkins.version> setting in a <properties></properties> block in your pom.xml. The buildPlugin() in the Jenkinsfile is the easiest possible way to build your plugin, if you want to add additional steps, you could have your own Jenkinsfile implementation.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPc4eF8fx1A5i6%2B_p4Ax4zhgg%2BvXob5H1a3BpjuAWfbqXP_J4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Ivo Bellin Salarin]

Great! Thanks a lot, Slide!

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVc03K5ua7KjijFQUd6BYLyaujV9KBrOY6wts9TTuptoeA%40mail.gmail.com.