[vigilnz-security-plugin] Release tag skipped deployment

16 views
Skip to first unread message

Susenthiran S

unread,
Dec 19, 2025, 10:48:50 PM (3 days ago) Dec 19
to Jenkins Developers
Hi Jenkins Infra team,

I recently pushed a release tag for my plugin:
Repository: jenkinsci/vigilnz-security-plugin
Tag: vigilnz-security-1.0

The build on ci.jenkins.io completed successfully, but the console log shows:
"Skipping Incrementals deployment for branch build of CD-enabled repo"
and no artifact was published to repo.jenkins-ci.org.

Could you please confirm if CD is enabled for this repository and help me understand why the release deployment was skipped?

Thanks,
Susenthiran

Mark Waite

unread,
Dec 19, 2025, 11:12:29 PM (3 days ago) Dec 19
to jenkin...@googlegroups.com
On Fri, Dec 19, 2025 at 8:48 PM Susenthiran S <susenthi...@gmail.com> wrote:
Hi Jenkins Infra team,

I recently pushed a release tag for my plugin:
Repository: jenkinsci/vigilnz-security-plugin
Tag: vigilnz-security-1.0
 
Welcome aboard!

Tags do not control continuous delivery releases, as far as I know.  Continuous delivery releases start when a relevant label is applied to one or more pull requests that have been merged into the primary branch.

No pull requests have been merged in that repository.  Because no pull requests have been merged, no release has been triggered.

The build on ci.jenkins.io completed successfully, but the console log shows:
"Skipping Incrementals deployment for branch build of CD-enabled repo"
and no artifact was published to repo.jenkins-ci.org.

Could you please confirm if CD is enabled for this repository and help me understand why the release deployment was skipped?

Please follow the steps described in the developer documentation to enable automated releases.

The repository permissions updater file is already configured to allow enabling continuous delivery in the plugin repository.

However, the repository is not configured for continuous delivery.  You need to complete the changes in the repository according to the instructions in the Jenkins developer .  I cloned the repository and ran the commands:

mvn validate help:evaluate -Dexpression=project.version
mvn validate help:evaluate -Dexpression=project.version -Dset.changelist -Dignore.dirt

Those commands returned unexpected values.  When you complete the steps to enable continuous delivery from the repository, those commands will return the types of values described in the documentation.
Mark Waite
Reply all
Reply to author
Forward
0 new messages