Document how to integrate Tugboat with GitHub-for-JIRA

[q0rban]

When:

• Using Tugboat with Deployment Statuses
• With repo hosted on GitHub
• And tickets / issues in JIRA
• And using GitHub for JIRA plugin in JIRA

JIRA will show deployments as unmapped. We should document how to set this up so that Tugboat environments display properly in JIRA.

@owenbush discovered the following:

Looks like I managed to get Github, and JIRA configured to no longer have unnamed environment releases.
In Github we now have 4 environments set up:
Dev
Test
Tugboat
Pantheon
I then added a .jira/config.yml file to our repo with the following environment mappings:

deployments:
  environmentMapping:
    development:
      - "Dev"
    testing:
      - "Tugboat"
    staging:
      - "Test"
    production:
      - "Pantheon"

Deployments to Dev should show up as Development in JIRA
Deployments to Tugboat should show up as Testing in JIRA
Deployments to Test should show up as Staging in JIRA
Deployments to Pantheon should show up as Production in JIRA
Below is a screenshot of a release for an issue that was just deployed to Tugboat.

To me it felt like Tugboat is more of a testing environment than a staging environment which is why I did the mapping that way. But this could be up to whoever the devs are on a project.

[KeyboardCowboy]

@qorban, where is the right place for something like this? Should we start a new section for third party integrations?

https://docs.tugboatqa.com/

[KeyboardCowboy]

Let's create a new top-level item for 3rd party integrations and move other things out of snippets as well.

[q0rban]

@KeyboardCowboy bumping this up. Will you have time to work on this? Perhaps Scribe could help us here?

[KeyboardCowboy]

I'm hoping I will soon, especially with some quiet holiday time coming up. Trying to get past a few Iowa hurdles right now.