style = intellij

danglingParentheses = false

maxColumn = 120

docstrings = JavaDoc

rewrite.rules = [SortImports]

project.git = true

sudo: required

group: deprecated-2017Q3

language: scala

scala:

- 2.11.8

services:

- docker

before_install:

- "./tools/travis/setup.sh"

install: true

script:

- "./tools/travis/build.sh && ./tools/travis/deploy.sh && ./tools/travis/test.sh"

deploy:

- provider: script

script: "./tools/travis/publish.sh ibmfunctions latest"

on:

branch: master

repo: ibm-functions/runtime-python

- provider: script

script: "./tools/travis/publish.sh ibmfunctions $TRAVIS_TAG"

on:

tags: true

all_branches: true

repo: ibm-functions/runtime-python

WARNING: Work in Progress (WIP) not ready for production

[](https://travis-ci.org/ibm-functions/runtime-python)

The runtime provides [python v3](python3/) with a set of [python packages](python/requirements.txt)

The runtime provides the following npm packages for [IBM Cloud](https://bluemix.net):

- IBM DB2/DashDB and IBM Informix [[email protected]](https://pypi.python.org/pypi/ibm_db)

- IBM Cloudant [[email protected]](https://pypi.python.org/pypi/cloudant)

- IBM Watson Developer Cloud Python SDK [[email protected]](https://pypi.python.org/pypi/watson-developer-cloud)

To use as a docker action

This works on any deployment of Apache OpenWhisk or IBM Cloud Functions

To use as a python kind action

Tip: Not available yet in the IBM Cloud

Prerequisite: *Export* OPENWHISK_HOME to point to your incubator/openwhisk cloned directory.

This will produce the image `whisk/action-python-v3`

Build and Push image

Deploy OpenWhisk using ansible environment that adds the new king `python:3`

Assuming you have OpenWhisk already deploy localy and `OPENWHISK_HOME` pointing to root directory of OpenWhisk core repository.

Set `ROOTDIR` to the root directory of this repository.

Redeploy OpenWhisk

To use as docker action push to your own dockerhub account

Then create the action using your the image from dockerhub

The `$user_prefix` is usually your dockerhub user id.

To run all tests: `./gradlew tests:test` this include tests depending on credentials

To run all tests except those which do not rely on credentials `./gradlew tests:testWithoutCredentials`

To run a single test-class: `./gradlew tests:test --tests <SomeGradleTestFilter>`

[Apache 2.0](LICENSE.txt)

config_root_dir: /tmp/wskconf

- kind: "python-jessie:3"

name: "action-python-v3"

kafka0 ansible_host=172.17.0.1 ansible_connection=local

kafkas

Gradle is used to build OpenWhisk. It does not need to be pre-installed as it installs itself using the [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html). To use it without installing, simply invoke the `gradlew` command at the root of the repository. You can also install `gradle` via [`apt`](http://linuxg.net/how-to-install-gradle-2-1-on-ubuntu-14-10-ubuntu-14-04-ubuntu-12-04-and-derivatives/) on Ubuntu or [`brew`](http://www.brewformulas.org/Gradle) on Mac. In the following we use `gradle` and `gradlew` as synonymous.

In general, project level properties are set via `-P{propertyName}={propertyValue}`. A task is called via `gradle {taskName}` and a subproject task is called via `gradle :path:to:subproject:{taskName}`. To run tasks in parallel, use the `--parallel` flag (**Note:** It's an incubating feature and might break stuff).

To build all Docker images use `gradle distDocker` at the top level project, to build a specific component use `gradle :core:controller:distDocker`.

Project level options that can be used on `distDocker`:

- `dockerImageName` (*required*): The name of the image to build (e.g. whisk/controller)

- `dockerHost` (*optional*): The docker host to run commands on, default behaviour is docker's own `DOCKER_HOST` environment variable

- `dockerRegistry` (*optional*): The registry to push to

- `dockerImageTag` (*optional*, default 'latest'): The tag for the image

- `dockerTimeout` (*optional*, default 240): Timeout for docker operations in seconds

- `dockerRetries` (*optional*, default 3): How many times to retry docker operations

- `dockerBinary` (*optional*, default `docker`): The binary to execute docker commands

To run tests one uses the `test` task. OpenWhisk consolidates tests into a single `tests` project. Hence the command to run all tests is `gradle :tests:test`.

It is possible to run specific tests using [Gradle testfilters](https://docs.gradle.org/current/userguide/java_plugin.html#test_filtering). For example `gradle :tests:test --tests "your.package.name.TestClass.evenMethodName"`. Wildcard `*` may be used anywhere.

In Gradle, most of the tasks we use are default tasks provided by plugins in Gradle. The [`scala` Plugin](https://docs.gradle.org/current/userguide/scala_plugin.html) for example includes tasks, that are needed to build Scala projects. Moreover, Gradle is aware of *Applications*. The [`application` Plugin](https://docs.gradle.org/current/userguide/application_plugin.html) provides tasks that are required to distribute a self-contained application. When `application` and `scala` are used in conjunction, they hook into each other and provide the tasks needed to distribute a Scala application. `distTar` for example compiles the Scala code, creates a jar containing the compiled classes and resources and creates a Tarball including that jar and all of its dependencies (defined in the dependencies section of `build.gradle`). It also creates a start-script which correctly sets the classpath for all those dependencies and starts the app.

In OpenWhisk, we want to distribute our application via Docker images. Hence we wrote a "plugin" that creates the task `distDocker`. That task will build an image from the `Dockerfile` that is located next to the `build.gradle` it is called from, for example Controller's `Dockerfile` and `build.gradle` are both located at `core/controller`.

If you want to create a new `build.gradle` for your component, simply put the `Dockerfile` right next to it and include `docker.gradle` by using

If your component needs to be build before you can build the image, make `distDocker` depend on any task needed to run before it, for example: