1 / 11

Yikes.. PATCHES!

Yikes.. PATCHES!. Big freakin topic, Need to organize efforts Concerned about tangents and progress Short Term and Long Term Making Progress. Short Term. Current Process (next slide) Don’t worry about what a patch is, other than a set of files with information about how to install.

niesha
Download Presentation

Yikes.. PATCHES!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Yikes.. PATCHES! • Big freakin topic, Need to organize efforts • Concerned about tangents and progress • Short Term and Long Term • Making Progress

  2. Short Term • Current Process (next slide) • Don’t worry about what a patch is, other than a set of files with information about how to install. • Must Organize them • patch repository • WEBDAV? SupportForce? • categorize them in salesforce. • Add “Solution” or “Patch” • Categorize Patch (Product, Version, Type) • Add link to real patch ( we might add gui within salesforce, no second gui) • Add notes about how to install. • Patch because of CASE • If it was because of a case, go to that case and link solution/patch. • If patch is specific to customer and not for the world, only make it available within a case. • Should rarely be the case. • When a “patch” • Anything that is an update to a stable/supported release. • From a case • Developer retrofits optimization backwards. • Need to encourage some of this • What a “package” • Service Pack, Release, Patch • They all need to be made avialable through the network • Ant TASK to take “BUILD(tar/zip)” and push to patch repository.

  3. Actor Customer Developer Community Find Defect! Opening Action Opens Case Post on Forum Opens JIRA Issue L/M/H Decision Point Developer writes code for solution Development Code checked into CVS on a branch Code added to tip of major Code added to tip of major Somebody BUILDS it Get’s built in a minor release build Get’s built in a minor release build Somebody pulls the changed files and zips into patch Closing Action Adds File/Notes To Case Developer Responds On Forum Notes entered in JIRA Closes Case

  4. Short Form for updated Process Find Defect Optimizations Code Enhancement WRITE/TEST And CHECK-IN CODE BUILD TEST CODE Community Release? PROMOTE SourceForge JBNet Repository

  5. Short Term Items • Create Package Repository – Frank/Eric • PROMOTE TASK (Ryan?/Rich) • push build to repository • Create item in salesforce • Add PATCH to salesforce (Frank/Rich) • Categorization Scheme to represent in salesforce (Ivelin?) • Support Process Doc (Rich/Luc)

  6. Long Term • Build System • Build • Types of Builds • Package • Types of packages • Promote • Types of promotion • Package Repository • Files • Metadata • Integration with Salesforce • How to exposte to customers • Getting JBN packages • Portal, Admin Server, Command Line • Unpack and Deploy • Reading a server (managing conflicts) • Moving files • Unwrapping and restart • Hot • Unpacking for JBoss AS • How to support release, servicepack, patch • Order of preference • System jars vs /server directories • What is a PATCH • Two Options • Mature – jar with updated classes laid down • Open – A replacement for something that exists • What is a PACKAGE • RPM with only JAVA Commands. • JRPM • Related – Dependency representation in the formats

  7. Public promote sourceforge Public package Public build Standard Package jpackage Release Release Package Release Patch CVS JBN Repository Package Service Pack Patch Private build Package Salesforce Service Pack Developer Private Package Private Promote

  8. network Person Some Machine Customer Portal JBN Repository Command Line Salesforce Admin Server Local Repository SOAP

  9. Some Machine SYSTEM(S) Command Line JBoss Admin Server Local Repository /xx/patch /xx/servicepack /xx/lib /xx/deploy /xx/conf NodeMgr

  10. Long Term Items • What is a release/servicepack/patch • What is a package • BuildSystem - Build/Package/Promote • Package Repository • Portal, SOAP Integration • Admin Server, Command Line • Unpackage/Deploy • Application Server

  11. Making Progress • Will manage tasks within JIRA – JBN. Link to related tasks. • Weekly meeting • Proposal for Architecture Council – When? • Short Term Changes Review to Dev and Support – When?

More Related