Back to Blog

Myst Studio 6.6.0-rc16

David Tran

Bug Fixes

  • FC-6491 - [#1569] - Fixed a longstanding bug when 10+ compute nodes were in lexical order resulting in managed servers and machines being mixed incorrectly

Improvements

  • FC-6498 - The Maven settings.xml from the Continuous Delivery Profile is always stored in the `$MYST_WORKSPACE/resources/maven/settings.xml`. System Artifacts can deploy successfully as the host no longer requires direct internet access.

See the majority of improvements which were in the previous release of 6.6.0-rc13.

https://www.mystsoftware.com/post/myst-studio-6-6-0-rc13

Known Issues

We are looking to resolve these issues in a future hotfix.

Platform Model Unexpected Automatic Update

Platform Models are automatically and unexpectedly updated by Myst under the following conditions.

  • Release Pipeline stream's behaviour is set to Update a blueprint
  • Release Pipeline stage's deploy scheme is set to Automatic deployments
  • (Trigger) A new revision is created in the platform model (i.e. A user saves and commits a platform model change).
Share on social media: 

More from our Blog

Myst Studio 7.0.0-rc7

Improved jsch library security and fixed a bug with 10+ compute nodes

Read Story

Myst Studio 6.7.1

Fixed Network Channel 'Outbound Enabled' not applying

Read Story

Myst Studio 6.7.0

Fixed an NPE regression

Read Story

Connect with the myst community on our slack channel.

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa.
We will never share your email address with third parties.
Join Community