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

['Jesse Glick' via Jenkins Developers]

On Sun, Dec 10, 2023 at 12:09 PM Mark Waite 
wrote:

> Apply the label to the existing pull request and then run the cd action
> from the "Actions" menu of the repository.
>
> That's worked for me in the past.
>

Please update
https://www.jenkins.io/doc/developer/publishing/releasing-cd/#releasing if
anything seems to be missing or unclear.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0G-%2BZOtN_1eKBhsNRxKwJZwnE0oEV-QNQbRd3pmy_C_A%40mail.gmail.com.

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

[tzach solomon]

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 existing pull request and then run the cd action
> from the "Actions" menu of the repository.
>
> That's worked for me in the past.
>
> Mark Waite
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/9a455bf0-5e5d-480e-a99c-14ea8b4eb96dn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAC19wgJQX8vPgF0MvPgUjUTw7P87zcwp55F0efk_iREkxPB-bg%40mail.gmail.com.

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

[Mark Waite]

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 for me in the past.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9a455bf0-5e5d-480e-a99c-14ea8b4eb96dn%40googlegroups.com.

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

[tzach solomon]

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
> "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 minimum required Jenkins version is not considered to be a
> breaking change.
>
> On Sunday, December 10, 2023 at 8:34:01 AM UTC-7 tzach@gmail.com
> wrote:
>
>> 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 this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/46e078a2-0dcd-4903-8651-8702c5257128n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAC19wgKxXuAPB%3DQcLWjdWzpQ2xE_PkQtmHSmr8FR7ucYeSe9eg%40mail.gmail.com.

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

[Mark Waite]

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 minimum required Jenkins version is not considered to be a 
breaking change.

On Sunday, December 10, 2023 at 8:34:01 AM UTC-7 tzach@gmail.com wrote:

> 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 this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/46e078a2-0dcd-4903-8651-8702c5257128n%40googlegroups.com.

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

[tzach solomon]

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 this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAC19wgLAL8fQn4sX79kmLjoY-FacmR2xJCmsbPo4kxLUA1sHHw%40mail.gmail.com.