[JIRA] [core] (JENKINS-21106) hudson.slaves.WorkspaceList setting not working
Massimo Rossello
created JENKINS-21106
hudson.slaves.WorkspaceList setting not working
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
20/Dec/13 12:52 PM
Description:
Our compiler's linker is complaining for the @ in the workspace path that comes with multiple concurrent jobs, so I wish to change the character using -Dhudson.slaves.WorkspaceList=+.
Changed /etc/default/jenkins and restarted the service.
Through ps I can see the property has been used:
/usr/bin/java -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 -Dhudson.slaves.WorkspaceList=+
Tried also with underscore, and surrounding the character with apostrophes ('), but it seems not working. Both on master and on slaves, the parallel workspaces are created using '@'.
Environment:
Jenkins 1.534 on Ubuntu 12.04.1
Project:
Jenkins
Priority:
Major
Reporter:
Massimo Rossello
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [text-finder] (JENKINS-20704) Jenkins Text Finder is waiting for a checkpoint
Massimo Rossello created JENKINS-20704 Jenkins Text Finder is waiting for a checkpoint Issue Type: Bug Assignee: drlewis Components: text-finder Created: 21/Nov/13 4:23 PM Description: When the first of two or more concurrent plugins is slower than the following, the others cannot finish their job and free the line because they remain stuck until the first finishes. On the console of following, faster jobs it is displayed: "Jenkins Text Finder is waiting for a checkpoint" According to https://issues.jenkins-ci.org/browse/JENKINS-9913 it is a bad behavior of the plugin Environment: Jenkins 1.534 Text Finder 1.9 Project: Jenkins Labels: performance job concurrent-build Priority: Major Reporter: Massimo Rossello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [text-finder] (JENKINS-20704) Jenkins Text Finder is waiting for a checkpoint
Massimo Rossello updated JENKINS-20704 Jenkins Text Finder is waiting for a checkpoint Change By: Massimo Rossello (21/Nov/13 4:26 PM) Description: Whenthefirstoftwoormore buildsofa concurrent plugins job isslowerthanthefollowing,theotherscannotfinishtheirjobandfreethelinebecausetheyremainstuckuntilthefirstfinishes.Ontheconsoleoffollowing,fasterjobsitisdisplayed:JenkinsTextFinderiswaitingforacheckpointAccordingtohttps://issues.jenkins-ci.org/browse/JENKINS-9913itisabadbehavioroftheplugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [external-resource-dispatcher] (JENKINS-16538) Resource remains sporadically locked
Massimo Rossello commented on JENKINS-16538 Resource remains sporadically locked I found that simply re-saving unmodified node configuration unlocks the resource (I have IDs defined, if that matters). Then, I have to kill the job which thought to have the resource locked, but didn't proceed further for some reason, otherwise it remains in queue forever This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16538) Resource remains sporadically locked
Massimo Rossello created JENKINS-16538 Resource remains sporadically locked Issue Type: Bug Affects Versions: current Assignee: rsandell Components: external-resource-dispatcher Created: 30/Jan/13 8:08 AM Description: The resource remains sporadically locked in spite of a successful release on log Collecting metadata... Metadata collection done. Releasing previously locked resource: 0019001200190071... Resource 0019001200190071 successfully released. Finished: SUCCESS Possibly the root cause can be the same as JENKINS-16302 Environment: Jenkins 1.478 external-resource-dispatcher 1.0b metadata 1.0b Project: Jenkins Priority: Major Reporter: Massimo Rossello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16302) Resource remains locked after job abort
Massimo Rossello created JENKINS-16302 Resource remains locked after job abort Issue Type: Bug Affects Versions: current Assignee: rsandell Components: external-resource-dispatcher Created: 10/Jan/13 3:18 PM Description: An aborted job does not release its locked resouce even if it reports it does Collecting metadata... Metadata collection done. Releasing previously locked resource: 0019001200190072... Resource 0019001200190072 successfully released. Finished: ABORTED Environment: Jenkins 1.478 external-resource-dispatcher 1.0b metadata 1.0b Project: Jenkins Labels: abort Priority: Major Reporter: Massimo Rossello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave
[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159198#comment-159198 ] Massimo Rossello commented on JENKINS-11926: Solved. I did not notice that some colleague of mine slightly changed the format of the output. Thanks to everybody! Massimo Warnings plugin does not work on a slave Key: JENKINS-11926 URL: https://issues.jenkins-ci.org/browse/JENKINS-11926 Project: Jenkins Issue Type: Bug Components: warnings Affects Versions: current Environment: Tried both with: - a windows master, and a linux slave. Jenkins 1.440 Warnings 3.24 - a linux box (different from the above) acting both as master and slave, Jenkins 1.440, Warnings 3.24 Reporter: Massimo Rossello Assignee: Ulli Hafner Labels: plugin, slave, warnings Attachments: issue11926.txt I create my own parser. If I use the Warning parsing on the master it works as expected. If I make the parsing on the slave it always reports 0 warnings -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave
[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Rossello resolved JENKINS-11926. Resolution: Not A Defect Issue reopening was due to an error in usage Warnings plugin does not work on a slave Key: JENKINS-11926 URL: https://issues.jenkins-ci.org/browse/JENKINS-11926 Project: Jenkins Issue Type: Bug Components: warnings Affects Versions: current Environment: Tried both with: - a windows master, and a linux slave. Jenkins 1.440 Warnings 3.24 - a linux box (different from the above) acting both as master and slave, Jenkins 1.440, Warnings 3.24 Reporter: Massimo Rossello Assignee: Ulli Hafner Labels: plugin, slave, warnings Attachments: issue11926.txt I create my own parser. If I use the Warning parsing on the master it works as expected. If I make the parsing on the slave it always reports 0 warnings -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave
[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159164#comment-159164 ] Massimo Rossello commented on JENKINS-11926: Hi, I confirm that the Windows master (Jenkins 1.450) + Linux slave configuration DOES NOT work with 3.27. I see no progress at all. This problem is coupled (as before) with a strange behavior on the master configuration page. Whenever the example parsed text is over about 250 characters, a match is no more found (even if more text is appended after a previously matched text). Regards Warnings plugin does not work on a slave Key: JENKINS-11926 URL: https://issues.jenkins-ci.org/browse/JENKINS-11926 Project: Jenkins Issue Type: Bug Components: warnings Affects Versions: current Environment: Tried both with: - a windows master, and a linux slave. Jenkins 1.440 Warnings 3.24 - a linux box (different from the above) acting both as master and slave, Jenkins 1.440, Warnings 3.24 Reporter: Massimo Rossello Assignee: Ulli Hafner Labels: plugin, slave, warnings I create my own parser. If I use the Warning parsing on the master it works as expected. If I make the parsing on the slave it always reports 0 warnings -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave
[
https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159164#comment-159164
]
Massimo Rossello edited comment on JENKINS-11926 at 2/16/12 2:05 PM:
-
Hi,
I confirm that the Windows master (Jenkins 1.450) + Linux slave configuration
DOES NOT work with 3.27. I see no progress at all.
This problem is coupled (as before) with a strange behavior on the master
configuration page. Whenever the example parsed text is over about 250
characters, a match is no more found (even if more text is appended after a
previously matched text).
Here is my current output:
{code}
[WARNINGS] Parsing warnings in files 'reports/flexelint.txt' with parser
AzcomLint
[WARNINGS] Parsing 1 files in
/opt/server/jenkins/workspace/customer1_continuous_trunk
[WARNINGS] Successfully parsed file
/opt/server/jenkins/workspace/customer1_continuous_trunk/reports/flexelint.txt
of module with 0 warnings.
[WARNINGS] Computing warning deltas based on reference build #600
{code}
Regards
was (Author: maxrossello):
Hi,
I confirm that the Windows master (Jenkins 1.450) + Linux slave configuration
DOES NOT work with 3.27. I see no progress at all.
This problem is coupled (as before) with a strange behavior on the master
configuration page. Whenever the example parsed text is over about 250
characters, a match is no more found (even if more text is appended after a
previously matched text).
Regards
Warnings plugin does not work on a slave
Key: JENKINS-11926
URL: https://issues.jenkins-ci.org/browse/JENKINS-11926
Project: Jenkins
Issue Type: Bug
Components: warnings
Affects Versions: current
Environment: Tried both with:
- a windows master, and a linux slave. Jenkins 1.440 Warnings 3.24
- a linux box (different from the above) acting both as master and slave,
Jenkins 1.440, Warnings 3.24
Reporter: Massimo Rossello
Assignee: Ulli Hafner
Labels: plugin, slave, warnings
I create my own parser. If I use the Warning parsing on the master it works
as expected. If I make the parsing on the slave it always reports 0 warnings
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave
[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159172#comment-159172 ] Massimo Rossello commented on JENKINS-11926: Ok, I will try to parse your attached file as soon as possible. Thanks Warnings plugin does not work on a slave Key: JENKINS-11926 URL: https://issues.jenkins-ci.org/browse/JENKINS-11926 Project: Jenkins Issue Type: Bug Components: warnings Affects Versions: current Environment: Tried both with: - a windows master, and a linux slave. Jenkins 1.440 Warnings 3.24 - a linux box (different from the above) acting both as master and slave, Jenkins 1.440, Warnings 3.24 Reporter: Massimo Rossello Assignee: Ulli Hafner Labels: plugin, slave, warnings Attachments: issue11926.txt I create my own parser. If I use the Warning parsing on the master it works as expected. If I make the parsing on the slave it always reports 0 warnings -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave
[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159035#comment-159035 ] Massimo Rossello commented on JENKINS-11926: Sorry, on the Linux+Linux configuration it was a mistake of mine. As soon as I'll have access to the system, I check again the Windows+Linux configuration. Thanks Warnings plugin does not work on a slave Key: JENKINS-11926 URL: https://issues.jenkins-ci.org/browse/JENKINS-11926 Project: Jenkins Issue Type: Bug Components: warnings Affects Versions: current Environment: Tried both with: - a windows master, and a linux slave. Jenkins 1.440 Warnings 3.24 - a linux box (different from the above) acting both as master and slave, Jenkins 1.440, Warnings 3.24 Reporter: Massimo Rossello Assignee: Ulli Hafner Labels: plugin, slave, warnings I create my own parser. If I use the Warning parsing on the master it works as expected. If I make the parsing on the slave it always reports 0 warnings -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave
[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Rossello reopened JENKINS-11926: Sorry Ulli, but version 3.27 does not solve the issue to me :( Warnings plugin does not work on a slave Key: JENKINS-11926 URL: https://issues.jenkins-ci.org/browse/JENKINS-11926 Project: Jenkins Issue Type: Bug Components: warnings Affects Versions: current Environment: Tried both with: - a windows master, and a linux slave. Jenkins 1.440 Warnings 3.24 - a linux box (different from the above) acting both as master and slave, Jenkins 1.440, Warnings 3.24 Reporter: Massimo Rossello Assignee: Ulli Hafner Labels: plugin, slave, warnings I create my own parser. If I use the Warning parsing on the master it works as expected. If I make the parsing on the slave it always reports 0 warnings -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
