As cool as Docker is there is quite a lot of stuff you need to start caring about, service discovery, orchestration, routing and so on, and there is a long line of technologies which help you achieve that, here is quite a long list just as an example:
svn: E210007: Cannot negotiate authentication mechanism
I've encountered the above error when trying to activate an Subversion (SVN) action from a Centos server which resides in one of the corporate domains into an SVN server that resides in another corporate domains.
Before I start I would like to say it was overwhelming to see that Kohsuke Kawaguchi, Heath Dorn and all other participants who took the trip to ISRAEL inspite of the delicate situation, took the time to participate in this event. And apart of a short distruption @ 09:15 it was a quite day for the Hertzliya area ...
This blog post is to serve as my JUC summary (Worth noting: this summary wasn't sponsered / ordered by any company and reflects my personal take of Jenkins and the Jenkins user conference.)
Assuming you have a Jenkins-Gradle-Artifactory system set up correctly and you in fact have a Java project being compiled, built and published to Artiafactory correctly, there is a chance you would like to build an Uber jar, in the case of one of our customers this in Uber jar was required to include all the Build ouputs (in this case in was two jars: product.jar & product-api.jar) and all the dependent jars
We have an application that to fully test it with different phases we would need about 15 jobs (see the following post for simplification of jobs:. The problem with this is that once you branch your trunk version you do not want to duplicate all jobs.
Recently I have had the opportunity to test drive packer.io on a project I am working on, and although I have heard the word packer here and there until you start using it you do not understand the power behind it. As a side note until now there was usage Razor which by the look of it the place where packer was inspired from + a better version of veewee
What is packer ?
More than a decade ago, when I was first been introduced with Maven, I had one big issue with its concept: along side with all its benefits (and there are many as such), I didn't like the idea that for each version of my product I need to set the version of it inside the pom.xml file and save the file (with the version text inside it) as part of my code.
This concept were against any understanding I have about versioning methodologies and it caused me to actually dislike Maven. Maven 3.2.1 introduced, for the first time, a small feature that turn all the written above upside-down.