cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Brockmeier (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2007) Release Notes failing to build on jenkins.cs.o
Date Thu, 11 Apr 2013 14:29:16 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628971#comment-13628971
] 

Joe Brockmeier commented on CLOUDSTACK-2007:
--------------------------------------------

Have looked into this, built the release notes on two different machines (F17 and F18) with
slightly different versions of Publican. Release notes build successfully on both. My guess
is that it's the common_content that's the problem. I changed it slightly to incorporate Feedback.xml
and updated the publican-cloudstack package as well (commit 7b77aff4539a6ba3bd09f245a665bb84504d2ee4)
which required a rebuild of the RPM for my system. Perhaps that's not automatically updated
on Jenkins?
                
> Release Notes failing to build on jenkins.cs.o
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-2007
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2007
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>    Affects Versions: 4.1.0
>         Environment: http://jenkins.cloudstack.org/job/docs-4.1-releasenotes/372/console
>            Reporter: Chip Childers
>            Assignee: Joe Brockmeier
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> The relevant log is here:
> Beginning work on en-US
> Release_Notes.xml:32: validity error : IDREF attribute linkend references an unknown
ID "feedback"
> Validation failed: 
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Finished: FAILURE

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message