Re: Two builds for PRs

2019-03-28 Thread Mark Waite
On Thu, Mar 28, 2019 at 6:22 PM Tom Duerr wrote: > Mark, > The issue only happens when the PR is NOT against a fork. Its been > difficult to debug since most of our developers > use their own forks. > I think that is the same condition I'm using with the git client plugin multibranch

Re: Two builds for PRs

2019-03-28 Thread Tom Duerr
Mark, The issue only happens when the PR is NOT against a fork. Its been difficult to debug since most of our developers use their own forks. I think I'm behind on most of the Pipeline related plugins except for the branch-source plugin. I had attempted a big upgrade of plugins last week that

Re: Two builds for PRs

2019-03-28 Thread Mark Waite
That's quite surprising, since my PR evaluation for the git client plugin on my own fork is running with GitHub and is only showing the 'pr-merge' job. Is the second job visible when executing in the Jenkins multibranch folder? If so, then I'm puzzled, because you're seeing something that I'm

Re: Two builds for PRs

2019-03-28 Thread Tom Duerr
Mark, I already have the "Exclude branches that are also filed as PRs" set. Guess that's part of my confusion. On Thu, Mar 28, 2019 at 4:58 PM Mark Waite wrote: > It might also work to filter branches based on the branch name at some > level, but that's more complicated that changing the

Re: Two builds for PRs

2019-03-28 Thread Slide
That's correct, it mentions in the help about filtering for PR builds and so forth. On Thu, Mar 28, 2019 at 4:37 PM Tom Duerr wrote: > Slide, thanks for the quick response as well. > Is this the setting you're referring to? > https://imgur.com/f2dDD2v > > > > > > On Thu, Mar 28, 2019 at 4:28 PM

Re: Two builds for PRs

2019-03-28 Thread Mark Waite
It might also work to filter branches based on the branch name at some level, but that's more complicated that changing the "Discover branches" setting in the plugin. Picture looks like this: [image: image.png] On Thu, Mar 28, 2019 at 5:22 PM Slide wrote: > This would generally be the branch

Re: Two builds for PRs

2019-03-28 Thread Tom Duerr
Slide, thanks for the quick response as well. Is this the setting you're referring to? https://imgur.com/f2dDD2v On Thu, Mar 28, 2019 at 4:28 PM Tom Duerr wrote: > Mark, thanks for the quick response. > My settings are here. > https://imgur.com/eDfxW45 > > I guess Im a little confused by

Re: Two builds for PRs

2019-03-28 Thread Tom Duerr
Mark, thanks for the quick response. My settings are here. https://imgur.com/eDfxW45 I guess Im a little confused by the options. Tom On Thu, Mar 28, 2019 at 4:19 PM Mark Waite wrote: > I thought that was an indication that the GitHub branch source is defined > to both create a job for each

Re: Two builds for PRs

2019-03-28 Thread Slide
This would generally be the branch filter parameter wouldn't it? You'd want to filter on the pr-* and master braches On Thu, Mar 28, 2019, 16:20 Mark Waite wrote: > I thought that was an indication that the GitHub branch source is defined > to both create a job for each branch and for each pull

Re: Two builds for PRs

2019-03-28 Thread Mark Waite
I thought that was an indication that the GitHub branch source is defined to both create a job for each branch and for each pull request. I think you need to reconfigure the job to not build a branch if it has a matching pull request. On Thu, Mar 28, 2019 at 5:17 PM Tom Duerr wrote: > Jenkin

Two builds for PRs

2019-03-28 Thread Tom Duerr
Jenkin 2.138 Branch-Source plugin 2.4.2 SCM=Github Enterprise Amazon Linux Hi, We've recently started converting from freestyle jobs to Jenkinsfile/pipelines. We're seeing odd behaviors when pull requests(PR) are created directly from our main repo and not from a fork of the repo.

Re: Passing the vaiable to Email Extension plugin

2019-03-28 Thread Slide
It looks like you might be mixing up some usages..if the variable is an environment variable (and that is the only type that will work in a template), you'd want to do something like this: <% ENV(var:"MYTOOL_VERSION") %> This may only work with the most recent email-ext version. On Thu, Mar 28,

Re: POSTing zip file using httpRequest in Jenkinsfile

2019-03-28 Thread Anonymous
Does someone solve this issue ? I feel like requestBody isn't working at all. However if I'm making a "basic" POST request with query like "http://localhost:5000/api?id=1; it does work.. Le lundi 30 janvier 2017 22:04:13 UTC+1, Christopher Burke a écrit : > > Hey everyone > >Part of my

Viewing Performance Plugin Result Graphs slows down jenkins

2019-03-28 Thread 'Kay J' via Jenkins Users
Hello everyone, I'm using latest jenkins LTS as well as up to date plugins. Plugins installed are nothing fancy: Pipeline, Github PR, Git and additional tools like timestamper etc. Problem: When viewing performance test result graphs, created by performance plugin, we sometimes get very high

Unable to login to jenkins with valid credentials

2019-03-28 Thread Ghulam Alekuzei
I'm having trouble in signing in to our Jenkins Server with any valid credentials. First I thought there is some problem with 1 of the credentials, so I turned off the security through config.xml and reset the password through GUI and also proof-checked that passwordhash has changed in

Passing the vaiable to Email Extension plugin

2019-03-28 Thread kalkin powale
Hi All, I wish to send some parameter/ variable from the current build job to the Email template to send it in an email. I have saved my email template as Manage_Jenkins>> Managed_Files >> custom_groovy_Email.groovy in email template, I am trying to use it as follows Duration:

Re: How to use the saveOutput option of emailext plugin in a pipeline

2019-03-28 Thread Jinlxz Liu
Thank you, Victor On Thursday, March 28, 2019, Victor Martinez wrote: > I just raised https://issues.jenkins-ci.org/browse/JENKINS-56794 > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop

Re: How to use the saveOutput option of emailext plugin in a pipeline

2019-03-28 Thread Victor Martinez
I just raised https://issues.jenkins-ci.org/browse/JENKINS-56794 -- 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 jenkinsci-users+unsubscr...@googlegroups.com.

Re: How to use the saveOutput option of emailext plugin in a pipeline

2019-03-28 Thread Victor Martinez
You are right! I took the wrong path to search for the code but without reading the specific code for the pipeline itself. So it's not supported I'm afraid! Sorry If I mislead you -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To

Re: Lost all views after upgrading from 2.73.3 to 2.107.3

2019-03-28 Thread Roshan Chandekar
Sequence matters. If you upgrade the Jenkins version first and then plugin upgrade that don't help. I followed below sequence and that helped me to fix the problem upgrade the plugin first from 2.73.3 UI without restart and then copy the 2.138 war to Jenkins home and then restart the Jenkins.

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

2019-03-28 Thread Roshan Chandekar
If you upgrade the Jenkins version first and then plugin upgrade that don't help. I followed below sequence and that helped me to fix the problem upgrade the plugin first from 2.73.3 UI without restart and then copy the 2.138 war to Jenkins home and then restart the Jenkins. Got all my view

Re: How to use the saveOutput option of emailext plugin in a pipeline

2019-03-28 Thread Jinlxz Liu
Hi Victor, I checked the workspace after the pipeline job was executed, but there was no html file under it. I added some loggers to capture the logs of emailext plugin and executed the plugin again, I received the email, but no output was captured for the logger, the configuration is as