Plugin build failure on ci.jenkins.io after upgrading plugin to Jenkins version 2.235.5 to 2.479.1

Using Jenkins Ask a question
1

I am facing an issue with the Jenkins CI pipeline for the Thycotic plugin. After upgrading the plugin from Jenkins version 2.235.5 to 2.479.1 and Java 8 to Java 17, the build fails on ci.jenkins.io, specifically on the Linux (linux-8) agent.
Earlier with java 8 and Jenkins version 2.235.5 the build(checks) successful.

Jenkins Plugin Setup:
Plugin Repo: Jenkins baseline upgraded to 2.479 by delinea-rajani · Pull Request #42 · jenkinsci/thycotic-secret-server-plugin · GitHub
Java version: Upgraded from 8 → 17
Jenkins baseline: 2.479 (compatible with Java 17)
Parent POM version: 5.7

Jenkinsfile Build Config:

buildPlugin(
  useContainerAgent: true,
  configurations: [
    [platform: 'linux', jdk: 17],
    [platform: 'windows', jdk: 17],
  ]
)

Local build pass using Java 17 but on ci jenkins io, the build fails with Java-related errors in pom. I have tried:
Ensured buildPlugin(…) configuration is correct
Checked if local dependencies are Java 17 compatible

Is there a known issue with Java 17 builds on ci jenkins io ?
Or is there something else I need to adjust in the plugin configuration to get this working?

Thanks in advance for any guidance

linux-8 / Build (linux-8) / Shell Script
Error in sh step, with arguments mvn --batch-mode --show-version --errors --no-transfer-progress --update-snapshots -Dmaven.repo.local=/home/jenkins/agent/workspace/cotic-secret-server-plugin_PR-42@tmp/m2repo -Dmaven.test.failure.ignore -Dspotbugs.failOnError=false -Dcheckstyle.failOnViolation=false -Dcheckstyle.failsOnError=false -Dpmd.failOnViolation=false -Penable-jacoco clean install.


[2025-05-30T05:00:25.399Z] + mvn --batch-mode --show-version --errors --no-transfer-progress --update-snapshots -Dmaven.repo.local=/home/jenkins/agent/workspace/cotic-secret-server-plugin_PR-42@tmp/m2repo -Dmaven.test.failure.ignore -Dspotbugs.failOnError=false -Dcheckstyle.failOnViolation=false -Dcheckstyle.failsOnError=false -Dpmd.failOnViolation=false -Penable-jacoco clean install
[2025-05-30T05:00:25.501Z] -XX:InitialHeapSize=187499968 -XX:MaxHeapSize=2999999488 -XX:+PrintCommandLineFlags -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseParallelGC 
[2025-05-30T05:00:25.703Z] Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
[2025-05-30T05:00:25.704Z] Maven home: /usr/share/apache-maven-3.9.9
[2025-05-30T05:00:25.704Z] Java version: 1.8.0_452, vendor: Temurin, runtime: /opt/jdk-8/jre
[2025-05-30T05:00:25.705Z] Default locale: en_US, platform encoding: UTF-8
[2025-05-30T05:00:25.705Z] OS name: "linux", version: "5.15.180.1-1.cm2", arch: "amd64", family: "unix"
[2025-05-30T05:00:26.509Z] [INFO] Error stacktraces are turned on.
[2025-05-30T05:00:26.610Z] [INFO] Scanning for projects...
[2025-05-30T05:00:29.220Z] [ERROR] [ERROR] Some problems were encountered while processing the POMs:
[2025-05-30T05:00:29.221Z] [ERROR] Unknown packaging: hpi @ line 13, column 16
[2025-05-30T05:00:29.221Z]  @ 
[2025-05-30T05:00:29.221Z] [ERROR] The build could not read 1 project -> [Help 1]
[2025-05-30T05:00:29.221Z] org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[2025-05-30T05:00:29.222Z] [ERROR] Unknown packaging: hpi @ line 13, column 16
[2025-05-30T05:00:29.222Z] 
[2025-05-30T05:00:29.222Z]     at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:389)
[2025-05-30T05:00:29.223Z]     at org.apache.maven.graph.DefaultGraphBuilder.collectProjects (DefaultGraphBuilder.java:349)
[2025-05-30T05:00:29.223Z]     at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor (DefaultGraphBuilder.java:340)
[2025-05-30T05:00:29.223Z]     at org.apache.maven.graph.DefaultGraphBuilder.build (DefaultGraphBuilder.java:76)
[2025-05-30T05:00:29.224Z]     at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:448)
[2025-05-30T05:00:29.224Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:197)
[2025-05-30T05:00:29.224Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
[2025-05-30T05:00:29.225Z]     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
[2025-05-30T05:00:29.225Z]     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
[2025-05-30T05:00:29.225Z]     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
[2025-05-30T05:00:29.225Z]     at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
[2025-05-30T05:00:29.226Z]     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
[2025-05-30T05:00:29.226Z]     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
[2025-05-30T05:00:29.226Z]     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
[2025-05-30T05:00:29.227Z]     at java.lang.reflect.Method.invoke (Method.java:498)
[2025-05-30T05:00:29.227Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
[2025-05-30T05:00:29.227Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
[2025-05-30T05:00:29.228Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361)
[2025-05-30T05:00:29.228Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
[2025-05-30T05:00:29.228Z] [ERROR]   
[2025-05-30T05:00:29.228Z] [ERROR]   The project io.jenkins.plugins:thycotic-secret-server:2.1 (/home/jenkins/agent/workspace/cotic-secret-server-plugin_PR-42/pom.xml) has 1 error
[2025-05-30T05:00:29.229Z] [ERROR]     Unknown packaging: hpi @ line 13, column 16
[2025-05-30T05:00:29.229Z] [ERROR] 
[2025-05-30T05:00:29.229Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[2025-05-30T05:00:29.229Z] [ERROR] 
[2025-05-30T05:00:29.230Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[2025-05-30T05:00:29.230Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException



linux-8 / Build (linux-8) / Archive JUnit-formatted test results
Error in junit step.

No test report files were found. Configuration error?
Build log
[2025-05-30T05:00:07.802Z] Recording test results
[2025-05-30T05:00:07.978Z] No test report files were found. Configuration error?
2

Seems you resolved at least the problem with the Jenkinsfile

3

The configuration on ci.jenkins.io disallows non-maintainers of plugins from modifying the Jenkinsfile. I ran your modified Jenkinsfile on the job as an administrator of ci.jenkins.io, but that is because administrators have the ability to replay a build with a different Jenkinsfile.

You can request to become a maintainer of the plugin so that your Jenkinsfile changes would be executed. You can periodically ask an administrator to run your Jenkinsfile for you. One of those two should let you complete your transition to Java 17.

5

I am maintaining the Thycotic plugin on GitHub. I’d like to become a maintainer on ci.jenkins.io so I can run and modify the Jenkinsfile directly. Could you guide me on how to request or confirm maintainer permissions for the plugin on the Jenkins infrastructure?

6

Thanks for contributing to the plugin! As far as I can tell from the repository permissions list, the only maintainer of that plugin is the account thycotic_dsv. That account has successfully worked with Jira issues.

The GitHub history shows that pull requests to that repository have been merged by:

I assume they have merge permission on the repository, while you do not.

You’re not listed as a maintainer in the repository permissions list. In order for your changes to the Jenkinsfile to be executed by ci.jenkins.io , your Jenkins Jira (and Artifactory) username needs to be in the repository permissions list.

If you don’t already have an account for Jenkins Jira and Jenkins Artifactory, you can register for an account. It is simplest if you use the same account name there as you use on GitHub.

Once you’ve registered your Jenkins account, please login to Jenkins Jira and Jenkins Artifactory, then submit a repository permissions pull request to add yourself as a maintainer in the repository permissions. Mention the existing maintainer in the pull request because that account will need to approve your addition as a maintainer.

Those steps are also described in the “adopt a plugin” documentation with screenshots and more description.