You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2020/10/02 13:49:00 UTC

[jira] [Commented] (PHOENIX-6173) Archive test artifacts in Jenkins multibranch postcommit job

    [ https://issues.apache.org/jira/browse/PHOENIX-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206194#comment-17206194 ] 

Istvan Toth commented on PHOENIX-6173:
--------------------------------------

This is isn't as straightforward as I'd hoped. 
archiveArtifacts will simply overwrite the artifacts from each branch.

Either the branches will need to be checked into and run from their own subdirectory,

we need to copy the test results to s tmp directory per banch before archiving,

or we need to look into using Yetus for this as well.

> Archive test artifacts in Jenkins multibranch postcommit job
> ------------------------------------------------------------
>
>                 Key: PHOENIX-6173
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6173
>             Project: Phoenix
>          Issue Type: Improvement
>          Components: core
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> The multibranch Jenkins postcommit jobs process the test output, but not the the other files generated during the test.
> These files are often needed for analysis
> Add these files as archived artifacts to the build.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)