Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-4052

When cloning a project from a specific branch using oauth, the working copy is placed in a 'project-clone' folder

    XMLWordPrintable

Details

    • False
    • None
    • False

    Description

      Description of problem:

      When creating a new devspace with the following criteria:

      • using a private Gitlab project
      • using an oauth token
      • specifying a non-default branch in the factory url
      • using the vscode editor

      the workspace clones the project into a 'project-clone-...' folder suffixed with a timestamp. Each time the workspace is restarted a new project-clone folder is created with a different timestamp

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Create a new private gitlab project with a new branch 'oauth'
      2. Create a devfile similar to the one attached and add it to the 'oauth' branch
      3. Create a .che/che-editor.yaml file with the content `id: che-incubator/che-code/insiders` and add it to the 'oauth' branch
      4. Set up devspaces with a gitlab oauth token
      5. Create a new devspace using the 'oauth' branch with the factory url `https://\{devspaces-url}/#https://gitlab.com/\{project-path}/-/tree/oauth`

      Actual results:

      Expected results:

      Reproducibility (Always/Intermittent/Only Once):

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

      Attachments

        Activity

          People

            amisevsk Angel Misevski
            myarbrou@redhat.com Michael Yarbrough
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: