>
> That "our local path" thing is not clear to me. What exactly would that
> be? If the file I create is in the root directory of the workspace , would
> that "local path" be empty?
>
Correct. The pathes you specify are relative to the workspace part. To
check just compare the
--
You
On Wed, Sep 22, 2021 at 8:16 AM 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:
>
>
>> I'm not familiar with the archive process. If you could provide me some
>> quick links for information, that would be useful. I'll also ask our
>> internal ops team.
>>
>>
>
>
>
> I'm not familiar with the archive process. If you could provide me some
> quick links for information, that would be useful. I'll also ask our
> internal ops team.
>
>
Archiving is not something special, it's a standard feature.
in a scripted pipeline:
archiveArtifacts artifacts:
On Wed, Sep 22, 2021 at 7:29 AM 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:
>
>
> db...@cloudbees.com schrieb am Mittwoch, 22. September 2021 um 14:54:48
> UTC+2:
>
>> On Mon, Sep 13, 2021 at 5:49 PM Jerome Godbout
>> wrote:
>>
>>> Humm, that would be hard and
db...@cloudbees.com schrieb am Mittwoch, 22. September 2021 um 14:54:48
UTC+2:
> On Mon, Sep 13, 2021 at 5:49 PM Jerome Godbout
> wrote:
>
>> Humm, that would be hard and security unwise. The executing node path
>> aren't available to the web.
>
>
> They are in the case of workspace files
On Mon, Sep 13, 2021 at 5:49 PM Jerome Godbout <
jerome.godbout.amo...@gmail.com> wrote:
> Humm, that would be hard and security unwise. The executing node path
> aren't available to the web.
They are in the case of workspace files (to users with appropriate
permissions).
I think the problem
Humm, that would be hard and security unwise. The executing node path
aren't available to the web. If you are on a secure local network and you
really want to go down that road, you need to
1. mount the slave nodes into the master node local path that would be
accessible by the jenkins
Thanks for the reply, but I think you've misunderstood the problem.
Getting, using, and publishing the filesystem path to the file is not a
problem. What I need to do is create a functional url to that file, which I
can print in the Jenkins build output, which a user can click to get to
that
Some helper I made for my scripted:
Path conversion:
*def ToWindowsPath(path) {*
*return path.replace("/", "\\");*
*}*
*def ToUnixPath(path) {*
*return path.replace("\\","/");*
*}*
*def ToNativePath(path) {*
*if(isUnix()) {*
*return ToUnixPath(path);*
* }*
*return ToWindowsPath(path);*
*}*
Hi,
no, not really. Especially as workspaces typically are reused between jobs
such an URL would be at leas open to surprise. Best practice is to archive
such files (log output, generated files. ) as artifacts to get
persistence.
Björn
davidmic...@gmail.com schrieb am Freitag, 10.
I do notice that my build has a "BUILD_URL" var in the environment, so that
gives me the "prefix" of the url, but the url to the file in the workspace
has pieces like the following after the BUILD_URL value:
"/execution/node/22/ws/". I don't see anything else in the environment that
can help
When a Jenkins build completes, I can navigate to "Workspaces" to manually
inspect files in the workspace. While I'm navigating that tree, and
viewing specific files, I can see that the current browser url goes
directly to that point in the tree, and to the specific file I am viewing.
Is there a
12 matches
Mail list logo
