prospect:
During the National Day of 22, I did a preliminary research on XcodeCloud. What is Xcode Cloud?
I have nothing to complain about: the new mac system settings page really feels like using a mobile phone, and it is getting uglier and uglier.
After upgrading the system, I found that my xcode was no longer available and needed to be updated, so I upgraded to the latest version 14.2. Open the project and suddenly find a ☁️ on the right side of the scheme,
After clicking it, it is really the XcodeCloud beta version. The function of Xinniannian is finally available (although we have implemented most of its functions through the hook hook of github).
Let's talk about the steps to use for reference.
First set up the workflow for the first time:
Precautions:
1. You need to have a cloud warehouse. If you have not created only local code, you will be prompted to "create a gitlab or github code warehouse first."
2. The account used by xcode needs to be bound to your code warehouse, and it will jump to App Store Connect halfway, where the binding relationship between the code warehouse and your apple developer account is completed. (You can choose all the codes in your code warehouse, or you can select a specific code warehouse). After the binding is successful, you can go back to xcode to use XcodeCloud.
3. If it is detected that there is no application corresponding to the buildid in App Store Connect, a new app application page will be automatically created for you (but if the name is repeated, it will prompt an error that the creation will not be successful), the name of the scheme used here (should be is an English), not PRODUCT_NAME
It was a bit rushed to enter the experience for the first time. I forgot to take screenshots in the middle steps. I am really sorry. However, the process is also very simple, mainly to set up the workflow for the first time, bind the code warehouse, submit App Store Connect to create an app application
If the last operation is successful, you will see
At this time, there will be your app on the sync App Store Connect
Click the "start build" in the last pop-up window of XcodeCloud to start your first compilation. At this time, you will see the xcode page switch to the colud build page
Synchronize the XcodeColud page of the page that opens the current app on App Store Connect, and you can also see the current build
Subsequent use and adjustment workflow
1. Afterwards, the view entry of the xcode development tool is no longer on the right side of the scheme, and it is adjusted to here.
(The workflow I set up follows his default: when new code is submitted and merged into the current branch, it will be automatically compiled)
Or check it in App Store Connect.
2. Modify the workflow:
Of course, if you want to adjust the workflow in the future, you can also adjust it. Select it in the xcode colud of App Store Connect
Enter the details of a certain build, and see a workflow, click on 
the workflow defined at that time to view, edit, and save
3. Parameter Analysis Description
Here you can also see the first time I forgot to take a screenshot. For example: packaging environment, triggering workflow start conditions, operations, follow-up operations.
1. Initiation conditions: branch change, pull request change, label change, schedule by score.
2. Operations: archiving (no cache mode is generally required in the release App Store mode flow to ensure that the code is all verified online package code), testing (executing device unit testing), analyzing, and building build.
3. Follow-up operations: notify internal textflight, notify external textflight, email notification.
Archive: Different checks will be added for different deployment preparations (eg: if testflight is checked, then the teaching and research appicons cannot be empty, etc.)
Test: Execute unit tests. build for testing
xcodebuild build-for-testing [-workspace <your_workspace_name>]
[-project <your_project_name>]
-scheme <your_scheme_name>
-destination <destination-specifier>