This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description
# Xserverpy

[![Build Status](https://travis-ci.org/oarrabi/xserverpy.svg?branch=master)](https://travis-ci.org/oarrabi/xserverpy) [![Coverage Status](https://coveralls.io/repos/oarrabi/xserverpy/badge.svg?branch=master&service=github)](https://coveralls.io/github/oarrabi/xserverpy?branch=master)
[![PyPI version](https://badge.fury.io/py/xserverpy.svg)](http://badge.fury.io/py/xserverpy)

Xserverpy makes it possible to use Xcode bots from the command line.



![Preview](https://raw.githubusercontent.com/oarrabi/xserverpy/master/assets/preview.gif)

# Use cases
- Running Xcode server tasks, like new integration (ie. Build project) or list bots, without the need to install or run Xcode.
- Build Xcode bots from another CI tool like Jenkins (see [Future milestones and improvements](#future-milestones-and-improvements).
- You love ASCII progress bars (or Nikola Tesla's inventions)

# Installation

## Using brew (recommended)
brew tap oarrabi/tap
brew install xserverpy

## Using pip
pip install xserverpy

# Usage

## Authentication and Host information
All of xserverpy command accept authentication and Xcode server host/port as flags. For example, in order to list all the bots you would run:

xserverpy bots --host HOST --port PORT --user USER --pass PASS

To reduce duplication in calling consequent or future commands, you can run `init` subcommand to store these configuration on your machine.

xserverpy init --host HOST --port PORT --user USER --pass PASS

Now that you stored them, you can call all of xcserverpy subcommands without passing these stored arguments:

xserverpy bots
xserverpy integrations list

xserverpy init flags:

--host HOST Xcode server host
--port PORT Xcode server host port, default 443
--user USER Username to use for authentication
--password PASSWORD Password to use for authentication
--local Store configuration file in the local directory

Note:
- Running `init` sotres a configuration file at `~/.xserverpy`.
- Using `init --local` stores the configuration in the current directory

## Bots
List all bots [Demo](http://showterm.io/1e0d25570e5c65ab57cd0)

xserverpy bots # pass host/user info or load from stored

## Integrations
List integrations per bot [Demo](http://showterm.io/5899725079c80c3026d9d)

xserverpy integrations list --bot <bot name="" or="" id="">
---
Integrate (build project) [Demo](http://showterm.io/bb69e715ba165d147edf5)

xserverpy integrations new --bot <bot name="" or="" id="">
---
Integrate and wait [Demo](http://showterm.io/4b61beb417fe4a5b1ba25)

xserverpy integrations new --bot <bot name="" or="" id=""> --wait
---
Show running integrations [Demo](http://showterm.io/eae3a3cabf806cc9fd84d)

xserverpy integrations running
---
Cancel integrations (build project) [Demo](http://showterm.io/9bbb138149c147ca1c103)

xserverpy integrations cancel --id <integration id="">

## Note on integrate and wait
When using `xserverpy integrations new --wait`, xserverpy keeps polling Xcode server for updates on the running integrations. The default interval is .5s, you can control the behavior and the format of the progress using the following flags:

--interval INTERVAL Interval to poll the server for updates, default .5s
--no-tty Force non tty progress reporting

# Future milestones and improvements
- Create Jenkins plugin to embed Xcode server tasks in Jenkins
- Implement show all pending integrations
- Improve code coverage

# Author
Omar Abdelhafith
[nsomar](http://nsomar.com), [nsomar medium](https://medium.com/@nsomar) [@ifnottrue](https://twitter.com/ifnottrue)

Release History

Release History

0.2.2

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
xserverpy-0.2.2-py2.py3-none-any.whl (14.3 kB) Copy SHA256 Checksum SHA256 py2.py3 Wheel Jul 27, 2015
xserverpy-0.2.2.tar.gz (48.5 kB) Copy SHA256 Checksum SHA256 Source Jul 27, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting