SDSChad

Perfect - thank you, Héber!

Hello, I am a Cloud user and I need to migrate the primary machine I use to perform GitSync on. I saw in another thread that this may be possible by migrating the "mappings" folder to the new machine, but I can't seem to find where such a folder may exist. Is such a solution still viable? Any help would be appreciated!

I was missing something that I didn't catch in the documentation. For others that find this, near the bottom of https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide#Jiraintegration there is an important note: If you use Jira Cloud, the User name must be the email address of the account, and the Password must be an API token. You can find out how to generate API tokens for your Atlassian Cloud account in their official documentation.

Hello, am I trying to configure Jira integration (Jira Cloud, Next-gen Project) with Plastic. When I try to test the connection, my logs show the following error: ERROR jiraextensionrest - Response from the server: Basic authentication with passwords is deprecated. For more information, see: https://confluence.atlassian.com/cloud/deprecation-of-basic-authentication-with-passwords-for-jira-and-confluence-apis-972355348.html It seems other people are having success on these forums connecting, so I'm wondering if I missing something in my setup? Thank you, Chad

Ah, I see now. I deleted the duplicated changesets and performed the gitsync from Machine A and everything is working as expected. Thank you for the information! On a related note, my primary reason for using GitSync is to interface with Unity Cloud Build. Is there a preferred way to lobby Unity for Plastic support? Best, Chad

Hello, I think I did something wrong, but I'm not sure exactly what yet. I recently did a git sync from Plastic and it told me that I needed to merge with the changes from Git, even though I had not made any direct changes to the git repo (all changes were performed through Plastic). Here are the steps that I followed: Machine A: 1. Created initial checkin along with a handful of other ones to main. 2. Synchronized all changes to my gitsync git repo. Machine B: 3. Made a few more checkins to main through Plastic. 4. Synchronized all changes to my gitsync git repro. After step 4, Plastic told me that my git repo had changed and that I need to merge. My branch explorer is attached and the red lines show changesets that are identical between the two (the bottom track was newly added by the git sync operation mentioned in step 4), but are somehow now needing to be merged. My question is if this is expected behavior? Should I just merge those identical changesets in, or did I do something improperly when switching between machines? Any help would be appreciated! Thank you, Chad

Hello Carlos, I deleted the git configuration from my plastic4 directory and was able to get the https link to my repository working with BitBucket using my normal Atlassian credentials. I must have had something wrong in my previous configuration. Thank you for the help!

Hello Carlos, yes, I am replicating from a Plastic repo to a Bitbucket git repo.

Hello everyone, I'm working on setting up GitSync to work with Bitbucket, but even though everything appears to be configured and executed successfully, no files show up after the replication is completed. I created a simple repository with one file in Plastic and the operation appeared to be successful (all green and report showed the statistics I'd expect), but the file ultimately did not show up in the Bitbucket repository. I did the same process with a GitLab account (repository with one file) and the file did show up as expected in GitLab. Has anyone else experienced issues with GitSync and Bitbucket? Note I tried both SSH and HTTPS, but there was no difference in outcome. Thank you, Chad