Hi Chad, I'm also having similar problem with one of our template, which uses package repository as material. I'm able to see proper version when I look at check connection in package repositories. but it's not showing the latest revision in material when I run the pipelines. I tried auto update true and manual trigger poll but no luck.
Could you please help me here ? Regards, Rajasekhar On Tuesday, 22 March 2022 at 06:01:43 UTC+5:30 [email protected] wrote: > Hello Chad, > > I went to the materials page, 'refreshed', and triggered, and this > surprisingly worked. I am using Bitbucket Cloud and GoCD version 21.3.0. > Once more pushes are made I'll see if I need to re-visit that materials > page, though I think it should work fine now. Also your two alternatives > are interesting; I might implement one of them in the future. Thank you for > your help! > > -Josh > > On Sunday, March 20, 2022 at 3:30:12 AM UTC-7 Chad Wilson wrote: > >> Hi Joshua >> >> I'm not really sure what could be going on here - I believe triggering a >> manual run (**without* "trigger with options") *should* cause it to also >> check the material for the latest revision, so I think something else is >> possibly going on here with configuration or Bitbucket. >> >> Is this Bitbucket Server or Bitbucket Cloud? Which GoCD version? What do >> the GoCD server logs say when you are triggering? >> >> Does the material show the correct (latest) revision on the "Materials" >> tab? Does it behave any differently if you "refresh" the material in the >> Materials tab before doing a manual trigger? >> >> Depending on your reason for using manual triggers (and likely not >> getting at the root of the problem unfortunately) a couple of other >> alternatives might be >> >> - re-enable regular polling, but add a **/* denylist to the other >> pipelines, so it ignores the changes by default >> - trick GoCD into thinking there are two different materials, >> possibly by using different capitalization of the domain name in the >> material - see if it works as expected then >> >> >> -Chad >> >> * By default trigger with options will run with the most recent run >> revision; you have to override it to trigger with the latest revision by >> selecting the revision from the dropdown. >> >> On Sun, Mar 20, 2022 at 2:31 AM Joshua von Damm <[email protected]> >> wrote: >> >>> I have a git repo on Bitbucket that is a material on my pipeline. This >>> repo is a material on several pipelines with the setting: 'Fetch updates >>> to this repository only on webhook or manual trigger', so I can't change my >>> one pipeline to the setting: ' Regularly fetch updates to this repository'. >>> >>> This would be fine if manual triggering worked. However after pushing to >>> that repo, manually running the pipeline doesn't get the latest revision on >>> that material. It can take days until I see that revision. >>> >>> How do I get it to see the latest revision? As this material is used on >>> multiple pipelines, could one be designated as the 'master' that I have to >>> manually trigger? >>> >>> Thanks! >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "go-cd" 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/go-cd/7e8c010b-9631-4503-99d6-d35f033a125an%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/go-cd/7e8c010b-9631-4503-99d6-d35f033a125an%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "go-cd" 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/go-cd/5858e5f6-dfc6-444a-8f06-1f63fecc0ca1n%40googlegroups.com.
