This is a small sidekick for this post. People often complain that automating the deployment line is sooooooo hard. It isn’t. This post explains the simplest way to automate something with the less possible effort.
I have had 2 talks about DevOps@Runtime (here and here), I’ve also been talking to people about the topic and I’ve promised to write a blog post about it, which I’m doing now. But before I can start with the Runtime, I have to talk a bit about DevOps in general and what it is. Therefore, in the prologue I will explain DevOps in a NutShell 😉
The last two month were so full with news and even fuller with work, that we had no time to publish october news, so november news have to tell all the stories.
After we decided to move everything we publish as open source into maven central and made a successful show case it’s time to start moving!
The new parent has now the sonatype parent as it’s parent (what a sentence!) and publishes everything to sonatype repositories – https://oss.sonatype.org/content/groups/public/.
To prevent version mismatch, every artifact will get a major upgrade, which means that effectively everything will start with a 2.
So it’s parent 2.0 and ano-util 2.0.0 which are already there:
and the rest will follow.
We keep you informed!