"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."
- Why I was worrying
- closed, private build jobs
- cron jobs, shell scripts, ant scripts
- unpredictable results
- Continuous integration
- ex. Hudson
- Common build infrastructure (CBI)
- Recipe for Success
- Rules of Engagement
- Transparency
- Invite participation
- Openness
- Accept participation
- Meritocracy
- Earn participation
- The Four Cs
- Code (must show up at Eclipse with code)
- Community
- End users, Adopters, Developers
- All are important
- Cleanliness (from an intellectual property perspective)
- Where does the code come from
- Copyright
- Ownership
- Licensing
- Cwality (Quality)
- Transparent issue tracking, list discussion
- Reviews (developing community, project is more than just code)
- Inviting/Accepting participation
- Diversity
"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."
- ALM "Stack"
- Build Maturity
- Modular builds make CI possible
- Tracking IP
- Licenses
- Third-party libraries
- Developers
- Contributors + Contributions
- CI = continuous integration
- IP = intellectual property
No comments:
Post a Comment