Running preflight builds
You can run test builds in your production build environment without impacting your production environment, using a preflight build. Preflight builds allow you to build code that has not been merged into your production code to determine if the build completes correctly.
A preflight build is like a regular build life, allowing you to test a build before committing code changes to the source control. The preflight build includes a clean-up service that deletes preflight build older than thirty days. This prevents the accumulation of test builds using server storage.
A preflight build cannot be specified as a dependency for either a regular or another preflight build. Because it can never be a dependency for any other build, it is always safe to delete.
To use this feature, you must download the Preflight client on any computer that can communicate with the UrbanCode Build server.
Request URL:
http://localhost:8080/tasks/project/BuildRequestTasks/viewBuildRequest?buildRequestId=463Request Status:
SubmittedRequest Status:
BUILD_LIFE_CREATED
Buildlife URL: http://localhost:8080/tasks/project/BuildLifeTasks/viewBuildLife?buildLif eId=386
Build Status: RUNNING
Build Status: FAILED
Notice that the Build Status field indicates that the preflight build failed. The error should be investigated and fixed before merging into the production code. The link in the Buildlife URL field provides additional information about the failure.
You can continue using the preflight build testing iterations of the code until a successful build occurs.