Jump to content

psantosl

Members
  • Content Count

    984
  • Joined

  • Last visited

  • Days Won

    24

psantosl last won the day on December 3 2019

psantosl had the most liked content!

Community Reputation

38 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. Remember to create repos you have to use the GUI, there is not support for that from the web dashboard. I bet this will ring a bell
  2. Hi, Please understand this is not the regular workflow. The way to abandon locks is: You checkout 100 files (probably not a common thing to do, anyway). Then you delete your workspace. Then your locks are lost. I would say, based on all our other customers, that abandoning a workspace with locks in it is not a common thing to do. Of course it can happen, and yes, of course we can have a better interface for handling that, but we consider this a rather corner case, otherwise we'd be running into it every single day, and fortunately we do not. We are here to try to make our customers happy. If you really think Plastic is the worse version control you ever used, then my recommendation is: "please stop using it". I prefer that you are happy using a competitor than unhappy using us.
  3. Are you sure you use different directories in Git? Or do you mean you use different repositories? When you say Git you mean GitHub or GitLab, correct? In Plastic you should achieve this doing the same as in Git, different repositories. It is also possible to achieve it with directories, but AFAIK, this is not really possible in Git. While you can do it using permissions in Plastic, I strongly recommend you to use different repositories for your case. This is a very good question. Git-Flow is somehow considered outdated these days because it is an overcomplicated solution. You could implement exactly the same thing with Plastic if you want, no limitations, but I don't recommend it. Task branches + trunk based development is a much faster way to work, and much simpler. You can keep merging branches back to main during the entire week, then release at the end of the week if needed. OR, you could now release more often. Regarding the v1.0 fix: why don't you simply create a new version with the fix at the current stable state and release it? This is entirely possible. Just do the fix based on the latest on main, merge it back, release. Yes, the user will get some improvements too, but that's not an issue 🙂 In case you really, really want to fix on top of v1.0: - You can create a branch out of v1.0 - Fix it there. - Label the cset in that branch accordingly and release it. - Merge the fix branch back to main too, so the fix also goes into the next release. Hope it helps, pablo
  4. Sorry to say the feature is not yet there. No excuses, we got swamped with other things and simply postponed this one. It is entirely my fault.
  5. Hi Jep, I bet you are almost there, but we're failing to explain it correctly. Sorry for that. Let me know if this two things help you. 1. I recorded a video explaining distributed vs centralized: 2. We have a section in the Plastic Book dedicated to this https://www.plasticscm.com/book/#_centralized_distributed In case none of these make it clear, just let me know, please 🙂
  6. I'm afraid we're not showing the LDAP names correctly on the client sides, for Active Directory, they show the SID. I think it gets better when you connect using AD mode instead of LDAP to AD.
  7. Are you using LDAP as your auth mode, right?
  8. Ok, but you're asking us different things on the same thread, correct?? I mean, what @Tobix wants is a "view changesets of current branch" in the context menu on the status bar. I hear what you say, but unless we can cluster more requests I'm not sure we'll make it. Yes, I know what you want, but I honestly think the BrEx gives you that, because you should always see your current branch quite easily. I can understand this is not your favorite choice, but we need to keep a vision on the product, and BrEx is definitely our way to understand version control. I mean, once I'm on my branch on brex, just clicking on the csets gives me the diff and everything. Also, I don't know if you switch branch every 5 minutes, but since I don't think it is the case, you can always have an open list of csets for the current branch. So, opening a new one will not be probably something you do very often. Maybe we can have a query to show the csets of "current branch". Regarding Jan's proposal: ok, a home button there, it could be. But it would be the same number of clicks like in the brex, correct? They both have the same menu.
  9. When you list repositories, you can only see the repos where you have list access. If you really need to know where you have checkin access, for instance, then you'd need to check the ACLs for each repo. So in short: there is no way to know "user has permissions" other than checking ACLs. You mean all the users who have access to a repo? No. Users are obtained from services like LDAP, for instance, so you could have users with access to a repo that never actually touched the repo, and the list of users is outside plastic (except for UP mode, but it is treated consistently as if it was external). See what I mean? there is no concept of "users of a repo", but simply there are users, and some of them have access. We have LDAP trees with tenths of thousands of users, and Plastic doesn't know about each of them. My question for you would be: what are you trying to achieve? Maybe we can help you if we understand that. Thanks, pablo
  10. Thanks for sharing! This is all our build master https://twitter.com/jesusmtate
  11. Wow! Never thought about this. And this menu is probably about to be gone (set selector should have been removed long ago). That being said: why don't you look into the branch explorer? You immediately see your changes, right? I'm trying to figure out why I never needed this before
  12. Why would you associate a checkin number to an issue tracker instead of the branch? I'd recommend you taking a look at https://www.plasticscm.com/book/#_a_perfect_workflow Also, we have integration with some issue trackers that can do this association for you. And, you can always write a trigger to do this association. Or a trigger to pop up a dialog that does this But, popping up a dialog with the cset number is not something we'd like to do, because it would be disruptive for mostly everyone except you 🙂
  13. Hi @tino333 You should use the date filter. The Branch Explorer is definitely not meant to draw the entire history under normal conditions: If I extend the filter back to 2005, when our repo history started, ours is also very slow. But if you just focus on the last week, everything will go fast. Now: one thing is redraw, the other refresh. It will probably take you 9 seconds to refresh, but then you can browse the entire graphic quite fast, dragging around. Correct?
  14. Why would you want to do that for a directory?
×
×
  • Create New...