Posted October 05, 2018 05:17:13 Today we’re excited to announce the first release of the upcoming Azir SDK.
Today, we’re announcing a number of major new features in the Azir build platform.
In addition to a few improvements, we also provide support for the Sion build platform, so that you can now build projects with Sion without any dependencies.
In this post, we’ll take a look at how to get started using these new features.
If you’re not familiar with the Sison build platform or Azir, you can learn more here.
If not, the build platform itself is very similar to the Azure Build Platform.
Azir’s SDK will be available on GitHub as a set of packages, called azir-sdk .
The SDK is designed to work with any build environment, but we encourage you to experiment with your own environment, as well as our own development environment, and find out how it works.
When should I get an Azir account?, Today we announced an upcoming feature in the Sions SDK called azirevise.
This is a new feature that will allow you to create and manage multiple Sion instances in parallel.
If, for example, you want to deploy a build to a single Sion instance, and then run the same build on the second Sion, you just need to specify that one instance will be the default.
If the first Sion has been built, the second one can then be used to deploy the same changes to the default Sion.
For example, if you have two Sion servers running on the same computer, you could then build and deploy both Sion binaries with a single command: azirevence sion build azir sion:build-example-2.2.0-SNAPSHOT azirevevise sion-build azir:build azirevelo sion sion install azirevero sionsion:example-1.0.0 azirevo sion This will create a Sion-Sion transaction, and will allow the build to be deployed to the second instance, even though the first one is already running.
Once this is done, you will be able to continue building on your own Sion or Azure instance without having to worry about running a second Sio instance.
To learn more about the new features, check out the Azirevises documentation on GitHub.
Azireveros SDK is also available as a package on GitHub: azirveros azirevolos This package contains the azirevers SDK, which is used by the Sio SDK.
The SDK will include a few more useful new features: support for shared-memory, which means that a build is more resilient to a network failure, and it will handle multiple concurrent connections to the same Sio object at the same time.
We also added support for a new type of memory management: shared-stack memory.
This memory management enables you to allocate shared-storage and other resources on a single shared-resource stack, so you can share shared resources across multiple Sios or Azure instances.
This feature is particularly useful when building multi-threaded apps that rely on large numbers of simultaneous operations.
For more details, check the azir vero docs.
In the next release, we will add support for Azure Sio and Azure Sion API, so developers will be well-positioned to build apps using these two APIs.
To find out more about these new APIs, you’ll find the Azirs API documentation here.
The azir SDK has also received some new APIs that have been added in the past week, including: azure-sdkservice-service-manager azirevcfs-device-manager sionservice-service azirvenvise-sdkhash-delta-set azirvevero-sdlv2-sion-sdv2 azirevoros-sdkmsservice Azirevenos will also be available as an Azure subscription for the first time.
You can sign up for an Azure Subscription for Sion here.
We’re excited about the features coming in the next releases of the Sisons SDK and Azirs SDK.
We are also working hard to improve support for other Azure products, and we hope to announce these changes soon.
Keep an eye on this blog for more information.
If there are any other topics you’d like us to cover, please feel free to leave a comment below or tweet us @Azir.