You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jspwiki.apache.org by "Juan Pablo Santos Rodríguez (Jira)" <ji...@apache.org> on 2025/07/29 14:48:00 UTC

[jira] [Closed] (JSPWIKI-1194) CI/CD Pipeline Optimization for Apache JSPWiki with JDK-17 Integration

     [ https://issues.apache.org/jira/browse/JSPWIKI-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juan Pablo Santos Rodríguez closed JSPWIKI-1194.
------------------------------------------------

> CI/CD Pipeline Optimization for Apache JSPWiki with JDK-17 Integration
> ----------------------------------------------------------------------
>
>                 Key: JSPWIKI-1194
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-1194
>             Project: JSPWiki
>          Issue Type: New Feature
>    Affects Versions: 2.12.2
>            Reporter: Arturo Bernal
>            Assignee: Arturo Bernal
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.12.3
>
>
> The CI/CD pipeline for Apache JSPWiki is currently experiencing issues related to the integration of JDK-17 and the handling of test-jar dependencies. This ticket aims to optimize the Jenkins pipeline by consolidating the build steps, ensuring compatibility with JDK-17, and resolving the test-jar dependency issues.
> *Details:*
>  * *Current Issues:*
>  ** The sonar scanner requires JDK-17 to run at SonarCloud.
>  ** The CI build is split into three steps: {{{}mvn package{}}}, SonarQube upload, and snapshot deployment.
>  ** The third stage skips tests, causing a test-jar dependency not to be built and uploaded.
>  ** Builds fail when the required test-jar is not found.
>  * *Objective:*
>  ** Ensure the CI pipeline uses JDK-17 as the primary JDK for builds.
>  ** Consolidate the Maven build steps to ensure the test-jar dependency is built and uploaded.
>  ** Maintain compatibility checks with JDK-11 and JDK-21 without interfering with the primary build process.
>  ** Modify the Jenkinsfile to reflect these changes.
> *Proposed Solution:*
>  # Update the Jenkinsfile to use JDK-17 as the primary JDK.
>  # Combine build steps to ensure the test-jar dependency is always built and uploaded.
>  # Retain JDK-11 and JDK-21 builds for compatibility checks.
>  # Simplify the conditional deployment process for snapshot versions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)