Automate cd.

[XiongKezhi]

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

Try to remain the semVer and use the generated number as patch version, so the expected format should be 1.7-123.vabcdef456789.

One problem: in this cd model, should we release a new version once we bump a new version of dependency? How can we avoid it if not?

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.38%. Comparing base (9a99cc3) to head (b652d16).
Report is 121 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master     #115      +/-   ##
============================================
- Coverage     85.52%   85.38%   -0.14%     
  Complexity      152      152              
============================================
  Files            17       17              
  Lines           746      746              
  Branches         57       57              
============================================
- Hits            638      637       -1     
- Misses           88       89       +1     
  Partials         20       20              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[timja]

are you trying to keep some form of versioning here rather than just commit count?

the format you're is recommended for 'wrapped' components, i.e. api libraries.

[XiongKezhi]

yes, I'm trying to use the generated number as the "patch" version in semantic versioning. But that introduces a problem: what if I want to release the next minor version? If using this automated cd, it seems I have to file a PR to update the version number and get it merged.

[timja]

The tekton client plugin does it with semantic commits I think: https://github.com/jenkinsci/tekton-client-plugin/blob/master/.github/workflows/cd.yaml#L26

[timja]

if you search 'Manually controlled prefix' on this page https://www.jenkins.io/doc/developer/publishing/releasing-cd/

you will get something similar with at least a low version number

[jglick]

As noted in https://www.jenkins.io/doc/developer/publishing/releasing-cd/#update-maven-pom-and-config this style is not recommended.

[jglick]

Suggested change

version-template: $MAJOR.$MINOR.$PATCH

[jglick]

Also

checks-api-plugin/pom.xml

Lines 5 to 10 in a278bc3

	<parent>
	<groupId>org.jvnet.hudson.plugins</groupId>
	<artifactId>analysis-pom</artifactId>
	<version>5.24.0</version>
	<relativePath />
	</parent>

is a red flag. Switch to the normal parent POM.