Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

152 results found

  1. If one company has 2 repositories syncronized, because it has 2 headquarters and it speeds up the process, then reviews done in one repository is not reflected in the other, turning reviews useless in this sceneario. Ideally, like changesets, branches and so on, code reviews should be in sync too

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  2. Allow modifying the PLASTIC_COMMENT environment variable from within before-checkin trigger process.

    My particular scenario is to enable VCS Commit Comments integration in Teamcity with Youtrack. using branch-per-task, the branch name can be used to extract ticket ID..

    for example .. for branch /main/yt_ADMINPORTAL-232 the ticket id is ADMINPORTAL-232... with this change, I'd create before-checkin trigger to modify the checkin comment by appending a line at the end:

    my comments here...

    ADMINPORTAL-232

    https://www.jetbrains.com/help/youtrack/standalone/Apply-Commands-in-VCS-Commits.html#vcs-commit-command-syntax

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  3. Plastic SCM lost all its settings and user settings when uninstalling Python.
    Uninstalled Python 2.7 and Python 3.6 ( Work related ).
    Then everything was lost in Plastic SCM, server, filters, colors.. everything.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Custom Checklist is very useful if you can't setup files to ignore.conf or hidden_changes.conf

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  6. The graphical branch view is fantastic, that said sometimes its helpful to see a list of all branches and the folders they are under. This is especially useful when using the gitflow model.

    Introducing a view that shows a list of all branches and the folders they reside under would be very helpful.

    Keep up the great work!

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Want to be able to select a wrike task from within the Plastic SCM to link a task to.

    Would also be handy to automatically create wrike tasks when a code review is created and for it to assign the the user.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  8. It would be useful while using xlinks.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  9. En vez de solo permitir/denegar borrar changeset, tener la opción de ser más flexibles, y permitir activar la opción de borrar los changeset propios, un usuario podría borrar sus propios changeset, pero no los de otro

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Borrar una rama cuando tiene changeset o poder seleccionar varios changeset para borrarlos de una vez

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Deleting changesets is extremely dangerous, and people end up complaining they deleted what they shouldn’t :-) Not the first time it happens.

    We have an option to remove csets from command line, which will probably suit your needs :-)

    bcm changeset remove —help
    Remove a changeset from the repository.

    Usage:

    cm changeset remove | rm

    Options:

    cset_spec The target changeset to be removed. It must fulfill some specific conditions. See help for further details.

    Remarks:

    - The target changeset must be the last in its branch. - The target changeset cannot be the parent of any other changeset. - The target changeset cannot be neither the source of a merge link nor part of an interval merge as source. - No label must be applied to the target changeset. - The target changeset must not be the root changeset (cs:0)

    Examples:

    cm changeset rm cs:4525@myrepo@myserver cm changeset remove cs:cb11ecdb-1aa9-4f11-8698-dcab14e5885a
  11. Ability to apply color to branches (simple but usefull tool). All of us works on separate branches and we have as well our "under dev" or task specific branches. We merge from and to only using our main branches. Colorcoding is very intuitive way to differentiate "development/beta" branches from final branches

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. We are signed up to Atlassian's services like JIRA and Confluence on their cloud. We also use Google Apps for Business. We were hoping to use Google as our central employee/user management place seeing as we can easily login to JIRA etc after linking up the Google accounts. However I found out that Plastic SCM doesn't yet support this integration with Google. I found this frustrating because I created a bunch of tasks for our Unity developers but when they went to submit their work via the Unity Plastic SCM plugin they weren't able to login using the Google-provisioned accounts.…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Have you thought about adding analysis tools such as temporal coupling diagrams (https://youtu.be/0oDporwhToQ?t=1502) and fractal figures (https://youtu.be/0oDporwhToQ?t=1819) into your product?

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  14. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. The Jenkins PlasticSCM plugin uses the same setting for workspace name and workspace directory.

    This prevents Jenkins from creating multiple workspaces on the same machine in the case below.

    e.g.
    c:\project-a\mywksp
    c:\project-b\mywksp

    Current behaviour is for Jenkins PlasticSCM plugin to create c:\project-a\mywksp with name mywksp. Then when creating c:\project-b\mywksp will use mywksp and overwrite the first workspace.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hi RichT,

    We consider this is a configuration issue, rather than a lack of functionality. The workspace name property can be edited in Jenkins to take advantage of the Jenkins build variables (such as JOB_NAME and NODE_NAME). That way you can have unique workspaces for each project or build agent. You can see this configuration in action on the Plastic SCM Jenkins plugin website: https://wiki.jenkins-ci.org/display/JENKINS/PlasticSCM+Plugin.

    Thank you for your feedback!

    Regards,
    Miguel

  16. I would like to be able to select at line level granularity, which hunks of a pending changes diff will be committed to a changeset, so that I may make different commits that split up changes along functional lines / with finer granularity. Any parts of the delta that are not committed should remain as pending changes.
    This would make it easier to allow selective merging of specific parts of functionality by cherry picking at changeset level.
    Coupled with some functionality to be able to split existing commits along similar lines, this would be a rather nice feature (maybe by…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Recently I have to switch between servers very often. In office it's intranet - at home a vpn. But there is just one input box which allows only a single url which is very inconvenient to use.

    Much better would be to have a dropdown with all the server addresses being used.

    The checkbox for "ssl" should be obsolete. You can determine if it's ssl connection from the address itself: "ssl://".

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. This is the same scm context menu you get when right clicking on a file in the solution explorer but means you don't have to navigate to the file to do this operation. You'd just right click on the file tab instead.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. In the global config (special repo: plastic-global-config) one can put a "<repo>/workspacetree/" sub-directory for keeping the following files:

    • ignore.conf
    • cloaked.conf
    • hidden_changes.conf
    • writable.conf / readonly.conf
    • filetypes.conf
    • semanticexcluded.conf (suggested?)

    This idea could be extended to normal repos! Being able to put all these .conf-files under a "workspacetree" directory in the repository (or local workspace) root would reduce the clutter and make it easier to locate these config-files.

    NOTE - The semanticexcluded.conf file does not currently work in these scenarios, but there is another uservoice suggesting that it should: https://plasticscm.uservoice.com/forums/15467-general/suggestions/13439505-make-semanticexcluded-conf-file-work-from-wkspace

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Locking certain files are that common thing to do for every project that this task should have a simple gui. Not everybody likes it to mess with config files.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  • Don't see your idea?