DOCSLIB.ORG

Conan Documentation Release 1.3.3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Conan Documentation Release 1.3.3 conan Documentation Release 1.3.3 conan Sep 24, 2021 CONTENTS 1 Upgrading to conan 1.0 3 1.1 Command line changes..........................................3 1.2 Deprecations/removals..........................................3 1.3 Settings and profiles. Gcc/CLang versioning..............................4 1.4 New features...............................................4 2 Introduction 5 2.1 Open Source...............................................5 2.2 Decentralized package manager.....................................5 2.3 Binary management...........................................6 2.4 Cross platform, build system agnostic..................................6 2.5 Stable...................................................7 3 Install 9 3.1 Install with pip (recommended).....................................9 3.2 Install from brew (OSX)......................................... 10 3.3 Install from AUR (Arch Linux)..................................... 10 3.4 Install the binaries............................................ 10 3.5 Initial configuration........................................... 10 3.6 Install from source............................................ 11 4 Getting started 13 4.1 A Timer using POCO libraries...................................... 13 4.2 Installing dependencies......................................... 14 4.3 Building the timer example....................................... 16 4.4 Inspecting dependencies......................................... 16 4.5 Searching packages........................................... 17 4.6 Building with other configurations.................................... 17 5 Using packages 19 5.1 Installing dependencies......................................... 19 5.2 Using profiles............................................... 23 5.3 Workflows................................................ 25 6 Creating packages 29 6.1 Getting started.............................................. 29 6.2 Recipe and sources in the same repo................................... 33 6.3 Package development flow........................................ 34 6.4 Packaging existing binaries....................................... 39 6.5 Understanding packaging........................................ 41 6.6 Define package ABI compatibility.................................... 43 i 6.7 Inspecting packages........................................... 48 6.8 Packaging approaches.......................................... 49 6.9 Tools for package creators........................................ 54 7 Uploading packages 57 7.1 Remotes................................................. 57 7.2 Uploading packages to remotes..................................... 58 7.3 Using Bintray............................................... 59 7.4 Artifactory Community Edition for C/C++............................... 63 7.5 Running conan_server.......................................... 65 8 Package apps and devtools 71 8.1 Running and deploying packages.................................... 71 8.2 Creating conan packages to install dev tools............................... 74 8.3 Build requirements............................................ 78 9 Mastering conan 83 9.1 Use conanfile.py for consumers..................................... 83 9.2 Conditional settings, options and requirements............................. 85 9.3 Version ranges.............................................. 86 9.4 Build policies............................................... 86 9.5 Environment variables.......................................... 87 9.6 Virtual Environments........................................... 88 9.7 Logging.................................................. 90 9.8 Sharing the settings and other configuration............................... 92 9.9 Conan local cache: concurrency, Continuous Integration, isolation................... 93 10 Systems and cross building 95 10.1 Cross building.............................................. 95 10.2 Windows Subsystems.......................................... 102 11 Integrations 105 11.1 CMake.................................................. 105 11.2 Autotools: configure/make........................................ 110 11.3 Visual Studio............................................... 110 11.4 Xcode................................................... 112 11.5 Compilers on command line....................................... 114 11.6 Android Studio.............................................. 116 11.7 CLion................................................... 121 11.8 Ninja, NMake, Borland......................................... 126 11.9 pkg-config and pc files.......................................... 126 11.10 Boost Build................................................ 130 11.11 QMake.................................................. 130 11.12 Premake................................................. 131 11.13 qbs.................................................... 131 11.14 Meson Build............................................... 132 11.15 Docker.................................................. 133 11.16 Git.................................................... 133 11.17 Jenkins.................................................. 133 11.18 Travis Ci................................................. 136 11.19 Appveyor................................................. 138 11.20 Gitlab................................................... 140 11.21 Circle CI................................................. 141 11.22 YouCompleteMe (vim).......................................... 143 11.23 SCons................................................... 143 ii 11.24 Custom integrations........................................... 144 12 Howtos 149 12.1 How to package header-only libraries.................................. 149 12.2 How to launch conan install from cmake................................ 151 12.3 How to create and reuse packages based on Visual Studio....................... 152 12.4 Creating and reusing packages based on Makefiles........................... 155 12.5 How to manage the GCC >= 5 ABI................................... 157 12.6 Using Visual Studio 2017 - CMake integration............................. 158 12.7 How to manage C++ standard...................................... 161 12.8 How to use docker to create and cross build C and C++ conan packages................ 162 12.9 How to reuse Python code in recipes................................... 165 12.10 How to create and share a custom generator with generator packages................. 168 12.11 How to manage shared libraries..................................... 171 12.12 How to reuse cmake install for package() method............................ 177 12.13 How to collaborate on other users’ packages.............................. 177 12.14 How to link with Apple Frameworks.................................. 178 12.15 How to collect licenses of dependencies................................. 179 12.16 How to capture package version from text or build files......................... 179 12.17 How to use Conan as other language package manager......................... 180 12.18 How to manage SSL (TLS) certificates................................. 185 13 Reference 187 13.1 Commands................................................ 187 13.2 conanfile.txt............................................... 223 13.3 conanfile.py............................................... 225 13.4 Generators................................................ 250 13.5 Profiles.................................................. 265 13.6 Build helpers............................................... 269 13.7 Tools................................................... 284 13.8 Configuration files............................................ 301 13.9 Environment variables.......................................... 306 14 Videos and links 313 15 FAQ 315 15.1 General.................................................. 315 15.2 Using conan............................................... 316 15.3 Troubleshooting............................................. 317 16 Changelog 321 16.1 1.3.3 (10-May-2018)........................................... 321 16.2 1.3.2 (7-May-2018)........................................... 321 16.3 1.3.1 (3-May-2018)........................................... 321 16.4 1.3.0 (30-April-2018).......................................... 322 16.5 1.2.3 (10-Apr-2017)........................................... 322 16.6 1.2.1 (3-Apr-2018)............................................ 323 16.7 1.2.0 (28-Mar-2018)........................................... 323 16.8 1.1.1 (5-Mar-2018)............................................ 324 16.9 1.1.0 (27-Feb-2018)........................................... 324 16.10 1.0.4 (30-January-2018)......................................... 326 16.11 1.0.3 (22-January-2018)......................................... 326 16.12 1.0.2 (16-January-2018)......................................... 326 16.13 1.0.1 (12-January-2018)......................................... 327 16.14 1.0.0 (10-January-2018)......................................... 327 iii 16.15 1.0.0-beta5 (8-January-2018)...................................... 327 16.16 1.0.0-beta4 (4-January-2018)...................................... 327 16.17 1.0.0-beta3 (28-December-2017).................................... 327 16.18 1.0.0-beta2 (23-December-2017).................................... 328 16.19 0.30.3 (15-December-2017)....................................... 328 16.20 0.30.2 (14-December-2017)....................................... 328 16.21
Load more

Recommended publications
  • Drupaltools Forks 11 Stars 44
    DrupalTools forks 11 stars 44 A list of popular open source and free tools that can help people accomplish Drupal related tasks. Acquia Dev Desktop (2015) Source: dev.acquia.com/downloads Docs: docs.acquia.com/dev-desktop Drupal: 7, 8 Description: Acquia Dev Desktop is a free app that allows you to run and develop Drupal sites locally on your computer and optionally host them using Acquia Cloud. Use Acquia Dev Desktop to evaluate Drupal, add and test other Drupal modules, and develop sites while on a plane or away from an internet connection. Requires: macos, windows Category: deployment, development, testing Aegir (2007) Source: github.com/aegir-project Docs: docs.aegirproject.org Drupal: 6, 7, 8 Description: Aegir allows you to deploy and manage many Drupal sites, and can scale across multiple server clusters. Aegir makes it easy to install, upgrade, and backup an entire network of Drupal sites. Requires: linux, own-server Category: clustering, hosting, multisite, paas Amazee Silverback (2019) Source: github.com/AmazeeLabs/silverback Drupal: 8 Description: A composer package adding common project dependencies, tooling and configuration scaffolding to Amazee Drupal projects. It aims to improve product quality and reduce maintenance costs by encouraging three simple principles: Maximize open source, Minimize requirements, Testability first. Requires: composer Category: building, cli, deployment, development, provisioning, scaffolding, testing Aquifer (2015) Source: github.com/aquifer/aquifer Docs: docs.aquifer.io Drupal: 6, 7, 8 Description: Aquifer is a command line interface that makes it easy to scaffold, build, test, and deploy your Drupal websites. It provides a default set of tools that allow you to develop, and build Drupal sites using the Drush-make workflow.
    [Show full text]
  • Automating Drupal Development: Make!Les, Features and Beyond
    Automating Drupal Development: Make!les, Features and Beyond Antonio De Marco Andrea Pescetti http://nuvole.org @nuvoleweb Nuvole: Our Team ),3.0<4 0;(3@ )Y\ZZLSZ 7HYTH Clients in Europe and USA Working with Drupal Distributions Serving International Organizations Serving International Organizations Trainings on Code Driven Development Automating Drupal Development 1. Automating code retrieval 2. Automating installation 3. Automating site configuration 4. Automating tests Automating1 code retrieval Core Modules Contributed, Custom, Patched Themes External Libraries Installation Pro!le Drupal site building blocks drupal.org github.com example.com The best way to download code Introducing Drush Make Drush Make Drush make is a Drush command that can create a ready-to-use Drupal site, pulling sources from various locations. In practical terms, this means that it is possible to distribute a complicated Drupal distribution as a single text file. Drush Make ‣ A single .info file to describe modules, dependencies and patches ‣ A one-line command to download contributed and custom code: libraries, modules, themes, etc... Drush Make can download code Minimal make!le: core only ; distro.make ; Usage: ; $ drush make distro.make [directory] ; api = 2 core = 7.x projects[drupal][type] = core projects[drupal][version] = "7.7" Minimal make!le: core only $ drush make distro.make myproject drupal-7.7 downloaded. $ ls -al myproject -rw-r--r-- 1 ademarco staff 174 May 16 20:04 .gitignore drwxr-xr-x 49 ademarco staff 1666 May 16 20:04 includes/ -rw-r--r-- 1 ademarco
    [Show full text]
  • Linux from Scratch 版本 R11.0-36-中⽂翻译版 发布于 2021 年 9 ⽉ 21 ⽇
    Linux From Scratch 版本 r11.0-36-中⽂翻译版 发布于 2021 年 9 ⽉ 21 ⽇ 由 Gerard Beekmans 原著 总编辑：Bruce Dubbs Linux From Scratch: 版本 r11.0-36-中⽂翻译版 : 发布于 2021 年 9 ⽉ 21 ⽇ 由 由 Gerard Beekmans 原著和总编辑：Bruce Dubbs 版权所有 © 1999-2021 Gerard Beekmans 版权所有 © 1999-2021, Gerard Beekmans 保留所有权利。 本书依照 Creative Commons License 许可证发布。 从本书中提取的计算机命令依照 MIT License 许可证发布。 Linux® 是Linus Torvalds 的注册商标。 Linux From Scratch - 版本 r11.0-36-中⽂翻译版 ⽬录 序⾔ .................................................................................................................................... viii i. 前⾔ ............................................................................................................................ viii ii. 本书⾯向的读者 ............................................................................................................ viii iii. LFS 的⽬标架构 ............................................................................................................ ix iv. 阅读本书需要的背景知识 ................................................................................................. ix v. LFS 和标准 ..................................................................................................................... x vi. 本书选择软件包的逻辑 .................................................................................................... xi vii. 排版约定 .................................................................................................................... xvi viii. 本书结构 .................................................................................................................
    [Show full text]
  • Jenkins Github Pull Request Integration
    Jenkins Github Pull Request Integration Jay remains out-of-date after Wittie synchronised oftener or hypnotized any tastes. Posticous Guthry augur her geebung so problematically that Anson militarizes very percussively. Long-ago Marvin energise her phenylketonuria so heuristically that Bo marinating very indeed. The six step i to endow the required plugin for integrating GitHub with Jenkins configure it. Once you use these tasks required in code merges or any plans fail, almost any plans fail. Enable Jenkins GitHub plugin service equal to your GitHub repository Click Settings tab Click Integrations services menu option Click. In your environment variables available within a fantastic solution described below to the testing. This means that you have copied the user git log in the repository? Verify each commit the installed repositories has been added on Code Climate. If you can pull comment is github pull integration? GitHub Pull Request Builder This is a different sweet Jenkins plugin that only trigger a lawsuit off of opened pull requests Once jar is configured for a. Insights from ingesting, processing, and analyzing event streams. Can you point ferry to this PR please? Continuous Integration with Bitbucket Server and Jenkins I have. Continuous integration and pull requests are otherwise important concepts for into any development team. The main advantage of finding creative chess problem that github integration plugin repository in use this is also want certain values provided only allows for the years from? It works exactly what a continuous integration server such as Jenkins. Surely somebody done in the original one and it goes on and trigger jenkins server for that you? Pdf deployment are integrated errors, pull request integration they can do not protected with github, will integrate with almost every ci job to.
    [Show full text]
  • Enabling Devops on Premise Or Cloud with Jenkins
    Enabling DevOps on Premise or Cloud with Jenkins Sam Rostam [email protected] Cloud & Enterprise Integration Consultant/Trainer Certified SOA & Cloud Architect Certified Big Data Professional MSc @SFU & PhD Studies – Partial @UBC Topics The Context - Digital Transformation An Agile IT Framework What DevOps bring to Teams? - Disrupting Software Development - Improved Quality, shorten cycles - highly responsive for the business needs What is CI /CD ? Simple Scenario with Jenkins Advanced Jenkins : Plug-ins , APIs & Pipelines Toolchain concept Q/A Digital Transformation – Modernization As stated by a As established enterprises in all industries begin to evolve themselves into the successful Digital Organizations of the future they need to begin with the realization that the road to becoming a Digital Business goes through their IT functions. However, many of these incumbents are saddled with IT that has organizational structures, management models, operational processes, workforces and systems that were built to solve “turn of the century” problems of the past. Many analysts and industry experts have recognized the need for a new model to manage IT in their Businesses and have proposed approaches to understand and manage a hybrid IT environment that includes slower legacy applications and infrastructure in combination with today’s rapidly evolving Digital-first, mobile- first and analytics-enabled applications. http://www.ntti3.com/wp-content/uploads/Agile-IT-v1.3.pdf Digital Transformation requires building an ecosystem • Digital transformation is a strategic approach to IT that treats IT infrastructure and data as a potential product for customers. • Digital transformation requires shifting perspectives and by looking at new ways to use data and data sources and looking at new ways to engage with customers.
    [Show full text]
  • Jenkins Automation.Key
    JENKINS or: How I learned to stop worrying and love automation #MidCamp 2018 – Jeff Geerling Jeff Geerling (geerlingguy) • Drupalist and Acquian • Writer • Automator of things AGENDA 1. Installing Jenkins 2. Configuation and Backup 3. Jenkins and Drupal JENKINS JENKINS • Long, long time ago was 'Hudson' JENKINS • Long, long time ago was 'Hudson' JENKINS • Long, long time ago was 'Hudson' JENKINS • Long, long time ago was 'Hudson' • After Oracle: "Time for a new name!" JENKINS • Long, long time ago was 'Hudson' • After Oracle: "Time for a new name!" • Now under the stewardship of Cloudbees JENKINS • Long, long time ago was 'Hudson' • After Oracle: "Time for a new name!" • Now under the stewardship of Cloudbees • Used to be only name in the open source CI game • Today: GitLab CI, Concourse, Travis CI, CircleCI, CodeShip... RUNNING JENKINS • Server: • RAM (Jenkins is a hungry butler!) • CPU (if jobs need it) • Disk (don't fill the system disk!) RUNNING JENKINS • Monitor RAM, CPU, Disk • Monitor jenkins service if RAM is limited • enforce-jenkins-running.sh INSTALLING JENKINS • Install Java. • Install Jenkins. • Done! Image source: https://medium.com/@ricardoespsanto/jenkins-is-dead-long-live-concourse-ce13f94e4975 INSTALLING JENKINS • Install Java. • Install Jenkins. • Done! Image source: https://medium.com/@ricardoespsanto/jenkins-is-dead-long-live-concourse-ce13f94e4975 (Your Jenkins server, 3 years later) Image source: https://www.albany.edu/news/69224.php INSTALLING JENKINS • Securely: • Java • Jenkins • Nginx • Let's Encrypt INSTALLING
    [Show full text]
  • Project Skeleton for Scientific Software
    Computational Photonics Group Department of Electrical and Computer Engineering Technical University of Munich bertha: Project Skeleton for Scientific Software Michael Riesch , Tien Dat Nguyen , and Christian Jirauschek Department of Electrical and Computer Engineering, Technical University of Munich, Arcisstr. 21, 80333 Munich, Germany [email protected] Received: 10 December 2019 / Accepted: 04 March 2020 / Published: 23 March 2020 * Abstract — Science depends heavily on reliable and easy-to-use software packages, such as mathematical libraries or data analysis tools. Developing such packages requires a lot of effort, which is too often avoided due to the lack of funding or recognition. In order to reduce the efforts required to create sustainable software packages, we present a project skeleton that ensures the best software engineering practices from the start of a project, or serves as reference for existing projects. 1 Introduction In a recent essay in Nature [1], a familiar dilemma in science was addressed. On the one hand, science relies heavily on open-source software packages, such as libraries for mathematical operations, implementations of numerical methods, or data analysis tools. As a consequence, those software packages need to work reliably and should be easy to use. On the other hand, scientific software is notoriously underfunded and the required efforts are achieved as side projects or by the scientists working in their spare time. Indeed, a lot of effort has to be invested beyond the work on the actual implementation – which is typically a formidable challenge on its own. This becomes apparent from literature on software engineering in general (such as the influential “Pragmatic Programmer” [2]), and in scientific contexts in particular (e.g., [3–6]).
    [Show full text]
  • Forcepoint Behavioral Analytics Installation Manual
    Forcepoint Behavioral Analytics Installation Manual Installation Manual | Forcepoint Behavioral Analytics | v3.2 | 23-Aug-2019 Installation Overview This Forcepoint Behavioral Analytics Installation manual guides technical Forcepoint Behavioral Analytics users through a complete installation of a Forcepoint Behavioral Analytics deployment. This guide includes step-by-step instructions for installing Forcepoint Behavioral Analytics via Ansible and Jenkins. This document covers system architecture, required software installation tools, and finally a step-by-step guide for a complete install. The System Architecture section shows how data moves throughout software components, as well as how 3rd party software is used for key front- and back-end functionalities. The Installation Components section elaborates on important pre-installation topics. In preparation for initial installation setup, we discuss high level topics regarding Jenkins and Ansible - the tools Forcepoint Behavioral Analytics utilizes to facilitate installation commands. Although Jenkins is pre-configured at the time of install, we include Jenkins Setup information and important access and directory location information for a holistic understanding of this key installation facilitator. To conclude this document, we include step-by-step instructions for using Ansible to initialize the Jenkins CI/CD server to install each required software component. An addendum is included for additional components which can optionally be installed. Go to the Downloads page and navigate to User and Entity Behavior Analytics to find the downloads for Forcepoint Behavioral Analytics. © 2019 Forcepoint Platform Overview - Component Platform Overview - Physical Installation Components Host OS Forcepoint requires a RedHat 7 host based Operating System for the Forcepoint Behavioral Analytics platform to be installed. CentOS 7 (minimal) is the recommended OS to be used.
    [Show full text]
  • Jenkins Slides Reordered
    Continuous Integration Continuous Integration • What is Continuous Integration? • Why do we need it? • Different phases of adopting Continuous Integration What is Continuous Integration? • Developers commit code to a shared repository on a regular basis. • Version control system is being monitored. When a commit is detected, a build will be triggered automatically. • If the build is not green, developers will be notified immediately. Why do we need Continuous Integration? • Detect problems or bugs, as early as possible, in the development life cycle. • Since the entire code base is integrated, built and tested constantly , the potential bugs and errors are caught earlier in the life cycle which results in better quality software. Different stages of adopting Continuous Integration Stage 1: • No build servers. • Developers commit on a regular basis. • Changes are integrated and tested manually. • Fewer releases. Few commits Stage 2: • Automated builds are Build nightly scheduled on a regular basis. • Build script compiles the application and runs a set of automated tests. • Developers now commit their changes regularly. • Build servers would alert the team members in case of Build and run tests build failure. Stage 3: Triggered • A build is triggered whenever atomically new code is committed to the central repository. • Broken builds are usually treated as a high priority issue and are fixed quickly. Build and run tests Stage 4: Triggered • Automated code quality atomically and code coverage metrics are now run along with unit tests to continuously evaluate the code quality. Is the code coverage increasing? Do we have fewer and fewer Build, run code quality and code build failures? coverage metrics along with tests Stage 5: Triggered • Automated Deployment atomically Production CI/CD Environment _______________________________________________ Continuous Integration Continuous Delivery Continuous Deployment • Continuous Integration The practice of merging development work with the main branch constantly.
    [Show full text]
  • Builder Documentation Release 3.26.0
    Builder Documentation Release 3.26.0 Christian Hergert, et al. Sep 13, 2017 Contents 1 Contents 3 1.1 Installation................................................3 1.1.1 via Flatpak...........................................3 1.1.1.1 Command Line....................................3 1.1.2 Local Flatpak Builds......................................4 1.1.3 via JHBuild...........................................4 1.1.3.1 Command Line....................................4 1.1.4 via Release Tarball.......................................5 1.1.5 Troubleshooting.........................................5 1.2 Exploring the Interface..........................................5 1.2.1 Project Greeter.........................................6 1.2.2 Workbench Window......................................6 1.2.3 Header Bar...........................................7 1.2.4 Switching Perspectives.....................................7 1.2.5 Showing and Hiding Panels...................................7 1.2.6 Build your Project........................................7 1.2.7 Editor..............................................9 1.2.8 Autocompletion......................................... 11 1.2.9 Documentation......................................... 11 1.2.10 Splitting Windows....................................... 12 1.2.11 Searching............................................ 14 1.2.12 Preferences........................................... 15 1.2.13 Command Bar.......................................... 16 1.2.14 Transfers...........................................
    [Show full text]
  • Elinux Status
    Status of Embedded Linux Status of Embedded Linux April 2015 Tim Bird Architecture Group Chair 1 LF CE Workgroup 1 10/23/2014 PA1 Confidential Outline Kernel Versions Technology Areas CE Workgroup Projects Other Stuff Resources 2 2 10/23/2014 PA1 Confidential Outline Kernel Versions Technology Areas CE Workgroup Projects Other Stuff Resources 3 3 10/23/2014 PA1 Confidential Kernel Versions • Linux v3.14 – 30 Mar 2014 – 70 days • Linux v3.15 – 8 Jun 2014 – 70 days • Linux v3.16 – 3 Aug 2014 – 57 days • Linux v3.17 – 5 Oct 2014 – 63 days • Linux v3.18 – 7 Dec 2014 – 63 days • Linux v3.19 – 8 Feb 2015 – 63 day • Linux v4.0-rc7 – (60 days so far) • Linus said probably this weekend or next 4 4 10/23/2014 PA1 Confidential Linux v3.14 • Last long-term stable (LTS) kernel • LTS is at 3.14.37 (as of March 2015) • Will be supported until August of 2016 • Current LTSI is based on 3.14.28 5 10/23/2014 PA1 Confidential Linux v3.16 • Power-aware scheduling • decode_stacktrace.sh • Converts offsets in a stack trace to filenames and line numbers • F2FS large volume support 6 10/23/2014 PA1 Confidential Linux v3.17 • Lots of ARM hardware support • Newly enabled ARM hardware • Rockchip RK3288 SoC • Allwinner A23 SoC • Allwinner A31 Hummingbird • Tegra30 Apalis board support • Gumstix Pepper AM335x • AM437x TI evaluation board • Other ARM boards with existing support also saw improvements with Linux 3.17 • Rework of "config-bisect" mode in ktest 7 10/23/2014 PA1 Confidential Linux v3.18 • OverlayFS introduced • Size reduction patch: • madvise and fadvise
    [Show full text]
  • Jenkins-Autojobs Documentation Release 0.17.4
    jenkins-autojobs documentation Release 0.17.4 Georgi Valkov February 16, 2017 Contents 1 Installing 3 2 Changes 5 2.1 Changelog................................................5 2.2 Tutorial..................................................8 2.3 Case Study: Git.............................................. 18 3 Development 23 3.1 Testing.................................................. 23 3.2 Todo................................................... 23 4 Similar Projects 25 5 License 27 i ii jenkins-autojobs documentation, Release 0.17.4 Jenkins-autojobs is a set of scripts that automatically create Jenkins jobs from template jobs and the branches in an SCM repository. Jenkins-autojobs supports Git, Mercurial and Subversion. A routine run goes through the following steps: • Read settings from a configuration file. • List branches or refs from SCM. • Creates or updates jobs as configured. In its most basic form, the configuration file specifies: • How to access Jenkins and the SCM repository. • Which branches to process and which to ignore. • Which template job to use for which branches. • How new jobs should be named. Autojobs can also: • Add newly created jobs to Jenkins views. • Cleanup jobs for which a branch no longer exists. • Perform text substitutions on all text elements of a job’s config.xml. • Update jobs when their template job is updated. • Set the enabled/disabled state of new jobs. A new job can inherit the state of its template job, but an updated job can keep its most recent state. Please refer to the tutorial and the example output to get started. You may also have a look at the annotated git, svn and hg config files. Notice: The documentation is in the process of being completely rewritten.
    [Show full text]