[JIRA] [mercurial-plugin] (JENKINS-25281) Mercurial plugin sometimes stalls when transferring bundle from master to slave
Kim Randell commented on JENKINS-25281 Mercurial plugin sometimes stalls when transferring bundle from master to slave We've had it happen one more time on a delta transfer. If/when it happens again I'll try to inspect the thread dumps on the master and slave and see if I can spot where FilePath.copyTo is getting stuck. 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-plugin] (JENKINS-9686) Mercurial polling does not expand parameters/tokens
Title: Message Title Kim Randell reopened an issue Reopened as I'm not sure if my previous comment has much visibility when the issue is closed. Jenkins / JENKINS-9686 Mercurial polling does not expand parameters/tokens Change By: Kim Randell Resolution: Fixed Status: Resolved Reopened 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-9686) Mercurial polling does not expand parameters/tokens
Title: Message Title Kim Randell commented on JENKINS-9686 Re: Mercurial polling does not expand parameters/tokens Would it be possible to fix this for Choice parameters as well as strings? This is often a more suitable and less error-prone way of parameterising branches. 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-30120) Plugin does not work with Mercurial 3.4.2
Title: Message Title
Kim Randell commented on JENKINS-30120
Re: Plugin does not work with Mercurial 3.4.2
There appears to be problem with Mercurial 3.4 even when the log command executes successfully. We are finding that the command returns a number of unwanted changesets (in our case ~2000 of them), apparently everything which is not an ancestor of the current branch head.
I tested this command manually and found that it returns the expected result for 3.3.3 and the extra results for 3.4 (and 3.6): hg log --rev :0 --follow --prune
The following command returns the desired results on 3.3.3, 3.4, and 3.6 hg log --rev "ancestors('')" --prune The single quotes around also fix the whitespace problem.
This is due to the following change: https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.4_.282015-05-01.29
log: make -fr show complete history from the given revs
https://selenic.com/pipermail/mercurial-devel/2015-March/066770.html
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-30120) Plugin does not work with Mercurial 3.4.2
Title: Message Title Kim Randell commented on JENKINS-30120 Re: Plugin does not work with Mercurial 3.4.2 Oh, I've just noticed that xavierzwirtz has already created a pull request with a fix for this. Linked it now. 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-30239) Choice parameters should be expanded in Mercurial polling
Title: Message Title Kim Randell created an issue Jenkins / JENKINS-30239 Choice parameters should be expanded in Mercurial polling Issue Type: Improvement Assignee: Jesse Glick Components: mercurial-plugin Created: 01/Sep/15 8:58 AM Environment: Windows Server 2012 Jenkins ver. 1.607 Mercurial plugin 1.52 Priority: Minor Reporter: Kim Randell In the fix for JENKINS-9686 (this changeset: https://github.com/jenkinsci/mercurial-plugin/commit/7d5b7d52221b55e7cb6bee5ae280bb3ecd2ffe9f), functionality for expanding String parameters was added to the Mercurial polling code. I would like to be able to use Choice parameters as well, as this is often a more suitable and less error-prone way of parameterising branches.
[JIRA] (JENKINS-52979) User-specified changelog size limit
Title: Message Title Kim Randell created an issue Jenkins / JENKINS-52979 User-specified changelog size limit Issue Type: New Feature Assignee: Unassigned Components: mercurial-plugin Created: 2018-08-10 11:01 Priority: Minor Reporter: Kim Randell We have a similar problem to the one that celltestr reported in JENKINS-16654. However, we would prefer to retain changelogs when the builds are incremental, while disabling them when switching branch or building after a long gap. Therefore, it would be useful if we could specify a size limit on the changelog (for instance, maximum number of changesets). When the size limit is reached, the changelog would be truncated (perhaps with a summary noting the total original size). Add Comment
[JIRA] (JENKINS-52979) User-specified changelog size limit
Title: Message Title Kim Randell updated an issue Jenkins / JENKINS-52979 User-specified changelog size limit Change By: Kim Randell Labels: mercurial 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-52979) User-specified changelog size limit
Title: Message Title Kim Randell updated an issue Jenkins / JENKINS-52979 User-specified changelog size limit Change By: Kim Randell Labels: mercurial performance 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-56026) Add previous revision to environment variables for Mercurial
Title: Message Title Kim Randell created an issue Jenkins / JENKINS-56026 Add previous revision to environment variables for Mercurial Issue Type: Improvement Assignee: Unassigned Components: mercurial-plugin Created: 2019-02-07 15:21 Labels: mercurial Priority: Minor Reporter: Kim Randell The git plugin provides the following environment variables: GIT_PREVIOUS_COMMIT: The hash of the commit last built on this branch, if any. GIT_PREVIOUS_SUCCESSFUL_COMMIT: The hash of the commit last successfully built on this branch, if any. It would be useful if the mercurial plugin provided the same information, e.g. MERCURIAL_PREVIOUS_REVISION: Full ID of revision last built on this job. MERCURIAL_PREVIOUS_SUCCESSFUL_REVISION: Full ID of revision last successfully built on this job. Add Comment
[JIRA] (JENKINS-56026) Add previous revision to environment variables for Mercurial
Title: Message Title Kim Randell updated JENKINS-56026 Pull request declined. https://github.com/jenkinsci/mercurial-plugin/pull/124 Jenkins / JENKINS-56026 Add previous revision to environment variables for Mercurial Change By: Kim Randell Status: Open Fixed but Unreleased Assignee: Kim Randell Resolution: Won't 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-56026) Add previous revision to environment variables for Mercurial
Title: Message Title Kim Randell updated JENKINS-56026 Jenkins / JENKINS-56026 Add previous revision to environment variables for Mercurial Change By: Kim Randell Resolution: Won't Fix Status: Fixed but Unreleased 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56026) Add previous revision to environment variables for Mercurial
Title: Message Title Kim Randell updated JENKINS-56026 Jenkins / JENKINS-56026 Add previous revision to environment variables for Mercurial Change By: Kim Randell Status: Reopened Fixed but Unreleased Resolution: Won't Do 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-3225) Hyperlink URLs in JUnit output
Title: Message Title Kim Randell commented on JENKINS-3225 Re: Hyperlink URLs in JUnit output Jesse Glick Was this lost in the conversion to a plugin? It doesn't seem to work any more. 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.133298.123618976.10500.1571407980207%40Atlassian.JIRA.
[JIRA] (JENKINS-3225) Hyperlink URLs in JUnit output
Title: Message Title Kim Randell commented on JENKINS-3225 Re: Hyperlink URLs in JUnit output Just noticed that it does work correctly when viewing the individual test, but not when expanding All Failed Tests from the main Test Report. I'll report that as a new issue. 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.133298.123618976.10527.1571410200212%40Atlassian.JIRA.
[JIRA] (JENKINS-59846) Hyperlink URLs in JUnit Test Report
Title: Message Title Kim Randell created an issue Jenkins / JENKINS-59846 Hyperlink URLs in JUnit Test Report Issue Type: Improvement Assignee: Unassigned Attachments: url.xml Components: junit-plugin Created: 2019-10-18 15:27 Environment: Windows Server 2012 Jenkins 2.176.4 JUnit 1.28 Priority: Minor Reporter: Kim Randell Adding a URL to JUnit output will automatically hyperlink in the page for the individual test (see https://issues.jenkins-ci.org/browse/JENKINS-3225 ). However, it does not get linked for the Test Report page when expanding the failure. Steps to reproduce: Create a Freestyle job with url.xml in the workspace In the build steps, touch url.xml In Post-Build Actions, add Publish JUnit test result report with Test Result XMLs as *.xml Run job Go to Test Results Expand All Failed Tests URL is not hyperlinked. Click test name link to go to test page. URL is hyperlinked.
[JIRA] (JENKINS-58369) xUnit Plugin problem with Boost test XML output that contains messages
Title: Message Title Kim Randell commented on JENKINS-58369 Re: xUnit Plugin problem with Boost test XML output that contains messages This comes from this line: https://github.com/jenkinsci/xunit-plugin/blob/5f017f9da41e987f3644c65f10658660519abfe5/src/main/resources/org/jenkinsci/plugins/xunit/types/boosttest-1.2-to-junit-4.xsl#L176 Note that $elt/@file is only populated if the TestCase element has a first child with a file attribute (line 172). Therefore, if there is a message or assertion failure in the test, classname is the suite name concatenated with the filename (minus extension), otherwise it is just the suite name. It's unclear to me why the filename should be used in the classname in any case. 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.200485.1562435124000.7149.1571067120264%40Atlassian.JIRA.
