<?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="Shelved by Jenkins. Build: $${BUILD_TAG}"/> </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="revert"> <f:checkbox title="${%Revert opened file list}" 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 | 26094 | Paul Allen |
Merge pull request #105 from jenkinsci/publishFilter 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 | 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 |
||
#4 | 19519 | Paul Allen |
Jelly header update. <?jelly escape-by-default='true'?> |
||
#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 | 11331 | Paul Allen |
Publish logging and help pages Added logging details for shelved/submitted files. Added help dialogs for Publish configuration. Added -k option for shelve revert. |
||
#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. |