-
New Feature
-
Resolution: Unresolved
-
Major
Would allow for use from workflows.
[JENKINS-25976] Make DeployPublisher a SimpleBuildStep
| Epic Link | New: JENKINS-34657 [ 170293 ] |
| Comment |
[ [~danielbeck] unless the code has changed the GET request does not actually trigger a build, rather it is a hint to Jenkins that there may be a change so go and run polling to see if there actually is a change. That is a subtle difference, as Jenkins is not trusting the GET request, rather it is trusting the polling of the git server. That at least was the design KK originally picked and the blog post was based on that design. I am not sure if the GET request has since been augmented in ways that supply contextual data that would not be available by polling. If so then that is a vulnerability, but the original design is only useful as a DoS attack of the git server ] |
| Workflow | Original: JNJira [ 159964 ] | New: JNJira + In-Review [ 180192 ] |
| Labels | Original: workflow | New: pipeline workflow |
| Labels | Original: pipeline workflow | New: pipeline |
| Epic Link | Original: JENKINS-34657 [ 170293 ] |
New:
|
Ryan Campbell
made changes -
| Description | Original: Would allow for use from workflows. |
New:
As a pipeline author, I would like to use the Jenkins Deployer plugin from within my pipeline scripts and declarative pipelines so that I can easily deploy my apps from my Jenkins pipeline and migrate my freestyle usage of this plugin to pipeline. Acceptance Criteria # Each of the supported container adapters will have a symbol that allows creation of references which includes the deployment details required by each deployment target # There will be a pipeline step called deploy that is configurable from within the pipeline script # There will be unit tests that confirm new functionality # There will be manual testing that deploys wars from the pipeline (preferably both Tomcat and Glassfish) # The plugin will be upgraded to a recent plugin pom so that the testing is performed against somewhat recent versions I'm proposing the following syntax, I think this provides a reasonably straightforward use and config. {code:java} node { def tc8 = tomcat8( url: 'http://localhost:1234/app', password: '******', userName: 'admin' ) deploy(container: tc8, war: '/target/app.war', contextPath: '/app') deploy(containers: [tc8, gf3], war: '/target/app.war', contextPath: '/app') }{code} Tech notes/tasks: * Refactor to work with pipeline APIs |
Ryan Campbell
made changes -
| Description |
Original:
As a pipeline author, I would like to use the Jenkins Deployer plugin from within my pipeline scripts and declarative pipelines so that I can easily deploy my apps from my Jenkins pipeline and migrate my freestyle usage of this plugin to pipeline. Acceptance Criteria # Each of the supported container adapters will have a symbol that allows creation of references which includes the deployment details required by each deployment target # There will be a pipeline step called deploy that is configurable from within the pipeline script # There will be unit tests that confirm new functionality # There will be manual testing that deploys wars from the pipeline (preferably both Tomcat and Glassfish) # The plugin will be upgraded to a recent plugin pom so that the testing is performed against somewhat recent versions I'm proposing the following syntax, I think this provides a reasonably straightforward use and config. {code:java} node { def tc8 = tomcat8( url: 'http://localhost:1234/app', password: '******', userName: 'admin' ) deploy(container: tc8, war: '/target/app.war', contextPath: '/app') deploy(containers: [tc8, gf3], war: '/target/app.war', contextPath: '/app') }{code} Tech notes/tasks: * Refactor to work with pipeline APIs |
New: Would allow for use from workflows. |
Sam Van Oort
made changes -
| Epic Link |
Original:
|
New: JENKINS-34657 [ 170293 ] |
| Assignee | Original: Stephen Connolly [ stephenconnolly ] |