What are the reasons for using "Merging the pull request with the current target branch revision"

GitHub Branch Source Plugin uses "Merging the pull request with the current target branch revision" strategy by default for "Discover pull request". What are the reasons for using it and not "The current pull request revision"? TIA, Vitaly -- You received this message because you are

original git sha when git[hub] commit is merged with master

Using the multibranch source plugin with github and pipelines, I notice that the commit from the github PR will sometimes be merged with remotes/origin/master and that merge commit is what GIT_COMMIT is set to which is what built and tested. I.e.: > git fetch --no-tags --progress

Re: Jenkins pipeline - Remove @tmp folder

Hi, Does anyone know exacly what the @tmp forlders are used for ? Regards, Constantin -- 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 to

Re: monitoring hudson via SNMP

really really old post BUT yes it is easy to turn on JVM SNMP monitoring with jenkins. SNMP is on UDP so you will not be able to use telnet to check is the service running. I made the same mistake at first!! DUH! :-o Use netstat: $ netstat -anp |grep 8020 udp6 0 0 127.0.0.1:8020

Re: Does the SSH Agents plugin support FIPS 140-2?

My recollection from previous times was that FIPS-140-2 compliant implementations must be "certified". I thought that required that a FIPS-140-2 implementation had to be purchased and included into the product that was intended to be FIPS-140-2 compliant. Jenkins has not purchased a FIPS-140-2

RE: Does the SSH Agents plugin support FIPS 140-2?

Thanks for the suggestion! We tried it and the ssh command said it wasn’t allowed to use ed25519 in FIPS mode. We’ve connected via JNLP so perhaps the issue has been sidestepped. Thanks again, Terry From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of

Re: Continuous integration creates a build loop

Hi, It's not the cleanest approach but we get around a similar issue by adding a specific string into the commit message( like "No Build") then in the Jenkinsfile we look for that string and exit if we find it. Tom On Tue, Feb 12, 2019 at 7:24 AM Steven Foster wrote: > I'm not sure what's

Bitbucket Branch Source Plugin version 2.4.0 doesn't find changes in repositories

Hi, The latest version of the Bitbucket Branch Source Plugin does not detect changes when the folder is scanned. Please see: JENKINS-55831 Regards, Carel -- You received this message because you are subscribed to the Google Groups

Re: How to monitor jenkins queue

Hi, Am 12.02.2019 um 19:46 schrieb vit.gorbu...@gmail.com: Is there some reporting tool/plugin that would allow to measure effectivness of queue usage? I would like to show how much time we actually I think you are looking for the load statistics at /load-statistics HTH -- You received this

Multiple `archiveArtifacts` commands in one Jenkins pipeline

Hi everyone! We are facing some issues with our main Jenkins pipeline. It consists of multiple stages which are executed on different machines, and each stage can produce artifacts. We are trying to archive these all by calling the `archiveArtifacts` pipeline command after each stage, but it

Re: Remove config Git Clïent plugin in Global Tool Configuration

Thank you Mark for your reply. I also thought there is'nt really a solution. Op do 7 feb. 2019 om 14:52 schreef Mark Waite : > No, there is not a way to remove the global configuration of an installed > plugin. > > You might be able to write a system groovy script that performs the delete >