Browse files

adds a publish_docs task to force stable docs generation and publishi…

…ng after a new stable tag has been pushed
  • Loading branch information...
1 parent e1e780a commit dff0dfb7f80199e8f13dd20b39e0bc6b79438863 @fxn fxn committed Nov 16, 2010
Showing with 25 additions and 0 deletions.
  1. +25 −0 Rakefile
@@ -4,6 +4,7 @@ require 'rdoc'
require 'rake'
require 'rdoc/task'
require 'rake/gempackagetask'
+require 'net/http'
# RDoc skips some files in the Rails tree due to its binary? predicate. This is a quick
# hack for edge docs, until we decide which is the correct way to address this issue.
@@ -172,3 +173,27 @@ task :update_versions do
+# We have a webhook configured in Github that gets invoked after pushes.
+# This hook triggers the following tasks:
+# * updates the local checkout
+# * updates Rails Contributors
+# * generates and publishes edge docs
+# * if there's a new stable tag, generates and publishes stable docs
+# Everything is automated and you do NOT need to run this task normally.
+# We publish a new verion by tagging, and pushing a tag does not trigger
+# that webhook. Stable docs would be updated by any subsequent regular
+# push, but if you want that to happen right away just run this.
+desc 'Publishes docs, run this AFTER a new stable tag has been pushed'
+task :publish_docs do
+'').start do |http|
+ request ='/rails-master-hook')
+ response = http.request(request)
+ puts response.body
+ end

0 comments on commit dff0dfb

Please sign in to comment.