[RTEMS Project] #2864: docs.rtems.org Automatic update of branches content when a rtems-doc.git change is made.

RTEMS trac trac at rtems.org
Mon Jan 16 22:42:16 UTC 2017


#2864: docs.rtems.org Automatic update of branches content when a rtems-doc.git
change is made.
---------------------------+-------------------
 Reporter:  chrisj         |       Owner:
     Type:  defect         |      Status:  new
 Priority:  high           |   Milestone:  4.12
Component:  Documentation  |     Version:  4.11
 Severity:  major          |  Resolution:
 Keywords:                 |
---------------------------+-------------------

Comment (by chrisj):

 Replying to [comment:3 amar]:
 > I have already written something like this for the new docs.rtems.org.
 Incremental builds (by commit) and release builds.

 Release builds are part of the release process which is a separate from
 this web site. The released documents are loaded on the the web site and
 the website's configuration updated to include the release details and the
 site is regenerated.

 For building from git I was told to sort out building by cron so this is
 what I have done.

 Is it possible to set up a share on the TrueNAS to be a clearing house
 between sync and docs?

 > It needs to be managed properly, most projects overwrite their 'devel'
 documentation with new versions.

 I am concerned it places extra stress on the limit resources we have so do
 not see holding builds as a priority. We have the source in git so someone
 can get that release and build it.

 >  I want to keep around every single built version for comparison this is
 more useful for contributors.

 How is this more useful for contributors?

--
Ticket URL: <http://devel.rtems.org/ticket/2864#comment:4>
RTEMS Project <http://www.rtems.org/>
RTEMS Project


More information about the bugs mailing list