If you use Python virtualenv, pylint and lxml together, you may see error messages in pylint test results. It`s because only trusted C extension resources (the standard library) should be used. Here is an opportunity to improve the pylint test results.
Generate a .pylintrc file
# generate .pylintrc file
Open the .pylintrc file for edit
# open for edit
Add lxml to extension-pkg-whitelist
# A comma-separated list of package or module names from where C extensions may
# be loaded. Extensions are loading into the active Python interpreter and may
# run arbitrary code
If you now perform the pylint test again, no error relating to lxml should appear.
Taurus from Blazemeter seems really to have a potential to be a star. There are new and easy ways to ease the workflow with JMeter. It allows, for example, configuration options and reports which JMeter does not offer by default.
# install via pip
$sudo pip install bzt
On error look for installed libxml2 and libxslt libraries!
You don`t need jMeter or jMeter PlugIns installed! All will automatically downloaded in given path (see YAML).
You are done with your work and push all into Git. The Build-Server starts his work and all test scripts are failing. Short look and it is clear – certificate errors. The next example shows, how to ignore certificate errors on PhantomJS.
Who the original symbols of Jenkins do not like, should try the Modern Status Plugin. The tiny plugin of Oliver Vinn provide a new and very cool set of icons for the continuous integration server. The installation is very simple!
This is a example of original icons:
Open the Plugin Manager and search for “Modern Status Plugin”.
After restart Jenkins the new iconset should be available and look like: