Re: bitbucket-plugin - why didn't my PR got released

Thanks Mark! Worked as a charm! :) Tzach On Sun, Dec 10, 2023, 18:09 Mark Waite wrote: > > > On Sunday, December 10, 2023 at 10:04:17 AM UTC-7 Tzach wrote: > > Thanks Mark as always :) > > Is there a way to "fix" the current PR or should I create a new one? > > > Apply the label to the

Re: bitbucket-plugin - why didn't my PR got released

On Sunday, December 10, 2023 at 10:04:17 AM UTC-7 Tzach wrote: Thanks Mark as always :) Is there a way to "fix" the current PR or should I create a new one? Apply the label to the existing pull request and then run the cd action from the "Actions" menu of the repository. That's worked

Re: bitbucket-plugin - why didn't my PR got released

Thanks Mark as always :) Is there a way to "fix" the current PR or should I create a new one? Tzach On Sun, Dec 10, 2023, 17:23 Mark Waite wrote: > The change detector inside the continuous delivery step is checking the > labels on the pull request. That pull request is not labeled. It has

Re: bitbucket-plugin - why didn't my PR got released

The change detector inside the continuous delivery step is checking the labels on the pull request. That pull request is not labeled. It has "BREAKING CHANGE" in the title, but does not have a label. I think that you want the label "developer" rather than "breaking", since changing the

bitbucket-plugin - why didn't my PR got released

Hi all, I've labeled my PR-97 with "BREAKING CHANGE:" but it was not released. What am I missing? Thanks, Tzach -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from