Jump to content

notken

Members
  • Posts

    40
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by notken

  1. Hi there. Our company insurance is due for renewal, and as part of the questionnaire we are being asked if all of our network services require 2FA/MFA. It struck us that Plastic SCM Cloud doesn't require it.

    We have strong passwords and an encryption key on Plastic, but I noticed that you do have 2FA as an option when logging in using Unity. Nevertheless there doesn't seem to be any way to make it a requirement.

    Is that possible, for an administrator to require 2FA for all users? Or is username/password always going to be a possibility?

  2. Is there some issue I'm not aware of? The Unity uptime page has green everywhere. But any single Plastic UI operation is taking 30-60 seconds to happen. Checking in a tiny XML file took over a minute. Changing branches usually times out.

    I've tried rebooting and resetting the Plastic services. I've checked with colleagues working in different locations on personal Internet connections and they're having variable but slow results too.

  3. I agree. It's been a very reliable service. But I reported everything we experienced today so that you can make it even better. If it can't authenticate perhaps it should time-out more quickly and report it to the user. I had rebooted my PC initially thinking it was me.

    Thanks for the status link.

  4. Just now, calbzam said:

    The www.plasticscm.com web was down for a few minutes.

    Is that connected to the cloud service? Because that was down for about 30 minutes.

    I get that these things can happen but I was just hoping that if it happens again it could be handled better by the clients. They need to time-out far quicker and return control to the user. I hoped it would only be for a short time so didn't do anything on my machine, but I think I might have had to uninstall Plastic to get Visual Studio to be usable.

    Previously too you've directed people to the Azure status page to see if the Cloud version is down, but Azure's status pages had green ticks everywhere. Could you maybe have your own status service too?

  5. After a *long* time - 20 minutes plus - the command line finally returned "Error: SSL negotiation with server Games_Press_Ltd@cloud failed. Authentication failed because the remote party has closed the transport stream."

  6. Hi there. I've opened Plastic SCM UI and it's stuck with a blank Workspace Explorer. The Gluon UI is constantly spinning "Loading", and the command line is stuck processing "cm status" in a workspace folder.

    I couldn't get on your Web site just now although that seems to be working again after a brief 503 error appeared.

    I take it this is an unexpected downtime, but any idea how long it will be, or if it can be handled better? Everything just looks like it's hanging right now. I can't even switch back to the main UI. Visual Studio won't even open presumably because the plugin is hanging.

  7. Hi Carlos. I downloaded yesterday's update as I saw there was mention of supporting Jira API keys, but now I can't even get a successful test connection to Jira. And still the plugin doesn't work.

    I couldn't delete the folder because there was a lock on it, but I did manage to delete the jira.conf file and all but the ssl_games_press_ltd@cloud folders, and the preferences do now 'stick'.

    Is this a known problem about the plugin and Jira's requirement to use API keys now? It doesn't look like the plugin works at all any more.

  8. All repos. The values aren't *blank* but they were reverting to the old values. What seemed to be happening is that it was saving them to jira.conf in the Games_Press_Ltd@cloud/allrepos folder, but reading the values back from ssl_games_press_ltd@cloud/allrepos

     

    Here's my jira.conf (minus the password):

    WorkingMode=TaskOnBranch

    Name=Host;Value=https%3A%2F%2F[removed].atlassian.net;Type=Host;IsGlobal=True
    Name=User name;Value=[removed];Type=User;IsGlobal=False
    Name=Password;Value=[removed];Type=Password;IsGlobal=False
    Name=Branch prefix;Value=JIRA-;Type=BranchPrefix;IsGlobal=True
    Name=Project Key;Value=MULTIPLE_PROJECTS;Type=Text;IsGlobal=True
    Name=Custom Field ID;Value=10016;Type=Text;IsGlobal=True
    Name=Use LDAP credentials if available;Value=False;Type=Boolean;IsGlobal=False
    Name=Use default proxy credentials;Value=False;Type=Boolean;IsGlobal=False
    Name=Issue query limit;Value=50;Type=Text;IsGlobal=False
    Name=Resolved issue states;Value=Done%2CMade%20Live%2CChecked%20In;Type=Text;IsGlobal=True
    Name=Issue types;Value=;Type=Text;IsGlobal=False
    Name=Fields mapping;Value=issue.Fields.Description-%3EDescription%7Cissue.Fields.Reporter.Name-%3EOwner%7Cissue.Fields.Summary-%3ETitle;Type=Text;IsGlobal=False
    Name=REST URL;Value=%2Frest%2Fapi%2F2%2F;Type=Text;IsGlobal=True
    Name=Task URL;Value=%2Fbrowse%2F;Type=Text;IsGlobal=True
    Name=Status transitions;Value=;Type=Text;IsGlobal=True
     

    While the test connection is fine, none of the integrations are working any more. We're still looking into that.

  9. This bug seems to have come back, but the solution isn't working any more. Jira no longer accepts username and password and needs a token instead (which you can use just like a username and password *I think*). But it won't save on version 8.0.16.3310.

    What I'm finding is that it's saving it to the non-SSL version of the conf file, but then reading it from the SSL version.

    My solution is:

    1. Set the values, test, and then save.
    2. Close Plastic GUI
    3. Go to c:\windows\users\[username]\AppData\Local\plastic4\issuetrackers\[non-ssl-server]\allrepos
    4. Copy jira.conf which should have today's timestamp
    5. Paste into c:\windows\users\[username]\AppData\Local\plastic4\issuetrackers\[ssl-server]\allrepos
    6. Re-open Plastic GUI

    The new values are now present. (The new Jira integration still isn't working but at least it connects!)

     

    UPDATE! This didn't work for a colleague who didn't even have an [ssl-server] folder. He's created his own and that has worked though.

  10. Hi there. We've recently moved to the Cloud edition from Team, and I've just run into an unexpected problem: we can't move a changeset into a new branch.

    We use branch per task, but sometimes we'll test if we actually do need to make changes from the main branch. That means if it's a quick fix I'll sometimes forget to create a new branch before making the change, and might even check it in before realising I haven't created a new branch. Under Team that wasn't a problem as I can just move the changeset to a new branch. But when I tried it in Cloud I was told it wasn't supported yet.

    I then thought I'd just recreate the change in a new branch and copy the code to that, before deleting the changeset in main since it was at the head, but apparently deleting changesets *also* isn't yet supported in the Cloud edition.

    These both seem like fairly common and not overly complicated operations, so I'm really surprised and disappointed we can no longer do it. Is there an ETA for when these features are going to be added, or will the Cloud edition *never* support them? I was lucky that I discovered this on a quiet work day because I can imagine it being more of an issue another day with changes accidentally making their way into main branch before they've been properly reviewed.

×
×
  • Create New...