bitbucket-plugin - release is not published

[tzach solomon]

Hi All,

Can you please help me understand why https://github.com/jenkinsci/bitbucket-plugin/releases/tag/215.vfe32d14d1f47 is not published?
It was released 3 days ago and I've probably done something wrong since I don't see it in the available version to upgrade.

Thanks in advance,

Tzach

[Daniel Beck]

The release does not exist in the Maven repo, so it cannot be made available.

Release drafter says the release was created from GH actions, but I cannot find the CD run creating it. Timing-wise it should probably be between 42 and 41.

Any idea why some runs are attributed to the ghost user?

[tzach solomon]

Daniel, you are correct. 
I've manually triggered the git actions since I saw it was triggered by merge.
The trigger was #27 https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1795360127

What have I done wrong? I thought that by merging my PR it would auto trigger the actions.

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

[tzach solomon]

"I've manually triggered the git actions since I saw it was triggered by merge" --> "I've manually triggered the git actions since I saw it was NOT triggered by merge."

[Daniel Beck]

On Mon, Feb 7, 2022 at 8:34 PM tzach solomon <tzach....@gmail.com> wrote:

Daniel, you are correct. 
I've manually triggered the git actions since I saw it was triggered by merge.
The trigger was #27 https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1795360127

What have I done wrong? I thought that by merging my PR it would auto trigger the actions.

Releases need CI to pass first, and it did not according to "Verify CI Status" in https://github.com/jenkinsci/bitbucket-plugin/runs/5067663410?check_suite_focus=true 

[tzach solomon]

Thanks Daniel (AGAIN! :)

Can you please point me out what to read in order to fix these issues?
On what did it fail?

--

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/CAMo7Pt%2B1BeuXKdzRQJ2NBRAqtLyegRrGbDq8cGcJHBT0_f0YWQ%40mail.gmail.com.

[Daniel Beck]

On Tue, Feb 8, 2022 at 1:25 PM tzach solomon <tzach....@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?

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.

[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?

--
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.

[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.

[Tim Jacomb]

Yes you need to label them 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAC19wg%2BVb0PLs42fa5T7aNSsP4JgZut5%3DZh1ij%2Be1FGaUpdDsQ%40mail.gmail.com.

[tzach solomon]

Thank you Tim :)

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

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bies4fzpvguCa7btv0an1%2B9E%2BuNVPbhFgZ1vTgeFzWeh8w%40mail.gmail.com.

[Gavin Mogan]

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

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.

[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

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuC8XcGfNQ%3Do%2BsfHjmDuOx1PE3mzrg79so39_%2B8eaR-Qg%40mail.gmail.com.

[tzach solomon]

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

- Tzach

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvyGk4hR8K%3DWELAZN%2BLHM6d10KSg9r%3Dg82o3OdSkrauWhQ%40mail.gmail.com.

[Mark Waite]

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