-
Bug
-
Resolution: Fixed
-
Major
-
None
Please add support for deploy plugin to accept parametrized variables for url, user and password.
I tried injecting parameters with envinject and then referencing them in deploy-plugin like %app.server.url%, ${app.server.url}, $app.server.url, but I'm still getting exception
FATAL: java.net.MalformedURLException: no protocol: %app.server%/manager
java.lang.AssertionError: java.net.MalformedURLException: no protocol: %app.server%/manager
[JENKINS-22403] allow deploy plugin to accept parametrized variables like %parameter% or $parameter
First Name Last Name
added a comment - Looking up similar codes I came to 'copyartifact-plugin-master'.
\src\main\java\hudson\plugins\copyartifact\CopyArtifact.java
...
public boolean perform(AbstractBuild<?,?> build, Launcher launcher, BuildListener listener)
throws InterruptedException, IOException {
upgradeIfNecessary(build.getProject());
PrintStream console = listener.getLogger();
String expandedProject = project, expandedFilter = filter;
try {
EnvVars env = build.getEnvironment(listener);
env.overrideAll(build.getBuildVariables()); // Add in matrix axes..
expandedProject = env.expand(project);
...
I guess we need similar mechanism in 'deploy-plugin-master'
First Name Last Name
added a comment - Looking up similar codes I came to 'copyartifact-plugin-master'.
\src\main\java\hudson\plugins\copyartifact\CopyArtifact.java
...
public boolean perform(AbstractBuild<?,?> build, Launcher launcher, BuildListener listener)
throws InterruptedException, IOException {
upgradeIfNecessary(build.getProject());
PrintStream console = listener.getLogger();
String expandedProject = project, expandedFilter = filter;
try {
EnvVars env = build.getEnvironment(listener);
env.overrideAll(build.getBuildVariables()); // Add in matrix axes..
expandedProject = env.expand(project);
...
I guess we need similar mechanism in 'deploy-plugin-master' 
Nils Kuhn
added a comment - Anything new about that? First Name Last Name
added a comment - Nope. 'deploy-plugin' is not mature for anything close to enterprise production environment. We went for a solution outside Jenkins (however trigger from Jenkins).
First Name Last Name
added a comment - Nope. 'deploy-plugin' is not mature for anything close to enterprise production environment. We went for a solution outside Jenkins (however trigger from Jenkins). 
First Name Last Name
added a comment - Contact me privately, we have an enterprise grade solution. Regards, Balazs
First Name Last Name
added a comment - Contact me privately, we have an enterprise grade solution. Regards, Balazs 
Vadim Ippolitov
added a comment - Is there any solution for this? We're using Tomcat 7. 
Robin Jansohn
added a comment - This should be supported since v1.12. 
Is there any solution or workaround for this? I am desperate to have 1 deployment job which can be used for many environments (DEV, TST etc.)