[
https://issues.apache.org/jira/browse/SOLR-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497349#comment-17497349
]
Jan Høydahl commented on SOLR-16041:
------------------------------------
The test Jenkins job seems to succeed now:
[https://ci-builds.apache.org/job/Solr/job/Solr-Smoketest-9.0/8/console]
Got some issues with corrupt gradle cache, so I checked the box for using a
GRADLE_HOME in the job work-dir, but that makes the git checkout "dirty" with a
huge warning log. Ideally we'd place GRADLE_HOME in some other location not
inside git checkout but not sure where that could be, if we want the cache to
survive until the next build. [~uschindler] any ideas?
Once the PR is merged to branch_9_0, we can switch the Jenkins job to checkout
the official branch and send failure logs to builds@solr list.
> Prepare a Jenkins job that runs smoke tester on 9.0
> ---------------------------------------------------
>
> Key: SOLR-16041
> URL: https://issues.apache.org/jira/browse/SOLR-16041
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The old ant build had a [target
> "nightly-smoke"|https://github.com/apache/lucene-solr/blob/branch_8_11/build.xml#L420:L466]
> that would build the release and run smoketester on it. This was run nightly
> before each release in Jenkins to catch issues early -
> [https://ci-builds.apache.org/job/Lucene/job/Lucene-Solr-SmokeRelease-8.11/]
> Could be useful to have a similar mechanism now.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
