Different author commit and pipeline

Question

Hi,

I've worked on a specific repository and I've committed in there and when looking in Bitbucket the name of the author of the commits is mine.

Nevertheless, the automatically triggered pipeline is showing that my colleague has started the pipeline, whilst this is an automatic process at which in other repositories the author of the commit is also the person who's linked to the pipeline.
So a strange thing seems to be happening with this specific repository.

I've checked my settings in SourceTree, but I'm nowhere using the name and/or email of my coworker. Also the repository doesn't contain any credentials in the .git directory which aren't mine and the settings of the repository are equal to others where everything goes fine. So I haven't a clue why this coworkers account is being linked to a pipeline which is triggered due to my branch with my commits.

Do you have any clue?

Erwin Augustijn · Answer

Hi ktomk,

Thanks for answering.
No, we're using defines branches in this format:

pipelines:
   default:
     - step: *validate-project
   branches:
     test:
       - step: *validate-project
       - step: *compile-files
       - step:
           <<: *publish
           name: Publish to test
           deployment: Test
      ...

The biggest problem we're facing is:

* I don't receive email when my pipelines (for that specific package) fails
* My colleague receives email from pipelines which are triggered by my code

Luckily I'm still the commit author, so it's not that I'm commiting as him, but I still think it's weird that I haven't found the explanation yet why this is happening.

Erwin Augustijn · Answer

Hi Theodora,

I'm using SourceTree for Windows with Pageant indeed.
I do have one ssh key which is linked to my Windows User account:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDVW91Vpu3BXfDeY48MWlYMj+PgGrCT/LPTUyulFS5KI5vr3ZZsa68XtYkeZVUAf/WQN+F/V208g7lE2fLafzV33Ih04yLbrEIiRuWjN9sHldwjhxJAsh1hM+5YNxawZ3ZCJYeWBUqmeqKyqTWHPzqZFFJWLIy2VWSYqzuqF1zytRDV7lGu41R2dGvLLE283LSsgZNzsZxjo2SkUMe4PIZAiwNM/D+cjckshzc2zMsmA4wM97OBPckN69aJNV19pcXtQPvGM/InbDYkQdp0qan7UPO2gMqoMArmqve6aiXyB3o0OUoGIYh22QWn+lvio0sZJM8lJHep2nCCM4jEZXPp

And one ssh key which is used by Docker (and autogenerated):

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDLcEHPHV77MoHDhgrjC4TpQ9/wqPAA0Tx2wG+HlSkAr9jxZAc+NXh6CnPhBCiigrglAJrvGIn6t8RNn5+Npn2NpsX8D1WY5cs/qkfgb3pBxBO6Gy5MjGCPg+7EOnEzrCAJwsMFbWlo2vgfdA/K5d92pgZITAW1og+Js9oXublo+2EfwsvoLs4qDQdPKRPd228he9pN5t9EygiqF+ZTwSPuECyTZTJQZVwNqXfGHslB/2cCVqP7lBkF27h0/BlHoi/YAbkTomnQmgMU9xrjOiSThvRwVtw/8l51igz9LHAqqp1ymffza1ESj3kB5wAGp0tUhHWh0vVtPqi3W6V04kK1 root@51a3747221b5

My .gitconfig file in my Windows User account:

[difftool "sourcetree"]
cmd = '' \"$LOCAL\" \"$REMOTE\"
[user]
name = Erwin LASTNAME
email = erwin@domain.ext
[mergetool "sourcetree"]
cmd = "'' "
trustExitCode = true

My .gitconfig file in my Docker environment:

[user]
name = Erwin LASTNAME
email = erwin@domain.ext
[core]
autocrlf = false
[pull]
rebase = false
[color]
ui = true
status = auto

[color "status"]
added = green
changed = blue
untracked = magenta
deleted = red

ktomk · Answer

IIRC this can happen when I share branches with colleagues and there is an ancestor that is shared and then I push it or my colleague pushed it, I can see pipelines created by me that are of my colleague and vice-versa.

Technically I can always push a commit of my colleague, still then I have triggered the pipeline but the commit is not "mine". So actually unless you need this more controlled, I'd say this is totally possible.

Are you using wildcard-patterns in the bitbucket-pipelines.yml to trigger on branches or tags?

(Also I assume you're using Git, let me know if not).