Bitbucket This Is Not A Valid Source Path

  1. Bitbucket This Is Not A Valid Source Pathway
  2. Bitbucket This Is Not A Valid Source Path
  3. Bitbucket This Is Not A Valid Source Pathogen
Bitbucket This Is Not A Valid Source Path
  • Status:Gathering Impact(View Workflow)
  • Resolution: Unresolved
  • Fix Version/s: None
  • Labels:

After installing/upgrading to Bitbucket server 4.0.2 I am no longer able to Clone in SourceTree.

Steps to Duplicate:

  1. Launch Sourcetree
  2. On the Repository Browser click on remote and you will see a list of repositories on the Bitbucket server
  3. Click clone
  4. Note that there is a message that says 'This is not a valid source path / URL' and the URL looks like: http://[email protected]/stash///git/TEST/test.git
  5. Note that the Source URL has multiple problems:
  6. # The port is missing. I connect to Stash on port 7990 and the port is not there
  7. # The /scm is missing. In its place is just //
  8. # There is an invalid /git in the URL
  9. # The Project is displayed in all uppercase letters

Step 3: Type or paste the repo address into the Source Path / URL box. Choose where you want to store it locally in the Destination Path box. Click the Clone button. Step 4: Enjoy your freshly cloned repo with an origin remote already set up for you. If you're not, then you're stuck in the stone ages) An automated deployment process from bitbucket to repo would save you the extra time spent logging in via ssh, prevent annoying permission issues and add some all round awesomeness to your team 😉. This tutorial is based on the automatic bitbucket deploy repo by bitbucket user @lilliputten. FRACTIONSCAUSAL: This option is only valid if a LDPRED result file prefix is supplied. A list of comma separated (without space) values between 1 and 0, excluding 0. 1 corresponds to the infinitesimal model and will yield results similar to LDpred-inf. Default values are -PS=1,0.3,0.1,0.03,0.01,0.003,0.001,0.0003,0.0001. Enter the full path to the skin data file. The user has the option to use a file browser to save/load the skin data file. Export Skin Data. Executes the command to save the skin data of the chosen geometry. If the file is not valid or not set a file browser is going to be open to give the user the chance of set the parameter on the correct way.

You can also reproduce this by clicking on the Clone in SourceTree button that displays in Bitbucket Server on the repository clone page. In this case the URL is still malformed but it looks different, from the looks of the Source URL (which can not be edited) everything seems correct but you still get the 'This is not a valid source path / URL' messager and you can not click the clone button.

is cloned from

SRCTREE-3182Unable to clone from Bitbucket Server 4.0.2

  • Closed
relates to

SRCTREEWIN-3765Cloning Bitbucket Server 4.0 repositories via Hosted Repositories is not possible due to error in the URL

  • Closed
mentioned in
This

Bitbucket This Is Not A Valid Source Pathway

Votes:
0Vote for this issue
Watchers:
2Start watching this issue
  • Status:Needs Triage(View Workflow)
  • Resolution: Unresolved
  • Fix Version/s: None
  • Labels:

I've seen several other discussions on a similar topic but none of them or their resolutions resolved this issue.

  1. I started with an issue in JIRA
  2. I clicked 'create branch'
  3. Followed the form to clone from a master branch.
  4. Clicked the 'Check out in Sourctree' button.
Bitbucket this is not a valid source pathfinder

Sourcetree opens and I'm presented with the main Sourcetree window, an orange Error 'This is not a valid source path / URL' and a blue 'URL Actions' window.

Bitbucket this is not a valid source pathfinderSource

Bitbucket This Is Not A Valid Source Path

Steps I have taken to attempt resolution are below. I re-attempted after each step.

  1. I have git installed on my machine and have tried switching to embedded git in Sourcetree.
  2. I enabled and downloaded embedded Mercurial in Sourcetree.
  3. I've successfully configured my SSH key and can view and clone and fetch repos from bitbucket within Sourcetree directly.
  4. I switched to an App Password and verified connectivity.
  5. I changed my authentication protocol to HTTPS and verified connectivity.
  6. I switched my authentication to basic and verified connectivity.

I consistently get the same error message and am unable to check out the branch in Sourcetree.

Let's encrypt xampp password. Download the letsencrypt-win-simple from github. We will use a third party tool.

Assignee:
Unassigned
Reporter:
Jonathan Adlerstein

Bitbucket This Is Not A Valid Source Pathogen

Votes:
0Vote for this issue
Watchers:
2Start watching this issue