To whoever set this up:
There was a job config problem where the Jenkins branch parameter wasn’t passed
to Yetus. Therefore both of these reports have been against trunk. I’ve fixed
this job (as well as the other jobs) to honor that parameter. I’ve kicked off
a new run with these changes.
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/2/
[Oct 20, 2017 9:27:59 PM] (stevel) HADOOP-14942. DistCp#cleanup() should check
whether jobFS is null.
[Oct 21, 2017 12:19:29 AM] (subru) YARN-6871. Add additional deSelects params in
-1 overall
The
New Revision...
This revision acknowledges the reality that we often have multiple phases
of feature lifecycle and that we need to account for each phase.
It has also been made more generic.
I have created a Tech Preview Security Audit list and a GA Readiness
Security Audit list.
I've also
Hi Marton -
I don't think there is any denying that it would be great to have such
documentation for all of those reasons.
If it is a natural extension of getting the checklist information as an
assertion of security state when merging then we can certainly include it.
I think that backfilling
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/563/
[Oct 19, 2017 6:51:24 AM] (zhz) HDFS-12502. nntop should support a category
based on
[Oct 19, 2017 1:02:13 PM] (weichiu) HADOOP-14880. [KMS] Document missing
KMS client side configs.
[Oct 19, 2017 1:17:59
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/1/
No changes
-1 overall
The following subsystems voted -1:
asflicense unit
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint
On 10/21/2017 02:41 AM, larry mccay wrote:
"We might want to start a security section for Hadoop wiki for each of the
services and components.
This helps to track what has been completed."
Do you mean to keep the audit checklist for each service and component
there?
Interesting idea, I
