So gotta say that now that the account:ci command came it was a breeze setting up automatic deployments but I feel it’s quite a concern that situations seems to happen when “project:validate --server” is successful but “project:deploy” is not successful (This case had problems deploying a menu link to a search which was also included in the project). Anyone with any ideas how we could improve the process or can share potential workarounds? (This specific case we created a search with the id in the environment which the deploy then could overwrite but would really like a handsoff approach to deployment)

@Petter we know that local validation has some problems, we fixed some of them in recent release but relevant teems are working on the core problem to make local validate more credible and smooth. But will take time. When you are running project:deploy without i, it is doing local validate by default. If you run project:deploy in interactive you can skip local validate but select server. But i understand that it might not be a best solution in ci/cd.

I did run “--server” though

You ran project:validate --server Project:deploy without "i" always go for local validate before deploy. You only have the optiona to select local or server in interactive mode.

aha that explains stuff

I would like to be sure this is what is happening. Can you share the SDF logs of error project:deploy is showing? You can DM them to me.