townsourced/ironsmith
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
50 Commits 1 Branch 5 Tags 268 KiB
Go 71.9%
JavaScript 18.8%
HTML 9.2%
479175baa0
Go to file
Tim Shannon 479175baa0 Changed forced build to be only off of trigger 
instead of anytime that it's not polled
2016-05-05 10:30:50 -05:00
datastore Added max version limit for projects 2016-05-04 15:39:56 -05:00
web Fixed small issue with logs in table formatting 2016-04-28 15:12:50 +00:00
.gitignore Ironsmith starting point 2016-03-29 21:43:58 +00:00
bindata.go Fixed small issue with logs in table formatting 2016-04-28 15:12:50 +00:00
build.sh Testing git hooks with ironsmith 2016-04-25 15:44:04 +00:00
cycle.go Changed forced build to be only off of trigger 2016-05-05 10:30:50 -05:00
error.go Updated import paths to new townsourced organization 2016-04-19 19:52:55 +00:00
exec.go Added max version limit for projects 2016-05-04 15:39:56 -05:00
json.go Updated build script 2016-04-20 16:42:16 +00:00
LICENSE Fleshed out how projects will be loaded and run 2016-03-30 21:48:52 +00:00
log.go Added logging and proper execution of commands 2016-04-05 21:59:52 +00:00
main.go Updated import paths to new townsourced organization 2016-04-19 19:52:55 +00:00
project.go Changed forced build to be only off of trigger 2016-05-05 10:30:50 -05:00
README.md Added time took to release log statement 2016-04-25 21:02:01 +00:00
server.go More web work 2016-04-15 21:57:59 +00:00
webProject.go Changed forced build to be only off of trigger 2016-05-05 10:30:50 -05:00

README.md

ironsmith

Ironsmith is a simple continuous integration (build - > test -> release) tool.

How it works

You'll setup a project which will need the following information:

  1. Script to fetch from the repository
    • Most of the time this will be a git clone call, but it can be a bash script calling an FTP or whatever
    • Choose between polling for changes, or triggered builds
      • Triggered builds will be triggered off of a web hook POST call
  2. Script to build the repository
  3. Script to test the repository
  4. Script to build the release file
  5. Path to the release file / can also be a script that returns a file name
  6. Script to set release name / version

An optional set of environment strings can be set to define the environment in which the scripts run.

"environment": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/go/bin",
"GOPATH=@dir"
]

Projects will be defined in a project.json file for now. I may add a web interface later.

@dir in any of the script strings or environment entries will be replaced with an absolute path to the current working directory of the specific version being worked on.

sh ./build.sh @dir

Ironsmith will take the information for the defined project above and do the following

  1. Create a directory for the project
  2. Change to that directory
  3. Create a bolt DB file for the project to keep a log of all the builds
  4. Run an initial pull of the repository using the pull script
  5. Run version script
  6. If pull is a new version, then Run the Build Scripts
  7. If build succeeds, run the test scripts
  8. If test succeeds, run the release scripts
  9. Load the release file into project release folder with the release name
  10. Insert the release information and the complete log into the Bolt DB file

This tool will (originally at least) have no authentication. I plan on adding it later.

To add a new project, add a .json file to the projects/enabled folder. Look at the template.project.json file in the projects folder for an example.