Re: bitbucket-plugin - release is not published

[Mark Waite]

I think that we used release drafter and Gavin's hackathon style tool 
in https://www.youtube.com/watch?v=iUlRnNcqQA8

On Saturday, February 26, 2022 at 12:13:09 PM UTC-7 tzach@gmail.com 
wrote:

> Thank you all! :)
> This community is amazing! :)
>
> - Tzach
>
> On Sat, Feb 26, 2022 at 8:05 PM Adrien Lecharpentier <
> adrien.lec...@gmail.com> wrote:
>
>> You can also see the labels used in Release Drafter for the Jenkins 
>> project here: 
>> https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml
>>
>> Le sam. 26 févr. 2022 à 19:00, 'Gavin Mogan' via Jenkins Developers <
>> jenkin...@googlegroups.com> a écrit :
>>
>>> I used to have a little hackathon style tool that let you setup your 
>>> repo with the standards, but at some point it broke
>>>
>>> https://github.com/halkeye/plugins-self-service/blob/master/labels.yaml 
>>> is the list of official labels though, you might be able to use other ones, 
>>> but that list worked once
>>>
>>> On Sat, Feb 26, 2022 at 9:50 AM tzach solomon  
>>> wrote:
>>>
 Thank you Tim :)

 Is there a list of labels I need to choose from or I can label with 
 everything I want?



 On Sat, Feb 26, 2022, 6:15 PM Tim Jacomb  wrote:

> Yes you need to label them 
>
> On Sat, 26 Feb 2022 at 14:47, tzach solomon  
> wrote:
>
>> I see now from 
>> https://www.jenkins.io/doc/developer/publishing/releasing-cd/ that I 
>> might have missed something? Do I need to label my PRs?
>>
>> *Now whenever Jenkins reports a successful build of your default 
>> branch, and at least one pull request had a label indicating it was of 
>> interest to users (e.g., enhancement rather than chore), your component 
>> will be released to Artifactory and release notes published in GitHub.*
>>
>> On Sat, Feb 26, 2022 at 4:42 PM tzach solomon  
>> wrote:
>>
>>> Daniel, thank you for trying to help. I really do appreciate it!
>>>
>>> I've tried again now to release a new version to fix 
>>> https://issues.jenkins.io/browse/JENKINS-41635 but CI/CD does not 
>>> seem to want to release my version.
>>>
>>> What have I done?
>>>
>>>1. Created a branch in my fork at 
>>>https://github.com/tzachs/bitbucket-plugin
>>>2. Pushed the commit
>>>3. Merged back to https://github.com/jenkinsci/bitbucket-plugin
>>>
>>> At this point the CI started working and I followed it and saw the 
>>> following failure, 
>>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/PR-83/1/pipeline
>>> BUT, 
>>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/master/88/pipeline
>>>  
>>> passed.
>>>
>>> Also... from the Actions 
>>>  tab, I've 
>>> seen multiple CD runs (which I did not trigger), the last one is 
>>> https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1903327517
>>> .  
>>> I don't know why release is not being performed? (shrugged)
>>>
>>> Can someone please help?
>>>
>>> On Tue, Feb 8, 2022 at 3:40 PM 'Daniel Beck' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>


 On Tue, Feb 8, 2022 at 1:25 PM tzach solomon  
 wrote:

> Thanks Daniel (AGAIN! :)
>
> Can you please point me out what to read in order to fix these 
> issues?
> On what did it fail?
> [image: image.png]
>
>
> This checks the "status" of the commit to be released as reported 
 by CI. It looks like if, at the time this action was run, something 
 was 
 wrong. You can see the script doing this at 
 https://github.com/jenkins-infra/verify-ci-status-action/blob/master/run.sh
  
 and I think we went into the block at line 42, so line 37 failed.


 -- 
 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-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.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-de...@googlegroups.com.
>> To view this discussion on the web 

Re: bitbucket-plugin - release is not published

[tzach solomon]

Thank you all! :)
This community is amazing! :)

- Tzach

On Sat, Feb 26, 2022 at 8:05 PM Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> wrote:

> You can also see the labels used in Release Drafter for the Jenkins
> project here:
> https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml
>
> Le sam. 26 févr. 2022 à 19:00, 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> a écrit :
>
>> I used to have a little hackathon style tool that let you setup your repo
>> with the standards, but at some point it broke
>>
>> https://github.com/halkeye/plugins-self-service/blob/master/labels.yaml
>> is the list of official labels though, you might be able to use other ones,
>> but that list worked once
>>
>> On Sat, Feb 26, 2022 at 9:50 AM tzach solomon 
>> wrote:
>>
>>> Thank you Tim :)
>>>
>>> Is there a list of labels I need to choose from or I can label with
>>> everything I want?
>>>
>>>
>>>
>>> On Sat, Feb 26, 2022, 6:15 PM Tim Jacomb  wrote:
>>>
 Yes you need to label them

 On Sat, 26 Feb 2022 at 14:47, tzach solomon 
 wrote:

> I see now from
> https://www.jenkins.io/doc/developer/publishing/releasing-cd/ that I
> might have missed something? Do I need to label my PRs?
>
> *Now whenever Jenkins reports a successful build of your default
> branch, and at least one pull request had a label indicating it was of
> interest to users (e.g., enhancement rather than chore), your component
> will be released to Artifactory and release notes published in GitHub.*
>
> On Sat, Feb 26, 2022 at 4:42 PM tzach solomon 
> wrote:
>
>> Daniel, thank you for trying to help. I really do appreciate it!
>>
>> I've tried again now to release a new version to fix
>> https://issues.jenkins.io/browse/JENKINS-41635 but CI/CD does not
>> seem to want to release my version.
>>
>> What have I done?
>>
>>1. Created a branch in my fork at
>>https://github.com/tzachs/bitbucket-plugin
>>2. Pushed the commit
>>3. Merged back to https://github.com/jenkinsci/bitbucket-plugin
>>
>> At this point the CI started working and I followed it and saw the
>> following failure,
>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/PR-83/1/pipeline
>> BUT,
>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/master/88/pipeline
>> passed.
>>
>> Also... from the Actions
>>  tab, I've
>> seen multiple CD runs (which I did not trigger), the last one is
>> https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1903327517
>> .
>> I don't know why release is not being performed? (shrugged)
>>
>> Can someone please help?
>>
>> On Tue, Feb 8, 2022 at 3:40 PM 'Daniel Beck' via Jenkins Developers <
>> jenkinsci-dev@googlegroups.com> wrote:
>>
>>>
>>>
>>> On Tue, Feb 8, 2022 at 1:25 PM tzach solomon <
>>> tzach.solo...@gmail.com> wrote:
>>>
 Thanks Daniel (AGAIN! :)

 Can you please point me out what to read in order to fix these
 issues?
 On what did it fail?
 [image: image.png]


 This checks the "status" of the commit to be released as reported
>>> by CI. It looks like if, at the time this action was run, something was
>>> wrong. You can see the script doing this at
>>> https://github.com/jenkins-infra/verify-ci-status-action/blob/master/run.sh
>>> and I think we went into the block at line 42, so line 37 failed.
>>>
>>>
>>> --
>>> 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/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.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/CAC19wg%2BVb0PLs42fa5T7aNSsP4JgZut5%3DZh1ij%2Be1FGaUpdDsQ%40mail.gmail.com
> 
> .
>
 --
 You received this 

Re: bitbucket-plugin - release is not published

[Adrien Lecharpentier]

You can also see the labels used in Release Drafter for the Jenkins project
here:
https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml

Le sam. 26 févr. 2022 à 19:00, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> I used to have a little hackathon style tool that let you setup your repo
> with the standards, but at some point it broke
>
> https://github.com/halkeye/plugins-self-service/blob/master/labels.yaml
> is the list of official labels though, you might be able to use other ones,
> but that list worked once
>
> On Sat, Feb 26, 2022 at 9:50 AM tzach solomon 
> wrote:
>
>> Thank you Tim :)
>>
>> Is there a list of labels I need to choose from or I can label with
>> everything I want?
>>
>>
>>
>> On Sat, Feb 26, 2022, 6:15 PM Tim Jacomb  wrote:
>>
>>> Yes you need to label them
>>>
>>> On Sat, 26 Feb 2022 at 14:47, tzach solomon 
>>> wrote:
>>>
 I see now from
 https://www.jenkins.io/doc/developer/publishing/releasing-cd/ that I
 might have missed something? Do I need to label my PRs?

 *Now whenever Jenkins reports a successful build of your default
 branch, and at least one pull request had a label indicating it was of
 interest to users (e.g., enhancement rather than chore), your component
 will be released to Artifactory and release notes published in GitHub.*

 On Sat, Feb 26, 2022 at 4:42 PM tzach solomon 
 wrote:

> Daniel, thank you for trying to help. I really do appreciate it!
>
> I've tried again now to release a new version to fix
> https://issues.jenkins.io/browse/JENKINS-41635 but CI/CD does not
> seem to want to release my version.
>
> What have I done?
>
>1. Created a branch in my fork at
>https://github.com/tzachs/bitbucket-plugin
>2. Pushed the commit
>3. Merged back to https://github.com/jenkinsci/bitbucket-plugin
>
> At this point the CI started working and I followed it and saw the
> following failure,
> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/PR-83/1/pipeline
> BUT,
> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/master/88/pipeline
> passed.
>
> Also... from the Actions
>  tab, I've
> seen multiple CD runs (which I did not trigger), the last one is
> https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1903327517
> .
> I don't know why release is not being performed? (shrugged)
>
> Can someone please help?
>
> On Tue, Feb 8, 2022 at 3:40 PM 'Daniel Beck' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>>
>>
>> On Tue, Feb 8, 2022 at 1:25 PM tzach solomon 
>> wrote:
>>
>>> Thanks Daniel (AGAIN! :)
>>>
>>> Can you please point me out what to read in order to fix these
>>> issues?
>>> On what did it fail?
>>> [image: image.png]
>>>
>>>
>>> This checks the "status" of the commit to be released as reported by
>> CI. It looks like if, at the time this action was run, something was 
>> wrong.
>> You can see the script doing this at
>> https://github.com/jenkins-infra/verify-ci-status-action/blob/master/run.sh
>> and I think we went into the block at line 42, so line 37 failed.
>>
>>
>> --
>> 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/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.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/CAC19wg%2BVb0PLs42fa5T7aNSsP4JgZut5%3DZh1ij%2Be1FGaUpdDsQ%40mail.gmail.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
>>> 

Re: bitbucket-plugin - release is not published

['Gavin Mogan' via Jenkins Developers]

I used to have a little hackathon style tool that let you setup your repo
with the standards, but at some point it broke

https://github.com/halkeye/plugins-self-service/blob/master/labels.yaml is
the list of official labels though, you might be able to use other ones,
but that list worked once

On Sat, Feb 26, 2022 at 9:50 AM tzach solomon 
wrote:

> Thank you Tim :)
>
> Is there a list of labels I need to choose from or I can label with
> everything I want?
>
>
>
> On Sat, Feb 26, 2022, 6:15 PM Tim Jacomb  wrote:
>
>> Yes you need to label them
>>
>> On Sat, 26 Feb 2022 at 14:47, tzach solomon 
>> wrote:
>>
>>> I see now from
>>> https://www.jenkins.io/doc/developer/publishing/releasing-cd/ that I
>>> might have missed something? Do I need to label my PRs?
>>>
>>> *Now whenever Jenkins reports a successful build of your default branch,
>>> and at least one pull request had a label indicating it was of interest to
>>> users (e.g., enhancement rather than chore), your component will be
>>> released to Artifactory and release notes published in GitHub.*
>>>
>>> On Sat, Feb 26, 2022 at 4:42 PM tzach solomon 
>>> wrote:
>>>
 Daniel, thank you for trying to help. I really do appreciate it!

 I've tried again now to release a new version to fix
 https://issues.jenkins.io/browse/JENKINS-41635 but CI/CD does not seem
 to want to release my version.

 What have I done?

1. Created a branch in my fork at
https://github.com/tzachs/bitbucket-plugin
2. Pushed the commit
3. Merged back to https://github.com/jenkinsci/bitbucket-plugin

 At this point the CI started working and I followed it and saw the
 following failure,
 https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/PR-83/1/pipeline
 BUT,
 https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/master/88/pipeline
 passed.

 Also... from the Actions
  tab, I've seen
 multiple CD runs (which I did not trigger), the last one is
 https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1903327517
 .
 I don't know why release is not being performed? (shrugged)

 Can someone please help?

 On Tue, Feb 8, 2022 at 3:40 PM 'Daniel Beck' via Jenkins Developers <
 jenkinsci-dev@googlegroups.com> wrote:

>
>
> On Tue, Feb 8, 2022 at 1:25 PM tzach solomon 
> wrote:
>
>> Thanks Daniel (AGAIN! :)
>>
>> Can you please point me out what to read in order to fix these issues?
>> On what did it fail?
>> [image: image.png]
>>
>>
>> This checks the "status" of the commit to be released as reported by
> CI. It looks like if, at the time this action was run, something was 
> wrong.
> You can see the script doing this at
> https://github.com/jenkins-infra/verify-ci-status-action/blob/master/run.sh
> and I think we went into the block at line 42, so line 37 failed.
>
>
> --
> 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/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.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/CAC19wg%2BVb0PLs42fa5T7aNSsP4JgZut5%3DZh1ij%2Be1FGaUpdDsQ%40mail.gmail.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/CAH-3Bies4fzpvguCa7btv0an1%2B9E%2BuNVPbhFgZ1vTgeFzWeh8w%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this 

Re: bitbucket-plugin - release is not published

[tzach solomon]

Thank you Tim :)

Is there a list of labels I need to choose from or I can label with
everything I want?



On Sat, Feb 26, 2022, 6:15 PM Tim Jacomb  wrote:

> Yes you need to label them
>
> On Sat, 26 Feb 2022 at 14:47, tzach solomon 
> wrote:
>
>> I see now from
>> https://www.jenkins.io/doc/developer/publishing/releasing-cd/ that I
>> might have missed something? Do I need to label my PRs?
>>
>> *Now whenever Jenkins reports a successful build of your default branch,
>> and at least one pull request had a label indicating it was of interest to
>> users (e.g., enhancement rather than chore), your component will be
>> released to Artifactory and release notes published in GitHub.*
>>
>> On Sat, Feb 26, 2022 at 4:42 PM tzach solomon 
>> wrote:
>>
>>> Daniel, thank you for trying to help. I really do appreciate it!
>>>
>>> I've tried again now to release a new version to fix
>>> https://issues.jenkins.io/browse/JENKINS-41635 but CI/CD does not seem
>>> to want to release my version.
>>>
>>> What have I done?
>>>
>>>1. Created a branch in my fork at
>>>https://github.com/tzachs/bitbucket-plugin
>>>2. Pushed the commit
>>>3. Merged back to https://github.com/jenkinsci/bitbucket-plugin
>>>
>>> At this point the CI started working and I followed it and saw the
>>> following failure,
>>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/PR-83/1/pipeline
>>> BUT,
>>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/master/88/pipeline
>>> passed.
>>>
>>> Also... from the Actions
>>>  tab, I've seen
>>> multiple CD runs (which I did not trigger), the last one is
>>> https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1903327517.
>>> I don't know why release is not being performed? (shrugged)
>>>
>>> Can someone please help?
>>>
>>> On Tue, Feb 8, 2022 at 3:40 PM 'Daniel Beck' via Jenkins Developers <
>>> jenkinsci-dev@googlegroups.com> wrote:
>>>


 On Tue, Feb 8, 2022 at 1:25 PM tzach solomon 
 wrote:

> Thanks Daniel (AGAIN! :)
>
> Can you please point me out what to read in order to fix these issues?
> On what did it fail?
> [image: image.png]
>
>
> This checks the "status" of the commit to be released as reported by
 CI. It looks like if, at the time this action was run, something was wrong.
 You can see the script doing this at
 https://github.com/jenkins-infra/verify-ci-status-action/blob/master/run.sh
 and I think we went into the block at line 42, so line 37 failed.


 --
 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/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.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/CAC19wg%2BVb0PLs42fa5T7aNSsP4JgZut5%3DZh1ij%2Be1FGaUpdDsQ%40mail.gmail.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/CAH-3Bies4fzpvguCa7btv0an1%2B9E%2BuNVPbhFgZ1vTgeFzWeh8w%40mail.gmail.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/CAC19wg%2BKZj_ewnE3GFpXpr5cLWc_Q6qnZTUW7oFmoE3%2B%3DcO-Xw%40mail.gmail.com.

Re: bitbucket-plugin - release is not published

[Tim Jacomb]

Yes you need to label them

On Sat, 26 Feb 2022 at 14:47, tzach solomon  wrote:

> I see now from
> https://www.jenkins.io/doc/developer/publishing/releasing-cd/ that I
> might have missed something? Do I need to label my PRs?
>
> *Now whenever Jenkins reports a successful build of your default branch,
> and at least one pull request had a label indicating it was of interest to
> users (e.g., enhancement rather than chore), your component will be
> released to Artifactory and release notes published in GitHub.*
>
> On Sat, Feb 26, 2022 at 4:42 PM tzach solomon 
> wrote:
>
>> Daniel, thank you for trying to help. I really do appreciate it!
>>
>> I've tried again now to release a new version to fix
>> https://issues.jenkins.io/browse/JENKINS-41635 but CI/CD does not seem
>> to want to release my version.
>>
>> What have I done?
>>
>>1. Created a branch in my fork at
>>https://github.com/tzachs/bitbucket-plugin
>>2. Pushed the commit
>>3. Merged back to https://github.com/jenkinsci/bitbucket-plugin
>>
>> At this point the CI started working and I followed it and saw the
>> following failure,
>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/PR-83/1/pipeline
>> BUT,
>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/master/88/pipeline
>> passed.
>>
>> Also... from the Actions
>>  tab, I've seen
>> multiple CD runs (which I did not trigger), the last one is
>> https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1903327517.
>> I don't know why release is not being performed? (shrugged)
>>
>> Can someone please help?
>>
>> On Tue, Feb 8, 2022 at 3:40 PM 'Daniel Beck' via Jenkins Developers <
>> jenkinsci-dev@googlegroups.com> wrote:
>>
>>>
>>>
>>> On Tue, Feb 8, 2022 at 1:25 PM tzach solomon 
>>> wrote:
>>>
 Thanks Daniel (AGAIN! :)

 Can you please point me out what to read in order to fix these issues?
 On what did it fail?
 [image: image.png]


 This checks the "status" of the commit to be released as reported by
>>> CI. It looks like if, at the time this action was run, something was wrong.
>>> You can see the script doing this at
>>> https://github.com/jenkins-infra/verify-ci-status-action/blob/master/run.sh
>>> and I think we went into the block at line 42, so line 37 failed.
>>>
>>>
>>> --
>>> 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/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.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/CAC19wg%2BVb0PLs42fa5T7aNSsP4JgZut5%3DZh1ij%2Be1FGaUpdDsQ%40mail.gmail.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/CAH-3Bies4fzpvguCa7btv0an1%2B9E%2BuNVPbhFgZ1vTgeFzWeh8w%40mail.gmail.com.

Re: bitbucket-plugin - release is not published

[tzach solomon]

I see now from https://www.jenkins.io/doc/developer/publishing/releasing-cd/
that
I might have missed something? Do I need to label my PRs?

*Now whenever Jenkins reports a successful build of your default branch,
and at least one pull request had a label indicating it was of interest to
users (e.g., enhancement rather than chore), your component will be
released to Artifactory and release notes published in GitHub.*

On Sat, Feb 26, 2022 at 4:42 PM tzach solomon 
wrote:

> Daniel, thank you for trying to help. I really do appreciate it!
>
> I've tried again now to release a new version to fix
> https://issues.jenkins.io/browse/JENKINS-41635 but CI/CD does not seem to
> want to release my version.
>
> What have I done?
>
>1. Created a branch in my fork at
>https://github.com/tzachs/bitbucket-plugin
>2. Pushed the commit
>3. Merged back to https://github.com/jenkinsci/bitbucket-plugin
>
> At this point the CI started working and I followed it and saw the
> following failure,
> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/PR-83/1/pipeline
> BUT,
> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/master/88/pipeline
> passed.
>
> Also... from the Actions
>  tab, I've seen
> multiple CD runs (which I did not trigger), the last one is
> https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1903327517.
> I don't know why release is not being performed? (shrugged)
>
> Can someone please help?
>
> On Tue, Feb 8, 2022 at 3:40 PM 'Daniel Beck' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>>
>>
>> On Tue, Feb 8, 2022 at 1:25 PM tzach solomon 
>> wrote:
>>
>>> Thanks Daniel (AGAIN! :)
>>>
>>> Can you please point me out what to read in order to fix these issues?
>>> On what did it fail?
>>> [image: image.png]
>>>
>>>
>>> This checks the "status" of the commit to be released as reported by CI.
>> It looks like if, at the time this action was run, something was wrong. You
>> can see the script doing this at
>> https://github.com/jenkins-infra/verify-ci-status-action/blob/master/run.sh
>> and I think we went into the block at line 42, so line 37 failed.
>>
>>
>> --
>> 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/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.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/CAC19wg%2BVb0PLs42fa5T7aNSsP4JgZut5%3DZh1ij%2Be1FGaUpdDsQ%40mail.gmail.com.

Re: bitbucket-plugin - release is not published

[tzach solomon]

Daniel, thank you for trying to help. I really do appreciate it!

I've tried again now to release a new version to fix
https://issues.jenkins.io/browse/JENKINS-41635 but CI/CD does not seem to
want to release my version.

What have I done?

   1. Created a branch in my fork at
   https://github.com/tzachs/bitbucket-plugin
   2. Pushed the commit
   3. Merged back to https://github.com/jenkinsci/bitbucket-plugin

At this point the CI started working and I followed it and saw the
following failure,
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/PR-83/1/pipeline
BUT,
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/master/88/pipeline
passed.

Also... from the Actions
 tab, I've seen
multiple CD runs (which I did not trigger), the last one is
https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1903327517.
I don't know why release is not being performed? (shrugged)

Can someone please help?

On Tue, Feb 8, 2022 at 3:40 PM 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
>
> On Tue, Feb 8, 2022 at 1:25 PM tzach solomon 
> wrote:
>
>> Thanks Daniel (AGAIN! :)
>>
>> Can you please point me out what to read in order to fix these issues?
>> On what did it fail?
>> [image: image.png]
>>
>>
>> This checks the "status" of the commit to be released as reported by CI.
> It looks like if, at the time this action was run, something was wrong. You
> can see the script doing this at
> https://github.com/jenkins-infra/verify-ci-status-action/blob/master/run.sh
> and I think we went into the block at line 42, so line 37 failed.
>
>
> --
> 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/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.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/CAC19wg%2BEd8RRBMrfngWtsv3dmpBkPJiuvogdcqTnU_%2BgYA-fyg%40mail.gmail.com.

Re: Unit tests failing during dependabot merge (junit upgrade)

[Mohammed Abdullah]

Understood, thanks. I will finish all the videos and have another go at it.

On Saturday, February 26, 2022 at 1:16:14 PM UTC+5:30 ga...@gavinmogan.com 
wrote:

> Not sure why previous ones didn't fall, I suspect they do.
>
> I think it's referring to the Java compiler level
>
>
> https://github.com/jenkinsci/global-post-script-plugin/blob/master/pom.xml#L26
>
> That should be 8 (1.8 is now 8). Also your parent pom is really old. I 
> believe that's covered in one of marks videos
>
> On Fri., Feb. 25, 2022, 11:10 p.m. Mohammed Abdullah,  
> wrote:
>
>> Hi All,
>>
>>   I am trying to merge my first PR , given by dependabot.
>>
>>   Its a tiny change from junit from 4.11 to 4.13.1 on the pom.xml but the 
>> unit tests are failing , please see this link 
>> .
>>
>>   It looks like more changes may be required to actually make the above 
>> change. Please see below example and let me know how to proceed:
>>
>> [2020-10-13T04:59:05.594Z] [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-compiler-plugin:2.5:compile 
>> (default-compile) on project global-post-script: Compilation failure: 
>> Compilation failure: 
>>
>>
>> [2020-10-13T04:59:05.594Z]
>>  
>> [ERROR] error: Source option 5 is no longer supported. Use 6 or later. 
>>
>>
>> [2020-10-13T04:59:05.594Z]
>>  
>> [ERROR] error: Target option 1.5 is no longer supported. Use 1.6 or later.
>>
>> Thanks,
>> Mohammed
>>
>> -- 
>> 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-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/29c85be8-cb83-4d89-abc5-58366b2090a5n%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/4d38cddf-6123-44b0-aa21-e647661ec8a8n%40googlegroups.com.