0

We're using octo.exe to create releases. It starts suddenly giving error saying can't find project. I checked the api/projects and that's true, it is not in the returned json response. But when I look at the dashboard I can see the project. The only thing I did was cloning another project from this one earlier. The cloned project is working fine but not the original project.

It exists in dashboard (web gui) but not in api (hence octa.exe can't find project)

Looks like api is caching the projects. The new projects that I created via GUI not available in api.

Thanks,

Zerdush
  • 13
  • 4
  • 1
    Which version of Octopus are you using? It might be easier to contact support for issues like this. support@octopusdeploy.com – Paul Stovell Nov 30 '14 at 20:54
  • If it's quick and easy, backup the Octopus Deploy database and recreate the project. – Kye Mar 01 '15 at 10:07

2 Answers2

0

I have had the same issue yesterday. It turns out to be something interesting. I believe that your project is still there properly set, but the total number of projects that you have become more than the listed ones in the API, and that's why the Octo.exe couldn't see it anymore.

I have explained here, how I managed to fix that issue quickly.

Danko Valkov
  • 1,038
  • 8
  • 17
0

This is due to how pagination is implemented in Octopus (pretty poorly if you ask me). But you can override it. add this to the URL (at the end).

'?skip=0&take=2147483647'

alternatively, you can watch the json returned, if you find the links.Page.Next property you can use that link to get next page of the api response.

4c74356b41
  • 69,186
  • 6
  • 100
  • 141