On Thursday, November 14, 2024 at 5:49:49 AM UTC-5 Vahila wrote:
Q1. Our plan is leverage CD but to trigger the release explicitly, not on
every push.
That would not be “CD” would it?
In the version format, is it okay to have only a manually controlled
semantic version(ex: 4.2.34) and not append the ${changelist}.
No, that is not supported. The design is that plugin versions are just
ordered counters generated by machines and consumed by machines, not
something a developer curates or a Jenkins administrator pays attention to.
You should not need semantic versions because you should not make
incompatible changes, and if you really are forced to, you will need to do
a lot more work than just change some number and hope users notice—the
expectation is that an admin will simply see a couple dozen plugin updates
and accept them all.
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?
Yes, the GHA workflow runs the Maven build all the way to the `deploy`
phase with all tests and other validations disabled, with generic
hardware/tools, which is why it is only run when the ci.jenkins.io build is
passing.
--
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 visit
https://groups.google.com/d/msgid/jenkinsci-dev/cb768927-afcc-4d13-b7a8-1fe36e49615dn%40googlegroups.com.
