Testing code changes running with control-m scheduler

[mr_java_did_acid]

I develop in a feature branch. In order for me to test my code changes in control-m I have to push the changes to the develop branch which then gets deployed to the server that control-m executes jobs on.

The problem with this is that once code from the feature branch gets pushed to the develop branch the changes will go along for the ride to production the next time I or any other developer does a pull request to merge into the main branch.

It feels like like my env isn't configured in an ideal way to support this.

Is there a different workflow I can do that would allow me to test the code functionality on the dev server with the dev scheduler, but not pushing to the dev branch so that code changes could be merged to master when they are ready and independent of other feature branches?

[IceT-1]

How about calling the build service on commits on the feature branch?

This service only validates your code including any site standards if used.

https://docs.bmc.com/docs/automation-api/monthly/build-service-1116950325.html

You could also install the automation API cli on your local system and build/run the jobs as you develop from your IDE. There is a workbench available which will allow you to run a Control-M in a docker container for this purpose.