Enable Continuous Delivery

[rantoniuk]

https://www.jenkins.io/doc/developer/publishing/releasing-cd/

[programbeginnerTW]

Hi, @rantoniuk !
It seems simple to follow the directions in the link to enable this feature!
May I start doing this?

[rantoniuk]

Thanks for volunteering, however this issue is actually for maintainers - that's why I already assigned it to myself. We need to see internally if we actually want this type of delivery and if it fits our development cycle.

[rantoniuk]

@olamy what are your thoughts on enabling this Continuous Delivery?

I think it make sense to automate the releases, but I'm not sure we want to go with this weird release numbering scheme, that increments the major numbers. To me one of the below version strings would probably be ok though:

• 1.321.vabcdef456789 or 1.999999-SNAPSHOT
• 4.0.0-123.vabcdef456789 or 4.0.0-999999-SNAPSHOT

(see Manually controlled prefix (optional) and Versioning with wrapped components (optional) from the releasing-cd page).

[olamy]

TBH, I'm not really active anymore on this plugin (but who knows :) )
So It's up to active people.
My personal thoughts, I would be -0, because I don't feel it right to be so dependent on external concurrent tooling for something such important as releasing....