We are in the world of multiple distributed different env.
World of Packaging
-----------------------------------------
System Packaging
package format FROM?
- WINDOWS exe - msi nuget.org or chocolatey
- LINUX
- Ubuntu debian apt repo
- RHEL rpm yum repo
- MAC dmg apple store
- ANDROID apk play store
App Packaging
package format FROM?
- GENERAL zip - tar MULTIPLE
- DOTNET dll - exe MULTIPLE
- JAVA jar - war - ear repo.maven.apache.org
You are developing exe msi debian rpm dmg apk zip tar jar - war - ear
- Where would i store all these private packages?
TYPES OF PACKAGE VERSION
- STABLE VERSION PACKAGE
- NON-STABLE VERSION PACKAGE
Org
- Have Multiple Project
- Have multple components/module/service
- Have Dependency on Internal or External pack
How we manage Internal depenendency for Multiple Project?
- Self service centralized platform
How we manage External depenendency for Multiple Project?
- Self service centralized platform
Security
- ROLE BASED ACCESS CONTROL
- EACH PROJECT
- WHO ADMIN
- WHO WRITE
- WHO READ - DEFAULT ALL
MUST UNDERSTAND YOUR BUILD TOOLS
- Maven
- Gradle
- Ant
- Msbuild
- pybuilder
- gobuild
- make
- bash
- ps
ENFORCE PROCESS and BEST PRACTICES IMPLEMENTATION
- During Build time
- During run time
- During Storing time
- Naming convention
- etc
Ease of Admin & Ops team.
- BACKUP
- Restoration
- Cleanup
- org policy implementation
Maintaining Package integrity????
software.exe --> blr ----HACKED/MODIFIED----> Us office ---> PROD --> Millions of users
DEV ---> QA ---> PROD
--------------------
SAME PACK
- CHECKSUM
- PGP
- SHA
- MD5