[
https://issues.apache.org/jira/browse/YETUS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822687#comment-15822687
]
Suraj Acharya commented on YETUS-474:
-------------------------------------
[~busbey] I used yesterdays outage to check the behaviour.
I see this
{code}
sacharya@sacharya-MBP:~/repos/yetus$ ./build.sh --release
working on version '0.6.0-SNAPSHOT'
generating release docs.
JSON returned ValueError. Unable to continue. No JSON object could be decoded
Traceback (most recent call last):
File "release-doc-maker/releasedocmaker.py", line 910, in <module>
main()
File "release-doc-maker/releasedocmaker.py", line 751, in main
jlist = sorted(JiraIter(vstr, projects))
File "release-doc-maker/releasedocmaker.py", line 401, in __init__
self.field_id_map = JiraIter.collect_fields()
File "release-doc-maker/releasedocmaker.py", line 317, in collect_fields
for part in data:
UnboundLocalError: local variable 'data' referenced before assignment
{code}
I believe this is an error. And it should fail the releasedoc process but try
and continue process.
Somewhat along the lines :
{code}
sacharya@sacharya-MBP:~/repos/yetus$ ./build.sh --release
working on version '0.6.0-SNAPSHOT'
generating release docs.
JSON returned ValueError. Unable to continue with releasedocmaker.py No JSON
object could be decoded
mv: target/0.6.0/RELEASENOTES.0.6.0.md: No such file or directory
mv: target/0.6.0/CHANGES.0.6.0.md: No such file or directory
hard reseting working directory.
HEAD is now at d3e11a8 fix error message on unable to connect to JIRA
creating source tarball at '/Users/sacharya/repos/yetus/target/'
running maven builds for java components
[INFO] Scanning for projects...
[INFO]
{code}
# Do you think this is okay?
# is the change in the scope of this jira or do you want me to spawn a new one?
> 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: 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)
