Comments (4)
bap:
I can think of a couple of ways to achieve this with the current version of the plugin
The first is to install the promoted-builds plugin
During the build, "Archive the artifacts" that you want to FTP
Create a promotion that has an action that performs the FTP
You can then easily switch between manual promotion or automatically promoting (the build can promote itself!)
This also has the advantage that any given build can be promoted (FTP'd) at any given time (eg rollback - if #34 has been sent, but is bad, #32 could easily be sent back accross by re-executing the promotion)
The other way is to use the new parameterized publishing feature
Set a parameter name in the Advanced options of the publisher, and make the build parameterized with a parameter of the same name
You can use a String parameter or choice to select between the two options below
.* will publish to all FTP servers
.+ will publish to all FTP servers that have a label (as you have not given any labels, this would mean that none would publish)
Set the default parameter value for builds that are started automatically
A skip option also feels like it should be a lot more generic than just adding to every plugin - they are all configured in the same manner, and they all loose their configs if disabled and the config saved.
Would either of the above (especially the promoted-builds solution) be acceptable?
from publish-over-ftp-plugin.
Put yourself in my situation: I have two hundred jobs, each with an associated release job. I would like development teams to maintain their own jobs, but my team ends up providing assistance for all the jobs. The actual build steps in the jobs are already complicated (but as simple as we could make them), so we've worked really hard to try and keep all configuration down as much as possible, including writing our own in-house plugins that wrap up some configuration, etc. So, although what you described seems fine, it doesn't help me keep this simple for the development teams.
I do agree that having a generic skip would have been a nice thing for Jenkins to have built into the framework. I see it kind of like the maven skip facility - each plugin had to roll its own, and not all of them have that capability. But in retrospect, maven should have made this easy also. Meanwhile, it is what it is.
from publish-over-ftp-plugin.
bap:
Jacob,
I have just released the Flexible Publish Plugin https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin (wiki page to become useful this afternoon )
With this plugin installed, you can add the "Send build artifacts over FTP" to the "Flexible publish" Post-build Action and use the Run Condition "Always" to enable the publish.
To "skip" without losing the FTP configuration, update the Run Condition to "Never".
Please close this issue if you find my solution acceptable.
Bap.
from publish-over-ftp-plugin.
bap:
No response, assume happy
from publish-over-ftp-plugin.
Related Issues (20)
- How to show FTP transfered file names in Jenkins console
- ERROR: Exception when publishing, exception message [Could not write file. Server message: [534 Policy requires SSL. 22:28:03 ]]
- [JENKINS-23175] Add support for Credentials plugin supplied credentials HOT 6
- [JENKINS-26550] publish over ftp plugin ver. 1.11 transfer 0 files HOT 1
- [JENKINS-27335] Can not send file from linux agent HOT 1
- [JENKINS-34993] Publish over FTP plugin hangs up HOT 1
- [JENKINS-36079] Regression in v.1.12 HOT 2
- [JENKINS-37089] How to configure "Publish over FTP plugin", I got "534 Policy requires SSL" error. HOT 1
- [JENKINS-37259] Client uses LIST output rather than using MLSD command. HOT 11
- [JENKINS-37507] Add Pipeline Support for Publish over FTP HOT 6
- [JENKINS-49518] Directory is not created anymore
- [JENKINS-50707] java.lang.StackOverflowError HOT 2
- [JENKINS-51001] Publish over ftp didn't create folders on HOT 1
- [JENKINS-54780] Support JCASC in Publish Over FTP plugin HOT 5
- [JENKINS-55816] Publish over FTP fails on multi-module project when modules skipped HOT 10
- [JENKINS-62379] Migrate publish over FTP docs from wiki to plugin README HOT 5
- [JENKINS-63214] Could not write file: 522 SSL/TLS required (...) HOT 3
- Iām having trouble with jenkins, public over FTP plugin
- Getting "unsupporteed SSL message" on connection
- Clean remote option fails
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
š Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ššš
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ā¤ļø Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from publish-over-ftp-plugin.