Some basic information about the cluster. Schedule or configure new builds. Editing an existing build. Deleting the sample build configuration. Adding a new build configuration. Autoclean will remove the build directory on completion The settings are validated by the server. Lets start some new builds. We have 3 worker executors connected. We run the webserver on a dedicated server, where I am recording. Tons of concurrent builds with so many executors. Monitoring memory and CPU usage on our executors. Wow, realtime logging output. Except its only near-real-time. Because we delay messages by 3 seconds from their timestamp. But the effect is nice. Oh yes, and the build log scrolls automatically. Downloading artifacts? this is probably not my development machine. For repeated builds the artifacts will be cached. At least with gradle/maven builds. Aha some builds have failed 🙂 The builds exit status is always logged. lets see why it failed. oops, probably 4 concurrent builds was a bit too much. Yay something went green. Nice! even the cleaning went well. Aha, its possible to clean up the build log. failed, something about javadoc. tsk tsk. lets clean this up. kaboom! this cleans up all the logs as well. which we store in memory. an about box? how original. this is the button you should click.
and then you should contribute. thanks for watching 🙂