The latest updates on your projects. Learn more about Vercel for Git ↗︎

@aybruhm It is expected that the oss tests fail here, since they are using the old backend hosted in oss.agenta.ai (which expects Dockerfile and not Dockerfile.agenta.oss).

The QA therefore needs to test these manually:

• New SDK on new OSS backend
• New SDK on new Cloud Backend
• Old SDK on new OSS backend
• Old SDK on new Cloud backend

We do not need to test new sdk on old backend (Since that should not work).

In the future, I think we need to move the dockerfile creation to the backend. It's just nice to have it in the FE for debugging for now (although, not sure if this is used at all).

@aybruhm It is expected that the oss tests fail here, since they are using the old backend hosted in oss.agenta.ai (which expects Dockerfile and not Dockerfile.agenta.oss)

Ah, got it. 😅 Thank you for clarifying.

@aybruhm updated the comment

@aybruhm I have also reverted the change you made, it looks to me that it introduces and error

@aybruhm I have also reverted the change you made, it looks to me that it introduces and error

🤔

We might want to move all the serve operations and files inside of a .agenta folder to avoid any conflicts.

I'm not sure if I understand what you mean.

NOTE

This is ready to be merged pre-release.
Merging it means breaking all serve-to-oss and serve-to-cloud CI until the new backend is deployed in oss and cloud