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
+1
Reynold Xin 于2019年1月4日周五 上午9:28写道：
> Committers,
>
> When you merge tickets fixing correctness bugs, please make sure you tag
> the tickets with "correctness" label. I've found multiple tickets today that
> didn't do that.
>
>
> On Fri, Aug 17, 2018 at 7:11 AM, Tom Graves
> wrote:
>
>> Since
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
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
