While you can use Globalization Pipeline through its service dashboard, we recommend integrating Globalization Pipeline into your DevOps environment to automate Globalization Pipeline operations and make translation part of your continuous delivery infrastructure. Based on your preference, there are three scenarios for integrating Globalization Pipeline into DevOps.
Static build time integration
Globalization Pipeline provides tools that can help you perform Globalization Pipeline operations during the build phase of your app. Please explore our build tools in these topics - Maven plugin, IBM UrbanCodeDeploy plugin, Jenkins plugin, Command-line and Ant tool.
Note: These tools provide you more flexibility in terms of supported file formats and controls than the Stand-alone use of Globalization Pipeline.Dynamic run time integration
Globalization Pipeline provides SDKs and clients that you can use to perform Globalization Pipeline operations at application runtime. Please explore our SDKs/clients in SDKs and Tools . You can also perform Globalization Pipeline operations using our swagger UI. You can perform REST calls to this swagger's endpoints from your app as an alternative to taking a SDK/client approach.
Note that your swagger doc instances will be different based on our configuration of Globalization Pipeline for your team. Please contact us for swagger doc access upon onboarding.
Hybrid integration
Your team can also choose a hybrid approach to DevOps integration where you opt for Static Build Time integration for your production app instance and Dynamic Run Time integration for your test/development environment, or in any other configuration you wish.