Reached out to Clay Johnson for help, and created an ASF Infra ticket to track this issue https://issues.apache.org/jira/browse/INFRA-27083 -- Sanjay
On Fri, Jun 27, 2025 at 2:03 PM sanjay dutt <sanjaydutt.unoffic...@gmail.com> wrote: > But at the same time, this one PR > <https://github.com/apache/solr/pull/3053> is able to push build scan via > github-runner which is strange because it's not allowed. And it only > started happening from the 11th Jun. And that's the last time the main > branch along with some other changes merged into this PR. > > https://github.com/apache/solr/actions/runs/15717950284 > Even now if you re-run the workflow you will see "Publishing build > scan..." in logs. > > > https://develocity.apache.org/scans?list.sortColumn=publicHostname&list.sortOrder=asc&search.relativeStartTime=P28D&search.rootProjectNames=solr-root&search.timeZoneId=Asia%2FCalcutta > > > > On Fri, Jun 27, 2025 at 12:48 PM sanjay dutt < > sanjaydutt.unoffic...@gmail.com> wrote: > >> Could be the access token (not valid anymore), we may need extra logging >> to confirm that. >> >> On Fri, Jun 27, 2025 at 11:28 AM David Smiley <dsmi...@apache.org> wrote: >> >>> Our Gradle build scans were reliably being published thru June 12th, then >>> more or less stopped: >>> >>> >>> https://develocity.apache.org/scans?search.relativeStartTime=P28D&search.rootProjectNames=solr-root >>> >>> Anyone know why? >>> >>> ~ David Smiley >>> Apache Lucene/Solr Search Developer >>> http://www.linkedin.com/in/davidwsmiley >>> >>
