On Wednesday, June 5, 2013 1:19:39 PM UTC-4, David Weintraub wrote: > On Jun 5, 2013, at 1:05 PM, David Walend <[email protected] <javascript:>> > wrote: > > I'm using the "trigger builds remotely" feature, and don't see the cause > anywhere obvious. > > Where should I see the cause? > > > What do you mean "see the cause"? Are you triggering builds remotely? Is > it building when triggered? Each build has a "Started by" entry on the > build's page. That usually says "Started by SCM change", but I believe says > "Started Remotely" when a remote trigger happens. > > I haven't used remote triggering in a while. It's mainly used when you > have a version control system like CVS where build polling would take too > many resources. Instead, you create a post-commit trigger and use "curl" or > "wget" to request the URL to trigger the build. >
Hi David, That's exactly what I'm doing, via git's post-receive script. Triggering the build is working fine. The URL has a cause field. Where does that go? curl --insecure https://10.0.0.61:8443/jenkins/job/ANCommonViaMaven/build?token=BuildMe&cause="Testing remote build trigger" Thanks, Dave -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
