| Issue 3530: | Gerrit forge is porbably sending wrong tirgger | |
| 2 people starred this issue and may be notified of changes. | Back to list |
***************************************************************** ***** ***** ***** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!! ***** ***** ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, CYANOGENMOD, ***** ***** INTERNAL ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.***** ***** ***** ***** THOSE ISSUES BELONG IN DIFFERENT ISSUE TRACKERS ***** ***** ***** ***************************************************************** Affected Version: What steps will reproduce the problem? 1. Re trigger the commit on https://eis-jenkins-buci-ducn-ihw-athena-staging.rnd.ki.sw.ericsson.se/job/sike-fw-test/7/console and ensure in cosole loggs that Jenkins has checkedout correct patchset 2. 3. What is the expected output? What do you see instead? We were expeting that Jenkins will recive a trigger that will point to latest Patchset, instead Jenking is receving a trigger for an old commit which is already submitted. Please provide any additional information below. We have noticed that Gerrit forge is sending wrong trigger info to jeninks. If you consult console traces on https://eis-jenkins-buci-ducn-ihw-athena-staging.rnd.ki.sw.ericsson.se/job/sike-fw-test/7/console . you will notice that instead of sending patchset with SHA-1 a34b65869bbcb9288ac7f6e9cb642516232bb846, somehow gerritforge is sending out really old SHA-1 id which has been submitted on April the 19th https://gerritforge.lmera.ericsson.se/gerrit/gitweb?p=athena-csm1-fw.git;a=commit;h=aadd06eea5673257e6113ad398618dfb11b4343f Patchset that we have submitted in Gerritforge https://gerritforge.lmera.ericsson.se/gerrit/#/c/174659/ Trigger received by Jenkins server https://eis-jenkins-buci-ducn-ihw-athena-staging.rnd.ki.sw.ericsson.se/job/sike-fw-test/7/
Aug 24, 2015
Project Member
#1
huga...@gmail.com
Status:
Invalid
|
|
| ► Sign in to add a comment |