Spaceのアップデート

コード変更の追跡に役立つ展開のをサポート
7月 11, 2022
新バージョン

機能

  • Added support for deployments - A deployment is a Space entity that represents the delivery of source code changes to a deployment environment (a deployment target).
    • As a user - Deployments let you track your code changes and answer questions like “Which product version is now in production?”, “Which specific commit was used to deploy the production version?”, “How many changes (commits) were there between version A and version B?”, etc.
    • As a team - Deployments make the product release lifecycle more transparent. As you have a predefined list of deployment targets (such as web, desktop, cloud, mobile, and so on), you always know where your product is deployed. A deployment schedule lets you plan how often it is deployed.
    • As a company - Deployments can also deliver company-wide benefits. For example, think of Space deployments as a uniform standard for defining deployment targets in your company. So every released product, application version, or internal service update is recorded and tracked. This could simplify managing risks in log4j-like scenarios. Having all targets defined in Space, you can easily track which library versions are delivered to the end users.
    • A deployment in Space doesn’t run any build scripts by itself. It is just a state machine that tracks the current deployment status. The status updates are sent by a CI/CD server with the help of the space command-line tool (provided as a Docker image: public.registry.jetbrains.space/p/space/containers/space-cli:latest) or with the Space HTTP API.
    • There’s also an option to manually change the deployment state in the UI. This means that you can use deployments with any CI/CD tool of your choice, including Space Automation, JetBrains TeamCity, GitHub Actions, and others.
Configure dev environments with devfiles

Space Cloud

完全なソフトウェア開発プラットフォーム

ご質問がありますか?

今すぐ JetBrains ライセンススペシャリストとライブ チャット