-
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
-
python-jinja-1.2-4.fc12.x86_64
Jinja is a sandboxed template engine written in pure Python. It
provides a Django-like non-XML syntax and compiles templates into
executable python code. It's basically a combination of Django
templates and python code.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-jinja-1.2-8.fc18.armv6hl
Jinja is a sandboxed template engine written in pure Python. It
provides a Django-like non-XML syntax and compiles templates into
executable python code. It's basically a combination of Django
templates and python code.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-jinja2-2.6-1.lbn13.noarch
Jinja2 is a template engine written in pure Python. It provides a
Django inspired non-XML syntax but supports inline expressions and an
optional sandboxed environment.
If you have any exposure to other text-based template languages, such
as Smarty or Django, you should feel right at home with Jinja2. It's
both designer and developer friendly by sticking to Python's
principles and adding functionality useful for templating
environments.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
python-jinja2-2.6-1.lbn13.noarch
Jinja2 is a template engine written in pure Python. It provides a
Django inspired non-XML syntax but supports inline expressions and an
optional sandboxed environment.
If you have any exposure to other text-based template languages, such
as Smarty or Django, you should feel right at home with Jinja2. It's
both designer and developer friendly by sticking to Python's
principles and adding functionality useful for templating
environments.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-jinja2-2.8-5.lbn19.noarch
Jinja2 is a template engine written in pure Python. It provides a
Django inspired non-XML syntax but supports inline expressions and an
optional sandboxed environment.
If you have any exposure to other text-based template languages, such
as Smarty or Django, you should feel right at home with Jinja2. It's
both designer and developer friendly by sticking to Python's
principles and adding functionality useful for templating
environments.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
python-jira-0.47-1.lbn19.noarch
This library eases the use of the JIRA REST API from Python and it has been used
in production for years.
As this is an open-source project that is community maintained, do not be surprised
if some bugs or features are not implemented quickly enough. You are always welcomed
to use BountySource to motivate others to help.
Quickstart
Feeling impatient? I like your style.
from jira import JIRA
jira = JIRA('https://jira.atlassian.com')
issue = jira.issue('JRA-9')
print issue.fields.project.key # 'JRA'
print issue.fields.issuetype.name # 'New Feature'
print issue.fields.reporter.displayName # 'Mike Cannon-Brookes [Atlassian]'
Located in
LBN
/
…
/
Cloud Computing
/
BastionLinux 19