projects / tools / python-jenkinsapi.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 667243d) | patch
Trigger parameterized builds with token as well
authorRamon van Alteren <ramon@vanalteren.nl>
Mon, 6 Feb 2012 08:29:04 +0000 (09:29 +0100)
committerRamon van Alteren <ramon@vanalteren.nl>
Wed, 8 Feb 2012 14:11:26 +0000 (15:11 +0100)
commit615ba5cca1d341765723e0a9381bfa1474c7ab5a
tree0388c395d8442eb62657193940cd519769406116tree | snapshot
parent667243d82fc1921eefda2612de3639884a284ba0commit | diff
Trigger parameterized builds with token as well

Per request of RBURHUM.
Although the api explaination recommends to use authentification / security to trigger builds and not
use the (deprecated) trigger builds remotely with a security token, apparently people are still using it.
jenkinsapi/job.py diff | blob | history
Domain: SCM / Build;