Critical When using p4 plugin version 1.7.4, changes are shown correctly.
In more recent versions of the plugin, "No changes" is always reported (both in the project view when selecting Recent Changes and in the build view).
I double-checked the changelog.xml and it is not empty.
Insofar I understand, it is the SCM plugin which parses the changelog.xml ?
A slightly redacted version of the changelog.xml (strings 'anonymized' to either 'abc' or 'xyz'):
<?xml version='1.0' encoding='UTF-8'?> <changelog> <entry> <changenumber><changeInfo>4171234</changeInfo> <clientId>abc_xyz</clientId> <msg>abc->xyz [4170123]: abcxyz </msg> <changeUser>abc</changeUser> <changeTime>2018-01-08 16:17:48</changeTime> <shelved>false</shelved> <files> <file endRevision="#42" action="EDIT" depot="%2F%2Fdepot%2Fabc%2Fabc%2Fabc%2Fabc%2Fxyz.xml" /> <file endRevision="#560" action="EDIT" depot="%2F%2Fdepot%2Fabc%2Fabc%2Fabc%2Fabc%2Fabc%2Fabc%2Fabc%2Fabc.dita" /> </files> <jobs> </jobs> </changenumber> </entry> </changelog>
[JENKINS-48845] Recent Changes / changelog not shown correctly by P4 Plugin
One way to fix this backwards-compatibility issue might be to harden lines 72-77 in P4ChangeParser for backwards compatibility, from the current :
if (browser == null) { String url = p4.getSwarm(); if (url != null) { this.browser = new SwarmBrowser(url); } }
into :
if (browser == null) { try { String url = p4.getSwarm(); if (url != null) { this.browser = new SwarmBrowser(url); } } catch(RequestException re) { if(re.getMessage() != null && !re.getMessage().contains("Unknown command")) { throw re; } // else : Ignore, the command is not supported by older versions } }
I forked p4-plugin, fixed and created a pull request
I tested by applying this fix to a 1.8.4 release tarball, building and deploying on our production system, where it works nicely.
Paul Allen
added a comment - Hi Philip,
Great work, thank you for the PR - I'll get that merged in.
It looks like the 'p4 property' command used by Swarm to get the URL is the issue (it was introduced in 2013.1). Is there anything we could do to help with the upgrade? 2012.1 is kind of old.
Kind regards,
Paul
Paul Allen
added a comment - Hi Philip,
Great work, thank you for the PR - I'll get that merged in.
It looks like the 'p4 property' command used by Swarm to get the URL is the issue (it was introduced in 2013.1). Is there anything we could do to help with the upgrade? 2012.1 is kind of old.
Kind regards,
Paul Hi Paul,
Thanks for the quick turnaround, I'm looking forward to the next release.
I'm not responsible for maintaining our P4 servers. I was in touch with our P4 team, and they are planning the upgrade, but apparently the situation is non-trivial, so it might take some time.
Best regards,
Philip
Paul Allen
added a comment - Ready for release. Paul Allen
added a comment - Released in 1.8.5 
Roberta T guo
added a comment - We are using P4 pluginin v1.8.7. In jenkins.log, we saw a lot of such exceptions threw when the plugin executed silently in Jenkin master for the SCM-perforce related jobs, even they are not running and even was disabled. Sometimes when there are many Jenkins jobs are triggered, this could cause the 'java.lang.OutOfMemoryError: GC overhead limit exceeded' error in Jenkins master.
How should we workaround this issus? Is this a direct cause for our Jenkins went dead today?
Thanks
Roberta T guo
added a comment - We are using P4 pluginin v1.8.7. In jenkins.log, we saw a lot of such exceptions threw when the plugin executed silently in Jenkin master for the SCM-perforce related jobs, even they are not running and even was disabled. Sometimes when there are many Jenkins jobs are triggered, this could cause the 'java.lang.OutOfMemoryError: GC overhead limit exceeded' error in Jenkins master.
How should we workaround this issus? Is this a direct cause for our Jenkins went dead today?
Thanks
Found these issues (repeated many times) in jenkins.log, which almost certainly are about this case. The 'unknown command' seems to point to an issue with older server versions (we're running at 2012.1, an upgrade is apparently planned this year).
My guess is that ConnectionHelper.getSwarm(ConnectionHelper.java:597) is not supported by 2012.1 and will always fail.
--------- Issue 1 ----------
--------- Issue 2 ----------