You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "shane knapp (JIRA)" <ji...@apache.org> on 2019/01/07 22:48:00 UTC
[jira] [Updated] (SPARK-26565) modify
dev/create-release/release-build.sh to let jenkins build packages w/o
publishing
[ https://issues.apache.org/jira/browse/SPARK-26565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
shane knapp updated SPARK-26565:
--------------------------------
Description:
about a year+ ago, we stopped publishing releases directly from jenkins...
this means that the spark-\{branch}-packaging builds are failing due to gpg signing failures, and i would like to update these builds to *just* perform packaging.
example:
[https://amplab.cs.berkeley.edu/jenkins/view/Spark%20Packaging/job/spark-master-package/2183/console]
i propose to change dev/create-release/release-build.sh...
when the script is called w/the 'package' option, remove ALL of the following bits:
1) gpg signing of the source tarball (lines 184-187)
2) gpg signing of the sparkR dist (lines 243-248)
3) gpg signing of the python dist (lines 256-261)
4) gpg signing of the regular binary dist (lines 264-271)
5) the svn push of the signed dists (lines 317-332)
PR coming soon.
was:
about a year+ ago, we stopped publishing releases directly from jenkins...
this means that the spark-\{branch}-packaging builds are failing due to gpg signing failures, and i would like to update these builds to *just* perform packaging.
example:
[https://amplab.cs.berkeley.edu/jenkins/view/Spark%20Packaging/job/spark-master-package/2183/console]
i propose to change dev/create-release/release-build.sh...
when the script is called w/the 'package' option, remove ALL of the following bits:
1) gpg signing of the source tarball (lines 184-187)
2) gpg signing of the sparkR dist (lines 243-248)
3) gpg signing of the python dist (lines 256-261)
4) gpg signing of the regular binary dist (lines 264-271)
5) the svn push of the signed dists (lines 317-332)
obligatory images:
!image-2019-01-07-14-46-20-907.png!!image-2019-01-07-14-46-40-836.png!
> modify dev/create-release/release-build.sh to let jenkins build packages w/o publishing
> ---------------------------------------------------------------------------------------
>
> Key: SPARK-26565
> URL: https://issues.apache.org/jira/browse/SPARK-26565
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.2.3, 2.3.3, 2.4.1, 3.0.0
> Reporter: shane knapp
> Assignee: shane knapp
> Priority: Major
> Attachments: fine.png
>
>
> about a year+ ago, we stopped publishing releases directly from jenkins...
> this means that the spark-\{branch}-packaging builds are failing due to gpg signing failures, and i would like to update these builds to *just* perform packaging.
> example:
> [https://amplab.cs.berkeley.edu/jenkins/view/Spark%20Packaging/job/spark-master-package/2183/console]
> i propose to change dev/create-release/release-build.sh...
> when the script is called w/the 'package' option, remove ALL of the following bits:
> 1) gpg signing of the source tarball (lines 184-187)
> 2) gpg signing of the sparkR dist (lines 243-248)
> 3) gpg signing of the python dist (lines 256-261)
> 4) gpg signing of the regular binary dist (lines 264-271)
> 5) the svn push of the signed dists (lines 317-332)
>
> PR coming soon.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org