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
On 17/10/12 14:12, Steve K wrote:
Hello,
Using the Git plugin, the repository created for the build, by
default, occupies the Jenkins' WORKSPACE directory.
Is there a way to tell the plugin to use a specific sub-directory of
WORKSPACE (we have several scripts that rely on a specific parent
Hi Jørgen,
On 01/08/12 05:19, Jørgen Tjernø wrote:
Darragh, or anyone else, do you know what's causing this?
We're also seeing it, and it's making the Job Config History plugin a
little useless, with all these add and remove changes happening.
- Jørgen.
Someone was kind enough to log a
I have a jenkins instance with the build config history plugin installed
and it appears to be spammed by every build due to a line being
successively added and then removed from the build config xml.
Here's the snipet from the end of a build config:
buildWrappers
Hi,
On 04/04/12 21:05, Sami Tikka wrote:
If the lock you mention below is something provided by the
locks-and-latches plugin, you should consider another way to make sure
only Job A or B runs. Locks-and-latches is unmaintained.
Yes, forgot to include that. It's the locks-and-latches plugin.
