CloudBees Long-Running Build Plugin 1.0-beta-1

2 minute read

RELEASED: Public: 2014-03-18

New features

Initial beta release. You need to enable the experimental update center in Jenkins global configuration to see beta versions.

Resolved issues


Known issues

  • CloudBees Internal Ticket: RM-2320

    The build is considered “completed” too early, which can cause problems interacting with some other plugins and Jenkins features.

  • CloudBees Internal Ticket: RM-2322

    Does not yet detect when the wrapper script is killed, for example by a machine reboot.

  • CloudBees Internal Ticket: RM-2324

    There is not yet a defense against other jobs grabbing an executor slot on a busy agent between build phases.

Cannot work on typical cloud agents, since these are typically ephemeral (have no persistent configuration) and are liable to be destroyed as soon as the initial steps complete. To let a detached script run even after a Jenkins restart, the agent computer must remain running and reattach with the same node name.

  • CloudBees Internal Ticket: RM-2321

    Build wrappers are currently supported only on the initial build steps, not on the main “detached” build step or post-build steps.

  • CloudBees Internal Ticket: RM-2323

    Build duration estimates inaccurate.

  • CloudBees Internal Ticket: RM-2328

    Restarting the Jenkins controller may kill even a detached script running on a controller executor. It is advisable to run builds on agents.

Only certain kinds of build steps are permitted in the asynchronous portion; they must be able to run to completion without access to Jenkins or a Jenkins agent. Currently just Bourne shell scripts and Windows batch scripts are implemented.

  • CloudBees Internal Ticket: RM-2327

    You must restart Jenkins after installing this plugin for it to work.

Only the detached phase of the build can survive Jenkins restarts (or agent reconnections). If there is an interruption in the agent connection during the initial build steps, or the post-build steps, the build will be considered aborted just like regular Jenkins jobs.