spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Cheung (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SPARK-22522) Convert to apache-release to publish Maven artifacts
Date Wed, 15 Nov 2017 18:34:00 GMT

    [ https://issues.apache.org/jira/browse/SPARK-22522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253918#comment-16253918
] 

Felix Cheung edited comment on SPARK-22522 at 11/15/17 6:33 PM:
----------------------------------------------------------------

sorry about the confusion - to clarify, the repo is the same in the existing process we have,
this JIRA is only proposing a tooling change, not a destination change. In fact, during the
officially documented ASF release process, once a release is voted it can be promoted from
repository.apache.org which gets the maven artifacts to maven central (repo1.maven.org) automatically
(again, same as today)

http://www.apache.org/dev/publishing-maven-artifacts.html#promote
"Congratulations, your vote was successful. The last step is to promote the artifacts to the
release repository where they will get picked up by Central."


was (Author: felixcheung):
sorry about the confusion - to clarify, the repo is the same in the existing process we have,
this JIRA is only proposing a tooling change, not a destination change. In fact, during the
officially documented ASF release process, once a release is voted it can be promoted from
repository.apache.org which gets the maven artifacts to maven central (repo1.maven.org) automatically
(again, same as today)

http://www.apache.org/dev/publishing-maven-artifacts.html#promote
Congratulations, your vote was successful. The last step is to promote the artifacts to the
release repository where they will get picked up by Central.

> Convert to apache-release to publish Maven artifacts 
> -----------------------------------------------------
>
>                 Key: SPARK-22522
>                 URL: https://issues.apache.org/jira/browse/SPARK-22522
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 2.3.0
>            Reporter: Felix Cheung
>            Priority: Minor
>
> see http://www.apache.org/dev/publishing-maven-artifacts.html
> to publish to Nexus/repository.apache.org which can be promoted to maven central (when
release).
> this is the same repo we are publishing to today. this JIRA is only tracking the tooling
changes.
> ...at the very least we need to revisit all the calls to curl (and/or gpg) in the release-build.sh
for the publish-release path - seems like some errors are ignored (running into that myself)
and it would be very easy to miss publishing one or more or all files.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message