[
https://issues.apache.org/jira/browse/YETUS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830101#comment-15830101
]
Sean Busbey commented on YETUS-474:
-----------------------------------
I'm fine with either fail-early or fail-at-end so long as we have an error code
at the end. Bonus points for better error messages than what we had at the
beginning. e.g. "I couldn't talk to JIRA", "I couldn't find that version in
JIRA" rather than stack traces. Personally, I don't think "the issue exists but
there are no issues assigned to it" should be an error condition.
How about a flag --fail-at-end that keeps going when there are problems?
> master build broken
> -------------------
>
> Key: YETUS-474
> URL: https://issues.apache.org/jira/browse/YETUS-474
> Project: Yetus
> Issue Type: Bug
> Components: build
> Affects Versions: 0.5.0
> Reporter: Sean Busbey
> Assignee: Suraj Acharya
> Priority: Blocker
> Fix For: 0.5.0
>
> Attachments: Bump_patch_to_0.99.98.patch,
> Bump_patch_to_0.99.99.patch, YETUS-474-01.patch, YETUS-474-02.patch,
> YETUS-474.patch
>
>
> {code}
> ./build.sh --release
> working on version '0.5.0-SNAPSHOT'
> generating release docs.
> There is no issue which has the specified version: 0.5.0
> mv: rename target/0.5.0/RELEASENOTES.0.5.0.md to target/RELEASENOTES.md: No
> such file or directory
> {code}
> I'm guessing it's the version bump and an edge case in handling RDM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
