Jump to content

calbzam

Administrators
  • Content Count

    2,230
  • Joined

  • Last visited

  • Days Won

    56

calbzam last won the day on November 11

calbzam had the most liked content!

Community Reputation

88 Excellent

About calbzam

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

47,137 profile views
  1. Hi, Checking the logs, I don't see Plastic GUi even querying for the JIRA tasks: Are you selecting these options when creating the branch in the GUI? If you have a commertial license, you can opena support ticket and we can arrange a GoToMeeting to review your setup. Regards, Carlos.
  2. Hi, - We have recently updated the guide: https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide#Client-configuration-JIRA-Parameters For Next-Gen projects, you can't use a custom field. So don't create a custom a field and leave the "Custom Field ID" empty. This way, the checkin information will be logged as a comment in your JIRA task. - But the problem you are reporting is different: when you create a task branch in Plastic, the query to get the list of JIRA tasks is empty, right? Could you attach your client log (plastic.debug.log.txt) and the estimated time when you run the operation so we can review the query and any potential error? Regards, Carlos.
  3. Hi, - The Xlinks are always pointing to changeset guids (the universal identified for a changeset). I'm afraid I don't fully understand your workflow. If you can reach us via support ticket, we can arrange a meeting a debug your setup. If the XLink target changeset is deleted, you should be able to edit the Xlink target to a different changeset. You need to delete and recreate the Xlinks from the parent repo (not from the XLinked repo): "A repository cannot be loaded inside itself." --> If you are getting this error message, I'm guessing if you are trying to create the the Xlink inside the Xlinked repo when it needs to be created from the parent repo. Regards, Carlos.
  4. Hi, - You are right that when you manually edit the Xlink target and checkin these changes, you will need to update the workspace to download the content from the new Xlink pointer. It could happen on a scenario where you are not performing the changes in the Xlinked repo via the parent repo so your Xlink is out of date. - In the merge scenario: the merge is initially performed in the Xlinked repo and then in the parent repo. You will see that there are two merge links in your pending changes (one form the Xlinked and one for the parent repo). When you are running a merge, the new revisions created in the task branch will be downloaded to your workspace so when you you checkin the merge result, the Xlink should be pointing to the merge result changeset and your workspace should include all the revisions downloaded during the merge. An extra update shouldn't be necessary. - If you are refering to some specific merge scenario, could you let me know the steps to reproduce? Ideally, the Xlinks are designed to be modified always from the parent repo. This way, the Xlink target will be always pointing to the last and when you perform some changes in the Xlink, they will be automatically propagated to the XLinked repo. Regards, Carlos.
  5. Hi, If you are using Plastic cloud, only the webtriggers are supported (but not client-side or server-side triggers). You can check the details in the following link: http://blog.plasticscm.com/2020/06/web-triggers-for-plastic-scm-cloud.html Regards, Carlos.
  6. Hi, I would check the following: 1. Review the trigger permissions to be sure your user has enough privilege to run it. 2. Create a very simple trigger: eg: output a string to a file and check if it works. 3. Review the Plastic client log to check the if there is any error in the log when running the trigger. Regards, Carlos.
  7. Hi @DennisGabriel, thank you very muich for the detailed explanation. 1 and 2. Thanks for explaining in detail the issues you faced when configuring the server. Your feedback is very appreaciated. 3. Regarding the SSL configuration: If you don't define a specific certificate and password in "network.conf", when you start the netcore server, a new self-signed certificate ("ssl-certificate.pfx") will be automatically created and you should be able to connect to the 8088 port using with this certificate. You don't need to manualy set the file path and certificate password in "network.conf". Of course, you can also define your own custom certificate and password. [ { "port": 8087 }, { "security": "ssl", "port": 8088 } ] If the issue, persists, please reach us at support@codicesoftware.com and we can arrange a meeting to help you with the last configuration steps. Regards, Carlos.
  8. Hi @SystemId, Do you mind to send an email to support@codicesoftware.com? We are still trying to find a consistent way you reproduce this issue. Any clue is very appreaciated. The workspace metadata is wrong (the same item is appearing as deleted multiple times). As a workaround to continue working: Could you backup the current workspace changes and re-create the workspace. You can just remove the ".plastic/plastic.wktree" then run an update so it's re-created and the workspace should be clean with no pending changes and ready to be used again (you won't need to re-download the full workspace content as it's already there). So sorry for the inconveniences, Carlos.
  9. Hi @jdavo19, only one dev is experiencing the issue? Could you attach the local server logs of the affected user? C:\Program Files\PlasticSCM5\server\plastic.debug.log.txt Regards, Carlos.
  10. Hi @lrg_steven, just to clarify, is this the asset that is causing the conflict? https://assetstore.unity.com/packages/tools/visual-scripting/bolt-163802 I guess you have also installed the Plastic SCM plugin? https://assetstore.unity.com/packages/tools/utilities/plastic-scm-plugin-for-unity-beta-169442 And you have 3 computer with the same installed packages but the issue is happening in just a specific one? Regards, Carlos.
  11. calbzam

    Export Settings

    Hi, I guess you mean your Plastic client configuration? The client configuration is stored in the following path: C:\Users\xxx\AppData\Local\plastic4 Regards, Carlos.
  12. Hi, So you are trying to pull a repo from the cloud to a local server, right? Could you attach the logs from your local server to review them (and the estimated time when the issue happened)? /Applications/PlasticSCMServer.app/Contents/MacOS/MonoBundle/plastic.debug.log.txt Regards, Carlos.
  13. Hi, Yes, this is the changeset guid and the message shows the specific changesets (heads) you need to merge. If you switch your workspace to the last changeset of "/main", this is one head. Then you need to run the merge from cs:xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx to br:/main to unify the heads. Regards, Carlos.
×
×
  • Create New...