[
https://issues.apache.org/jira/browse/LUCENE-10174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl reopened LUCENE-10174:
----------------------------------
Re-opening to enhance the 'assembleRelease' step, to avoid OOM in gpg-agent.
Will split in two commands and skip 'clean':
{code:java}
gradlew assembleRelease ...
gradlew assembleRelease -Psign --max-workers 1 ... {code}
> Update buildAndPushRelease.py for new gradle build
> --------------------------------------------------
>
> Key: LUCENE-10174
> URL: https://issues.apache.org/jira/browse/LUCENE-10174
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: main (9.0)
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> With LUCENE-9488 and LUCENE-10173 the gradle build was polished to properly
> build source and binary artifacts, and sign those using either gpg tool or a
> built-in java-based signing plugin. See
> [https://github.com/apache/lucene/blob/main/help/publishing.txt]
> This jira will update {{buildAndPushRelease.py}} script to use the correct
> build parameters. It will also add cmdline args to choose between gpg and
> built-in (gpg default), and to supply the location of {{gpgHome}} if you do
> not use gpg. We'll also add an option to NOT prompt for passphrase in the
> python script, which will fallback to defaults (gpg-agent, env.vars or
> gradle.properties).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
