Re: Upgrade of Jenkins - is it necessary to upgrade slaves too?
I'm confident the Java web start (JNLP) scenario does not require that you perform any other upgrade steps. I've used that technique for years across many Jenkins versions without ever performing any upgrade on the machine which invokes Java web start. Since the "slave as a Windows service" seems to use JNLP as well, I'm reasonably confident that the upgrade is automatic in that scenario, just as it is automatic in the Java web start scenario. Mark Waite https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29 > > From: Vladimir Zak >To: jenkinsci-users@googlegroups.com >Sent: Saturday, January 5, 2013 12:47 PM >Subject: Re: Upgrade of Jenkins - is it necessary to upgrade slaves too? > >Hi, > >I have already read it but for running slave via Java web start and >then windows service there is no information about that. > >Thank you. > >zakyn > > > > >2013/1/5 Mark Waite : >> It depends how you launch the slave. There is a good description on the >> wiki which can guide you. >> >> See >> https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-Differentwaysofstartingslaveagents >> >> Mark Waite >> >> >> From: zakyn >> To: jenkinsci-users@googlegroups.com >> Sent: Saturday, January 5, 2013 7:14 AM >> Subject: Upgrade of Jenkins - is it necessary to upgrade slaves too? >> >> Hello, >> >> I would like to upgrade my old Jenkins to the LTS Jenkins and I have a slave >> too. Should I anyhow upgrade the slave agent too or not? >> >> Thanks a lot. >> >> Zakyn >> >> > > >
Re: Upgrade of Jenkins - is it necessary to upgrade slaves too?
Hi, I have already read it but for running slave via Java web start and then windows service there is no information about that. Thank you. zakyn 2013/1/5 Mark Waite : > It depends how you launch the slave. There is a good description on the > wiki which can guide you. > > See > https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-Differentwaysofstartingslaveagents > > Mark Waite > > > From: zakyn > To: jenkinsci-users@googlegroups.com > Sent: Saturday, January 5, 2013 7:14 AM > Subject: Upgrade of Jenkins - is it necessary to upgrade slaves too? > > Hello, > > I would like to upgrade my old Jenkins to the LTS Jenkins and I have a slave > too. Should I anyhow upgrade the slave agent too or not? > > Thanks a lot. > > Zakyn > >
Re: Upgrade of Jenkins - is it necessary to upgrade slaves too?
It depends how you launch the slave. There is a good description on the wiki which can guide you. See https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-Differentwaysofstartingslaveagents Mark Waite > > From: zakyn >To: jenkinsci-users@googlegroups.com >Sent: Saturday, January 5, 2013 7:14 AM >Subject: Upgrade of Jenkins - is it necessary to upgrade slaves too? > > >Hello, > >I would like to upgrade my old Jenkins to the LTS Jenkins and I have a slave >too. Should I anyhow upgrade the slave agent too or not? > >Thanks a lot. > >Zakyn > >
Upgrade of Jenkins - is it necessary to upgrade slaves too?
Hello, I would like to upgrade my old Jenkins to the LTS Jenkins and I have a slave too. Should I anyhow upgrade the slave agent too or not? Thanks a lot. Zakyn
Re: publish-over-ssh plugin not transferring files
Quoting iamgen...@gmail.com:
Hi,
I am trying to use publish-over-ssh plugin along with Jenkins on Windows
2008 R2 server. Jenkins plug-in is installed and seems to be configured
correctly. I can see in the verbose output (pasted below) that Jenkins is
able to connect to the remote unix server and is able to run a command but
is not able to transfer any files. It always says 0 files transferred.
Output:
SSH: Connecting from host [ABCDEF]
SSH: Connecting with configuration [AIX DEV] ...
SSH: Creating session: username [aaa], hostname [10.10.10.10], port [22]
SSH: Connecting session ...
SSH: Connected
SSH: Opening SFTP channel ...
SSH: SFTP channel open
SSH: Connecting SFTP channel ...
SSH: Connected
SSH: cd [/home/aaa]
SSH: OK
SSH: Disconnecting configuration [AIX DEV] ...
SSH: Transferred 0 file(s)
Build step 'Send files or execute commands over SSH' changed build result
to SUCCESS
SSH: Connecting from host [ABCDEF]
SSH: Connecting with configuration [AIX DEV] ...
SSH: Creating session: username [aaa], hostname [10.10.10.10], port [22]
SSH: Connecting session ...
SSH: Connected
SSH: Opening SFTP channel ...
SSH: SFTP channel open
SSH: Connecting SFTP channel ...
SSH: Connected
SSH: cd [/home/aaa]
SSH: OK
SSH: Opening exec channel ...
SSH: EXEC: channel open
SSH: EXEC: STDOUT/STDERR from command [echo hello
] ...
SSH: EXEC: connected
hello
SSH: EXEC: completed after 203 ms
SSH: Disconnecting configuration [AIX DEV] ...
SSH: Transferred 0 file(s)
No emails were triggered.
--
Configuration:
Source files: ${web.dir}/war/WEB-INF/lib/*.jar
--
I have looked at the log, trying to see the actual path for the source
files but it doesn't seem to help much. Every time the configured source
file path and actual path comes out to be the same hence doesn't help much
in pin pointing the erorr:
04-Jan-2013 15:04:56 jenkins.plugins.publish_over.BPTransfer getSourceFiles
FINE: Source files: configured [./ui/ProjectName/build.xml/**],
actual [./ui/ProjectName/build.xml/**]
04-Jan-2013 15:04:54 jenkins.plugins.publish_over.BPTransfer getSourceFiles
FINE: Source files: configured [./ui/ProjectName/**], actual
[./ui/ProjectName/**]
--
Can someone please help me identify what is the issue with file transfer?
Thanks,
Prashant
You are not matching any source files, so there is nothing to transfer.
From the console and the log output, the job you are running has 2
transfer sets with the source files set to
"./ui/ProjectName/build.xml/**" for the first and
"./ui/ProjectName/**" for the second.
The reason that there are no files transferred is that either the
following directories do not exist in the workspace or that they
contain no files: "ui/ProjectName/build.xml" and "ui/ProjectName"
If you run the publisher that you say is configured with the Source
files pattern above, then the log entry would look something like the
following: (if web.dir is a jenkins environment variable that expands
to target/web)
FINE: Source files: configured [${web.dir}/war/WEB-INF/lib/*.jar],
actual [target/web/war/WEB-INF/lib/*.jar]
