7.0.1.1 – November 6, 2018

Fixes in this Release

PH03880 UPGRADING TO 7.0.1.0 WILL SET ALL AUTHORIZED AGENTS TO UNLICENSED
PH01861 UPDATE USERS FAILS IF USER WAS DELETED FROM LDAP
PH01812 TEAM INHERITANCE IS NOT APPLIED AFTER CREATING ENVIRONMENTS BASED ON A RESOURCE TEMPLATE
PH01028 SOME LDAP SERVER IMPLEMENTATIONS HAVE ISSUES SEARCHING ON BASE OBJECT WITH SINGLE-LEVEL SCOPE
PH00515 AUTOMATICALLY INCLUDING AGENTS IN RESOURCES INCLUDES DELETED AGENTS
PI99173 KEEP ME LOGGED IN DOES NOT WORK, INTERMITTENT LOGOUTS
PI97823 ERROR HANDLING AROUND RELAY TOKENS SHOULD BE IMPROVED
PI97631 INCREMENTAL VERSIONS ARE IN REVERSE ORDER WHEN DEPLOYING A SNAPSHOT IN THE COMPONENT VERSIONS POP-UP WINDOW
PI97391 NPE WHEN RUNNING AUTO-CONFIGURE FROM THE ACTIONS MENU
PI97389 AUTO DISCOVERY DOES NOT RUN WHEN AN AGENT POOL IS ADDED TO A RESOURCE
PI97055 USER WITHOUT MANAGE TEAMS ON A RESOURCE CAN DO SO WITH THE CLI COMMAND ADDRESOURCETOTEAM
PI93053 CALENDAR AND DEPLOYMENT HISTORY SHOW XML ENCODED CHARACTERS FOR QUOTES AND OTHER SPECIAL CHARACTERS
PI92703 DOWNLOAD ARTIFACTS STEP RANDOMLY FAILS WITH: STREAM CORRUPT: INVALID HASH: ALGORITHM=MD5,…
PI92583 INVALID DATE FORMAT FOR DEPLOYMENT COUNT REPORT WITH CUSTOM DATE RANGE
PI89053 DELETING A COMPONENT VERSION ERRONEOUSLY REQUIRES APPLICATION PERMISSIONS
PI89031 PROCESS REMAINS IN RUNNING STATE WITH DB2 CLOB SIZE ERROR
PI88396 CANNOT CHANGE COMPONENT TEMPLATE VERSION
PI84685 COMPONENT IMPORTS TAKE A LONG TIME WHEN THEY HAVE MANY COMPONENT AND COMPONENT TEMPLATE PROCESSES
PI78635 SCRIPT BODY EDITOR IN GENERIC PROCESSES DOES NOT HAVE ACE EDITOR.

Known Problems and Workarounds

To search for additional post-release issues that IBM Rational Support documented, visit the IBM Support portal.

Upgrade Notes

 

Starting in 7.0.1.0

UrbanCode Deploy 7.0.1.0 introduces the concept of Agent Configuration Templates (which are used in migrating agents from JMS communication to the new WEB communication). This upgrade did not grant the System Team access to Agent Configuration Templates. Users will need to grant these permissions to if users on that team wish to access the functionality.

It should also be noted that some of the servers code station metadata has been migrated to the database. Specifically, it is the content of the $APPDATA/var/repository/ptr directory. This stores the association between component versions and artifact blob files. This resolves some server-side performance issues that negatively impacted relay codestation cache cleanup. The old data files are preserved without modification to support upgrade rollback. However, they are not updated going forward. This means that a later rollback would break new, post-upgrade version artifact associations (blobs files would remain but would be inaccessible).

Starting in 7.0.0.0

UrbanCode Deploy 7.0 introduces new functionality that allows you to add process change management to your deployment processes. This functionality is still in BETA, and we are actively looking for customer feedback. If you would like to access a cloud instance of UCD, to use and provide feedback without having to set it up, please reach out to your IBM representative and let them know!

UrbanCode Deploy 7.0 also introduces new server/agent communication protocols.

  • For new installations of the Deploy server users will be prompted for additional information unconditionally (all new installs will default to the web socket protocol).
  • When installing new Deploy agents, users will be asked for their preference, either JMS or web sockets. The default is web.
  • When upgrading the Deploy server, the user will be prompted for additional information to support the web socket protocol, however, no agents will change communication protocols as part of the upgrade.
  • An interactive (manual) upgrade of an agent will also prompt for new information to support the web sockets protocol. Upgrading through the web-ui will upgrade existing agents and keep them on the current server/agent communication (JMS)

It should be noted that in all scenarios, UrbanCode Deploy supports running both the new agent communication (web sockets) with the older model (JMS) in parallel.

Starting in 6.2.7.1

API-breaking changes have been made to the supported REST endpoints that set properties in UCD, affecting the setAgentProperty, setApplicationProperty, setComponentEnvironmentProperty, setComponentProperty, setEnvironmentProperty, setResourceProperty, setSystemProperty, and setVersionProperty endpoints. Any scripts that need to set properties on components, agents, the system, processes, process requests, applications, or environments will need to be adjusted. Consult the documentation for the new syntax.

Also, because of these API changes, the plugins that set properties in UCD are not backwards compatible. In the following list of plugins, any plugin version before the version listed is not compatible with UCD 6.2.7.1 or later, and and any plugin version after the version listed is not compatible with 6.2.7.0 or earlier. On upgrading to UCD 6.2.7.1, the plugins will automatically be updated to a supported version. However, using old versions of processes that are locked in snapshots or downgrading the UCD plugin version may cause steps to fail.

Plugin 6.2.7.1+ compatible versions
IBM UrbanCode Deploy Applications 77+
IBM UrbanCode Deploy Components 71+
IBM UrbanCode Deploy Environments 77+
IBM UrbanCode Deploy Resources 74+


Starting in 6.2.5.2

Starting the server for the first time may take longer than usual. For very large installations, allow an extra hour for the first server startup. Subsequent startups will take the regular amount of time.

Users now do not receive notifications based on their membership in a role on the System Team. Users will have to be added to the correct role on a different team as well to receive notifications.

The server now deletes all contents of the var/temp directory on server startup.

Starting in 6.2.5.1

Process requests from deleted environments will now be deleted. To keep process requests from deleted environments, add this property to the installed.properties file: com.urbancode.ds.cleanup.HistoryCleanup.disableDeletedEnvironmentCleanup=true

Starting in 6.2.5.0

The UCD_SESSION_KEY header has been renamed to UCD_CSRF_TOKEN. The previous name is also accepted until 6.3 when it will be removed from the product.

Users now require the “Execute” permission on agents in order to run processes against them. All existing user roles will receive this permission when upgrading from a version before 6.2.5.0. When upgrading, ensure that any user that needs to execute processes is on the same team as the agents required to run those processes.

Starting in 6.2.4.0

You must upgrade Agent Relays when upgrading from a version below 6.2.4.0. Also, the TLS protocol 3DES is no longer supported.

After upgrading from before 6.2.4.0, users will not be able to view or delete agent relays until they have been granted permission to those relays. Relays that existed before the upgrade are only added to the System Team by default. For users to view agent relays, a user with Manage Security permission should give the correct roles the new For relays that existed before the upgrade, a user with Manage Security permissions will have to add the agent relays to the correct teams and give the correct roles the Agent Relay view and edit permissions.

When upgrading an IBM UrbanCode Deploy agent, end-to-end JMS encryption will automatically be enabled on all agents. In order for agent communication to function properly with end-to-end encryption enabled, the IBM UrbanCode Deploy server and agent clocks need to be synchronized to within a few minutes. To disable this feature, add the line agent.jms.disable_full_encryption=true” to the agent’s conf/agent/installed.properties file before upgrading the agent.

Starting in 6.2.3.0

If you are upgrading from version 6.2.3.0 and earlier, servers and relays must be upgraded at the same time. Agents connected through relays may not connect successfully until both server and relay are upgraded. This is due to an incompatibility between versions of an library used by UCD.

Starting in 6.2.3.0, authentication tokens will be obfuscated in the UI and REST API after their initial creation. Scripts and users will only be able to retrieve the full authentication token immediately after creating it.

The silent install of the IBM UrbanCode Deploy server hangs when prompting for the value of the server installation directory (install.server.dir). To workaround the problem, run the following instead of calling ./install-server.sh directly:
echo "" > answerFile.txt echo "" >> answerFile.txt ./install-server.sh < answerFile.txt (or install-server.bat < answerFile.txt for Windows installations)

Starting in 6.2.2.0

The IBM UrbanCode Deploy server and agent relays now require a Java Runtime Environment (JRE) or Java Development Kit (JDK) version 8. If you are updating or changing the JRE to the latest version, see
Changing or updating the JRE of servers and Updating the JRE location for agent relays for instructions. For documentation on the IBM JRE, see IBM SDK, Java Technology Edition.

Starting in 6.2.1.1

To ensure that all secure property values are obscured, the values of all properties in the history for existing deployments are obscured. In the deployment history for deployments that you run after you upgrade, only secure properties are obscured in the logs.

New security features erase old component version import logs to hide secure information. If you want to keep the logs, in the installed.properties file, set the com.urbancode.ds.cleanup.sourceConfig.fullCleanupSkip property to true.

Plan & Prepare

For supported platforms and requirements, see the reports that can be dynamically generated using the Software Product Compatibility Reports (SPCR) tool.

Note: Some supported plug-ins have system requirements that vary from the core product. Information on system requirements for individual plug-ins is available on the download page for that plug-in.

To get started quickly to try the software, IBM UrbanCode Deploy is shipped with an Apache Derby database. Apache Derby deployments are not supported for production environments. As you plan your production topology, review the installation guide.