Workflow ToolsStay Out of Production! Use WF to Deploy Code & Content
@Mediacurrent
Derek DeRapsDrupal DeveloperMediacurrent
Yesterday
WTF is
?WFT
WF is NOT a
module.
Well…
● WF is a module, + much more● WF is an approach● WF is a method● WF is a wrapper @ other tools● WF is a new best practice
It’s the icing on a 5 layer cake.
● Git● SSH● Drush● Jenkins● Deploy & UUID modules○ + many more
Who made it, and Why?
● Dave Hall (Pfizer)● Tim Holt (Acquia)● Drupal workflow sucks● No current “best practice” for
deploying content● New tools maturing
Pause to watch entire WF presentation from Prague
(not really, but do watch it at home!)
Old hat.
New hotness!
OK THAT’S AWESOME
i can haz some??“ ”
https://github.com/proviso/proviso
Yes, but don’t muck up your local stack.
STEP 1 of 3Download the latest “WF Example Profile”
STEP 2 of 3
Drupal setup● Drush make (must use 5.x)● Create “Reply” bundle “job_comment”● Enable all wf_example modules● Feature-revert all● Set variable ‘wf_sandbox_basepath’● Configure git module
Rules → Jenkins jobs● Rule: After saving a new workflow job
○ Job: create-branch, et cetera...● Rule: After a job is approved
○ Job: merge-branch● Rule: After a job is deployed to the final environment
○ Job: delete-sandbox○ Job: sync-dr○ Job: prod-snapshot○ Job: prod-archive
● Rule: After deleting a workflow job○ Job: delete-sandbox
STEP 3 of 3
Demo ;)