Add custom block device mapping configuration
Prevent nodes that are still starting up from being idle-stopped

Per JENKINS-23792, the EC2 plugin will shut down nodes that're still starting
up if the idle timeout is shorter than the time the node takes to go from
launch request to successfully starting its first job on an executor.

To prevent this, don't perform idle shutdown on a node that is marked offline.
When it comes online, executors will be created and the new idle time will
become the executor creation time, effectively resetting the timer.
Report "pending" not "stopping" for pending nodes in logs

Fixup for 8a9a885 (github pull #101): correct a case fall-through that
resulted in the wrong log message being emitted for starting nodes.
Merge pull request #104 from ringerc/logging-detail-case-fix

Report "pending" not "stopping" for pending nodes in logs
Merge pull request #102 from ringerc/no-idle-out-before-launch

Prevent nodes that are still starting up from being idle-stopped
Merge pull request #98 from 2m/custom-block-device-mapping

Add block device mapping configuration
Corrected block device configuration to align with current EC2 API
Revert "Corrected block device configuration to align with current EC2 API"

This reverts commit 4f31e0450f9fe1c5fa8b30fe8550a0ff657b1d29.
JENKINS-4995 Support Windows AMIs
Merge pull request #105 from jenkinsci/feature/windows-slave-support

JENKINS-4995 Support Windows AMIs
[maven-release-plugin] prepare release ec2-1.24
[maven-release-plugin] rollback the release of ec2-1.24
[maven-release-plugin] prepare release ec2-1.24
[maven-release-plugin] rollback the release of ec2-1.24
Added git URL to the pom
[maven-release-plugin] prepare release ec2-1.24
[maven-release-plugin] rollback the release of ec2-1.24
[maven-release-plugin] prepare release ec2-1.24
[maven-release-plugin] rollback the release of ec2-1.24
[maven-release-plugin] prepare release ec2-1.24