[JIRA] (JENKINS-54059) GSoC 2019 prepwork (October-December)
Title: Message Title Lloyd Chang updated an issue Jenkins / JENKINS-54059 GSoC 2019 prepwork (October-December) Change By: Lloyd Chang GSoC 2019 preparation work EPIC. This EPIC contains tasks we need to address before the public application and project publishing starts CC [~martinda] [~jeffpearce] [~lloydchang] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54059) GSoC 2019 prepwork (October-December)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54059 GSoC 2019 prepwork (October-December) Change By: Oleg Nenashev GSoC 2019 preparation work EPIC. This EPIC contains tasks we need to address before the public application and project publishing starts CC [~martinda] [~jeffpearce] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54059) GSoC 2019 prepwork (October-December)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54059 GSoC 2019 prepwork (October-December) Issue Type: Epic Assignee: Unassigned Components: other Created: 2018-10-13 02:42 Labels: gsoc Priority: Minor Reporter: Oleg Nenashev GSoC 2019 preparation work EPIC. This EPIC contains tasks we need to address before the public application Add Comment
[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option
Title: Message Title Nitin Surana edited a comment on JENKINS-48556 Re: timestamps() randomly not recognized as a valid option Have been working without any issues, suddenly started getting this issue during builds (cron/webhook or manual, all fails fail )```vars/BasePipeline.groovy: 19: Invalid option type "timeout".Valid option types: [buildDiscarder, checkoutToSubdirectory, disableConcurrentBuilds, disableResume, durabilityHint, newContainerPerStage, overrideIndexTriggers] @ line 19, column 13. timeout(time: 15, unit: '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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option
Title: Message Title Nitin Surana edited a comment on JENKINS-48556 Re: timestamps() randomly not recognized as a valid option Have been working without any issues, suddenly started getting this issue during builds : (cron/webhook or manual, all fails) ```vars/BasePipeline.groovy: 19: Invalid option type "timeout".Valid option types: [buildDiscarder, checkoutToSubdirectory, disableConcurrentBuilds, disableResume, durabilityHint, newContainerPerStage, overrideIndexTriggers] @ line 19, column 13. timeout(time: 15, unit: '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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option
Title: Message Title Nitin Surana edited a comment on JENKINS-48556 Re: timestamps() randomly not recognized as a valid option Have been working without any issues, suddenly started getting this issue during builds : ``` vars/BasePipeline.groovy: 19: Invalid option type "timeout". Valid option types: [buildDiscarder, checkoutToSubdirectory, disableConcurrentBuilds, disableResume, durabilityHint, newContainerPerStage, overrideIndexTriggers] @ line 19, column 13. timeout(time: 15, unit: '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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option
Title: Message Title Nitin Surana commented on JENKINS-48556 Re: timestamps() randomly not recognized as a valid option Have been working without any issues, suddenly started getting this issue during builds : vars/BasePipeline.groovy: 19: Invalid option type "timeout". Valid option types: [buildDiscarder, checkoutToSubdirectory, disableConcurrentBuilds, disableResume, durabilityHint, newContainerPerStage, overrideIndexTriggers] @ line 19, column 13. timeout(time: 15, unit: '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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54058) Old agent.jar causes JNLP agent to fail checkout with java.lang.IllegalAccessError
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54058 Old agent.jar causes JNLP agent to fail checkout with java.lang.IllegalAccessError Change By: Mark Waite Summary: Old agent.jar causes Windows JNLP agent to fail clone checkout with java.lang.IllegalAccessError 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54058) Old agent.jar causes Windows JNLP agent to fail clone with java.lang.IllegalAccessError
Title: Message Title Mark Waite updated JENKINS-54058 Jenkins / JENKINS-54058 Old agent.jar causes Windows JNLP agent to fail clone with java.lang.IllegalAccessError Change By: Mark Waite Status: Fixed but Unreleased Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54058) Old agent.jar causes Windows JNLP agent to fail clone with java.lang.IllegalAccessError
Title: Message Title Mark Waite updated JENKINS-54058 Older agent.jar and slave.jar files running on the agent machine were the root cause of this problem. Once I updated the agent.jar to the version included with Jenkins 2.138.2, the jobs completed successfully. Jenkins / JENKINS-54058 Old agent.jar causes Windows JNLP agent to fail clone with java.lang.IllegalAccessError Change By: Mark Waite Status: Open Fixed but Unreleased Assignee: Jeff Thompson 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
[JIRA] (JENKINS-54058) Old agent.jar causes Windows JNLP agent to fail clone with java.lang.IllegalAccessError
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-54058
Old agent.jar causes Windows JNLP agent to fail clone with java.lang.IllegalAccessError
Change By:
Mark Waite
I upgraded a few workflow plugins that were recently released, switching from the beta version of those plugins to the released versions of the plugins. After doing that, my Pipeline jobs that were performing checkout on JNLP based Windows machines failed. The Windows agents are connected with JNLP. The checkouts failed on 4 different Windows 10 machines with the same stack trace:{noformat}14:09:24 Cloning the remote Git repository14:09:24 Cloning the remote Git repository14:09:24 ERROR: Error cloning remote repo 'origin'14:09:24 hudson.plugins.git.GitException: java.io.IOException: Remote call on JNLP4-connect connection from 172.16.16.196/172.16.16.196:54100 failed14:09:24 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:148)14:09:24 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)14:09:24 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)14:09:24 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)14:09:24 at java.lang.reflect.Method.invoke(Method.java:498)14:09:24 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)14:09:24 at com.sun.proxy.$Proxy97.execute(Unknown Source)14:09:24 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144)14:09:24 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1184)14:09:24 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)14:09:24 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)14:09:24 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)14:09:24 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)14:09:24 at hudson.security.ACL.impersonate(ACL.java:290)14:09:24 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)14:09:24 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)14:09:24 at java.util.concurrent.FutureTask.run(FutureTask.java:266)14:09:24 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)14:09:24 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)14:09:24 at java.lang.Thread.run(Thread.java:748)14:09:24 Caused by: java.io.IOException: Remote call on JNLP4-connect connection from 172.16.16.196/172.16.16.196:54100 failed14:09:24 at hudson.remoting.Channel.call(Channel.java:961)14:09:24 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)14:09:24 ... 19 more14:09:24 Caused by: java.lang.IllegalAccessError: tried to access field hudson.remoting.Channel.executor
[JIRA] (JENKINS-54035) can't exclude everything under a given dir
Title: Message Title Ulli Hafner edited a comment on JENKINS-54035 Re: can't exclude everything under a given dir Currently the filter is invoked after all preprocessing steps. I.e. after absolute paths have been detected, etc. Maybe it makes sense to move this step to the beginning (or after the absolute path resolving). From the log I see that almost every warning has no absolute path (0 resolved, 766 unresolved, 14 already absolute). I.e. the parser seems not to work as expected. What makes me wonder: the log says: applying 1 filter, but in your example you have 2. But anyway, I think you need to change the regular _expression_ so that it matches the whole entire file name, not only a portion. I.e. in your example the .\* is missing in the front. See the [new test|https://github.com/uhafner/warnings-ng-plugin/commit/50d7719ba5ff7c2f345a5f30bfc08270928d2b2b] that shows that the filter works.Maybe it makes sense to add an example text box in the UI of the snippet generator so you can experiment with the filter regexp.Should I change the name of the 'pattern' box to 'regular _expression_'? I can clarify as well that the whole property text must match. Java regular expressions are a little bit different since they match the entire string. I'll check if there is something available that matches only a part of the string. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54058) Old agent.jar causes Windows JNLP agent to fail clone with java.lang.IllegalAccessError
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54058 Old agent.jar causes Windows JNLP agent to fail clone with java.lang.IllegalAccessError Change By: Mark Waite Summary: Old agent.jar causes Windows JNLP agent fails to fail clone with java.lang.IllegalAccessError 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54035) can't exclude everything under a given dir
Title: Message Title Ulli Hafner commented on JENKINS-54035 Re: can't exclude everything under a given dir Currently the filter is invoked after all preprocessing steps. I.e. after absolute paths have been detected, etc. Maybe it makes sense to move this step to the beginning (or after the absolute path resolving). From the log I see that almost every warning has no absolute path (0 resolved, 766 unresolved, 14 already absolute). I.e. the parser seems not to work as expected. What makes me wonder: the log says: applying 1 filter, but in your example you have 2. But anyway, I think you need to change the regular _expression_ so that it matches the whole file name, not only a portion. I.e. in your example the .* is missing in the front. See the new test that shows that the filter works. Maybe it makes sense to add an example text box in the UI of the snippet generator so you can experiment with the filter regexp. Should I change the name of the 'pattern' box to 'regular _expression_'? I can clarify as well that the whole property text must match. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54047) All boolean parameters get set to true when used to set env vars.
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-54047 All boolean parameters get set to true when used to set env vars. Change By: Devin Nusbaum Component/s: pipeline-model-definition-plugin Component/s: 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54047) All boolean parameters get set to true when used to set env vars.
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-54047
Re: All boolean parameters get set to true when used to set env vars.
I'm not quite sure what's going on here, but I was able to reproduce it. Looks like someone in JENKINS-47881 also mentioned a similar issues using the ternary operator for an environment variable. CC @ [~ abayer ] , are we all missing something obvious here?{code:java}pipeline {agent anyparameters { booleanParam defaultValue: true, description: '', name: 'p1'}environment {NOT_P1 = "${(!params.p1) ? 'true' : 'false'}"}stages {stage('JENKINS-54047') {steps {// If p1 == true, then this prints "expecting false, got true"// If p1 == false, then this prints "expecting true, got false"echo "expecting ${!p1}, got ${NOT_P1}"}}}} {code}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54047) All boolean parameters get set to true when used to set env vars.
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-54047 All boolean parameters get set to true when used to set env vars. Change By: Devin Nusbaum Labels: 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54047) All boolean parameters get set to true when used to set env vars.
Title: Message Title
Devin Nusbaum commented on JENKINS-54047
Re: All boolean parameters get set to true when used to set env vars.
I'm not quite sure what's going on here, but I was able to reproduce it. Looks like someone in JENKINS-47881 also mentioned a similar issues using the ternary operator for an environment variable. CC @abayer, are we all missing something obvious here?
pipeline {
agent any
parameters {
booleanParam defaultValue: true, description: '', name: 'p1'
}
environment {
NOT_P1 = "${(!params.p1) ? 'true' : 'false'}"
}
stages {
stage('JENKINS-54047') {
steps {
// If p1 == true, then this prints "expecting false, got true"
// If p1 == false, then this prints "expecting true, got false"
echo "expecting ${!p1}, got ${NOT_P1}"
}
}
}
}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46354) Retry in Declarative options skips retried stages due to earlier failure
Title: Message Title
Bruno Campolo edited a comment on JENKINS-46354
Re: Retry in Declarative options skips retried stages due to earlier failure
{code:java}import jenkins.model.*pipeline {agent any options { retry(3) }stages {stage('Stage1') {steps {echo "Starting Stage1"}}stage('Stage2') {steps {echo "Starting Stage2"error "This will cause the pipeline to retry"}}}post {always {echo 'This will always run'}success {echo 'This will run only if successful'}failure {echo 'This will run upon failure'}unstable {echo 'This will run only if the run was marked as unstable'}changed {echo 'This will run only if the state of the Pipeline has changed'}}}{code}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54027) ID analysis is already used by another action
Title: Message Title Ulli Hafner commented on JENKINS-54027 Re: ID analysis is already used by another action I see. If you are using aggregatingResults: true then there is currently no way to specify an ID. This is something I need to change. There are two options: add an extra parameter ID (and name) to the recordIssues step. It will only be used for aggregatingResults: true auto-merge results that have the same ID The first approach seems to be too complex to understand since the ID parameter makes no sense for aggregatingResults: false. So it makes more sense to implement the second one, what do you think? What is still not clear to me: if all results of CentOS and Ubuntu will be merged, what do you expect in the UI? Should there be a column that shows from where (OS) the warnings are? Are the warnings of the OS compilers different at all? Currently, the plugin skips duplicate warnings that have the same properties. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54058) Windows JNLP agent fails clone with java.lang.IllegalAccessError
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-54058
Windows JNLP agent fails clone with java.lang.IllegalAccessError
Change By:
Mark Waite
I upgraded a few workflow plugins that were recently released, switching from the beta version of those plugins to the released versions of the plugins. After doing that, my Pipeline jobs that were performing checkout on Windows machines failed. The Windows agents are connected with JNLP. The checkouts failed on 4 different Windows 10 machines with the same stack trace:{noformat}14:09:24 Cloning the remote Git repository14:09:24 Cloning the remote Git repository14:09:24 ERROR: Error cloning remote repo 'origin'14:09:24 hudson.plugins.git.GitException: java.io.IOException: Remote call on JNLP4-connect connection from 172.16.16.196/172.16.16.196:54100 failed14:09:24 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:148)14:09:24 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)14:09:24 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)14:09:24 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)14:09:24 at java.lang.reflect.Method.invoke(Method.java:498)14:09:24 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)14:09:24 at com.sun.proxy.$Proxy97.execute(Unknown Source)14:09:24 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144)14:09:24 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1184)14:09:24 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)14:09:24 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)14:09:24 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)14:09:24 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)14:09:24 at hudson.security.ACL.impersonate(ACL.java:290)14:09:24 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)14:09:24 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)14:09:24 at java.util.concurrent.FutureTask.run(FutureTask.java:266)14:09:24 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)14:09:24 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)14:09:24 at java.lang.Thread.run(Thread.java:748)14:09:24 Caused by: java.io.IOException: Remote call on JNLP4-connect connection from 172.16.16.196/172.16.16.196:54100 failed14:09:24 at hudson.remoting.Channel.call(Channel.java:961)14:09:24 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)14:09:24 ... 19 more14:09:24 Caused by: java.lang.IllegalAccessError: tried to access field hudson.remoting.Channel.executor from class
[JIRA] (JENKINS-44172) Better scan of multibranch pipelines
Title: Message Title Jason Parraga commented on JENKINS-44172 Re: Better scan of multibranch pipelines After moving to multi branch pipelines our company has experienced issues with the branch scanning. We have a few integration test style jobs which run for about 2 hours and each job may have between 20-40 open pull requests (arguably, this is an issue itself). Anyway, every time the branches are scanned our build queue blows up and we cannot check in code for roughly a day unless we spend time killing many of those jobs. Since we have a few jobs like this, this happens a couple times a week. We would really benefit from being able to specify a cron _expression_ for scanning. This would allow us to at least scan during off peak hours like on the weekends so there is minimal disruption. Right now we are at the mercy of the configured interval which I assume begins when you make the interval 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54057) [JEP-302] Implement evergreen Data auto-rollback using the snapshotting system
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54057 [JEP-302] Implement evergreen Data auto-rollback using the snapshotting system Change By: Baptiste Mathus Summary: [JEP-302] Implement evergreen Data auto-rollback using the snapshotting system 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54057) Implement evergreen Data auto-rollback using the snapshotting system
Title: Message Title Baptiste Mathus started work on JENKINS-54057 Change By: Baptiste Mathus 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54056) Implement Evergreen automated Update Level rollback
Title: Message Title Baptiste Mathus updated JENKINS-54056 Jenkins / JENKINS-54056 Implement Evergreen automated Update Level rollback Change By: Baptiste Mathus 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Karl Shultz commented on JENKINS-54046 Re: GitHub branch souce plugin fails to move temporary files I'm so glad that helped fix you guys up. Thanks for reporting the bug, and thanks for all the followup information. That really helps! Sometimes bug reporters vanish, so thanks for sticking around. There's not a new version of the plugin yet - 2.4.0 is the latest version available. We'll need to get this fixed up, though. I've got an idea for how to do that, but it's more of a workaround than an actual fix. It would make the default cache behavior conditional. Windows master? Cache disabled by default, but can be turned back on via the same means we've been using in this ticket. !=Windows master? Cache enabled, still set to the previous default of 20MB. Can still be changed or disabled as you want. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54058) Windows JNLP agent fails clone with java.lang.IllegalAccessError
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54058 Windows JNLP agent fails clone with java.lang.IllegalAccessError Change By: Mark Waite Environment: Jenkins 2.138.2 as described in [docker-lfs| https://github.com/MarkEWaite/docker-lfs/tree/7b59084c2f271e215e3eeac2bc2295208edcc75c ] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54058) Windows JNLP agent fails clone with java.lang.IllegalAccessError
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54058 Windows JNLP agent fails clone with java.lang.IllegalAccessError Change By: Mark Waite Environment: Jenkins 2.138.2 as described in [docker-lfs| https://github.com/MarkEWaite/docker-lfs/tree/7b59084c2f271e215e3eeac2bc2295208edcc75c ] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54058) Windows JNLP agent fails clone with java.lanbg.IllegalAccessError
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-54058 Windows JNLP agent fails clone with java.lanbg.IllegalAccessError Issue Type: Bug Assignee: Jeff Thompson Components: core, remoting Created: 2018-10-12 20:15 Environment: Jenkins 2.138.2 as described in https://github.com/MarkEWaite/docker-lfs/tree/7b59084c2f271e215e3eeac2bc2295208edcc75c Priority: Minor Reporter: Mark Waite I upgraded a few workflow plugins that were recently released, switching from the beta version of those plugins to the released versions of the plugins. After doing that, my Pipeline jobs that were performing checkout on Windows machines failed. The checkouts failed on 4 different Windows 10 machines with the same stack trace: 14:09:24 Cloning the remote Git repository 14:09:24 Cloning the remote Git repository 14:09:24 ERROR: Error cloning remote repo 'origin' 14:09:24 hudson.plugins.git.GitException: java.io.IOException: Remote call on JNLP4-connect connection from 172.16.16.196/172.16.16.196:54100 failed 14:09:24 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:148) 14:09:24 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 14:09:24 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 14:09:24 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 14:09:24 at java.lang.reflect.Method.invoke(Method.java:498) 14:09:24 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) 14:09:24 at
[JIRA] (JENKINS-54058) Windows JNLP agent fails clone with java.lang.IllegalAccessError
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54058 Windows JNLP agent fails clone with java.lang.IllegalAccessError Change By: Mark Waite Summary: Windows JNLP agent fails clone with java. lanbg lang .IllegalAccessError 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51308) [JEP-305] Incrementalify the Metrics plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51308 [JEP-305] Incrementalify the Metrics plugin Change By: Baptiste Mathus Priority: Major Minor 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54057) Implement evergreen Data auto-rollback using the snapshotting system
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54057 Implement evergreen Data auto-rollback using the snapshotting system Issue Type: New Feature Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-12 19:58 Priority: Critical Reporter: Baptiste Mathus 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54057) Implement evergreen Data auto-rollback using the snapshotting system
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54057 Implement evergreen Data auto-rollback using the snapshotting system Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54056) Implement Evergreen automated Update Level rollback
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54056 Implement Evergreen automated Update Level rollback Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53273) Implement the Evergreen Automated Rollback system
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53273 Implement the Evergreen Automated Rollback system Change By: Baptiste Mathus Epic Name: Evergreen Automatic Rollback System 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54056) Implement Evergreen automated Update Level rollback
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54056 Implement Evergreen automated Update Level rollback Issue Type: New Feature Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-12 19:57 Priority: Critical Reporter: Baptiste Mathus When an Update Level (UL) is upgraded to, Evergreen should automatically go to the previous version if Jenkins isn't available after restart. Acceptance Criteria Updating to an UL that prevents Jenkins from starting again should automatically trigger going back to a working UL. NOTE: The Data snapshotting part, especially useful if a plugin has changed its data format, will not be handled here. We will solely focus on the UL and global list of things to "go to". Add Comment
[JIRA] (JENKINS-54056) Implement Evergreen automated Update Level rollback
Title: Message Title Baptiste Mathus started work on JENKINS-54056 Change By: Baptiste Mathus 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53273) Implement the Evergreen Automated Rollback system
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53273 Implement the Evergreen Automated Rollback system Change By: Baptiste Mathus The automated rollback system has been designed, but not implemented yet.Related JEPs/documents: * [JEP 302|https://github.com/jenkinsci/jep/tree/master/jep/302] wasn't implemented back then because we were missing for the client Git based snapshotting system* [JEP 306|https://github . It's now time to do it. com/jenkinsci/jep/tree/master/jep/306] for the healthchecking h3. Acceptance criteria# Set up an evergreen instance, it is at UL-X# publish a (broken) update level (example: adding a plugin without a required dependency) => instance upgrades to UL-X# after restart, evergreen client detects Jenkins cannot restart, and rolls back to UL-X.# Jenkins is accessible again# a correct UL is published, Jenkins can upgrade to 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53273) Implement the Evergreen Automated Rollback system
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53273 Implement the Evergreen Automated Rollback system Change By: Baptiste Mathus Summary: Implement the git-based snapshot rollback Evergreen Automated Rollback system described in JEP 302 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53983) Per-instance tainting still serves the tainted level if you're "coming from" a lower level
Title: Message Title Baptiste Mathus resolved as Fixed Jenkins / JENKINS-53983 Per-instance tainting still serves the tainted level if you're "coming from" a lower level Change By: Baptiste Mathus Status: In Progress 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54055) MSDeploy ERROR_SITE_DOES_NOT_EXIST does not fail job
Title: Message Title Justin Nimmo updated an issue Jenkins / JENKINS-54055 MSDeploy ERROR_SITE_DOES_NOT_EXIST does not fail job Change By: Justin Nimmo Environment: Jenkins is on RHEL 7 Red Hat Enterprise Linux Server 7.5 (Maipo) and agents are windows agents Server 2012 R2. Active Directory plugin2.8 AnsiColor0.5.2 Ant Plugin1.8 Apache HttpComponents Client 4.x API Plugin4.5.5-3.0 Artifactory Plugin2.16.2 Audit Trail2.3 Authentication Tokens API Plugin1.3 Autofavorite for Blue Ocean1.2.2 Bitbucket Branch Source Plugin2.2.12 Bitbucket Pipeline for Blue Ocean1.6.2 Bitbucket Plugin1.1.8 Blue Ocean1.6.2 Blue Ocean Core JS1.6.2 Blue Ocean Pipeline Editor1.6.2 bouncycastle API Plugin2.17 Branch API Plugin2.0.20 Build Monitor View1.12+build.201809061734 Build Timeout1.19 build-name-setter1.6.9 built-on-column1.1 change-assembly-version-plugin1.10 Checkstyle Plug-in3.50 Command Agent Launcher Plugin1.2 Common API for Blue Ocean1.6.2 Compact Columns1.10 Conditional BuildStep1.3.6 Config API for Blue Ocean1.6.2 Config File Provider3.2 Console Column Plugin1.5 Console Tail Plugin1.1 Copy Artifact1.39.1 Copy project link plugin1.5 Credentials Binding Plugin1.16 Credentials Plugin2.1.18 Dashboard for Blue Ocean1.6.2 Dashboard View2.9.11 Deploy to container Plugin1.13 Design Language1.6.2 Display URL API2.2.0 Display URL for Blue Ocean2.2.0 Docker Commons Plugin1.13 Docker Pipeline1.17 Drop Down ViewsTabBar Plugin1.7 Durable Task Plugin1.26 Email Extension Plugin2.63 embeddable-build-status1.9 EnvInject API Plugin1.5 Environment Injector Plugin2.1.6 Escaped Markup Plugin0.1 Events API for Blue Ocean1.6.2 Extended Choice Parameter Plug-In0.76 External Monitor Job Type Plugin1.7 Extra Columns Plugin1.20 Favorite2.3.2 Flyway Runner1.9 Folders6.5.1 Git client plugin2.7.3 Git Parameter0.9.5 Git Pipeline for Blue Ocean1.6.2 Git plugin3.9.1 GIT server Plugin1.7 GitHub API Plugin1.92 GitHub Branch Source Plugin2.4.0 GitHub Pipeline for Blue Ocean1.6.2 GitHub plugin1.29.3 Gradle Plugin1.29 Handy Uri Templates 2.x API Plugin2.1.6-1.0 HPE Security Fortify Jenkins Plugin17.20.0183 HTML Publisher plugin1.17 i18n for Blue Ocean1.6.2 Icon Shim Plugin2.0.3 Infrastructure plugin for Publish Over X0.22 Ivy Plugin1.28 Jackson 2 API Plugin2.8.11.3 Javadoc Plugin1.4 _javascript_ GUI Lib: ACE Editor bundle plugin1.1 _javascript_ GUI Lib: Handlebars bundle plugin1.1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin1.2.1 _javascript_ GUI Lib: Moment.js bundle plugin1.1.1 JDK Tool1.0 JIRA Integration for Blue Ocean1.6.2 JIRA plugin3.0.2 Job Configuration History Plugin2.18.2 Job Import Plugin3.0 jQuery plugin1.12.4-0 JSch dependency plugin0.1.54.2 JUnit Plugin1.26.1 JWT for Blue Ocean1.6.2 LDAP Plugin1.20 Mailer Plugin1.21 MapDB API Plugin1.0.9.0 Mask Passwords Plugin2.12.0 Matrix Authorization Strategy Plugin2.3 Matrix Project Plugin1.13 Maven Integration plugin3.1.2 Mercurial plugin2.4 Metrics Plugin4.0.2.2 Modern Status1.2 MSBuild Plugin1.29 MSTest plugin0.23 MSTestRunner plugin1.3.0 Multiple SCMs plugin0.6 Nested View Plugin1.14 New Relic Deployment Notifier1.3 Next Build Number Plugin1.5 Nuget Plugin0.7 NUnit plugin0.23 OWASP Markup Formatter
[JIRA] (JENKINS-54055) MSDeploy ERROR_SITE_DOES_NOT_EXIST does not fail job
Title: Message Title Justin Nimmo updated an issue Jenkins / JENKINS-54055 MSDeploy ERROR_SITE_DOES_NOT_EXIST does not fail job Change By: Justin Nimmo Environment: Jenkins is on RHEL 7 Linux and agents are windows agents Server 2012 R2 . Active Directory plugin2.8 AnsiColor0.5.2 Ant Plugin1.8 Apache HttpComponents Client 4.x API Plugin4.5.5-3.0 Artifactory Plugin2.16.2 Audit Trail2.3 Authentication Tokens API Plugin1.3 Autofavorite for Blue Ocean1.2.2 Bitbucket Branch Source Plugin2.2.12 Bitbucket Pipeline for Blue Ocean1.6.2 Bitbucket Plugin1.1.8 Blue Ocean1.6.2 Blue Ocean Core JS1.6.2 Blue Ocean Pipeline Editor1.6.2 bouncycastle API Plugin2.17 Branch API Plugin2.0.20 Build Monitor View1.12+build.201809061734 Build Timeout1.19 build-name-setter1.6.9 built-on-column1.1 change-assembly-version-plugin1.10 Checkstyle Plug-in3.50 Command Agent Launcher Plugin1.2 Common API for Blue Ocean1.6.2 Compact Columns1.10 Conditional BuildStep1.3.6 Config API for Blue Ocean1.6.2 Config File Provider3.2 Console Column Plugin1.5 Console Tail Plugin1.1 Copy Artifact1.39.1 Copy project link plugin1.5 Credentials Binding Plugin1.16 Credentials Plugin2.1.18 Dashboard for Blue Ocean1.6.2 Dashboard View2.9.11 Deploy to container Plugin1.13 Design Language1.6.2 Display URL API2.2.0 Display URL for Blue Ocean2.2.0 Docker Commons Plugin1.13 Docker Pipeline1.17 Drop Down ViewsTabBar Plugin1.7 Durable Task Plugin1.26 Email Extension Plugin2.63 embeddable-build-status1.9 EnvInject API Plugin1.5 Environment Injector Plugin2.1.6 Escaped Markup Plugin0.1 Events API for Blue Ocean1.6.2 Extended Choice Parameter Plug-In0.76 External Monitor Job Type Plugin1.7 Extra Columns Plugin1.20 Favorite2.3.2 Flyway Runner1.9 Folders6.5.1 Git client plugin2.7.3 Git Parameter0.9.5 Git Pipeline for Blue Ocean1.6.2 Git plugin3.9.1 GIT server Plugin1.7 GitHub API Plugin1.92 GitHub Branch Source Plugin2.4.0 GitHub Pipeline for Blue Ocean1.6.2 GitHub plugin1.29.3 Gradle Plugin1.29 Handy Uri Templates 2.x API Plugin2.1.6-1.0 HPE Security Fortify Jenkins Plugin17.20.0183 HTML Publisher plugin1.17 i18n for Blue Ocean1.6.2 Icon Shim Plugin2.0.3 Infrastructure plugin for Publish Over X0.22 Ivy Plugin1.28 Jackson 2 API Plugin2.8.11.3 Javadoc Plugin1.4 _javascript_ GUI Lib: ACE Editor bundle plugin1.1 _javascript_ GUI Lib: Handlebars bundle plugin1.1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin1.2.1 _javascript_ GUI Lib: Moment.js bundle plugin1.1.1 JDK Tool1.0 JIRA Integration for Blue Ocean1.6.2 JIRA plugin3.0.2 Job Configuration History Plugin2.18.2 Job Import Plugin3.0 jQuery plugin1.12.4-0 JSch dependency plugin0.1.54.2 JUnit Plugin1.26.1 JWT for Blue Ocean1.6.2 LDAP Plugin1.20 Mailer Plugin1.21 MapDB API Plugin1.0.9.0 Mask Passwords Plugin2.12.0 Matrix Authorization Strategy Plugin2.3 Matrix Project Plugin1.13 Maven Integration plugin3.1.2 Mercurial plugin2.4 Metrics Plugin4.0.2.2 Modern Status1.2 MSBuild Plugin1.29 MSTest plugin0.23 MSTestRunner plugin1.3.0 Multiple SCMs plugin0.6 Nested View Plugin1.14 New Relic Deployment Notifier1.3 Next Build Number Plugin1.5 Nuget Plugin0.7 NUnit plugin0.23 OWASP Markup Formatter Plugin1.5 PAM Authentication plugin1.4
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-54031 GitHub OAuth plugin fails with Jenkins 2.146 Change By: Daniel Beck 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54030) "java.lang.IllegalStateException: closed" for GitHub Branch Source 2.4.0
Title: Message Title Karl Shultz commented on JENKINS-54030 Re: "java.lang.IllegalStateException: closed" for GitHub Branch Source 2.4.0 Nick Jones - would you mind closing this issue as a duplicate of JENKINS-54046? Normally I prefer to "keep the older ones," so to speak, but the conversation accidentally happened over there instead. I can do it, but thought I'd let you since you're the originator (and not everybody likes having their bugs closed by other people). 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54055) MSDeploy ERROR_SITE_DOES_NOT_EXIST does not fail job
Title: Message Title Justin Nimmo created an issue Jenkins / JENKINS-54055 MSDeploy ERROR_SITE_DOES_NOT_EXIST does not fail job Issue Type: Bug Assignee: Unassigned Components: pipeline, pipeline-stage-step-plugin Created: 2018-10-12 19:32 Environment: Jenkins is on Linux and agents are windows agents. Active Directory plugin 2.8 AnsiColor 0.5.2 Ant Plugin 1.8 Apache HttpComponents Client 4.x API Plugin 4.5.5-3.0 Artifactory Plugin 2.16.2 Audit Trail 2.3 Authentication Tokens API Plugin 1.3 Autofavorite for Blue Ocean 1.2.2 Bitbucket Branch Source Plugin 2.2.12 Bitbucket Pipeline for Blue Ocean 1.6.2 Bitbucket Plugin 1.1.8 Blue Ocean 1.6.2 Blue Ocean Core JS 1.6.2 Blue Ocean Pipeline Editor 1.6.2 bouncycastle API Plugin 2.17 Branch API Plugin 2.0.20 Build Monitor View 1.12+build.201809061734 Build Timeout 1.19 build-name-setter 1.6.9 built-on-column 1.1 change-assembly-version-plugin 1.10 Checkstyle Plug-in 3.50 Command Agent Launcher Plugin 1.2 Common API for Blue Ocean 1.6.2 Compact Columns 1.10 Conditional BuildStep 1.3.6 Config API for Blue Ocean 1.6.2 Config File Provider 3.2 Console Column Plugin 1.5 Console Tail Plugin 1.1 Copy Artifact 1.39.1 Copy project link plugin 1.5 Credentials Binding Plugin 1.16 Credentials Plugin 2.1.18 Dashboard for Blue Ocean 1.6.2 Dashboard View 2.9.11 Deploy to container Plugin 1.13 Design Language 1.6.2 Display URL API 2.2.0 Display URL for Blue Ocean 2.2.0 Docker Commons Plugin 1.13 Docker Pipeline 1.17 Drop Down ViewsTabBar Plugin 1.7 Durable Task Plugin 1.26 Email Extension Plugin 2.63 embeddable-build-status 1.9 EnvInject API Plugin 1.5 Environment Injector Plugin 2.1.6 Escaped Markup Plugin 0.1 Events API for Blue Ocean 1.6.2 Extended Choice Parameter Plug-In 0.76 External Monitor Job Type Plugin 1.7 Extra Columns Plugin 1.20 Favorite 2.3.2 Flyway Runner 1.9 Folders 6.5.1 Git client plugin 2.7.3 Git Parameter 0.9.5 Git Pipeline for Blue Ocean 1.6.2 Git plugin 3.9.1 GIT server Plugin 1.7 GitHub API Plugin 1.92 GitHub Branch Source Plugin 2.4.0 GitHub Pipeline for Blue Ocean 1.6.2 GitHub plugin 1.29.3 Gradle Plugin 1.29 Handy Uri Templates 2.x API Plugin 2.1.6-1.0 HPE Security Fortify Jenkins Plugin 17.20.0183 HTML Publisher plugin 1.17 i18n for Blue Ocean 1.6.2 Icon Shim Plugin 2.0.3 Infrastructure plugin for Publish Over X 0.22 Ivy Plugin 1.28 Jackson 2 API Plugin 2.8.11.3 Javadoc Plugin 1.4 _javascript_ GUI Lib: ACE Editor bundle plugin
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Daniel Beck commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 (Note that my comment was originally written for a different report, so it might not only affect allowAnonymousReadPermission. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Daniel Beck commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 It seems that GitHub OAuth plugin ignores permission relationships, specifically permissions implied by Item/Read with allowAnonymousReadPermission set. Item/Discover is declared to be implied by Item/Read: https://github.com/jenkinsci/jenkins/blob/371b9c134681e3e04f52a5e0bb39c747e6d44c45/core/src/main/java/hudson/model/Item.java#L258 That's what the Stapler routing hardening in 2.138.2 and 2.146 assumes to be the case to make this nice and succinct: https://github.com/jenkinsci/jenkins/blob/371b9c134681e3e04f52a5e0bb39c747e6d44c45/core/src/main/java/hudson/model/AbstractItem.java#L942...L949 (This slightly more readable code that'll make it into 2.147 after https://github.com/jenkinsci/jenkins/pull/3690 but functionally in this regard identical to what's in 2.138.2) GitHub OAuth needs to handle permissions implied by those it grants, at least Item/Discover. I'm pretty OK with the behavior in core. Meanwhile, you could set the system property hudson.model.AbstractItem.skipPermissionCheck to true ( https://wiki.jenkins.io/display/JENKINS/Features+controlled+by+system+properties ), but note that this disables a security improvement. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53956) Pipeline job hangs forever at end
Title: Message Title Sam Van Oort commented on JENKINS-53956 Re: Pipeline job hangs forever at end Jose Blas Camacho Taboada Please could you take a look? Thanks! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53958) Pipeline Jobs not started when locale master Node is offline
Title: Message Title Sam Van Oort commented on JENKINS-53958 Re: Pipeline Jobs not started when locale master Node is offline Daniel Hoerner Not clear what you mean, what do you mean by "defined another master node" and "alternative master"? Specifically what does this mean: > I have defined another master Node with Name 'master' and this Node is online. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54035) can't exclude everything under a given dir
Title: Message Title
Brian J Murrell commented on JENKINS-54035
Re: can't exclude everything under a given dir
I've tried GnuMakeGcc since in fact the files I want to exclude in in projects under the excluded subdirectory built with make. I have also added a second filter to match non-fully-qualified path names in addition to the fully-qualified-path filter I already had:
filters: [excludeFile('.*\\/_build\\.external\\/.*'),
excludeFile('_build\\.external\\/.*')]
Neither of those has eliminated the bulk of those 700+ compiler warnings that I want to exclude.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46354) Retry in Declarative options skips retried stages due to earlier failure
Title: Message Title
Bruno Campolo commented on JENKINS-46354
Re: Retry in Declarative options skips retried stages due to earlier failure
import jenkins.model.*
pipeline {
agent any
options {
retry(3)
}
stages {
stage('Stage1') {
steps {
echo "Starting Stage1"
}
}
stage('Stage2') {
steps {
echo "Starting Stage2"
error "This will cause the pipeline to retry"
}
}
}
post {
always {
echo 'This will always run'
}
success {
echo 'This will run only if successful'
}
failure {
echo 'This will run upon failure'
}
unstable {
echo 'This will run only if the run was marked as unstable'
}
changed {
echo 'This will run only if the state of the Pipeline has changed'
}
}
}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46354) Retry in Declarative options skips retried stages due to earlier failure
Title: Message Title
Bruno Campolo updated an issue
Jenkins / JENKINS-46354
Retry in Declarative options skips retried stages due to earlier failure
Change By:
Bruno Campolo
Comment:
{code:java}// code placeholder{code}import jenkins.model.*pipeline \{ agent any options { retry(3) } stages \{ stage('Stage1') { steps { echo "Starting Stage1" } } stage('Stage2') \{ steps { echo "Starting Stage2" error "This will cause the pipeline to retry" } } } post \{ always { echo 'This will always run' } success \{ echo 'This will run only if successful' } failure \{ echo 'This will run upon failure' } unstable \{ echo 'This will run only if the run was marked as unstable' } changed \{ echo 'This will run only if the state of the Pipeline has changed' } } }
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46354) Retry in Declarative options skips retried stages due to earlier failure
Title: Message Title
Bruno Campolo commented on JENKINS-46354
Re: Retry in Declarative options skips retried stages due to earlier failure
// code placeholder
import jenkins.model.*pipeline { agent any options { retry(3) } stages { stage('Stage1') { steps { echo "Starting Stage1" } } stage('Stage2') { steps { echo "Starting Stage2" error "This will cause the pipeline to retry" } } } post { always { echo 'This will always run' } success { echo 'This will run only if successful' } failure { echo 'This will run upon failure' } unstable { echo 'This will run only if the run was marked as unstable' } changed { echo 'This will run only if the state of the Pipeline has changed' } } }
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53689) Unity3d Failed To Build due to mergeReleaseResources FAILED error
Title: Message Title Dogukan Erkut assigned an issue to Dogukan Erkut Jenkins / JENKINS-53689 Unity3d Failed To Build due to mergeReleaseResources FAILED error Change By: Dogukan Erkut Assignee: lacostej Dogukan Erkut 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53689) Unity3d Failed To Build due to mergeReleaseResources FAILED error
Title: Message Title Dogukan Erkut assigned an issue to lacostej Jenkins / JENKINS-53689 Unity3d Failed To Build due to mergeReleaseResources FAILED error Change By: Dogukan Erkut Assignee: Dogukan Erkut lacostej 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Elie Kassis commented on JENKINS-53735 Re: Parallel sequential stages not showing Triggered Builds while Processing hi Olivier Lamy, are you planning to fix 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Nick Jones commented on JENKINS-54046 Re: GitHub branch souce plugin fails to move temporary files Thanks for your help, Karl Shultz! In our test Jenkins environment, I've updated the jenkins.xml file to set the system property, upgraded back to 2.4.0, and confirmed that the Script Console reports the cacheSize as being 0 after a restart. I'll keep an eye on it to see whether the error recurs there, but will otherwise hold off on upgrading our production Jenkins instance to 2.4.0 until I'm quite certain the issue is resolved by this system property (or there's a newer version of the plugin that fixes the underlying 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54009) Changelogs for Blue Ocean 1.8.4 and 1.9.0 are missing
Title: Message Title Keith Zantow updated JENKINS-54009 Jenkins / JENKINS-54009 Changelogs for Blue Ocean 1.8.4 and 1.9.0 are missing Change By: Keith Zantow 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54009) Changelogs for Blue Ocean 1.8.4 and 1.9.0 are missing
Title: Message Title Keith Zantow updated JENKINS-54009 Jenkins / JENKINS-54009 Changelogs for Blue Ocean 1.8.4 and 1.9.0 are missing Change By: Keith Zantow 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54053) Git plugin uses git.exe as default on Windows server, even for Linux agents
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-54053 Git plugin uses git.exe as default on Windows server, even for Linux agents Change By: Mark Waite Assignee: Mark Waite 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54035) can't exclude everything under a given dir
Title: Message Title
Brian J Murrell commented on JENKINS-54035
Re: can't exclude everything under a given dir
But that doesn't seem to be working either. I have:
filters: [excludeFile('.*\\/_build.external\\/.*')]
But still seeing this when I click the exclamation mark:
Can't resolve absolute paths for some files:- topology-linux.c- topology-linux.c- topology-linux.c- topology-linux.c- topology-linux.c ... skipped logging of 761 additional errors ...Can't create fingerprints for some files:- 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c- 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c- 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c- 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c- 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c ... skipped logging of 767 additional errors ...Can't create blame requests for some affected files:- Skipping non-workspace file topology-linux.c- Skipping non-workspace file topology-linux.c- Skipping non-workspace file topology-linux.c- Skipping non-workspace file topology-linux.c- Skipping non-workspace file topology-linux.c ... skipped logging of 761 additional errors ...Git blame reported several errors:No blame results for request <@2/_build.external/mercury/Testing/util/test_atomic_queue.c - [32, 31]>.
Git blame reported several errors:No blame results for request <_build.external/mercury/Testing/na/na_test.c - [517]>.
Git blame reported several errors:No blame results for request <_build.external/pmix/src/mca/gds/gds.h - [320]>.
Git blame reported several errors:No blame results for request <_build.external/mercury/src/util/mercury_atomic_queue.h - [158]>.
Git blame reported several errors:No blame results for request <@2/_build.external/pmix/src/mca/gds/gds.h - [320]>.
Git blame reported several errors:No blame results for request <@2/_build.external/mercury/Testing/na/na_test.c - [517]>.
Git blame reported several errors:No blame results for request <@2/_build.external/mercury/src/util/mercury_atomic_queue.h - [158]>.
Git blame reported several errors:No blame results for request <_build.external/mercury/Testing/driver/kwsys/ProcessUNIX.c - [1477]>.
Git blame reported several errors:No blame results for request <@2/_build.external/mercury/Testing/driver/kwsys/ProcessUNIX.c - [1477]>.
I would think I shouldn't be seeing those <@2/build.external/mercury _git blame issues if the filter was working correctly should i? On the other hand I also see:
Information Messages
Parsing console log (workspace: '/var/lib/jenkins/workspace/daos-stack-org_daos_PR-13-XSYVVAKVRRCIRZBUBQLEPYMVXQHYAQV52HHPQR55EURLM5NXUHMA')
Post processing issues on
[JIRA] (JENKINS-54052) MultibranchProject ignores quietPeriod
Title: Message Title Anton Tanasenko commented on JENKINS-54052 Re: MultibranchProject ignores quietPeriod https://github.com/jenkinsci/branch-api-plugin/pull/131 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54054) Job URL passed to webhook is incorrect (null base url)
Title: Message Title Alexander Komarov created an issue Jenkins / JENKINS-54054 Job URL passed to webhook is incorrect (null base url) Issue Type: Bug Assignee: Jo Vandeginste Components: mattermost-plugin Created: 2018-10-12 16:36 Environment: Jenkins 2.144 Plugin: mattermost: 2.5.2 Mattermost: 5.3.1 Priority: Minor Reporter: Alexander Komarov Problem Job status notifications sent to Jenkins have the following link back url: http://nulljob/test-mattermost/8/ While "Test" button notifications (from Global Configuration or from Job Config) have the correct Jenkins base URL: Mattermost/Jenkins plugin: you're all set! (parameters: endpoint='https://MATTERMOST/hooks/', room='test', icon='', buildServerUrl='http://JENKINS:8080/') Configuration My global configuration has a Jenkins URL correctly set. I've tried both setting and not setting the Build Server URL in the Mattermost config section (to the same value), same result. It doesn't matter if I specify the mattermost endpoint URL/channel in the job or in global, or both. Jenkins log:
[JIRA] (JENKINS-54035) can't exclude everything under a given dir
Title: Message Title
Brian J Murrell edited a comment on JENKINS-54035
Re: can't exclude everything under a given dir
Surely the RE for your example should be: . \ *\/path\/to\/exclude\/. \ * , yes? Or is {{/}} not considered special in whatever RE module you are using?
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54035) can't exclude everything under a given dir
Title: Message Title
Brian J Murrell edited a comment on JENKINS-54035
Re: can't exclude everything under a given dir
Surely the RE for your example should be: .*\/path\/to\/exclude\/.*, yes? Or is {{/}} not considered special in whatever RE module you are using?
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title
Brian J Murrell commented on JENKINS-48300
Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
The workaround I tried was to go to Manage Jenkins -> System Console
Did you mean Script Console (/script)
System.setProperty("org.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL", 36000)
When I did that I got:
groovy.lang.MissingMethodException: No signature of method: static java.lang.System.setProperty() is applicable for argument types: (java.lang.String, java.lang.Integer) values: [org.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL, ...]
Possible solutions: setProperty(java.lang.String, java.lang.String), getProperty(java.lang.String), getProperty(java.lang.String, java.lang.String), hasProperty(java.lang.String), getProperties(), getProperties()
at groovy.lang.MetaClassImpl.invokeStaticMissingMethod(MetaClassImpl.java:1501)
at groovy.lang.MetaClassImpl.invokeStaticMethod(MetaClassImpl.java:1487)
at org.codehaus.groovy.runtime.callsite.StaticMetaClassSite.call(StaticMetaClassSite.java:53)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:133)
at Script1.run(Script1.groovy:1)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:585)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:623)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:594)
at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:142)
at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:114)
at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
at hudson.util.RemotingDiagnostics.executeGroovy(RemotingDiagnostics.java:111)
at jenkins.model.Jenkins._doScript(Jenkins.java:4381)
at jenkins.model.Jenkins.doScript(Jenkins.java:4352)
at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:860)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)
at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225)
at
[JIRA] (JENKINS-54053) Git plugin uses git.exe as default on Windows server, even for Linux agents
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-54053 Git plugin uses git.exe as default on Windows server, even for Linux agents Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-10-12 16:24 Environment: Jenkins 2.146 Default plugins Priority: Minor Reporter: Mark Waite When I run Jenkins from the war file on Windows with the default plugins, it defines the git implementation as "git.exe" instead of "git". When I add a Linux agent, it incorrectly attempts to use "git.exe" as the git executable on the Linux agent. It should use "git" as the default git implementation on Linux agents even when connected from a Windows master. Add Comment
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title
Karl Shultz edited a comment on JENKINS-54046
Re: GitHub branch souce plugin fails to move temporary files
Looks like the default file on a Windows system would be {{C:\Program Files\Jenkins\jenkins.xml}}. Judging by what I see in the traces that [~medianick] and [~lwiechec] provided, I'm guessing both of yours will be in {{C:\Jenkins\jenkins.xml}}. Edit that file, find the {{}} tag, and add the system property disabling the cache there, without removing any of the settings you already had there:{ { code:xml}** leave the existing settings alone and add ** -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0{code}Personally, I hate editing xml files, so maybe take a backup of that file before you do so.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title
Karl Shultz commented on JENKINS-54046
Re: GitHub branch souce plugin fails to move temporary files
Looks like the default file on a Windows system would be C:\Program Files\Jenkins\jenkins.xml. Judging by what I see in the traces that Nick Jones and Lukasz Wiechec provided, I'm guessing both of yours will be in C:\Jenkins\jenkins.xml. Edit that file, find the tag, and add the system property disabling the cache there, without removing any of the settings you already had there: {{code:xml} ** leave the existing settings alone and add ** -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0
Personally, I hate editing xml files, so maybe take a backup of that file before you do so.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54052) MultibranchProject ignores quietPeriod
Title: Message Title Anton Tanasenko created an issue Jenkins / JENKINS-54052 MultibranchProject ignores quietPeriod Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2018-10-12 16:08 Priority: Minor Reporter: Anton Tanasenko Quiet period is ignored when scheduling build in a multibranch project. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Karl Shultz commented on JENKINS-54046 Re: GitHub branch souce plugin fails to move temporary files No. When set via the script console, you'll be back to 20 after a restart. To have the change persist, you'll want to set a system property. On my box (which is running Ubuntu Linux), that lives in /etc/default/jenkins. In JAVA_ARGS, mine now looks like this. # arguments to pass to java # Allow graphs etc. to work even when an X server is present # JAVA_ARGS="-Djava.awt.headless=true" JAVA_ARGS="-Djava.awt.headless=true -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0" Once the property is set, restart Jenkins via sudo service jenkins restart, or by whatever means you use on Windows to do the same thing. If you're running via java -jar..., you should be able to use the -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0 property right there. There's a second way to confirm that the setting has been changed. Under Manage Jenkins, go to "System Information" and look for the property. Should look like this now (I've drawn a red box around 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-54046 GitHub branch souce plugin fails to move temporary files Change By: Karl Shultz Attachment: screenshot-3.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54051) GitHub-Branch-Source plugin 2.3.5 Security Update causing error in adding GitHub Enterprise Servers
Title: Message Title Trey Owens created an issue Jenkins / JENKINS-54051 GitHub-Branch-Source plugin 2.3.5 Security Update causing error in adding GitHub Enterprise Servers Issue Type: Bug Assignee: Unassigned Attachments: Github-branch-source_Add_GIt_Enterprise_Error.png Components: github-branch-source-plugin Created: 2018-10-12 15:46 Environment: GitHub-Branch-Source-Plugin 2.3.5+ CB Jenkins 2.138.x Labels: github-branch-source-plugin plugins Priority: Minor Reporter: Trey Owens Version 2.3.5 of the GitHub-Branch-Source Plugin introduced a bug that is causing an error to be displayed when trying to add GitHub Enterprise Servers within `Manage Jenkins-> Configure System -> GitHub Enterprise Servers` "This URL Requires POST" as the new security patch in 2.3.5 is background checking valid URLs. This error displays whether the `API endpoint` field is blank or has a valid endpoint specified. Downgrading to version 2.3.4 of the GitHub-Branch-Source Plugin no longer displays the error. Picture is attached showing the error.
[JIRA] (JENKINS-35708) EC2 Plugin: Ability to round robin EC2 availability zones
Title: Message Title Matt Sicker updated JENKINS-35708 Jenkins / JENKINS-35708 EC2 Plugin: Ability to round robin EC2 availability zones Change By: Matt Sicker Status: Open Fixed but Unreleased Resolution: Fixed Released As: 1.41 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52828) Add slave suffix command
Title: Message Title Matt Sicker updated JENKINS-52828 Jenkins / JENKINS-52828 Add slave suffix command Change By: Matt Sicker Status: Open Fixed but Unreleased Resolution: Fixed Released As: 1.41 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53048) Parallel sequential stages not rendering correctly
Title: Message Title
Adam Carroll commented on JENKINS-53048
Re: Parallel sequential stages not rendering correctly
I recently updated to use the newest version of BlueOcean (1.9) and this behavior does not work for a scripted pipeline, only declarative. My sequential nodes end up squashed into one stage. Is it expected to work for scripted? My basic scripted pipeline structure looks like this: stage("Build and test") { parallel linux: { node("nodeA") { ... } node("nodeB") { .. } }, windows: { .
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54039) Calendar plugin: Future scheduled jobs not showing up
Title: Message Title Sven Schoenung commented on JENKINS-54039 Re: Calendar plugin: Future scheduled jobs not showing up Much of what I wrote in the other ticket (JENKINS-54037) also applies here. In addition it would be helpful to know the exact cron _expression_ that you're using. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54037) Calendar plugin: Not all jobs showing up
Title: Message Title Sven Schoenung commented on JENKINS-54037 Re: Calendar plugin: Not all jobs showing up There's no minimally required duration for builds. They always show up no matter how long they took. When displayed in the calendar they're always big enough so that the name of the job can be displayed. Example: My guess is that the problem is somewhere else. Some things to check: 1. See if the [Jenkins logfile](https://wiki.jenkins.io/display/JENKINS/Logging) shows any exceptions coming from the calendar-view plugin. 2. Create a List View where everything is configured the same as for the Calendar View. Does the job show up in the List View? (CalendarView is a subtype of ListView and inherits much of its behaviour. If a job doesn't display in ListView, its builds won't show up in CalendarView either). 3. Open /job/NAME_OF_YOUR_JOB/api/json in a browser. This should give information about the type of job we're talking about as well as its builds. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53779) Code decoupling
Title: Message Title Rolando-Mihai Vlad resolved as Fixed Jenkins / JENKINS-53779 Code decoupling Change By: Rolando-Mihai Vlad 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53779) Code decoupling
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-53779 Re: Code decoupling Test passed. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Karl Shultz commented on JENKINS-54046 Re: GitHub branch souce plugin fails to move temporary files Nick Jones, I'll try it and let you know. BRB. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Karl Shultz commented on JENKINS-54046 Re: GitHub branch souce plugin fails to move temporary files Great. Thanks for getting back to me and confirming that! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before We have done some investiation, it seem indeed that the environment variable injection to shell is the culprit here. However, the problem seem deeper than that and involve the fabric8 kubernetes Watchexec PipeInput which is really slow. Still, If the watch channel could be kept open during every step within a container steps and send the envVars only a single time could probably improve performance quite a lot. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53965) ConsoleLog is missing build output
Title: Message Title Jesse Glick commented on JENKINS-53965 Re: ConsoleLog is missing build output In the first case the aggregated log file actually starts with 12 NUL bytes, where hello\nworld\n should have been. I guess the combination of /dev/std* pseudo-files and stream redirection wreaks havoc somewhere, though I do not understand it exactly. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54037) Calendar plugin: Not all jobs showing up
Title: Message Title Sven Schoenung updated an issue Jenkins / JENKINS-54037 Calendar plugin: Not all jobs showing up Change By: Sven Schoenung Attachment: very_fast_build.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46354) Retry in Declarative options skips retried stages due to earlier failure
Title: Message Title Jesse Glick commented on JENKINS-46354 Re: Retry in Declarative options skips retried stages due to earlier failure So…is there a test case that does not involve script? That is really all I was getting at. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Nick Jones commented on JENKINS-54046 Re: GitHub branch souce plugin fails to move temporary files Karl Shultz, does setting the org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize to 0 in the Script Console persist across Jenkins service restarts, or is there a command-line option that would accomplish that? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54030) "java.lang.IllegalStateException: closed" for GitHub Branch Source 2.4.0
Title: Message Title Nick Jones commented on JENKINS-54030 Re: "java.lang.IllegalStateException: closed" for GitHub Branch Source 2.4.0 Karl Shultz – yes, master is running Windows Server 2012 R2 (for now; we're migrating to 2016 soon), and all build agents are running Windows Server 2016. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Lukasz Wiechec commented on JENKINS-54046 Re: GitHub branch souce plugin fails to move temporary files Karl, thanks - I set the cache to 0 (it was showing 20, as you correctly predicted) and - it removed the problem. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54030) "java.lang.IllegalStateException: closed" for GitHub Branch Source 2.4.0
Title: Message Title Karl Shultz commented on JENKINS-54030 Re: "java.lang.IllegalStateException: closed" for GitHub Branch Source 2.4.0 Also - I've posted information for how to disable the caching in JENKINS-54046, which looks to be a duplicate of this issue. One or the other will probably get closed as a duplicate eventually. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Karl Shultz commented on JENKINS-54046 Re: GitHub branch souce plugin fails to move temporary files Once that's done, I'm hoping the problem will disappear. The root cause of this is still under investigation, but there are a handful of open issues and PRs in okhttp that look similar. Most notably, this one. Stephen Connolly - FYI. I think we have some Windows users who are hitting problems with the cache, possibly because it's renaming files that are still open. In the meantime, as written up above, I've suggested to the reporter that they disable the cache entirely. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Karl Shultz commented on JENKINS-54046 Re: GitHub branch souce plugin fails to move temporary files Lukasz Wiechec - thanks for reporting this. It appears to be the same issue as reported in JENKINS-54030|https://issues.jenkins-ci.org/browse/JENKINS-54030]. If you've got the ability (and the willingness ) to do this, here's something you can try. Let's try turning off the disk cache entirely. Here's how. 1. Go to the Script console on your Jenkins instance. That's at https://:port-number/script. 2. In that window, enter the following: org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize and click Run. You should see a result of 20. 3. To turn the caching off entirely, run the same command again, but append =0 to the end of it. org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0 This should now return 0, meaning the cache is disabled. You can then run it again, without the =0 on its end, to verify that the change took. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-54046 GitHub branch souce plugin fails to move temporary files Change By: Karl Shultz Attachment: screenshot-2.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54048) Fetch single commit only
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-54048 Fetch single commit only Change By: Mark Waite Assignee: Mark Waite 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-54046 GitHub branch souce plugin fails to move temporary files Change By: Karl Shultz Attachment: screenshot-1.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54030) "java.lang.IllegalStateException: closed" for GitHub Branch Source 2.4.0
Title: Message Title Karl Shultz commented on JENKINS-54030 Re: "java.lang.IllegalStateException: closed" for GitHub Branch Source 2.4.0 Nick Jones, thanks for reporting it. From the trace, it looks like you're running Jenkins on Windows. Is that right? (That's fine if you are, BTW, just trying to narrow down the scope of the problem 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54009) Changelogs for Blue Ocean 1.8.4 and 1.9.0 are missing
Title: Message Title Keith Zantow started work on JENKINS-54009 Change By: Keith Zantow 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Sam Van Oort commented on JENKINS-46096 Re: Pipeline stage view rendered at bottom of page, below build history Tony Hoyle Marcus Philip You guys are welcome to take a stab at the proper fix for this if you like – the blocker with https://github.com/jenkinsci/pipeline-stage-view-plugin/pull/55 is that it is simply reverting https://github.com/jenkinsci/pipeline-stage-view-plugin/pull/35 – which makes sense with wider screens now quite common. What needs to happen is the graphs need to be at the top until the screen is wide enough, and then they should reflow to the right – but I'm no expert at CSS and our layouts aren't trivial, so I'm not sure how to do that. If someone else can provide a solution for that goal, I'd be happy to merge and release it though. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53923) Collecting build job results using [.result] property returns null
Title: Message Title Vassilena Treneva assigned an issue to Andrew Bayer Jenkins / JENKINS-53923 Collecting build job results using [.result] property returns null Change By: Vassilena Treneva 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53923) Collecting build job results using [.result] property returns null
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-53923 Collecting build job results using [.result] property returns null Change By: Vassilena Treneva Priority: Minor Major 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. For more options, visit https://groups.google.com/d/optout.
