2019.7

Features

• Key improvements in stembuild with features such as SSH enable-by-default for deployed Windows VMs on vSphere and security fixes.
• Enabled the Hyper-V Windows feature

2019.6

Give useful error messages

- when WinRM fails to create a shell, print the actual error message

1803.12

Give useful error messages

- when WinRM fails to create a shell, print the actual error message

2019.5

Integration and contract tests use credential url for vcenter

- Since we want the stembuild user to be the user with minimal
permissions for running package/construct, and the govc commands that
are run in test set-up for our integration/contract tests require additional permissions,
we need to provide different credentials for these test-setup commands.
- We now take in a VCENTER_ADMIN_CREDENTIAL_URL string to pass to these commands
- VCENTER_ADMIN_CREDENTIAL_URL is in the form of "username:password@url"
- We cannot use GOVC_USERNAME/GOVC_PASSWORD or a full GOVC_URL for
either the stembuild or admin users because govc will always choose
these credentials if provided.

[#166227545](https://www.pivotaltracker.com/story/show/166227545)
 [Pipeline Fix] Fix stembuild integration test permissions issue

1803.11

Integration and contract tests use credential url for vcenter

- Since we want the stembuild user to be the user with minimal
permissions for running package/construct, and the govc commands that
are run in test set-up for our integration/contract tests require additional permissions,
we need to provide different credentials for these test-setup commands.
- We now take in a VCENTER_ADMIN_CREDENTIAL_URL string to pass to these commands
- VCENTER_ADMIN_CREDENTIAL_URL is in the form of "username:password@url"
- We cannot use GOVC_USERNAME/GOVC_PASSWORD or a full GOVC_URL for
either the stembuild or admin users because govc will always choose
these credentials if provided.

[#166227545](https://www.pivotaltracker.com/story/show/166227545)
 [Pipeline Fix] Fix stembuild integration test permissions issue

1709.22

Integration and contract tests use credential url for vcenter

- Since we want the stembuild user to be the user with minimal
permissions for running package/construct, and the govc commands that
are run in test set-up for our integration/contract tests require additional permissions,
we need to provide different credentials for these test-setup commands.
- We now take in a VCENTER_ADMIN_CREDENTIAL_URL string to pass to these commands
- VCENTER_ADMIN_CREDENTIAL_URL is in the form of "username:password@url"
- We cannot use GOVC_USERNAME/GOVC_PASSWORD or a full GOVC_URL for
either the stembuild or admin users because govc will always choose
these credentials if provided.

[#166227545](https://www.pivotaltracker.com/story/show/166227545)
 [Pipeline Fix] Fix stembuild integration test permissions issue

2019.4

Update README

2019.3

Features

• Introduced a new command stembuild construct
• Introduced new functionality in the stembuild package to directly import an OVA from vCenter and convert it into stemcell
• These new functionalities are not available for Windows 2012R2

NOTE: Ensure you download the stembuild that corresponds to the operating system of your local host and the stemcell version that you want to build (e.g. download 2019.3 stembuild for building a 2019.3 stemcell)

1803.10

Update README

1803.9

Features

• Introduced a new command stembuild construct
• Introduced new functionality in the stembuild package to directly import an OVA from vCenter and convert it into stemcell
• These new functionalities are not available for Windows 2012R2

NOTE: Ensure you download the stembuild that corresponds to the operating system of your local host and the stemcell version that you want to build (e.g. download 1803.9 stembuild for building a 1803.9 stemcell)