Thanks for the link to that issue. But it is not really the issue I am having.
I am not using the CMake build step, but only using it to get the tool in the
path and get auto installers.
Same for the custom tools. Both custom tools and CMake work in the Scripted
Pipeline job type but I can't
It seems that the Declarative Pipeline (Pipeline Model Definition) does not
support some important tools with the "tools" block, in particular the
CMake tool and custom tools.
I tried all combinations I could find of things like
tools {
I have this problem, too. I assume there must be a more modern solution to
the problem of configuration management and tracking, because this is
shockingly bad.
On Thursday, May 14, 2015 at 5:07:41 PM UTC-7, dougla...@gmail.com wrote:
>
> I couldn't find any way of entering Git credentials that
Hi,
I want to setup a jenkins job which takes 2 parameters which take IP
addresses and host names from the user and then iterates over the IPs to
run curl.
So a user can enter one ore more values for IP and VM Name.
IP=aa.bb.cc.dd ee.ff.gg.hh (new line separated)
HOST_NAME=hostname1 hostname2
It is not supported:
https://issues.jenkins-ci.org/browse/JENKINS-34998
From: on behalf of Colin Bennett
Reply-To: "jenkinsci-users@googlegroups.com"
Date: Thursday, February 16, 2017 at 2:56 PM
To:
"scripted" Pipeline simply uses typical programmatic "if" construct.
Declarative makes this more, well, declarative and is a bit different for
readability purpose.
Le 9 févr. 2017 1:52 PM, "Roi Aldaag" a écrit :
> Thanks Tyler for your prompt response!
>
> Just to make it
Hi all,
I am using withCredentials in pretty much every one of my stages and I
would like to know if there is a way to only call it once.
I found a topic [JENKINS-37823] mentionning the wrapper section (now
deprecated in favor of the options directive) but options does not
recognize
Hello,
wanted to ask for help with creating docker service from pipeline. For now
I'm running my app stack from compose file on a single node.
Created a swarm cluster (1.13.1) and wondering how can I create each
component of this compose file as a standalone service from pipeline.
When I do
Hi,
I get an error when I try to execute a job on a windows slave.
I added the error log below.
I seems that depending on how I start the windows salve – the error occurs
or not.
I want to start the slave via execution command on the master, like this*
ssh -v mcetestuser@20-MCE-UT2
There is no support yet for swarm mode AFAIK
On Thu, Feb 16, 2017 at 10:06 AM, Denis J. Cirulis
wrote:
> Hello,
>
> wanted to ask for help with creating docker service from pipeline. For now
> I'm running my app stack from compose file on a single node.
> Created a
it should technically be possible to do it through the groovy console...
but I would not try unless the bet was large enough to justify the
considerable effort... especially when writing a plugin to do it will give
you IDE autocompletion and would take *me* maybe 5 minutes compared with at
least
Question: why can't you use the Gradle wrapper? This allows you to rely
only on a JDK. No need to rely on a Gradle installation.
On Thursday, 16 February 2017 09:34:34 UTC+1, Bill Dennis wrote:
>
> Yes, I did all that gradle configuration. 'GRADLE_LATEST' is the label we
> used for our gradle
Yes, I did all that gradle configuration. 'GRADLE_LATEST' is the label we used
for our gradle installation. We name it that way so every time we update to the
latest gradle, we don't need to change all our jobs that we want to be on the
latest gradle version. We also use gradle version specific
Hi Stephen,
thank you for the answer!
Still, the question is: is there a way to do the thing (without plugin),
and how, if the answer is 'yes'?
wbr, Alexander.
On Wednesday, February 1, 2017 at 3:14:48 PM UTC+7, Stephen Connolly wrote:
>
> Writing a plugin would be easier than your suggested
Hi all -
I have a docker host. Jenkins ssh's (as the user jenkins) to this host via
pipeline steps and builds apps inside the specified docker image. This all
pretty much flows as planned. However... when the pipeline executes a
"docker.insdie" or via pipeline -> agent -> docker, the
In case anyone else is playing along (or for future me), I fixed the first
problem by specifying "master" instead of "*" for branches to build:
[image: Inline images 1]
It noticed force pushes after that too. And I discovered that the plugin
was listening
This is by design. If the build process doesn't run as host's user
"jenkins" then this would corrupt the workspace with files one can't
read/delete later
The fact the jenkins user doesn't exists isn't an issue.
You should prepare your docker image so it let arbitrary user create
content under
Can I set the go path in the pipeline? Is it just a matter of an "sh"
step. Or is there a more elegant way to pass that variable to the docker
run?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop
Hi -
It is designed like that. Jenkins is masking the credentials details in the
logs by design as you might not want them visible there. If you echo the
credentials details to a file kept in the workspace, you should see the
actual values in the file. That is how I check it for debugging.
A jenkins pipeline calls an API that returns metrics and prints it in the
console output with formatting. However, Jenkins pipeline prints standard
output for each command like below: How to disable this or turn it off?
Hide quoted text
[Pipeline] sh
[Rel _pipeline] Running shell script
https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs
might help you
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
IIUC you're trying to use the FS somehow. In general don't do this because
you're tying yourself to internals that may change anytime (and could never
work as soon as you're starting to use many different agents for those
jobs).
Google for "copy artifacts plugin"
Le 7 févr. 2017 2:48 PM, "Moshe
For future reference I discovered this issue is fixed by gradle plugin
v1.26 - this issue: https://issues.jenkins-ci.org/browse/JENKINS-37394
On Thursday, 16 February 2017 02:40:42 UTC, Bill Dennis wrote:
>
> Hi -
>
> I'm looking to use gradle to run tests in declarative pipeline jobs.
>
>
Nice to know.
Thank you
From: on behalf of Bill Dennis
Reply-To: "jenkinsci-users@googlegroups.com"
Date: Thursday, February 16, 2017 at 9:40 AM
To: Jenkins Users
If a freestyle job, pass a boolean param (or even a yes/no string), then
use the "conditional build step plugin" to make basically a if on the param
value.
HTH
Le 8 févr. 2017 10:39 PM, a écrit :
Hello all,
I am new to jenkins
I have a jenkins build running on a
> On 07.02.2017, at 14:48, Moshe Zuisman wrote:
>
> %workspace%../../../label=windows2012Aws_ONE_LOCAL_MSSQL
Doing things like that will prevent you from starting to build on agents, e.g.
to reduce the load on the master, or to implement more restrictive security. So
this
I found the problem by myself.
It was indeed wrong access rights to C:\╗Windows.
I was not able to create files in that directory - after disablig UAC by
the following
it works.
Press keys “Windows Key + R”, type regedit
Locate
Le 9 févr. 2017 4:38 PM, "Omeka" a écrit :
Previously the current LTS of jenkins would not work with docker 1.12
because of this issue https://github.com/maxfields2000/dockerjenkins_
tutorial/issues/20
Has anyway here tested jenkins LTS with the Docker 1.13?
Is there a way
28 matches
Mail list logo