All right - thanks for reviewing the plan guys!
I've updated the jobs in Jenkins, and after sorting out a
JDK21-related hiccup or two, everything looks to be healthy. (Or, as
healthy as our test runs typically are *sigh*)
I've got a PR to update a few references to the Jenkins jobs in our
READMe
I had no idea how deep our testing went!
All makes sense!
Sent from my iPhone
> On Oct 24, 2024, at 10:16 PM, David Smiley wrote:
>
> Sounds very good Jason; thanks for the summary and execution of the plan.
>
>> On Thu, Oct 24, 2024 at 3:56 PM Jason Gerlowski
>> wrote:
>>
>> My original w
Sounds very good Jason; thanks for the summary and execution of the plan.
On Thu, Oct 24, 2024 at 3:56 PM Jason Gerlowski
wrote:
> My original writeup here missed one important detail that Uwe recently
> clarified for me on the lucene lists. [1]. The constant presence of
> some Solr jobs in the
My original writeup here missed one important detail that Uwe recently
clarified for me on the lucene lists. [1]. The constant presence of
some Solr jobs in the Jenkins build-queue isn't accidental, it's by
design(!) We've historically triggered some jobs "hourly" instead of
"nightly" in order to
+1. cleanups always good. Also, do we need to keep the smoke test 9.7 running
if we don’t think there will be a 9.7.1 release?
Jan Høydahl
> On 15 Oct 2024, at 14:32, David Smiley wrote:
>
> +1 Sure; seems like a simple solution.
>
>> On Tue, Oct 15, 2024 at 7:27 AM Jason Gerlowski
>> wrote
+1 Sure; seems like a simple solution.
On Tue, Oct 15, 2024 at 7:27 AM Jason Gerlowski
wrote:
> Hi all,
>
> While cleaning up our Jenkins agents, I noticed that we trigger a lot
> of long-running (> 1 hr) jobs on a nightly basis. Each family of jobs
> differs slightly in the gradle task it runs
