I am not entirely happy with github issues as they are vendor specific.
However, I also acknowledge that it eases contribution path and reduces
troubles with sign ups.
As for github actions - I've recently ported own builds and made couple
reusable workflows for maven build and release [1] which I continue
tweaking. Overall reusable workflows have some limitations, but they
come handy with mutliple job/repos/branches. People even come with
cross-repository triggers [2] which might be seen similar to jenkins
pipelines.
I experienced no stability issues, even using public executors, so big +
for github on that field.
Cheers,
Łukasz
[1] https://github.com/ConnectorIO/gh-actions-shared
[2]
https://blog.marcnuri.com/triggering-github-actions-across-different-repositories
On 5.02.2024 07:56, Jean-Baptiste Onofré wrote:
Hi,
Yeeah, that would help. As said, my priority is the 4.5.0 release this
week. The move to GH will happen after.
Thanks !
Regards
JB
On Mon, Feb 5, 2024 at 7:33 AM Grzegorz Grzybek <gr.grzy...@gmail.com> wrote:
Hello
JBO - we can discuss on slack later if you decide to migrate - we can use the
scripts I used to migrate Pax projects.
regards
Grzegorz Grzybek
sob., 3 lut 2024 o 06:39 Jean-Baptiste Onofré <j...@nanthrax.net> napisał(a):
Hi guys,
it seems we have a consensus here.
I propose to complete Karaf 4.5.0 release first and then I will move
forward on the switch to GH Issues (and also GH Actions).
Thanks,
Regards
JB
On Tue, Oct 31, 2023 at 9:27 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
Hi guys,
I would like to propose to move from Jira to GH Issues and from
Jenkins to GH Actions.
As we have several sub-projects, each sub-project will have its own
space, like we do for Karaf Minho
(https://github.com/apache/karaf-minho).
The migration should be "smooth" and I will work on it if you agree.
Thoughts ?
Regards
JB
