Piotr and I are very well aware of reusable GitHub workflows
<https://docs.github.com/en/actions/using-workflows/reusing-workflows>. As
a matter of fact, that is what I am currently working on: moving all our
shared `pom.xml` (the distribution ZIP creation, signing, changelog
management, etc.) and GitHub workflow (`build.yml`, etc.) boilerplate to
`logging-parent` and *reusing* it in `logging-log4j-tools` to cut a
release. In our last video call – we missed you Matt ;) – I agreed with
Ralph to PoC this and share the results in `dev@` and upon consensus
practice this on `logging-log4j2`.

On Wed, Aug 23, 2023 at 11:09 PM Matt Sicker <m...@musigma.org> wrote:

> Something that may be relevant as we split up repos more and have more
> actions defined.
>
> > Begin forwarded message:
> >
> > From: Slawomir Jaranowski <s.jaranow...@gmail.com>
> > Subject: Shared GitHub actions
> > Date: August 19, 2023 at 10:17:58 AM CDT
> > To: Commons Developers List <d...@commons.apache.org>
> > Reply-To: "Commons Developers List" <d...@commons.apache.org>
> > List-Id: <dev.commons.apache.org>
> >
> > Hi,
> >
> > I see that Apache Commons projects use GitHub actions ...
> > In every project actions is defined from scratch, it looks very similar,
> > like:
> >
> >
> https://github.com/apache/commons-parent/blob/master/.github/workflows/maven.yml
> >
> https://github.com/apache/commons-codec/blob/master/.github/workflows/maven.yml
> >
> https://github.com/apache/commons-cli/blob/master/.github/workflows/maven.yml
> >
> > Maintaining such resources in each project separately can waste time ...
> >
> > I have introduced shared GitHub actions  in Maven projects and can help
> to
> > do similar tasks in Commons projects.
> > https://github.com/apache/maven-gh-actions-shared
> >
> > Of course each project can have its own requirements and it will be
> > reasonable to have separate shared actions for Commons projects.
> >
> > If you are interested let me know and we can start working on it in some
> > example projects.
> >
> > --
> > Sławomir Jaranowski
>
>

Reply via email to