Thank you, works for me.
BTW, I've (re)opened a request for the documentation:
https://issues.jenkins-ci.org/browse/JENKINS-2983#comment-231262
--
Radek
- Original Message -
From: Radek Holy rh...@redhat.com
To: jenkinsci-users@googlegroups.com
Sent: Thursday, June 25, 2015
I think you don't need public access for that. I trigger my builds via http
from a hook on my git repository server with http auth. The workspace
should be accessable the same way. (not tested)
Max
Am 25.06.2015 11:16 schrieb Vincent Latombe vincent.lato...@gmail.com:
Hi,
you could use the
Either I don't understand you or you didn't understand me.
The job is already triggered by changes in a Git repository. But one of the
steps in the build script is to trigger a build in the external build service.
Then it waits for the results and continues with some additional tests.
--
Thanks, I'll check. Especially I'll check whether it works if the process runs
on a slave.
BTW, is the path documented somewhere? I don't see it in the .../api
resources.
Can you think of any concerns related to the publicly accessible workspace? (In
my case, there are no secrets in the
Hi,
you could use the workspace access through job url/ws/filepath if it is
feasible for you to grant public access to the job workspace.
Vincent
2015-06-24 13:13 GMT+02:00 rh...@redhat.com:
Hello,
is there a documented/supported (!) way how to access files created by the
job in the middle
Hello,
is there a documented/supported (!) way how to access files created by the
job in the middle of the build? As part of the build process, I'd like to
call a build service (Fedora Copr) which requires a publicly available file
which will be generated by the job. Then, I'd like to continue
