>
> 1) https://issues.apache.org/jira/browse/SPARK-26565
> 2) create world-wide campaign to stop bash scripting
>
3) re-create these builds w/o calling release-build.sh at all (preferred)
gt;> *From:* shane knapp
>> *Sent:* Sunday, January 6, 2019 11:38 AM
>> *To:* Felix Cheung
>> *Cc:* Dongjoon Hyun; Wenchen Fan; dev
>> *Subject:* Re: Spark Packaging Jenkins
>>
>> noted. i like the idea of building (but not signing) the release and
>>
:42 AM Felix Cheung
wrote:
> Awesome Shane!
>
>
> --
> *From:* shane knapp
> *Sent:* Sunday, January 6, 2019 11:38 AM
> *To:* Felix Cheung
> *Cc:* Dongjoon Hyun; Wenchen Fan; dev
> *Subject:* Re: Spark Packaging Jenkins
>
> noted. i l
Awesome Shane!
From: shane knapp
Sent: Sunday, January 6, 2019 11:38 AM
To: Felix Cheung
Cc: Dongjoon Hyun; Wenchen Fan; dev
Subject: Re: Spark Packaging Jenkins
noted. i like the idea of building (but not signing) the release and will
update the job(s) this
--
> *From:* Felix Cheung
> *Sent:* Sunday, January 6, 2019 11:17 AM
> *To:* Dongjoon Hyun; Wenchen Fan
> *Cc:* dev; shane knapp
> *Subject:* Re: Spark Packaging Jenkins
>
> The release process doc should have been updated on this - as mentioned we
> do not use Jenkins
https://spark.apache.org/release-process.html
Look for do-release-docker.sh script
From: Felix Cheung
Sent: Sunday, January 6, 2019 11:17 AM
To: Dongjoon Hyun; Wenchen Fan
Cc: dev; shane knapp
Subject: Re: Spark Packaging Jenkins
The release process doc should
)
From: Dongjoon Hyun
Sent: Saturday, January 5, 2019 9:46 PM
To: Wenchen Fan
Cc: dev; shane knapp
Subject: Re: Spark Packaging Jenkins
Thank you, Wenchen.
I see. I'll update the doc and proceed to the next step manually as you advise.
And it seems that we can
Thank you, Wenchen.
I see. I'll update the doc and proceed to the next step manually as you
advise. And it seems that we can stop the outdated Jenkins jobs, too.
Bests,
Dongjoon.
On Sat, Jan 5, 2019 at 20:15 Wenchen Fan wrote:
> IIRC there was a change to the release process: we stop using the
IIRC there was a change to the release process: we stop using the shared
gpg key on Jenkins, but use the personal key of the release manager. I'm
not sure Jenkins can help testing package anymore.
BTW release manager needs to run the packaging script by himself. If there
is a problem, the release
Hi, All.
It turns out that `gpg signing` is the next huddle in Spark Packaging
Jenkins.
Since 2.4.0 release, is there something changed in our Jenkins machine?
gpg: skipped
"/home/jenkins/workspace/spark-master-package/spark-utils/new-release-scripts/jenkins/jenkins-credentials-JEtz0nyn/gpg
https://issues.apache.org/jira/browse/SPARK-26537
On Fri, Jan 4, 2019 at 11:31 AM shane knapp wrote:
> this may push in to early next week... these builds were set up before my
> time, and i'm currently unraveling how they all work before pushing a
> commit to fix stuff.
>
> nothing like some c
this may push in to early next week... these builds were set up before my
time, and i'm currently unraveling how they all work before pushing a
commit to fix stuff.
nothing like some code archaeology to make my friday more exciting! :)
shane
On Fri, Jan 4, 2019 at 11:08 AM Dongjoon Hyun
wrote
Thank you, Shane!
Bests,
Dongjoon.
On Fri, Jan 4, 2019 at 10:50 AM shane knapp wrote:
> yeah, i'll get on that today. thanks for the heads up.
>
> On Fri, Jan 4, 2019 at 10:46 AM Dongjoon Hyun
> wrote:
>
>> Hi, All
>>
>> As a part of release process, we need to check Packaging/Compile/Test
>>
yeah, i'll get on that today. thanks for the heads up.
On Fri, Jan 4, 2019 at 10:46 AM Dongjoon Hyun
wrote:
> Hi, All
>
> As a part of release process, we need to check Packaging/Compile/Test
> Jenkins status.
>
> http://spark.apache.org/release-process.html
>
> 1. Spark Packaging:
> https://am
14 matches
Mail list logo
