Hello,
Probably this will help you to resolve your problem.
1. No Authorized Queues for Agent Pool
This issue usually occurs due to permission settings or misconfigurations. Here are some steps to troubleshoot:
- Check Permissions: Ensure that the user or service account running the pipeline has the necessary permissions to use the agent pool. You can do this by navigating to the Project Settings > Agent pools and checking the security settings for the pool.
- Verify Agent Pool Configuration: Make sure the agent pool is correctly configured and has agents available. Go to Project Settings > Agent pools and verify that the pool is listed and has agents assigned to it.
- Service Connection: Ensure that the service connection to your SVN repository is correctly set up and has the necessary permissions. Go to Project Settings > Service connections and verify the connection details.
2. Connecting SVN Repo to Azure DevOps
To connect an SVN repository to Azure DevOps and ensure updates are reflected, you can follow these steps:
- Create a Service Connection:
- Go to Project Settings > Service connections.
- Click on New service connection and select Subversion.
- Enter the required details for your SVN repository and save the connection.
- Create a Pipeline:
- Go to Pipelines > New pipeline.
- Select Use the classic editor for more control.
- Choose your repository type as Subversion and select the service connection you created.
- Configure the pipeline steps as needed.
- Set Up Continuous Integration:
- In the pipeline configuration, set up triggers to ensure that changes in the SVN repository trigger the pipeline.
- Go to the Triggers tab and enable Continuous integration.
- Build and Deploy:
- Define the build and deployment steps in your pipeline to ensure that changes in the SVN repository are built and deployed to your Azure DevOps environment.
Hope all this will help you.
Kind Regards,