Changes in 3.14
We are excited to announce the Octopus Deploy plugin for Atlassian Bamboo continuous integration server.
This includes build tasks to make it easy to integrate your build and deployment pipelines.
- Package applications for deployment
- Push packages to Octopus
- Create Octopus releases
- Deploy Octopus releases
Octopus Tentacle 3.14.15: Octopus Tentacle 3.14.15 is not backwards compatible with Octopus Server versions less than 3.14.15. This has been fixed as of Octopus Tentacle 3.14.159.
Octopus Server configuration automation: If you are using scripts to automate your Octopus Server installation, please test these scripts with Octopus Server 3.14.x. We have made some changes to simplify configuration of your Octopus Server, but weren't able to maintain 100% backwards compatibility with some of the more obtuse scripts we tested. If you encounter any problems, please look at the scripts generated when you use the Octopus Server wizard.
SQL Database schema upgrades: It may also be worth noting we have adjusted the SQL database schema upgrades so they can be run at the time, and by a user account, which best suits your scenario:
- Automatically after the installer completes (new behaviour) - this runs the schema upgrades as the user account who started the installer - falls back to the existing behaviour if the installing user cannot access the SQL database
- Automatically during the Octopus Server startup (just like before) - this runs the schema upgrade as the user account who started the Octopus Server
- Automatically when executing the
Octopus.Server.exe configure command for a setting which is stored in the database (just like before) - this runs the schema upgrade as the user account who started the Octopus Server
- Manually by executing the brand new
Octopus.Server.exe database --upgrade command - this will run the schema upgrades as the user account who started the command
This may not affect many customers, but enables some advanced scenarios where you can grant limited privileges to the Octopus Server account, and grant schema change privileges to a special account used for installation.
SQL Error 4060 - Cannot open database "OctopusDeploy" requested by the login. The login failed.
If you see an error message like this after the installer completes, you can start the Octopus Server just like before and let it perform the schema upgrades.
Read the upgrade guide for more details on upgrading from your current version to Octopus 3.14.