Discussion

WordPress error log

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

0 comments
Show all comments
Discussion

Challenges in Implementing a Continuous Monitoring Plan - Delta Risk

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...

MoreLess

0 comments
Show all comments

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 

0 comments
Show all comments
Discussion

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!

0 comments
Show all comments

Material Symbols & Icons - Google Fonts

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...MoreLess

0 comments
Show all comments

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

1 comments

Really love the idea of using templates for this. Will make creating configuration services, entity event listeners, and other utility classes...MoreLess

Show all comments

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),...MoreLess

0 comments
Show all comments

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.

2 comments

Hi, it downloads and installs both from and to source environment or one of those two should be a target ?

Do you have a video to show how it works ?

Thanks :)

Show all comments (1)

Git] GitFlow, usar ou não usar? – Código Maromba

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...

MoreLess

0 comments
Show all comments

Clio version 6.1.0.19 provides new functions to find differences in system settings, features, and packages across two Creatio instances

clio show-diff --source ENV1 --target ENV2

to save the result to a file specify the file option as follows

clio show-diff --source ENV1 --target ENV2 --file "C:\manifests\diff-env1-env2.yaml"

P/S: This command finds all data from source source which not presented or has different values on the target environment

3 comments

Great Idea!

Show all comments (2)