2024

Here are the highlights of new and updated features for this release:

When you push a pipeline using the Saagie CI/CD process, a link to the source code is added to the pipeline’s graph, on the Overview page.

You cannot change this link by hand. Also, if you create a new version of your pipeline via the Saagie platform, the link to the source code is removed as it is no longer relevant. However, the link remains accessible from the corresponding version of your pipeline.

For more information, see Using the CI/CD.

You can now modify your pipeline via the Code tab. The Code tab has been added to the Edit mode of your pipeline. It allows you to view, copy, import, and export your pipeline as code.

The Code tab is linked to the Design tab, which is the visual mode to edit your pipeline, the one you are already familiar with. Changes made in one will be reflected in the other. Synchronization takes place as soon as you switch from one tab to the other.

For more information, see Upgrading Pipelines.

In addition to existing environment variables that are set at the global, project, and pipeline levels, you can now create environment variables at the app level.

For more information, see the app Environment Variables Page.

This new version of the Saagie installer is now also compatible with Kubernetes versions 1.26.x and 1.27.x.

For more information on supported versions of Kubernetes, see the Compatible Kubernetes Versions.

Saagie is now compatible with the two versions of cgroups in Linux: cgroup v1 and cgroup v2.

For more information on supported versions of cgroups, see Compatible cgroup Versions.

The procedure for upgrading Saagie to this new version is different from the usual one. It applies only to the upgrade to version 2024.02 of Saagie.

It added some configuration process for Saagie platform on Kubernetes, where PVCs and secrets are labeled with installation IDs.

For more information, see Upgrading Saagie to Version 2024.02.

The button for upgrading your jobs, apps, and pipelines existed under two different names: Edit and Upgrade app/job/pipeline.

To avoid confusion, we have decided to only keep the Edit button. You can find it on the Overview page of your app, job, and pipeline.

The process to delete projects, jobs, apps, pipelines, and pipeline versions has been improved. Now, to delete any of these items, you must manually enter a confirmation message before you can confirm the deletion. This message is case sensitive. It prevents you from deleting items by mistake.

We have added the ability to sort the list of projects and pipelines for consistency. This also improves your user experience.

You can now find the Sort by filter in your projects and pipelines library.

Except from the Overview page of a job or a pipeline, it was not possible to know who has started an instance.

From now on, you can see who has started an instance from the Instances page of your job or pipeline.

If it is a manual run, there will be a Started by mention with the name of the person who did the run.

If it is a scheduled run, there will be a Started mention with a Scheduled badge.

When expanding the size of your storage space, a status badge is now display to indicate that the operation has started. Wait a few minutes and manually refresh the page.

There is no new technology that has been added to the Saagie technology repository for this release.

Here are the highlights of new and updated features for this release:

You can now move a pipeline from one project to another and on a different platform from the pipeline library or its Overview page. Click the kebab menu   Move to… and enter the required information. The moved pipeline keeps its jobs, conditions, pipeline environment variables, versions, instances, logs, alerts, and resource settings.

This avoids you to start from scratch and improves your productivity.

For more information, see Moving a Pipeline to Another Project.

Duplicating pipelines was already possible, but only to make a shallow duplication of it. You can now make a deep duplication of your pipelines.

This avoids you to start from scratch and improves your productivity.

For more information, see Duplicating Pipelines.

Just like jobs, pipelines now have an alias in addition to their name. A pipeline alias is required and unique to each pipeline in a project.

For more information, see Pipeline Alias.

It was already possible to increase the capacity of your storage space, but we have made some improvements to it.

As an administrator, the configuration for your storage space size has changed. When you will launch the latest Saagie installer, you will have to specify the step and maximum size of the storage space. These values will be displayed on your Saagie platform when creating or editing a storage space.

→ For more information, see Storage Space Size Settings.

As a user, you can manage the size of your storage space with a slider. Its minimum and maximum size is defined by your administrator when configuring the size of the storage spaces.

→ For more information, see Modifying Storage Space Settings.

From the storage space library of your project or app, you can now duplicate a storage space. The duplication includes a complete copy of the original storage space with its contents.

This avoids you to start from scratch and improves your productivity.

For more information, see Duplicating Storage Spaces.

When you push a job using the Saagie CI/CD process, a link to the source code is added to the package of the job.

You cannot change this link by hand. Also, if you change your job package via the Saagie platform, the link to the source code is removed as it is no longer relevant. However, it remains accessible from the corresponding version of your job.

For more information, see Using the CI/CD.

As an administrator, you can now configure your Saagie platform(s) so that you can log in using SSO. To do so, you must enable the SSO option when upgrading Saagie. When you will launch the latest Saagie installer, answer SSO at the Authentication Mode prompt when configuring the deployment mode.

→ For more information, see also Enabling Single Sign-On (SSO) Authentication.

As a user, once the SSO system has been set up, you will be able to log in to Saagie with the defined identity provider.

→ For more information, see Connecting to Saagie Using SSO For the First Time.

The following technologies have been added in the official Saagie technology repository: