-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/12/15 08:00, James wrote: > On Tue, Dec 1, 2015 at 12:52 AM, James <purpleidea at gmail.com> > wrote: >> 3) Most importantly: triggering the builds: best I can come up >> with is putting a git post-update hook in my local repo, and >> `wget` the special: "Trigger builds remotely (e.g., from >> scripts)" url when I want to run it. This actually works, but it >> requires you to actually already be logged in to jenkins, and I >> wasn't sure how to dump in my username and password into a wget >> command. >> > > PS: I hacked this part together with this script: > https://github.com/purpleidea/oh-my-vagrant/blob/master/extras/post-push.git-hook > > It basically logs in with wget and saves a cookie to use for the > subsequent kick. Unfortunately it's all linked up to a "git pushx" > target. If someone knows a better way to kick this off, please LMK. > I don't think I should store the CentOS CI password in the github > hosted hooks! > >> Thanks, James @purpleidea Hi James, Why don't you want to use the "poll SCM" trigger ? that's the most used one, and is transparent on your side. - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZdRj0ACgkQnVkHo1a+xU7srQCfa/w6AFqQOmMwWlE4b83S3bop AX0AnR70sCErZjULw2YCPETGNItNBbBc =NW78 -----END PGP SIGNATURE-----