[
https://issues.apache.org/jira/browse/LUCENE-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433424#comment-17433424
]
Jan Høydahl edited comment on LUCENE-9809 at 10/24/21, 11:16 AM:
-----------------------------------------------------------------
I'll try the env.var approach for pw. If folks are OK with pulling the maven
artifacts from git repo's build folders instead of using exactlyt the same
folder that was uploaded and voted upon, then this should be ok. I guess the
theoretical risk is if RM gets confused and somehow invokes another build and
uploads another commit hash to maven. There will be several days in between the
first build, voting and the staging to artifactory. But as long as the
releaseWizard is used, which has a dedicated git clone, this should not be a
real risk anyway.
was (Author: janhoy):
I'll try the env.var approach for pw. If folks are OK with pulling the maven
artifacts from git repo's build folders instead of using exactlyt the same
folder that was uploaded and voted upon, then this should be ok. I guess the
theoretical risk is if RM gets confused and somehow invokes another build and
uploads another commit hash to maven. As long as the releaseWizard is used,
which has a dedicated git clone this should not be a real risk anyway.
> Adapt Release Wizard to only release Lucene
> -------------------------------------------
>
> Key: LUCENE-9809
> URL: https://issues.apache.org/jira/browse/LUCENE-9809
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: main (9.0)
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
--
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
