GitHub Actions

[Tony Atkins]

Hi, Gio.

Great to hear this.  I know we could all work our way through the
documentation and experiment with our own projects in time, but It'd be
great for maintainers in the community to save time by learning from what
you had to do.  Would you be able to briefly write up what you had to do or
possibly demo/present briefly in an upcoming meeting?

Cheers,


Tony

On Tue, 16 Jun 2020 at 21:46, Giovanni Tirloni <gtirloni at ocadu.ca> wrote:

> Hello,
>
> It seems GitHub Actions is working as expected.
>
> With that in mind, I'd like to disable Jenkins for the two Fluid repos
> that have builds enabled: Infusion and Kettle.
>
> Please let me know if there are any concerns.
>
> Regards,
> Giovanni
>
> ------------------------------
> *From:* Giovanni Tirloni <gtirloni at ocadu.ca>
> *Sent:* Monday, April 20, 2020 18:10
> *To:* fluid-work at lists.idrc.ocad.ca <fluid-work at lists.idrc.ocad.ca>
> *Subject:* GitHub Actions
>
> Hello,
>
> We're running an experiment to see if GitHub Actions [0] is a good
> replacement for our current Jenkins-based CI system.
>
> I've enabled Actions in the fluid-project/infusion repository today. Every
> new PR (and updates to old PRs) and commits to the master branch will
> trigger CI builds in both GitHub Actions and Jenkins. We'll run them in
> parallel for a while to collect usage data.
>
> The GitHub Actions workflow has a few benefits for us:
>
>    - GitHub-owned runners so we don't need to worry about maintaining our
>    own servers
>    - Configuration As Code: the CI configuration lives in the repository
>    and can be modified with PRs
>    - Better integration with the GitHub UI
>
> We'll be trying more customizations in the near future but for now the
> GitHub Actions workflow in the Infusion repository more or less mimics the
> actions of the Jenkins-based pipeline configuration in the
> fluid-project/ci-service repository. For example, it doesn't yet publish a
> new Infusion build when commits are made to the master branch, that's
> coming next as it requires changes to how we do deployments.
>
> If you notice any issues or have any feedback, please feel free to reach
> out. If we have a good experience with Actions, we'll add it to more
> repositories.
>
> 0 - https://github.com/features/actions
>
> Regards,
> *Giovanni Tirloni*
> DevOps Engineer
> Inclusive Design Research Centre, OCAD University
> https://idrc.ocadu.ca
> _______________________________________________________
> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
> To unsubscribe, change settings or access archives,
> see https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20200619/2ba93717/attachment.htm>