Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin deletes the jfrog home directory on the controller instead of the agent #35

Open
cfraenkel opened this issue Jul 29, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@cfraenkel
Copy link

Describe the bug

I'm executing jenkins jobs on both ephemeral and persistent nodes.
The plugin creates the encrypted config on the worker node correctly. At the end of the pipeline the plugin does not delete the file on the worker node but on the controller.

Current behavior

The log contains a directory on the controller. This is especially obvious when the controller is running a different OS from the worker node:

17:44:04  [Pipeline] script
17:44:04  [Pipeline] {
17:44:04  [Pipeline] powershell
17:44:05  [Pipeline] jf
17:43:47  [dir] $ cmd.exe /C "C:\JenkinsAgentWorkspace\tools\io.jenkins.plugins.jfrog.JfrogInstallation\jf-2.58.2\jf.exe 

...

17:44:09  
17:44:09  /var/jenkins_home/jobs/misc/jobs/test/jobs/update/workspace/PR-12@tmp/jfrog/4/.jfrog deleted
17:44:09  Finished: FAILURE

Reproduction steps

  • Configure a (persistent) remote worker node in jenkins
  • execute a jf task on that node

Expected behavior

After execution the jfrog home directory in workspace temp folder on the worker node is deleted.

JFrog plugin version

1.5.0

JFrog CLI version

2.58.2

Operating system type and version

Linux controller, windows server 2022 datacenter worker

JFrog Artifactory version

No response

JFrog Xray version

No response

@cfraenkel cfraenkel added the bug Something isn't working label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant