With Hudson driving builds from the top; Git, Gerrit, Maven, and Tycho in the middle; and Mylyn controlling the pieces from the developer's desktop, The Eclipse Foundation provides an impressive stack of technologies for building software. All this great technology combined with governance, intellectual property management, architectural guidance, and coordination via the simultaneous release, combine to deliver an Application Lifecycle Management (ALM) solution that is the envy of other open source projects and IT departments around the globe.
Tycho promises to merge the world of osgi/p2 with Maven apparently making it dead easy to build plugins.
The JBoss Tools and Developer Studio team moved to Tycho last year and with 350+ plugins we learned a lot about what Tycho can do and not do.
In this talk I will update on the Good, bad and ugly experiences we had and continue to have and discuss our recommendations on how to and how not use Tycho.
By adopting Kanban for our teams, employing an organization-wide release process and utilizing tooling for continuous integration of software, we have a process and system in place that allows us to effectively scale our Agile methodology across an enterprise and beyond a single team.
This tutorial will walk participants through the creation of a flexible, enterprise-grade, build system that can not only checkout, compile, and unit test your code - but also dynamically create Eclipse workspaces.
The tutorial will start with an introduction to dependency management and Ivy. This includes the key Ivy concepts of Artifacts, Configurations, Resolvers, Publishers, and Conflict Management.
From there we discuss what makes a "good" build system by way of patterns and practices.
- Managing build script dependencies
- Major build stages
- The module loop
