Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Building/EclipseCon2010Panel"

(Continuous Integration)
Line 13: Line 13:
 
*Dealing with 5 o'Clock checkin syndrom?  
 
*Dealing with 5 o'Clock checkin syndrom?  
 
*Dealing with long running builds.
 
*Dealing with long running builds.
 +
*Dealing with static code analysis tools ( findbugs/checkstyle/warnings/pmd...), tests ( Junit/swtbot ) and "build it quickly !" (stephane.bouchet)
  
 
= Testing  =
 
= Testing  =

Revision as of 07:29, 22 March 2010

Questions for the EclipseCon 2010 Build Panel:


General

  • How important is it to make a build agnostic?
  • Will modeling builds and new DSLs be the silver bullet to complicated, reproducible builds?
  • What pain points does your build process address?
  • Is your build tighly designed for one way of building, or is it flexible?


Continuous Integration

  • But it works on my machine!
  • Dealing with 5 o'Clock checkin syndrom?
  • Dealing with long running builds.
  • Dealing with static code analysis tools ( findbugs/checkstyle/warnings/pmd...), tests ( Junit/swtbot ) and "build it quickly !" (stephane.bouchet)

Testing

  • Running User Interface Tests
  • Running SWTBot
  • Running JUnit 3 and JUnit 4 Bundle Tests together.

Eclipse

  • Building OSGI applications.
    • Manifest first or Code First?
  • Map Files or No?
  • Tag Before or Tag After?
  • What is the best way to deal with Eclipse based eGit projects?
  • Has the introduction of P2 made life easier or harder for the build engineer?

Back to the top