[JIRA] [git-plugin] (JENKINS-30131) build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label
Title: Message Title Ferenc Kovacs commented on JENKINS-30131 Re: build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label the relevant code is here: https://github.com/jenkinsci/jenkins/blob/1fe9cf7b7ada45230f2bc5b8e2f1bdb93175ff9f/core/src/main/java/hudson/model/AbstractProject.java#L1415 that check was originally added to address https://issues.jenkins-ci.org/browse/JENKINS-1348 then was tweaked a bit over the years but mostly stayed the same so if there is no workspace and the job has a label which isn't the current nodeName it won't trigger a build. I think the check against the label should be improved, AFAIK it would be perfectly legal to trigger a build if the job is assigned to a label which has online nodes matching it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [git-plugin] (JENKINS-30131) build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label
Title: Message Title Ferenc Kovacs updated an issue Jenkins / JENKINS-30131 build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label Change By: Ferenc Kovacs I have a job which is set to poll a repository, and also uses the Polling uses certain paths behavior (include) along with the Force polling using workspace behavior.Polling worked properly when the workspace was already present, but äfter after wiping the workspace it did not trigger a build.When I made jenkins to poll the repo via calling /git/notifyCommit?url="" />Scheduled polling of chef-diff-app-apt-mirror-manualbut my job was not builtlooking into the git polling log for this job I've seen this:Started on Aug 25, 2015 9:43:02 AMNo workspace is available, so can’t check for updates. (nonexisting_workspace)Done. Took 2 msNo changesI've tried to simplify my build to see if that resolves the issue, and realized that removing the "Restrict where this project can be run" settings solves the issue, even thought that in my setup this setting was redundant as the only node available/allowed to run jobs without explicit node restrictions was the same as I was specifying with my label.After I removed the restrict label and curled /git/notifyCommit again I got a build started and this in my git polling log:Started on Aug 25, 2015 9:55:41 AMNo workspace is available, so can’t check for updates.Scheduling a new build to get a workspace. (nonexisting_workspace)Done. Took 1 msChanges foundLet me know if you need any more info to reproduce the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-30131) build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label
Title: Message Title Ferenc Kovacs updated an issue Jenkins / JENKINS-30131 build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label Change By: Ferenc Kovacs I have a job which is set to poll a repository, and also uses the Polling uses certain paths behavior (include) along with the Force polling using workspace behavior.Polling worked properly when the workspace was already present, but äfter wiping the workspace it did trigger a build.When I made jenkins to poll the repo via calling /git/notifyCommit?url="" />Scheduled polling of chef-diff-app-apt-mirror-manualbut my job was not builtlooking into the git polling log for this job I've seen this:Started on Aug 25, 2015 9:43:02 AMNo workspace is available, so can’t check for updates. (nonexisting_workspace)Done. Took 2 msNo changes I've tried to simplify my build to see if that resolves the issue, and realized that removing the "Restrict where this project can be run" settings solves the issue, even thought that in my setup this setting was redundant as the only node available/allowed to run jobs without explicit node restrictions was the same as I was specifying with my label. After I removed the restrict label and curled /git/notifyCommit again I got a build started and this in my git polling log:Started on Aug 25, 2015 9:55:41 AMNo workspace is available, so can’t check for updates.Scheduling a new build to get a workspace. (nonexisting_workspace)Done. Took 1 msChanges found I've tried to simplify my build to see if that resolves the issue, and realized that removing the "Restrict where this project can be run" settings solves the issue, even thought that in my setup this setting was redundant as the only node available/allowed to run jobs without explicit node restrictions was the same as I was specifying with my label. Let me know if you need any more info to reproduce the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-30131) build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label
Title: Message Title Ferenc Kovacs updated an issue Jenkins / JENKINS-30131 build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label Change By: Ferenc Kovacs I have a job which is set to poll a repository, and also uses the Polling uses certain paths behavior (include) along with the Force polling using workspace behavior.Polling worked properly when the workspace was already present, but äfter wiping the workspace it did trigger a build.When I made jenkins to poll the repo via calling /git/notifyCommit?url="" />Scheduled polling of chef-diff-app-apt-mirror-manualbut my job was not builtlooking into the git polling log for this job I've seen this:Started on Aug 25, 2015 9:43:02 AMNo workspace is available, so can’t check for updates. (nonexisting_workspace)Done. Took 2 msNo changes After I removed the restrict label and curled /git/notifyCommit again I got a build started and this in my git polling log:Started on Aug 25, 2015 9:55:41 AMNo workspace is available, so can’t check for updates.Scheduling a new build to get a workspace. (nonexisting_workspace)Done. Took 1 msChanges foundI 've tried to simplify my build to see if that resolves the issue, and realized that removing the "Restrict where this project can be run" settings solves the issue, even thought that in my setup this setting was redundant as the only node available/allowed to run jobs without explicit node restrictions was the same as I was specifying with my label.Let me know if you need any more info to reproduce the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-30131) build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label
Title: Message Title Ferenc Kovacs created an issue Jenkins / JENKINS-30131 build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 25/Aug/15 4:55 PM Environment: Jenkins version: 1.609.2 GIT Plugin version: 2.4.0 git version: 1.7.10.4 Labels: polling pollscm git-plugin Priority: Minor Reporter: Ferenc Kovacs I have a job which is set to poll a repository, and also uses the Polling uses certain paths behavior (include) along with the Force polling using workspace behavior. Polling worked properly when the workspace was already present, but äfter wiping the workspace it did trigger a build. When I made jenkins to poll the repo via calling /git/notifyCommit?url="" I got the following response: Scheduled polling of chef-diff-app-apt-mirror-manual but my job was not built looking into the git polling log for this job I've seen this: Started on Aug 25, 2015 9:43:02 AM No workspace is available, so can’t check for updates. (nonexistin
[JIRA] [matrix-project-plugin] (JENKINS-11993) matrix flyweight and configuration builds have "overlapping" workspace directories
Ferenc Kovacs commented on JENKINS-11993 matrix flyweight and configuration builds have "overlapping" workspace directories I don't have this problem anymore, as the project using this setup was eventually moved to git, but from a quick look into Throttle Concurrent Builds plugin, I'm not sure that this would solve the issue. AFAIR you don't have to enable concurrent execution for the matrix job to be able to bump into this issue, and I don't see any mention about flyweight builds at https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin and even if it would affect the execution of the flyweight jobs, this issue isn't about executing the jobs in concurrent, but executing the flyweight and the matrix configuration jobs on the same node (even in a serialized matter). could you ellaborate how would your suggestion work in the practice? I can see why could somebody argue that the svn plugin is doing what it was instructed to do (eg. wiping out any files/dirs from the checkout) but I think that it is rather unfortunate, that by default the checkout dir for the flyweight job to fetch the remote changes will use the same directory which the matrix configuration builds are residing in. 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/d/optout.
[JIRA] [jira] (JENKINS-16683) the Build Blocker Plugin is missing from Jira
Ferenc Kovacs commented on JENKINS-16683 the Build Blocker Plugin is missing from Jira I'm pretty sure that it wasn't there when I created the ticket (I tried everything starting with build or blocker), but now it is there, so this is resolved. 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] [jira] (JENKINS-16683) the Build Blocker Plugin is missing from Jira
Ferenc Kovacs resolved JENKINS-16683 as Fixed the Build Blocker Plugin is missing from Jira Change By: Ferenc Kovacs (03/Jul/13 2:25 PM) Status: Open Resolved Resolution: Fixed 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-16683) the Build Blocker Plugin is missing from Jira
Ferenc Kovacs created JENKINS-16683 the Build Blocker Plugin is missing from Jira Issue Type: Bug Assignee: Unassigned Components: jira Created: 07/Feb/13 3:50 PM Description: At first I've just thought that there are no open issues for this plugin, but when I clicked the Edit tab on the issue list for this plugin I got an error message telling me that: "The value 'build-blocker-plugin' does not exist for the field 'component'. I also tried finding the component using the autocomplete feature, but I couldn't find it, so it is either called something really un-intuitive or it is completely missing. Project: Jenkins Priority: Major Reporter: Ferenc Kovacs 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-11993) matrix flyweight and configuration builds have "overlapping" workspace directories
Ferenc Kovacs commented on JENKINS-11993 matrix flyweight and configuration builds have "overlapping" workspace directories for the record: I've just realized that the Exclude flyweight tasks plugin can be used to workaround this problem. 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-8460) xUnit does not parse nested -tags from PHPUnit
[ https://issues.jenkins-ci.org/browse/JENKINS-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161623#comment-161623 ] Ferenc Kovacs commented on JENKINS-8460: hm. now I'm getting "for the metric 'JUnit' is not valid. The result file has been skipped." for each of my sample junit.xml. could you give me a junit file which works for you? (of course all of my sample and "production" files are working with the built-in junit plugin just fine) I tried to test it with the latest release (non-lts) on a vanila ubuntu vm: same problem. > xUnit does not parse nested -tags from PHPUnit > - > > Key: JENKINS-8460 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8460 > Project: Jenkins > Issue Type: Improvement > Components: xunit >Affects Versions: current > Environment: Debian Lenny, PHP 5.3.5-0.dotdeb., PHPUnit 3.5.7 >Reporter: dito_ch >Assignee: gbois >Priority: Minor > > xUnit does not read the following output with nested -tags from > PHPUnit: > > assertions="2" failures="0" errors="0" time="0.032417"> > assertions="2" failures="0" errors="0" time="0.032417"> > file="src/protected/tests/unit/DbTest.php" line="4" assertions="2" > time="0.032417"/> > > > > The version without nested tags works: > > assertions="2" failures="0" errors="0" time="0.032417"> > file="src/protected/tests/unit/DbTest.php" line="4" assertions="2" > time="0.032417"/> > > > I think it would be nice, if xUnit supports nested -tags. The > workaround with a xlst is somehow cumbersome. -- 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-8460) xUnit does not parse nested -tags from PHPUnit
[ https://issues.jenkins-ci.org/browse/JENKINS-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161116#comment-161116 ] Ferenc Kovacs commented on JENKINS-8460: I can still reproduce the problem with the same junit.xml after upgrading the xunit plugin: 02-Apr-2012 23:07:43 hudson.plugins.labeledgroupedtests.LabeledTestResultGroupPublisher perform INFO: Test results parsed: hudson.plugins.labeledgroupedtests.MetaLabeledTestResultGroup@57476fc5 02-Apr-2012 23:07:43 com.thalesgroup.hudson.plugins.xunit.service.XUnitService infoSystemLogger INFO: [xUnit] - [JUnit] - 1 test report file(s) were found with the pattern 'junit.xml' relative to '/var/lib/jenkins/jobs/test-xunit/workspace' for the testing framework 'JUnit'. 02-Apr-2012 23:07:43 com.thalesgroup.hudson.plugins.xunit.service.XUnitService warningSystemLogger WARNING: [xUnit] - The file '/var/lib/jenkins/jobs/test-xunit/workspace/junit.xml' is an invalid file. 02-Apr-2012 23:07:43 com.thalesgroup.hudson.plugins.xunit.service.XUnitService errorSystemLogger SEVERE: [xUnit] - The result file '/var/lib/jenkins/jobs/test-xunit/workspace/junit.xml' for the metric 'JUnit' is not valid. The result file has been skipped. > xUnit does not parse nested -tags from PHPUnit > - > > Key: JENKINS-8460 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8460 > Project: Jenkins > Issue Type: Improvement > Components: xunit >Affects Versions: current > Environment: Debian Lenny, PHP 5.3.5-0.dotdeb., PHPUnit 3.5.7 >Reporter: dito_ch >Assignee: gbois >Priority: Minor > > xUnit does not read the following output with nested -tags from > PHPUnit: > > assertions="2" failures="0" errors="0" time="0.032417"> > assertions="2" failures="0" errors="0" time="0.032417"> > file="src/protected/tests/unit/DbTest.php" line="4" assertions="2" > time="0.032417"/> > > > > The version without nested tags works: > > assertions="2" failures="0" errors="0" time="0.032417"> > file="src/protected/tests/unit/DbTest.php" line="4" assertions="2" > time="0.032417"/> > > > I think it would be nice, if xUnit supports nested -tags. The > workaround with a xlst is somehow cumbersome. -- 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-6443) AggregatedTestResultPublisher$TestResultAction cannot be cast to hudson.tasks.test.TestResult
[ https://issues.jenkins-ci.org/browse/JENKINS-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161065#comment-161065 ] Ferenc Kovacs commented on JENKINS-6443: I'm still seeing broken graphs with this error on my jenkins install (jenkins lts 1.447.1 running on debian squeeze). Some jobs (with the same config except they are using different git branches) are fine others borked. > AggregatedTestResultPublisher$TestResultAction cannot be cast to > hudson.tasks.test.TestResult > - > > Key: JENKINS-6443 > URL: https://issues.jenkins-ci.org/browse/JENKINS-6443 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Hudson 1.356 on Java 1.6.0_20 x64, Windows Server 2008 > x64 >Reporter: Arve Knudsen > Fix For: current > > > I am having some issues with publishing of JUnit reports, in that certain > data don't come out right. Aggregation of testresults is enabled. I see in > Hudson's log that exceptions are reported, at least some of which have to do > with testresult reporting. I've attached a paste of my log, so you should be > able to grasp the context in which this is happening. -- 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-8460) xUnit does not parse nested -tags from PHPUnit
[ https://issues.jenkins-ci.org/browse/JENKINS-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferenc Kovacs reopened JENKINS-8460: I'm experiencing the same issue. this doesn't work: https://gist.github.com/2142831/c2dc88f5179bfeecd9cd586306f9946fb88210a0 this one works (if I remove the nested testsuite tags) https://gist.github.com/2142831/3daf2e9f8fdbef30ecb800040675af63d6d8dfee I wanted to move from the built-in junit plugin to xunit when I bumped into this. The junit plugin was supporting my nested testsuites (see https://issues.jenkins-ci.org/browse/JENKINS-6545). I'm using the latest lts(1.424.6) with the latest available xunit plugin(1.40). Here is the relevant lines from the logs: 21-Mar-2012 00:43:04 com.thalesgroup.hudson.plugins.xunit.service.XUnitService infoSystemLogger INFO: [xUnit] - [JUnit] - 1 test report file(s) were found with the pattern 'junit.xml' relative to '/var/lib/jenkins/jobs/test-xunit/workspace' for the testing framework 'JUnit'. 21-Mar-2012 00:43:04 com.thalesgroup.hudson.plugins.xunit.service.XUnitService warningSystemLogger WARNING: [xUnit] - The file '/var/lib/jenkins/jobs/test-xunit/workspace/junit.xml' is an invalid file. 21-Mar-2012 00:43:04 com.thalesgroup.hudson.plugins.xunit.service.XUnitService errorSystemLogger SEVERE: [xUnit] - The result file '/var/lib/jenkins/jobs/test-xunit/workspace/junit.xml' for the metric 'JUnit' is not valid. The result file has been skipped. let me know if you need anything else to reproduce the issue. > xUnit does not parse nested -tags from PHPUnit > - > > Key: JENKINS-8460 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8460 > Project: Jenkins > Issue Type: Improvement > Components: xunit >Affects Versions: current > Environment: Debian Lenny, PHP 5.3.5-0.dotdeb., PHPUnit 3.5.7 >Reporter: dito_ch >Assignee: gbois >Priority: Minor > > xUnit does not read the following output with nested -tags from > PHPUnit: > > assertions="2" failures="0" errors="0" time="0.032417"> > assertions="2" failures="0" errors="0" time="0.032417"> > file="src/protected/tests/unit/DbTest.php" line="4" assertions="2" > time="0.032417"/> > > > > The version without nested tags works: > > assertions="2" failures="0" errors="0" time="0.032417"> > file="src/protected/tests/unit/DbTest.php" line="4" assertions="2" > time="0.032417"/> > > > I think it would be nice, if xUnit supports nested -tags. The > workaround with a xlst is somehow cumbersome. -- 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
