[
https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798541#comment-16798541
]
stack commented on HBASE-22052:
-------------------------------
Its the publishhtml jenkins plugin. It looks like it copies files. Its gone mad
when this patch is in place.
https://wiki.jenkins.io/display/JENKINS/HTML+Publisher+Plugin
{code}
21:28:45 [htmlpublisher] Archiving HTML reports...
21:28:45 [htmlpublisher] Archiving at BUILD level
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_branch-2.1@2/output-jdk8-hadoop2
to /x1/jenkins/jenkins-home/jobs/HBase
Nightly/branches/branch-2-1.nhtl1j/builds/976/htmlreports/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29
....
Cancelling nested steps due to timeout
02:43:43 Sending interrupt signal to process
{code}
See long time spread in above.
How would I run what this publishHTML is trying outside jenkins so can repro?
I could try removing the second archive in the below...
stash name: 'general-result', includes: "${OUTPUT_DIR_RELATIVE}/commentfile"
// Has to be relative to WORKSPACE.
archive "${env.OUTPUT_DIR_RELATIVE}/*"
archive "${env.OUTPUT_DIR_RELATIVE}/**/*"
... see if we end up doing less work.
Would be nice to see what it thinks its doing though.
> pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove
> redunant version specifications
> -----------------------------------------------------------------------------------------------------------
>
> Key: HBASE-22052
> URL: https://issues.apache.org/jira/browse/HBASE-22052
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.2.0, 2.0.5, 2.1.4
>
> Attachments: HBASE-22052.branch-2.0.001.patch,
> HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch,
> HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch,
> HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch,
> HBASE-22052.branch-2.2.001.patch, HBASE-22052.branch-2.2.002.patch
>
>
> Working on HBASE-22029, where we fail compile of hbase-it module four hours
> into an RC build, it looks like transitive include of jersey-core is the
> culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue
> is about having hadoop2 profile and hadoop3 profiles match around jersey-core
> treatment. Some miscellaneous cleanups are also done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)