# Deployment playbooks, tasks, and the best way to build this?

**URL:** <https://forum.ansible.com/t/deployment-playbooks-tasks-and-the-best-way-to-build-this/12627>\
**Category:** Ansible Project\
**Created:** [April 4, 2013, 7:31pm UTC](https://forum.ansible.com/t/deployment-playbooks-tasks-and-the-best-way-to-build-this/12627 "2013-04-04T19:31:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ashley\_Penney](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Ashley\_Penney](https://forum.ansible.com/u/Ashley_Penney)\
**Post date:** [April 4, 2013, 7:31pm UTC](https://forum.ansible.com/t/deployment-playbooks-tasks-and-the-best-way-to-build-this/12627/1 "2013-04-04T19:31:52Z")

</div>

Hi all,

I have a use case that I’m trialing ansible for and I’m having trouble building it in a clean way without duplication. I thought I’d come to the list and ask for advice.

I have some generic stuff that happens for all of our application deployments, but are slightly different for each application (version and name). On top of that I have other steps like installing a repo file and custom steps for each application after the generic stuff.

What I have right now is this playbook, deploy.yml:

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [April 4, 2013, 8:12pm UTC](https://forum.ansible.com/t/deployment-playbooks-tasks-and-the-best-way-to-build-this/12627/2 "2013-04-04T20:12:14Z")

</div>

You can use includes with parameters to achieve this.

tasks:

- include: path/to/base\_include.yml a=1 b=2 c=3

- include: path/to/base\_include.yml a=1 b=2 c=3