[TIMOB-8914] Validate sandbox functionality - Jenkins post build trigger(s) launch local Drillbit application
| GitHub Issue | n/a |
|---|---|
| Type | Sub-task |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2012-05-04T12:28:37.000+0000 |
| Affected Version/s | Backlog |
| Fix Version/s | Release 2.1.0, Sprint 2012-09 Core |
| Components | Drillbit |
| Labels | n/a |
| Reporter | Robert Collazo |
| Assignee | Robert Collazo |
| Created | 2012-04-29T12:54:52.000+0000 |
| Updated | 2012-06-15T16:33:33.000+0000 |
Description
This involves initial Administrative tasks including Linux-based Tomcat, Jenkins, GitHub, and Titanium/SDK/Drillbit installation. Most of this effort is for Jenkins and GitHub plugin configuration. Once configured, the automation triggers will be tested:
1. manual file change
2. manual GitHub commit to sandbox repository
3. automation trigger fired from GitHub to Jenkins
4. Jenkins launch (trigger) of Build tasks for sandbox project
5. Jenkins launch (trigger) of post-build script
6. Post build script execution of Drillbit test
Linux sandbox platform installations are completed. GitHub to Jenkins trigger on 'commit' is not working at this time. Post-build script trigger can be verified from Jenkins admin test.
All components are installed, integrated and functional. This task is complete.