Hello everyone,
I have following set up in my Jenkins instance (Version 2.240):
A Maven setting.xml is stored in Managed File -> Global Maven Settings.xml.
In Managed Jenkins -> Managed Tools, this settings.xml is set in Maven
configuration -> Default global settings provider -> Provided global
My colleague pointed me in.
The trick is to iterate over all CredentialsProvider and filter by id:
@Field
def privateToken = CredentialsProvider
.lookupCredentials(StandardCredentials, (Item) null, ACL.SYSTEM)
.find { it.id == "gitlab-api" }
.apiToken
Am Freitag, 15. Mä
Hello,
I'm currently programming a Seed Job that requests via REST API a list of
repositories from a Gitlab instance. I want to iterate this list and create
a pipeline job for each repository. My idea is to use Gitlab plugin and
Credential Plugin for storing the API token and the Job DSL plugin
Hello Mailinglist,
is it possible to run a pipeline script on all Jenkins nodes?
Thanks and best regards,
Sandra
--
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
Hello,
I'd like to change the current workspace in a pipeleine script. My naive
approach is the following script
pipeline {
agent any
environment {
WORKSPACE = '/home/sparsick'
}
stages {
stage('Build') {
steps {
sh 'echo $WORKSPACE'
I have tried the Multi Branch Pipeline plugin. In my case it have't worked
because I have to increase the timeout for cloning and at the moment it is
not possible to increase the timeout because of a bug
(https://issues.jenkins-ci.org/browse/JENKINS-31924).
At the end I could solve my problem
Thank you for your replies. I will try out both advices.
Am Dienstag, 24. Mai 2016 20:19:10 UTC+2 schrieb David Karlsen:
>
> afaik the post-deploy step is specific to a maven-type job
> specifically, so you just need to run a normal maven command.
> You could also try this option
>
> http:/
Hello,
I have following problem and maybe someone has a good idea how I can solve
it.
I have a Git repository with several branches. I'd like to bring all
branches under CI control. That means, after every push to the repository,
indepentent in which branch, a job should check whether the
