Improvements to Post Deployment Job configurations
- FC-6409 - [#386057] - Fixed a regression caused by 6.6.0-rc7 (FC-6353) where jsonpayload was only passed when a job parameter was defined. In 6.6.0-rc6 and earlier versions, no job parameter was required.
- FC-6409 - [#386057] - Reduced confusion by changing the 'Exclude Properties' to an 'Include Properties'. Existing data will be migrated during the upgrade and does not require any user intervention.
Myst can invoke a Jenkins job in the Release Pipeline. In 6.6.0-rc6 and prior, by default Myst passed the jsonpayload parameter if any Jenkins job was defined in Myst. This was not always required.
What did we change?
We made a UI change from 'Exclude Properties' to 'Include Properties'. Your configuration is unaffected here.
We changed when jsonpayload was passed to Jenkins:
- Platform Instance or Stream Model is selected (screenshot) then jsonpayload is passed to Jenkins.
- No properties are selected then jsonpayload is not passed.
To use jsonpayload, setup the Jenkins job with a parameter named jsonpayload. The jsonpayload will consist of platform instance and stream model properties.
Known Issues
We are looking to resolve these issues in a future release candidate.
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 (ie. A user saves and commits a platform model change).
Unable to Access Terminated Platform Models
Platform Models that are in a TERMINATED state will not open and return an error. This issue was identified with a particular customer. We are yet to see this occur on other datasets. A root cause analysis is underway.
.png)
