[
https://issues.apache.org/jira/browse/HADOOP-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated HADOOP-11746:
--------------------------------------
Attachment: HADOOP-11746-17.patch
After sleeping on it, I think it's better to be safe than sorry in case of
problems. A few extra lines for extra paranoia...
-17:
* During re-exec mode, make sure jenkins reports the console in the "switching"
message in case something goes wrong.
* In reset repo mode, always force checkout to trunk after cleaning the repo
area. This might not actually matter in the grand scheme of things, but if
something goes haywire in the middle this should provide some level of safety
to get us back to a clean slate.
* Don't switch to any branches that match: branch-0, branch-1, branch-2.[0-7].
It should be noted that currently the code to find a branch won't properly
detect minor or micro version branches anyway, so the branch-2 minor version
lockout is just in case someone fixes that bug later. ;)
It should be safe to commit this to branch-2 and have the system come back to
trunk for 'real' patches.
> rewrite test-patch.sh
> ---------------------
>
> Key: HADOOP-11746
> URL: https://issues.apache.org/jira/browse/HADOOP-11746
> Project: Hadoop Common
> Issue Type: Test
> Components: build, test
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Attachments: HADOOP-11746-00.patch, HADOOP-11746-01.patch,
> HADOOP-11746-02.patch, HADOOP-11746-03.patch, HADOOP-11746-04.patch,
> HADOOP-11746-05.patch, HADOOP-11746-06.patch, HADOOP-11746-07.patch,
> HADOOP-11746-09.patch, HADOOP-11746-10.patch, HADOOP-11746-11.patch,
> HADOOP-11746-12.patch, HADOOP-11746-13.patch, HADOOP-11746-14.patch,
> HADOOP-11746-15.patch, HADOOP-11746-16.patch, HADOOP-11746-17.patch
>
>
> This code is bad and you should feel bad.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
