You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2014/01/28 00:55:41 UTC
[jira] [Created] (INFRA-7243) Buildbot job to publish quid trunk
documentation
Keith Wall created INFRA-7243:
---------------------------------
Summary: Buildbot job to publish quid trunk documentation
Key: INFRA-7243
URL: https://issues.apache.org/jira/browse/INFRA-7243
Project: Infrastructure
Issue Type: Task
Components: Buildbot
Environment: Buildbot Ubuntu 10.4.x (LTS)
Reporter: Keith Wall
Hello,
(re. http://qpid.2158936.n2.nabble.com/What-is-the-intended-process-to-publish-trunk-docbooks-to-the-Qpid-website-td7602146.html)
I'd like to request a new buildbot job to publish Qpid's trunk documentation. The job needs to run on an ubuntu slave. It needs to perform an svn updates (after an initial checkout), run a makefile, then finally commit the result back to svn to publish the result. Is this within buildbot's capabilities?
Is there a mechanism to to set the job first *WITHOUT* the final commit step, so that we may review the job logs and confirm the output is correct.
I list below:
1) ubuntu package dependencies
2) svn + other shell commands
Can you let me know if more information is required?
Dependencies
============
sudo apt-get install cmake doxygen fop graphviz make python-pygments epydoc-doc python-yaml xsltproc
Job commands
============
1) svn checkout/update http://svn.apache.org/repos/asf/qpid/trunk/qpid qpid
then if there are new revisions:
2) svn checkout/update http://svn.apache.org/repos/asf/qpid/site site
3) cd /path/to/site
4) make clean gen-release RELEASE=trunk CHECKOUT_DIR=/path/to/qpid && make render
5) svn add docs/releases/qpid-trunk # add any new files
6) svn st docs/releases/qpid-trunk | grep ^! | awk '{print $2}' | xargs --no-run-if-empty svn rm --force # remove any removed files
7) svn commit -m "publish qpid-trunk docs" docs/releases/qpid-trunk # finally commit the result back to site.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)