The Go team is excited to announce the Early Access (EA) release of 12.3. This allows our community of users to try out the features in Go 12.3 before it is officially released. The installers for various platforms are available in the links specified below.
Please try it out and give us feedback! We will actively respond to questions and comments on this build through the community forums.
Early access builds are not intended for your production environment.
What is new in 12.3?
- Go’s new “Fan-in” feature allows you to model your workflow to fail fast. Continuous Delivery is about failing fast to learn fast. Early failure is cheap and easy to fix. So it really comes down to getting short feedback loops across your build-test-release workflow. What can you do with “fan-out” and “fan-in”?
- package the right versions of your components – eliminate spurious builds
- parallelize testing activities in different environments to find issues as quickly as possible
- Are you happy with a pipeline and are ready to create a template? Extract a template! This makes scaling easier and promotes consistency in your build-test-release workflow. A common use case is when you want to start using your deployment mechanism across multiple environments.
- Pipeline Group administrators can now view and edit the underlying XML configuration. Some administrative tasks are easier done using the XML (and believe it or not some users prefer the XML!). We took this away in a previous release and are bringing it back in a better form.
- Silent (unattended) Windows installer. You no longer need to stick (and click) around when you install a Windows agent. Thank you for your patience!
- Your CCtray client now shows you who broke the build.
- API to cancel a Stage.
Go Community Edition
- Go Community now has access to all features!
- Teams of up to 10 users can now have access to a fully featured Continuous Delivery tool, for free.
- This includes Go Environments, templates, pipeline groups and pipeline group security.
- The Pipeline Compare feature now uses “push date” and not “author commit date”.
- Check connection issue with Perforce
Please sign in to leave a comment.