Thank you for your inputs! I have few follow-up questions.
Q1. Our plan is leverage CD but to trigger the release explicitly, not on
every push. In the version format, is it okay to have only a manually
controlled semantic version(ex: 4.2.34) and not append the ${changelist}.
Would we be able to leverage the CD without any issues?
Q2. I wanted to understand the role of the Jenkins build and the CD using
GitHub actions. My understanding is that on ci.jenkins.io CI build occurs
and tests are run. And GitHub actions is used to upload the artifacts to
Maven antifactory. Is this correct?
Thank you,
Vahila.
On Thursday, November 14, 2024 at 2:07:50 AM UTC+5:30 jgl...@cloudbees.com
wrote:
> On Wed, Nov 13, 2024 at 2:46 PM Vahila <kayithiva...@gmail.com> wrote:
>
>> *Q1. Release Triggering:* My understanding is that every successful
>> build of the default branch triggers a release
>>
> If at least one PR with an “interesting” label (so for example `bug` but
> not `dependencies`) has been merged since the last release.
>
>> in the kubernetes-plugin
>> <https://github.com/jenkinsci/kubernetes-plugin/pull/1139/files>, the
>> latest release includes changes from multiple PRs.
>>
> I think there were a few PRs merged in close succession, so the trunk
> build kept on getting interrupted.
>
>> does the release happen when the PR is merged?
>>
> Not quite; it is triggered when there is a passing ci.jenkins.io build of
> the default branch. Normally that would happen within a few minutes of the
> PR being merged.
>
> *Q2. Automated Versioning:* How is the automated version generated?
>>
>
> https://github.com/jenkinsci/jep/blob/master/jep/305/README.adoc#basic-usage
>
> How is the version determined when multiple PRs or commits are involved?
>>
> The version is deterministic for a given commit, regardless of what chain
> of PRs led to it.
>
>
>> *Q3. PR Labels:* The labels added to PRs are crucial as they determine
>> whether a release occurs. Is there any documentation specifying which
>> labels trigger a release and which do not?
>>
>
> https://github.com/jenkinsci/.github/blob/1b5201fb8a46f811502f076272376dd72eea9e54/.github/release-drafter.yml#L9-L61
>
> plus
> https://github.com/jenkins-infra/interesting-category-action/blob/78f4b74509528c18790d9c36b2cccb5b21ed3451/action.yaml#L9-L13
>
>
> Feel free to update the docs page to clarify anything discussed above (in
> terms that make sense to you).
>
--
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 visit
https://groups.google.com/d/msgid/jenkinsci-dev/d6f3eca2-5b0d-4ffd-a81b-e1b268df8f31n%40googlegroups.com.
