Hi everyone Karaf Decanter has been using GitHub Issues and Actions for months without problem (stability, etc).
On the other hand, on Karaf (runtime), we still have "stability" issues with Jenkins. I will move forward on moving Karaf (runtime) to GitHub: 1. I will enable GitHub Action for CI (and disable Jenkins in a second step) 2. I will review the .asf.yaml and enable GitHub Issues. For the existing issue, we can use the same script used on Pax projects. 3. I will enable dependabot I will do that after the 4.4.8 release (just to avoid "noise" during the release process). Regards JB On Wed, Feb 5, 2025 at 4:54 PM Jean-Baptiste Onofré <[email protected]> wrote: > > Hi folks, > > I moved karaf-decanter to GitHub resources. Basically, it means: > 1. The Jira issues have been moved to GitHub Issues > (https://github.com/apache/karaf-decanter/issues). I did a cleanup too > in the meantime. The decanter component is now Archived on Jira. > 2. The CI moved from Jenkins to GitHub Action (named Build, > https://github.com/apache/karaf-decanter/actions/workflows/build.yml). > Jenkinsfile has been removed from karaf-decanter. > 3. Dependabot has been enabled to create dependency update PRs. > 4. I defined PR and branch policy: > - squash & commit is the only merge button available on PR > - merging pull request require at least one approval > - main branch requires linear history > > Regards > JB > > On Tue, Oct 31, 2023 at 9:27 AM Jean-Baptiste Onofré <[email protected]> > 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
