Nice stuff

[deiv061]

Hello,
Great project really appreciate that

I struggle with a similar solution. Is it possible to start only VM without creating them from AMI because I have to use macOS bare metal on a dedicated host in AWS? Can you give me a suggestion? Main goal is to have onespin agent which will be scheduled for start/stop depending on business hours and if the items in the job queue are more than 1 to start VM and init the job after succeeding to stop the VM.

[ghost]

Hello, sorry for the response delay I was out of office.

This project is intended to start and provision a fresh VM each time and then trash it. Eventually I can add more AMI or add the ability to select a custom AMI. But, in your case, you seem to have an already ready (stopped) instance that you just want to start on stop depending on if needed or not. This project look to be overkill for this.

I assume you can achieve what you want with a simpler solution. For instance:

• Configure the Azure pipeline agent on your VM like a standard self-hosted agent in a dedicated agent pool.
• Then, create your pipeline as follow:
  • Create a "start" job that is a MS hosted agent with a single step that call AWSCLI to start your instance.
  • Create a job that run on your dedicated agent pool, this job will run your build steps.
  • Create a "stop" job that is a MS hosted agent with a single step that call AWSCLI to stop your instance. This job may eventually check the jobs queue to avoid stopping the instance if still needed. Ensure that this job condition is set to "Always()" to make sur the instance is topped in the case your build fail.

If you want make sure your instance is stopped outside business hours, a good solution is CloudWatch/Eventbridge events (See this example) eventually coupled with a Lambda function if you need more precise action.

[deiv061]

Sorry for the delay.Nice solution. I create a similar but with Hosted Agent in Azure and Lamba functions, which seems to work as well.
Thank you :)