I'm just looking for automated testing of pull requests. Any packaging/publishing of SNAPSHOTs would still need to be done on Jenkins and is only needed after a PR is merged. (IMHO publishing SNAPSHOTs for SCIMple is optional at this point). If/when we get to that point we can/should reevaluate the CI requirements. [Opinion] For now, we can keep it simple and just use GH Actions.
On Tue, May 31, 2022 at 10:02 AM Shawn McKinney <[email protected]> wrote: > My experience with Jenkins is limited, so excuse my ignorance. > > Can you describe the goal, is it to setup a pipeline in order to run > automated testing and packaging? > > I know we do that with other projects. For example, fortress has a > pipeline. > > Stefan was the one who helped us get that going. > > — > Shawn > > > On May 20, 2022, at 9:52 AM, Brian Demers <[email protected]> wrote: > > > > I'm not sure when the Jenkins PR builder was added, but based on the > history, I was the first person to trigger the job. > > It failed: > https://ci-builds.apache.org/job/Directory/job/dir-scimple-pull-requests > > > > Connection timeout connecting to GitHub. It's possible this was a > one-time problem, but... > > I just added the configuration for GH actions, as this should allow us > to run CI against external forks (contributions). > > Along with this, I enabled dependabot to help keep the dependencies > updated. > > All PRs are now built against Java 8, 11, and 17. > > > > I'll try to babysit all of the dep updates, as they are pushed through > dependabot. > > > > NOTE: There is still a Jenkins job that polls (daily) for changes to > `develop`, and it looks like it's configured to publish SNAPSHOTs. > > > > > > I might be missing some context about how/when/why the Jenkins PR job > was added, if so please let me know and I can re-enable the job. > > > > -Brian > >
