Travis build notifications sent to wrong person

Nobody has claimed this yet.

Travis uses last person to commit as the username associated with the triggered build rather than the person who triggered the build.

That user gets notified about the Travis build (if it was successful or not), creating unnecessary noise. Usually, this is not a problem because if you go to trigger a build it's likely you were the last person to commit to mason. However you can trigger Travis builds by publishing a package before you commit code changes to mason, and in that case you might not be the last person who made a commit.

If the Circle Trigger API can support connecting triggers to workflows, then we can have a separate publishing workflow that doesn’t notify last person to commit but rather the person who is triggering.

According to a Circle CI rep, the Circle Trigger API is likely to gain support for workflows soon.

cc @springmeyer

Start by reviewing the Travis build-notification behavior and the Circle Trigger API's workflow support described in the issue. Confirm whether triggers can target a separate publishing workflow, then verify that successful and failed publishing builds notify the person who triggered them rather than the last committer.

Written by the indexing model from the issue text.