[
https://issues.apache.org/jira/browse/METRON-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496642#comment-16496642
]
ASF GitHub Bot commented on METRON-1590:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1041
I would say that the scripts we have wrt PR's and RC's and Commits should
be as common as possible. With the goal that they actually share code down the
line. So I would say that the configuration and preference persistence for
working dir and other options be done as nick's scripts
> validate-jira-for-release script checks out project into current directory
> not workdir
> --------------------------------------------------------------------------------------
>
> Key: METRON-1590
> URL: https://issues.apache.org/jira/browse/METRON-1590
> Project: Metron
> Issue Type: Bug
> Reporter: Justin Leet
> Assignee: Justin Leet
> Priority: Major
>
> validate-jira-for-release at
> [https://github.com/apache/metron/blob/master/dev-utilities/release-utils/validate-jira-for-release#L165-L168]
> The clone checks out into current dir, so `$WORKDIR/metron-$VERSION` never
> gets created. However, since the `cd` fails, we stay in the working dir, and
> the script happens to work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
