If you standardize your deployment scripts on bash then there is very little training needed for your sysadmins. This set of tools is: bash, curl, md5sum. For this reason, I often suggest bash coupled with a set of "lowest common demoninator" tools that are going to be available on almost every Linux distribution. While you could write a custom Java application to interact with Nexus using the Aether library, if you did so you would be creating a system that would need to maintained by a group of Java developers. This newly emerging space is often called Devops and it is a particularly interesting part of the modern IT department. Deploying software to production networks is very often a responsibility shared by two separate teams: Development and Operations with an Operations group owning much of the process. While there are many options, I would argue for something closer to Puppet or a custom script. The production automation and deployment space has thousands of options from Puppet to ControlTier to OSGi-based solutions to approaches that involve a series of custom scripts. Deployment Scripts: What to write them in Once you've mastered complex assemblies and created Matrix jobs to publish release artifacts to Nexus, you start to see Nexus as a central part of your approach to deploying software to various environments.
If you've used Nexus for development and you've perfected the art of continuous integration, you may have noticed that Nexus does more than just support development.
0 kommentar(er)
