Cannot publish latest version.

0
Hello, Having problems deploying the latest version of my Application to Accp. I’ve tried removing the local folder and pulling a fresh version down from the cloud but still have errors. When I select Project > Deploy to Licensed Cloud Node the error I receive is ‘Applicant has no studios target set. Ask the Technical Contact of this applicant to set studios target in the development portal. I also asked my team member to try and he gets the same error. I then tried it the original way Project > Create Deployment package then go onto the portal and try to upload the new Deployment package but receive the error ‘An error occured, please contact your system administrator’. Deployment has worked previously so unsure what is going wrong, if anyone could offer any help I would appreciate it. Thanks in advance :)
asked
4 answers
1

Hi Oliver,

Mendix introduced the "Mendix studio target”, in the V4 you can set one environment to be the studio target. When using "Deploy to Licensed Cloud Node”, it will also move the package to this environment and restart it.  For the V3 there were some issues, but they should be resolved now. 

When creating packages locally, be sure to have the correct JDK present and selected in the project settings. You could try to build a package in the cloud, by using the button "Create package from teamserver” in the environment settings of your project.

 

https://docs.mendix.com/releasenotes/developer-portal/deployment

https://docs.mendix.com/developerportal/deploy/studio-deployment-settings#target

answered
1

See this forum post: https://forum.mendix.com/link/questions/102390 It is a new feature from Mendix that has not been thought through and is very confusing. This should be changed because it is causing a lot of confusement and frustration.

Regards,

Ronald

 

answered
0

Does this action worked before?

Alternatively, if oyu have a lincenced node, you could build the package based on the latest revision and deploy it then in the sprintr

answered
0

Dangerous setting. When you have to put a hotfix in production and it should not to deploy in acceptance (when target is acceptance), now it always put your hotfix into acceptance first. This is not always desirable.

answered