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
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:
>
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
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
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
>>
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
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
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
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,
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]
On Tue, Feb 8, 2022 at 2:19 PM 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
>
>
> On Mon, Feb 7, 2022 at 8:34 PM tzach solomon
On Mon, Feb 7, 2022 at 8:34 PM tzach solomon
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
"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."
On Mon, Feb 7, 2022 at 9:33 PM tzach solomon
wrote:
> Daniel, you are correct.
> I've manually triggered the git actions
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,
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?
--
14 matches
Mail list logo
