[
https://issues.apache.org/jira/browse/YETUS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561366#comment-16561366
]
Yetus QA commented on YETUS-643:
--------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
19s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
1s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:red}-1{color} | {color:red} shelldocs {color} | {color:red} 0m
0s{color} | {color:red} The patch generated 2 new + 20 unchanged - 4 fixed = 22
total (was 24) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
0s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 26s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/yetus:6c9c3d9 |
| JIRA Issue | YETUS-643 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12933535/YETUS-643.001.patch |
| Optional Tests | shellcheck shelldocs |
| uname | Linux 75b6c494086c 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14
08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | nobuild |
| git revision | master / e37f763 |
| shellcheck | v0.4.6 |
| shelldocs |
https://builds.apache.org/job/PreCommit-YETUS-Build/755/artifact/patchprocess/diff-patch-shelldocs.txt
|
| Max. process+thread count | 10 (vs. ulimit of 1000) |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-YETUS-Build/755/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> default custom maven repo should use workspace when in jenkins mode
> -------------------------------------------------------------------
>
> Key: YETUS-643
> URL: https://issues.apache.org/jira/browse/YETUS-643
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Critical
> Fix For: 0.8.0
>
> Attachments: YETUS-643.00.patch, YETUS-643.001.patch
>
>
> Instead of using something off of home, maybe it would make more sense to use
> the workspace directory as the maven repo cache location when custom maven
> repos are used under Jenkins. This would give a lot more exposure to what is
> going on that normally isn't seen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
