Skip to content

0.54.1

Latest
Latest
Compare
Choose a tag to compare
@yesnault yesnault released this 02 Apr 14:27
· 290 commits to master since this release
v0.54.1
b38eaf8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Note about upgrading CDS

Please install version 0.53.0 before installing this new release.

When you are upgrading CDS:

  • backup your database before any operation

Notable Changes in version 0.54.1

In the full changelog, you will find a lot of commits about "workflow v2" / "ui" / "hook" / "ascode". All this work is here to prepare the new CDS "As Code". You will alredy find some documentation about new features, but we will make a full presentation of the new engine when it will be ready for production use.

As part of this new engine, we had to refactor the way that CDS commmunicates with the VCS Servers (bitbucket, github, etc...). This refactoring makes it easier to manage authorization based on Personal Access Tokens, instead of using oauth2 as before.
In the latest version 0.53.0, this was already refactored: you could manage VCS Server with the old and new way. With the version 0.54.1, you can only manage your VCS server one way.

If you migrate from a version 0.53, you have two solutions:

  • solution A: migrate on the new VCS system before installing the 0.54.1 version
  • solution B: install the version 0.54.1 and use the new VCS system. The VCS communication will be unavailable until you set the vcs server in each cds project.

Solution A

The cdsctl binary contains all commands to manage VCS Server on your CDS projects.

cdsctl experimental project YOUR_CDS_PROJECT_KEY, replace YOUR_CDS_PROJECT_KEY with the KEY of your CDS Project.

Github

Generate a new token on https://github.com/settings/tokens with the following scopes:

  • repo:status
  • public_repo

Create a yml file, example of vcs-github.yml file:

version: v1.0
name: github
type: github
description: "my github"
auth:
    username: your-username
    token: ghp_your-token-here
options:
    urlApi: "" # optional, default is https://api.github.com
    disableStatus: false    # Set to true if you don't want CDS to push statuses on the VCS server - optional
    disableStatusDetails: false # Set to true if you don't want CDS to push CDS URL in statuses on the VCS server - optional
    disablePolling: false   # Does polling is supported by VCS Server - optional
    disableWebHooks: false  # Does webhooks are supported by VCS Server - optional

Then import the configuration:

cdsctl project vcs import YOUR_CDS_PROJECT_KEY vcs-github.yml

Bitbucket Datacenter

Example with vcs-bitbucket.yml file:

version: v1.0
name: bitbucket
type: bitbucketserver
description: "My Bitbucket Datacenter"
url: "http://localhost:7990/bitbucket"
auth:
    user: username-on-bitbucket
    token: the-long-token-here
options:
    disableStatus: false    # Set to true if you don't want CDS to push statuses on the VCS server - optional
    disableStatusDetails: false # Set to true if you don't want CDS to push CDS URL in statuses on the VCS server - optional
    disablePolling: false   # Does polling is supported by VCS Server - optional
    disableWebHooks: false  # Does webhooks are supported by VCS Server - optional

Then import:

cdsctl project vcs import YOUR_CDS_PROJECT_KEY vcs-bitbucket.yml

Solution B

It's the same as solution A, but your will find the useful commands with cdsctl project vcs (instead of cdsctl experimental project vcs)

The version 0.54.1 allows you to use the webui to configure the VCS project.

What's Changed

Features

Bug Fixes

Full Changelog: v0.53.0...v0.54.1

Contributors

alrs, yesnault, and 6 other contributors
Assets 39
Loading