Hello there,
I am reaching out for advice and best practices on managing Jenkins job configurations in an organization where multiple teams are involved. We are facing some challenges in maintaining consistency and ensuring that each teams needs are met without causing conflicts or redundancy.
We have several development teams; each responsible for different parts of our product suite. These teams often need to create and manage their own Jenkins jobs.
While some pipelines are unique to specific teams, others are shared across multiple teams. This sometimes leads to difficulties in configuration management, especially when teams have differing requirements or priorities.
We have considered using Jenkins Job DSL and pipelines as code to standardize configurations; but we are still ironing out the best approach for collaboration and version control.
Ensuring proper access control is also crucial; as we want to allow teams to manage their own jobs without affecting others inadvertently.
Best practices for organizing and managing Jenkins job configurations across multiple teams.
Strategies for using Jenkins Job DSL or other tools to maintain consistency and manage shared resources.
Also, I have gone through this post; https://community.jenkins.io/t/jenkins-with-multiple-deploys-in-single-jenkins-job-aws-devops/ which definitely helped me out a lot.
How to handle access control in a way that balances security with the need for flexibility.
Thanks in advance for your help and assistance. 