Jump to content

M-Pixel

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About M-Pixel

  • Rank
    Newbie
  1. 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
  2. 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.
  3. 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?
  4. 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.
  5. 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?
  6. 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 6.0.16.884-2.1 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 127.0.0.1:8087 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?
×