Re: The pipeline emailextrecipients step takes too long time

It seems emailextrecipients are using 60 seconds for each email it finds. I am going to add the timestamper plugin to see what parts of the debug output from emailextrecipients are taking so long. mandag 27. april 2020 10.39.30 UTC+2 skrev Sverre Moe følgende: > > Well at this point I

Re: The pipeline emailextrecipients step takes too long time

: > > There is no lookup until the email is sent. There may be a call to resolve > a username to the email address though. Are you using ldap or AD? > > On Mon, Apr 27, 2020, 01:39 Sverre Moe > > wrote: > >> Well at this point I am not sending any email, yet. >> I

Re: The pipeline emailextrecipients step takes too long time

esolve usernames >> from the changeset so an email address. It provides an extension point for >> this that other plugins can implement to provide that service. If you are >> having long delays accessing LDAP, that would definitely point to that as a >> culprit for the

Re: The pipeline emailextrecipients step takes too long time

> from the changeset so an email address. It provides an extension point for > this that other plugins can implement to provide that service. If you are > having long delays accessing LDAP, that would definitely point to that as a > culprit for the length of time. > > >

Re: The pipeline emailextrecipients step takes too long time

sets. /Sverre tirsdag 28. april 2020 22.52.06 UTC+2 skrev Sverre Moe følgende: > > > Found this setting in Configure Global Security for LDAP: > Disable Ldap Email Resolver > I ticked it, now I will see if that can help the issue. > > > LDAP Caching: > I had not enabl

Re: The pipeline emailextrecipients step takes too long time

ugging into > Jenkins? > > > > But I guess that email-ext insider Slide might have much better hints… > > > > HTH Reinhold > > > > *From:* jenkins...@googlegroups.com < > jenkins...@googlegroups.com > *On Behalf Of *Sverre Moe > *Sent:* Mi

Re: The pipeline emailextrecipients step takes too long time

My code for finding the changeset authors worked fine. If any developers have wrong email address, then so be it. This solution is much much faster. def getAuthors(build) { final def authors = [] final def changeSets = build.changeSets for (def cs: changeSets) { final def autho

Re: The pipeline emailextrecipients step takes too long time

l directly. > > On Wed, Apr 29, 2020 at 8:18 AM Sverre Moe > wrote: > >> My code for finding the changeset authors worked fine. >> If any developers have wrong email address, then so be it. >> This solution is much much faster. >> >> def getAuthors(bu

Re: RegEx Job Filter for SCM Not Working

difficult to maintain if I had to list each jobs in this file for each view. tirsdag 7. april 2020 10.42.54 UTC+2 skrev Sverre Moe følgende: > > I am trying to get the Regular Expression Job Filter to work with SCM > Configuration. > > Regular Expression: ssh://g...@git.comp

Re: RegEx Job Filter for SCM Not Working

The plugin does not support Pipeline projects for SCM Configuration filtering on RegEx. I have created a change request: https://issues.jenkins-ci.org/browse/JENKINS-62233 mandag 4. mai 2020 11.51.52 UTC+2 skrev Sverre Moe følgende: > > According to documentation it should be possible.

Re: Blue Ocean Pipeline Stages missing

Still seeing this problem. Not on every jobs I wonder if I should report a bug for this. Now running Jenkins LTS 2.222.3 Blue Ocean 1.23.1 torsdag 2. april 2020 kl. 19:09:03 UTC+2 skrev Sverre Moe: > I noticed something odd today. > When I opened Blue Ocean on a recent build I noticed tha

Jenkins Git Init Fails

Cloning Git with an old version of Git now seems to fail Cloning the remote Git repository ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Could not init /home/build/jenkins/workspace/rebuild-packages/base at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(Cli

Re: Jenkins Git Init Fails

d line git versions prior to 2.0 will miss many, many > improvements that have been made to command line git. > > On Wed, Oct 14, 2020 at 10:21 AM Sverre Moe wrote: > >> Cloning Git with an old version of Git now seems to fail >> >> Cloning the remote Git repository ERR

A couple of Git problems

I'm using Git with Jenkins and are having some problems. Have turned off JGit with -Dorg.jenkinsci.plugins.gitclient.Git.useJGit=false, because otherwise it would not work. I'm using the following Git Url in my project settings: ssh:// g...@git.company.com/packages/companyApp.git Problem 1:

Re: A couple of Git problems

chi's "Git polling must die" posting which describes how to improve the responsiveness of your jobs and reduce git polling significantly. Mark Waite From: Sverre Moe To: jenkinsci-users@googlegroups.com Sent: Wednesday, April 17, 2013 7:08 AM Subject: A coup

Re: A couple of Git problems

(yes only the slave node had git) and giving the user jenkins access to the git repository. /Sverre - Original Message - From: "Sverre Moe" To: jenkinsci-users@googlegroups.com Sent: Thursday, 18 April, 2013 8:51:05 AM Subject: Re: A couple of Git problems I have made sur

Adding SSH Site: Cannot connect

Under Jenkins configuration I try to add a SSH site under SSH remote hosts. After adding the host, port, username and password I get the message "Can't connect to server". This ssh site is accessible from the machine Jenkins is running on. I have no problem connecting with ssh on the command li

Matrix build job: Workspace and SCM problem

I have a problem with my Configuration Matrix using Axis builds. My jenkins have 3 different build nodes: Development-opensuse-x86_64 Development-sles-x86 Development-sles-x86_64 I have configured one Multi-configuration jenkins job to build on each of these environments using Axis. *Parent bui

Groovy filterLine() not working in Scriptler

Running the follow code in "Execute Groovy script" works: final def project = buildConfigurationFile.filterLine { it.startsWith(projectLine) }.toString().normalize() However when I add the script in Scriptler and run it in "Scriptler script" it fails. Why is that? Could it be a different vers

Groovy triggering build with both default and new parameters

Groovy Code for triggering a build with a parameter def params = [ new StringParameterValue('UPSTREAM_TRIGGER_CAUSE', 'true') ] def paramsAction = new ParametersAction(params) def cause = new UpstreamCause(build) def futureTask = project.scheduleBuild2(project.quietPeriod, cause, paramsActio

Re: Groovy triggering build with both default and new parameters

rametersAction = new ParametersAction(jobParams) def cause = new UpstreamCause(build) def futureTask = project.scheduleBuild2(project.quietPeriod, cause, parametersAction) However it gets stuck on scheduleBuild2 and does not return. torsdag 26. november 2015 12.38.06 UTC+1 skrev Sverre Moe følgende:

Re: Groovy triggering build with both default and new parameters

Period, cause, parametersAction) torsdag 26. november 2015 13.13.54 UTC+1 skrev Sverre Moe følgende: > > I have tried the following solution: > def property = project.getProperty(ParametersDefinitionProperty.class) > def jobParams = property.getParameterDefinitions(); > > def newP

Trigger build of other projects before this build

I have several projects of type Multi-Configuration. When a project starts a build I have a need to trigger builds of other projects (under certain conditions) before any of the configurations are started. However I cannot see how it would be possible. I have a rather complex workflow: 1) A new

Re: Trigger build of other projects before this build

07.41.08 UTC+1 skrev Baptiste Mathus følgende: > > > Le 7 déc. 2015 1:05 PM, "Sverre Moe" > a > écrit : > > > > I have several projects of type Multi-Configuration. When a project > starts a build I have a need to trigger builds of other projects (under

Save project causes StackOverflowError

After I upgraded to Jenkins 1.640 every time I save a project (any project) is gives me an StackOverflowError A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a com

Re: Save project causes StackOverflowError

When I removed Repository Browser GitWeb I was able to save the project without any problems. onsdag 9. desember 2015 11.34.11 UTC+1 skrev Sverre Moe følgende: > > After I upgraded to Jenkins 1.640 every time I save a project (any > project) is gives me an StackOverflowError >

Groovy save project does not always work

I am not sure what I am doing wrong with my groovy script. I have written a groovy update script to bulk update all my projects. Sometimes it does not take affect when I call project.save() I can open that project configuration page and everything looks right. The updated content is there. However

Re: Groovy save project does not always work

s now shows the environment variables. onsdag 13. april 2016 09.47.23 UTC+2 skrev Sverre Moe følgende: > > I am not sure what I am doing wrong with my groovy script. > I have written a groovy update script to bulk update all my projects. > Sometimes it does not take affect when I

Jenkins 2.0 Upgrade

How can I be sure before upgrade to Jenkins 2.0 that all my installed plugins are still compatible? Has there been any changes to the API that would require me to update my groovy scripts? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To u

Jenkins Pipeline: Plugins that doesn't yet support it

Jenkins Pipeline (former Workflow) looks like a great way to create a specialized build workflow that the standard project types can't do. Currently I am using Multi-configuration projects leveraging templates (Template Plugin) for similar build logic among all projects. Not all plugins have bee

Pipeline with notifyCommit

Using Jenkins Pipeline there is no longer Source Code Management because checkout is handled within the pipeline script. How can i get notifyCommit to work while using Pipeline script? https://jenkins/git/notifyCommit?url=ssh://g...@git.company.com/namespace/projectA.git I know there is an SCM c

Unable to stop pipeline job

After loading a Pipeline script the job froze and I was unable to stop the build. Clicking X had no effect. Restarting Jenkins had no effect. Deleting the job had no effect. A second restart after I deleted the job then the build executor was emptied. This is the output I got when loading a

Pipeline: Keep the main logic outside of Jenkinsfile

What is the best design approach to keeping the Jenkinsfile small (little build logic as possible)? Having close to a hundred projects and several branches on each, then duplicating the pipeline logic within each Jenkinsfile would be a maintenance nightmare. 1) I could put the Pipeline script

Re: Pipeline: Keep the main logic outside of Jenkinsfile

-ci.org/display/JENKINS/Pipeline+Remote+Loader+Plugin > or > https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Shared+Groovy+Libraries+Plugin > ? > > 2016-05-24 16:00 GMT+02:00 Sverre Moe >: > >> What is the best design approach to keeping the Jenkinsfile small (littl

Re: Unable to stop pipeline job

running steps"? > > 2016-05-24 9:08 GMT+02:00 Sverre Moe >: > >> After loading a Pipeline script the job froze and I was unable to stop >> the build. >> Clicking X had no effect. >> Restarting Jenkins had no effect. >> Deleting the job had no effect

Re: Pipeline: Keep the main logic outside of Jenkinsfile

Yes, that explained a lot. Thanks. lørdag 28. mai 2016 02.11.53 UTC+2 skrev Kohsuke Kawaguchi følgende: > > See https://github.com/jenkinsci/workflow-cps-global-lib-plugin > > Hope that helps! > > On Thu, May 26, 2016 at 12:37 AM Sverre Moe > wrote: > >> Yes, I c

Re: Pipeline: Keep the main logic outside of Jenkinsfile

src/com/company/Build.groovy When I tried to push it didn't work sverre@mintaka:~/workspace/workflowLibs> git push --set-upstream origin master fatal: unable to access 'https://build.company.com:8443/workflowLibs.git/': The requested URL returned error: 403 mandag 30. mai 2016 08

Pipeline Global Library vars file naming convention

This naming does not work: vars/packageInformation.groovy I get the following exception when calling a function packageInformation.init() java.lang.NullPointerException: Cannot invoke method init() on null object This works vars/packageinformation.groovy According to the instructions/tutorial o

Re: Pipeline Global Library vars file naming convention

Well if it is a bug. I was not entirely sure as I have just begun using Pipeline. I will create a bug report of this problem. tirsdag 31. mai 2016 12.55.59 UTC+2 skrev Daniel Beck følgende: > > > > On 31.05.2016, at 12:01, Sverre Moe > > wrote: > > > > This n

What I miss with Pipeline: Console output from each node

I have been using Jenkins Multi-configuration. With my move over to Pipeline scripts and Jenkinsfile I still build on multiple nodes/slaves. When building all the nodes in parallel the console output is a mess. It is very difficult to separate the output from a single node. I really miss from Mu

Re: What I miss with Pipeline: Console output from each node

freebsd.org/job/FreeBSD_HEAD/ > > I haven't tried it with pipelines that execute in parallel, so would be > curious as to how it works for you > > -- > Craig > > On Wed, Jun 1, 2016 at 3:07 AM, Sverre Moe > wrote: > > I have been using Jenkins Multi-configur

Re: What I miss with Pipeline: Console output from each node

make the Log in Stage View more readable with label so one could distinguish between steps of "Shell script". However the list of steps within one stage is not structured by which node it executed on. torsdag 2. juni 2016 09.17.04 UTC+2 skrev Sverre Moe følgende: > > I have in

Pipeline: Transfer files via SSH

I need to transfer some files to a server. Have followed the suggestion mention in https://issues.jenkins-ci.org/browse/JENKINS-27963 Tried sshagent with both scp and rsync. Neither works. I have created a Credential for this server in Jenkins. Using rsync sshagent(['repository']) { sh "rsy

Pipeline: Building downstream dependencies

My first predicament: In Multi-configuration build, one single executor can contain multiple parent build, but that single executor can only contain one configuration/axis/slave build at a time. Using Pipeline I am not sure how to get it to work like this. After my Build stage I try to schedule

Re: Pipeline: Transfer files via SSH

nteractive) How does it use the credentials private key from Jenkins in the ssh/scp/rsync command? lørdag 4. juni 2016 15.15.48 UTC+2 skrev Baptiste Mathus følgende: > > Did you try passing the host key checking ssh parameter to "no"? > Le 2 juin 2016 4:10 PM, "Sverre

Re: Pipeline: Building downstream dependencies

ing for an available executor). > > Even the master node has limited executors. What I need is to schedule builds on a flyweight executor since it does not need an actual workspace to perform. Using this will likely allocate a heavyweight executor. node("master") { } fred

Re: Pipeline: Transfer files via SSH

Crendentials. mandag 6. juni 2016 09.06.59 UTC+2 skrev Sverre Moe følgende: > > Using the following with ssh I can disable host key verification > ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no > r...@server.company.com > also > scp -o UserKnownHost

Re: jenkins sequential job

The Build Flow Plugin could build all those jobs in sequence. However it is now deprecated in favor of Jenkins Pipeline. https://github.com/jenkinsci/pipeline-plugin You could create a pipeline/workflow that will build each your jobs in sequence. Or you could use the Promoted Builds Plugin http

Re: Moving a job to a Folder

import com.cloudbees.hudson.plugins.folder.Folder def jenkinsInstance = jenkins.model.Jenkins.getInstance() def newProject = jenkinsInstance.createProject(Folder.class, "my-folder-project") mandag 6. juni 2016 15.17.13 UTC+2 skrev kumar naresh følgende: > > Hi Daniel, > > could you please let m

Multibranch Pipeline: How to parameterize?

Jenkins Pipeline can be parameterized, but not multibranch pipelines. There is no option for "This build is parameterized" in the configuration of a multibranch pipeline. Why is that? I have a multibranch project for each repository with multiple branches. ProjectA master develop re

Re: Moving a job to a Folder

Try the Groovy Postbuild Plugin You could also use the build step "Execute system Groovy script" torsdag 9. juni 2016 08.05.39 UTC+2 skrev kumar naresh følgende: > > > Hi Sverre Moe, > > > thanks that works really good. > > I'm actually trying to add build

Archive multiple artifacts with same name

As I am building on multiple slave nodes I get RPM artifacts from each node. Building on 4 64bit Linux OS, I will get 4 distinct artifacts with the same name. Using ArtifactArchiver will only archive one of those distinct archives and overwrite the previous archived artifact. Considering since

Re: Multibranch Pipeline: How to parameterize?

+2 skrev Sverre Moe følgende: > > Jenkins Pipeline can be parameterized, but not multibranch pipelines. > There is no option for "This build is parameterized" in the configuration > of a multibranch pipeline. Why is that? > > I have a multibranch project for each repos

Re: Pipeline: Transfer files via SSH

ate key for the user build. torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende: > > I need to transfer some files to a server. > Have followed the suggestion mention in > https://issues.jenkins-ci.org/browse/JENKINS-27963 > Tried sshagent with both scp and rsync. Neither wor

Re: Getting started with Pipeline

Pipelines with Jenkinsfile runs in a sandbox and thus you need to approve certain functions. Manage Jenkins -> In-process Script Approval mandag 13. juni 2016 12.32.14 UTC+2 skrev Jerry Steele følgende: > > Thanks for getting me started on this. If you don't mind helping me > troubleshoot, I'll

Re: Pipeline: Transfer files via SSH

jenkins:1.642.1 || echo 'data > container already existing?' " > > """ > } > > 2016-06-13 9:53 GMT+00:00 Sverre Moe >: > >> Am i missing something in my script content? >> sshagent(['repository']) { >> sh 'ssh -Xf bu...@rep

Re: Pipeline: Transfer files via SSH

mandag 13. juni 2016 19.21.10 UTC+2 skrev Thomas Zoratto følgende: > > Hi, > > Try to ssh in verbose mode and you'll know what's happening. > > ssh -v ... > > (The more v you put, the more verbose it will be) > > Le 13 juin 2016 à 15:21, Sverre Moe > a &g

Re: Run pipeline flyweight executors off of master

I don't think you are supposed to do any real work in a flyweight executor. Steps need to be within a node{} which will allocate a heavyweight executor. I use the flyweight executors only to trigger downstream builds. tirsdag 14. juni 2016 02.47.40 UTC+2 skrev Eli White følgende: > > By not runni

Re: Pipeline: Transfer files via SSH

ive shell there is no tty so it fails when trying to ask for > passphrase. > > Le 14 juin 2016 à 08:20, Sverre Moe > a > écrit : > > It looks like it is trying the private key credentials from Jenkins, but > fails. When it fails it tries the public key for the user, then fi

Re: Run pipeline flyweight executors off of master

st whatever user error we feasibly > can. Messing up jenkins files seems like a really easy thing to do. > > It sounds like this ability might not exist. I'll open a JIRA for it. > > On Monday, June 13, 2016 at 11:29:40 PM UTC-7, Sverre Moe wrote: >> >> I don't

Re: Pipeline: Transfer files via SSH

mas Zoratto følgende: > > Ok, then try to ssh manually with full verbose mode (-vvv) > > Le 14 juin 2016 à 08:54, Sverre Moe > a > écrit : > > The private key is actually not password protected. I chose empty password > when I generated the private key on the server. > &

Re: Split Pipeline script into multiple files -- run it without unnecessary nodes

Take a look at Pipeline Global Library https://github.com/jenkinsci/workflow-cps-global-lib-plugin I started with the same problem as you now have and solved it by using global pipeline scripts. These global script are stored in Jenkins git repository workflowLibs.git and can be accessed within

Pipeline: stash includes with git directory

I need the git directory stashed because I need git archive, which does not work unless the git repository is present. I have tried several patterns, but been unsuccessful. stash includes: '**', name: 'root' stash includes: '**/*', name: 'root' stash includes: '**/.*, **/*', name: 'root' stash in

Re: Pipeline: stash includes with git directory

.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ... 1 more torsdag 16. juni 2016 09.59.16 UTC+2 skrev Sverre Moe følgende: > > I need the git d

Change location of workflowLibs.git

Is it possible to change the repository location for workflowLibs.git? The current location is JENKINS_HOME/workflow-libs We have a remote git repository for all our code and utilities. Can we use this central git repository as the remote location for workflowLibs.git? Also perhaps use a differen

Re: Change location of workflowLibs.git

476 > > And I'm also waiting on this ;-) > -- > > > Ludovic SMADJA > R&D engineer - build process and development > JALIOS SA > http://www.jalios.com > > > Le vendredi 17 juin 2016 à 04:16 -0700, Sverre Moe a écrit : > > Is it possible to chan

Re: Change location of workflowLibs.git

es the 'actual' repository for > changes, and pushes changes to Jenkins' internal one, no? > > > On 17.06.2016, at 13:16, Sverre Moe > > wrote: > > > > Is it possible to change the repository location for workflowLibs.git? > > The current l

Pipeline: Stop building all branches after Branch indexing

When performing branch indexing on Multibranch Pipeline I only want it to start building the new branches that become available and not all the other previous added branches. Not sure if this is possible currently. Perhaps add a feature request to make i configurable. -- You received this mes

Re: Multibranch (Pipeline) / Branch tracking

A DRY Jenkinsfile for each branch and put your main build script in the Pipeline Global Library https://github.com/jenkinsci/workflow-cps-global-lib-plugin mandag 20. juni 2016 12.05.07 UTC+2 skrev Christoph M følgende: > > Hi! > > For a new project I want to use the new Pipeline feature. We have

Pipeline: Fails reading build cause

I have tried reading the build cause as suggested in this example https://github.com/jenkinsci/pipeline-examples/tree/master/pipeline-examples/get-build-cause Accessing the build cause outside of a node causes the pipeline to fail right after entering the first stage and without an error or excep

Re: Pipeline: Fails reading build cause

flyweight executor fails or any other heavyweight executor than master. tirsdag 21. juni 2016 08.11.43 UTC+2 skrev Sverre Moe følgende: > > I have tried reading the build cause as suggested in this example > > https://github.com/jenkinsci/pipeline-examples/tree/master/pipeline-examples/get

Re: Multibranch Pipeline: How to parameterize?

perty.setKeepJenkinsSystemVariables(true) property.setKeepBuildVariables(true) property.setInfo(info) project.addProperty(property) project.save() mandag 13. juni 2016 10.20.55 UTC+2 skrev Sverre Moe følgende: > > Either I am doing it wrong, or Multibranch pipeline has no way

Re: Multibranch Pipeline: How to parameterize?

he snippet generator gives me for any of the choices, script, file or content. onsdag 22. juni 2016 08.27.13 UTC+2 skrev Sverre Moe følgende: > > Each branch pipeline has their own config.xml. A standard pipeline job > does have support for parameterization. I think I read somew

Re: Multibranch Pipeline: How to parameterize?

multibranch pipeline. onsdag 22. juni 2016 08.45.18 UTC+2 skrev Sverre Moe følgende: > > Found some clue in https://issues.jenkins-ci.org/browse/JENKINS-32780 > Using the Snippet code generator I was able to generate a build parameter > properties [[$class: 'ParametersD

Pipeline: Defined parameters are not available in the build

Have defined parameter for my pipeline projects in the main pipeline script: properties([[$class: 'ParametersDefinitionProperty', parameterDefinitions: [[$class: 'BooleanParameterDefinition', defaultValue: false, description: 'Description', name: 'PROP_VERIFY') After building the first time

Re: Pipeline: Defined parameters are not available in the build

Seems there is an issue for this https://issues.jenkins-ci.org/browse/JENKINS-30206 I hope for a fix soon. I am stuck without this. onsdag 22. juni 2016 13.13.48 UTC+2 skrev Sverre Moe følgende: > > Have defined parameter for my pipeline projects in the main pipeline > script: >

Re: Pipeline: Defined parameters are not available in the build

mjHL0aA> > > for details. > > The linked issue seem to be a slightly different problem. > > Björn > > Am Mittwoch, 22. Juni 2016 13:13:48 UTC+2 schrieb Sverre Moe: >> >> Have defined parameter for my pipeline projects in the main pipeline >> scrip

Pipeline: Sending email on failed and fixed builds

One benefit with sending email in pipeline script is better control of which error in the pipeline deserves sending email and to whom. By adding a try-catch surrounding the code compile I send out email when it fails. That case the developers get notified only for errors that concern them. try

Re: Pipeline: Sending email on failed and fixed builds

notification similar to what you need > > > https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-test.groovy#L233 > > You need to set and check the currentBuild.result value, and do different > things based on that. > > -- > Craig > > On Thu, J

Re: Pipeline: Defined parameters are not available in the build

It is working. I was just accessing the parameter in a wrong way. Trying env.PARAM does not work. Found an example that lead me to the answer. def param = false if (getBinding().hasVariable("MY_PARAM")) { param = MY_PARAM } onsdag 22. juni 2016 13.37.29 UTC+2 skrev Sverre Mo

Re: Pipeline: Sending email on failed and fixed builds

ot;, subject: SUBJECT, body: CONTENT } /* Must re-throw exception to propagate error */ throw e } torsdag 23. juni 2016 10.07.31 UTC+2 skrev Craig Rodrigues følgende: > > Yes, step mailer sends mail on fixed builds, but currentBuild.result is > null unless you > set it. T

Re: Pipeline: Sending email on failed and fixed builds

I got Mailer to send success after failed. I wish "mail" or "emailext" could support this as those allow to define the subject and body. torsdag 23. juni 2016 10.58.51 UTC+2 skrev Sverre Moe følgende: > > Ok > We went away from the Mailer because we wanted to mi

Cloning workflowLibs.git with ssh

- ssh://USERNAME@server:PORT/workflowLibs.git through Jenkins SSH - http://LOCATION/workflowLibs.git (when your Jenkins app is located on the url http://LOCATION/). As noted in JENKINS-26537

Re: Cloning workflowLibs.git with ssh

Yes, that worked. Thanks. onsdag 29. juni 2016 00.14.07 UTC+2 skrev Kohsuke Kawaguchi følgende: > > You should use your user name on Jenkins. You'll also need to register > your public key on Jenkins. See http://LOCATION/me/configure > > On Tue, Jun 28, 2016 at 3:27 AM

Pipeline: connection is not authenticated

Our git remote server is Gitolite and is has the public key of all the users git clone ssh://g...@git.company.com/project.git This has worked in Jenkins for standard project types, FreeStyle, Maven, Multiconfiguration. The user jenkins Now using Pipeline, it fails to authenticate indexing the add

Re: How to break a pipeline manually?

You could use the error step: error 'Error message' https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#code-error-code-error-signal mandag 30. mai 2016 09.21.16 UTC+2 skrev Feng Yu følgende: > > Hi there: > Here is my pipeline code: > node{ > // my code here > try { >

Re: Pipeline: connection is not authenticated

Is there no way to use Multibranch Pipeline without using stored Credentials on the GitSCMSource? On other project types it is enough that the jenkins user's public key is stored on the git server. onsdag 29. juni 2016 08.54.15 UTC+2 skrev Sverre Moe følgende: > > Our git remot

Re: Pipeline: connection is not authenticated

jenkins' private key (not the git one). > > Björn > > Am Mittwoch, 29. Juni 2016 08:54:15 UTC+2 schrieb Sverre Moe: >> >> Our git remote server is Gitolite and is has the public key of all the >> users >> git clone ssh://g...@git.company.com/project.git >

Multibranch Pipeline: Jenkins View missing last build information

The Jenkins views has no information about "Last Success", "Last Failure" and "Last Duration" for Multibranch Pipelines. It should propagate the result from the last built branch. I could not find any issues for this, so not sure if there is any work in progress to implement it. https://issues.je

Multibranch Pipeline: Checkout hangs on git rev-list

Recently we upgraded Jenkins from 2.100 to 2.103, and a bunch of plugins at the same time. After this we are frequently experiencing checkout scm to freeze at the last step in this process (git rev-list). It will hang there forever, way past the default 10 minutes timeout. Seems we are not the

Re: Multibranch Pipeline: Checkout hangs on git rev-list

> Mark Waite > > On Fri, Feb 2, 2018 at 4:14 PM Sverre Moe > wrote: > >> Recently we upgraded Jenkins from 2.100 to 2.103, and a bunch of plugins >> at the same time. >> After this we are frequently experiencing checkout scm to freeze at the >> last step i

Re: Multibranch Pipeline: Checkout hangs on git rev-list

Just now we got one Multibranch pipeline to hang on git rev-list on a project that has no git tags. Running with latest Jenkins, git plugin, git-client plugin and git. mandag 5. februar 2018 09.17.03 UTC+1 skrev Sverre Moe følgende: > > The problem occurred with the latest version of git

Re: Multibranch Pipeline: Checkout hangs on git rev-list

t plugin. Why is it picking that ancient commit? What does it want to >> do next? I tried adding a debug logger for 'hudson.plugins.git' and Log >> Level 'All' but I don't see anything useful. >> >> >> On Monday, February 5, 2018 at 1:48:25 A

Multibranch Pipeline: no branch checkout

Multibranch Pipeline Branch:RELEASE2 [Pipeline] checkout Cloning the remote Git repository Cloning with configured refspecs honoured and without tags Cloning repository ssh://g...@git.company.com/domain/projectA.git > git init > /home/build/jenkins/workspace/projectA_RELEASE2-UTQNYKNJI6D4OV7ZUB

Re: Multibranch Pipeline: no branch checkout

13. februar 2018 13.56.23 UTC+1 skrev Sverre Moe følgende: > > Multibranch Pipeline > > Branch:RELEASE2 > [Pipeline] checkout > Cloning the remote Git repository > Cloning with configured refspecs honoured and without tags > Cloning repository ssh://g...@git.company.com/doma

Re: BlueOcean observations from user

, and perhaps also how many projects to list before you need to click "Show more". The end user needs to get a better overview without needing to add projects to favorites. fredag 17. november 2017 12.35.23 UTC+1 skrev Sverre Moe følgende: > > Favorites helps a little, but it may

Pipeline: Resource Locking Plugin hangs

Lockable Resource Plugin Lockable Resources Manager Lockable Resources resource: testing1-repository, labels:testing-repository resource: testing2-repository, labels:testing-repository resource: testing3-repository, labels:testing-repository Configured these 3 resources in Jenkin

Re: Pipeline: Resource Locking Plugin hangs

torsdag 8. mars 2018 12.37.47 UTC+1 skrev Reinhold Füreder følgende: > > Very naïve thought(s): > > > > While “*Do not know why nodeName1 acquired the lock before nodeName > released.*“ might be just a matter of output flushing/buffering, > I thought so also, probably because of parallell exe

Tap4j Plugin Exception

Using Tap4j in Jenkins generates Exception in jenkins log output It does not make sense. A class cannot be casted to same class... Mar 08, 2018 1:40:50 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: Error while serving https://build-ci.company.com:8443/view/systems/job/

Re: Pipeline: Resource Locking Plugin hangs

torsdag 8. mars 2018 17.06.12 UTC+1 skrev Sverre Moe følgende: > > > > torsdag 8. mars 2018 12.37.47 UTC+1 skrev Reinhold Füreder følgende: >> >> Very naïve thought(s): >> >> >> >> While “*Do not know why nodeName1 acquired the lock before no

<    1   2   3   4   >