15 posts tagged with "devops"

Kraken version 1.6 introduces support for Windows in deploying a virtual machine with the Kraken Agent on AWS EC2. This means that it is now possible to execute jobs on Windows systems in the AWS EC2 environment.

The 1.6 release brings several more changes and fixes. To see the details, please check the the release notes. Some of the changes included are:

• added link to docs page in the top bar
• added checking agents group correctness provided in schema
• several fixes

More details about the support for Windows in AWS EC2 are provided below (Read More).

Kraken version 1.5 introduces support for Windows in the Kraken Agent. This means that it is now possible to execute jobs on Windows systems using Kraken CI.

The 1.5 release brings several more changes and fixes. To see the details, please check the the release notes. Some of the changes included are:

• fixed detecting Kraken Agent environment when it is run inside Docker that is using CGroup v2 - this solves #303
• fixed triggering a flow by GitHub webhook when another flow is in progress - this solves #296
• fixed handling multiline secrets
• improved handling agent inactivity - now it is not needed to reenable agent when it was disabled due to inactivity

More details about the support for Windows are provided below.

The Kraken version 1.4 introduces environment variables. This feature allows for defining variables and their values associated with a branch. These variables can then be used in a workflow schema using schema context and also in shell commands as regular environment variables.

1.4 release brings several more features - check the release notes.

More details about environment variables can be found in the documentation, specifically in the Environment Variables section.

The Kraken version 1.3 introduces the conditional steps. This feature enables skipping a step under certain conditions. This condition can be based on any data available in the system including the latest data from previous steps.

1.3 release brings several more features - check the release notes.

More details about the conditional steps are below.

The Kraken version 1.1 introduces even more improvements in logging.

The major changes are:

• added storing user data server-side
• data of internal objects and user data are now exposed in a schema code
• added support for several new operating systems

1.1 release brings several more features - check the release notes.

More details about the major features are below.

The Kraken version 1.0 introduces even more improvements in logging.

The major changes are:

• added global and per-branch logs retention policy
• added presenting logs of server-side activities related to a branch, a flow, a run and a job

1.0 release brings several more features - check the release notes.

More details about the major features are below.

The Kraken version 0.1126 introduces much improved logs handling and presentation.

The standing-out features connected with logs are:

• single-line and multi-line secrets masking
• coloring ANSI codes
• no issue with handling huge logs containing even more than 10.000 lines
• switching timestamps on/off
• auto scroll when at the bottom
• paging logs

And the new features introduced by this Kraken version:

• job logs are split by steps sections in UI
• steps status and metadata presented at the top of each step logs section
• download a step log

More details are below.

CCTray is a protocol that allows users to fetch the current state of a branch using dedicated clientes.

Kraken CI exposes a URL for a given branch that can be put to such a client. This URL is available on a branch management page, in the Status Badge & CCTray tab:

These feature landed in 0.1097 version and is documented in notifications docs docs.

Till now, Kraken CI relied on pretty old versions of Clickhouse and MinIO. In the latest Kraken CI release, both have been upgraded.

Clickhouse has been upgraded from 20.11.4.13 to 22.10.2.11. The migration is seamless from the Kraken CI point of view. There is no need for explicit data migration.

MinIO has been upgraded from RELEASE.2020-12-18T03-27-42Z to RELEASE.2022-10-24T18-35-07Z. The major visible change is the names of environment variables that hold credentials. Previously they were MINIO_ACCESS_KEY and MINIO_SECRET_KEY, now they are MINIO_ROOT_USER and MINIO_ROOT_PASSWORD, respectively. Values of these variables may stay the same; they do not need to be changed.

These changes landed in 0.1091 version.

There has beed developed an addition to users management: authentication against external authentication servers using either LDAP or OpenID Connect with OAuth.

LDAP allows administrator to connect Kraken system to corporate LDAP or Active Directory. OIDC & OAuth beside bringing another source of users' identity it also provides Signe Sign-On scheme.

This features landed in 0.1047 version and is documented in identity providers docs.