531 results found

1. Provide changeset-id's in update triggers

   Now, the update triggers only provide a path to the workspace being updated.
   Having access to the old and new changeset-id's opens up quite a lot new possibilities.

   For example, in UE4, when working with plugins in a code project, they are compiled automatically at first. When making code changes to the plugins, they are often not automatically detected which causes the engine to crash at startup.
   Deleting two specific folders makes the engine recompile those binaries automatically and thus fixes this inconvenience. Unfortunately, this process takes about 5 minutes on average so doing it after every update is not feasible.
   By providing a specific string/tag in the comment of checkins that require a compile, we are able to only recompile when necessary.

   In order to make this work, we have to write out the current changeset-id to a file in the before-update trigger. Then in the after update trigger, we get the current one. Finally we would use the find command to get all changesets in between those two and check if any of their comments contain the tag.

   We are already able to access the current changeset-id with
   cm status --nochanges
   and some parsing. (Although this could be made easier.)
   Thus, only exposing the future changeset-id in before-update and the previous changeset-id in after-update would suffice.

   Thanks in advance

   Now, the update triggers only provide a path to the workspace being updated.
   Having access to the old and new changeset-id's opens up quite a lot new possibilities.

   For example, in UE4, when working with plugins in a code project, they are compiled automatically at first. When making code changes to the plugins, they are often not automatically detected which causes the engine to crash at startup.
   Deleting two specific folders makes the engine recompile those binaries automatically and thus fixes this inconvenience. Unfortunately, this process takes about 5 minutes on average so doing it after every update is not… more

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Sync, Repos and Workspaces on their own tab

   Hi,

   Since the latest release it's possible to close the tabs in the caption area.

   Great feature but I would like one more enhancement, a non closeable tab (preferably the first tab on the right) that contains non workspace related subtabs like Your Workspaces, Your Repositories Rss Notification and Sync replication (not sure about Shelves).

   This way the workspace related tabs stay cleaner (and smaller).

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   started  ·  AdminCodice Software (CEO / Founder, plasticscm) responded

   Actually we started doing this on the new Mac and Linux GUIs :-) The new GameUI also supports this mechanism. Soon we’ll have it on the regular Windows GUI.

3. Add a context menu to the 'Checking pending changes' window

   There is no context menu available for changed files in the 'Checking pending changes' window. However, there is a similar view in the 'Pending changes' tab of PlasticSCM's main window and a context menu is available there.

   The thing is that the context menu enables you to view changes using a diff tool you prefer (the one set in application preferences). In the window mentioned in the topic there is no such menu at all and you can view changes only using the diff tool embedded inside that window.

   Most of us in our company are used to WinMerge and we would like to continue using it with PlasticSCM. The 'Pending changes' view enables you to do that, but I think you rarely use it when managing source code changes directly from Visual Studio (which displays the discussed window).

   There is no context menu available for changed files in the 'Checking pending changes' window. However, there is a similar view in the 'Pending changes' tab of PlasticSCM's main window and a context menu is available there.

   The thing is that the context menu enables you to view changes using a diff tool you prefer (the one set in application preferences). In the window mentioned in the topic there is no such menu at all and you can view changes only using the diff tool embedded inside that window.

   Most of us in our company are used to WinMerge and… more

   14 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. automated replication

   I'm working on a main computer and a laptop for when i'm on the road.
   When i'm working on my laptop I would like to have it automatically push changes to my other computer or the central server when I check-in a change-set.

   Also i would like to be able to subscribe to a repo of specific branches so it automatically pulls changesets from the central server or the computer.

   14 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Secure code reviews

   Right now there is no mechanism to prevent users from deleting code reviews (unless I've missed something obvious), which is a problem for what we're trying to do. If nothing else it would be nice to have a "before-rmreview" trigger that we can hook into

   14 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Add "Update Cloaked" (and "Update Forced") to Items context menu.

   If i have items or xlinks specified in cloaked.conf, the only way to force an update of these is to:

   • either removed them from cloaked.conf before "Update workspace"

   • or run "cm update --cloaked <path>" from the command line.

   NOTE: Contrary to old documentation, running the "cm update --forced <path>" command will not update cloaked stuff.

   I suggest adding a "Update Cloaked" command to the context menu in the Items view. Maybe also an "Update Forced" command, but this is probably less important.

   14 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Improve vertical ordering in Branch Explorer, make use of hierarchy

   The default ordering of branches in Branch Explorer could be improved. It should respect and make use of the branch hierarchy, so as not to cross lines unnecessarily.

   When I have several top-level branches with some child branches each, they are not grouped together vertically in a hierarchically logical order. Instead they seem to be randomly placed (?) leading to a lot of lines crossing each other. (I always enable "Display cross-branch changeset links" which makes this more obvious.)

   I think child branches should always be displayed below their immediate parent (or sibling if multiple children overlap in time).

   14 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   7 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Branch explorer: make "cross-branch changeset links" clickable like merge arrows

   On merge arrows, we can click and get a tooltip of info (changeset and branch of source and destination, respectively). We can also right-click and choose commands "Go to source/destination changeset".

   I suggest making the "cross-branch changeset links" (branch base/parent & child relation lines) clickable in the same manner.

   You could display the following tooltip info:

   • base/parent changeset number,
   • base/parent branch name,
   • child branch name

   Also, you could provide the following right-click commands:

   • Go to branch base / Go to parent changeset,
   • Go to child branch

   The first command would be much more intuitive than first locating and selecting the child branch, then right-click and choose "Branch Explorer - Go to branch base". And for the second command, there is no equivalent currently in the UI.

   We have a very large tree of branches (when not applying filters) and navigating the branch explorer can be daunting sometimes. A single merge arrow or branch-relation line can stretch across several "screens" both horizontally and vertically. It's easy to get lost, especially since there is currently no way to follow a branch-relation from base to child, only the other way around.

   Thus, the suggested feature would IMHO simplify branch navigation immensely!

   On merge arrows, we can click and get a tooltip of info (changeset and branch of source and destination, respectively). We can also right-click and choose commands "Go to source/destination changeset".

   I suggest making the "cross-branch changeset links" (branch base/parent & child relation lines) clickable in the same manner.

   You could display the following tooltip info:

   • base/parent changeset number,
   • base/parent branch name,
   • child branch name

   Also, you could provide the following right-click commands:

   • Go to branch base / Go to parent changeset,
   • Go to child branch

   The first command would be much more intuitive than first locating and selecting the… more

   14 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. provide an increased level of support for the eclipse ide platform.

   Basically the visual studio plugin for PlasticSCM is very powerful, however the majorly popular Eclipse IDE open source platform plugin is very very limited. I'd like to see an increased level of support for this platform as I'm sure many others would as well.

   13 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Better issue tracker API

    Here are a few ideas for an improved issue tracker API. These suggestions were first posted in the forum 05 December 2011.

    Create branch from ticket
    I was surprised that I could not create a branch from a list of tickets. Instead I have to use a branch name convension to link my branch to a ticket. It should be trivial to extend the extension API with a "load tickets" method and present the list of tickets when creating a branch. How to select the tickets to be shown could be a matter of extension configuration. This could be made even better if the API could make the extension provide a list of filters to choose from.

    It is not that it is a big issue to use the branch naming convension, but it would allow a more smooth workflow if the list of tickets was integrated with branch creation.

    Two way state synchronization
    I was also surprised that the extension seems to be a one way system with no support for adding states or comments to the ticketing system.
    I had expected to find a "hook" to branch switching or creation. That way it would have been possible to change ticket state from say "new" to "open".
    If the ticket properties, especially state, were synchronized with Plastic attributes, it would provide a very convenient way of filtering branches when integrating completed tasks for a build.
    If there was a "hook" for changeset comments, changeset comments could also be added to the ticket comments. This would provide possibilities for a detailed change log.
    Two way states and events on commits, branch switches, etc. is what I miss the most.

    Caching
    I would benefit performance if every branch explorer refresh didn't caused a complete loading of all issue tracker tasks in view. You might expect the branch explorer to attempt a refresh if you hit the refresh button, but it the refresh fails, for example if you are offline or the ticket server for some reason is not available, then all your ticket titles disappear. This is a problem if you have adopted a ticket id branch naming scheme. It would be better, if Plastic cached tickets and only replaced titles if a new was actually loaded. Also, why is the extension asked to load a ticket both by the branch explorer and when clicking on a branch?
    I do however realize that the extension could do such caching by itself, but it would be easier to develop extensions if such behavior was implemented in the calling system.

    Repository mapping
    I found the repository to ticket system project mapping a little clumpsy in the API. E.g. when refreshing the branch explorer, the extension is asked to load tickets for all visible branches, but with the empty string as repository name. Only when clicking on a branch, the repository name is provided. There is probably an explanation, but it made it hard to map repositories with projects in the ticketing system. This is a problem for ticketing systems like YouTrack, where the project name (in short form) is part of the ticket ID and IDs within projects are sequential (i.e. non-unique globally).

    Auto comments
    In Plastic preferences you can setup auto-comments. You can choose between user name and date. This is almost entirely useless since that information is already baked easily available.
    When using build servers like TeamCity, you get some nice links to your ticketing system if you refer to ticket id's in the comments. A typical workflow is making a solving a bunch of tickets and then integrating the branches in a build branch that the build server will use to generate a new build. In the process of integrating branches, it would be helpful if the comments automatically the ticket ids, since this would make a full circle between the VCS, Build server and ticketing system. Manully entering these comments is tidious and error prone, since it is often only a matter of repeating branch names and ticket titles.
    It would be nice if the "custom" auto-comment formatter was extended more tags. Most obvious are branch name, ticket title, ticket id, ticket description.

    Here are a few ideas for an improved issue tracker API. These suggestions were first posted in the forum 05 December 2011.

    Create branch from ticket
    I was surprised that I could not create a branch from a list of tickets. Instead I have to use a branch name convension to link my branch to a ticket. It should be trivial to extend the extension API with a "load tickets" method and present the list of tickets when creating a branch. How to select the tickets to be shown could be a matter of extension configuration. This could be made… more

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. goto child changeset

    In branch explorer there is a 'goto parent changeset' context menu. A similar one for children, possibly listing multiple branches, would be useful. Navigation is quite difficult in this direction.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Have a mechanism to split repositories

    It would be very helpful if there was a means by which certain directories/paths could be moved from 1 repository to another, complete with history.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Possibility to undo checkout without loosing file content changes

    Let the user undo a checkout without loosing the modifications themselves. The result would be a file with status "Changed".
    Neither the content nor the file's timestamp should change by this operation.
    Currently, undoing a checkout always results in downloading the versioned content.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    8 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Auto Refresh Branch Explorer Option

    An option to refresh the branch explorer automatically would be nice. Similar to Auto Refresh Pending Changelist Option.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Implement cloud-based backups for Plastic Cloud

    I propose that Plastic Cloud offers an incremental backup method. It should export backup data to customer-provided cloud storage (AWS S3 / Google Cloud Storage / Azure Storage), perform backups with high frequency (possibly with a combination of full / incremental backups), and only leave the responsibility of validating these backups with the customer.

    Our use case:

    We use Plastic Cloud instead of Plastic Server, because it reduces our operational overhead. Plastic Cloud is great in many ways, but using it means that we also entrust the responsibility of availability, security, as well as backups/disaster recovery with Codice Software.

    As our organization grows larger and older, we need to have shared responsibility for backups/disaster recovery. If we ask ourselves, "do we have backups?" then we must be able to answer "yes, and we have verified that they are not corrupt", not "yes, we trust that another organization does it for us".

    It is possible to handle backups today: run a local Plastic Server, scan the Plastic Cloud organization, replicate what's in there to local repositories, then archive the local repositories. However, that requires a fair bit of operational work.

    I would like to see that Plastic Cloud offered an 'automated backups' feature: I provide details on a customer-controlled cloud storage bucket in a cloud provider like AWS/GCE/Azure, and credentials that allow Plastic Cloud write-only rights to the bucket (without the rights to modify what's already in the bucket). Plastic Cloud would then regularly export changes to the bucket. For example, a full export once per month + an incremental export once per day. I would like notifications to be sent to me (for example via emails) whenever there is a problem with export process, as well as summaries of this somewhere (for example within the weekly digest emails that are sent out).

    I would like validation to be left with the customer (although someone will probably ask for some degree of automation here as well). As such, I expect that I can restore a backup - or perhaps part of a backup, like, only a single repo - into a local Plastic Server and then be able to access the contents directly.

    The automated "export to cloud storage bucket" process will allow us to easily implement any process we would like for further backups (for example, manually copy backups from cloud bucket to offline storage).

    It would be helpful to be able to be able to get some idea of the contents of a backup without needing to perform a full restore. (Example: which repos are inside the backup? what is the range of changesets contained within the backup?) This could either be a tool that inspects the backup files itself, or additional text file(s) that are written at the time when the backups are created.

    One nice side effect of a backup mechanism like this is that it provides us with the ability to recover from some of our mistakes, that would otherwise require contacting Codice support.

    The feature requires additional backend-side processing and network transfer. We are happy to pay extra for this.

    (Slightly related, there is a cloud-to-cloud backup service for GitHub: https://backhub.co/ - this has a much broader featureset than suggested above, but it demonstrates the core need.)

    I propose that Plastic Cloud offers an incremental backup method. It should export backup data to customer-provided cloud storage (AWS S3 / Google Cloud Storage / Azure Storage), perform backups with high frequency (possibly with a combination of full / incremental backups), and only leave the responsibility of validating these backups with the customer.

    Our use case:

    We use Plastic Cloud instead of Plastic Server, because it reduces our operational overhead. Plastic Cloud is great in many ways, but using it means that we also entrust the responsibility of availability, security, as well as backups/disaster recovery with Codice Software.

    As… more

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. in file history change workspace

    Add option to right click in file history to change the workspace to the changeset selected.

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. When entering visibility mode, it would be useful to keep conditional format colors rather than moving them to the navigator.
    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Show at least one changeset in queries

    With some (external) repositories last changes are sometimes so long ago that nothing shows up in for example the xlink changeset selector.

    So please show at least the last release if the query does not return results. This behavior should also be implemented for other query based views. Maybe with a switch in the preference to turn it on/off.

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. To have the possibility of add general comments per code review and per file in the code review

    I would like to don't be forced to always attach a comment to a concrete line. I want to have the possibility of adding general comments to the review and to files in the review

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. VS plugin: Add in-editor diff markers with associated commands

    We were using the VisualSVN plugin for Visual Studio before, and we miss the excellent "Quick Diff" feature: https://www.visualsvn.com/visualsvn/features/

    This feature replaces/enhances the "Track Changes" markers in the Visual Studio code editor with colored lines (in the left margin), to indicate blocks of lines that are changed relative to the latest changeset (different colors for modified, added, deleted). It also adds commands (revert block, navigate prev/next change block).

    There are some other (open source) plugins that offer similar functionality: "Git Diff Margin", "TfsPendingChangesMargin", "HgVS".

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close