Thanks for forwarding to the list Shawn. I do know what they’re talking about: the “description” for a build of those jobs is supposed to be the issue number that a patch is pulled from in order to review the patch. The job is configured to pull this information from the job’s build log, but since the build has other issues in it, doing this is apparently unreliable.
I’ve switched the configuration for both jobs to instead use the $ISSUE_NUM param that’s passed into the build; we’ll see if that works. -- Steve www.lucidworks.com > On Jul 3, 2018, at 3:04 PM, Shawn Heisey <apa...@elyograg.org> wrote: > > In the middle of the night in my timezone, on the #lucene-dev IRC channel, > this report came in: > > 02:48 < gezapeti> Hey! I've noticed that the pre-commit jobs for both Lucene > and Solr are setting incorrect descriptions sometimes: > 02:48 < gezapeti> https://builds.apache.org/job/PreCommit-lucene-Build and > https://builds.apache.org/job/PreCommit-SOLR-Build/ > 02:50 < gezapeti> The problem is that they are getting the description from > the > log via regular expression and that is not reliable enough. > They could simply use the issue number in the parameter of > the job to set the description > > I don't understand what they're saying. They left the channel and haven't > come back, so I can't ask them for a clarification. > > Is there enough information in that report for someone else to know what the > problem is? > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
