Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G Guides
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ios-general
  • Guides
  • Wiki
  • jenkins auto build

jenkins auto build · Changes

Page history
ar.kalmykov created page: jenkins auto build authored Mar 26, 2018 by Artem Kalmykov's avatar Artem Kalmykov
Hide whitespace changes
Inline Side-by-side
Showing with 10 additions and 0 deletions
+10 -0
  • jenkins-auto-build.md jenkins-auto-build.md +10 -0
  • No files found.
jenkins-auto-build.md 0 → 100644
View page @ 9c70b4a7
Server is currently hosted locally on 192.168.88.177:8080.
If you want to create a new app for auto builds go to Jenkins and copy an existing job (e.g. iOS_ITPMonitor_Testflight).
# Structure
- `This project is parameterized` checkbox is turned on, and LiveBuild boolean argument is added. It is used later to determine which configuration should be used.
- `Prepare an environment for the run` checkbox is turned on. `Keep Jenkins Environment Variables` and `Keep Jenkins Build Variables` sub checkboxes are turned on to ensure this job receives the required environment variables (passwords, fastlane path etc).
- `Source code management` section should be setup according to the project. The good practice is to give `Jenkins` Gitlab user permissions to read/write into the repository and use that user's credentials in Jenkins job. Don't forget to specify the default branch.
- Under `Source code management` `Wipe out repository & force clone` option may be specified under `Additional behaviours` to be sure that git-related commands succeed.
- Under `Post-build actions`, `Archive the artifacts` option may be specified with the following parameter: `*.ipa, *.dSYM.zip` to export `ipa` file and debug symbols.
- Under `Post-build actions`
\ No newline at end of file
Clone repository
  • Swift Code Style
  • automated slack builds
  • continuous integration
  • Home
  • jenkins auto build
  • shared localization
  • versioning rules