d all of those need to be moved too.
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/Job-Config-History-Plugin-and-Jenkins-Enterprise-from-CloudBees-tp4666783p4674210.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
You received this message becau
Hi Bob,
I am heavily using CB Enterprise plugins. (Note Folders is not an
enterprise plugin but one of the cloudbees free as-in-beer ones)
I have found most plugins now work. Over the couple of years I have found
some incompatabilities with plugins.
When I have previously found issues clou
Hi,
We are using Jenkins Enterprise from CloudBees and have jobs contained within
CloudBees Folders.
The JobConfigHistory plugin (
https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin ) works
fine for jobs that are at the root level; however, if the job is under a
CloudBees fol
I am using both the Jenkins Job Configuration History plugin v2.2 and
EnvInject v 1.73
As has been noted in the Jira, envinject seems to modify the config each
time the job is run creating long job config histories.
I have just noticed that there are some optins for configuring Job Config
Hi,
Resolved my own problem.
On 01/11/12 13:47, Darragh Bailey wrote:
> Hi,
>
> I'm trying to put together a script that can be run via the console or
> possibly the groovy plugin, to remove all the additional saved configs
> added due to how the envInject and jobConfigHistory plugins interact
Hi,
I'm trying to put together a script that can be run via the console or
possibly the groovy plugin, to remove all the additional saved configs
added due to how the envInject and jobConfigHistory plugins interact.
Related Jira is https://issues.jenkins-ci.org/browse/JENKINS-14144.
The core p
