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

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: copyartifact-plugin
    • None
    • Environment:
      Windows 7,

      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.

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

              Created:
              Updated:
              Resolved: