Hi,
We're looking to use Jenkins w/ workflow to replace our in-house CI
system. However, there's a bunch of stuff that doesn't seem to be
present in the addin (some of it might be missing features, some might
be plugin compatibility, some might be me not seeing something in the
documentation)
On Tue, Dec 16, 2014 at 10:50 AM, James Nord te...@teilo.net wrote:
Its not possible as far as I am aware - and it was something I mentioned
a few months ago.
However - in my previous usage of this - it didn't really matter about the
50 shell scripts - as they where grouped logically into
On Tuesday, 16 December 2014 10:15:31 UTC, Jo Shields wrote:
Hi,
We're looking to use Jenkins w/ workflow to replace our in-house CI
system. However, there's a bunch of stuff that doesn't seem to be
present in the addin (some of it might be missing features, some might
be plugin
https://github.com/directhex/jenkins-git-catch-up
/micdrop
When I'm done, it'll optionally allow for merges to be squashed (i.e. if
someone merges a large branch, that merge commit will be regarded as one
commit, not as potentially dozens)
--
You received this message because you are
I'm trying to resolve the nearly-a-decade-old bug to allow Jenkins to do
one build per commit, without dirty workarounds in dispatcher jobs.
Currently, it'll bundle together multiple commits received at once - for
example, a user does git push to send more than one commit.
I've written a custom
Hi all,
I'm observing a problem with our new Jenkins master, running on an Ubuntu
VM on a high-spec Azure instance - latency between master and workers is
*crazy* high. Like 30 plus seconds:
https://jenkins.mono-project.com/computer/. The SSH-based workers can
generally survive that, but the JNLP
Okay, a co-worker may have found a magical fix - Azure times out idle
network connections after 4 minutes, but the default value
for hudson.slaves.ChannelPinger.pingInterval is 5 minutes...
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
