An exception occured when calling build_job after I upgraded jenkinsapi from 0.2.16 to 0.2.19

Jenkins version: 1.558 jenkinsapi version: 0.2.19 When I downgrade jenkinsapi from 0.2.19 to 0.2.16, everything is OK. Exception call stack: javax.servlet.ServletException: java.lang.IllegalStateException: This build is not parameterized! at

Re: An exception occured when calling build_job after I upgraded jenkinsapi from 0.2.16 to 0.2.19

'When I downgrade jenkinsapi from 0.2.19 to 0.2.16, everything is OK.' I mean it works fine after I fixed a bug in jenkinsapi/job.py by adding if action is None: continue to the for action in self._data['actions'] loop in function def get_params(self). 在 2014年4月21日星期一UTC+8下午4时51分30秒，Qifa

Re: New plugin Perforce

Hi Steve, Thanks for your reply, I have added comments below... [Steve RE: Credentials] The new plugin extends Jenkins Credentials into two new types. Perforce Password credential and Perforce Ticket credential; these both support SSL and P4TRUST finger prints. I did look at the password

ConsoleLogFilter data

I need to extend an existing plugin to capture all the job console log. I created a ConsoleLogFilter and it works great, everything appears in the job log as expected, matching before my consolefilter was installed. except one issue. I am saving the output into a ByteArrayOutputStream, 1

Re: A strange behavior on Jenkins - variable is always null.

This field can be null if it is instantiated via deserialization from build.xml. Is this field present in all serialized build.xml files? Am 21.04.2014 um 05:21 schrieb Code ekkapo...@gmail.com: This question is related to How to bind a checkbox on config.jelly with a Builder class?. The

Understanding how Jenkins URLs are mapped to code

Hi Just wondering if anyone can point me at some documentation / examples about how Jenkins URLs are mapped through to code? For instance I've been looking at URLs such as /createItem and /git/notifyCommit but can't seem to figure out how the URL calls are mapped through to know which bits of

Re: A strange behavior on Jenkins - variable is always null.

Yes, it is serialized in the xml file, but it's is config.xml on each job. On Monday, April 21, 2014 9:44:31 PM UTC+7, Ullrich Hafner wrote: This field can be null if it is instantiated via deserialization from build.xml. Is this field present in all serialized build.xml files? Am

Jenkins Failed to dynamically deploy this plugin

I developed a jenkins plugin and gave its version to 1.0.0.0, later I added more feature and updated the version to 1.0.0.1. I packaged it on my machine then tried to upload the hpi file to Jenkins but it failed. This is the error message: java.io.IOException: Failed to dynamically deploy this