Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About M-Pixel

  • Rank

Recent Profile Visitors

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

  1. M-Pixel

    Git clean equivalent

    `% { rm $_ }` does not work from a cmd file. Also, `rm` will only work on Windows if you've installed unix command line tools, which is not a prerequisite for using Plastic. Many people will not have that command available. Here's a "hard reset.cmd" that I use on Windows: @echo !!!!!!!!!!!!!!!!!!! @echo !!!!! WARNING !!!!! @echo !!!!!!!!!!!!!!!!!!! @echo You are about to delete all ignored and private files. @echo Please make sure that you haven't forgotten to check in or shelve any of them. @pause for /F "usebackq tokens=*" %%I in (`cm status --private --ignored --short .`) do ( del /A /Q "%%I" rmdir /S /Q "%%I" rmdir /S /Q "%%I" ) It's certainly ridiculous, especially the fact that rmdir is required twice in a row, but it's closest I was able to get to removing the files and directories in Windows. And even still, some files could not be deleted with these commands. The script could be simpler if it were a PowerShell script, however that would require some setup in order to run as conveniently as a cmd file. It's slower than it needs to be because if a folder is ignored/private, then this command will waste time deleting each item contained in the folder individually. I think that this is a pretty compelling use case to add a native cm clean command, so I hope Codice reconsiders their response to the former feature request mentioned above.
  2. M-Pixel

    Where can I find documentation on how to use ignore.conf?

    So, if I wanted to say "ignore everything in A except for cs files, and ignore absolutely everything including cs files in A/B", then that's impossible in Plastic SCM? That's very inconvenient for users of Unreal Engine because of the way it intersperses generated and downloaded files throughout the directory structure. Git supports this sort of arrangement very easily by giving increasing priority to each line in the ignore file.
  3. M-Pixel

    Where can I find documentation on how to use ignore.conf?

    This is definitely not the case (at least, not in 2017, maybe it was in 2014). Given ignore * !*.cs obj and workspace ignore.conf Program.cs obj/ someAutomaticallyGenerated.cs someAutomaticallyGenerated.cs shows up despite the fact that its parent folder is ignored. Even changing `obj` to `obj/**` did not change anything
  4. M-Pixel

    Best way to track Git + fork(s)

    I've discovered that Git Sync works on a repository level, not a branch level. So it's impossible to sync simultaneously with multiple Git repositories. The solution that I intend to use now is to migrate updates from upstream repos to fork repos using a local intermediary Git repository, while syncing Plastic only with the leafmost Git repository.
  5. M-Pixel

    Gluon via CM

    I'm working on a script for work environment setup, something that installs and configures the software necessary to develop the product. I found the command line parameters unattended installation, which covers installing Gluon. The final step that I'm working towards is setting the branch of the workspace, but before that can happen the workspace needs to be created, configured, and updated. Using cm, what commands should I use in order to make sure that my workspace is 100% Gluon-compatible?
  6. M-Pixel

    Best way to track Git + fork(s)

    Here's the scenario: Foo has repository Bar on GitHub SuperCow has repository Baz on GitHub, which is a fork of Foo/Bar I want to, in turn, fork Baz as a Plastic SCM repo, while retaining the ability to merge and cherry-pick from Baz and Bar, and the ability to contribute to Baz. After doing a bit of reading, my intuition is that I should create a repository where the main branch is synced with Foo/Bar, a child branch is synced with SuperCow/Baz, and a subsequent child branch that I use for development. The documentation doesn't cover any scenarios that involve multiple Git repositories, fork or not, so I figure there is probably something wrong with my suggested approach, or, at the very least, gotchas that I should be aware of.
  7. M-Pixel

    multiple root branches

    I see that it's possible to create additional branches at the root level (e.g. create `/foo` instead of `/main/foo`). What are some potential use-cases for this? What are the advantages and disadvantages of each?
  8. I've got a cloud subscription - a few other developers and I have been using it for a few months on other machines both with and without local servers. I have a fresh install of plasticscm-cloud version on OpenSUSE. After signing into my cloud account in the main interface, and enabling the local server daemon service, I find that I'm able to connect to without any trouble. When I try to do anything with it, though, I get an error window that says "Limited by days evaluation license has expired." I couldn't find anything in the configuration guide about directly configuring the local server, apart from creating Sync Views. There are currently zero Google search results for the error message I'm receiving. I also notice there's an info message that says "It seems you don't have a Plastic Cloud organization yet" in my GUI. No results for that either. So what needs to be done here? Is there some sort of log-in process that I can do from the server CLI? Or if it's best to wipe all local configuration and start over, where are all of the files I would need to delete in order to accomplish that?