Details
-
Bug
-
Status: Fixed but Unreleased (View Workflow)
-
Blocker
-
Resolution: Cannot Reproduce
-
None
-
Redhat 7.4 PPC Big Endian
Description
The build parameters and environment variables not working in Publish over ssh. Previously it worked. Now in this version 1.19.1 , it is not working. The parameter values are null so that no files are copied over.
Attachments
Activity
Also, please highlight the issue in the log so I know exactly what you are trying to show.
Ayappan Perumal
added a comment - Sorry for the late response.
If you see the first image, the "$" variables are put into the Publish over SSH plugin. But they are not getting set inside this plugin because of which no files are copied over. I am attaching the older log.
Ayappan Perumal
added a comment - Sorry for the late response.
If you see the first image, the "$" variables are put into the Publish over SSH plugin. But they are not getting set inside this plugin because of which no files are copied over. I am attaching the older log.
I can't reproduce this. I setup an environment variable in the global config for Jenkins and also setup a parameter for the build. I used both in the remote directory and it worked just fine, the variables were expanded and the correct stuff was done. Is there a specific field that is having issues?
I even tried using variables in the source files text box and that worked fine too.
Ayappan Perumal
added a comment - I tried today also. The issue is still there.
If you see the latest attachment (image) in this Jira, $PKG (and also$REL) is defined as a string parameter in the job.
$COM_VER is defined under the Build step (Execute shell).
I hope you are trying to reproduce this with the latest plugins.
Ayappan Perumal
added a comment - I tried today also. The issue is still there.
If you see the latest attachment (image) in this Jira, $PKG (and also$REL) is defined as a string parameter in the job.
$COM_VER is defined under the Build step (Execute shell).
I hope you are trying to reproduce this with the latest plugins.
Ayappan Perumal
added a comment - Jenkins is actually running on a PPC (PowerPC) 64 bit Big Endian RHEL 7.4 machine.
Ayappan Perumal
added a comment - Jenkins is actually running on a PPC (PowerPC) 64 bit Big Endian RHEL 7.4 machine. Environment variables defined in an execute shell step will not propagate past that step. You would need to use something like EnvInject to get them back to be usable in another build step or post-build step. I don't have any access to a PPC machine, but I don't think running on that type of HW is an issue.
Ayappan Perumal
added a comment - Okay we can leave those variables defined in an execute shell step. But the PKG variable defined under "This project is parameterized" should be passed. But that is not happening here.
Ayappan Perumal
added a comment - Okay we can leave those variables defined in an execute shell step. But the PKG variable defined under "This project is parameterized" should be passed. But that is not happening here. I am not able to reproduce this issue. It works for me locally just fine.
Ayappan Perumal
added a comment - Okay. I will test this in one more machine Ubuntu PPC64 Little Endian and update the status.
Ayappan Perumal
added a comment - Okay. I will test this in one more machine Ubuntu PPC64 Little Endian and update the status. For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues
Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/106
And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-52016%22
(Note: this is an automated bulk comment)
Do you have a log of a previous run that I could compare?