[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine

Thu, 15 Nov 2012 16:31:47 -0800

I have found the cause of this behaviour - change log disappears if in SCM config of job "Show all CVS output" is checked to yes. As soon as I uncheck "Show all CVS output" I cant see any changes in the change log.

I reckon what’s happening CVS update stdout is redirected to log if the box is checked otherwise CVS update stdout is getting parsed and chages are stripped off from cvs update log and put in the changelog. This is not the right behaviour as one expects verbose CVS update command with stdout & stderr as is in the log without being doctored to reflect the true picture as well as the changes in the change log if you are checking show all cvs output box.

I am building a build pipeline for CI & deployment from dev -> test -> uat -> staging -> prod for a legacy app COBOL where each component is compiled to its own binary (i.e. for every foo.cbl there is foo.so) unlike Java where entire workspace is compiled & package to a monolithic binary (.ear or .war etc). It's a component driven migration where there is need to compile only the programs updated by cvs and packaging only the updated components their corresponding binaries. For this I need to pass list of CVS updated components which I can get from CVS update log and pass it to the build script. I was hoping to see them as args passed to Shell in '$*' in post build but nothing there, as I think Jenkins concept is compile the entire workspace not a component driven migration.

Also noticed that the warnings of warnings of cvs command are not displayed in the log regardless of box checked or not. Warnings of CVS update are important for situations where lot of components of repository becomes obsolete and you remove tag e.g PROD from them in cvs, next update will remove the obsoleted sources from the filesystem but you still need to know what sources are removed from the filesystem to delete components dependencies and binaries from the filesystem as they are not checked in CVS generally.

eg. cvs update: warning: srcmgr/logs/blah.log is not (any longer) pertinent

Long story short we should be able to see cvs update stdout/stderr as is returned by Shell in the log in verbose mode and needless to say changes in the change log.
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

Reply via email to