I suspect nobody was reading the conversation Eric and I were having on bui...@solr.apache.org; maybe because nobody looks there. Maybe we should never do that and have it be build-only messages. Nevertheless all active Solr committers should subscribe to that list if you haven't (it's a basic project hygiene thing -- monitor builds). So I am copy-pasting to our dev list.
I will very soon take action to DELETE (not disable) the Jenkins CI builds for 8.9, 8.10 (not 8.11), 9.0, 9.1, 9.2, 9.3, 9.4, 9.5 -- there are more than one jobs for some of these releases. Our ref guide instructions actually indicate to do this: https://cwiki.apache.org/confluence/display/SOLR/JenkinsReleaseBuilds+-+Solr so I won't wait for someone to tell me not to follow these instructions ;-). Yet release after release, nobody has done this despite this being a release-wizard step (AFAICT). What's broken in our process here folks? (Don't ask me, I only did a *patch* release once which has no step to do here.) ~ David ---------- Forwarded message --------- From: David Smiley <dsmi...@apache.org> Date: Fri, May 31, 2024 at 11:14 AM Subject: Re: [JENKINS] Solr » Solr-Smoketest-9.4 - Build # 284 - Still Failing! To: <dev@solr.apache.org>, Gus Heck <gus.h...@gmail.com>, <gerlowsk...@gmail.com> Cc: Eric Pugh <ep...@o19s.com>, <bui...@solr.apache.org> I don't think we need release jobs for older releases -- older than the latest. Our release process refers RMs to visit https://cwiki.apache.org/confluence/display/SOLR/JenkinsReleaseBuilds+-+Solr which first instructs to remove old jobs. I think this only happens for major/minor releases but not patch releases. https://ci-builds.apache.org/job/Solr/ Gus, you did 9.6.0. Did the release wizard direct you to https://cwiki.apache.org/confluence/display/SOLR/JenkinsReleaseBuilds+-+Solr ? Jason, you did 9.5.0. Same question. On Fri, May 31, 2024 at 8:45 AM Eric Pugh <ep...@opensourceconnections.com> wrote: > > At first blush, running locally things are fine…. > > Is there any chance that the various Jenkins jobs could be > sharing/communicating across each other where a bad running Solr instance in > main is still there and causing others to fail? I ask because why would 9.1, > 9.3, 9.4, 9.5, 9.6 all start failing between 3 days and 10 hours ago and 2 > days 9 hours ago? I get changes on 9.6, but not on the previous versions. > > > > > > > > On May 31, 2024, at 8:19 AM, Eric Pugh <ep...@opensourceconnections.com> > > wrote: > > > > Looks like it’s failing in 9x too. I’ll check out what’s going on. > > > > What is our policy for having older tests…. Do we actually need to keep > > around the checks for 9.0 through 9.5? If we found a major issue in a > > previous release like 9.2, would we just ship an updated 9.x, so it would > > be a 9.6.2 or a 9.7? > > > > Wondering if having fewer Jenkins jobs would make it easier to keep tabs on > > them? > > > > > >> On May 31, 2024, at 1:33 AM, David Smiley <dsmi...@apache.org> wrote: > >> > >> Eric, maybe you were working on authentication matters and could thus > >> guess as to why some smoke tests fail here? This one is for 9.4 but > >> there's another for 9.6 > >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
