jenkinsci / jenkinsci/subversion-plugin

[JENKINS-22090] svn-tag does not handle multi-configuration projects correctly

Open
#1,115 1 comment 0 reactions 0 assignees View on GitHub
component:subversion-plugin component:svn-tag-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
131
Forks
275
Avg merge
12h 4m
Merged PRs (30d)
6

Description

When SVN tagging is enabled in a Multi-Configuration with mulitple slaves, each slave attempts to apply the subversion tag.

If there are ten slaves building, each slave will attempt to remove and apply the same label.

Given each slave is using the exact same code base, build number etc, I would expect tagging to occur once at the master upon the success of all the slaves.

---
Originally reported by anstaafl, imported from: svn-tag does not handle multi-configuration projects correctly


  • assignee: k2nakamura
  • status: Open
  • priority: Major
  • component(s): subversion-plugin, svn-tag-plugin
  • label(s): multi-configuration, plugin, subversion
  • resolution: Unresolved
  • votes: 1
  • watchers: 4
  • imported: 20251212-090250

Raw content of original issue

When SVN tagging is enabled in a Multi-Configuration with mulitple slaves, each slave attempts to apply the subversion tag.
If there are ten slaves building, each slave will attempt to remove and apply the same label.
Given each slave is using the exact same code base, build number etc, I would expect tagging to occur once at the master upon the success of all the slaves.

  • environment: Multiple slave machines of different architecture/OS building the same code base

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.