[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159653#comment-159653 ] Bruno P. Kinoshita commented on JENKINS-12810: -- Hi Jaroslavas, We could create a new strategy for this, like JUnitClassNameAndCaseNameResultSeeker. The reason for not changing the two existing ones, is that there are many tools that generate JUnit report, and some of them use only class name, others only case name in the XML (or none sometimes heh). This strategy would match for classname.testname (e.g.: TestClass1.TestCase1). What do you think? JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- 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-12931) Let ClearCase UCM plugin be able to have a different checkout path than view
Christian Wolfgang created JENKINS-12931: Summary: Let ClearCase UCM plugin be able to have a different checkout path than view Key: JENKINS-12931 URL: https://issues.jenkins-ci.org/browse/JENKINS-12931 Project: Jenkins Issue Type: Improvement Components: clearcase-ucm Reporter: Christian Wolfgang Currently the view is checked out to $WORKSPACE/view. It should be possible to alter this destination. This will make it compatible with the multiple-scms plugin! -- 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-12810) JUnit test results are getting wrongly attached to all the test cases
[
https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159654#comment-159654
]
Jaroslavas D. commented on JENKINS-12810:
-
Bruno.
It would be nice to have such strategy too. Thank you!
*How this strategy will be presented in Jenkins?*
# Will it be two fields in Jenkins and TestLink. For example:
#- {{'Test Class': tests.TestClass}}
#- {{'Test Method': TestMethod}}
# or it will be one field. For example:
#- {{'Test Class with Method': tests.TestClass.TestMethod}}
JUnit test results are getting wrongly attached to all the test cases
-
Key: JENKINS-12810
URL: https://issues.jenkins-ci.org/browse/JENKINS-12810
Project: Jenkins
Issue Type: Bug
Components: testlink
Affects Versions: current
Reporter: Vignesh Senapathy
Assignee: Bruno P. Kinoshita
Fix For: current
Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png,
screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png
Hi,
I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the
Junit Test results are getting generated. This in turn calls the Testlink xml
rpc and attaches the results to the test case, but the test results are
attached wrongly. The 1st test case has 6 results, the next has 5 and so on
and the last one has 1 test result attached to it. I dont know if it is bug
which is causing this. Please let me know what seems to be the problems. Also
the execution flags are correctly rendered in this. which ever test case
fails is marked as failed and which passed is marked as passed.
Also I have one custom field which maps to the test suite name and test
classname.
--
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-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159655#comment-159655 ] Bruno P. Kinoshita commented on JENKINS-12810: -- Hi Jaroslavas, Never mention it, thank you for helping to improve the plug-in with good ideas :) More likely to be like option #2. At moment, there is no easy way to implement the option #1. I'll have a working version ready for tests today or tomorrow. JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- 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
Sealer Printer Order
Hello Customer, Greetings to you,well I would like to know whether you sell *Sealer Printer*.Let me know the models,sizes and prices of them.Also I would like to know whether you accept credit card payment.Hope to hear back from you soon. Best Regards, Bill Morgan
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159656#comment-159656
]
Bruno P. Kinoshita commented on JENKINS-12916:
--
Hi Nikolay
Actually, you'll have a strategy with data providers soon. See [1] ;-)
Is it possible to map just test-methods names to the testlink methods(by for
ex. java class, test-method pair, without using dataprovider) ?
Not with the latest release. But it is being tested by some users in an alpha
version. Would you like to give it a try too? This version is 3.1-alpha. I can
attach the hpi package here today or tomorrow. I'm finishing to fix some tests.
Cheers
[1] https://github.com/cbeust/testng/issues/181#issuecomment-4232884
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
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-11074) LOADING Overlay does not go away - IE 8
[ https://issues.jenkins-ci.org/browse/JENKINS-11074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159657#comment-159657 ] A Serrano commented on JENKINS-11074: - Same issue here. Can't access the global configuration from any browser, Opera, FF, Chrome, IE9 Jenkins ver. 1.452 LOADING Overlay does not go away - IE 8 --- Key: JENKINS-11074 URL: https://issues.jenkins-ci.org/browse/JENKINS-11074 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: IE 8 - Windows Reporter: josh kehoe Attachments: source.htm Using IE 8, the LOADING overlay does not go away on the job configure page. Per issue #6542, I am opening a new defect and attaching page source. The JS error is: Webpage error details User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.2; MS-RTC LM 8; .NET4.0C; .NET4.0E) Timestamp: Wed, 21 Sep 2011 13:55:25 UTC Message: Object required Line: 860 Char: 33 Code: 0 URI: http://jenkins/static/89477826/scripts/hudson-behavior.js Thank you! -- 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-9117) Jenkins hangs in the shutdown mode after thinBackup is triggered
[ https://issues.jenkins-ci.org/browse/JENKINS-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159658#comment-159658 ] Ralitsa Chipeva commented on JENKINS-9117: -- Hi all, actually we also face the same problem with our Jenkins instance. The version of the plugin we use is 1.4 also. This is strange, as I think that when I read about the plugin I understood it does not shut down the Jenkins instance, right? Regards, Ralitsa Jenkins hangs in the shutdown mode after thinBackup is triggered Key: JENKINS-9117 URL: https://issues.jenkins-ci.org/browse/JENKINS-9117 Project: Jenkins Issue Type: Bug Components: thinBackup Reporter: Thomas Fürer Assignee: Thomas Fürer thinBackup triggers a backup job and did not return from the shutdown mode -- 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-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159659#comment-159659 ] Bruno P. Kinoshita commented on JENKINS-12810: -- @Jaroslavas, @Vignesh: I have just attached a new alpha version of the plug-in here, could you give it a try, please? The file name is testlink-3.1-alpha2.hpi Thank you in advance! JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- 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-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno P. Kinoshita updated JENKINS-12916:
-
Attachment: testlink-3.1-alpha2.hpi
TestLink Plug-in 3.1 alpha #2
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
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-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159665#comment-159665 ] Jaroslavas D. commented on JENKINS-12810: - h3.What I have already found: # (/) it is possible now to define multiple fields in 'Custom Fields' # (!) help text problem remains Till now I haven't found any problem in new version, however, I will try some more cases tomorrow. New plugin version works fine for me. *Thank You a lot for your work!* JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png, testlink-3.1-alpha2.hpi Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- 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-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159667#comment-159667
]
Nikolay Myakushkin commented on JENKINS-12916:
--
Thank you, Bruno
This is great news.
Best Regards,
Nick
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
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-12862) CVS confused about what to checkout and where to checkout to
[ https://issues.jenkins-ci.org/browse/JENKINS-12862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159668#comment-159668 ] Kelly Hickel commented on JENKINS-12862: I also seem to be having this issue, simple jobs that listed multiple CVS module names for the checkout are now checking out the entire repo for the first module. Oddly enough the other modules seem to be correct. as a result, I believe all of our Jenkins jobs are now broken, with no workaround that I know of. kind of a problem, that.. CVS confused about what to checkout and where to checkout to Key: JENKINS-12862 URL: https://issues.jenkins-ci.org/browse/JENKINS-12862 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Reporter: nhnb Priority: Critical The recent CVS plugin is confused about what to checkout and where: CVSROOT: :pserver:anonym...@arianne.cvs.sourceforge.net:/cvsroot/arianne Remote Name: stendhal This configuration used to work in the past. But now it does a checkout of every module in the CVS-repository and it places this checkout above the workspace folder. As a result, the CVS changes are invisible because the last checkout below the workspace folder remains unchanged. Using different configurations of the Localname (empty or non empty) and Legacy Mode checkbox may result in only the right module to be checked out, but not into the workspace folder but a subfolder with the module name below the workspace folder. Again, this will result in the checkout being mostly invisible because an outdated version remains at the correct location. Furthermore deselecting the legacy mode checkbox is ignored. After saving the form and reopening the configuration form, the checkbox is selected again. It is possible to deselect it directly in config.xml, but this just causes the CVS plugin to again do a checkout of all modules to the parent folder of workspace. I tried several combinations of the configuration settings but I am still unable to find a workaround for this issue. Out jenkins server is publically available at http://stendhalgame.org/jenkins/job/stendhal_HEAD -- 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-12581) CVS: First CVS Update after Checkout reads whole CVS-Repository
[ https://issues.jenkins-ci.org/browse/JENKINS-12581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159669#comment-159669 ] Kelly Hickel commented on JENKINS-12581: I'm thinking that issue JENKINS-12862 is also related to this. Either way, my jenkins server is now busted. CVS: First CVS Update after Checkout reads whole CVS-Repository --- Key: JENKINS-12581 URL: https://issues.jenkins-ci.org/browse/JENKINS-12581 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Tomcat6 / RHEL5 Reporter: chrisabit Assignee: Michael Clarke Priority: Blocker When migration from old CVS-Plugin to the new Jenkins CVS-Plugin Local Name isn't defined. This leads to a HUGE problem: The first CVS-Update (not the first CVS-Checkout! This works!) will execute: cvs update -d -P -r HEAD -D 2012-01-30 16:37:56CE Thus the whole CVS repository is read. Simple solution: When migrating: Remote Name and Local Name must both be set. -- 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-11337) Git plugin only triggers a build for one branch
[ https://issues.jenkins-ci.org/browse/JENKINS-11337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159671#comment-159671 ] Andreas Pakulat commented on JENKINS-11337: --- No I think you misunderstood our description. The Git plugin used to work like this: 1. Look at all branches and note down which have changed 2. Kick off a new build for each branch that has changed So if I have 5 branches and 3 changed I'd get 3 new builds in the job, one for each branch. Git plugin only triggers a build for one branch --- Key: JENKINS-11337 URL: https://issues.jenkins-ci.org/browse/JENKINS-11337 Project: Jenkins Issue Type: Bug Components: git Affects Versions: current Reporter: Andreas Pakulat Assignee: abayer Priority: Critical I've just downloaded Jenkins 1.434 to see wether the last comment in #JENKINS-7554 from Christian Weiske is true that the newest git plugin solves the problems with the GIT_BRANCH/GIT_COMMIT envvars and setting the build up to build multiple branches. Unfortunately it turns out that the plugin does not support building multiple branches anymore at all. No matter wether I leave the branch field empty or add multiple branches to the build configuration it always only builds master. Tried with a totally fresh job so all branches need to be considered 'updated' and polling as well as manual building. -- 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-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159675#comment-159675 ] Bruno P. Kinoshita commented on JENKINS-12810: -- Thanks for the feedback Vignesh! I'm trying to find some time to review all the HTML help files, log messages and the test summary notes :-) Thank you for the work! This will help me a lot. Thank you too! This alpha testing helps a lot! When is the official release? It was planned for March 1st, but due to some bug fixing in this alpha version, and the HTML help files changed after the refactoring, I will postpone it for next week's Wednesday (but it may happen before that ;) Cheers, B JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png, testlink-3.1-alpha2.hpi Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- 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-12936) EnvInject Plugin 1.30 does not display all properties on job config page
mwebber created JENKINS-12936:
-
Summary: EnvInject Plugin 1.30 does not display all properties on
job config page
Key: JENKINS-12936
URL: https://issues.jenkins-ci.org/browse/JENKINS-12936
Project: Jenkins
Issue Type: Bug
Components: envinject
Reporter: mwebber
Assignee: gbois
I upgraded from EnvInject Plugin 1.28 to 1.30. The result was that, for some
jobs, variables I have previously defined are not displayed on the job
configuration page.
This is where I have selected Inject environment variables to the build
process, and have entries in the Properties Content box. Even though the
entries are on teh job config file, they are not always displayed in the
Properties Content box.
When the config.xml looks like this, the Properties Content box IS correctly
populated:
{noformat}
EnvInjectBuildWrapper
info
propertiesContentbranchTagPath=v0.9/propertiesContent
loadFilesFromMasterfalse/loadFilesFromMaster
/info
/EnvInjectBuildWrapper
{noformat}
When the config.xml looks like this, the Properties Content box s incorrectly
displays EMPTY:
{noformat}
EnvInjectBuildWrapper
info
propertiesContentMap class=linked-hash-map
entry
stringmaterialize_component/string
stringsda/string
/entry
entry
stringmaterialize_category/string
stringsda/string
/entry
entry
stringmaterialize_version/string
stringv0.9/string
/entry
entry
stringmaterialize_workspace_path/string
string${WORKSPACE}/materialize_workspace/string
/entry
/propertiesContentMap
loadFilesFromMasterfalse/loadFilesFromMaster
/info
/EnvInjectBuildWrapper
{noformat}
--
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-6647) Add ability to allocate range of TCP Ports
[ https://issues.jenkins-ci.org/browse/JENKINS-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159676#comment-159676 ] Richard Mortimer commented on JENKINS-6647: --- I need a similar feature to allow me to fix JENKINS-12821. That needs consecutive ports but it would be easy to provide an option to do both. I plan to start working on this in the next day or two. Add ability to allocate range of TCP Ports -- Key: JENKINS-6647 URL: https://issues.jenkins-ci.org/browse/JENKINS-6647 Project: Jenkins Issue Type: Improvement Components: port-allocator Affects Versions: current Reporter: Eric Smalling Assignee: ramapulavarthi It would be nice to be able to ask for a range of ports (not necessarily contiguous, but that could be a useful option I suppose) given a name, the variables would be allocated with a counter suffix. For instance, I'm thinking of two fields being presented: Name and Count. If the user eneted, Foo, and 10, then Foo1, Foo2, Foo3 ... Foo10 would all be allocated. -- 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-6647) Add ability to allocate range of TCP Ports
[ https://issues.jenkins-ci.org/browse/JENKINS-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Mortimer reassigned JENKINS-6647: - Assignee: Richard Mortimer (was: ramapulavarthi) Add ability to allocate range of TCP Ports -- Key: JENKINS-6647 URL: https://issues.jenkins-ci.org/browse/JENKINS-6647 Project: Jenkins Issue Type: Improvement Components: port-allocator Affects Versions: current Reporter: Eric Smalling Assignee: Richard Mortimer It would be nice to be able to ask for a range of ports (not necessarily contiguous, but that could be a useful option I suppose) given a name, the variables would be allocated with a counter suffix. For instance, I'm thinking of two fields being presented: Name and Count. If the user eneted, Foo, and 10, then Foo1, Foo2, Foo3 ... Foo10 would all be allocated. -- 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-12938) MavenReporters always run, even if unneeded: MavenFingerprinter is slow
James Atwill created JENKINS-12938: -- Summary: MavenReporters always run, even if unneeded: MavenFingerprinter is slow Key: JENKINS-12938 URL: https://issues.jenkins-ci.org/browse/JENKINS-12938 Project: Jenkins Issue Type: Bug Components: maven Environment: Linux, separate master/slave. Slave launched via SSH. Multi-minute, multi-module maven build. Reporter: James Atwill The MavenFingerprinter MavenReporter should not run if fingerprinting the build is disabled. --- Yesterday I attached YourKit to our Jenkins Maven-style build. I was attached to the actual Maven3 builder and discovered that 36% of our build time is spent in MavenReporters we don't use. We don't have fingerprinting turned on but the MavenFingerprinter report still runs and was particularly expensive. --- I rebuilt the maven-plugin removing the @Extension from MavenArtifactArchiver, MavenFingerprinter and MavenMailer and improved our build time by 36%. -- 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-12939) Be able to blacklist extensions in ClassicPluginStrategy
James Atwill created JENKINS-12939: -- Summary: Be able to blacklist extensions in ClassicPluginStrategy Key: JENKINS-12939 URL: https://issues.jenkins-ci.org/browse/JENKINS-12939 Project: Jenkins Issue Type: New Feature Components: plugin Reporter: James Atwill Priority: Minor Sometimes there are @Extensions which are part of a plugin that we simply don't want to run but due to limitations with the plugin / plugin configuration / etc we have no way of disabling. The MavenFingerprinter extension (see JENKINS-12938) is the specific use case. It would be handy to be able to blacklist an @Extension either as a System property or from Manage Jenkins Manage Plugins. The alternative is removing the @Extension from the bytecode in .hpi archives, which isn't nearly as fun on a production server as you'd think it would be. :-) -- 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-11628) Jenkins is no longer updating JIRA tickets
[ https://issues.jenkins-ci.org/browse/JENKINS-11628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159678#comment-159678 ] Peter Callies commented on JENKINS-11628: - I'm seeing the same thing. In the JIRA SOAP dump, I see jenkins connect, I see Jenkins request the issue and JIRA responds, but then I don't see jenkins even attempt to add a comment to the issue. Jenkins 1.444 JIRA Pluging 1.29 JIRA: 5.0 Jenkins is no longer updating JIRA tickets -- Key: JENKINS-11628 URL: https://issues.jenkins-ci.org/browse/JENKINS-11628 Project: Jenkins Issue Type: Bug Components: jira Affects Versions: current Reporter: Andrew Knapp Ever since we upgraded Jenkins to 1.435 (I think), the JIRA plugin has been broken. No other changes have been made, but the plugin is not updating the corresponding issues in JIRA. I see our JIRA user making soap calls in our JIRA logs (I turned on the soap dump logs), but it's not actually updating the tickets. Any ideas? Let me know if you need more information about our setup or whatnot. JIRA Plugin version: 1.29 Jenkins version: 1.437 -- 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-12928) Job name Enforcer
[ https://issues.jenkins-ci.org/browse/JENKINS-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159679#comment-159679 ] domi commented on JENKINS-12928: I have this pretty much implemented, just need to clean things up a bit more... There will be a new extension point which allows you to not only reject job names, but also to transform these in to a new name. The thing is, that will also have to add this check to a job update - because a rename of the job must be controlled too. I will provide two implementation of this new extension: - default: does nothing, same as today - regex: does exactly what you have provided in your code I'll get back to you as soon as I'm further. Job name Enforcer - Key: JENKINS-12928 URL: https://issues.jenkins-ci.org/browse/JENKINS-12928 Project: Jenkins Issue Type: New Feature Components: core Reporter: Daniel Petisme Fix For: current The aim of this feature is to be able to add constraints on job's name. For instance a simple use case is to be sure the jobs created follow a naming convention. This feature comes from the following thread in the jenkins-developer ML. [https://groups.google.com/forum/?hl=fr#!topic/jenkinsci-dev/rsxUpaNAe18] -- 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-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159680#comment-159680 ] Bruno P. Kinoshita commented on JENKINS-12810: -- Hi Jaroslavas, sorry, I marked the JIRA e-mail with your comment in my inbox, but forgot to comment here. help text problem remains Will review it in the next days. I'm working on another issue related to Maven projects (must be easy to fix). Then I'll start packaging the final release, fixing all the messages, texts, and add notes for i18n. Thank You a lot for your work! Thank you too, for your time testing the alpha version. It helps me a lot, and prevents many bugs of passing to other users. You guys are the quality net of the plug-in :-) Cheers, B JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png, testlink-3.1-alpha2.hpi Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- 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-12940) Jenkins Configure Job -view gets stuck with LOADING
[ https://issues.jenkins-ci.org/browse/JENKINS-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jani Simomaa updated JENKINS-12940: --- Description: Hey! Jenkins version on both machines are latest 1.452 I'm having an issue with my own created plugin. It works fine if it is used locally on my Windows master but when I try to upload this plugin to Ubuntu master Jenkins the plugin and the Jenkins configure Job -view stuck with LOADING text and gray background. I also get a huge stack trace into Jenkins log but I'm not able to figure it out why it doesn't work. Stack trace here: http://pastebin.com/T5JwJErq I'll attach the source of my plugin. Thanks! was: Hey! I'm having an issue with my own created plugin. It works fine if it is used locally on my Windows master but when I try to upload this plugin to Ubuntu master Jenkins the plugin and the Jenkins configure Job -view stuck with LOADING text and gray background. I also get a huge stack trace into Jenkins log but I'm not able to figure it out why it doesn't work. Stack trace here: http://pastebin.com/T5JwJErq I'll attach the source of my plugin. Thanks! Jenkins Configure Job -view gets stuck with LOADING --- Key: JENKINS-12940 URL: https://issues.jenkins-ci.org/browse/JENKINS-12940 Project: Jenkins Issue Type: Bug Components: plugin Environment: OS Name: Microsoft® Windows VistaT Home Premium OS Version:6.0.6002 Service Pack 2 Build 6002 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free System Type: X86-based PC Processor(s): 1 Processor(s) Installed. [01]: x64 Family 16 Model 2 Stepping 3 AuthenticAMD ~1200 Mhz BIOS Version: American Megatrends Inc. 0906 , 25.12.2008 Reporter: Jani Simomaa Priority: Blocker Labels: jenkins, plugin Attachments: RetryBuild_source.zip Hey! Jenkins version on both machines are latest 1.452 I'm having an issue with my own created plugin. It works fine if it is used locally on my Windows master but when I try to upload this plugin to Ubuntu master Jenkins the plugin and the Jenkins configure Job -view stuck with LOADING text and gray background. I also get a huge stack trace into Jenkins log but I'm not able to figure it out why it doesn't work. Stack trace here: http://pastebin.com/T5JwJErq I'll attach the source of my plugin. Thanks! -- 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-12936) EnvInject Plugin 1.30 does not display all properties on job config page
[
https://issues.jenkins-ci.org/browse/JENKINS-12936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois resolved JENKINS-12936.
-
Resolution: Fixed
It was a bug display.
Properties were correctly injected.
Anyway, fix in 1.31
EnvInject Plugin 1.30 does not display all properties on job config page
Key: JENKINS-12936
URL: https://issues.jenkins-ci.org/browse/JENKINS-12936
Project: Jenkins
Issue Type: Bug
Components: envinject
Reporter: mwebber
Assignee: gbois
I upgraded from EnvInject Plugin 1.28 to 1.30. The result was that, for some
jobs, variables I have previously defined are not displayed on the job
configuration page.
This is where I have selected Inject environment variables to the build
process, and have entries in the Properties Content box. Even though the
entries are on teh job config file, they are not always displayed in the
Properties Content box.
When the config.xml looks like this, the Properties Content box IS
correctly populated:
{noformat}
EnvInjectBuildWrapper
info
propertiesContentbranchTagPath=v0.9/propertiesContent
loadFilesFromMasterfalse/loadFilesFromMaster
/info
/EnvInjectBuildWrapper
{noformat}
When the config.xml looks like this, the Properties Content box s
incorrectly displays EMPTY:
{noformat}
EnvInjectBuildWrapper
info
propertiesContentMap class=linked-hash-map
entry
stringmaterialize_component/string
stringsda/string
/entry
entry
stringmaterialize_category/string
stringsda/string
/entry
entry
stringmaterialize_version/string
stringv0.9/string
/entry
entry
stringmaterialize_workspace_path/string
string${WORKSPACE}/materialize_workspace/string
/entry
/propertiesContentMap
loadFilesFromMasterfalse/loadFilesFromMaster
/info
/EnvInjectBuildWrapper
{noformat}
--
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-12940) Jenkins Configure Job -view gets stuck with LOADING
[
https://issues.jenkins-ci.org/browse/JENKINS-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159683#comment-159683
]
Richard Mortimer commented on JENKINS-12940:
This isn't really the place to ask questions. Its best to ask thinks like this
on the mailing lists or in #jenkins on IRC.
However you have mixed cases in your package names. Windows lets you get away
with this because filenames are not case sensitive. On linux they are so your
mistake causes the error.
{code}
Caused by: java.lang.NoClassDefFoundError:
Lcom/jsimomaa/jenkins/plugin/RetryBuild/RetryBuildListener;
{code}
That has RetryBuild in capitals but the source uses lower case in the folder
name.
A quick look at the source and I suspect that you need to replace
{code}
package com.jsimomaa.jenkins.plugin.RetryBuild;
{code}
with
{code}
package com.jsimomaa.jenkins.plugin.retrybuild;
{code}
Jenkins Configure Job -view gets stuck with LOADING
---
Key: JENKINS-12940
URL: https://issues.jenkins-ci.org/browse/JENKINS-12940
Project: Jenkins
Issue Type: Bug
Components: plugin
Environment: OS Name: Microsoft® Windows VistaT
Home Premium
OS Version:6.0.6002 Service Pack 2 Build 6002
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
System Type: X86-based PC
Processor(s): 1 Processor(s) Installed.
[01]: x64 Family 16 Model 2 Stepping 3
AuthenticAMD ~1200 Mhz
BIOS Version: American Megatrends Inc. 0906 , 25.12.2008
Reporter: Jani Simomaa
Priority: Blocker
Labels: jenkins, plugin
Attachments: RetryBuild_source.zip
Hey!
Jenkins version on both machines are latest 1.452
I'm having an issue with my own created plugin. It works fine if it is used
locally on my Windows master but when I try to upload this plugin to Ubuntu
master Jenkins the plugin and the Jenkins configure Job -view stuck with
LOADING text and gray background. I also get a huge stack trace into Jenkins
log but I'm not able to figure it out why it doesn't work.
Stack trace here: http://pastebin.com/T5JwJErq
I'll attach the source of my plugin.
Thanks!
--
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-9937) Rebuild plugin visible to everyone, regardless of project-based matrix security settings.
[ https://issues.jenkins-ci.org/browse/JENKINS-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159684#comment-159684 ] ragesh_nair commented on JENKINS-9937: -- The release 1.10 is having this fix. Are you still facing the issue?? Rebuild plugin visible to everyone, regardless of project-based matrix security settings. - Key: JENKINS-9937 URL: https://issues.jenkins-ci.org/browse/JENKINS-9937 Project: Jenkins Issue Type: Bug Components: rebuild Affects Versions: current Environment: Ubuntu, OS X Reporter: James Mills Assignee: ragesh_nair Hi. I am running Jenkins version 1.414, and I have the rebuild plugin installed. My Jenkins installation is locked down with project-based matrix security, allowing only read access to the anonymous user to both Jenkins and the project. However, in addition to read access, the anonymous user aso has the full ability to trigger a rebuild using the plugins added rebuild link! Is there a way to restrict this link, as I do not want anyone who is not approved to be able to (re)build on this server. Thanks! ~james -- 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-12898) Option for Valgrind report to include each problem as a test failure
[ https://issues.jenkins-ci.org/browse/JENKINS-12898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159685#comment-159685 ] gbois commented on JENKINS-12898: - Could you attach it? Option for Valgrind report to include each problem as a test failure Key: JENKINS-12898 URL: https://issues.jenkins-ci.org/browse/JENKINS-12898 Project: Jenkins Issue Type: Improvement Components: xunit Reporter: Chris Withers Assignee: gbois Priority: Minor It would be great if Valgrind xml could be turned into one-test-failure-per-error as an option. The current support turns the whole valgrind run into one test, which either passes or fails. This is great if you're starting from a zero-problem situation, however, if you're starting from a 1000s-of-problems situation, it would be great to be able to see the trend graph going down over time. I believe the proposal I make will address this, and might only need an xslt, but I don't have the xml skills to make that work... -- 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-12898) Option for Valgrind report to include each problem as a test failure
[ https://issues.jenkins-ci.org/browse/JENKINS-12898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159686#comment-159686 ] gbois commented on JENKINS-12898: - Do you know that the underlying library (DTKit) can call a Python script through the Java Scripting language (with Java 6)? Option for Valgrind report to include each problem as a test failure Key: JENKINS-12898 URL: https://issues.jenkins-ci.org/browse/JENKINS-12898 Project: Jenkins Issue Type: Improvement Components: xunit Reporter: Chris Withers Assignee: gbois Priority: Minor It would be great if Valgrind xml could be turned into one-test-failure-per-error as an option. The current support turns the whole valgrind run into one test, which either passes or fails. This is great if you're starting from a zero-problem situation, however, if you're starting from a 1000s-of-problems situation, it would be great to be able to see the trend graph going down over time. I believe the proposal I make will address this, and might only need an xslt, but I don't have the xml skills to make that work... -- 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-12898) Option for Valgrind report to include each problem as a test failure
[ https://issues.jenkins-ci.org/browse/JENKINS-12898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12898 started by gbois. Option for Valgrind report to include each problem as a test failure Key: JENKINS-12898 URL: https://issues.jenkins-ci.org/browse/JENKINS-12898 Project: Jenkins Issue Type: Improvement Components: xunit Reporter: Chris Withers Assignee: gbois Priority: Minor It would be great if Valgrind xml could be turned into one-test-failure-per-error as an option. The current support turns the whole valgrind run into one test, which either passes or fails. This is great if you're starting from a zero-problem situation, however, if you're starting from a 1000s-of-problems situation, it would be great to be able to see the trend graph going down over time. I believe the proposal I make will address this, and might only need an xslt, but I don't have the xml skills to make that work... -- 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-12900) Better feedback needed when a report can't be processed
[ https://issues.jenkins-ci.org/browse/JENKINS-12900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12900. - Resolution: Fixed These kind of errors are aimed at the integrators/administrators. xUnit have chosen to not provide these information in the Job log. These details can be displayed in the global configuration through the following actions: Manage Jenkins System Log Add new log recorder. Give a name as 'xUnit Logger' and add the following logger: * XUnitService for a severity as 'all' Better feedback needed when a report can't be processed --- Key: JENKINS-12900 URL: https://issues.jenkins-ci.org/browse/JENKINS-12900 Project: Jenkins Issue Type: Bug Components: xunit Reporter: Chris Withers Assignee: gbois The following is simply not enough to figure out what is wrong with a report file: [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing JUnit [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern '**/valgrind-junit.xml' relative to '/home/jenkins/workspace/workspace/valgrind' for the testing framework 'JUnit'. [xUnit] [ERROR] - The result file '/home/jenkins/workspace/workspace/valgrind/valgrind-junit.xml' for the metric 'JUnit' is not valid. The result file has been skipped. [xUnit] [INFO] - Setting the build status to FAILURE [xUnit] [INFO] - Stopping recording. It really needs to say at least what line caused the problem, and preferably what it thought the problem was. -- 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-12912) URLTtrigger does not poll on jobs which are tied to disconnected slaves
[
https://issues.jenkins-ci.org/browse/JENKINS-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159688#comment-159688
]
OHTAKE Tomohiro commented on JENKINS-12912:
---
Yes, that is the behavior of 0.9 and what I would like.
Since bringing slaves up takes much cost, I would like slaves to be powered off
while there are no jobs.
URLTtrigger does not poll on jobs which are tied to disconnected slaves
---
Key: JENKINS-12912
URL: https://issues.jenkins-ci.org/browse/JENKINS-12912
Project: Jenkins
Issue Type: Bug
Components: urltrigger
Environment: Jenkins 1.451
URLTrigger Plugin 0.10, 0.14
Reporter: OHTAKE Tomohiro
Assignee: gbois
Since 0.10, URLTtrigger does not poll on jobs which are tied to disconnected
slaves even if there are available executors on master.
URLTrigger Plugin 0.9 makes master poll the URL even if the jobs are tied to
slaves.
If there are changes in URL, a slave that is tied to the job wakes up and
runs the job.
URLTrigger 0.9 says that polling has been done on slaves, but master polles.
{code:title=URLTrigger Log (0.14, job which is tied to disconnected slaves)}
Polling for the job aa
Searching a node to run the polling for the label ''.
Can't find any complete active node for the polling action. Maybe slaves are
not yet active at this time or the number of executor of the master is 0.
Checking again in next polling schedule.
{code}
{code:title=URLTrigger Log (0.14, job which is not tied to any slaves)}
Polling for the job bb
Polling on master.
Polling started on Feb 28, 2012 10:22:42 AM
Invoking the url:
http://aaa.invalid/bb
Inspecting the content
Polling complete. Took 0.12 sec.
No changes.
{code}
{code:title=URLTrigger Log (0.9, job which is tied to disconnected slaves)}
Polling started on Feb 28, 2012 10:51:04 AM
Searching a node to run the polling for the label ''.
Invoking the url:
http://aaa.invalid/bb
Inspecting the content
Polling complete. Took 0.14 sec
No changes.
{code}
Workarounds:
* Downgrade URLTrigger Plugin to 0.9
* Do not tie jobs which uses Use URLTrigger
** Create a job that uses URLTrigger and do not tie the job to any slaves.
** Configure the job to build other projects in its post-build actions.
--
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-10167) Image is misplaced in background and long text shift right column,
[
https://issues.jenkins-ci.org/browse/JENKINS-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159689#comment-159689
]
SCM/JIRA link daemon commented on JENKINS-10167:
Code changed in jenkins
User: Seiji Sogabe
Path:
src/main/java/hudson/plugins/persona/selector/RightSideSelector.java
src/main/resources/hudson/plugins/persona/selector/RightSideSelector/config.jelly
src/main/resources/hudson/plugins/persona/selector/RightSideSelector/floatingBox.jelly
src/main/resources/hudson/plugins/persona/selector/RightSideSelector/summary.jelly
http://jenkins-ci.org/commit/persona-plugin/714de304b56583bde7f03a55982dc4745eb2c716
Log:
[FIXED JENKINS-10167]Image is misplaced in background and long text shift
right column.
Compare: https://github.com/jenkinsci/persona-plugin/compare/7163525...714de30
Image is misplaced in background and long text shift right column,
--
Key: JENKINS-10167
URL: https://issues.jenkins-ci.org/browse/JENKINS-10167
Project: Jenkins
Issue Type: Improvement
Components: persona
Affects Versions: current
Reporter: Vincent Carluer
Assignee: vcarluer
Fix For: current
Image in background can be override by build list.
Quote text in right shift hudson main right panel column based on its length.
I tried various jelly file and this one fits well to me:
!--
The MIT License
Copyright (c) 2009 Cliffano Subagio
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the Software), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
--
j:jelly xmlns:j=jelly:core xmlns:st=jelly:stapler xmlns:d=jelly:define
xmlns:l=/lib/layout xmlns:t=/lib/hudson xmlns:f=/lib/form
xmlns:i=jelly:fmt xmlns:local=local
j:set var=img value=${action.image}/
div style=max-width:400px;
img src=${rootURL}/${img.smallIconUrl} width=48 height=48 /
Foo Bar says: ${action.quote}
img src=${rootURL}/${img.backgroundImageUrl} width=100%/
/div
/j:jelly
--
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-12942) Make token macro either part of the core or ship it along with core.
Slide-O-Mix created JENKINS-12942: - Summary: Make token macro either part of the core or ship it along with core. Key: JENKINS-12942 URL: https://issues.jenkins-ci.org/browse/JENKINS-12942 Project: Jenkins Issue Type: Improvement Components: core Affects Versions: current Reporter: Slide-O-Mix Assignee: Kohsuke Kawaguchi Priority: Minor It would be nice to make the token macro plugin part of the core, or at least bundled with core so that the functionality could be added to more of Jenkins internals. -- 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-10550) Please add next-executions plugin to jira component list
[ https://issues.jenkins-ci.org/browse/JENKINS-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Kline closed JENKINS-10550. - Assignee: Peter Kline Please add next-executions plugin to jira component list Key: JENKINS-10550 URL: https://issues.jenkins-ci.org/browse/JENKINS-10550 Project: Jenkins Issue Type: Improvement Components: jira Reporter: Peter Kline Assignee: Peter Kline The Next Executions plugin is not listed in the component list: https://wiki.jenkins-ci.org/display/JENKINS/Next+Executions -- 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-9596) SCM polling with GIT creates Spurious Builds with No Changes
[ https://issues.jenkins-ci.org/browse/JENKINS-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159691#comment-159691 ] Peter Kline commented on JENKINS-9596: -- This is no longer an issue for us after using the method by Kohsuke: http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ SCM polling with GIT creates Spurious Builds with No Changes -- Key: JENKINS-9596 URL: https://issues.jenkins-ci.org/browse/JENKINS-9596 Project: Jenkins Issue Type: Bug Components: git Affects Versions: current Reporter: Charles Scalfani Assignee: abayer Priority: Minor Attachments: config.xml I see many builds when pushes to non-master branches (I'm only pulling from the master branch). The build is triggered by SCM change but the master branch has the same ID. Here is a discussion on StackOverflow where others are encountering the same problem (http://stackoverflow.com/questions/5784329/how-can-i-make-jenkins-ci-with-git-trigger-on-pushes-to-master). -- 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-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159692#comment-159692 ] Jaroslavas D. commented on JENKINS-12810: - Hi, Bruno. Release is good. I haven't fount any issues. One question. What about platform support? Is it any chance to have it in future? JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png, testlink-3.1-alpha2.hpi Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- 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-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159692#comment-159692 ] Jaroslavas D. edited comment on JENKINS-12810 at 3/1/12 7:32 AM: - Hi, Bruno. Release is good. I haven't found any issues. One question. What about platform support? Is it any chance to have it in future? was (Author: jar): Hi, Bruno. Release is good. I haven't fount any issues. One question. What about platform support? Is it any chance to have it in future? JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png, testlink-3.1-alpha2.hpi Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- 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-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159693#comment-159693 ] Jaroslavas D. commented on JENKINS-12810: - Oh, I have found what it's supported from 3.0 version (JENKINS-9054).. only for TAP. How it should be used? Is it possible to have it for JUnit? JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png, testlink-3.1-alpha2.hpi Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- 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
