Job rejected because resource class doesn't exist for android-machine with latest orb version about android-orb HOT 5 CLOSED

Awesome, glad I could get that sorted for you quickly, thank you for the quick updates!

from android-orb.

Hi @PetarKaukov this doesnt sound like an issue with the orb, can you fill out a support request? Do note that if you are a free customer you only have access up to a large resource class.

from android-orb.

Hi @PetarKaukov this doesnt sound like an issue with the orb, can you fill out a support request? Do note that if you are a free customer you only have access up to a large resource class.

We're definitely not a free customer, as we, as a company, have been using CircleCI for a long time. We've used all kinds of resource classes in our pipelines.

And, as mentioned in the issue, it works flawlessly up to version 2023.08.1. And this issue only affects android-machine, android-docker runs without issues up to the latest version - 2023.10.2.

When I set the docker-machine job to use the older version, our pipelines passed, but that's not how I would expect it to work.

All of our jobs use xlarge if it's of any use.

Edit: I'll fill a support request, yes.

from android-orb.

Hi @PetarKaukov, one last question before you reach out to support, are you attempting to use the tag 2023.10.2 for the machine executor as well? If so, that would explain the failures. There was only one version of the machine image released last month and it was tagged 2023.10.1. The docker image was rereleased because of an issue with the ndk variant and thats why there is a 2023.10.2 tag for the docker image.

from android-orb.

I see. I attempted to run a pipeline with "2023.10", but it failed with the same error.

However, specifying "2023.10.1" actually passed the pipeline. A bit confusing, but I understand now why it's like that. Thanks for the replies, our pipelines are green again with 2023.10 :)

from android-orb.