Forge-cli install invalid workspace

Hi,

We’ve been having a strange issue when running a forge install of an app. If we provide the site with the URL formatted as "https://bitbucket.org/<workspace_name> (see screenshot below), it keeps telling us it’s not valid.

Things to consider, if it helps to give some context: the “forge install” command is being run on a RHEL server acting as a Jenkins slave, with a particular version of Node behind, and the whole process is part of a groovy pipeline.

Is there a specific syntax or format when passing the site as an argument for the install command? We literally have no clue what could be wrong.

Thanks a lot for your help.

We found the problem.

As it turns out, forge does some kind of “translation” from ‘https://bitbucket.org/<workspace_id>’ to ‘https://api.bitbucket.org/2.0/workspaces/<workspace_id>’ and we found out that the server itself can’t reach that endpoint (it gives a 503 code). That’s why it is identified as an invalid workspace.

In the end, it seems this is just a firewall issue.

Thanks anyway.