MettleCI provides a set of processes and plugins for performing Continuous Integration/Deployment on Information Server assets but it doesn't prevent teams from using any of Bamboo's other facilities to work with source files of other types. In fact, Data Migrators actively encourage customers to customise their MettleCI plans for each site and project to ensure that their Shell files, SQL scripts, etc are managed with the same level of control as their Information Server assets.
DataStage assets of all types can be checked in from the Check in menu item. Non-DataStage assets can be checked-in using other Git tools (e.g. Atlassian SourceTree), the Git command line, or the Bitbucket GUI. An important step is that each checked in asset is associated with a Jira story. This is easily achieved using Bitbucket's Smart Commits feature, which enables Developers to specify Jira stories and (optionally) Jira workflow transitions as part of their assets' commit messages. When MettleCI performs a deployment, all assets associated with the deployed stories are propagated to the specified target environment. Similarly, all assets associated with each story are visible in Jira.
DataStage project level configuration files such as DSParams, UVCONFIG, uvodbc.config, and Parameter Set files are checked in to Git and MettleCI deploys them to ensure all environment variables and project specific settings are managed like any other Information Server asset. These are explicitly referenced in the deployment plan as a requirement for provisioning a cleanroom target project.