We're using Jenkins (and precisely Cloudbees) for couple years. Well, it works.

Not I have new use case when I would like to allow trigger build remotely (w/o user account in Cloudbees).

Looks like it's impossible (standard token trigger mechanism requires an account in Cloudbees).

The only one way that I see it to set-up instant message integration (e.g. Jabber) and trigger builds in chat. It's nice solution that I would like to have, but ... it doesn't work for me. No errors and no messages (I tried different jabber servers).

Because I have only one such weird user I don't want to install special software (like Jabber/IRC server) and wanna use existing (like Gtalk or similar).

Any thoughts will be welcome.

1

There are 1 answers

4
Jesse Glick On BEST ANSWER

standard token trigger mechanism requires an account in Cloudbees

You can use the Build Token Root plugin to bypass authentication long enough to check the token.

In the long term it would be desirable for Jenkins to let users create non-user principals that would have their own API tokens and SSH keys (but no UI login) and a restricted subset of permissions, so you could freely create a one-off principal for a specific purpose such as triggering builds. The infrastructure for such a feature does not exist today, however.