Class TargetGroup
- All Implemented Interfaces:
Describable<TargetGroup>
Grouping is the whole reason the API is shaped this way. A flat list of files crossed with a flat list of substitutions would apply XML paths to JSON files and fail under the default error policy; scoping substitutions to the files they belong to is what makes the canonical example work.
-
Nested Class Summary
Nested Classes -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptiongetFiles()The file patterns as newline-separated text, for the form view only.voidMethods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface hudson.model.Describable
getDescriptor
-
Constructor Details
-
TargetGroup
@DataBoundConstructor public TargetGroup(@NonNull List<String> files, @NonNull List<Substitution> substitutions)
-
-
Method Details
-
getFiles
-
getFilesText
The file patterns as newline-separated text, for the form view only.Not a configuration property:
DescribableModelderives properties from the@DataBoundConstructorparameters and@DataBoundSettermethods, so this getter is invisible to Pipeline binding and to the Snippet Generator. It exists because Jenkins form binding has no workable idiom for aList<String>, so the form uses a textarea andTargetGroup.DescriptorImpl.newInstance(org.kohsuke.stapler.StaplerRequest2, net.sf.json.JSONObject)converts it back. The Pipeline API staysfiles: ['a', 'b']. -
getSubstitutions
-
getFormat
-
setFormat
-