[JIRA] (JENKINS-50019) java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title Rick Oosterholt commented on JENKINS-50019 Re: java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer Rebooting did the trick for me to. Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189018.1520521286000.5470.1578562920394%40Atlassian.JIRA.
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title Rick Oosterholt updated an issue Jenkins / JENKINS-58381 Trend graph not appearing Change By: Rick Oosterholt Comment: This bug doesn't only concern pipeline jobs only. Freestyle jobs neither shows a trend chart. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200503.1562595115000.7907.1567753441581%40Atlassian.JIRA.
[JIRA] (JENKINS-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Rick Oosterholt commented on JENKINS-40251 Re: Dependency Check trend graphs and related values are not shown None of the tickets above concern the portlet. Should this ticket be reopen or should I create a new ticket for the dependency check portlet bug? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176904.1481021727000.7902.1567753380713%40Atlassian.JIRA.
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title Rick Oosterholt commented on JENKINS-58381 Re: Trend graph not appearing This bug doesn't only concern pipeline jobs only. Freestyle jobs neither shows a trend chart. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200503.1562595115000.7893.1567753260566%40Atlassian.JIRA.
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title Rick Oosterholt assigned an issue to Rick Oosterholt Jenkins / JENKINS-58381 Trend graph not appearing Change By: Rick Oosterholt Assignee: Steve Springett Rick Oosterholt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200503.1562595115000.7875.1567753081998%40Atlassian.JIRA.
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title Rick Oosterholt assigned an issue to Unassigned Jenkins / JENKINS-58381 Trend graph not appearing Change By: Rick Oosterholt Assignee: Rick Oosterholt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200503.1562595115000.7881.1567753082240%40Atlassian.JIRA.
[JIRA] (JENKINS-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Rick Oosterholt commented on JENKINS-40251 Re: Dependency Check trend graphs and related values are not shown Would you be so kind to add a comment with a link to the new-codebase-issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176904.1481021727000.7214.1567692061424%40Atlassian.JIRA.
[JIRA] (JENKINS-59238) Add links to the CVE information of the NVD site
Title: Message Title Rick Oosterholt created an issue Jenkins / JENKINS-59238 Add links to the CVE information of the NVD site Issue Type: New Feature Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-09-05 07:16 Priority: Minor Reporter: Rick Oosterholt The old version of the dependency check plugin created a report with direct links the the NVD site. This was very convenient. It would be nice to have this link added again in the 5.x version. Add Comment This messa
[JIRA] (JENKINS-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Rick Oosterholt reopened an issue Jenkins / JENKINS-40251 Dependency Check trend graphs and related values are not shown Change By: Rick Oosterholt Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176904.1481021727000.6902.1567667641081%40Atlassian.JIRA.
[JIRA] (JENKINS-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Rick Oosterholt commented on JENKINS-40251 Re: Dependency Check trend graphs and related values are not shown Reopened because the latest 5.x release broke the dependency check portlet again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176904.1481021727000.6899.1567667641040%40Atlassian.JIRA.
[JIRA] (JENKINS-47445) 'Zero state image' trend graph is misleading
Title: Message Title Rick Oosterholt commented on JENKINS-47445 Re: 'Zero state image' trend graph is misleading Can you explain why? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185891.1508139462000.3582.1562477700127%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53439) Variables are not substituted for repository browser url
Title: Message Title Rick Oosterholt commented on JENKINS-53439 Re: Variables are not substituted for repository browser url This issue is still valid. It also shows in the job 'Changes'; the parameter in the Changeset revision url isn't replaces either. We are also using the Jira plugin, the 'Update relevant issues' feature also suffers this issue since the Jira tickets are also updated with comments with the corrupt url. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Rick Oosterholt commented on JENKINS-53745 Re: Multiple JUnit reports recordings analyses at the same time Well, this fix introduces this nasty side effect. I'm not even using a 'absolute path'. Previously it was not skipping any test result file when analyzing the performance. Maybe it has something to do with the fact we use multiple jenkins nodes? What information can I supply in order to get this bug fix? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Rick Oosterholt edited a comment on JENKINS-53745 Re: Multiple JUnit reports recordings analyses at the same time I'm afraid that has nothing to do with it. The configured source path used to work as expected for more than a year now. Only recently this issue occurred.Even after changing the source path to a restrictive "report/test/TEST-*.xml" , the plugin starts evaluating the test files with multiple 'threads'... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Rick Oosterholt commented on JENKINS-53745 Re: Multiple JUnit reports recordings analyses at the same time I'm afraid that has nothing to do with it. The configured source path used to work as expected for more than a year now. Only recently this issue occurred. Even after changing the source path to a restrictive "report/test/TEST-*.xml" the plugin starts evaluating the test files with multiple 'threads'... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Rick Oosterholt commented on JENKINS-53745 Re: Multiple JUnit reports recordings analyses at the same time Builds in which the performance plugins seems to run multiple times, also adds a new artifact to the build generated by the performance plugin: standardResults.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title
Rick Oosterholt edited a comment on JENKINS-53745
Re: Multiple JUnit reports recordings analyses at the same time
bq. {quote} Could you please check count of files in this path? {quote} Our Jenkins instance works with multiple slaves; The directory structure is somewhat different in slaves than on the master node. Workspaces are not located inside the 'builds' directory, but if I use the following command:{noformat}ls /var/lib/jenkins/workspace/JOB_NAME/report/ \ * \ */*.xml | wc -l{noformat}in the slave 'workspace path', the results is 314 file (could be the 311, at the time of reporting of this issue). bq. {quote} Does the count of line above ^^^ increase on each build? {quote} No, this is always printed 311 times.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Rick Oosterholt commented on JENKINS-53745 Re: Multiple JUnit reports recordings analyses at the same time Could you please check count of files in this path? Our Jenkins instance works with multiple slaves; The directory structure is somewhat different in slaves than on the master node. Workspaces are not located inside the 'builds' directory, but if I use the following command: ls /var/lib/jenkins/workspace/JOB_NAME/report/\*\*/*.xml | wc -l in the slave 'workspace path', the results is 314 file (could be the 311, at the time of reporting of this issue). Does the count of line above ^^^ increase on each build? No, this is always printed 311 times. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Rick Oosterholt commented on JENKINS-53745 Re: Multiple JUnit reports recordings analyses at the same time How can I debug this issue? It's really getting a big problem because of the huge workspaces and the major increase of the build time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title
Rick Oosterholt updated an issue
Jenkins / JENKINS-53745
Multiple JUnit reports recordings analyses at the same time
Change By:
Rick Oosterholt
Normally the build log shows one line stating JUnit reports recordings are beings analysed like this:{noformat}Performance: Recording JUnit reports '**/report/**/*.xml'{noformat}But on my builds the 'Recording JUnit reports' line is repeated * 310 times * ! The total build size increased from ~20Mb to ~*200Mb*.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Rick Oosterholt created an issue Jenkins / JENKINS-53745 Multiple JUnit reports recordings analyses at the same time Issue Type: Bug Assignee: Andrey Pokhilko Components: performance-plugin Created: 2018-09-24 12:01 Environment: Jenkins ver. 2.133 Performance Plugin 3.12 Priority: Major Reporter: Rick Oosterholt Normally the build log shows one line stating JUnit reports recordings are beings analysed like this: Performance: Recording JUnit reports '**/report/**/*.xml' But on my builds the 'Recording JUnit reports' line is repeated 310 times! Add Comment
[JIRA] (JENKINS-19767) "No permission to view config history" when pressing "Config changed since last build" badge on job page
Title: Message Title Rick Oosterholt commented on JENKINS-19767 Re: "No permission to view config history" when pressing "Config changed since last build" badge on job page I'm facing the same issue. We do not use https, so that didn't solve the issue. What information do you need? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-19767) "No permission to view config history" when pressing "Config changed since last build" badge on job page
Title: Message Title Rick Oosterholt assigned an issue to Mirko Friedenhagen Jenkins / JENKINS-19767 "No permission to view config history" when pressing "Config changed since last build" badge on job page Change By: Rick Oosterholt Assignee: Mirko Friedenhagen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-19767) "No permission to view config history" when pressing "Config changed since last build" badge on job page
Title: Message Title Rick Oosterholt reopened an issue Jenkins / JENKINS-19767 "No permission to view config history" when pressing "Config changed since last build" badge on job page Change By: Rick Oosterholt Resolution: Not A Defect Status: Closed Reopened Assignee: Mirko Friedenhagen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Rick Oosterholt commented on JENKINS-40251 Re: Dependency Check trend graphs and related values are not shown When can we expect the 1.4.5 release? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Rick Oosterholt commented on JENKINS-40251 Re: Dependency Check trend graphs and related values are not shown Has anyone filed a bug on the analysis-core-plugin? This issue is still reproducible with dependency-check 1.4.4, Jenkins 2.39 and analysis-core-plugin 1.81. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35257) Release plugin ignores release parameters in Jenkins 2.7
Title: Message Title Rick Oosterholt resolved as Fixed Released it in 2.6 Jenkins / JENKINS-35257 Release plugin ignores release parameters in Jenkins 2.7 Change By: Rick Oosterholt Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34979) Port allocation duplicate on "Concurrent builds"
Title: Message Title Rick Oosterholt commented on JENKINS-34979 Re: Port allocation duplicate on "Concurrent builds" Ryan Cocks: Non sure, probably between 1.652 and 1.656 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33263) Detecting mercurial changes doesn't work for "concurrent builds"
Title: Message Title Rick Oosterholt commented on JENKINS-33263 Re: Detecting mercurial changes doesn't work for "concurrent builds" Really? General aspects are able to run concurrent builds and haven scm changes. Not when combining there are no changes anymore. Might be hard to fix, but no reason to mark it as 'not a defect' IMHO Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35700) Add 'JDK parameter' as option for 'Parameters for test job'
Title: Message Title Rick Oosterholt updated an issue Jenkins / JENKINS-35700 Add 'JDK parameter' as option for 'Parameters for test job' Change By: Rick Oosterholt The parallel test executor plugin already support 'Parameters for test job'. A 'JDK parameter' would be very useful to be able to run the test for a specific JDK.JDK parameter per project is supported by [ this plugin JDK Parameter Plugin | https://wiki.jenkins-ci.org/display/JENKINS/ JDK + Parameter + Plugin]. Maybe it can be used? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35700) Add 'JDK parameter' as option for 'Parameters for test job'
Title: Message Title Rick Oosterholt updated an issue Jenkins / JENKINS-35700 Add 'JDK parameter' as option for 'Parameters for test job' Change By: Rick Oosterholt The parallel test executor plugin already support 'Parameters for test job'. A 'JDK parameter' would be very useful to be able to run the test tests for a specific JDK.JDK parameter per project is supported by [JDK Parameter Plugin|https://wiki.jenkins-ci.org/display/JENKINS/JDK+Parameter+Plugin]. Maybe it can be used? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35700) Add 'JDK parameter' as option for 'Parameters for test job'
Title: Message Title Rick Oosterholt updated an issue Jenkins / JENKINS-35700 Add 'JDK parameter' as option for 'Parameters for test job' Change By: Rick Oosterholt Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35700) Add 'JDK parameter' as option for 'Parameters for test job'
Title: Message Title Rick Oosterholt updated an issue Jenkins / JENKINS-35700 Add 'JDK parameter' as option for 'Parameters for test job' Change By: Rick Oosterholt Labels: bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35700) Add 'JDK parameter' as option for 'Parameters for test job'
Title: Message Title Rick Oosterholt updated an issue Jenkins / JENKINS-35700 Add 'JDK parameter' as option for 'Parameters for test job' Change By: Rick Oosterholt I just created a new The parallel test executor plugin already support 'Parameters for test job that only contains a Parallel Test Execution ' . Tried the job with both a matrix job, and a regular maven job.Both fail with this exception:Copying file to FATAL: Failed to copy /var/lib/jenkins/jobs/backstage.ParallelTestExecution/builds/2013-06-06_20-20-25/ A 'JDK parameter -files/test-splits/split.1.txt ' would be very useful to /home/builder/workspace/backstage.Test.chromehudson.util.IOException2: Failed be able to copy /var/lib/jenkins/jobs/backstage.ParallelTestExecution/builds/2013-06-06_20-20-25/parameter-files/ run the test -splits/split for a specific JDK . 1.txt to /home/builder/workspace/backstage.Test.chrome at hudson.FilePath.copyTo(FilePath.java:1726) at hudson.model.FileParameterValue$FileItemImpl.write(FileParameterValue.java:267) at hudson.FilePath.copyFrom(FilePath.java:830) at hudson.model.FileParameterValue$2.setUp(FileParameterValue.java:136) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1576) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241)Caused JDK parameter per project is supported by : java [this plugin|JDK Parameter Plugin] . io.FileNotFoundException: /home/builder/workspace/backstage.Test.chrome (Is a directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:179) at java.io.FileOutputStream.(FileOutputStream.java:131) at hudson.FilePath.write(FilePath.java:1622) at hudson.FilePath.copyTo(FilePath.java:1719) ... 9 more Maybe it can be used? Add Comment
[JIRA] (JENKINS-35700) Add 'JDK parameter' as option for 'Parameters for test job'
Title: Message Title Rick Oosterholt created an issue Jenkins / JENKINS-35700 Add 'JDK parameter' as option for 'Parameters for test job' Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: parallel-test-executor-plugin Created: 2016/Jun/14 1:37 PM Labels: bug Priority: Major Reporter: Rick Oosterholt I just created a new job that only contains a Parallel Test Execution. Tried the job with both a matrix job, and a regular maven job. Both fail with this exception: Copying file to FATAL: Failed to copy /var/lib/jenkins/jobs/backstage.ParallelTestExecution/builds/2013-06-06_20-20-25/parameter-files/test-splits/split.1.txt to /home/builder/workspace/backstage.Test.chrome hudson.util.IOException2: Failed to copy /var/lib/jenkins/jobs/backstage.ParallelTestExecution/builds/2013-06-06_20-20-25/parameter-files/test-splits/split.1.txt to /home/builder/workspace/backstage.Test.chrome at hudson.FilePath.copyTo(FilePath.java:1726) at hudson.model.FileParameterValue$FileItemImpl.write(FileParameterValue.java:267) at hudson.FilePath.copyFrom(FilePath.java:830) at hudson.model.FileParameterValue$2.setUp(FileParameterValue.java:136) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1576) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Caused by: java.io.FileNotFoundException: /home/builder/workspace/bac
[JIRA] (JENKINS-35700) Add 'JDK parameter' as option for 'Parameters for test job'
Title: Message Title Rick Oosterholt updated an issue Jenkins / JENKINS-35700 Add 'JDK parameter' as option for 'Parameters for test job' Change By: Rick Oosterholt Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [port-allocator-plugin] (JENKINS-34979) Port allocation duplicate on "Concurrent builds"
Title: Message Title Rick Oosterholt updated an issue Jenkins / JENKINS-34979 Port allocation duplicate on "Concurrent builds" Change By: Rick Oosterholt Priority: Minor Major 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] [port-allocator-plugin] (JENKINS-34979) Port allocation duplicate on "Concurrent builds"
Title: Message Title Rick Oosterholt created an issue Jenkins / JENKINS-34979 Port allocation duplicate on "Concurrent builds" Issue Type: Bug Assignee: Andres Rodriguez Components: port-allocator-plugin Created: 2016/May/20 10:27 AM Environment: Jenkins Version: 2.5 OS: Ubuntu Guess it is introduced in Jenkins 2.0? Was there a rewrite in how plugins are loaded when running concurrent? Its own classloader? Priority: Minor Reporter: Rick Oosterholt When configuring a "Pooled TCP port", the pool assignment is not unique when the build is performed concurrently (see "Execute concurrent builds if necessary"). Never had an issue before and problem seems to be introduced after we updated to Jenkins 2.0. Easy repro: create new job with "Pooled TCP port" and "Execute concurrent builds if necessary" options execute build multiple times see console output: same
[JIRA] [core] (JENKINS-34113) Add possibility to number of builds to BuildTimeTrend
Title: Message Title Rick Oosterholt created an issue Jenkins / JENKINS-34113 Add possibility to number of builds to BuildTimeTrend Issue Type: New Feature Assignee: Unassigned Components: core Created: 2016/Apr/08 7:24 AM Priority: Minor Reporter: Rick Oosterholt It would be nice if the 'build time trend' chart can be configured. This could be do by a configure button just like 'Dependency-Check trend', 'PMD trend', 'Java Warnings Trend', 'Open Tasks Trend' or 'Log Parser Trend'. It could also be done by making it possible to supply a url parameter to the build time trend chart url; e.g. /job/buildTimeGraph/png?nrBuilds=X Add Comment
[JIRA] [mercurial-plugin] (JENKINS-33263) Detecting mercurial changes doesn't work for "concurrent builds"
Title: Message Title Rick Oosterholt updated an issue Jenkins / JENKINS-33263 Detecting mercurial changes doesn't work for "concurrent builds" Change By: Rick Oosterholt The changelog of a build cannot be determined when a job is configured to "Execute concurrent builds if necessary".When for example four builds run concurrent, three builds report"WARN: Revision data for previous build unavailable; unable to determine change log" Always one One of the concurrent builds always is able to determine the changelog.This is probably caused by the fact that the builds try to get the revision of the build which is executed concurrent and does not yet have the revision data determined. 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] [mercurial-plugin] (JENKINS-33263) Detecting mercurial changes doesn't work for "concurrent builds"
Title: Message Title Rick Oosterholt created an issue Jenkins / JENKINS-33263 Detecting mercurial changes doesn't work for "concurrent builds" Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin Created: 02/Mar/16 9:55 AM Environment: Jenkins ver. 1.651 Linux (amd64) Multiple nodes Priority: Minor Reporter: Rick Oosterholt The changelog of a build cannot be determined when a job is configured to "Execute concurrent builds if necessary". When for example four builds run concurrent, three builds report "WARN: Revision data for previous build unavailable; unable to determine change log" Always one of the concurrent builds is able to determine the changelog. This is probably caused by the fact that the builds try to get the revision of the build which is executed concurrent and does not yet have the revision data determined.
[JIRA] [build-timeout-plugin] (JENKINS-789) build-timeout — ver.1.3: should kill the all process tree.
Title: Message Title
Rick Oosterholt edited a comment on JENKINS-789
Re: build-timeout — ver.1.3: should kill the all process tree.
Problem for us too since we use ant to run our unit tests with: "forked". OS is Linux. {code:xml} {code}
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] [build-timeout-plugin] (JENKINS-789) build-timeout — ver.1.3: should kill the all process tree.
Title: Message Title Rick Oosterholt commented on JENKINS-789 Re: build-timeout — ver.1.3: should kill the all process tree. Problem for us too since we use ant to run our unit tests with: "true" ... /> 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] [core] (JENKINS-28800) Sorting is inverted by default (Name descending)
Title: Message Title Rick Oosterholt created an issue Jenkins / JENKINS-28800 Sorting is inverted by default (Name descending) Issue Type: Bug Assignee: Unassigned Attachments: Selection_011.png Components: core Created: 09/Jun/15 8:24 AM Priority: Minor Reporter: Rick Oosterholt Views are default sorted by Name in the inverted order. Sorting should be ascending by default. Add Comment
[JIRA] [junit] (JENKINS-24580) "Older" and "Newer" buttons should be flipped
Rick Oosterholt created JENKINS-24580 "Older" and "Newer" buttons should be flipped Issue Type: Bug Assignee: Unassigned Attachments: JENKINS-24580.png Components: junit Created: 04/Sep/14 11:44 AM Description: When viewing the history of test results the "Newer" and "Older" buttons should be flipped. This order just doesn't make sense. Project: Jenkins Priority: Minor Reporter: Rick Oosterholt 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] [junit] (JENKINS-24580) "Older" and "Newer" buttons should be flipped
Rick Oosterholt updated JENKINS-24580 "Older" and "Newer" buttons should be flipped Change By: Rick Oosterholt (04/Sep/14 11:47 AM) Attachment: JENKINS-24580.png 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] [core] (JENKINS-24244) Scheduled polling not run
Rick Oosterholt commented on JENKINS-24244 Scheduled polling not run There's this weird behavior in Jenkins that skips any SCM polling while Jenkins is in "quiet down" mode (the red banner "Jenkins is preparing to shut down"). Make sure you're not in this mode (one of the backup plugins does this IIRC) at the scheduled time. That's it! I'm using Exclusive Execution Plugin which puts Jenkins in "shutdown mode". Thanks for your help! Has anyone an idea to ensure a specific project is executed "exclusively" in Jenkins? 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] [core] (JENKINS-24244) Scheduled polling not run
Rick Oosterholt edited a comment on JENKINS-24244 Scheduled polling not run Setting the hudson.triggers.Trigger log to FINER shows indeed: ... cron checking 20-8-14 2:03 ... aug 20, 2014 2:03:01 PM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@64ae3cef[Build STABLE] with spec ‘H 3 * * 1-6’ aug 20, 2014 2:02:01 PM FINER hudson.triggers.Trigger did not trigger hudson.model.FreeStyleProject@64ae3cef[Build STABLE] ... enter/leaving the cron schedule field in config shows the correct info (I've translated it to EN): Would last have run at Wednesday August 20 2014 3:00:08 CEST; would next run at Thursday 21 August 2014 3:00:08 CEST. I'll check for the hudson.triggers.SCMTrigger logging tomorrow (do not want to change the cron spec; might have something to to with the issue) 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] [core] (JENKINS-24244) Scheduled polling not run
Rick Oosterholt commented on JENKINS-24244 Scheduled polling not run Well, that might be my bad. I just copied the relevant part of the log. I really should have mentioned that ... the log is quite large and does contain cron checking 20-8-14 2:03 the hudson.triggers.SCMTrigger is completely empty. what is the next step to do to help you guys get the right info? 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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt edited a comment on JENKINS-24244 Polling of Mercurial scm stoped working Setting the hudson.triggers.Trigger log to FINER shows indeed: aug 20, 2014 2:03:01 PM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@64ae3cef[Build STABLE] with spec ‘H 3 * * 1-6’ aug 20, 2014 2:02:01 PM FINER hudson.triggers.Trigger did not trigger hudson.model.FreeStyleProject@64ae3cef[Build STABLE] enter/leaving the cron schedule field in config shows the correct info (I've translated it to EN): Would last have run at Wednesday August 20 2014 3:00:08 CEST; would next run at Thursday 21 August 2014 3:00:08 CEST. I'll check for the hudson.triggers.SCMTrigger logging tomorrow (do not want to change the cron spec; might have something to to with the issue) 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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt commented on JENKINS-24244 Polling of Mercurial scm stoped working Setting the hudson.triggers.Trigger log to FINER shows indeed: aug 20, 2014 2:03:01 PM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@64ae3cef[Build STABLE] with spec ‘H 3 * * 1-6’ aug 20, 2014 2:02:01 PM FINER hudson.triggers.Trigger did not trigger hudson.model.FreeStyleProject@64ae3cef[Build STABLE] enter/leaving the cron schedule field in config shows the correct info (I've translated it to EN): Would last have run at Wednesday August 20 2014 3:00:08 CEST; would next run at Thursday 21 August 2014 3:00:08 CEST. I'll check for the hudson.triggers.SCMTrigger logging tomorrow (do not want to change the cron spec; might have something to to with the issue... 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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt commented on JENKINS-24244 Polling of Mercurial scm stoped working I've checked the scm-polling.log from the project, but this was only containing info from the latest manual trigger performed by /job/foo/polling. 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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt commented on JENKINS-24244 Polling of Mercurial scm stoped working In Manage Jenkins » System Logs, create a new log recorder and add a logger hudson.triggers.Trigger at level FINE. Any interesting output after a while? Seems to work OK, this is logged every minute: aug 20, 2014 9:15:01 AM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@64ae3cef[Build STABLE] with spec ‘H 3 * * 1-6’ 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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt commented on JENKINS-24244 Polling of Mercurial scm stoped working Thanks Daniel for helping out and guiding me. Yes, when navigating to /job/foo/polling, the build is scheduled/executed and the polling log is updated. output of /descriptor/hudson.triggers.SCMTrigger: Current SCM Polling Activities No polling activity is in progress. 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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt commented on JENKINS-24244 Polling of Mercurial scm stoped working Well, instead of marking this issue at resolved, you could have just asked for more info. That is the reason I posted this issue; though the community/maintainers would request more info when needed or guide a user to get some... here's the requested info: Polling used to work just fine. We have lots of other build which still work fine. As stated, the polling runs only once after restart of Jenkins. The plugin version is 1.50. We are only using Mercurial, so I cannot say whether or not other SCMs do work. Seems like you are not using caching. Not sure what you mean, were can I check this. If you or others need any more info or guide me to get logging or something, I would be more than happy to provide it. 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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt reopened JENKINS-24244 Polling of Mercurial scm stoped working Change By: Rick Oosterholt (19/Aug/14 7:03 AM) Resolution: Incomplete Status: Resolved Reopened 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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt
updated JENKINS-24244
Polling of Mercurial scm stoped working
Change By:
Rick Oosterholt
(13/Aug/14 12:09 PM)
Description:
Mercurial scm polling stops after running once after restart.
Jenkins version: 1.570 (can only choose 'current' in Jira)
config.xml scm:{code:xml}(Default)http://host/path/projectBRANCHstabletruehttp://host/path/project/false{code}config.xml triggers:{code:xml}H 3 * * 1-6false{code}scm-polling.log (today is 14-aug-2014, so it did not run for a couple of days already):{code}Started on 9-aug-2014 3:27:01Polling SCM changes on master[workspace] $ hg pull --rev stablepulling from http://host/path/projectno changes found[workspace] $ hg log --rev stable --template {node}[workspace] $ hg log --rev stable --template {rev}Done. Took 1,3 secondenNo changes{code}
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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt
updated JENKINS-24244
Polling of Mercurial scm stoped working
Change By:
Rick Oosterholt
(13/Aug/14 12:08 PM)
Description:
Mercurial scm polling stops after running once after restart.config.xml scm:{code:xml}(Default)http://host/path/projectBRANCHstabletruehttp://host/path/project/false{code}config.xml triggers:{code:xml}H 3 * * 1-6false{code}scm-polling.log
(today is 14-aug-2014, so it did not run for a couple of days already)
:{code}Started on 9-aug-2014 3:27:01Polling SCM changes on master[workspace] $ hg pull --rev stablepulling from http://host/path/projectno changes found[workspace] $ hg log --rev stable --template {node}[workspace] $ hg log --rev stable --template {rev}Done. Took 1,3 secondenNo changes{code}
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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt
updated JENKINS-24244
Polling of Mercurial scm stoped working
Change By:
Rick Oosterholt
(13/Aug/14 12:06 PM)
Summary:
Polling of Mercurial scm
stop
stoped
working
Description:
Mercurial scm polling stops after running once after restart.config.xml scm:{code:xml}(Default)http://host/path/projectBRANCHstabletruehttp://host/path/project/false{code}
config.xml
triggers:{code:xml}H 3 * * 1-6false{code}
scm-polling.log:{code}Started on 9-aug-2014 3:27:01Polling SCM changes on master[workspace] $ hg pull --rev stablepulling from http://host/path/projectno changes found[workspace] $ hg log --rev stable --template {node}[workspace] $ hg log --rev stable --template {rev}Done. Took 1,3 secondenNo changes{code}
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] [mercurial] (JENKINS-24244) Polling of Mercurial scm stop working
Rick Oosterholt created JENKINS-24244 Polling of Mercurial scm stop working Issue Type: Bug Assignee: Jesse Glick Components: mercurial, pollscm Created: 13/Aug/14 11:58 AM Description: Mercurial scm polling stops after running once after restart. config.xml scm: "hudson.plugins.mercurial.MercurialSCM" plugin="mercurial@1.50"> (Default) http://host/path/project BRANCH stable true "hudson.plugins.mercurial.browser.HgWeb"> http://host/path/project/ false triggers: H 3 * * 1-6 false Project: Jenkins Priority: Major Reporter: Rick Oosterholt 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.
