Jump to content

calbzam

Administrators
  • Content Count

    1,664
  • Joined

  • Last visited

  • Days Won

    38

calbzam last won the day on August 16

calbzam had the most liked content!

Community Reputation

64 Excellent

About calbzam

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

46,473 profile views
  1. Hi, Semantic Merges needs java for java and C++ parser. Is this your case? If you run one of the C# samples included with the tool, you shouldn't need to install java. Could you try it? Regards, Carlos.
  2. HI Mikael, - Regarding the robustness: if you stop the process or kill the operation via Ctrl+C, it should finish the sync of the current changeset and stop the operation. Then, you should be able to re-launch it. The problem is when there is a power outage or an uncontrolled shutdown. In that case, the sync may be broken. - @manu performed the same gitsync against a local server (a few months ago) and he reports that it took just a few hours. Not sure why it's taking so long to sync to your cloud organization. Could you try installing a hosted Plastic server in your machine? If this operation is much faster, then you can push it from the Plastic local server to the cloud. Regards, Carlos-
  3. Hi, Why do you need to listen for the attribute changed in a changeset? The goal of enabling mergebot is to automatize the merges of your task branches. When the branch attribute is set to resolve, mergebot tries to automatically merge/integrate it into your baseline (before passing your tests...). Mergebot merges branches and that's why it listens to the branch attribute value. Regards, Carlos.
  4. Thanks for the update. Yes, you can directly run GitSync with a cloud repo. I can see you have opened a new thread regarding this workflow so let's monitor the operation there. Regards, Carlos.
  5. Hi, It seems that some dlls are missing. Do you have any external tool/antivirus that may be removing them? Reinstalling doesn't help? If the issue persists, you can reach us at support@codicesoftware.com and we can arrange a meeting to debug it. Regards, Carlos.
  6. Hi, If you want to change the encryption key, you need to remove all your cloud repos first to start from scratch. If you just want to be requested to re-enter the encryption key again, you can remove the following files and restart the GUI:* Client: /Users/xxx/.plastic4/cryptedservers.conf * Server: /Applications/PlasticSCMServer.app/Contents/MonoBundle/cryptedservers.conf Regards, Carlos.
  7. Hi, If you create a new workspace and run a clean update, does the issue persist? In that case, please reach us at support@codicesoftware.com including the logs. We may need to arrange a meeting with you. You shouldn't be locked in a merge even if a file was removed. Regards, Carlos.
  8. calbzam

    JIRA plug

    Hi, Just to clarify the problem is when trying to configure the JIRA plug in the webadmin panel, right? Are you following the instructions from: http://127.0.0.1:7178/devops/plugs/types/jenkins/info ? I don't see any reference to the token API. Where are you reading it? PD: The following link explains how you can configure JIRA as issue tracker for Plastic but if I properly understand this is not what you actually want. You are just configuring the JIRA plug for devops purposes. https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide#JIRAintegration Regards, Carlos.
  9. You are right, the stash (we call it shelve in Plastic) is not still supported for cloud repos (only local ones). Let me understand a little bit more your workflow: - If you are creating task branches, I guess you are developers (I mean working with source code, not binary assets that then you won't be able to merge). As a developer using Plastic Cloud edition, you can also work distributed, hosting your local repos and then pushing/pulling to the cloud. I guess at the moment you are working fully centralized (your workspaces directly pointing to a cloud repo). - When you create a shelve, you are creating a temporary changeset and when you apply the shelve, you are actually running a merge of this temporary changeset with your workspace content (resolving the conflicts if necessary). That's why following this workflow you won't end up in an issue like the explained in the article: https://plasticscmsupport.zendesk.com/hc/en-us/articles/360014970894-The-parent-revision-of-the-item-is-inconsistent-with-the-loaded-one-in-changeset-cs-xxx Regards, Carlos.
  10. Hi, The problem when switching your workspace with local changes is you can end up facing problems like the following: https://plasticscmsupport.zendesk.com/hc/en-us/articles/360014970894-The-parent-revision-of-the-item-is-inconsistent-with-the-loaded-one-in-changeset-cs-xxx That's the reason why we don't allow by default to switch your workspace with local changes (although it's up to you to enable it). Not sure if you are aware of the "shelve" feature (also the "checkin changes to a different branch"). They can also be useful in scenarios like yours. Regards, Carlos.
  11. Hi, Regarding "readonly.conf": Contains the paths of the controlled items to keep as "readonly" after an update. This config file is located in the plastic4 directory (under $HOME/.plastic4 on Linux/Mac systems or C:\Users\user\AppData\Local\plastic4 on Windows), or in the plastic-global-config repository so that all clients have the same settings by default. You need to be sure that the "readonly.conf" file is already in the workspace before running the initial update (or distribute it via "plastic-global-config"). This way, the configured files will be read-only after the initial update. It's very important to train the users working with binaries so they checkout the file always before locally modify it. We are open to arranging a free training session with your team. Regards, Carlos.
  12. Hi, You are right, the locks are only useful if you are working o a single branch (normally working with binary/not mergeable files). This "single branch + locks" workflow fits good for the artists or developers working with assets (not mergeable files). By the way, are you using Gluon? https://www.plasticscm.com/gluon If you are going to create branches, it normally means that at some point you will need to run a merge so you are editing text/mergeable files. We generally recommend removing from the lock rules the files that are going to be modified in the task branches and finally at some point merged. I guess your scenario is very specific because you are creating branches where you also modify the binary files and you don't plan to merge later? 1) If this "fork" doesn't need to be integrated later, you can push this branch to a different repo where you can perform your changes. This way, the locks from the original repo won't be affecting you. 2) If this "fork" needs to be integrated at some point, you will need to perform the changes on a task branch. And we recommend you to remove the files from the "lock.conf" rules. If you are modifying the files on a task branch, it normally means they are mergeable, so locks shouldn't be necessary. PD: In the following blog post you can also read some improvements we have on our road map regarding the locks and task branches (your feedback is welcome!): http://blog.plasticscm.com/2018/04/2018-backlog.html Regards, Carlos.
  13. There was a temporary problem that should be already fixed. Sorry for the inconveniences, Carlos.
  14. Hi, 1. Could you attach the Plastic client log? C:\Users\carlos\AppData\Local\plastic4\logs\plastic.debug.log.txt 2. Could you run the following query in your browser? https://my.jira.com/rest/api/2/issues/{issueId}/transitions - Our code is processing the definition of the transition following the next steps from 1 to 3: [{ // transition definition "to": { // status definition "name": "...", // 2. status.name == "In Progress" "statusCategory": { "key": "..." // 1. status.statusCategory.key == "indeterminate" "name": "..." // 3. status.statusCategory.name == "In Progress" } } }] Regards, Carlos.
  15. Hi, We need to review the Plastic client after you run the GitSync to check if there is any error there: C:\Users\xxx\AppData\Local\plastic4\logs\plastic.debug.log.txt Regards, Carlos
×
×
  • Create New...