[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title vinoth SS commented on JENKINS-47496 Re: No automatic builds for tags I found some issue on Build strategy plugin for tags, if i specify Ignore tags newer than to 1 days, no automated builds are triggering, if i specify only 7 days builds are triggering, can we have that restriction to 1 day as well. so that automated builds will trigger only for tags which created less than 1 day. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.16455.1559191680599%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Devin Lane commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ I just worked through this issue today and have found a reasonable solution. First, the problem lies in the way that Jenkins makes a connection to the slave; apparently, the "checkout" command uses an environment obtained from a non-interactive login, and BEFORE environment from Jenkins node config takes place. The rest of the build uses a "normal" environment so you may find that git lfs commands work there. One method of fixing this is to alter /etc/ssh/sshd_config (for macOS), set "PermitUserEnvironment" to YES, then restart sshd. Next, edit /Users/Jenkins/.ssh/environment and set PATH="$PATH:/usr/local/bin" etc as required. Finally, have Jenkins reconnect to the slave to pick up the new environment. More details at https://support.cloudbees.com/hc/en-us/articles/229724088-How-to-set-up-a-Jenkins-agent-to-have-the-same-path-as-the-user-when-connected-via-Remote-Desktop- Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192786.1533214686000.16433.1559188020470%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Devin Lane edited a comment on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ I just worked through this issue today and have found a reasonable solution. First, the problem lies in the way that Jenkins makes a connection to the slave; apparently, the "checkout" command uses an environment obtained from a *non-interactive* login, and BEFORE environment from Jenkins node config takes place. The rest of the build uses a "normal" environment so you may find that git lfs commands work there. One method of fixing this is to alter /etc/ssh/sshd_config (for macOS), set "PermitUserEnvironment" to YES, then restart sshd. Next, edit /Users/Jenkins/.ssh/environment and set PATH="$PATH:/usr/local/bin" etc as required. Finally, have Jenkins reconnect to the slave to pick up the new environment. More details at [https://support.cloudbees.com/hc/en-us/articles/229724088-How-to-set-up-a-Jenkins-agent-to-have-the-same-path-as-the-user-when-connected-via-Remote-Desktop-] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192786.1533214686000.16444.1559188020629%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title Satoshi Goto commented on JENKINS-56854 Re: ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub but this is expected behavior for the current version. Okay. I closed this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198514.155421873.16429.1559184120130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title Satoshi Goto updated JENKINS-56854 Jenkins / JENKINS-56854 ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub Change By: Satoshi Goto Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198514.155421873.16426.1559184060282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed
Title: Message Title Shubham Mishra commented on JENKINS-55618 Re: When using spot instances, requests 3-4 nodes when one is needed Thanjs Vladislav Naumov, I will check and test it. BTW do we need to downgrade the jenkins version also because as of now I am using jenkins version 2.138 and ec2 plyugin version is 1.43. Please suggest. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196789.1547639731000.16409.1559182200388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title Liam Newman commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits John Gaunt Ah, I see. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186379.1510079108000.16403.1559180340389%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Jesse Glick commented on JENKINS-57634 Re: GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Some historical suggestions can be found in JENKINS-36089. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199564.1558605601000.16400.1559179980171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Liam Newman commented on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing Bryce Schober Thanks for filing a new JIRA for that issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171936.1466038064000.16361.1559179800684%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57164) Allow Users to include/exclude paths from Multibranch SCM Triggering
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-57164 Allow Users to include/exclude paths from Multibranch SCM Triggering Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198914.1556077222000.16359.1559178840190%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44360) '%' in branch name causes GitHub multi-branch job failures
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-44360 '%' in branch name causes GitHub multi-branch job failures Change By: Mark Waite A '%' character in a branch name breaks the GitHub API calls on a git repository if the job performing the clone is generated by GitHub Organization Folder plugin (windows or Linux) or the GitHub branch source (windows master or agent only Linux ).Steps to duplicate the problem:# Define a GitHub multibranch PIpeline job referencing the MarkEWaite/jenkins-bugs repository (or a GitHub Organization Folders job which references the GitHub organization MarkEWaite, looking only at the repository jenkins-bugs)# Scan the repository, watch the jobs run# Open the has-percent-%-JENKINS-44360 job and confirm it failed to cloneSteps to show the same branch working with a multibranch pipeline:# Define a multi-branch pipeline job using the MarkEWaite/jenkins-bugs github repo using Git as the branch source rather than GitHub# Scan the repository, watch the jobs run# Open the has-percent-%-JENKINS-44360 job and confirm it cloned successfullyThe issue seems to require:* GitHub Organization Folders or GitHub multibranch* '%' in the branch name on the repository Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-44360) '%' in branch name causes GitHub multi-branch job failures
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-44360 '%' in branch name causes GitHub multi-branch job failures Change By: Mark Waite A '%' character in a branch name breaks clone the GitHub API calls on a git repository if the job performing the clone is generated by GitHub Organization Folder plugin (windows or Linux) or the multi- GitHub branch plugin source (windows master or agent only). The same character in the same branch does not break clone with a multi-branch pipeline automatically defined job on Linux. Steps to duplicate the problem:# Define a GitHub multibranch PIpeline job referencing the MarkEWaite/jenkins-bugs repository (or a GitHub Organization Folders job which references the GitHub organization MarkEWaite, looking only at the repository jenkins-bugs ) # Scan the repository, watch the jobs run# Open the has-percent-%-JENKINS-44360 job and confirm it failed to cloneSteps to show the same branch working with a multibranch pipeline:# Define a multi-branch pipeline job using the MarkEWaite/jenkins-bugs github repo using Git as the branch source rather than GitHub # Scan the repository, watch the jobs run# Open the has-percent-%-JENKINS-44360 job and confirm it cloned successfullyThe issue seems to require:* GitHub Organization Folders or GitHub multibranch * '%' in the branch name on the repository Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-44360) '%' in branch name causes GitHub multi-branch job failures
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-44360 '%' in branch name causes GitHub multi-branch job failures Change By: Mark Waite Summary: '%' in branch name causes Windows GitHub multi-branch job failures Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182170.1495170253000.16339.1559176140863%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51454) Pipeline retry operation doesn't retry when there is a timeout inside of it
Title: Message Title
Basil Crow commented on JENKINS-51454
Re: Pipeline retry operation doesn't retry when there is a timeout inside of it
As a workaround, I was able to catch FlowInterruptedException and rethrow a more generic exception:
import org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
retry(3) {
try {
timeout(time: 10, unit: 'MINUTES') {
[..]
}
} catch (FlowInterruptedException e) {
// Work around https://issues.jenkins-ci.org/browse/JENKINS-51454
error 'Timeout has been exceeded'
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190810.1526899694000.16323.1559175840196%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51454) Pipeline retry operation doesn't retry when there is a timeout inside of it
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-51454 Pipeline retry operation doesn't retry when there is a timeout inside of it Change By: Basil Crow Assignee: Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190810.1526899694000.16314.1559175720676%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51454) Pipeline retry operation doesn't retry when there is a timeout inside of it
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-51454 Pipeline retry operation doesn't retry when there is a timeout inside of it Change By: Basil Crow Component/s: workflow-basic-steps-plugin Component/s: pipeline-model-definition-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190810.1526899694000.16304.1559175720513%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51454) Pipeline retry operation doesn't retry when there is a timeout inside of it
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-51454 Pipeline retry operation doesn't retry when there is a timeout inside of it Change By: Basil Crow Summary: Declarative pipeline Pipeline retry operation doesn't retry when there is a timeout inside of it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190810.1526899694000.16284.1559175660567%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51454) Pipeline retry operation doesn't retry when there is a timeout inside of it
Title: Message Title
Basil Crow updated an issue
Jenkins / JENKINS-51454
Pipeline retry operation doesn't retry when there is a timeout inside of it
Change By:
Basil Crow
When a declarative {{timeout}} call is fired inside of a {{retry}}, *retry is not being triggered* and *job execution is aborted*, the only way to make it work is by surrounding the {{timeout}} operation with a {{try/catch}}.h3. without try/catchLog output {code}Cancelling nested steps due to timeout{code}Execution result{code}Timeout has been exceededFinished: ABORTED{code}h3. with try/catchLog output {code}Timeout set to expire after 2 sec without activitySleeping for 2 secCancelling nested steps due to timeoutERROR: catched timeout! org.jenkinsci.plugins.workflow.steps.FlowInterruptedExceptionRetrying{code}Execution result{code}Finished: SUCCESS{code} h2. Examples to reproduce the issueh3. Failing example{code:java}node {def timeoutSeconds = 3stage('Preparation') { // for display purposesretry(3){timeout(activity: true, time: 2, unit: 'SECONDS') {sleep(timeoutSeconds)}timeoutSeconds--} }}{code}h3. Working example{code:java}node {def timeoutSeconds = 3stage('Preparation') { // for display purposesretry(3){try{timeout(activity: true, time: 2, unit: 'SECONDS') {sleep(timeoutSeconds)}}catch(err){timeoutSeconds--script{ def user = err.getCauses()[0].getUser() error "[${user}] catched timeout! $err"}}} }}{code}
Add Comment
[JIRA] (JENKINS-44360) '%' in branch name causes Windows multi-branch job failures
Title: Message Title
Mark Waite edited a comment on JENKINS-44360
Re: '%' in branch name causes Windows multi-branch job failures
I continue to see job failures when using a branch name containing '%' with either a GitHub organization folder or a GitHub branch source. I don't see those job failures when I use Git as a branch source, only if I use GitHub as the branch source or a GitHub organization folder. I haven't checked Bitbucket branch source or Gitea to see if the issue is specific to GitHub or is connected to something unrelated to the branch API plugin.The failing job writes the following surprising log file into {{build/1/log}}:{noformat}Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password)java.io.FileNotFoundException: https://api.github.com/repos/MarkEWaite/jenkins-bugs/git/refs/heads/has-percent-%-JENKINS-44360at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243)at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)at org.kohsuke.github.Requester.parse(Requester.java:625)at org.kohsuke.github.Requester.parse(Requester.java:607)at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException:... Long content that looks like an HTML file ...at org.kohsuke.github.Requester.handleApiError(Requester.java:699)at org.kohsuke.github.Requester._to(Requester.java:306)at org.kohsuke.github.Requester.to(Requester.java:247)at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891)at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1531)at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582)at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98)at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}I've uploaded {{build/1/log}} as [^JENKINS-44360.log] The specific branch that shows the failure is in my [jenkins-bugs GitHub repository|https://github.com/MarkEWaite/jenkins-bugs/tree/has-percent-%25-JENKINS-44360].
Add Comment
[JIRA] (JENKINS-44360) '%' in branch name causes Windows multi-branch job failures
Title: Message Title
Mark Waite edited a comment on JENKINS-44360
Re: '%' in branch name causes Windows multi-branch job failures
I continue to see job failures when using a branch name containing '%' with either a GitHub organization folder or a GitHub branch source. I don't see those job failures when I use Git as a branch source, only if I use GitHub as the branch source or a GitHub organization folder. I haven't checked Bitbucket branch source or Gitea to see if the issue is specific to GitHub or is connected to something unrelated to the branch API plugin.The failing job writes the following surprising log file into {{build/1/log}}:{noformat}Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password)java.io.FileNotFoundException: https://api.github.com/repos/MarkEWaite/jenkins-bugs/git/refs/heads/has-percent-%-JENKINS-44360at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243)at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)at org.kohsuke.github.Requester.parse(Requester.java:625)at org.kohsuke.github.Requester.parse(Requester.java:607)at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException:... Long content that looks like an HTML file ...at org.kohsuke.github.Requester.handleApiError(Requester.java:699)at org.kohsuke.github.Requester._to(Requester.java:306)at org.kohsuke.github.Requester.to(Requester.java:247)at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891)at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1531)at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582)at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98)at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}I've uploaded {{build/1/log}} as [^JENKINS-44360.log]The specific branch that shows the failure is in my [jenkins-bugs GitHub repository|https://github.com/MarkEWaite/jenkins-bugs/tree/has-percent-%25-JENKINS-44360].
Add Comment
[JIRA] (JENKINS-44360) '%' in branch name causes Windows multi-branch job failures
Title: Message Title
Mark Waite edited a comment on JENKINS-44360
Re: '%' in branch name causes Windows multi-branch job failures
I continue to see job failures when using a branch name containing '%' with either a GitHub organization folder or a GitHub branch source. I don't see those job failures when I use Git as a branch source, only if I use GitHub as the branch source or a GitHub organization folder. I haven't checked Bitbucket branch source or Gitea to see if the issue is specific to GitHub or is connected to something unrelated to the branch API plugin.The failing job writes the following surprising log file into {{build/1/log}}:{noformat}Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password)java.io.FileNotFoundException: https://api.github.com/repos/MarkEWaite/jenkins-bugs/git/refs/heads/has-percent-%-JENKINS-44360at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243)at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)at org.kohsuke.github.Requester.parse(Requester.java:625)at org.kohsuke.github.Requester.parse(Requester.java:607)at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException:... Long content that looks like an HTML file ...at org.kohsuke.github.Requester.handleApiError(Requester.java:699)at org.kohsuke.github.Requester._to(Requester.java:306)at org.kohsuke.github.Requester.to(Requester.java:247)at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891)at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1531)at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582)at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98)at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat} I've uploaded {{build/1/log}} as [^JENKINS-44360.log]
Add Comment
[JIRA] (JENKINS-44360) '%' in branch name causes Windows multi-branch job failures
Title: Message Title Mark Waite commented on JENKINS-44360 Re: '%' in branch name causes Windows multi-branch job failures I continue to see job failures when using a branch name containing '%' with either a GitHub organization folder or a GitHub branch source. I don't see those job failures when I use Git as a branch source, only if I use GitHub as the branch source or a GitHub organization folder. I haven't checked Bitbucket branch source or Gitea to see if the issue is specific to GitHub or is connected to something unrelated to the branch API plugin. The failing job writes the following surprising log file into build/1/log: Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password) java.io.FileNotFoundException: https://api.github.com/repos/MarkEWaite/jenkins-bugs/git/refs/heads/has-percent-%-JENKINS-44360 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285) Caused: org.kohsuke.github.GHFileNotFoundException: ... Long content that looks like an HTML file ... at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1531) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE Add Comment
[JIRA] (JENKINS-44360) '%' in branch name causes Windows multi-branch job failures
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-44360 '%' in branch name causes Windows multi-branch job failures Change By: Mark Waite Attachment: JENKINS-44360.log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182170.1495170253000.16246.1559174820611%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44360) '%' in branch name causes Windows multi-branch job failures
Title: Message Title Mark Waite updated JENKINS-44360 Jenkins / JENKINS-44360 '%' in branch name causes Windows multi-branch job failures Change By: Mark Waite Resolution: Cannot Reproduce Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182170.1495170253000.16236.1559174400738%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44360) '%' in branch name causes Windows multi-branch job failures
Title: Message Title Jesse Glick resolved as Cannot Reproduce Likely obsolete as of JENKINS-2111. Jenkins / JENKINS-44360 '%' in branch name causes Windows multi-branch job failures Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182170.1495170253000.16220.1559173500535%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51454) Declarative pipeline retry operation doesn't retry when there is a timeout inside of it
Title: Message Title Basil Crow commented on JENKINS-51454 Re: Declarative pipeline retry operation doesn't retry when there is a timeout inside of it I can reproduce this error in a scripted pipeline as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190810.1526899694000.16208.1559169120115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Bryce Schober commented on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing Liam Newman Note that the ignore-committer-strategy plugin doesn't support simple (non-email) subversion usernames, and at least superficially (at least in its UI wording) only supports Git. See also JENKINS-57474. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171936.1466038064000.16159.1559168160708%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title John Gaunt commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits Liam Newman this plugin might also have the same end effect, but what my changes do is set the ignoredCommitters on the Bitbucket side, which is a little more visible to most devs at our organization. The effect being that the event never gets to Jenkins from Bitbucket. Since there is already a variable for the setting in the Bitbucket Webhook code it seemed sane to allow it to be set. I've not been able to set it in any fashion to date, it's always an empty string. I also need to make sure I can set this value from a groovy init script (which perhaps that plugin enables as well). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186379.1510079108000.16151.1559167020147%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47503) Abort ongoing builds of PR if new change to the same PR was submitted
Title: Message Title Nicholas Brown commented on JENKINS-47503 Re: Abort ongoing builds of PR if new change to the same PR was submitted Liam Newman just porting assumes the code that implements the behavior is the same for each plugin. They may work in different ways. Beyond that, I'm also not familiar with the code or implementation design/behaviors of either plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185960.1508335272000.16139.1559166060233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57537) catchError - Expecting "class hudson.model.Result" for parameter "buildResult"
Title: Message Title Devin Nusbaum started work on JENKINS-57537 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199445.1558161153000.16135.1559165640223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57537) catchError - Expecting "class hudson.model.Result" for parameter "buildResult"
Title: Message Title Devin Nusbaum updated JENKINS-57537 Jenkins / JENKINS-57537 catchError - Expecting "class hudson.model.Result" for parameter "buildResult" Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199445.1558161153000.16137.1559165640247%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57537) catchError - Expecting "class hudson.model.Result" for parameter "buildResult"
Title: Message Title Devin Nusbaum commented on JENKINS-57537 Re: catchError - Expecting "class hudson.model.Result" for parameter "buildResult" I was able to reproduce the issue and can confirm that this is specific to Declarative Pipelines. I am working on a PR to fix the issue: https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/85. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199445.1558161153000.16133.1559165580223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core
Title: Message Title Natasha Stopa commented on JENKINS-57672 Re: Determine Dependencies between PluginManager.java on Jenkins Core I started looking into splitting a separate module out from Jenkins core that would contain the plugin management class and its dependencies, but it appears that the number of dependencies will be quite large https://github.com/stopalopa/jenkins/tree/plugin-manager-dependencies. Next I will look into mapping out and documenting the more direct dependencies of the plugin management to see if these can more easily be cut out from the core. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199605.1558721108000.16131.1559164500102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57755) Hot reload while running `mvn:hpi run` gives error
Title: Message Title Parichay Barpanda commented on JENKINS-57755 Re: Hot reload while running `mvn:hpi run` gives error And hot reload also causes the credentials to not load and also add credentials not function. It says detecting classloader changes and removing caches and the credentials doesn't get loaded from Credentials plugin. Maybe need to do something with the uberclassloader thing that Gitea Plugin has implemented. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199700.1559163186000.16129.1559163840216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core
Title: Message Title Natasha Stopa started work on JENKINS-57672 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199605.1558721108000.16128.1559163840205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Liam Newman resolved as Fixed Resolving for now based on existing plugin. Please comment if not done. Jenkins / JENKINS-35988 Equivalent to polling commit exclusions for branch indexing Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171936.1466038064000.16089.1559163421992%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57756) Unable to save config: No enum constant hudson.plugins.ec2.ConnectionStrategy.Private IP
Title: Message Title dave goodine created an issue Jenkins / JENKINS-57756 Unable to save config: No enum constant hudson.plugins.ec2.ConnectionStrategy.Private IP Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-05-29 20:55 Environment: Jenkins ver. 2.164.3 ec2-plugin 1.43 Priority: Major Reporter: dave goodine Hi, After upgrading to 1.43, I was unable to save the main configuration page. When I tried to save, I got this stack trace: java.lang.IllegalArgumentException: No enum constant hudson.plugins.ec2.ConnectionStrategy.Private IP at java.lang.Enum.valueOf(Enum.java:238) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:733) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:778) Caused: java.lang.IllegalArgumentException: Failed to convert the connectionStrategy parameter of the constructor public hudson.plugins.ec2.SlaveTemplate(java.lang.String,java.lang.String,hudson.plugins.ec2.SpotConfiguration,java.lang.String,java.lang.String,com.amazonaws.services.ec2.model.InstanceType,boolean,java.lang.String,hudson.model.Node$Mode,java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,hudson.plugins.ec2.AMITypeData,java.lang.String,boolean,java.lang.String,java.util.List,java.lang.String,java.lang.String,java.lang.String,boolean,boolean,boolean,java.lang.String,boolean,java.lang.String,boolean,boolean,boolean,hudson.plugins.ec2.ConnectionStrategy,int) at
[JIRA] (JENKINS-57755) Hot reload while running `mvn:hpi run` gives error
Title: Message Title Parichay Barpanda assigned an issue to Parichay Barpanda Jenkins / JENKINS-57755 Hot reload while running `mvn:hpi run` gives error Change By: Parichay Barpanda Assignee: Kohsuke Kawaguchi Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199700.1559163186000.16085.1559163240288%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57755) Hot reload while running `mvn:hpi run` gives error
Title: Message Title
Parichay Barpanda created an issue
Jenkins / JENKINS-57755
Hot reload while running `mvn:hpi run` gives error
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
gitlab-branch-source-plugin
Created:
2019-05-29 20:53
Labels:
gsoc-2019
Priority:
Minor
Reporter:
Parichay Barpanda
There is something wrong here. Receiving a long error. But it doesn't affect the functionality. {{WARNING: Failed to scout com.cloudbees.plugins.credentials.UserCredentialsProvider java.lang.ExceptionInInitializerError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:669) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:471) at hudson.ExtensionList.load(ExtensionList.java:365) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:303) at hudson.ExtensionList.getComponents(ExtensionList.java:168) at jenkins.model.Jenkins$8.onInitMilestoneAttained(Jenkins.java:1121) at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:82) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:104) at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:176) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: attempt to register a second PermissionGroup for com.cloudbees.plugins.credentials.CredentialsProvider at hudson.security.PermissionGroup.register(PermissionGroup.java:139) at hudson.security.PermissionGroup.(PermissionGroup.java:63) at
[JIRA] (JENKINS-57754) Advanced button should align with delete button
Title: Message Title Parichay Barpanda assigned an issue to Unassigned Jenkins / JENKINS-57754 Advanced button should align with delete button Change By: Parichay Barpanda Assignee: Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199699.1559162932000.16079.1559163000137%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57754) Advanced button should align with delete button
Title: Message Title Parichay Barpanda assigned an issue to Parichay Barpanda Jenkins / JENKINS-57754 Advanced button should align with delete button Change By: Parichay Barpanda Assignee: Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199699.1559162932000.16078.1559163000112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: Support Multi User Picker custom field parameter mapping Deakey Tan Can you help share the solution / script that you're using here? It'll be very helpful for the community if they come across a similar requirement. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.16081.1559163000161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57754) Advanced button should align with delete button
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57754 Advanced button should align with delete button Issue Type: Bug Assignee: Unassigned Attachments: Screenshot from 2019-05-30 02-14-41.png Components: core Created: 2019-05-29 20:48 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda The advanced button Global Configuration doesn't align with the delete but so creates an inconsistency in the UI. Add Comment
[JIRA] (JENKINS-57516) Bitbucket branch source does not support tag notification
Title: Message Title Krzysztof Malinowski commented on JENKINS-57516 Re: Bitbucket branch source does not support tag notification This is Bitbucket Server 5.12.2. It looks like it falls into check for BRANCH ref change, while the actual notification had a TAG here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199419.1558086229000.16076.1559162820133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title Tatu Saloranta commented on JENKINS-50223 Re: Pipeline Jenkins master ran out of Java Metaspace Excellent! I think we managed to trigger this problem as well, via some seemingly unrelated refactoring, resulting in max uptime of 4-5 days for some masters. For what it is worth, Jenkins Metrics plug-in sends 2 useful metrics – `vm.class.loaded`, `vm.class.unloaded` – difference of which is number of classes currently retained. So we are graphing that to see class retention over time, which showed steady increase without pronunced sawtooth pattern which normally occurs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189249.1521223408000.16065.1559162700305%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57753) Doesn't display connection established configuration is reloaded
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57753 Doesn't display connection established configuration is reloaded Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-05-29 20:38 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Under the credentials entry, it shows a message `Cannot resolve suitable credentials with id:`. This is most probably happening because Jenkins is not sending request to GitLab Server to log in. I haven't been able to replicate this issue. Right now, when the Global configuration is loaded, it gets logged in but there is a need to show a loading symbol for the user to know that authentication with the server is being processed. Add Comment
[JIRA] (JENKINS-57752) Unable to add a text message in advanced configuration
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57752 Unable to add a text message in advanced configuration Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-05-29 20:30 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Trying to show a text message in the UI when the user presses `Advanced..` button. But unable find a suitable function for it in groovy. Add Comment
[JIRA] (JENKINS-57751) Unable to delete server configuration
Title: Message Title Parichay Barpanda commented on JENKINS-57751 Re: Unable to delete server configuration Only happens when there is only 1 GitLab Server configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199696.1559161096000.16060.1559161380114%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other
Title: Message Title Liam Newman edited a comment on JENKINS-55726 Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other FYI , this - Rejoice everyone! This functionality is available here: "Github Custom Notification Context SCM Behaviour"https://github.com/jenkinsci/github-scm-trait-notification-context-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16058.1559161140360%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57751) Unable to delete server configuration
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57751 Unable to delete server configuration Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-05-29 20:18 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Running the plugin with `mvn hpi:run`and a GitLab Server is added from the dropdown in Global Config. If no credentials is added to the server and server is tried to be deleted. It doesn't get deleted even upon saving the settings. Add Comment
[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other
Title: Message Title Liam Newman commented on JENKINS-55726 Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other FYI, this functionality is available here: "Github Custom Notification Context SCM Behaviour" https://github.com/jenkinsci/github-scm-trait-notification-context-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16052.1559161020443%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other
Title: Message Title Liam Newman resolved as Fixed Jenkins / JENKINS-55726 GitHub commit status context not unique enough or configurable - jobs always overwrite each other Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16054.1559161020475%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46119) Use the job name in context string
Title: Message Title Liam Newman commented on JENKINS-46119 Re: Use the job name in context string Turns out this is implemented here: https://github.com/jenkinsci/github-scm-trait-notification-context-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184356.1502369952000.16040.1559160901145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46119) Use the job name in context string
Title: Message Title Liam Newman resolved as Fixed Jenkins / JENKINS-46119 Use the job name in context string Change By: Liam Newman Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184356.1502369952000.16042.1559160901190%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-55726 GitHub commit status context not unique enough or configurable - jobs always overwrite each other Change By: Liam Newman Summary: GitHub can incorrectly flag PRs as passing checks if multiple commit status context not unique enough or configurable - jobs run against the same repository always overwrite each other Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16030.1559159760256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55726) GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-55726 GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository Change By: Liam Newman GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository. Multiple jobs configured against the same source repo will incorrectly set all checks successful if the last completed check is successful.In my opinion, if there is no mechanism to define mandatory and optional checks, then the worst status check should provide the overall result.This could be a check prior to submitting status that validates the prior status is not unsuccessful, and it is the same git sha1, and it is a different job name.The secondary issue here is that only a single link is added to the PR, and so there is no indication on the GitHub PR how many jobs ran. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16027.1559159640135%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-56853) Pull Request validation by multiple jenkins - webhook name configuration
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-56853 Pull Request validation by multiple jenkins - webhook name configuration Change By: Liam Newman Summary: Pull Request validation by multiple jenkins - webhook name configuration Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198513.1554214749000.16025.1559159520123%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-55013 support for App Center Change By: Mez Pahlan Component/s: appcenter-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196049.1543936697000.16020.1559159460672%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title Liam Newman resolved as Fixed https://issues.jenkins-ci.org/browse/JENKINS-54864?focusedCommentId=355479=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-355479 Jenkins / JENKINS-55453 Github PR creating job but not building Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196579.1546967067000.16006.1559159400415%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41692) It should be possible to build pull requests without building their feature branches
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-41692 It should be possible to build pull requests without building their feature branches Change By: Liam Newman Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178522.1486109681000.15996.1559159220542%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Liam Newman edited a comment on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing [~acejam]Ignore by commiter: https://github.com/jenkinsci/ignore-committer-strategy-plugin[~tknerr] [~webrat] [~woland] [~nlowe_hyland] [~natefaerber][~leedega] I think this does what is being requested here: https://wiki.jenkins.io/display/JENKINS/Multibranch+Build+Strategy+Extension+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171936.1466038064000.15954.1559159101801%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-35988 Equivalent to polling commit exclusions for branch indexing Change By: Liam Newman Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171936.1466038064000.15956.1559159101822%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Liam Newman edited a comment on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing [~acejam]Ignore by commiter: https://github.com/jenkinsci/ignore-committer-strategy-plugin[~tknerr] [~webrat] [~woland] [~nlowe_hyland] [~natefaerber] I think this does what is being requested here: https://wiki.jenkins.io/display/JENKINS/Multibranch+Build+Strategy+Extension+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171936.1466038064000.15878.1559159040806%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Liam Newman commented on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing Joshua Noble Ignore by commiter: https://github.com/jenkinsci/ignore-committer-strategy-plugin Torben Knerr Andreas Sieferlinger Alexander Siniouguine I think this does what is being requested here: https://wiki.jenkins.io/display/JENKINS/Multibranch+Build+Strategy+Extension+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171936.1466038064000.15839.1559158980667%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title Ulli Hafner updated JENKINS-57098 Jenkins / JENKINS-57098 JSON Exchange format for import/export? Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198843.16000.15836.1559158860194%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57686) A list of improvements in GitLab Server Configuration
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57686 A list of improvements in GitLab Server Configuration Change By: Parichay Barpanda 1) Add support for generating personal access token via username/password credentials like GitHub Plugin2) Add Java 8 functional interfaces for behavioural design pattern3) Add support for testing connection4) -Make manage hooks independent of credentials-5) Add a `none` option when no credential is added to server configuration All features with strikethroughs are completed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199621.1558824827000.15834.1559158680050%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57686) A list of improvements in GitLab Server Configuration
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57686 A list of improvements in GitLab Server Configuration Change By: Parichay Barpanda 1) Add support for generating personal access token via username/password credentials like GitHub Plugin2) Add Java 8 functional interfaces for behavioural design pattern 3) Add support for testing connection4) -Make manage hooks independent of credentials-5) Add a `none` option when no credential is added to server configuration Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199621.1558824827000.15833.1559158620058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57686) A list of improvements in GitLab Server Configuration
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57686 A list of improvements in GitLab Server Configuration Change By: Parichay Barpanda Comment: 3) Add support for testing connection4) Make manage hooks independent of credentials Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199621.1558824827000.15832.1559158500056%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50561) Add @Symbol to "throttle builds" job properties
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50561 Re: Add @Symbol to "throttle builds" job properties not at all Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189630.1522823307000.15829.1559158380135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56468) githubPRComment throws NPE
Title: Message Title Liam Newman commented on JENKINS-56468 Re: githubPRComment throws NPE Gil Bahat Does this still happen in the latest github-branch-source-plugin (2.5.3)? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198067.1551981547000.15826.1559158320125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50561) Add @Symbol to "throttle builds" job properties
Title: Message Title Liam Newman commented on JENKINS-50561 Re: Add @Symbol to "throttle builds" job properties Ivan Fernandez Calvo Does the generated code not work? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189630.1522823307000.15824.1559158260195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50561) Add @Symbol to "throttle builds" job properties
Title: Message Title Liam Newman reopened an issue Jenkins / JENKINS-50561 Add @Symbol to "throttle builds" job properties Change By: Liam Newman Resolution: Fixed Status: Resolved Reopened Assignee: Andrew Bayer Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189630.1522823307000.15817.1559158140648%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50561) Add @Symbol to "throttle builds" job properties
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-50561 Add @Symbol to "throttle builds" job properties Change By: Liam Newman Comment: [~ifernandezcalvo]Please open a new issue. Should be an easy fix. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189630.1522823307000.15812.1559158140584%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50561) Add @Symbol to "throttle builds" job properties
Title: Message Title Liam Newman commented on JENKINS-50561 Re: Add @Symbol to "throttle builds" job properties Ivan Fernandez Calvo Please open a new issue. Should be an easy fix. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189630.1522823307000.15807.1559158140518%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50561) Add @Symbol to "throttle builds" job properties
Title: Message Title Liam Newman updated JENKINS-50561 Jenkins / JENKINS-50561 Add @Symbol to "throttle builds" job properties Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189630.1522823307000.15802.1559158080765%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47503) Abort ongoing builds of PR if new change to the same PR was submitted
Title: Message Title Liam Newman commented on JENKINS-47503 Re: Abort ongoing builds of PR if new change to the same PR was submitted Nicholas Brown Cool, so the behavior just needs porting to bitbucket plugin. Do you have time to submit a PR? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185960.1508335272000.15789.1559157900264%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title Liam Newman commented on JENKINS-56255 Re: occasionally builds the branch for a PR also Brian J Murrell No, you haven't done anything wrong. Just not enough resources. I understand your frustration. Is there any pattern to when this happens? My guess is this is a race condition related to scanning, but we'll see. What is the config for your multibranch pipeline? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197825.1550941413000.15787.1559157780085%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56853) Pull Request validation by multiple jenkins
Title: Message Title Liam Newman commented on JENKINS-56853 Re: Pull Request validation by multiple jenkins Linked Issue is for making status context configurable (2). We can use this issue to track (1) webhook name specifically. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198513.1554214749000.15782.1559157420289%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49259) Support team dimension in GitHub
Title: Message Title Liam Newman started work on JENKINS-49259 Change By: Liam Newman Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188116.1517321943000.15784.1559157420312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48631) Automatically remove the cache created on disk when lightweight checkout is used
Title: Message Title Lorenzo Solano Martinez commented on JENKINS-48631 Re: Automatically remove the cache created on disk when lightweight checkout is used Any updates or workaround with this one? I'm filling up a 20GBs in minutes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187285.151369896.15776.1559157300325%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51765) PRs are not rebuilt after their target branch is updated
Title: Message Title Liam Newman edited a comment on JENKINS-51765 Re: PRs are not rebuilt after their target branch is updated [~viceice][~kfernald] That strategy might only be in: https://wiki.jenkins.io/display/JENKINS/Basic+Branch+Build+Strategies+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191212.1528363782000.15774.1559157120442%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51765) PRs are not rebuilt after their target branch is updated
Title: Message Title Liam Newman commented on JENKINS-51765 Re: PRs are not rebuilt after their target branch is updated Michael Kriese That strategy might only be in: https://wiki.jenkins.io/display/JENKINS/Basic+Branch+Build+Strategies+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191212.1528363782000.15769.1559157120382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54045) Jenkinsfile in subfolder not found
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-54045 Jenkinsfile in subfolder not found Change By: Liam Newman Labels: regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194660.1539338261000.15763.1559156940298%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57014) Enable deployment web hooks
Title: Message Title Liam Newman started work on JENKINS-57014 Change By: Liam Newman Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198716.1555357864000.15761.1559156880175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57749) Latest terraform version (0.12.0) not available for download via global tool installation from bintray
Title: Message Title David Pires commented on JENKINS-57749 Re: Latest terraform version (0.12.0) not available for download via global tool installation from bintray Could be a local cache issue, however I'm not sure how to refresh that. I have run the crawler by itself and it is returning 0.12.0. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199694.155915236.15759.1559156640078%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57026) commit build status not always reported on github
Title: Message Title Liam Newman commented on JENKINS-57026 Re: commit build status not always reported on github Atanas Zhelev Is this happening in the latest version of the plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198728.1555433047000.15757.1559156580080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55726) GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository
Title: Message Title Liam Newman commented on JENKINS-55726 Re: GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository Jon-Paul Sullivan there is this plugin that lets people notify github in whatever way they choose. https://github.com/jenkinsci/pipeline-githubnotify-step-plugin Generally, the assumption for Pipeline has been that there is one pipeline per repository, so it was safe to have a hard-coded context. Are you not using Pipeline or using more than one pipeline per repository? In any case, having the github-branch-source support a user configurable context string seems like a reasonable feature request. Would you be willing to submit a PR for this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.15754.1559156520125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors
Title: Message Title David Schneider commented on JENKINS-57595 Re: with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors Can we please get an ETA for resolving this issue? We're currently blocked with setting up a new Jenkins server because we're not able to revert back to an earlier version of the plug-in. Until this is resolved we can't set up user roles on the new server. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199519.1558510674000.15750.1559155800169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42643) Conditional application of triggers in Declarative
Title: Message Title Tri Nguyen commented on JENKINS-42643 Re: Conditional application of triggers in Declarative I imagine the cron string could be set conditionally (only has a value on `master` branch, and an empty string if not)? In the case that you call cron with an empty string, would it have any side effect? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179585.1489096826000.15747.1559155561462%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57579) New "unstable" step is not visualizing stage as unstable
Title: Message Title Devin Nusbaum updated JENKINS-57579 Jenkins / JENKINS-57579 New "unstable" step is not visualizing stage as unstable Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199495.1558434359000.15703.1559155441171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57579) New "unstable" step is not visualizing stage as unstable
Title: Message Title Devin Nusbaum commented on JENKINS-57579 Re: New "unstable" step is not visualizing stage as unstable Ok, it turns out that the PR I have open to Blue Ocean to fix the per-step icon also has a fix that matters in some cases for the overall visualization, so this should be fixed once that gets released. This comment on the PR has some technical details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199495.1558434359000.15691.1559155441016%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title Liam Newman commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits John Gaunt Are you saying this plugin doesn't already do what you want? https://github.com/jenkinsci/ignore-committer-strategy-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186379.1510079108000.15705.1559155441195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57579) New "unstable" step is not visualizing stage as unstable
Title: Message Title Devin Nusbaum started work on JENKINS-57579 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199495.1558434359000.15697.1559155441099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53210) Scan Organisation no longer triggering project scans
Title: Message Title Liam Newman resolved as Fixed Jenkins / JENKINS-53210 Scan Organisation no longer triggering project scans Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193236.1535031895000.15680.1559155080256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54956) Github merge refs not working correctly
Title: Message Title Liam Newman resolved as Cannot Reproduce Jenkins / JENKINS-54956 Github merge refs not working correctly Change By: Liam Newman Status: In Progress Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195979.1543563431000.15677.1559154960312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54956) Github merge refs not working correctly
Title: Message Title Liam Newman commented on JENKINS-54956 Re: Github merge refs not working correctly Javier RaezThomas Riccardi Could you try out github branch source plugin v2.5.3? I'm going to resolve this this due to lack of response. We can reopen if it still occurring. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195979.1543563431000.15674.1559154900096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title Liam Newman commented on JENKINS-56854 Re: ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub Running in debug mode is definitely a hack. My point is that this is a reasonable feature enhancement request - to add more environment variables for pull requests, but this is expected behavior for the current version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198514.155421873.15672.1559154660110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50013) Provide better polling filter debugging
Title: Message Title Eric Blom commented on JENKINS-50013 Re: Provide better polling filter debugging Is it possible to add a polling filter for a pipeline job? I'm converting freestyle jobs to pipelines and I'm struggling to figure out how to migrate our polling filters. I've searched the documentation, asked on IRC, and then found this ticket. Based on this title of this ticket I'm hopeful that polling filters are supported in pipelines they just are documented. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189011.1520506503000.15665.1559154000298%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55348) Display Pull Request Name instead of ID in the UI
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-55348 Display Pull Request Name instead of ID in the UI Change By: Liam Newman Component/s: branch-api-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196444.1545944269000.15667.1559154000334%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Mads Mohr Christensen commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free I've created an installer plugin for AdoptOpenJDK: https://github.com/jenkinsci/adoptopenjdk-plugin The initial release is still pending though as crawler metadata is not updating: INFRA-2111 I have also opened a [PR|https://github.com/jenkinsci/jdk-tool-plugin/pull/5] that adds a warning text to the Oracle JDK installer about the license change and I've also opened a [PR|https://github.com/jenkins-infra/crawler/pull/82] that restores Java 10 and adds Java 11 and Java 12. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194838.1540287328000.15642.1559153640387%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
