You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Ben Weidig (Jira)" <ji...@apache.org> on 2026/05/03 09:51:00 UTC
[jira] [Resolved] (TAP5-2819) Jenkinsfile Matrix build
[ https://issues.apache.org/jira/browse/TAP5-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ben Weidig resolved TAP5-2819.
------------------------------
Fix Version/s: 5.10.0
Resolution: Done
To simplify the build setup, we now have Multibranch Jenkinsfile-based build jobs:
* Jenkinsfile
* Jenkingsfile.integration-variants
The primary Jenkinsfile is a matrix build for the minimum and maximum supported JDK, running all unit tests and the default set of integration tests.
The secondary Jenkinsfile runs the other 3 integration test variants.
The split allows for faster iteration times and mitigates the general flakiness of integration tests to some extent.
The auto-discovery of new branches is currently disabled, but should be configured after cleaning up all the stale branches.
> Jenkinsfile Matrix build
> ------------------------
>
> Key: TAP5-2819
> URL: https://issues.apache.org/jira/browse/TAP5-2819
> Project: Tapestry 5
> Issue Type: Task
> Reporter: Ben Weidig
> Assignee: Ben Weidig
> Priority: Minor
> Fix For: 5.10.0
>
>
> Currently, the Jenkins projects are configured manually for different Java versions.
> However, there seems to be a matrix feature [0] for quite some time that would move the config from the build server directly into the project.
> Tis should be evaluated and implemented if it makes maintenance easier over time.
> [0]: [https://www.jenkins.io/blog/2019/11/22/welcome-to-the-matrix/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)