Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 10/10/2011 in all areas

  1. We're starting the development of the next GUI (called GUI 9 internally) in the next weeks. We expect having time to refactor the dark theme and implement a proper one.
    3 points
  2. Hi all, I have the latest Jenkins and latest Plastic plugin for it. I am attempting to set up a Unity build machine. Anyway, each time I build, the Plastic Jenkins plugin is removing the existing workspace and re-downloading it in its entirety. This is even with the "Use Update" flag set to true in the project configuration. This is not what I want as our build is capable of working incrementally and just switching to the head of /main each time we want a new build. The time difference is like 3m vs 40m. This seems like a bug. I know that it used to be a bug around v2 of the plugin, but was since fixed. Can someone help?
    3 points
  3. Hi My Jenkins and PlasticSCM are working complately fine. Use Update is working OK as long as I am not changeing selector value (sometimes I need to tune branch). Could you please tell me what is the reason to delete complately workspace in such case and re-create it from scrach? Generally it would not be a big problem except that my repo is quite big and when workspace is deleted my cloaked, ignore and hidden_change configuration is also complately removed Especially that in GUI I am switching between branches and even repositories and/or server and there is no need to re-create workspace. Thanks in advance for the answer.
    3 points
  4. Hi Marc, In the next 1-3 months we should be releasing the first version of our new multiplatform GUI and it should also include the dark theme. Sorry for the inconveneinces again, Carlos.
    2 points
  5. Hi! Thank you for the feedback on this. To build on the reply from @ollieblanks, we are currently working on addressing this. By default, the checkout will not be enforced. There will still be an option to enable the "forced checkout of Unity assets", but it will not be the default behavior anymore. This will be released in an upcoming version after we complete the move of the plugin to the Unity Package Manager. Please feel free to share more feedback on your experience with Plastic SCM for Unity with us!
    2 points
  6. Hi, We are working a new multiplatform GUI. It should ease the development of a modern dark theme taht works both for Windows, macOS and Linux. Hopefully we have good new soon. I'm sharing your request with the product team. Regards, Carlos.
    2 points
  7. A new coworker of mine had this problem too. They had the wrong encryption key. Everything is starting to work correctly after we entered the correct encryption key.
    2 points
  8. Yes Yes, just make sure ignore.conf isn't confifured to ignore itself and everybody will have the same settings. Glad I could help.
    2 points
  9. Hello, Have you manually moved the "client.conf" to this path? By default, it shouldn't be there. Anyway, assigning the necessary permissions to the file should prevent this error to happen. Regards, Carlos.
    2 points
  10. Hi, We just changed this behavior. There is a fix ready that will be shipped in the next public release. It will be reday today or early next week. We apologize for the inconvenience.
    2 points
  11. Although you're past your issue, I figure I might as well mention this for anybody else that comes across this thread looking for a solution in a similar situation: in a scenario where you have hundreds of moves, the least-effort solution is probably to check-in the moves that were correct, then turn off auto-detect and check-in the other ones in a separate changeset. While it might sound messy to have two commits where you could have one, ideally, these moves are being performed on a task-branch, so you would still have a single commit on your main-line. Of course, this is still a work-around. While I can understand from a software architecture perspective why Plastic does not allow you to selectively undo auto-moves (because the auto-moves are transient), it would be much better if Plastic SCM allowed auto-moves to be "staged" (or "locked-in"), just like how you can change items from Private to Added.
    2 points
  12. Hey, just thought I'd say thanks to the devs and support team for the good job you guys are doing. Plastic has been easy to use for the most part and the support team has always been quick to reply when I've had questions. Keep up the good work! (This message was not paid for)
    2 points
  13. It is now in 'Developer settings' (settings -> developer settings -> personal access token -> generate new token), but the solution is still working 5 years later ;-). Thank a lot ! https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
    2 points
  14. Hi, when there will be a plugin for WebStorm? IMHO it can't be much work because WebStorm is based on IntelliJ IDEA. Asking greetings Reiner
    2 points
  15. It's very handy for us to be able to send links to each other at my work which lead to a particular diff. Based on some old blog posts I tried to implement this the best I could but was having issues using the syntax indicated. (see this post: http://www.plasticscm.net/index.php?/topic/2491-jira-interactive-link-to-changeset/?hl=%2Bjira+%2Bplastic) To launch a diff use the following URLs (On Windows) Branch Diff: plastic://showbranch=br:<BranchPath>@<RepoName>@<Server:Port> Changeset Diff: plastic://showchangeset=cs:<Cset Number>@br:<Branch Path>@<RepoName>@<Server:Port> I'm just posting this to help someone else out who may be trying to do the same thing.
    2 points
  16. Hi all, Delphi support is the top 5 request in our User Voice: Delphi support in SemanticMerge. So we're eager to add Object Pascal to the list of supported languages. In order to do so we’ve developed a way to plug-in external parsers, so if you can develop a Delphi language parser it will be very simple to get it invoked from Semantic. If you’re interested on joining our “Delphi Parser” effort, please join this thread and we will send you the required tools. Right now all what plugin a parser requires is: * Create an standalone executable. * Able to receive some data as arguments. * And able to export the "tree" of the file in YAML format. Of course you'll need all the details but this is just an intro of what it takes. We've also developed tools to help testing the parsers, like a "directory parser" which will loop through a code tree parsing (invoking your parser) and then rebuilding the source file making sure the original and the regenerated ones match. We're eager to get this started! pablo
    2 points
  17. I've been using 4.1.10.372 - Brighton as a hermit developer on a single workspace for about a year now and recently had to refactor my PC drives and network mapping. The drives on my PC have changed and I would like to change the location of the workspace path. I searched the knowledge base and the forum and didn't see any posts on this subject, but perhaps I'm not searching for the correct terms. Anyhow, I would like to keep the current changeset history but redirect the workspace path. For example: from - F:\MyApps to - G:\Network\MyApplications Thanks -
    2 points
  18. Is there a version of Gluon for mac? there doesn't seem to be an option to install it on mac like there is in the windows installer. If there is no mac version is one planed? ​Cheers!
    2 points
  19. Hi Wolfram, I've seen this idea being kicked around before - branching for the sake of maintaining multiple 'kinds' of a product, as opposed to parallel development streams of the *same* product. The latter has a notion of merging changes back together at some point - be they hotfixes on a release branch going back to the development mainline, or a new feature off a feature branch. The idea is that the product may at various times bifurcate into more than one parallel version, but this is a variation on simply having one line of development. Ultimately it's still just one product. You might get abandoned experimental branches and POCs too, but they don't get merged back. What you want, I think, is a set of never-ending branches that represent similar products that share code in common, but should not be regarded (and not sold) as one thing. As I'm sure you already know, you can start with a common main branch, make product line-specific branches off that and then have a rule that merges must flow from the main up to the branches, but never the other way (otherwise you'll end up creating a fused product). This takes some discipline, and if you detect bugs on a specific product (which will be the case for those reported in the field), then you'll have to make the effort to triage those bugs into those that are product line-specific, and those that are common. The product line-specific ones get fixed on the branches, and the common ones get fixed on main (or on temporary topic branches that flyout from main) and then get merged up into all the product line branches. Of course, this doesn't always work out in the heat of development, in which case you have to cherry-pick a fix from the product-line branch back to main, massage it to make sure that no fusion of product line-specific stuff occurs in the merge. It's achievable in Plastic if you isolate your bug reproduction tests and fixes in either single commits or topic branches that flyout off the product line-specific branches - you can cherry pick these without bringing in too much unrelated cruft. I really would stick to just that flow and avoid cloaks and subtractive merges - these things have their place, but you'd have to be very careful about code organisation, for example, if you want to use cloaking to make a merge back from a product specific branch back to main safe. Which brings me to... Have you considered factoring your codebase into a common piece and stuff that can be product-specific? I would hope that most of your code could be hived off into a library that has just one delivery branch (I'm ignoring release branches, you get the picture, I'm sure) in its own repository. The product specific stuff can then become completely independent projects with their own repositories. You can either go the route of delivering the library as a binary internally, or use an XLink to mount it within your individual projects. You can do both if you want - you'll know when you'll need to do that. You could go the route of keeping your product lines as one repository with line-specific branches here too; in which case I'd hope that having the common library would cut down on the ceremony of maintaining the branches and sticking to the merge discipline - less code to worry about. If you go down that last variation, consider using feature toggles and configuration so that the product specific-lines only vary in configuration files and not in main code - in which case you can start to think about cloaking again; this time it might be easier. So to summarise, it can be done but there is no silver bullet I know of. I'm curious myself now to know if anyone else has experience with this... Regards, Gerard
    2 points
  20. 2 points
  21. I'm sorry but I can't reproduce the issue. Can you tell me if you osee the same behavior after creating a new Jenkinks project? This is what I get after creating a brand new one: Started by an SCM change Building in workspace C:\Program Files (x86)\Jenkins\workspace\TestingPlasticSCMPlugin [ZZZ_Wks] $ cm lwk --format={0}#{1}#{2} ZZZ_Wks#SUPERAWESOMECOM#c:\Program Files (x86)\Jenkins\workspace\TestingPlasticSCMPlugin\ZZZ_Wks [ZZZ_Wks] $ cm ss wk:ZZZ_Wks Selector for workspace ZZZ_Wks: repository "ZZZ@localhost:8087" path "/" smartbranch "/Production" [ZZZ_Wks] $ cm update "c:\Program Files (x86)\Jenkins\workspace\TestingPlasticSCMPlugin\ZZZ_Wks" Downloading big file c:\Program Files (x86)\Jenkins\workspace\TestingPlasticSCMPlugin\ZZZ_Wks\trigger.txt (12 bytes) Copied c:\Program Files (x86)\Jenkins\workspace\TestingPlasticSCMPlugin\ZZZ_Wks\trigger.txt [ZZZ_Wks] $ cm wi "c:\Program Files (x86)\Jenkins\workspace\TestingPlasticSCMPlugin\ZZZ_Wks" --machinereadable --fieldseparator=def#_#sep BRdef#_#sep/Productiondef#_#sepZZZ@localhost:8087 [ZZZ_Wks] $ cm find changeset where date between '2016-09-07T12:49:13' and '2016-09-07T12:57:08' and branch='/Production' on repositories 'ZZZ@localhost:8087' --xml --dateformat=yyyy'-'MM'-'dd'T'HH':'mm':'ss <?xml version="1.0" encoding="utf-8" ?> <PLASTICQUERY> <CHANGESET> <ID>50325</ID> <CHANGESETID>313</CHANGESETID> <COMMENT></COMMENT> <DATE>2016-09-07T12:55:42</DATE> <OWNER>mlucio</OWNER> <REPOSITORY>ZZZ</REPOSITORY> <REPNAME>ZZZ</REPNAME> <REPSERVER>localhost:8087</REPSERVER> <BRANCH>/Production</BRANCH> <PARENT>312</PARENT> <GUID>5cfb81dd-ef47-4cc4-8d57-04c256f87bc8</GUID> </CHANGESET> </PLASTICQUERY> [ZZZ_Wks] $ cm gwp "c:\Program Files (x86)\Jenkins\workspace\TestingPlasticSCMPlugin\ZZZ_Wks" --format={1} c:\Program Files (x86)\Jenkins\workspace\TestingPlasticSCMPlugin\ZZZ_Wks [ZZZ_Wks] $ cm diff cs:313@ZZZ@localhost:8087 --format={path}#@_sep_@#{revid}#@_sep_@#{parentrevid} --repositorypaths "/trigger.txt"#@_sep_@#50321#@_sep_@#50315 Finished: SUCCESS It's a build triggered by a new change in the repository, only one file is downloaded and the workspace is preserved.
    2 points
  22. Thank you for the feedback. Let me start a few tests and I'll try to get more info.
    2 points
  23. Hi Misieq, we changed the way the selector is parsed so we don't force unneeded updates operations. Not sure if it's your case but it's worth to try it out. https://github.com/jenkinsci/plasticscm-plugin/commit/3749e47129a95dd1ce85766953dd65d12bd40047 Can you give it a try and give us feedback? If it keeps failing we'll schedule internal test to give you a fix.
    2 points
  24. Hi, We have recently release the 2.6 version including a fix. https://wiki.jenkins-ci.org/display/JENKINS/PlasticSCM+Plugin Could you upgrade and check if the issue is reproducible? Regards, Carlos.
    2 points
  25. Hi Manu, Thanks for the tip - I'll stick with the Cloud edition for now, as I think I'd have to have the full paid regular server license to run GitServer if I remember correctly - I went for the Cloud edition as an easier way to manage the fee. I'll wait for the fix to come out, please post an update when it does.
    2 points
  26. I've rolled back Plastic SCM to the previous released version: 5.4.16.769 (Every Breath You Take) - this fixes the problem for me for now; I can start the Plastic SCM service and use GitServer. I looked through 'plastic.debug.log.txt' again after deleting the old contents and restarting the server; I'm still seeing the same assembly resolution failures as in the original post above, even though the service now starts up correctly and works, so I guess that information was irrelevant after all.
    2 points
  27. Hi I have noticed new Jenkins plugin version (2.5)with some corrections around "Use Update". So checked again behaviour with parametrized selectors and workspace deletion... It looks that the issue is still present I went quickly through plugin code (at GitHub) and this is what I have found: PlasticSCM.checkout(...) -> PlasticSCM.isWorkspaceDeleteNeeded -> workspaceConfiguration.equals(...) -> builder.append(this.selector, other.selector); So it looks that in fact any change in selector will always lead to Workspace deletion and re-creation from the scrach... Do you plan to change this behaviour? Or at least please do not delete conf files (cloaked, hidden_changes and ignore).
    2 points
  28. Hi! we are able to reproduce the issue and we are going to be fixing it asap, hopefully today. I'll update this thread once the bugfix is public.
    2 points
  29. Hey, I figured out the problem through some extensive research of my own and, I thought I'd leave the fix here for anyone else with this problem since it isn't documented anywhere as far as I can tell. It turns out I actually blocked myself out by using 2-factor authentication on Github, and PlasticSCM doesn't work with 2FA by default. That's why my username/password combination wasn't working when I tried to sync with git. In order to bypass this problem, I had to generate a personal access token in the Github 'Application' settings and then use that as my password in PlasticSCM. Everything works just fine now, and I'm happy as can be.
    2 points
  30. thanks, I have merged + fixed it now
    2 points
  31. Hi, I'm guessing if the following path may also work: https://blog.plasticscm.com/2019/01/fully-automated-plastic-scm-setup-on-raspberry-pi.html But using an old Plastic server that you won't be able to upgrade not sure if it's a good idea. Don't you have any other machine where you can install the server (even your WIndows machine)? Regards, Carlos.
    1 point
  32. Hi Alan, Thanks for your feedback, I will share it with the Development Team. Regards, Rafael. PlasticSCM Support Team
    1 point
  33. It is up and running. Thanks!
    1 point
  34. My team can't connect to the servers. How can I check the server status? It would be nice if there was a popup in-application, or place online (even like twitter) where we could get confirmation that the servers are down, and the expected time for them to be back up.
    1 point
  35. I am also having connection issues to my team's plastic cloud instance.
    1 point
  36. \o/ It's working now But I don't got what I was doing wrong, differences between your setup and mine is only your binding that is to "Repositories" and not my local repository specifically Anyway, thanks for help 😜
    1 point
  37. Hi John, Are you using a WiFi connection? We have seen this error in the past and it comes due to some network issues. Probably using a different network or a wired connection will let you perform the whole checkin. That's why you were able to submit them one by one. Best, Héber.
    1 point
  38. Hi, If you just want to search a string in local workspace files you should be able to use a "grep", right? https://www.cyberciti.biz/faq/howto-use-grep-command-in-linux-unix/ Regards, Carlos.
    1 point
  39. I shared this request with the team. We already internally commented some improvements about how the user can fine tune the move detections performed by Plastic. It would be a nicefeature but I'm afraid it's not scheduled for the near future. Regards, Carlos.
    1 point
  40. As i said earlier - i solved my problem by defining 2 different libraries in Jenkins Settings. I'm ok with this workaround. So we can close this topic In case, you want to investigate this further: version selection doesn't work as they propose in the previous link for legacy SCM. I tested it with: - Plastic - returns errors in selector - Github (legacy SCM) - just checksout latest changeset (regardless of brunch) I didn't find any references to someone using library versions on legacy SCM and decided that this is a Jenkins bug, but i didn't created issue on their bug tracker
    1 point
  41. I believe you can also remove the file from source control by deleting the file in plastic scm (but keeping the file on disk), checking in the delete, then adding the file to ignore.conf. The file will no longer be tracked and will be removed from your repo. For files you'd like to keep in the repo but you still wish to ignore in some capacity, you'll want to add to the cloaked list or the hidden changes list, depending on your needs.
    1 point
  42. My impressions and thoughts for first look... A general comment: With wide screen monitors, horizontal space is easier to give up than vertical space. Vertical space is a premium. Please keep that in mind when adding things to the vertical space. Using more space for the headings and tabs allows you to put more info there, but takes away from the precious limited vertical space for the main part of the screen. At least having an option to put this on the left hand side vs top could be nice. I understand wanting to make the gui more accessible for new users. But you need to also not leave users that are used to the system. Ability to control the interface, to a degree, can be useful in this (e.g. minimal view, vs more info view). I can already see some operation I do taking more click in the new interface than in the old. One thing I do (admittedly more in tool admin role than as a developer) is open up the list of repo, then view a repo (e.g. branch explore a repo w/o a WS). It looks like now I have to first click to create a new tab, then select repo list. I assume the rest of my operation would be the same from there, but still at least one more click. It would be good to have the GUIs more similar across the platforms (for us, esp Windows and Linux). But my first priority would be making features available in one gui available in all. While I could see this consolidating effort a step in that direction, I hope we do not take a step back and see features go missing (e.g that are already in the windows gui today). I would REALLY like to see some missing functions added to the gui as more important than a gui re-design. How long have we now had the ability to create xlinks to a path in a repo, but still have to create it only using the CLI? That (and any other missing functions) need to be added to the gui. I could see more customization of the gui, esp for experienced users. Say, being able to have a custom left hand "new tab" buttons on the left hand side (hidden and empty when you first install the client?) I could also see more customization to right click menu options for experienced users (not only for tabs for for other contexts). Thanks, Todd
    1 point
  43. These changes but good! But I do have to say as an end user the GUI is not the painful part of Plastic, but rather unexplained/strange conditions. Any effort to address error states/messages better would be an even bigger win, in my opinion. Just these 2 we brought up here for example: Renaming a branch causes other workspaces referencing it to "break" without explanation (just error messages) "Hidden changes" causing a warning that looks unrelated, every single time you switch workspaces (even if having changed files locally is the intended usage pattern for hidden changes!) Also not being able to use shelving for cloud users would be nice. Anyhow, we really like how you're being responsive again these are meant as constructive criticism. Thank you!
    1 point
  44. bump, I just ran into this for lots of files, quite painful
    1 point
  45. I think that repro is simple - I've marked this toggle in options few days ago and pending changes get destroyed. Maybe that when pending changes are "destroyed" Options window values overrides cfg file or sth like that.
    1 point
  46. We found a strange behavior in Plastic recently: Somebody deletes a directory and check-in this change. Others update their workspace, but the deleted folder and all its content is not deleted but rather left in their workspaces as private items. Why is that? It brings more work for everybody – all need to delete the already deleted folder too (and make sure not to delete any other private items, they might have). I understand that there can be more complex situation: somebody have some private items in a folder which was under version control but which was deleted now. It would not be right to delete that folder during update with the private items of that user in it. Plastic should delete only the files which was deleted under version control system and folders which contain these files only. However if there are no private items, it seems to me to be OK to delete the whole folder, when it was the checked-in change.
    1 point
  47. Hi Tomas, But the internal ID is not related with the branch or changeset target. If you run a "cm find review" you'll get something like this: >cm find review 1138 11/2/2016 11:23:18 AM mlucio Status0 "test2" ChangeSet 12 1139 11/2/2016 5:57:53 PM mlucio Status0 "CodeReviewForBRanch" Branch id:873 1140 11/2/2016 5:58:03 PM mlucio Status0 "CodeReviewForCset" ChangeSet 8 The ID is the database index, the last value is the target object. Would it be enough for you to be able to edit the CR using the "cm cr -e" command?
    1 point
  48. Hi! We fixed and issue similar than the one you reported. Can you please tell me the macplastic version you are using? if it's not greater or equals than 5.4.16.782 please upgrade and try again. (current one is 5.4.16.787)
    1 point
  49. Wow! Top 5?? Too bad I'm not working with Delphi anymore. I really would like to help you! Keep the good work!!
    1 point
×
×
  • Create New...