[ 
https://issues.apache.org/jira/browse/DIRMINA-1197?focusedWorklogId=1023621&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1023621
 ]

ASF GitHub Bot logged work on DIRMINA-1197:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Jun/26 08:14
            Start Date: 04/Jun/26 08:14
    Worklog Time Spent: 10m 
      Work Description: elecharny commented on PR #53:
URL: https://github.com/apache/mina/pull/53#issuecomment-4620268878

   Hi Piotr,
   
   some information:
   * branches 2.0.X and 2.1.X *won't* work with java > 1.8
   * The maven command should be `mvn clean install -Pserial` (the 'serial' 
profile is necessary to build all the modules.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1023621)
    Time Spent: 20m  (was: 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: 20m
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to