I don’t need to introduce either of these. Let’s just get to the point. The goal is ultimately to configure Jenkins packaging successfully. Free your hands. Used often, but they have never been configured. So learn about configuration

  1. First let’s configure Fastlane packaging. Fir plugins and dandelion plugins are installed in Fastlane, which will be automatically uploaded after the package is successfully packaged, and then the slack, email and other notifications can be opened after the success.
  2. I won’t focus on Fastlane here. After all, there are a lot of articles on the net, I casually looked for one, we can refer to fastlane packaging automatic tutorial
  3. At this time, Fastlane can be packaged at the terminal and uploaded to dandelion or FIR. If Jenkins has a problem, you can quickly whip out a new package with Fastlane without delay. You can configure packaging commands for these different environments. Of course, you can better name yourself
  4. Fastlane autopackage some commands
  • Fastlane ios autoCfg env: Appstore Desc: Automatic packaging
  • Test package: Fastlane ios autoCfg env:dev desc: automatic packaging
  • Simulation package: fastlane ios autoCfg env:pre_release DESC: automatic packaging
  • Preview package: Fastlane ios autoCfg env:verifityPreviewApp desc: automatic package

The next point is Jenkins.

  • Install Jenkins to install Java JDK 8 connection https://www.oracle.com/java/technologies/javase-downloads.html first
  • After installing Java JDK, check java-versoin on the terminal to see whether the installation is successful.

Then it’s time to sneak Jenkins. There are two installation methods: terminal installation and download installation packages.

  • Brew Install Jenkins is a command line installation, I tried it, felt too slow, gave up, directly introduce the download and install.
  • Jenkins download the macOS version of LTS, which is conveniently a.pkg file, and install it. Download the Jenkins website link directly. You have to be careful when you turn around here.

Correct to find Jenkins installed under this directory.

Java-jar Jenkins. War // The default port is 8080, which can be changed if specified

Java-jar Jenkins. War –httpPort=8888 // Select either port 8888

That’s when Jenkins’ operating environment kicks in. After the belt is successfully started, type http://localhost:8888 // in the browser to write the specified number of ports. The default port is 8080

  • Do not close the terminal

  • The following interface will appear when you run it for the first time, prompting you to fill in the contents of the specified path file (the contents can also be seen on the terminal).

  • And then I’m going to take this and I’m going to find this path and I’m going to open the initialAdminPassword file and I’m going to copy the password and I’m going to continue.

  • I’m gonna go ahead and say New

    Then you can click OK

Then add your own Git connection. Here I’m logging in with my account and password

The branch here, you replace it with a variable, and then you configure it according to your branch structure

This time their own configuration can choose branches outside

Finally, configure the shell script

Finally, configure the post-build operations

Then you can pack happily

Refer to the link

www.jianshu.com/p/56518eb05…

www.jianshu.com/p/dc6f3fea7…

Update the error problem encountered, and the solution, record, welcome to exchange.

Fastlane met a similar one while packing

This is the first time to choose the configuration certificate, you need to enter the computer password, select all allow, I used Xcode package successfully once, then use Fastlane type, there will be no problem.