You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2018/08/02 16:09:00 UTC
[jira] [Resolved] (YETUS-579) record job number in jenkins mode
[ https://issues.apache.org/jira/browse/YETUS-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved YETUS-579.
------------------------------------
Resolution: Fixed
This is the wrong way to solve this problem. Closing as won't fix.
> record job number in jenkins mode
> ---------------------------------
>
> Key: YETUS-579
> URL: https://issues.apache.org/jira/browse/YETUS-579
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Reporter: Allen Wittenauer
> Priority: Trivial
>
> While looking at why a jenkins job failed, a quick look at the system found a precommit-hbase job that I believe had been "lost" by Jenkins running on that node. It'd be useful to pass the jenkins job info on the command line during a docker re-exec so that a ps will show where it came from to help debug issues like this one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)