Difference between revisions of "Packaging for deployment"
From CitconWiki
Jump to navigationJump to search (Rough outline) |
m (Link) |
||
| Line 5: | Line 5: | ||
== Java == | == Java == | ||
| − | [[Scarytom]] described how his company currently used a shared director to hold executable jars from which the deployment tool plucks them for deployment into production. The problems with this are a lack of resiliency --not highly available, and tends to fill up. The idea of wrapping the jars in Debian packages and using the o/s package manager was well received. | + | [[User:Scarytom]] described how his company currently used a shared director to hold executable jars from which the deployment tool plucks them for deployment into production. The problems with this are a lack of resiliency --not highly available, and tends to fill up. The idea of wrapping the jars in Debian packages and using the o/s package manager was well received. |
== JavaScript == | == JavaScript == | ||
Latest revision as of 23:19, 20 September 2014
packaging for deployment
Relativity small group gathered to discuss how releasable artifacts were packaged for deployment into production.
Java
User:Scarytom described how his company currently used a shared director to hold executable jars from which the deployment tool plucks them for deployment into production. The problems with this are a lack of resiliency --not highly available, and tends to fill up. The idea of wrapping the jars in Debian packages and using the o/s package manager was well received.
JavaScript
? Said he was using maven with the Wagon plugin to essentially copy files directly into production.
python
Zip
iOS
Someone described a system they had built that used a web robot like selenium to drive the apple app website automatically.
