package org.jenkinsci.plugins.p4.publish; import java.io.Serializable; import org.kohsuke.stapler.DataBoundConstructor; import hudson.Extension; public class SubmitImpl extends Publish implements Serializable { private static final long serialVersionUID = 1L; private final boolean reopen; public boolean isReopen() { return reopen; } @DataBoundConstructor public SubmitImpl(String description, boolean onlyOnSuccess, boolean delete, boolean reopen) { super(description, onlyOnSuccess, delete); this.reopen = reopen; } @Extension public static final class DescriptorImpl extends PublishDescriptor { @Override public String getDisplayName() { return "Submit change"; } } }
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 23685 | Paul Allen | Copy main -> dev | ||
#1 | 20641 | Paul Allen | Copy main -> dev (jenkinsci/p4-plugin) | ||
//guest/perforce_software/p4jenkins/main/src/main/java/org/jenkinsci/plugins/p4/publish/SubmitImpl.java | |||||
#4 | 19790 | Paul Allen |
Add a propagate delete option to Publish. Originally only add/edits were permitted to prevent users deleting files with incorrect View maps, but this option allows deletes if enabled. JENKINS-27885 |
||
#3 | 14035 | Paul Allen |
Publish on Success option. Added a checkbox to the Publish step to only shelve/submit change if the build succeeded. |
||
#2 | 11334 | Paul Allen |
Remote slave support for Publish Perforce Publish commands need to be executed from the remote slave. - Includes refactoring into task package |
||
#1 | 11231 | Paul Allen |
Publish assets to Perforce. New feature to allow Jenkins to shelve or submit the build result to Perforce. Configured as a Post Build Step, the Perforce credential and workspace are required as the asset could be published to a different Perforce instance. |