dweiss edited a comment on pull request #391: URL: https://github.com/apache/lucene/pull/391#issuecomment-946437537
> Or the script could run the main build in parallel and then run just the signing serially. Sure. Split in two - I also suggested removing "clean" because rebuilding from any state should always yield correct task outputs (this isn't ant where you have to clean leftovers over and over). So this sequence: ``` gradlew assembleRelease gradlew assembleRelease -Psign --max-workers 1 ``` will rerun some tasks but will sign in a single worker. We could also order all signing tasks within gradle code (so that they can't run in parallel, no matter what) but it seems like an unnecessary complexity given the infrequent use of the script. I'd rather do the above (or fall back to just specifying --max-workers X, where X is small-ish for gpg signing). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
