You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/06/04 07:53:00 UTC
[jira] [Work logged] (DIRMINA-1197) Fix abandoned GitHub Actions
[ https://issues.apache.org/jira/browse/DIRMINA-1197?focusedWorklogId=1023620&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1023620 ]
ASF GitHub Bot logged work on DIRMINA-1197:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jun/26 07:52
Start Date: 04/Jun/26 07:52
Worklog Time Spent: 10m
Work Description: ppkarwasz opened a new pull request, #53:
URL: https://github.com/apache/mina/pull/53
Update the GitHub Actions workflow to current action versions and runners, and clarify its comments.
- Pin to ubuntu-latest, windows-latest and macos-latest, testing JDK 17, 21 and 25 on Temurin.
- Bump actions/checkout to v6 (without persisting credentials), actions/setup-java to v5 (with Maven caching), and add an actions/upload-artifact@v7 step for the surefire reports.
- Limit push builds to the maintained production branches so internal feature branches are not built twice.
- Add a workflow-level concurrency group that cancels superseded pull request runs while letting pushes to the production branches run to completion.
- Run `mvn verify` instead of `mvn test`, and set per-job permissions.
Assisted-By: Claude Opus 4.8 (1M context) <no...@anthropic.com>
Issue Time Tracking
-------------------
Worklog Id: (was: 1023620)
Remaining Estimate: 0h
Time Spent: 10m
> Fix abandoned GitHub Actions
> ----------------------------
>
> Key: DIRMINA-1197
> URL: https://issues.apache.org/jira/browse/DIRMINA-1197
> Project: MINA
> Issue Type: Improvement
> Reporter: Piotr Karwasz
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Many workflows in {{apache/mina}} seem abandoned.
> Currently only two branches carry a workflow, both the single file {{{}.github/workflows/ci.yaml{}}}:
> * {{trunk}} (last modified 2020-10-12)
> * {{2.2.X}} (last modified 2023-04-30)
> Branches {{2.0.X}} and {{2.1.X}} have no workflows at all. Meanwhile all four branches received commits as recently as 2026-06-01, so the workflow files have sat untouched for 3 to 5 years against actively developed code.
> Both {{ci.yaml}} files use sunset runners and obsolete actions, so they can no longer run on current GitHub infrastructure:
> * {{runs-on}} requests {{ubuntu-18.04}} (fully removed in April 2023) and {{windows-2016}} (also removed). Jobs pinned to these labels can no longer be scheduled and fail immediately.
> * Steps use {{actions/checkout@v1}} and {{{}actions/setup-java@v1{}}}, both deprecated Node 12 era actions. The current majors are v4/v5.
> * The trigger is {{on: [push]}} with no branch or path filter, so it attempts to run on every push to every branch, including {{bugfix/*}} and experimental branches.
> I can help modernizing the workflows, but I would need to know which branches should run workflows on {{{}push{}}}. Is it {{{}2.0.X{}}}, {{{}2.1.X{}}}, {{2.2.X}} and {{{}trunk{}}}? Note that {{2.0.X}} and {{2.1.X}} currently have none, so please confirm whether they should gain one.
> Note that workflows should be updated regularly, especially since all actions except those from the {{actions}} and {{github}} organisation need to be whitelisted by the ASF. If there are many active development branches, it might be useful to host *reusable* workflows in one specialized branch (e.g. {{{}gha/v1{}}}) and only refer to them from other branches.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org