Development: Difference between revisions

From Adam Colton
Jump to navigation Jump to search
No edit summary
 
Line 22: Line 22:
=== Build/Publishing ===
=== Build/Publishing ===
I may be using Go which requires a build. I want to incorporate a more complex JavaScript tool-chain using JavaScript optimizers which will also require a build. Finally, I want to be able to target various machines.
I may be using Go which requires a build. I want to incorporate a more complex JavaScript tool-chain using JavaScript optimizers which will also require a build. Finally, I want to be able to target various machines.
=== Issue Tracker ===
Perhaps [http://www.mantisbt.org/ Mantis]?


== Integration ==
== Integration ==

Latest revision as of 15:31, 20 June 2013

Components

  • Editor
  • Source Control
  • Continuous Integration
  • Issue Tracker
  • Documentation
  • Build/Publishing
  • Backups

Editor

I think I'm going with Sublime Text.

Source Control

Git. I think I'll simply have a repo on the dev machine.

Backups

AMIs. I need to come up a with a rotation. I would also like to see if they can be exported.

Continuous Integration

I'm leaning towards Buildbot, but I should also look at Apache Ant. I may also forgo this entirely and do the whole thing with some scripting.

Build/Publishing

I may be using Go which requires a build. I want to incorporate a more complex JavaScript tool-chain using JavaScript optimizers which will also require a build. Finally, I want to be able to target various machines.

Issue Tracker

Perhaps Mantis?

Integration

I would really like source control, continuous integration and the issue tracker to all work together. I don't want to impose my prejudices on the system, so I will stick the basic requirements rather than how I expect it to work. I should be able to associate commits with issues and have the status of the continuous integration performed on those commits tied to the issue tracker.