-
password-reset-jenkins-2.0.4-3.lbn36.noarch
Reset Jenkins UI Admin password
Located in
LBN
/
…
/
CI/CD
/
BastionLinux 36
-
password-reset-jenkins-2.0.4-3.lbn36.noarch
Reset Jenkins UI Admin password
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 36
-
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
-
python-jenkins-0.2.1-1.lbn19.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 19
-
python-jenkins-0.4.13-1.lbn19.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
/
…
/
Plone and Zope
/
BastionLinux 19
-
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-1.3.0-1.lbn19.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 19
-
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
-
python-jenkins-view-builder-0.4.2-1.lbn19.noarch
There are several types of views in jenkins
Build Pipeline View
Nested View
Dashboard
List View
Radiator
jenkins-view-builder as of now supports List View and Build Pipeline View with support for other views coming soon. Examples of yaml files are in the tests/fixtures folder. Views are specified as yaml files and given to the jenkins-view-builder to upload to jenkins. Say, you have the following List View view in a yaml file
- view:
type: list
name: monsanto
description: Merge ply jobs
jobs:
- Merge-nova-Ply
- Merge-config-Ply
- Merge-bark-Ply
columns:
- status
- weather
recurse: False
jenkins-view-builder can create this view in jenkins. jenkins-view-builder needs a jenkins config file which tells it how to connect to jenkins. The config file looks like this
[jenkins]
user=user
password=password
url=http[s]://jenkinsurl
Once that is ready, we are all set to create the view in jenkins using the following command
jenkins-view-builder update --conf path-to-jenkins-config-file path-to-view-yaml-file
There should be feedback on stdout on what the tool is doing. update command is capable of determining if the view already exists and if it does then it just updates it.
It is also possible to test the view to make sure that jenkins-view-builder is creating the correct xml that it would post to jenkins. This can be done using the following command
jenkins-view-builder test path-to-view-yaml-file
Running this command will spit out the generated xml in the out folder of the current working directory. If the output looks good, the update command can be used to upload the view.
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 19
-
python-jenkinsapi-0.2.25-1.lbn19.noarch
This library can help you:
* Query the test-results of a completed build
* Get a objects representing the latest builds of a job
* Search for artefacts by simple criteria
* Block until jobs are complete
* Install artefacts to custom-specified directory structures
* username/password auth support for jenkins instances with auth turned on
* Ability to search for builds by subversion revision
* Ability to add/remove/query Jenkins slaves
* Ability to add/remove/modify Jenkins views
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
