write groovy scripts is
> pretty much the only workable technique.
>
> On Wednesday, February 8, 2017 at 2:32:37 AM UTC-7, Barry Laffoy wrote:
>>
>> By digging into the source code, I found an answer myself.
>>
>> import jenkins.model.Jenkins
>> i
2017 09:18:46 UTC, Barry Laffoy wrote:
>
> In my never-ending quest to create a deployment script for Jenkins (why is
> this so difficult?), I would like to be able to configure the quiet period
> on startup, *without needing to configure it through the UI*.
>
> Is there a
In my never-ending quest to create a deployment script for Jenkins (why is
this so difficult?), I would like to be able to configure the quiet period
on startup, *without needing to configure it through the UI*.
Is there a way of configuring this through groovy? Ideally I would like to
place a
January 5, 2017 at 3:37:54 AM UTC-8, Barry Laffoy wrote:
>>
>> If this is of use to anybody else, I was able to workaround this
>> implementation problem in the jenkinsci/docker with the following:
>>
>> FROM jenkins:2.19.4
>>
>> ARG user=jenkins
>>
to do
it. Cloning the entire jenkinsci/docker repo and setting these build args
directly seems like a better option.
On Wednesday, 4 January 2017 17:05:56 UTC, Barry Laffoy wrote:
>
> Dirk Heinrichs' comments have made me realise that this problem goes both
> ways. Since my host h
.
What I need to be doing is building the jenkinsci/docker image with
"--build-arg uid=$(id -u) --build-arg gid=$(id -g)" to match the container
to the host user.
On Wednesday, 4 January 2017 08:51:41 UTC, Barry Laffoy wrote:
>
> Aha, I understand what you're saying now. There is suc
Aha, I understand what you're saying now. There is such a user on both the
development and the production hosts I'm using, unfortunately. I'll
investigate what can be done to change that.
On Wednesday, 4 January 2017 08:44:45 UTC, Dirk Heinrichs wrote:
>
> Am 04.01.2017 um 09:35 schrieb
socket into docker and away you
> go... of course none of that is written yet... so fit now just hack it
> working
>
> On Tue 3 Jan 2017 at 14:21, Barry Laffoy <laf...@gmail.com >
> wrote:
>
>> Hi
>>
>> I'm trying to set-up our Jenkins master in a repr
ut root & gosu?
Or do you mean to only run the container as a user on host with uid 1000?
On Wednesday, 4 January 2017 07:51:23 UTC, Dirk Heinrichs wrote:
>
> Am 03.01.2017 um 15:21 schrieb Barry Laffoy:
>
> Mounting the key location as volume with `docker run -v
> /path/t
Hi
I'm trying to set-up our Jenkins master in a reproducible way using the
Docker image here: https://github.com/jenkinsci/docker
One problem I am having is how to make ssh private keys (e.g. for polling
git repos) available within the container in a secure manner. Ideally, I
would like to be
gt; error: failed to run repack
Signal 15 is SIGTERM, right? I can't see what has caused that though.
On Thu, Jun 23, 2016 at 11:11 AM, Barry Laffoy <laff...@gmail.com> wrote:
> Hi
>
> I've seen this problem crop up several times in our Jenkins set up.
>
> The Jenkins
Hi
I've seen this problem crop up several times in our Jenkins set up.
The Jenkins git polling will start triggering jobs non-stop for a branch of
git that has already been deleted from origin. The only fix I can find is
to go into the workspace used for polling on all Jenkins slaves/agents
= Jenkins.instance
def evnp = new EnvironmentVariablesNodeProperty();
for (prop in evnp) {
prop.envVars.put("MY_OTHER_NAME", "my_other_value")
}
instance.nodeProperties.add(evnp)
instance.save()
Perfect!
On Tuesday, 3 May 2016 16:02:15 UTC+1, Barry Laffoy wrote:
>
> Hi
>
&
Hi
Does anyone have any advice on using the either of these plugins?
https://wiki.jenkins-ci.org/display/JENKINS/External+scheduler+plugin
https://wiki.jenkins-ci.org/display/JENKINS/REST+Service+Scheduler+Plugin
We're having serious issues with how Jenkins chooses to schedule jobs, and
I
Is it possible to trigger a build of a job from a Build Flow job whose
execution does not block the execution of the calling job?
If that's not clear, say I have three Jenkins jobs: flow-job, short-job,
long-job. "flow-job" is used to trigger a build of both "short-job" and
"long-job".
provide another one
> called experimental. It might help you if you would like to archive those
> artifacts (hpi/jpi) in your internal artifact repo.
>
> I hope it helps
>
> Cheers
>
> On Friday, 25 September 2015 12:45:46 UTC+2, Barry Laffoy wrote:
>>
>>
Hi
Is there any way of managing the plugins installed in Jenkins other than
through the GUI interface?
Ideally I would like to be able to define a list of plugins (names, URLs,
version numbers) in a text file, which would be read by Jenkins and ensure
that the correct plugins are installed
:
Quoting Barry Laffoy laff...@gmail.com:
How can I force Publish Over SSH to work even if the build has been marked
a failure?
Use Send files or execute commands over SSH after the build runs in
configuration section Build environment
--
You received this message because you
Hi
I'd like to publish build artifacts from testing and linting jobs (XMLs,
JSON) to an external server over SSH. To do this, I'm using the Publish
Over SSH plugin. I have a problem though, in that if there are any testing
or linting errors the build is marked as a failure. After this, Publish
I tried wrapping the Publish Over SSH post-build step with a
Flexible-Publish conditional action set to always, but the same outcome
results.
I think that I may have to use scp from bash scripts to do my publishing,
if Jenkins refuses to cooperate.
On Mon, 13 Jul 2015 at 11:31 Barry Laffoy laff
20 matches
Mail list logo
