[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title
Robert Pitt edited a comment on JENKINS-52661
Re: P4 Plugin fails to parse changelog
Note we're still suffering from this in a number of jobs.Some additional context, the file in question invariably looks perfectly but with 0 changes (valid/expected) :{noformat}{noformat}We're using it in a pipeline job which does multiple checkouts (we have multiple p4 servers).I'm not sure we've ever seen it in a job which does a single checkout from one server.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-52661) P4 Plugin fails to parse changelog
Title: Message Title Robert Pitt commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog Note we're still suffering from this in a number of jobs. Some additional context, the file in question invariably looks perfectly but with 0 changes: We're using it in a pipeline job which does multiple checkouts (we have multiple p4 servers). I'm not sure we've ever seen it in a job which does a single checkout from one server. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Robert Pitt commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 As another Windows/.NET organisation the move to XML 1.1 has impacting us as well. After a google it seems that XML 1.1 is not well supported; moving Jenkins to 1.1 is regrettable. Realistically though I don't imagine this change to be rolled back, we're going to have to hack our code. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46902) Double Byte Order Mark - UTF8
Title: Message Title Robert Pitt edited a comment on JENKINS-46902 Re: Double Byte Order Mark - UTF8 Similar problem but in the opposite direction ; there is a lot of pain and error in the way utf8 has been introduced/supported . The change in behaviour dependant upon client/plugin version has caused much confusion... however right now things are definitely broken/wrong as the latest plugin behaves differently from the latest client, and possible the server being in unicode mode further changes things. Please also JENKINS-49141 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46902) Double Byte Order Mark - UTF8
Title: Message Title Robert Pitt edited a comment on JENKINS-46902 Re: Double Byte Order Mark - UTF8 Similar problem but in the opposite direction ; there is in JENKINS-49141There has been a lot of pain and error in the way utf8 has been introduced/supported.The change in behaviour dependant upon client/plugin version has caused much confusion... however right now things are definitely broken/wrong as the latest plugin behaves differently from the latest client, and possible the server being in unicode mode further changes things. Please also JENKINS-49141 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46902) Double Byte Order Mark - UTF8
Title: Message Title Robert Pitt commented on JENKINS-46902 Re: Double Byte Order Mark - UTF8 Similar problem but in the opposite direction. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-25995) Cannot find function querySelectorAll while running HtmlUnit tests
Title: Message Title Robert Pitt edited a comment on JENKINS-25995 Re: Cannot find function querySelectorAll while running HtmlUnit tests If any experts in maven/Jenkins know of a way to coerce/hack the system to use newer versions of HtmlUnit whilst still building against * older * Jenkins cores, please speak up!Alternatively I wonder if there's a way for us to hide the offensive method from the HtmlUnit browser somehow \(?) 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-25995) Cannot find function querySelectorAll while running HtmlUnit tests
Title: Message Title Robert Pitt commented on JENKINS-25995 Re: Cannot find function querySelectorAll while running HtmlUnit tests If any experts in maven/Jenkins know of a way to coerce/hack the system to use newer versions of HtmlUnit whilst still building against older Jenkins cores, please speak up! Alternatively I wonder if there's a way for us to hide the offensive method from the HtmlUnit browser somehow (?) 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-37094) log noise/spam 'Unable to guess repository browser.' if used on a server without Swarm.
Title: Message Title Robert Pitt created an issue Jenkins / JENKINS-37094 log noise/spam 'Unable to guess repository browser.' if used on a server without Swarm. Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2016/Aug/01 2:16 PM Environment: p4-plugin 1.40 Priority: Minor Reporter: Robert Pitt The p4-plugin seems to generate noise/spam in the system log if used against a P4 server without the P4.Swarm.URL property set. INFO org.jenkinsci.plugins.p4.PerforceScm guessBrowser Unable to guess repository browser. Not having a Swarm URL is perfectly valid IMO, so this should be silent. Add Comment
