config.jelly #7 

<?jelly escape-by-default='true'?>
<j:jelly 	xmlns:j="jelly:core" 	xmlns:st="jelly:stapler" 	xmlns:d="jelly:define" 
			xmlns:l="/lib/layout" 	xmlns:t="/lib/hudson" 		xmlns:f="/lib/form">
			
	<f:entry title="${%Description}" field="description">
		<f:textarea default="Submitted by Jenkins. Build: $${BUILD_TAG}"/>
	</f:entry>

    <f:entry title="${%Purge Revisions}" field="purge">
        <f:textbox default=""/>
    </f:entry>

	<f:entry field="onlyOnSuccess">
		<f:checkbox title="${%Only publish on build success}" default="false"/>
	</f:entry>
	
	<f:entry field="delete">
		<f:checkbox title="${%Propagate deletes}" default="false"/>
	</f:entry>

	<f:entry field="modtime">
		<f:checkbox title="${%Use MODTIME for consistency check}" default="false"/>
	</f:entry>

	<f:entry field="reopen">
		<f:checkbox title="${%Reopened files}" default="false"/>
	</f:entry>

    <f:advanced>
        <f:entry title="Publish paths" field="paths">
            <f:textarea default="${descriptor.defaultPath}"/>
        </f:entry>
    </f:advanced>
	
</j:jelly>
# Change User Description Committed
#7 26142 paul_allen Enable Advanced Publish paths for Submits.

Publish path filter for reconcile JENKINS-56501
#6 25668 paul_allen Merge pull request #94 from lystor/bug-56414

JENKINS-56414: Support of Reconcile with Modtime in P4Publish
#5 20954 paul_allen Add purge -S<n> option for the Submit stage of Publish.

If a value is provided it will set the purge option on all files found as part of the reconcile (ADD/EDIT).  It will not remove the purge option once set.

JENKINS-36112
#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 19519 paul_allen Jelly header update.

<?jelly escape-by-default='true'?>
#2 14035 paul_allen Publish on Success option.

Added a checkbox to the Publish step to only shelve/submit change if the build succeeded.
#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.