using the jenkins CICD integration for a project

[BarrinMW]

using the jenkins CICD integration for a project

[IceT-M]

Hi Daniel,

There is just 1 pipeline definition per repository. A common scenario is that each application has a separate repository using the same template for the pipeline configuration. Some users have 1 repository for all Control-M workflows.

This code snippet might help (i'll publish this full example later this week):

for f in $path/*.json
   do
      ctm deploy $f
   done

It basically loops over a folder ($path) and executes the deploy command for each file in that directory ($f).

This could be extended to loop over over folders as well.

Let me know if this helps.

Regards,
Tijs

[BarrinMW]

Thanks - that makes sense, have implemented similar which is working now

                for f in $path/*.json
                do
                        echo "building the checked in files by validating against the build environment"
                        curl -k -silent --fail --show-error --no-include -H "Authorization: Bearer $token" -X POST -F "definitionsFile=@$f" -F "deployDescriptorFile=@deployDescriptors/$BUILD_DESCRIPTOR" "$ENDPOINT/build"
                done

[Galgc]

Another option is:

1. Use the cli package command to create a zip from the source directory, it will package all the jsons/xmls or other means to create a zip
2. Run the build against the zip file