Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

GIT Service Account

Hello,

 

We are connecting to a GIT repository using Bitbucket in TAC 6.3.1. I am able to connect successfully, but I was wondering about the best practices to do so. For example, my username is my own (i.e. jsmith) and we want to use a more generic account (i.e. talend_git). Is this recommended and/or acceptable? I've looked through TAC documentation and the forums but I didn't notice anything concrete.

 

Thanks,

 

Alex

Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

As a best practice, each user should have a different Git user account.  This way you can track who did the commit.  For example, if someone mess up your repository, you can identify the user, and provide him training and guidance to avoid that.

 

A generic user obscure the commits since they all appear under the same user.

 

Even for automation and ci, use a different user to identify any commit done by your CI process.

View solution in original post

1 Reply
Anonymous
Not applicable
Author

As a best practice, each user should have a different Git user account.  This way you can track who did the commit.  For example, if someone mess up your repository, you can identify the user, and provide him training and guidance to avoid that.

 

A generic user obscure the commits since they all appear under the same user.

 

Even for automation and ci, use a different user to identify any commit done by your CI process.