The Clio team is launching a new project called T.I.D.E.! This tool will enable seamless synchronization of configurations between a Git repository and the Creatio environment directly from Creatio.

The alpha version of T.I.D.E. will be available on Friday, December 13th! 🎉

Be among the first users and help us make this product even better!

Clio version 8.0.1.4 allows redirecting logs of any command to a file. To do it, use the following form

clio <COMMAMD> <COMMAND PARAMETERS> --log d:\log\my-log-file.txt

It creates an easy way to organize data for auditing the actions and changes and their parameters

Clio version 8.0.1.3 provides the ability to show and store the last compilation log from Creatio environment

clio last-compiltaion-log -e <ENV>

To store it locally, use the --log option

clio last-compilation-log -e <ENV> --log c:\log.txt

To display RAW output from the server, use the following

clio last-compilation-log -e <ENV> --raw

WerdienJihed, thanks for your idea and contribution to the Clio project 👍

P.S: In the next releases, we will extend the list of commands that will support store log to file for improving UX work with ci/cd pipelines

Clio version 8.0.1.2 provides support for a long time compiling all configuration during CI/CD pipelines via command

clio compile-configuration --all -e MyEnv

For cases when you want to run additional compilation of your configuration after installing a package, you can use the following command

clio install MyPackage.zip --force-compilation -e MyEnv

P.S This approach can be useful for ensuring resilient CI\CD pipelines 

Clio will be updated to. NET8 starting from 8.0.1.1. The Creatio platform will be updated to .NET 8 starting from 8.2.1, which will be released in December of this year.

In the 8.0.1.1 version, a flag --ts was added to show timestamps in the log messages:

clio ping env --ts

Thanks Federico Buffa for submitting a pull request on the Clio GitHub repository!

Hi!

We are excited to announce a new feature in Clio release 6.1.0.37: the Set application icon command! This new command allows you to easily set or update the application icon for your Creatio projects directly from the command line, ensuring your application meets the Creatio Marketplace requirement.

Example of using:

clio set-app-icon -p <APP_NAME> -i <ICON_PATH> -f <PACKAGE_FOLDER_PATH>

Replace <APP_NAME> with the name or code of your application, <ICON_PATH> with the actual path to your SVG icon file, and <PACKAGE_FOLDER_PATH> with the path to the folder containing your application packages.

P.S: Set application icon command is compatible with all Creatio versions 8.0+

Happy coding!

Clio release 6.1.0.33 provides adding source code schemas to the package via Clio. It can be useful for working with C# code in IDE or Creatio embedded code designer,

// Adding source code schemas MySourceCodeSchemaName to package MyPackage
clio add-schema MySourceCodeSchemaName -t source-code -p C:\MyPackage

P.S: We plan to add more OOTB templates, the ability to create your own and add a set of different objects for complex cases like using virtual entity

New Clio release version 6.1.0.22 extends clone-env operation for simple copy your packages from one environment to another. It can be used when you want to try your code on the new version of Creatio platform or check compatibility with another products.

To clone all packages from maintainer(s), run the following command.

clio clone-env --maintainer ATF --source SOURCE_ENV --target TARGET_ENV

If you want to try a new release of Creatio, use the exclude-maintainer argument to exclude all OOTB Creatio packages.

clio clone-env --exclude-maintainer Creatio,Terrasoft --source SOURCE_ENV --target TARGET_ENV

P.S In the future, we plan to release ability transfer features and settings between environments and transfer data sets.

New Clio release version 6.1.0.21 allows clone packages from one Creatio environment to another. 

clio clone-env --source Dev --target QA --working-directory [OPTIONAL PATH TO STORE]

The command creates a manifest from the source and target, calculates the difference between them, downloads the changed package from the source environment to the working directory (optional parameter), and installs it in the source environment.

Clio release version 6.1.0.20 provides the ability to customization your app-hubs with a branch-oriented strategy. Now you can define the following structure

To define a branch use the following arguments

clio publish-app --app-name Application_1 --branch master --app-version 1.0.4 --app-hub ./builds --repo-path .

Also, support branching was added to the apply-manifest command and you can specify the branch name in the yaml file\

NOTICE: If you use a naming convention requires a zip file name to be different than app code, then use aliases in manifest file