Principal Cloud Architect at a wholesaler/distributor with 1,001-5,000 employees
Real User
Top 10
2021-06-17T11:41:07Z
Jun 17, 2021
VSCode or eclipse, Gitlab, terraform, ansible, nexus, Azure Container instances or Kubernetes Services
VSCode to rule them all. Some devs use eclipse, we leave that up to personal choice.
GitLab offers not only a sourcecode repo, but also a nice CI/CD solution which works very well for us. No need for Jenkins with that. Also features a container registry (and lots more). For us, Gitlab is where everything starts. Nice and easy integration with any auth provider.
Terraform for setting up the runtime environment, Ansible for configuration of target VMs, containers and pods. Easy to move between clouds - VMWare, Azure, AWS....
Nexus as a storage for any build artifacts and ALM
Deploy to container service of choice, we use ACI for Docker and AKS for Kubernetes.
Go Serverless FTW!
Search for a product comparison in Release Automation
Community Manager at a tech services company with 51-200 employees
Real User
Jul 26, 2020
Thanks for weighing in :) would you mind elaborating a little bit on how you use each of the tools? Do they integrate well? Have you used other tools in the past that you switched from?
Co Founder and Technical Architect at Think NYX Technologies LLP
Reseller
2021-01-04T14:13:26Z
Jan 4, 2021
In my Opinion, We should could the all aspect of CI/CD while selecting tools, like Code Quality, Versioning, Code Review, SAST, DAST, FT, Performance testing, Build Tools, UT, Distribution Management, Deployment, IaC, Containerization if organization is in same mode, below are the tools that I recommend for Java based applications.
Maven/Gradle, Junit, Selenium, Jmeter, OWASP DC, Zap, Sonarqube, GIT (I like GitLab), Nexus, Ansible and Terraform for IaC and Kubernetes with Docker or any other CRI for containerization.
I have done the complete integration of this along with JIRA and couple of monitoring tools for end to end pipeline setup,
Release Automation streamlines the deployment process of applications, offering efficiency and reducing manual errors. It facilitates faster release cycles and ensures consistency across environments.Automating the release process enhances operational productivity by orchestrating and standardizing it. It integrates with existing tools to provide a cohesive workflow from development to deployment. Its flexibility adapts to different requirements, ensuring each release is smooth and...
VSCode or eclipse, Gitlab, terraform, ansible, nexus, Azure Container instances or Kubernetes Services
VSCode to rule them all. Some devs use eclipse, we leave that up to personal choice.
GitLab offers not only a sourcecode repo, but also a nice CI/CD solution which works very well for us. No need for Jenkins with that. Also features a container registry (and lots more). For us, Gitlab is where everything starts. Nice and easy integration with any auth provider.
Terraform for setting up the runtime environment, Ansible for configuration of target VMs, containers and pods. Easy to move between clouds - VMWare, Azure, AWS....
Nexus as a storage for any build artifacts and ALM
Deploy to container service of choice, we use ACI for Docker and AKS for Kubernetes.
Go Serverless FTW!
Jenkins, git, nexus, sonar qube, ansible, aws
Thanks for weighing in :) would you mind elaborating a little bit on how you use each of the tools? Do they integrate well? Have you used other tools in the past that you switched from?
Jenkins as open source choice
Octopus+TeamCity for on premise because this couple is very mature
In the cloud the tools that the service provider give you.
git, Jenkins, sonarqube, nexus, eclipse,
- Planning (Azure DevOps Boards)
- Source code (Git or TFS VCS)
- Testing tools (unit and integration) - Web and/or Mobile - Katalon
- CI/CD pipelines (Azure DevOps Pipelines)
- Application monitoring tool - Feeding Back and repeat
In my Opinion, We should could the all aspect of CI/CD while selecting tools, like Code Quality, Versioning, Code Review, SAST, DAST, FT, Performance testing, Build Tools, UT, Distribution Management, Deployment, IaC, Containerization if organization is in same mode, below are the tools that I recommend for Java based applications.
Maven/Gradle, Junit, Selenium, Jmeter, OWASP DC, Zap, Sonarqube, GIT (I like GitLab), Nexus, Ansible and Terraform for IaC and Kubernetes with Docker or any other CRI for containerization.
I have done the complete integration of this along with JIRA and couple of monitoring tools for end to end pipeline setup,