Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14653

Copy Artifacts plugin does not accept Maven module as Project Name with TriggeredBuildSelector

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: copyartifact-plugin
    • Labels:
      None
    • Environment:
      Windows 7,
    • Similar Issues:

      Description

      When copying artifacts from a Maven project: if you type the bare Jenkins project name (i.e. "my-build-trunk") into the "Project Name" field then Jenkins will display the message:

      "Artifacts will be copied from all modules of this Maven project; click the help icon to learn about selecting a particular module."

      At this point, a reasonable user would expect to be able to configure a Maven module instead, e.g. "my-build-trunk/com.stuff.my$moduleName".

      However, the TriggeredBuildSelector does not understand Maven project names because it is only expecting a bare Jenkins project name. This creates such frustration and confusion that users are forced to examine the plugin's source code to find out WHAT ON EARTH is going wrong.

        Attachments

          Activity

            People

            • Assignee:
              ikedam ikedam
              Reporter:
              chrisr Chris Rankin
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: