As per the screenshot, when trying to use octo.exe create promote-release I get the following error:
Release ‘0.3.4195’ of project ‘SolvAPP’ cannot be deployed to environment ‘PROD 02’ because the environment is not in the list of environments that this release can be deployed to. This may be because a) the environment does not exist or is misspell ed, b) The lifecycle has not reached this phase, possibly due to previous deployment failure, c) you don’t have permission to deploy to this environment, or d) the environment is not in the list of environments defined by the lifecycle.
The project, deployto and from parameters are spelt correctly and are in the right case. As per the screenshot I am able to deploy the release mentioned from QA to PROD - 02.
Command Line Tool Version: 4.31.1
Octo Version: 4.0.10
If anyone has suggestions on how to fix this issue it would be greatly appreciated.
thanks in advance
Thanks for getting in touch! I appreciate you sending through those screenshots. From the Octo.exe screenshot, it looks like the promote-release command is targeting a project called
SolvAPP, though the screenshot of your web portal is in the project called
SolvAPI. Is it just that slight misspelling that’s caused this unexpected behavior by chance?
I look forward to hearing back!
Thanks for your reply, I apologise the screen shot was slightly incorrect we have a SolvAPP and SolvAPI project in octo. I have updated the screen shot so we are comparing apples with apples.
Hopefully there is something else you can pick up that is incorrect.
Thanks for confirming that, and no worries! Everything else in the screenshots seem to line up. Can you confirm if this API key belongs to this same
admin user you’re logged in with in the portal? I assume they have adequate permissions to deploy this project to Prod - 02, but if you’re unsure you can test their permissions in the portal under Configuration > Test Permissions, and select the user. Can you also send a screenshot showing the configuration of the lifecycle this release is deploying through? That’ll help me accurately attempt to reproduce this or see what’s going on.
Let me start with your a legend,
The API key was associated with a different user who did not have access to the prod 02 environment. Such a simple thing I didn’t event think to check as it was setup once 2 years ago and forgotten about.
thanks for your help much appreciated it.
You’re quite welcome, and thank you for your very kind words! Great to hear it’s been sorted out, and please don’t hesitate to reach out if you have any questions or concerns in the future.