[JIRA] (JENKINS-15872) Running 'rlog' after 'cvs up -r TAG' superfluous giving incorrect change log for the workspace
Akhil Mittal updated JENKINS-15872 Running rlog after cvs up -r TAG superfluous giving incorrect change log for the workspace Change By: Akhil Mittal (22/Nov/12 12:11 AM) Priority: Major Blocker 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Change By: Akhil Mittal (22/Nov/12 12:12 AM) Priority: Major Blocker 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
[JIRA] (JENKINS-15872) Running 'rlog' after 'cvs up -r TAG' superfluous giving incorrect change log for the workspace
Akhil Mittal updated JENKINS-15872 Running rlog after cvs up -r TAG superfluous giving incorrect change log for the workspace Please note that head has moved since then to 1.23 Change By: Akhil Mittal (20/Nov/12 9:09 PM) Attachment: rlog.txt 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
[JIRA] (JENKINS-15872) Running 'rlog' after 'cvs up -r TAG' superfluous giving incorrect change log for the workspace
Akhil Mittal created JENKINS-15872 Running rlog after cvs up -r TAG superfluous giving incorrect change log for the workspace Issue Type: Bug Assignee: Unassigned Components: cvs Created: 19/Nov/12 9:36 PM Description: Is running 'rlog' after 'cvs up -r TAG' ok? Don't think so If you are selecting 'Location' as Tag e.g. Location : Tag Tag Name : DEV cvs commands run by Jenkins will be something like cvs update -d -r DEV blah_module cvs rlog -S -d'19 Nov 2012 11:43:30 +110019 Nov 2012 11:47:37 +1100' blah_module What if the tag DEV on component/module has not moved but several versions are committed to cvs? In this case what's happening is your workspace is not changed still has got the old components with 'DEV' tag revisions however change log will show the committed changes 'cos of rlog. I'll try to explain 1. Notice foo.bar 'DEV' tag is not at head cvs log srcmgr/test/someDir/foo.bar | egrep 'head:|DEV:' head: 1.15 DEV: 1.5 2. I committed a change cvs commit -m 'test' srcmgr/test/someDir/foo.bar Checking in srcmgr/test/someDir/foo.bar; /cvs/srcmgr/test/someDir/foo.bar,v -- foo.bar new revision: 1.16; previous revision: 1.15 3. Notice that even though I have committed a change but my tag 'DEV' is not moved at all cvs log srcmgr/test/someDir/foo.bar | egrep 'head:|DEV:' head: 1.16 DEV: 1.5 4. Now my Jenkins settings is 'Location: tag', 'tag: DEV' 'Update: ticked' Run Jenkins Building in workspace /export/home/amittal/temp cvs update -d -P -r DEV srcmgr cvs update: Updating srcmgr cvs update: Updating srcmgr/adhoc cvs update: Updating srcmgr/cm cvs update: Updating srcmgr/cm/bin cvs update: Updating srcmgr/logs cvs update: Updating srcmgr/test cvs update: Updating srcmgr/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs update: Updating srcmgr/test/someDir cvs rlog -S -d19 Nov 2012 15:42:34 +110019 Nov 2012 15:51:08 +1100 srcmgr cvs rlog: Logging srcmgr cvs rlog: Logging srcmgr/adhoc cvs rlog: Logging srcmgr/cm cvs rlog: Logging srcmgr/cm/bin cvs rlog: Logging srcmgr/logs cvs rlog: Logging srcmgr/test cvs rlog: Logging srcmgr/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs rlog: Logging srcmgr/test/someDir temp $ /bin/sh -xe /var/tmp/hudson5023473001197182858.sh + pwd /export/home/amittal/temp Notifying upstream projects of job completion Finished: SUCCESS 5. Jenkins displayed the committed change in the change log Changes Summary test amittal: test 1.16 srcmgr/test/someDir/foo.bar cat changelog.xml ?xml version="1.0" encoding="UTF-8"? changelog entry changeDate2012-11-19 04:49:26/changeDate author![CDATAamittal]/author file name![CDATAsrcmgr/test/someDir/foo.bar]/name fullName![CDATA/cvs/srcmgr/test/someDir/foo.bar]/fullName revision1.16/revision /file msg![CDATAtest]/msg /entry /changelog 6. Now this is the problem what's happening here is since we are running 'cvs up -r DEV' and the tag DEV is not moved my workspace is still at old revision, no update (in this case 1.5) cvs log srcmgr/test/someDir/foo.bar | egrep 'head:|DEV:' head: 1.16 DEV: 1.5 However since we are running 'rlog' and a commit happened it shows that in change log whereas in my workspace there is no change to build. Therefore I think if we are running 'cvs up/co' with '-r TAG' option, running 'rlog' after that to determine change log for workspace is superfluous/not correct. As change log in this case should be determined by the TAG move not by commits. Project: Jenkins Priority: Major Reporter: Akhil Mittal
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Yep I have raised JENKINS-15872 for that now, any update on this one. 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Just letting you know that even with 'Show all CVS Output' ticked on CVS plugin 2.7 no change log is displayed, however with 2.4 it displays the change log if 'Show all CVS Output' is ticked. I haven't checked 2.5 2.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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Change By: Akhil Mittal (15/Nov/12 9:36 PM) Attachment: Jenkins_console_build17_out.txt 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Change By: Akhil Mittal (15/Nov/12 9:37 PM) Attachment: rlog_of_solaris_cli.txt 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Change By: Akhil Mittal (15/Nov/12 9:37 PM) Attachment: Jenkins_console_build17_out.txt 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Attached 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Change By: Akhil Mittal (16/Nov/12 12:28 AM) Attachment: screen_shot.doc 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal reopened JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Hi, I am still getting this issue where I am seeing no changes in change log it updated my workspace though rlog command works fine on Solaris CLI as. My set up is Jenkins ver. 1.488 CVS plugin I tried both latest 2.7 2.4 no luck My Project job configuration for SCM is location: Tag Tag name: DEV Use Update is checked (yes) Basically I want Jenkins to kick of build job if there are any updates to a particular tag in this case DEV, which works fine with this scheme for my workspace but the change is not reflected in change log. Console output cvs checkout -r DEV -d temp srcmgr cvs checkout: Updating temp cvs checkout: Updating temp/adhoc cvs checkout: Updating temp/cm cvs checkout: Updating temp/cm/bin cvs checkout: Updating temp/logs cvs checkout: Updating temp/test U temp/test/someotheFile cvs checkout: Updating temp/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs checkout: Updating temp/test/someDir U temp/test/someDir/foo.bar Using locally configured password for connection to :pserver:amittal@melcvs01:/cvs cvs rlog -S -d15 Nov 2012 15:24:35 +110015 Nov 2012 15:39:59 +1100 srcmgr cvs rlog: Logging srcmgr cvs rlog: Logging srcmgr/adhoc cvs rlog: Logging srcmgr/cm cvs rlog: Logging srcmgr/cm/bin cvs rlog: Logging srcmgr/logs cvs rlog: Logging srcmgr/test cvs rlog: Logging srcmgr/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs rlog: Logging srcmgr/test/someDir It updates my workspace however there is nothing in the change log or changes in Jenkins, whereas I can run rlog on Solaris CLI cvs rlog -S -d'15 Nov 2012 15:24:35 +110015 Nov 2012 15:39:59 +1100' srcmgr cvs rlog: Logging srcmgr cvs rlog: Logging srcmgr/adhoc cvs rlog: Logging srcmgr/cm cvs rlog: Logging srcmgr/cm/bin cvs rlog: Logging srcmgr/logs cvs rlog: Logging srcmgr/test RCS file: /cvs/srcmgr/test/someotheFile,v head: 1.3 branch: locks: strict access list: symbolic names: TAGINFO: 1.1 SOURCE_CONTROL: 1.1 QA: 1.1 PRODSTAGE: 1.1 PRODBUILD: 1.1 PRODFIX: 1.1 SITPR1: 1.1 UATPR1: 1.1 TESTGAP: 1.1 TESTMIG: 1.1 TRNG: 1.1 HUGO: 1.1 DEVGAP: 1.1 DEVMIG2: 1.1 DEVMIG: 1.1 DEV: 1.3 keyword substitution: kv total revisions: 3; selected revisions: 1 description: revision 1.2 date: 2012/11/15 04:39:21; author: amittal; state: Exp; lines: +1 -0 empty log message *** = cvs rlog: Logging srcmgr/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs rlog: Logging srcmgr/test/someDir Change log is empty /export/home/amittal/.jenkins/jobs/Akhil/builds/17 cat changelog.xml ?xml version="1.0" encoding="UTF-8"? changelog /changelog TIA Akhil Change By: Akhil Mittal (15/Nov/12 5:29 AM) Resolution: Fixed 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
