How to find out plugins depending on Matrix-Auth-Plugin

2021-12-24 Thread Riccardo Foschia 

Hi Jenkins Users,

from the change log of Matrix-Auth-Plugin (see 
https://github.com/jenkinsci/matrix-auth-plugin/blob/master/CHANGELOG.md ):


"If you use any plugins with a dependency on this plugin, make sure 
they're compatible with this release before upgrading."


How do I find those plugins that depend on Matrix-Auth-Plugin?

Thanks in advance,
Riccardo

--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/90c7e68b-2d8f-e487-fb08-95af10a1cacf%40meta-level.de.

Cannot update Jenkins on Debian due to certification problem

2021-10-05 Thread Riccardo Foschia 

Hi all,

I'm trying to update a Jenkins installation on Debian to the current 
version 2.314 using


apt-get update
apt-get install jenkins

but calling apt-get update gives me the following error so apt-get 
install fails also:


Fehl:8 https://pkg.jenkins.io/debian binary/ Release
  server certificate verification failed. CAfile: 
/etc/ssl/certs/ca-certificates.crt CRLfile: none


E: The repository 'https://pkg.jenkins.io/debian binary/ Release' does 
no longer have a Release file.
N: Updating from such a repository can't be done securely, and is 
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user 
configuration details.


The error for me looks like
https://issues.jenkins.io/browse/INFRA-1725
https://issues.jenkins.io/browse/INFRA-2685

Is there currently an issue with SSL certificate for 
https://pkg.jenkins.io? Or is there another problem? What can I do?


Thanks in advance and kind regards,
Riccardo

--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d06ab08a-d78f-2a82-cca4-77312f72b16a%40meta-level.de.

Re: Another CLI question

2017-10-05 Thread Riccardo Foschia 


Am 04.10.2017 um 22:37 schrieb Richard Ginga:

Hi Michael, thanks for the response, nothing in my nginx configuration
indicates any buffering explicitly one way or the other.



Richard, just in case you are using any kind of anti-virus software on 
the machine executing the CLI commands, it's probably an issue with an 
anti-virus software (as in the other thread with CLI issues you didn't 
wan't to hijack ;-) ): try to disable the scanning of HTTP responses in 
your anti-virus software.



You should also try to enable logging in the CLI client like this:

java -jar jenkins-cli.jar -noKeyAuth -s 
https://stt-jenkins.disruptorbeam.com/ -logging FINE connect-node 




On Wed, Oct 4, 2017 at 3:17 PM, Michael Pailloncy <
michael.paillo...@gmail.com> wrote:


If you run this very same command directly on the Jenkins server and
without reaching it through your reverse proxy, does it work ?
I'm wondering if it's not related to the configuration of your reverse
proxy. As described in this documentation
, you
need to ensure that it doesn't buffer request/response bodies when serving
Jenkins through HTTPS.

Hopefully it helps.

2017-10-04 19:01 GMT+02:00 Richard Ginga :


is anybody out there?

my script syntax for this is

cmd = 'java -jar ~/Downloads/jenkins-cli.jar -noKeyAuth -s
https://stt-jenkins.disruptorbeam.com/ -auth
rginga:0793b086e3c9272ddeb0daff1093518c connect-node ' + params.NODENAME
st = sh(returnStatus: true, script: cmd)



On Wed, Oct 4, 2017 at 10:08 AM, Richard Ginga 
wrote:


I see a thread happening on CLI issues. I have a different
question/issue and do not want to hijack that other discussion.

when running any cli in a pipeline script I an getting below but the
command works

*00:04:11.368* + java -jar /Users/jenkins/Downloads/jenkins-cli.jar -noKeyAuth 
-s https://stt-jenkins.disruptorbeam.com/ -auth rginga:xx connect-node 
perf-test-client3

*00:04:28.597* Oct 04, 2017 9:52:34 AM hudson.cli.CLI$5 run*00:04:28.597* 
WARNING: null*00:04:28.597* java.io.IOException: Stream is closed*00:04:28.597* 
  at 
sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3512)*00:04:28.597*
  at 
sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3486)*00:04:28.597*
   at 
java.io.DataOutputStream.writeInt(DataOutputStream.java:197)*00:04:28.597*   at 
hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:175)*00:04:28.597*
 at 
hudson.cli.PlainCLIProtocol$ClientSide.sendEndStdin(PlainCLIProtocol.java:347)*00:04:28.597*
 at hudson.cli.CLI$5.run(CLI.java:679)*00:04:28.597*

--
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com





--
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/ms
gid/jenkinsci-users/CAL3PpaU2vJiaU65icq6vBNwBs%3D7_%3DvG_a4_
tOq_vdVxHbLo4Ug%40mail.gmail.com

.

For more options, visit https://groups.google.com/d/optout.



--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/jenkinsci-users/CAPO77c2yn_VvCtXNbeA9R27E2yNm8xb2_
PTn1UEK-0ocoTHvXw%40mail.gmail.com

.
For more options, visit https://groups.google.com/d/optout.







--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8db26ce9-fe13-c85e-6db6-5ac83724a6a8%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-05 Thread Riccardo Foschia 
After some research we found the problem: it was the anti-virus software 
because it damaged the HTTP responses.  After disabling the HTTP 
scanning feature everything worked fine.


Thanks to all for their help!

Am 04.10.2017 um 13:50 schrieb Riccardo Foschia:

Hi all,

after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http
protocol but it doesn't work (SSH protocol seems to work after the
upgrade).

No matter which CLI command I use, after a few seconds the call returns
but shows no result. E.g.

java -jar jenkins-cli.jar -s http://10.0.3.108 -logger FINE help

called from a Windows command line returns nothing. No errors are
reported. On console I see only the following output:

Okt 04, 2017 1:11:33 PM hudson.cli.CLI _main
FINE: using connection mode HTTP
Okt 04, 2017 1:11:33 PM hudson.cli.CLI plainHttpConnection
FINE: Trying to connect to http://10.0.3.108:8080/ via plain protocol
over HTTP
Okt 04, 2017 1:11:34 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing upload side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established upload side


On Jenkins server (running on Debian) I enabled HTTP access log and I
see the following lines there:

10.0.1.66 - - [04/Okt/2017:13:41:50 +0200] "GET / HTTP/1.1" 200 295675
"-" "Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 6458
"-" "Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 0
"-" "Java/1.8.0_141"

I also tried this with other CLI commands like version or who-am-i and
providing an additional -auth parameter with the right API-Token to the
command line like

java -jar jenkins-cli.jar -s http://10.0.3.108 -auth foschia:
02a781f2a2fe96e8d38dc548ab07912e -logger FINE version

but the result on the command line and the log outputs on client and
server side remain the same.

After reading all available Jenkins documentation and googling around I
really do not know, what to do next.

I would really appreciate any hints.

Thanks in advance,
Riccardo



--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5fa5831a-e837-5b04-ca04-6be94f2b69e5%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Riccardo Foschia 


Am 04.10.2017 um 15:51 schrieb Devin Nusbaum:

Do you see any errors in the logs on the Jenkins server, and is the 
jenkins-cli.jar you are using from your 2.81 instance? You can download a fresh 
jar from http://YOUR_HOST/jenkins/jnlpJars/jenkins-cli.jar. (If you aren’t 
using the /jenkins context path just http://YOUR_HOST/jnlpJars/jenkins-cli.jar).



The jenkins-cli.jar is the one from the 2.81 server instance. I 
downloaded it from the link you mentioned. The MANIFEST.MF of this jar 
says, it's Jenkins-CLI 2.81.


And I do not see exceptions in /var/lib/jenkins/jenkins.log around the 
times I launch the CLI commands.





On Oct 4, 2017, at 7:50 AM, Riccardo Foschia <riccardo.fosc...@meta-level.de> 
wrote:

Hi all,

after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http protocol 
but it doesn't work (SSH protocol seems to work after the upgrade).

No matter which CLI command I use, after a few seconds the call returns but 
shows no result. E.g.

java -jar jenkins-cli.jar -s http://10.0.3.108 -logger FINE help

called from a Windows command line returns nothing. No errors are reported. On 
console I see only the following output:

Okt 04, 2017 1:11:33 PM hudson.cli.CLI _main
FINE: using connection mode HTTP
Okt 04, 2017 1:11:33 PM hudson.cli.CLI plainHttpConnection
FINE: Trying to connect to http://10.0.3.108:8080/ via plain protocol over HTTP
Okt 04, 2017 1:11:34 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing upload side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established upload side


On Jenkins server (running on Debian) I enabled HTTP access log and I see the 
following lines there:

10.0.1.66 - - [04/Okt/2017:13:41:50 +0200] "GET / HTTP/1.1" 200 295675 "-" 
"Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 6458 "-" 
"Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 0 "-" 
"Java/1.8.0_141"

I also tried this with other CLI commands like version or who-am-i and 
providing an additional -auth parameter with the right API-Token to the command 
line like

java -jar jenkins-cli.jar -s http://10.0.3.108 -auth foschia:
02a781f2a2fe96e8d38dc548ab07912e -logger FINE version

but the result on the command line and the log outputs on client and server 
side remain the same.

After reading all available Jenkins documentation and googling around I really 
do not know, what to do next.

I would really appreciate any hints.

Thanks in advance,
Riccardo

--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/47734b97-86aa-3555-e7b0-4fac1cbd26c7%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.




--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8589e9fd-ca8d-7bdb-aebf-bc11c8bf08c7%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Riccardo Foschia 



Am 04.10.2017 um 14:53 schrieb Daniel Beck:



On 4. Oct 2017, at 14:29, Riccardo Foschia <riccardo.fosc...@meta-level.de> 
wrote:

Thanks for your answer, but there is no proxy running.


What security realm are you using?



We are using LDAP and project based matrix authorization (like before 
upgrading).


In the old Jenkins version we used before upgrading to 2.81 we needed to 
authorize user anonymous with common read and connect permissions. These 
user still exists after upgrading to 2.81, see attached screen shot.


--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/eccad6a1-fcd0-10b6-dae3-674dfa03ea46%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Riccardo Foschia 


Am 04.10.2017 um 14:00 schrieb Daniel Beck:



On 4. Oct 2017, at 13:50, Riccardo Foschia <riccardo.fosc...@meta-level.de> 
wrote:

after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http protocol 
but it doesn't work (SSH protocol seems to work after the upgrade).

No matter which CLI command I use, after a few seconds the call returns but 
shows no result. E.g.



If Jenkins is running behind a reverse proxy, make sure the settings are 
correct.

For example for nginx,

proxy_http_version 1.1;
proxy_request_buffering off;



Thanks for your answer, but there is no proxy running.


--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/73022ea1-67f2-4979-852b-ff318b9a29b6%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.

Jenkins CLI with http protocol does not respond in 2.81

2017-10-04 Thread Riccardo Foschia 

Hi all,

after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http 
protocol but it doesn't work (SSH protocol seems to work after the 
upgrade).


No matter which CLI command I use, after a few seconds the call returns 
but shows no result. E.g.


java -jar jenkins-cli.jar -s http://10.0.3.108 -logger FINE help

called from a Windows command line returns nothing. No errors are 
reported. On console I see only the following output:


Okt 04, 2017 1:11:33 PM hudson.cli.CLI _main
FINE: using connection mode HTTP
Okt 04, 2017 1:11:33 PM hudson.cli.CLI plainHttpConnection
FINE: Trying to connect to http://10.0.3.108:8080/ via plain protocol 
over HTTP

Okt 04, 2017 1:11:34 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing upload side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established upload side


On Jenkins server (running on Debian) I enabled HTTP access log and I 
see the following lines there:


10.0.1.66 - - [04/Okt/2017:13:41:50 +0200] "GET / HTTP/1.1" 200 295675 
"-" "Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 6458 
"-" "Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 0 
"-" "Java/1.8.0_141"


I also tried this with other CLI commands like version or who-am-i and 
providing an additional -auth parameter with the right API-Token to the 
command line like


java -jar jenkins-cli.jar -s http://10.0.3.108 -auth foschia:
02a781f2a2fe96e8d38dc548ab07912e -logger FINE version

but the result on the command line and the log outputs on client and 
server side remain the same.


After reading all available Jenkins documentation and googling around I 
really do not know, what to do next.


I would really appreciate any hints.

Thanks in advance,
Riccardo

--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/47734b97-86aa-3555-e7b0-4fac1cbd26c7%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.

Re: How to keep Unix process alive after job is completed?

2013-04-26 Thread Riccardo Foschia 

Hi,

Take a look at 
https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller section 
If your build wants to leave a daemon running behind...


Greetings,
Riccardo

Am 26.04.2013 10:08, schrieb hezjing:

Hi

I have a job which will be run in an Linux slave.

This job will execute a shell command to start a server process which will
run forever. Unfortunately this process is terminated when the job is
finished.

When I tested this using PuTTY, the server process is still alive after I
logged-in and out several times.

May I know how to keep a Unix process alive after the job is completed?




--

META-LEVEL Software AG
Saarbrücker Str. 51
66130 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Ivy 2.3.0 in Ivy Plugin?

2013-02-28 Thread Riccardo Foschia 

Greetings,

does anybody know if there are plans to update Jenkins' Ivy plugin to 
use Ivy 2.3.0?


The reason why I'm asking: we just upgraded our build scripts to use 
Apache Ivy 2.3.0 instead of 2.2.0 version. We also use the newest 
Jenkins Ivy Plugin (1.21) which internally uses Ivy 2.2.0. The last time 
we did such an Ivy upgrade we had problems with our builds on Jenkins 
because the older Ivy version in Jenkins Ivy plugin could not parse ivy 
files containing features from the newer Ivy version.


For now nobody has changed the ivy files and everything seems work on 
Jenkins, but I think it's just a matter of time until someone does a 
change to an ivy file that causes a problem with the older Ivy version 
used in Jenkins Ivy Plugin.


Riccardo

--

META-LEVEL Software AG
Saarbrücker Str. 51
66130 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to pass $jenkins-workspace variable in ant task

2012-08-09 Thread Riccardo Foschia 

Hi,

using enviroment variable WORKSPACE works for me, i.e. in ant do 
something like


property environment=env/
echo message=${env.WORKSPACE}/

Regards,
Riccardo

Am 09.08.2012 13:53, schrieb Kamal Ahmed:



Hi,
I used:

report=${jenkins-workspace}/SoaTestJenkinsReports/report.html


but its being translated as

drwxr-xr-x. 3 jenkins jenkins 4096 Aug  7 10:02 The JENKINS workspace 
location passed from command line.



--

META-LEVEL Software AG
Saarbrücker Str. 51
66130 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn