-
jenkins-cli-2.390-1.lbn36.noarch
Jenkins CLI tool (wrapper for jenkins-cli.jar) /usr/bin/jenkins-cli
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 36
-
jenkins-plugin-installation-manager-2.12.11-1.lbn36.noarch
The plugin manager downloads plugins and their dependencies into a folder so that they can
easily be imported into an instance of Jenkins. The goal of this tool is to replace the Docker
install-plugins.sh script and the many other implementations of plugin management that have
been recreated across Jenkins. The tool also allows users to see more information about the
plugins they are downloading such as available updates and security warnings. By default,
plugins will be downloaded; the user can specify not to download plugins using the --no-download
option.
Usage
-----
/usr/bin/jenkins-plugins --help
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 36
-
jenkins-slave-3107.v665000b_51092-1.lbn36.noarch
Slave setup for Jenkins/SSH/Java client. This does the static/software setup that
Jenkins would perform launching a slave node. The global 'Remote working directory'
may be set to /var/lib/jenkins.
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 36
-
python-jenkins-1.5.0-1.lbn25.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.
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 25
-
python-jenkins-job-builder-3.2.0-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.
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 25
-
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
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python3-collective-xmltestreport-2.0.2-1.lbn36.noarch
Introduction 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...
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-apache-airflow-jenkins-2.4.3-2.lbn36.noarch
Apache/Airflow jenkins provider
Located in
LBN
/
…
/
Big Data
/
BastionLinux 36
