Search results for jenkins

python-jenkins-0.4.16.dev1-1.lbn25.py37.noarch

Python Jenkins is a library for the remote API of the Jenkins continuous integration server. It is useful for creating and managing jobs as well as build nodes.

python-jenkins-job-builder-2.9.1-1.lbn25.noarch

Jenkins Job Builder takes simple descriptions of Jenkins jobs in YAML format, and uses them to configure Jenkins. You can keep your job descriptions in human readable text format in a version control system to make changes and auditing easier. It also has a flexible template system, so creating many similarly configured jobs is easy.

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.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.

plone.recipe.codeanalysis-1.0rc1-1.lbn25.noarch

Introduction plone.recipe.codeanalysis provides static code analysis for Buildout-based Python projects, including flake8, JSHint, CSS Lint, and other code checks. This buildout recipe creates a script to run the code analysis: bin/code-analysis By default plone.recipe.codeanalysis also creates a git pre-commit hook, in order to run the code analysis automatically before each commit. plone.recipe.codeanalysis comes with a Jenkins integration, that allows to use the same code analysis settings on your local machine as well as on Jenkins. plone.recipe.codeanalysis provides a Jenkins setting that allows to run it on a Jenkins CI server and to process and integrate the output via the Jenkins Violations plugin. Usually you do not want the recipe to create Jenkins output files on your local machine. Therefore it makes sense to enable the Jenkins output only on the CI machine. The Jenkins job itself should run "bin/code-analysis": The Jenkins Violations plugin needs to be configured to read the output files generated by this configuration. pep8 (to read the flake8 output): **/parts/code-analysis/flake8.log csslint: **/parts/code-analysis/csslint.xml jslint (to read the jshint output: **/parts/code-analysis/jshint.xml

python2-collective.xmltestreport-2.0.1-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: $ zope-xmltestrunner --xml -s my.package Use zope-xmltestrunnner --help for a full list of options. If you are using Jenkins, you can now configure the build to publish xUnit test reports for <buildoutdir>/parts/test/testreports/*.xml (or ~/testreports/ if using console script).

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.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.

python3-grafana-dashboard-builder-0.1.0a14-1.lbn25.py37.noarch

grafana-dashboard-builder is an open-source tool for easier creation of Grafana dashboards. It is written in Python and uses YAML descriptors for dashboard templates. This project has been inspired by Jenkins Job Builder that allows users to describe Jenkins jobs with human-readable format. grafana-dashboard-builder aims to provide similar simplicity to Grafana dashboard creation and to give users easy way how they can create dashboard templates filled with different configuration.

python3-collective.xmltestreport-2.0.1-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.