MCE^3 - Felix Krause - Continuous Delivery for Mobile Apps Using Fastlane
-
"We can't release. Chris is currently on vacation"
-
"The provisioning profiles doesn't contain all devices"
-
"We can't release an update, the build is broken"
-
"We need the latest screenshots for the website"
-
"Uh, that bug fix is not worth a new release"
Goals
- Automatic Deplyment
- Version Control
-
developer independent
ScreenShots
- Every time there's a new device size ,
- every time you change the design of application,
- every time you add a new language.
five screen shots
for six device types
for ten different languages
you end up with 300 screenshots
Provisioning Profiles
Code signing ,
and Provisioning Profiles
Dialog: Failed to code sign
* Cert : Code Signing Certificate
Code Signing Identity: 包含 a certificate 和 your private key
- this private key is only saw in the local machine ,
it is not on the Apple developer portal .That is the reason Why you have to manually transfer to a new Mac , when you like to transfer your code signing identities
- provision profiles are stored on the Apple developer portal, and can always be received from there.
关于 证书,最后 重申 again the only thing, that is only on the local machine is
the private key of your certificate
* Sign: Provisioning Profile
To generate one .
* Gym: Building & Signing
要解决的 问题: 你有几个程序员(每个人有自己的 apple id), 有几个app 项目, 乘积起来, > 证书 蛮多的
Key : Match, onboard a new user
a git repo , to define which user read access( 读权限) and write access (写权限)
方案的实质是, 将 have access for to the developer portal , 转化为 just need access to the git repo
To deploy
use fast file
新的 技术 笔记工作流,
live 笔记 / GitHub, 简书
自己的笔记中 整理/ 结构化
网友评论