Search results for jenkins

bastion-product-jenkins-2.457-0.1.lbn36.noarch

Our Subscription Manager utilises X509 certificates to define the product(s) a system is built upon/subscribed to. This is the product for Continous Build Server

chef-handler-jenkins-0.2-1.lbn19.noarch

Track deployment of files through Jenkins

chef-handler-jenkins-0.3-1.lbn25.noarch

Track deployment of files through Jenkins.

BastionLinux/CI/CD manual page

collective.recipe.jenkinsjob-1.0_alpha1-1.lbn19.noarch

Introduction ============ Simple buildout recipe that generated three commands *push a jenkins job*, *pull a jenkins job* and *trigger build on jenkins job*. Recipe enables developer to sync configuration on Jenkins with buildout configuration. Workflow to be used with the recipe: - create and configure a job through the web - run pull jenkins job - later, make more changes the job through the web - run pull jenkins job and use your SCM to diff the config - (optional) push configuration to any other server or use it as restore - (optional) trigger build, because you are too lazy to wait n minutes for cronjob

collective.recipe.jenkinsjob-1.0_alpha1-1.lbn25.noarch

Introduction ============ Simple buildout recipe that generated three commands *push a jenkins job*, *pull a jenkins job* and *trigger build on jenkins job*. Recipe enables developer to sync configuration on Jenkins with buildout configuration. Workflow to be used with the recipe: - create and configure a job through the web - run pull jenkins job - later, make more changes the job through the web - run pull jenkins job and use your SCM to diff the config - (optional) push configuration to any other server or use it as restore - (optional) trigger build, because you are too lazy to wait n minutes for cronjob

collective.xmltestreport-1.3.1-1.lbn13.noarch

This package provides an extension to the test runner to the one that ships with zope.testrunner, as well as a buildout recipe based on zc.recipe.testrunner to install a test script for this test runner. The test runner is identical to the one in zope.testrunner, but it is capable of writing test reports in the XML format output by JUnit/Ant. This allows the test results to be analysed by tools such as the Jenkins continuous integration server. The recipe accepts the same options as zc.recipe.testrunner, so look at its documentation for details. When buildout is run, you should have a script in bin/test and a directory parts/test. To run the tests, use the bin/test script. If you pass the --xml option, test reports will be written to parts/test/testreports directory: $ bin/test --xml -s my.package Use bin/test --help for a full list of options. If you are using Jenkins, you can now configure the build to publish JUnit test reports for <buildoutdir>/parts/test/testreports/*.xml.

collective.xmltestreport-1.3.4-1.lbn19.noarch

This package provides an extension to the test runner to the one that ships with zope.testrunner, as well as a buildout recipe based on zc.recipe.testrunner to install a test script for this test runner. The test runner is identical to the one in zope.testrunner, but it is capable of writing test reports in the XML format output by JUnit/Ant. This allows the test results to be analysed by tools such as the Jenkins continuous integration server. The recipe accepts the same options as zc.recipe.testrunner, so look at its documentation for details. When buildout is run, you should have a script in bin/test and a directory parts/test. To run the tests, use the bin/test script. If you pass the --xml option, test reports will be written to parts/test/testreports directory: $ bin/test --xml -s my.package Use bin/test --help for a full list of options. If you are using Jenkins, you can now configure the build to publish JUnit test reports for <buildoutdir>/parts/test/testreports/*.xml.

collective.xmltestreport-1.3.4-1.lbn25.noarch

This package provides an extension to the test runner to the one that ships with zope.testrunner, as well as a buildout recipe based on zc.recipe.testrunner to install a test script for this test runner. The test runner is identical to the one in zope.testrunner, but it is capable of writing test reports in the XML format output by JUnit/Ant. This allows the test results to be analysed by tools such as the Jenkins continuous integration server. The recipe accepts the same options as zc.recipe.testrunner, so look at its documentation for details. When buildout is run, you should have a script in bin/test and a directory parts/test. To run the tests, use the bin/test script. If you pass the --xml option, test reports will be written to parts/test/testreports directory: $ bin/test --xml -s my.package Use bin/test --help for a full list of options. If you are using Jenkins, you can now configure the build to publish JUnit test reports for <buildoutdir>/parts/test/testreports/*.xml.

docker-swarm-0.4.0-1.lbn19.x86_64

Docker Swarm is native clustering for Docker. It turns a pool of Docker hosts into a single, virtual host. Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Flynn, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself. Like other Docker projects, Swarm follows the "batteries included but removable" principle. It ships with a set of simple scheduling backends out of the box, and as initial development settles, an API will be developed to enable pluggable backends. The goal is to provide a smooth out-of-the-box experience for simple use cases, and allow swapping in more powerful backends, like Mesos, for large scale production deployments.