Jump to content

psantosl

Members
  • Content Count

    875
  • Joined

  • Last visited

  • Days Won

    20

psantosl last won the day on January 15

psantosl had the most liked content!

Community Reputation

34 Excellent

About psantosl

  • Rank
    CTO - Plastic SCM

Contact Methods

  • Website URL
    https://blog.plasticscm.com

Profile Information

  • Gender
    Male
  • Interests
    plastic plastic plastic...

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. psantosl

    Make branch main

    Hi, You can delete the last 3 changesets in the main branch (I assume you no longer need them). And then move the changesets in the other branch to main (you can merge, or you can simply move at this point): http://blog.plasticscm.com/2016/11/move-changesets-to-different-branch.html
  2. psantosl

    "replicate" one server to "another"

    Hi! All you have to do is to create a sync view with all the repos on one server and the other, and launch the replicas. Then you'll replicate all repos from A to B. Check this for more info: https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide#Chapter23:TheSynchronizationview If I wasn't clear enough, please ask! 🙂
  3. psantosl

    Delete Change set on Main Branch

    Hi! So, instead of merging you just copied the files again, right? Check this for more info: https://www.plasticscm.com/book/#_delete_empty_branches_only In short: you can't really delete this changeset without deleting the last one on main first.
  4. psantosl

    Can we use Plastic Cloud as issue tracker server?

    Hi David, Thanks for reaching out, and sorry for the delay, but we were discussing the solution internally. As far as I know, there shouldn't be a problem to connect your Plastic with a Mantis. Remember that the "integration" happens on the client side, so there will be the same integration whether you are on Cloud or on-premise. Built-in issue tracker: believe it or not, we have our own internal issue tracker !! You can see some screenshots here: And here a more recent one just taken: But yes, it is not meant to be a production issue tracker. We've dreamed about making it public, but... well, too much work. We struggle with Plastic already, so I don't think we'll be adding TTS (that's its name) soon to the pack. (Now who knows if I'll be eating my own words soon :P) Integrating with others is of course an option. We do integrate with a number of them: Jira, Bugzilla, and a few others. And... you can develop your own integration in almost no time: https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide#WritingPlasticSCMcustomextensions Hope it helps!
  5. Hi David, First, thank you for taking the time to compile all this great feedback. I'm the CTO here at Plastic, so let me share with you some of the designs we have for the upcoming Code Review system. Our plan was to implement it last year, but we got swamped by a ton of other smaller but still important things. First let me share what we consider the keys of the new code review system: I'm copy/pasting from internal docu :-) And this is how the overall design of the review window and its elements look like. The key elements for Code Review are: Comments are now together with the diff (on a side panel). Comments have replies, so you can handle threads there. The key is that you can "ask questions" and "ask for changes". And then it is very easy to track if those questions were answered or if the actual changes where made, which is one of the things you wanted to see. How? You'll type a special comment with a mark saying it is a change request. Then it will be very easy to track if the change or question was answered, and double clicking will show you the right diff: When you checkin, you'll be able to select (or using a comment) the "change" you are addressing: Finally, we'll have a conversation tab, to discuss general things outside the diffs themselves: And you can review changeset by changeset too, not only entire branches, which is great IMO: The last thing will be "review scripts": And that's just the beginning. So, in summary: we have put together a bunch of ideas thanks to all the feedback we got and our own practice of code reviews. Now it is a matter of finding the time to implement this in an incremental way. We want to finish some key changes on the server, which will enable the next Cloud version (and also key for some huge customers we have with 3000+ seats). And we also have to improve the single branch workflow for developers on game teams... so it is not yet decided when Reviews are going to happen. pablo
  6. psantosl

    ignore.conf doesn't seem to work

    Focusing just on the .git => I think ignore.conf thinks "." means a file and its extension. Check this http://blog.plasticscm.com/2014/11/configuring-ignored-items-on-your.html just in case it helps. Otherwise we'll get back to you in a few hours.
  7. psantosl

    Improved "cm.exe" command output

    Thanks Rubén, I just wanted to follow up with this: In the last versions since you wrote this we released a few command line improvements trying to make the whole thing better. Small tweaks here and there but the goal is to really make a big change in a few weeks. Check 7.0.16.2828 for instance. We reviewed some on the CLI docu. Still work to do. The plan is to continue expanding the REST API. We are in the middle of a few things right now that keep us certainly busy, but we are really committed to make all these happen. Some of the big things we are on: Tons of improvements to the macOS GUI. We always get heads up from users telling it is not on par with Windows. Multi-process server for Enterprise setups. This is a big effort and we need it to circumvent some issues in Mono and as the basis for the next Plastic Cloud we are working on. (I could talk about this for hours but I will just keep it short). New Unity Plugin. Unity teams are key for us. We are working on a big new plugin (where, small and easy, but big effort).
  8. psantosl

    Can't get rid of a pending merge link

    Why you didn't just click on Undo in pending changes? Didn't it work? Can you tell us how you were able to switch branches after a merge? An scenario will help us fix the issue.
  9. psantosl

    Can't get rid of a pending merge link

    Hi, Yes, this is pretty normal: you have pending changes in your workspace, and one of the pending changes is a merge link. If you want to undo everything, undo the changes. Warning: you will loose the changes! It is not a good idea to switch to different branches with pending changes, that's why it is forbidden by default (you had to change a setting to allow you to switch branch with changes, it is only meant for really advanced users, because the usual is to run into trouble). So, what do you want to do with these changes?
  10. Yes, I think what you need is readonly.conf https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide?term=readonly.conf#Chapter16:Configurationfiles
  11. Well, all the issue is exactly what the message says: your server is configured to use Active Directory, but yours is a Team Edition license, not an Enterprise Edition. Makes sense?
  12. psantosl

    remove unused local files

    Hi, Do this: From command line cm lrep --format=TABLE => will give you a list of your repos, including and ID. You can delete repos you don't use with cm rmrep. Remember the IDs of the repos you removed This m rmrep (or delete repos from GUI) "unlinks" the repos from Plastic, but doesn't really delete them from disk. You can now go and remove them from disk (or back them up first). pablo
  13. psantosl

    mergbots setup

    And yes, we must improve this, to make it easier to understand if things go wrong from the webadmin... we are on it ?
  14. psantosl

    mergbots setup

    Hi @Foxer You don't need an issue tracker nor a CI, Plastic can merge the branches back as soon as they get the right attribute (if I'm not mistaken, because we have different mergebots internally and it varies). If the mergebot doesn't start, check: \devops\logs under your Plastic SCM *server* installation. Check the trunkbot.*.log.txt. It will tell you why it is not starting. pablo
  15. psantosl

    Server-side merge and replicatewrite permissions

    I'm going to check but "replicatewrite" definitely shouldn't have nothing to do here ?
×