jenkinsci / plasticscm-plugin

A plugin for Jenkins to be able to use Plastic SCM
MIT License
16 stars 31 forks source link

added option to change Workfolder for checkout #6

Closed childnode closed 9 years ago

childnode commented 9 years ago

current:

now:

note:

childnode commented 9 years ago

.hpi compilation can also be get from http://q.childno.de/osfyw

childnode commented 9 years ago

your jenkins needs a new config, hpi has to be build with JDK6 or .pom needs clean definitions!

childnode commented 9 years ago

failure on "cm wi"

ravelus commented 9 years ago

Please, address this issue to support@codicesoftware.com; thank you :)

childnode commented 9 years ago

@ravelus why? working code is finally there: https://github.com/childnode/plasticscm-plugin/releases/tag/plasticscm-plugin-2.2-SNAPSHOT-workdir

But there are quite some issues to tackle: Build Specific Workspace Names doesn't make sense to me, therefor the changes in https://github.com/childnode/plasticscm-plugin/commit/336397b are some (dirty) workarounds but I think substituteBuildParameter() and therefor using http://javadoc.jenkins-ci.org/hudson/model/ParametersAction.html#substitute(hudson.model.AbstractBuild, java.lang.String) is quite a bad idea for workspace names while this allows workspace names that are build and not job specific that might then mess up server with workspaces for each build.

ravelus commented 9 years ago

I'm not managing this codebase anymore (but PlasticSCM organization), so I'm not authorized to merge these changes to the mainline, you know.

Sorry for the inconveniences.

childnode commented 9 years ago

but still a month ago you committed a bunch of files ... why is it then here on gitHub if code is not maintained here?! That doesn't make sense to me... nevertheless: I contacted plasticSCM Team

ravelus commented 9 years ago

The code is still maintained in GitHub (I never said the opposite :)), I've just said that I personally don't maintain this code any longer. I used to do it till one week ago.

Good, talk to support, they will deal with this issue properly, planning it and study the changes and eventually merging them to master and publishing a new release of the plugin.