You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chronicles is starting to take shape and would benefit greatly from its own place in our App Store.
Our other apps use DevOps for building and releasing, but seeing as we already run most of our repo scripts in GitHub using Actions, it is a good idea to follow this trend.
Getting Chronicles to App Store requires:
Building the App using XCode. This can be done in a GitHub action
Sending the .ipa to App Store under the Equinor org.
As for WHEN to build and release, I think it is nice to do this on every package release. In our package.json file is a command release:all. This triggers changesets to release all packages to the npm registery. The execution of this command is a good time to trigger the XCode build and release action.
Some considerations:
The agent must be running mac os since it requires XCode.
The job should be run independently of the other build and release jobs so that it does not block the execution of the others. Perhaps a separate action is best.
Alternatives
No response
Other info
Some reasons why it is wise to start looking at this immediately:
@marinalinn has joined our teams(s)! I am sure she would appreciate seeing this app in action. Also, welcome Marina 🎉
Physical human touch is a very important aspect when creating a great mobile UX and this will be lost when using the dev simulator.
The text was updated successfully, but these errors were encountered:
Package / App
MAD Chronicles
Description
Chronicles is starting to take shape and would benefit greatly from its own place in our App Store.
Our other apps use DevOps for building and releasing, but seeing as we already run most of our repo scripts in GitHub using Actions, it is a good idea to follow this trend.
Getting Chronicles to App Store requires:
As for WHEN to build and release, I think it is nice to do this on every package release. In our
package.json
file is a commandrelease:all
. This triggers changesets to release all packages to the npm registery. The execution of this command is a good time to trigger the XCode build and release action.Some considerations:
Alternatives
No response
Other info
Some reasons why it is wise to start looking at this immediately:
The text was updated successfully, but these errors were encountered: