We figured out this issue. If the git URL used for the pipeline jenkinsFile and the checkout command in the jenkinsFile are exactly the same then we get the warning: Pipeline] echo <https://bvgscm-jenkins2.broadcom.net/job/BCM1000/job/F2/job/publish_regress_full/89/console#> Warning, empty changelog. Have you run checkout?
By simply adding username@ to the url which matches the user name specified in the credentialsId in one of the checkouts the warning goes away and we see changes. This seems like a bug to me? Where should it be reported? On Monday, February 14, 2022 at 2:13:42 PM UTC-8 jimsearle wrote: > > Our pipeline job using Gerrit was working, but the checkout area was > removed so the next job run recreated it and now all runs show: > > [Pipeline] echo > <https://bvgscm-jenkins2.broadcom.net/job/BCM1000/job/F2/job/publish_regress_full/89/console#> > > Warning, empty changelog. Have you run checkout? > > I've run a few changes thru with publish and submit but Jenkins keeps > saying the changelog is empty. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a9709a16-f42f-4f2a-b57d-82e87565ac3cn%40googlegroups.com.
