Partner – CAST AI – NPI EA (tag = kubernetes)
The Kubernetes ecosystem is huge and quite complex, so it’s easy to forget about costs when trying out all of the exciting tools.
To avoid overspending on your Kubernetes cluster, definitely have a look at the free K8s cost monitoring tool from the automation platform CAST AI. You can view your costs in real time, allocate them, calculate burn rates for projects, spot anomalies or spikes, and get insightful reports you can share with your team.
Connect your cluster and start monitoring your K8s costs right away:
>> FREE Kubernetes cost monitoring
Partner – MongoDB – NPI EA (tag = MongoDB) Partner – Thundra – NPI EA (tag = Jenkins)
You can get some real insight into your CI pipelines, and into your tests by using Foresight.
This includes not just the basics but some actual, actionable data like Change Impact Analysis, where we can see the changes in a PR and correlate them to test runs and test coverage to show how they affect our builds:
>> Try out Foresight in a project
This tutorial introduces the deploy plugin, one of the core plugins of the Maven build tool.
For a quick overview of the other core plugins, refer to this article.
2. Plugin Goals
We use the deploy plugin during the deploy phase, pushing artifacts to a remote repository to share with other developers.
In addition to the artifact itself, this plugin ensures that all associated information, such as POMs, metadata or hash values, is correct.
The deploy plugin is specified in the super POM, hence it's not necessary to add this plugin to the POM.
The most noticeable goal of this plugin is deploy, bound to the deploy phase by default. This tutorial covers the deploy plugin in detail, hence we won't go any further.
The deploy plugin has another goal named deploy-file, deploying an artifact in a remote repository. This goal isn't in common use though.
This article gave a brief description of the deploy plugin.
We can find more information about this plugin on the Maven website.
res – Maven (eBook) (cat=Maven)