Could be that it requires a newer version of Jenkins like 2.249.x. Not
sure on the exact requirements, but whenever something doesn't show
updates in the UC, that's typically one of the main reasons.
On Tue, 13 Oct 2020 at 11:09, Gavin McDonald <gmcdon...@apache.org> wrote:
>
> Hi ,
>
> On Tue, Oct 13, 2020 at 5:25 PM Matt Sicker <boa...@gmail.com> wrote:
>
> > I'm not sure if we have the latest version of it, but the GitHub SCM
> > reporting plugin we have installed should add GitHub Checks links to
> > replay parts or all of a pipeline. Note that the GitHub SCM Reporting
> > option is not enabled by default, but enabling it is about all you
> > need to do to get the features it provides.
> >
>
> We are on version 1.10 - I see there are 8 newer releases since this,
> however
> our Jenkins is not saying there are any updates. Will have to investigate
> further.
>
> Gav...
>
>
> >
> > On Tue, 13 Oct 2020 at 00:02, Joan Touzet <woh...@apache.org> wrote:
> > >
> > > And to add to this, with the Blue Ocean UI for Multibranch Pipeline, it
> > > is a single click to rebuild a build. It's not as friendly as
> > > commenting, but it's a single button on the results view for your build,
> > > which is linked right from the PR.
> > >
> > > Of course, this is limited to only people who have Jenkins accounts,
> > > which is all committers to our repo.
> > >
> > > -Joan
> > >
> > > On 2020-10-12 11:10 p.m., Christopher wrote:
> > > > Hi Andor,
> > > >
> > > > I'm not sure if INFRA is going to enable that plugin, but I thought
> > > > I'd suggest some alternatives if they don't:
> > > >
> > > > In Accumulo, we set up a "PR Builder" job in Jenkins, that we can
> > > > manually trigger. It is a parameterized build that takes two
> > > > parameters: PR and PR_Variant.
> > > > The PR is the PR number, and the variant is either "head" or "merge".
> > > > The branch specifier to check out is:
> > > > refs/remotes/origin/pr/${PR}/${PR_variant}
> > > > The refspec to fetch from the repository configuration looks like:
> > > > +refs/pull/*:refs/remotes/origin/pr/* (you have to click on Advanced
> > > > to see this option)
> > > > We also use the "Set Build Name" option to: PR #${PR} (Build
> > #${BUILD_NUMBER})
> > > > And include a "Pre-Build step" to upload the build description to:
> > > > Pull Request <a href="${GIT_URL}/pull/${PR}">#${PR}</a> - <a
> > > > href="${GIT_URL}/commits/${GIT_COMMIT}">${GIT_COMMIT}</a>
> > > >
> > > > This works well for us. It may work for you also. The only thing is
> > > > you have to go to Jenkins to trigger the build manually.
> > > >
> > > > We also use GitHub Actions, which is probably even easier to build,
> > > > because GitHub has a "rebuild jobs" option, right in the interface (to
> > > > work around transient build problems), and you can configure some
> > > > manually triggered jobs as well. We have several that might be useful
> > > > examples at:
> > https://github.com/apache/accumulo/tree/main/.github/workflows/
> > > >
> > > > I hope this helps somebody, if not you,
> > > >
> > > > Christopher
> > > >
> > > > On Mon, Oct 12, 2020 at 8:53 AM Andor Molnar <an...@apache.org> wrote:
> > > >>
> > > >> Hi,
> > > >>
> > > >> Sorry if the topic is redundant, I haven’t been following builds@
> > list for a while and couldn’t find the archives online.
> > > >>
> > > >> Is there already a way to configure GitHub PR comment to trigger
> > build in the new Jenkins instance?
> > > >>
> > > >> I think it was the ‘GitHub PR Comment Build’ plugin in the old
> > instance.
> > > >> https://plugins.jenkins.io/github-pr-comment-build
> > > >>
> > > >> Thanks,
> > > >> Andor
> > > >>
> > > >>
> >
> >
> >
> > --
> > Matt Sicker <boa...@gmail.com>
> >
>
>
> --
>
> *Gavin McDonald*
> Systems Administrator
> ASF Infrastructure Team
--
Matt Sicker <boa...@gmail.com>
