[
https://issues.apache.org/jira/browse/SOLR-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497306#comment-17497306
]
Jan Høydahl commented on SOLR-16041:
------------------------------------
Yea, guess we could easily generate a test GPG key and put its private key on
Jenkins. But I don't want to put that key on our official KEYS file, but the
smoketester already has
[--local-keys|https://github.com/apache/solr/blob/main/dev-tools/scripts/smokeTestRelease.py#L1016]
support, so the Jenkins job could feed the test key to smoke tester and it
would be happy I suppose :)
> 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
