DOCSLIB.ORG

Jenkins-Autojobs Documentation Release 0.17.4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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. Things may seem incomplete and out of place. Contents 1 jenkins-autojobs documentation, Release 0.17.4 2 Contents CHAPTER 1 Installing The latest stable version of jenkins-autojobs can be installed from pypi using pip. $ pip install jenkins-autojobs Jenkins-autojobs depends on a version of lxml with support for XML canonicalization (c14n). Setup will attempt to install one if it is not present on your system. You might have to install the libxml and libxslt development headers if you haven’t already done so: On a Debian compatible OS: $ apt-get install libxml2-dev libxslt1-dev On a Redhat compatible OS: $ yum install libxml2-devel libxslt-devel On Arch Linux or derivatives: $ pacman -S libxslt libxml2 3 jenkins-autojobs documentation, Release 0.17.4 4 Chapter 1. Installing CHAPTER 2 Changes Changelog 0.17.4 (Mar 03, 2016) • More robust handling of the project description element (see ‘issue 56‘_). • Added the verify-ssl, cert-bundle, and client-cert config-file options and the command-line switches to match them. These control the SSL certificate verification to the Jenkins server. 0.17.3 (Feb 10, 2016) • Fix error-prone handling of the //project/description config.xml element (see issue #54). 0.17.2 (Jan 21, 2016) • Actually change the default tag method to description. This was announced as the default behaviour in 0.17.0, but was accidentally omitted from that release (issue #50). Version 0.17.1 was skipped because of a failed upload to PyPi (see issue #74). 0.17.0 (Oct 19, 2015) • Jenkins-autojobs will now use the job description field to store its metadata. Expect to see (created by jenkins-autojobs) and (jenkins-autojobs-tag: $tagname [...]) lines appended to the description of all managed jobs. This metadata was previously stored as elements in the job’s config.xml. Unfortunately, any manual re- configuration of the job would cause Jenkins to remove these extra elements. This issue is described in greater detail in issue #28. The old behavior can be kept by setting the tag-method option to element. • Added the cleanup-filters configuration option, which filters the list of jobs that jenkins-autojobs con- siders for cleanup by view name or regular expression (thanks @bartoszj). Example usage: # Cleanup only jobs in the 'Feature' and 'Release' views as well as all jobs that start with 'scratch'. cleanup-filters: views: -'Feature' 5 jenkins-autojobs documentation, Release 0.17.4 -'Release' jobs: -'^scratch-. *' • Added the list-closed option to the mercurial plugin, which controls the listing of closed branches. The old behaviour and current default value is true. Note that this feature currently works only for local mercurial repositories. 0.16.2 (Oct 02, 2015) • Fix accidentally introduced import error (thanks @bartoszj). 0.16.1 (Sep 30, 2015) • Fix cleanup functionality and improve performance (thanks @bartoszj). 0.16.0 (Sep 23, 2015) • Add the build-on-create option, which triggers a build when the job is created (thanks @bartoszj). • Ignore permission denied errors during job cleanup (thanks @bartoszj). • Fix issue with listing local mercurial branches (thanks ‘@Myz‘_). 0.15.1 (May 05, 2015) • The repo and repo-orig keys are now available to the namefmt and substitute options. They hold the sanitized and raw value of the repo top-level config key. 0.15.0 (Feb 16, 2015) • The * wildcard can now be used in the branches config key of jenkins-makejobs-svn. Example usage: file:///repo/projects/*/branches. 0.14.3 (Jan 02, 2015) • Fix sticky state when template job is enabled (thanks @d-a-n and @sustmi). 0.14.2 (Nov 24, 2014) • Fix reading of scm-username and scm-password from stdin (thanks @yamikuronue). • Fix user input on Python 3. • Fix typo that was preveneting jenkins-autojobs from working on Python 2.6 (thanks @aklemp). 6 Chapter 2. Changes jenkins-autojobs documentation, Release 0.17.4 0.14.1 (Nov 23, 2014) • Ignore the ‘All’ view when adding jobs to views (thanks ‘@myz‘_). • View creation now respects the dryrun (-n) option (thanks @aklemp). • Fix reporting of view creation (thanks @aklemp). • Fix the httpdebug (-t) option on Python 3. The httpdebug option is now available in the config file. 0.14.0 (Oct 27, 2014) • Learn the ability to add generated jobs to specific views. • Fix compatiblity with newer version of the Jenkins Mercurial plugin (thanks @ThomasMatern). 0.13.1 (May 29, 2014) • Add the tag config option to the subversion script (thanks @mrook). 0.13.0 (Apr 08, 2014) • Add the tag config option. • The cleanup option now accepts a tag name. • The substitute option now has access to matched groups (thanks @traviscosgrave). • The substitute and namefmt options can now refer to named capture groups. For example: refs: -'refs/heads/feature-(\d\d)-(?P<name>\w+)-(\d)': namefmt:'wip-{name}-{3}' The above ref config will map the branch feature-random-10 to job wip-random-10. 0.12.0 (Mar 09, 2014) • Fix a bug that made jenkins-autojobs remove all managed jobs if list_branches() failed with cleanup on (thanks @sja). • Use jenkins-webapi 0.2.0. 0.11.0 (Feb 04, 2014) • Add the cleanup config option (thanks @timmipetit). If set to true, jenkins-autojobs will remove all jobs for which a branch no longer exists. • Jenkins-autojobs now adds a createdByJenkinsAutojobs element to the config.xml of jobs that it creates. 2.1. Changelog 7 jenkins-autojobs documentation, Release 0.17.4 0.10.0 (Jan 08, 2014) • Add the sanitize config option (thanks @xgouchet). You can now substitute characters or whole patterns with the sanitize option: sanitize: '@!?#&|\^_$%*':'_' # replace any of '@!?#&|\^_$%*' with '_' 're:colou?r':'color' # replace regex 'colou?r' with 'color' The default is ’@!?#&|\^_$%*’: ’_’, which is the list of characters that are not allowed in job names. 0.9.1 (Jan 08, 2014) • Command line flags -u|-p properly overwrite username and password config keys (thanks @timmipetit). 0.9.0 (Nov 27, 2013) • Add support for Python 3.x. • Add the ‘python’ option to the mercurial yaml config. This sets the Python executable that will be used to call mercurial. This is useful when the default Python in PATH is not Python 2.x. • Use jenkins-webapi instead of python-jenkins. 0.6.0 (Sep 05, 2012) • Add mercurial support. 0.5.0 (Aug 06, 2012) Initial Release. Tutorial This tutorial goes over the steps of installing and configuring jenkins-autojobs. Installing The latest stable version of jenkins-autojobs can be installed from pypi using pip. $ pip install jenkins-autojobs Jenkins-autojobs depends on a version of lxml with support for XML canonicalization (c14n). Setup will attempt to install one if it is not present on your system. You might have to install the libxml and libxslt development headers if you haven’t already done so: On a Debian compatible OS: $ apt-get install libxml2-dev libxslt1-dev 8 Chapter 2. Changes jenkins-autojobs documentation, Release 0.17.4 On a Redhat compatible OS: $ yum install libxml2-devel libxslt-devel On Arch Linux or derivatives: $ pacman -S libxslt libxml2 Usage If jenkins-autojobs was installed succesfully, you’ll find that there are three new scripts on your system: • jenkins-makejobs-git • jenkins-makejobs-svn • jenkins-makejobs-hg All scripts accept the same command-line options and arguments and nearly the same configuration files. Usage: jenkins-makejobs-* [-rvdtjnyoupUYOP] <config.yaml> General Options: -n dry run -v show version and exit -d debug config inheritance -t debug http requests Repository Options: -r <arg> repository url -y <arg> scm username -o <arg> scm password -Y scm username (read from stdin) -O scm password (read from stdin) Jenkins Options: -j <arg> jenkins url -u <arg> jenkins username -p <arg> jenkins password -U jenkins username (read from stdin) -P jenkins password (read from stdin) Template Jobs Autojobs creates jobs from template jobs. Subsequent changes to the template jobs are propagated to all derived jobs (this behavior is configurable). A template job can be any regular Jenkins job. Depending on the SCM plugin you are using, you have to configure certain fields: Git: * Source Code Management: * Git: * Repository URL: https://your.domain/your-project.git * Branch Specifier: master * Checkout/merge to local branch (under advanced): master Subversion: 2.2.
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]
  • 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]
  • 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]
  • 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 User Success Stories
    Jenkins User Success Stories Education Travel Aerospace Insurance Finance Retail JENKINS IS THE WAY A curated cross-industry collection of Jenkins user stories Welcome. In 2020, we launched JenkinsIsTheWay.io, a global showcase of how developers and engineers build, deploy, and automate great stuff with Jenkins. Jenkins Is The Way is based on your stories. You shared how using Jenkins has helped make your builds faster, your pipelines more secure, and your developers and software engineers happier. In essence, Jenkins has made it a whole lot easier to do the work you do every day. You’ve also shared the amazing stuff you are building: your innovation, your ingenuity, and your keen ability to adapt Jenkins plugins to handle everyday business issues. With this in mind, we share this ebook with you. These half-dozen stories shine a spotlight on how Jenkins users solve unique software development challenges across industries and around the globe. They also illustrate how Jenkins community members build next-generation DevOps and CI/CD platforms, which serve as the backbone for software innovation across companies of all sizes. We applaud the excellent work you do. And we thank you for being part of our community. Best regards, Alyssa Tong Jenkins Events Officer 2020 and Advocacy & Outreach SIG AEROSPACE Jenkins Is The Way to space. SUMMARY A satellite’s onboard computer is one of the core components directly responsible for mission success. It’s necessary to include hardware- "Jenkins allows us based testing in the CI process to catch potential hardware/software to get fast feedback incompatibilities early-on.
    [Show full text]
  • Reproducible Builds Summit II
    Reproducible Builds Summit II December 13-15, 2016. Berlin, Germany Aspiration, 2973 16th Street, Suite 300, San Francisco, CA 94103 Phone: (415) 839-6456 • [email protected] • aspirationtech.org Table of Contents Introduction....................................................................................................................................5 Summary.......................................................................................................................................6 State of the field............................................................................................................................7 Notable outcomes following the first Reproducible Builds Summit..........................................7 Additional progress by the reproducible builds community......................................................7 Current work in progress.........................................................................................................10 Upcoming efforts, now in planning stage................................................................................10 Event overview............................................................................................................................12 Goals.......................................................................................................................................12 Event program........................................................................................................................12 Projects participating
    [Show full text]
  • System Administrator
    System Administrator Emweb is a software engineering company specialized in the development of innovative software. We are located in Herent (Leuven, Belgium) and serve customers all over the world. Emweb's major products are Wt, an open source library for the development of web applications, and Genome Detective, a software platform for microbial High Throughput Sequencing analysis. Our solutions excel in quality and efficiency, and are therefore applied in complex applications and environments. As we continuously grow, we are currently looking for new colleagues with the following profile to join our team in Herent. Your responsibility is to deploy our software in the cloud, maintain our cloud infrastructure, as well as our network and server park in Herent. We are active in multiple applications domains: Web applications Bio-informatics computational biology and molecular epidemiology Your responsibilities are: Operational management of the local network and cloud infrastructure (AWS, OpenStack, private cloud); system administration of our Linux servers, and to lesser extent Windows computers Operational management of cloud software products developed or managed by emweb Release management and configuration management of our software Update and document operational procedures and maintain compliance with security standards Automating operating system updates and configuration changes Monitor performance and maintain systems according to requirements Troubleshoot issues and outages Answering operational technical queries and assisting users Ensuring security, efficiency and continuity of IT infrastructure through access controls, backups and firewalls With the following skills, you are the perfect match to complete our team: Master of Science in Information Technology, Computer sciences or a related discipline, or equivalent by experience Experience as a system administrator, network administrator or similar role.
    [Show 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
    [Show full text]