You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Here's the issue, we have three developers, and are developing using a tool called Talend Open Studio (TOS). Due to corruption issues we had, we are all running TOS using the same user profile. Now we are having issues with pushing to bitbucket. Here is the scenario:
Steps 1, 4, & 5 occur under our own user profiles.
Steps 2 & 3 occur under "shared"
To allow "shared" to export to the local repository, we clone from the command prompt using;
runas /user:"shared" /env /savecred "bitbucket generated clone string"
This sets authorities appropriately to allow "shared" to export and update the local repository.
The problem is that the clone includes the bitbucket userid from the user that originally cloned the repository, and only that user can push or pull from/to it. Only a single person can work in a TOS model at a time. So we don't get corruption from that, but we don't know which user is going to be updating the model at any given time, and we don't want to restrict updates to a single developer because sometimes one of us is unavailable.
Other than each of us maintaining our own local repository for each model, is there a way for dev1 to push a change to a local repository that dev2 cloned? We each have our own bitbucket logins,
The tracking remote URL for the local repository is: https://email@example.com/workspace/repository.git
We don't want to: