txels / autojenkins Goto Github PK

Thank you for the cool tool. One feature I'd love is the ability to pass parameters to a job with the "build" method. I end up using other tools because this feature is missing.

Thanks

Requests has a convenient way to parse JSON responses:

http://docs.python-requests.org/en/latest/user/quickstart/#json-response-content

Not only is this easy to use, but it prevents the major security issue of calling eval() on a response from a remote service.

The scripts provided in the distribution get installed with no extension on Windows. I see two possible solutions.

1. Since the project already assumes the presence of setuptools, use console_scripts entry points to invoke the functionality from the project, and let distribute create the appropriate scripts.
2. In the setup script on Windows, rename the scripts with .py extensions.

I prefer the first solution as it is elegant and well-tested. I'll put together a patch.

This can result in a 10x speedup when querying an HTTPS Jenkins server for large numbers of job statuses, by reusing the existing SSL session to avoid renegotiating the key for each request. The code is simple:

class Jenkins(object):
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.session = requests.Session()

    def _http_get(self, url, **kwargs):
        ''' Perform an HTTP GET request.

            This will add required authentication and SSL verification arguments.
        '''
        response = self.session.get(url, auth=self.auth, verify=self.verify_ssl_cert, proxies=self.proxies, **kwargs)
        return _validate(response)

    def _http_post(self, url, **kwargs):
        ''' Perform an HTTP POST request.

            This will add required authentication and SSL verification arguments.
        '''
        response = self.session.post(url, auth=self.auth, verify=self.verify_ssl_cert, proxies=self.proxies, **kwargs)
        return _validate(response)

I was thinking about taking a shot at creating a GUI client for monitoring builds using Tk. Not sure how big of an undertaking that will be, but it would be pretty useful add-on, I think.

I realize this might be a bit silly/trivial for some people, but projects such as this one would probably get more notice if you had installation and setup instructions, as well as contribution guidelines.

http://docopt.org/

Make it saner such as:

autojenkins create <jobname> ...
autojenkins delete <jobname>
...

...or ajk

When you read here:
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API

The problem is when the "Prevent Cross Site Request Forgery exploits" is enabled with a default user
then you need to fetch the token (see link) and passing it to the POST request. For the moment I disabled that on my local Jenkins to try out this library but finally that "feature" would be required.

Hello,

Can i query that info somehow with your great tool?

Thanks

Hi txels, tried to find an address to message you but failed so figured this is the best way to ask. I'd like to use this fine project at work, but IT requires us to know what license all the code we use is distributed under. Is this code released to the public doman, BSD, GPL or something altogether more exotic?

Cheers,

Phil

Sometimes it is useful to synchronously run a build from a script, and perform some action upon completion, depending on success or failure.

This can be implemented by adding a method wait_for_build(poll=10), and adding a switch to the build script, e.g. ajk-build -w