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 <[email protected]> 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 > <https://github.com/jenkinsci/bitbucket-plugin/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 < > [email protected]> wrote: > >> >> >> On Tue, Feb 8, 2022 at 1:25 PM tzach solomon <[email protected]> >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAC19wg%2BVb0PLs42fa5T7aNSsP4JgZut5%3DZh1ij%2Be1FGaUpdDsQ%40mail.gmail.com.
