You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2023/05/19 02:00:00 UTC

[jira] [Closed] (GUACAMOLE-1754) CI in Github Actions

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

Mike Jumper closed GUACAMOLE-1754.
----------------------------------
    Fix Version/s: 1.6.0
       Resolution: Done

> CI in Github Actions
> --------------------
>
>                 Key: GUACAMOLE-1754
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1754
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-client, guacamole-server
>            Reporter: James Muehlner
>            Assignee: Mike Jumper
>            Priority: Major
>             Fix For: 1.6.0
>
>
> We should consider using Github Actions to run CI for PRs to ensure that all changes at least build before being merged. 
> My first thought would be to just run the included docker build for both guacamole-server and guacamole-client.
> We would have to make sure that we don't hog the runners for too long though, as noted in [https://infra.apache.org/github-actions-secrets.html] 
> {quote}The ASF maxes out its runner allocation quite often, so a project needs to plan carefully to make best use of them for everyone's sake. For example, it would be important not to trigger a full release test with a pull request that is correcting a typo on one page in one module.
> {quote}



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