[
https://issues.apache.org/jira/browse/COUCHDB-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853160#comment-13853160
]
Eli Stevens commented on COUCHDB-2007:
--------------------------------------
I'm not 100% certain that I fully understand what parts of the final text came
from which subkey of _info, but I think that you could do something like this
(starting at line 55):
if _info.get('LOCAL_VERSION_RELEASE') == '.%revision%':
release += '-dev'
elif _info.get('LOCAL_VERSION_RELEASE'):
if _info['LOCAL_VERSION_STAGE'].find('jenkins') > 0:
release += '.' + _info['LOCAL_VERSION_RELEASE'][-9:]
else:
release += _info['LOCAL_VERSION_STAGE'] + _info['LOCAL_VERSION_RELEASE']
> Building docs under CI fails
> ----------------------------
>
> Key: COUCHDB-2007
> URL: https://issues.apache.org/jira/browse/COUCHDB-2007
> Project: CouchDB
> Issue Type: Bug
> Components: Build System, Documentation
> Reporter: Jan Lehnardt
>
> Building the PDF version of the docs fails under CI due to release name:
> The CouchDB.tex file that gets generated includes a line that looks like this:
> \release{1.6.0+build.jenkins-ERLANG_VERSION=R14B04,label=Mac-OS-10-8-2-832-76-g2996574}
> It isn’t clear whether this is plain to long or whether there are invalid
> characters in there.
> I don’t quite understand how docs inherit the release name, so I need to ask
> for help here.
> The release name otherwise is valid, as it encodes the different build matrix
> settings.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
