Jump to content
Plastic SCM forums are now in Unity. Click here to open the new forum ×

lrg_steven

Members
 View Profile  See their activity

  • Posts

    23

  • Joined

  • Last visited

 Content Type 

Posts posted by lrg_steven

  1. Error: The file ... is not in sync with the changeset you are working on

    in General

    Posted

    It seems that shelving can sometimes cause this issue. The steps to fix are:

    • Go to the Workspace Explorer
    • Find the file in question
    • Right-click and select History to see the file history screen
    • There will be a list of revisions on the left side and if you're seeing this error, the most recent one is probably not the bold one
    • If you're sure that you want to overwrite the file first backup your changes because the next step will lose them
    • After changes have been backed up somewhere else, right click on the newest entry and select "Revert file to this version"
    • The bold text may not change, but if you re-apply your changes to the file, you can check it in and the new checkin will be bold in the history

  3. "invalid credentials: username or password is incorrect" error preventing me from uploading or downloading changes

    in General

    Posted

    I deleted Plastic entirely, deleted Plastic4 from AppData and deleted all the leftover files in Program Files, restarted my computer, then I reinstalled plastic, pulled a new copy of the repo into a new workspace, manually made my changes to my project again again using WinMerge (from a backup copy of the workspace files), and still I can not push.

  5. "invalid credentials: username or password is incorrect" error preventing me from uploading or downloading changes

    in General

    Posted

    Same behaviour "Invalid credentials, username or password are not valid." popup, but if I commit one file at a time, no errors. I installed the latest version, have signed out and in several times, deleted my client.conf file, and still the error happens when I try to commit new files but not when I'm just committing changes, or just adding one or two files at a time.

  6. cm fast-import to @cloud runs, produces output with no errors, but no files appear in cloud

    in Git interop

    Posted

    I'm trying to move a 30GB repo from git to PlasticSCM. I've followed the instructions here: https://blog.plasticscm.com/2011/10/connecting-plastic-scm-to-github.html

    When I execute 

    cm fast-import repo@company@cloud repo.fe --export-marks=marks.cm

    Everything seems to be running normally. The operation takes a long time and regularly updates its process. It eventually finishes and says what it has detected in the repo but then nothing appears in Plastic.

  7. [Resolved] One-time import of Git bare repo into Plastic Cloud

    in General

    Posted

    I'm glad that I saw this post. PowerShell messes up git exports so badly, it should probably be noted in the docs. The only time I've ever done a git export was for this. I thought it was weird that the PowerShell export took hours and produced a ~50GB file for an ~30GB repo. Doing everything on the normal command prompt produced a ~30GB file in less than a minute and I don't get that weird "]uldn't process command [??b l o b" error when importing.

  13. Can't unlock files on Cloud

    in General

    Posted

    We are having an issue on Cloud where a file is locked, the user who locked the file has nothing in their pending changes, the user can not "Undo Checkout", the repository owner on Plastic SCM can not "Undo Checkout", and "cm unlock" on the repository owner's machine does not unlock the file.

  14. Preventing locking across branches / forking

    in Branching and merging

    Posted

    On 6/7/2021 at 10:41 AM, nahuelarjonadev said:

    I guess the before-checkout operation should verify both 1) that the file is not locked on the central repo, and 2) that the requesting user has the most up-to-date version of the file in comparison to main.

    We're working with Cloud so this type of trigger still seems useful. Though, for 2, we'd want to ensure that the file in our current branch was the most up-to-date across all branches. I looked at the trigger documentation but I did not see a good example of how to do something like this.

  16. Jenkins, problems with cm on Mac

    in Integrations

    Posted

    Did this solution work? The cm integration for Jenkins fails out of the box still on macOS. Since we're just running it as master, the fastest fix was to specify the executable in 

    Manage Jenkins > Configure System > Plastic SCM > Command Line Client Executable: /usr/local/bin/cm

    You can access it using sh if you add it to the path in your pipeline script 

    environment { 
	PATH="/usr/local/bin:$PATH"
}

    Note that updating the path in the script does not fix the original plugin issue.

  18. Environment Variables null in Jenkins pipelines even after successful connection

    in Integrations

    Posted

    The environment variables listed on the Jenkins plugin page return null for me in pipelines (https://plugins.jenkins.io/plasticscm-plugin/#documentation). They are null in both the stage where I do my cm call and other stages. I'm new to Jenkins Pipelines so I'm not sure if there is something simple that I'm missing.

      

            stage('Update Repository') {
            steps {
                cm(
					branch: '/main',
					repository: "${PLASTICSCM_TARGET_REPOSITORY}",
					server: 'mycompany@cloud',
					cleanup: 'STANDARD',
					directory: 'win64'
				)
				echo "${env.PLASTICSCM_CHANGESET_GUID}"
				echo "${env.PLASTICSCM_AUTHOR}"
            }
        }
		stage('Check variables') {
			steps {
				script {
					echo "${env.PLASTICSCM_CHANGESET_GUID}"
					echo "${env.PLASTICSCM_AUTHOR}"
				}
			}
		}

     

×
×
  • Create New...