You want to do something like this:
def GIT_VER = sh(returnStdout: true, script: 'git tag... | tail -n1')
Each invocation of sh will have it's own environment space.
On Fri, Oct 19, 2018, 15:12 wrote:
> Hi,
> I have the following steps in my jenkinsfile that work pretty well with
>
Hi,
I have the following steps in my jenkinsfile that work pretty well with
$GIT_VER=some number in the following step only.
stage('Git Checkout') {
steps {
git(url: 'ssh://mygit/my.git', branch: 'develop')
sh '''export GIT_VER=$(git tag -l [0-9].* --points-at
As per the documentation of that plugin, below, the moment I grant access
to ^foo.* they'll be able to see everything under foo right? In my case,
everything under 'A'. Or, may be am not getting it right. Could you
please help me on how to set it up?
First, assign that user/ group to read/
> On 19. Oct 2018, at 19:16, gotviser...@gmail.com wrote:
>
> We are using https://wiki.jenkins.io/display/JENKINS/Role+Strategy+Plugin
> this plugin. Unfortunately, as per this plugin we can only restrict users
> from other team to modify the jobs. Cannot completely hide the jobs. Any
>
Hello,
I'm trying to set up a Jenkins master to use another server as a Jenkins
agent host, running Docker containers on the host for different
environments.
My master is running jenkinsci/blueocean. The agent host server is running
Docker with tcp://0.0.0.0:2376 open.
TL;DR Question: Why
Could someone help me?
Em terça-feira, 16 de outubro de 2018 18:51:47 UTC-3, Paulo Diniz escreveu:
>
> Hello everyone.
>
> I have a Jenkins project, with build in Maven for an IBM WebSphere
> Application Server.
> I added the WebSphere Deployer Plugin to my Jenkins.
> Assigns the WebSphere
Hi,
We have the following requirement. Any recommendations?
We have a Folder 'A' created in Jenkins for an application team 'A'. We
have two subdivision under this application team 'A1 and A2'. There are 4
users, 2 under each subdivision - A1-User1, A1-User2 and A2-User1,
A2-User2. Both
This is supposed to only show when Jenkins detects an upgrade from 1.495 or
older. IIRC, it uses information from the global config.xml to determine that.
Any scripting messing with this file could be a possible culprit.
I recommend not executing this. I'm not sure whether the format of secrets
We recently upgraded Jenkins from 2.146 to 2.147 (which is the newest release
at the time of writing).
Since then, Jenkins has displayed a message in the WebUI:
"Because of a security vulnerability discovered earlier, we need to change the
encryption key used to protect secrets in your
There is a message that makes it clear it was not supposed to be installed
on non-evergreen instances, but for some reason, it's removed
Filed https://issues.jenkins-ci.org/browse/JENKINS-54167 to fix it and make
it clearer for users this plugin must not be installed by anyone manually.
Le ven.
(replies inline)
On Thu, 18 Oct 2018, gotviser...@gmail.com wrote:
> My Jenkins is not a docker setup. Can I still use this? I found a plugin
> and installed it. But getting this error
The Evergreen plugin is not useful when installed in a non-Jenkins Evergreen
instance. That plugin only
Hi there,
We are using Jenkins to deploy to a Windows Server and we would like to
push a PowerShell script through ssh with the ssh-step plugin
(https://jenkins.io/doc/pipeline/steps/ssh-steps/) and the sshstep
But I can't seam to put the deploy file on a certain drive path - I only
manage it
Hello,
Is it possible to access the folder properties of the folder within the
pipeline job.
Like for example: Let's say I use a folder property with name and value
like the following:
NAME = VERSION
VALUE =2?
Can I access this in the jenkins pipeline jobs created within the folder
--
You
13 matches
Mail list logo
