You can use the build scripts to add your build artifacts
to IBM® UrbanCode Deploy for
deployment to the IBM Worklight® Server.
Procedure
You can use any of the following methods to add your build
artifacts to UrbanCode Deploy:
Option |
Description |
Copy the files into a user-defined file system |
Copy the build artifacts to a location on the UrbanCode Deploy
server's file system for a versioned file. |
Push the files to the UrbanCode Deploy server |
Use the Command-line client (CLI) to push the build artifacts
to the UrbanCode Deploy server. The CLI is a command-line interface
that provides access to the UrbanCode Deploy server. You can use
the CLI to push the build artifacts to the UrbanCode Deploy server
in the following scenarios: - When the Jazz™ Build Engine
and the UrbanCode Deploy server are not installed on the same build
computer.
- To support running the UrbanCode Deploy server on different operating
systems.
Tip: You can use the following commands to deploy
binary files to the UrbanCode Deploy server: - createVersion
- Create the component version.
- addVersionFiles
- Upload the component files.
|
Copy the files into a source-code management system |
Copy the build artifacts into a source-code management system,
such as:- Git
- IBM Rational® Asset Manager
- Subversion
|
Tip: Assign a version
to the mobile application that is deployed to the Application Center.
This version must match the version that is assigned in UrbanCode
Deploy. For example, if the mobile application has a commercial version
of 1.0 on the Application Center and the internal version from the
latest build is 16, assign version 1.0.16 to the application in UrbanCode
Deploy. Keeping the version numbers synchronized helps you to recover
if you encounter a problem. For example, if the latest version of
the mobile application was not deployed successfully to the Application
Center.