MyST allows each artifact build from a CI server to be auto-registered in MyST Studio at build-time. From MyST Studio, artifacts can be grouped into one of more Application Blueprints. However, if you wish to add a lot of artifacts to a blueprint then you may wish to do this via a programmable interface so that it can be performed in bulk. Bulk loading of artifacts and associating them with application blueprints can be facilitated with two automations:
- Automated job creation to ensure all of the artifacts to be later included in an application blueprint are pre-seeded
- Bulk automated association of artifacts within application blueprints using the REST APIs
Automated job creation
CI build jobs can be configured to automatically push to MyST Studio. This registration must be performed prior to any attempt to group Artifacts into Application Blueprints.
If you are using Jenkins for CI and need to create a large number of automated build jobs from scratch Groovy scripts are a great way to do this.
Creation of application blueprints using REST APIs
Once artifacts are imported
- you can get a list of them
- each artifact ID can then be referenced into an ABP file
The following will give you the list of registered artifacts in MyST Studio:
curl -k -X GET -H "Authorization: Bearer $MYST_TOKEN" https://$MYST_HOST/api/v1/release-management/artifacts?topLevel=true&withBuilds=true&withVersions=true
Once we have the list of artifacts, we can obtain their identifier. For example, in the following example the identiifer of StockTraderOrder is -1470134432437629926 and the identifier of StockExhangeListingSchema is 5583472864719133317
{
"data": [
{
"id": "-1470134432437629926",
"name": "StockTraderOrder",
"resourceType": "ARTIFACT",
...
},
{
"id": "5583472864719133317",
"name": "StockExhangeListingSchema",
"resourceType": "ARTIFACT",
...
}
],
...
}
If we wanted to then include 1.0 of these artifacts in a new Application Blueprint called Stock we could create a payload like this:
{
"initialVersion": {
"version": "1.0.0",
"artifacts": [
{
"id": "-1470134432437629926",
"userVersion": "1.0"
},
{
"id": "5583472864719133317",
"userVersion": "1.0"
}
]
},
"versions": [],
"postCIJobDef": {},
"name": "Stock"
}
To push this to the MyST Studio, we can then execute push this payload to the cloud (assuming it saved to a file called abp.json) with a curl command similar to the following:
curl -k -X POST -H "Authorization: Bearer $MYST_TOKEN" -H "Content-Type: application/json" -d @abp.json https://$MYST_HOST/api/v1/release-management/application-blueprints
