[JIRA] (JENKINS-53867) Too many open files caused Jenkins crashed
Title: Message Title Tapio Reijonen edited a comment on JENKINS-53867 Re: Too many open files caused Jenkins crashed I think, we can't run this "file-leak-detecor",java.lang.Error: Failed to activate file leak detector: Exception in thread "main" java.lang.IllegalStateException: Unable to find tools.jar at /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/../lib/tools.jar --- — you need to run this tool with a JDK at org.kohsuke.file_leak_detector.Main.loadAttachApi(Main.java:73) at org.kohsuke.file_leak_detector.Main.run(Main.java:48) at org.kohsuke.file_leak_detector.Main.main(Main.java:36) Is this the only way to find out which component cause 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-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title yuan kang updated an issue Jenkins / JENKINS-53780 jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins Change By: yuan kang Labels: jira- plugin -3.0.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Mark Waite edited a comment on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites I've seen the same problem with Jenkins 2.138.1, Blue Ocean 1.8.4, and autofavoriting plugin 1.2.2.I built the tip of the plugin development branch and confirmed that the tip of the branch does not fail the builds. The build is available in [my github repository|https://github.com/MarkEWaite/docker-lfs/blob/02b72ca50f00447fd9824624544f1d8581665dec/ref/plugins/blueocean-autofavorite.jpi] if someone else needs it before the official release. I recommend the tip of the branch be released so that this bug is 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-41805) Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.
Title: Message Title Idan Adar commented on JENKINS-41805 Re: Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace. +1 Our agents remain unclean because of this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Mark Waite edited a comment on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites I've seen the same problem with Jenkins 2.138.1, Blue Ocean 1.8.4, and autofavoriting plugin 1.2.2 .I built the tip of the plugin development branch and confirmed that the tip of the branch does not fail the builds.I recommend the tip of the branch be released so that this bug is 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-53945) Adding a new configuration to the azure-vm-agents-plugin to enable MSI
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-53945 Adding a new configuration to the azure-vm-agents-plugin to enable MSI Change By: Jie Shen Assignee: Azure DevOps Jie Shen 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-49316) Create Item: OK button disabled until TAB pressed
Title: Message Title Daniel Sanchez commented on JENKINS-49316 Re: Create Item: OK button disabled until TAB pressed Just followed the steps you mentioned and the issue seems to be there. As well as if you delete your selection and don't select anything else, the OK button doesn't get disabled. I would like to work on this issue. I will be assigning it to myself. 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-49316) Create Item: OK button disabled until TAB pressed
Title: Message Title Daniel Sanchez assigned an issue to Daniel Sanchez Jenkins / JENKINS-49316 Create Item: OK button disabled until TAB pressed Change By: Daniel Sanchez Assignee: Daniel Sanchez 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-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Nick Follett edited a comment on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
I am having this problem with declarative pipelines. {code:java}pipeline { agent any options {ansiColor('xterm')// Prevent multiple pipelines from running concurrently and failing due to tfstate lock filedisableConcurrentBuilds() } triggers {gitlab( branchFilterType: 'All', triggerOnPush: false, triggerOnMergeRequest: true, triggerOpenMergeRequestOnPush: "never", triggerOnNoteRequest: true, noteRegex: "jenkins rebuild", skipWorkInProgressMergeRequest: true,) } ...}{code} All of my pipelines are auto-imported from a separate job using the Job DSL plugin. I need to manually run each job once in order for the config.xml to be populated with the settings from the Jenkinsfile. When I check the configuration in the UI after this initial run I see that the pipeline is configured with the settings shown above. After I trigger the pipeline with a test merge request in GitLab the pipeline will succeed, but the trigger settings will disappear in the UI. If I trigger the job again manually the trigger settings for GitLab webhooks will re-appear.[Jenkins ver. 2.107.3|https://jenkins.io/]
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-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Nick Follett commented on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
I am having this problem with declarative pipelines.
pipeline {
agent any
options {
ansiColor('xterm')
// Prevent multiple pipelines from running concurrently and failing due to tfstate lock file
disableConcurrentBuilds()
}
triggers {
gitlab(
branchFilterType: 'All',
triggerOnPush: false,
triggerOnMergeRequest: true,
triggerOpenMergeRequestOnPush: "never",
triggerOnNoteRequest: true,
noteRegex: "jenkins rebuild",
skipWorkInProgressMergeRequest: true,
)
}
...
}
All of my pipelines are auto-imported from a separate job using the Job DSL plugin. I need to manually run each job once in order for the config.xml to be populated with the settings from the Jenkinsfile. When I check the configuration in the UI after this initial run I see that the pipeline is configured with the settings shown above. After I trigger the pipeline with a test merge request in GitLab the pipeline will succeed, but the trigger settings will disappear in the UI.
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-53952) Linux slaves are not starting anymore
Title: Message Title Gunter Grodotzki created an issue Jenkins / JENKINS-53952 Linux slaves are not starting anymore Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2018-10-08 23:23 Environment: Jenkins ver. 2.138.1 Priority: Blocker Reporter: Gunter Grodotzki Similar to https://issues.jenkins-ci.org/browse/JENKINS-53876 Unfortunately with the latest 1.40.1 EC2 nodes are not launching anymore: $ cat Jenkins\ Prebuilt\ Slave\ \(sir-p9ai6v8m\)/slave.log Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: null Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: Using key: master xxx -BEGIN RSA PRIVATE KEY- xxx Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as ubuntu ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:368) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:318) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:282) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at
[JIRA] (JENKINS-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Simon DeMartini commented on JENKINS-53920 Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again I've started experiencing this issue as well after a recent upgrade to 1.40. It looks like the plugin stops the nodes all right, but when it goes to restart them, it tries to connect but constantly times out and it looks like the EC2 instance it should have started is still stopped 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-53951) withMaven fail to set maven path when global variable is set
Title: Message Title Bernardo Vale updated an issue Jenkins / JENKINS-53951 withMaven fail to set maven path when global variable is set Change By: Bernardo Vale If there's a global variable defining a path to maven /bin . Pipeline integration fails to setup the request requested maven tool. **Steps to Reproduce**1. Install two maven versions, say 3.5.3 and 3.5.4 2. Define a global variable MAVEN+ PATH +MAVEN =/path/to/maven/3.5.3 /bin 3. Create a pipeline that uses withMaven step selecting maven 3.5.4Run sh "mvn --version"We expect it to show selected version 3.5.4 but it will show 3.5.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53951) withMaven fail to set maven path when global variable is set
Title: Message Title Bernardo Vale created an issue Jenkins / JENKINS-53951 withMaven fail to set maven path when global variable is set Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-10-08 21:14 Environment: Jenkins ver. 2.107.3 Priority: Minor Reporter: Bernardo Vale If there's a global variable defining a path to maven. Pipeline integration fails to setup the request maven tool. *Steps to Reproduce* 1. Install two maven versions, say 3.5.3 and 3.5.4 2. Define a global variable MAVEN+PATH=/path/to/maven/3.5.3 3. Create a pipeline that uses withMaven step selecting maven 3.5.4 Run sh "mvn --version" We expect it to show selected version 3.5.4 but it will show 3.5.3 Add Comment
[JIRA] (JENKINS-53750) Shell scripts keep the working directory locked on Windows
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-53750 Shell scripts keep the working directory locked on Windows Change By: Devin Nusbaum Component/s: workflow-durable-task-step-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53750) Shell scripts keep the working directory locked on Windows
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-53750
Re: Shell scripts keep the working directory locked on Windows
While it would be nice to improve the behavior here, it seems like there are some straightforward workarounds if I understand correctly: * Move the directory manipulation into your sh/bat script, and combine your scripts into one (it's generally better to combine your scripts anyways) * Add a manual {{sleep}} between sh/bat steps in cases where both scripts both modify the same directory in the workspace.We do not explicitly test using ` {{ sh ` }} on Windows, so although you may be able to get it working with Cygwin, MSys, etc., and we will do our best to fix any regressions we introduce, it is not recommended, and something like this that has never worked (as far as I can tell) does not seem like something we would prioritize for a fix.That said, the code is open source, and if you want to work on fixing it, I am happy to help review your changes. I would start with creating a reproduction test in [workflow-durable-task-step|https://github.com/jenkinsci/workflow-durable-task-step-plugin] step along the lines of the following to demonstrate the issue: {code :java }@Issue("JENKINS-53750")@Test public void cleanupBeforeStepCompletes() throws Exception {Assume.assumeTrue("Test is Windows-specific", Functions.isWindows());WorkflowJob p = j.jenkins.createProject(WorkflowJob.class, "p");p.setDefinition(new CpsFlowDefinition("node {\n" +" dir('foo/bar') {\n" +"sh 'sleep 1'\n" +" }\n" +" bat 'rename foo baz'\n" +"}", true));j.assertBuildStatusSuccess(p.scheduleBuild2(0));}{code} Once you have that test failing in the way you intend, you could make changes to BourneShellScript/FileMonitoringTask in durable-task to see how they affect the test. I don't have an environment to be able to reproduce the issue myself, but maybe something like switching [these two lines|https://github.com/jenkinsci/durable-task-plugin/blob/2016c3f3e3f10a8bd51a7b2d073ef7eb91d85f10/src/main/java/org/jenkinsci/plugins/durabletask/FileMonitoringTask.java#L488-L489] so the workspace is cleaned up before the script exits would help?
Add Comment
[JIRA] (JENKINS-53750) Shell scripts keep the working directory locked on Windows
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-53750 Shell scripts keep the working directory locked on Windows Change By: Devin Nusbaum Labels: pipeline sh 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-53750) Shell scripts keep the working directory locked on Windows
Title: Message Title
Devin Nusbaum commented on JENKINS-53750
Re: Shell scripts keep the working directory locked on Windows
While it would be nice to improve the behavior here, it seems like there are some straightforward workarounds if I understand correctly:
Move the directory manipulation into your sh/bat script, and combine your scripts into one (it's generally better to combine your scripts anyways)
Add a manual sleep between sh/bat steps in cases where both scripts both modify the same directory in the workspace.
We do not explicitly test using `sh` on Windows, so although you may be able to get it working with Cygwin, MSys, etc., and we will do our best to fix any regressions we introduce, it is not recommended, and something like this that has never worked (as far as I can tell) does not seem like something we would prioritize for a fix. That said, the code is open source, and if you want to work on fixing it, I am happy to help review your changes. I would start with creating a reproduction test in workflow-durable-task-step step along the lines of the following to demonstrate the issue:
@Issue("JENKINS-53750")
@Test public void cleanupBeforeStepCompletes() throws Exception {
Assume.assumeTrue("Test is Windows-specific", Functions.isWindows());
WorkflowJob p = j.jenkins.createProject(WorkflowJob.class, "p");
p.setDefinition(new CpsFlowDefinition("node {\n" +
" dir('foo/bar') {\n" +
"sh 'sleep 1'\n" +
" }\n" +
" bat 'rename foo baz'\n" +
"}", true));
j.assertBuildStatusSuccess(p.scheduleBuild2(0));
}
Once you have that test failing in the way you intend, you could make changes to BourneShellScript/FileMonitoringTask in durable-task to see how they affect the test. I don't have an environment to be able to reproduce the issue myself, but maybe something like switching these two lines so the workspace is cleaned up before the script exits would help?
Add Comment
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Jesse Glick commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body get the thread dump from the hung tests which are running a separate process launched by gradle If that is all you wanted, you may be barking up the wrong tree. The JUnit Timeout rule, for example, applies a per-test-case timeout (which is likely to be more robust and easier to manage that a per-build timeout) and automatically displays a thread dump for hung tests. 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body Thanks, I did see that, but a "kill -3" on the main gradle process isn't going to help me - I need to get the thread dump from the hung tests which are running a separate process launched by gradle. My current approach is to run "jstack" on every java process on the slave (we have a single executor policy) I also just tried setting JENKINS_SERVER_COOKIE on the child process and that doesn't help with killing subprocesses, but I haven't had time to research further. /usr/bin/timeout does work in combination with my trap script. 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-52826) Clicking Configure on a worker created by GCE Plugin results in an error
Title: Message Title Rachel Yen closed an issue as Fixed Added a view only form. Jenkins / JENKINS-52826 Clicking Configure on a worker created by GCE Plugin results in an error Change By: Rachel Yen Status: Open Closed Resolution: Fixed Released As: https://github.com/jenkinsci/google-compute-engine-plugin/releases/tag/google-compute-engine-1.0.5 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-53950) Support configuration as code
Title: Message Title Naineel Shah created an issue Jenkins / JENKINS-53950 Support configuration as code Issue Type: Improvement Assignee: Unassigned Components: influxdb-plugin Created: 2018-10-08 19:53 Priority: Minor Reporter: Naineel Shah Enable support for configuration as code (https://github.com/jenkinsci/configuration-as-code-plugin) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Jesse Glick commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body And no you do not need a separate pipeline-timeout-prekill.sh if you are using /usr/bin/timeout. Look at my example again. That one-liner sends SIGQUIT after ten seconds, then waits one more second for the thread dump to appear, and sends a SIGTERM. 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Jesse Glick commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body As I said before, yes Jenkins might be sending SIGTERM to the whole process tree, not only the entry script. This might be worked around (untested) via JENKINS_SERVER_COOKIE=suppress java -jar … since it uses this environment variable to identify some processes. I have forgotten the details at this point. (JENKINS-28182) The “good solutions” are Java shutdown hooks using /usr/bin/timeout 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body Interestingly, when I use the linux "timeout" that you mention instead of the timeout step, traps work fine... So the linux solution is a combination of the shell script and timeout: timeout 10 bash pipeline-timeout-prekill.sh './gradlew ' Which is a lot of parts... but OK - now I'll just need to find an equivalent for windows (we do cross-platform testing on many platforms, that's why I wanted to solve this in pipeline 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-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Javier Delgado commented on JENKINS-47643 Re: Allow [ci skip] to work for non-pull request changes Kevin Burnett, marbon and David Sanftenberg, could you test the opened pull request artifacts? Both hpi files found at https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fscm-trait-commit-skip-plugin/detail/feature%2FskippingBranches/1/artifacts (github and bitbucket) implement filtering branches on both [skip-ci] and [ci-skip] committed messages 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body Jesse Glick at your suggestion I switched from using pipeline tricks to the bash script (which I tested only locally): https://github.com/akomakom/jenkins-scripts/blob/master/pipeline-timeout-prekill/pipeline-timeout-prekill.sh It does not work in Jenkins. It works fine in local testing (pkill --signal SIGTERM or Ctrl-C) but not in a Jenkins timeout step - the trap never runs, termination is instant. This leads me to believe that Jenkins actually sends a SIGTERM to the whole process tree right away. In other words, there is still no good solution aside for pipeline tricks. 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-53949) Unable to see jobs in my new Jenkins ver. 2.138.1
Title: Message Title Suresh Garg created an issue Jenkins / JENKINS-53949 Unable to see jobs in my new Jenkins ver. 2.138.1 Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2018-10-08 19:25 Environment: Windows Priority: Minor Reporter: Suresh Garg I installed Jenkins version 2.138.1. I copied over the jobs folder from another server. I started Jenkins and I am unable to see the jobs in the dashboard. This is the error I am seeing: I have made sure that, I can, Access the config.xml in each of the job folders The plugins are all installed. Failed Loading item sce-installer-util.trunk com.thoughtworks.xstream.mapper.CannotResolveClassException: maven2-moduleset at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
[JIRA] (JENKINS-53947) Evergreen instance fails to start with "sh: tsc: not found" error
Title: Message Title Baptiste Mathus commented on JENKINS-53947 Re: Evergreen instance fails to start with "sh: tsc: not found" error Confirmed to be fixed by running from the fresh latest built public image. Thanks Tyler ! 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-53424) script-security plugin breaks parameterized pipeline builds
Title: Message Title Devin Nusbaum updated JENKINS-53424 Jenkins / JENKINS-53424 script-security plugin breaks parameterized pipeline builds Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: script-security 1.46 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Jesse Glick commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body Bourne shell scripts will indeed not be available in most Windows flavors, but I assume an analogous feature is easy to write in Powershell. Or, again, depending on the Java program in question, you can intercept SIGTERM in a cross-platform manner using Java APIs. In fact, at least on Linux, you can dispense with the timeout step altogether! sh 'timeout 11 timeout -sQUIT 10 java -jar …/jdk5/demo/jfc/SwingSet2/SwingSet2.jar' As to why you should always prefer native solutions to Pipeline script tricks, this is a subject for innumerable conference talks. Just trust me that you are better off keeping the Pipeline script to the bare minimum necessary to orchestrate actions on the Jenkins service, boiling your actual build down to a sh './run' if at all possible. 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-53948) HTTP Proxy Configuration
Title: Message Title Mohammed Salam created an issue Jenkins / JENKINS-53948 HTTP Proxy Configuration Issue Type: Bug Assignee: Mohammed Salam Components: ldap-plugin Created: 2018-10-08 17:39 Environment: windows 10 Priority: Major Reporter: Mohammed Salam Error 400 Add Comment This
[JIRA] (JENKINS-53947) Evergreen instance fails to start with "sh: tsc: not found" error
Title: Message Title R. Tyler Croy updated JENKINS-53947 Jenkins / JENKINS-53947 Evergreen instance fails to start with "sh: tsc: not found" error Change By: R. Tyler Croy 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-38609) Shared libraries root to be specified in the PATH field
Title: Message Title Dana Goyette commented on JENKINS-38609 Re: Shared libraries root to be specified in the PATH field Another reason the /vars location is bad: it breaks IDE classpaths. I can't just set / as the source root if I also want stuff under /src to be counted as the classpath, so it's forced me to add a symlink: src/vars -> ../vars. I'd much rather have the pipeline stuff follow standard maven project conventions (such as src/main/). With the bug marked "won't do", I can't even select "vote for 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body Why, specifically? Is the DSL behavior expected to change? They all have downsides over the built-in that this ticket originally requests: bash script won't work in Windows. groovy script fixes that, but both make quoting for a complex sub-process invocation very hard to understand (eg 'bash -c "sleep 5"') because they have to accept the commands as parameters. pipeline tricks don't have either limitation, but they do add unnecessary verbosity to the output. 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-53944) Findbugs pulls in a very old Xerces library version
Title: Message Title Alex Taylor commented on JENKINS-53944 Re: Findbugs pulls in a very old Xerces library version https://github.com/jenkinsci/findbugs-plugin/pull/16 to update 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-53906) Jenkins fails to start with Exception after update to 2.144
Title: Message Title Jesse Glick updated JENKINS-53906 Jenkins / JENKINS-53906 Jenkins fails to start with Exception after update to 2.144 Change By: Jesse Glick Status: Fixed but Unreleased Reopened 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-53906) Jenkins fails to start with Exception after update to 2.144
Title: Message Title Jesse Glick resolved as Not A Defect Not sure what exactly happened here. Jenkins / JENKINS-53906 Jenkins fails to start with Exception after update to 2.144 Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov edited a comment on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body I'll try to make the link in my previous comment more visible. I have 4 solutions now, with this one being the one I'm using:[https://github.com/akomakom/jenkins-scripts/blob/master/pipeline-timeout-prekill/pipeline-timeout-prekill-pure-dsl-failfast.groovy] The only thing I would wish to change would be to silence or reduce the *waitUntil* output... 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Jesse Glick commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body To be clear, I strongly recommend solving this at the native process level rather than with Pipeline tricks. 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov edited a comment on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body h3. Summary of findings:I was able to work around this using [a few different methods|https://github.com/akomakom/jenkins-scripts/tree/master/pipeline-timeout-prekill]: <-- Link * A *shell script* that traps and cleans up before kill (not cross-platform) * A *groovy script* that traps and cleans up before kill * A pure pipeline *DSL script* that uses parallel closure to do the same without an external script (at the cost of uglier output) 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body I'll try to make the link in my previous comment more visible. I have 4 solutions now, with this one being the one I'm using: https://github.com/akomakom/jenkins-scripts/blob/master/pipeline-timeout-prekill/pipeline-timeout-prekill-pure-dsl-failfast.groovy 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-53906) Jenkins fails to start with Exception after update to 2.144
Title: Message Title Frank Shimizu edited a comment on JENKINS-53906 Re: Jenkins fails to start with Exception after update to 2.144 Fixed by downgrading to a non-corrupt gradle plugin version with matching checksums . 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-53947) Evergreen instance fails to start with "sh: tsc: not found" error
Title: Message Title R. Tyler Croy updated JENKINS-53947 Jenkins / JENKINS-53947 Evergreen instance fails to start with "sh: tsc: not found" error Change By: R. Tyler Croy 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Jesse Glick commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body So if I follow correctly, Jenkins was behaving correctly to the extent that its behavior followed what Ctrl-C in a shell would do (send SIGTERM to subprocesses), and you were able to write a Bourne shell script with a little difficulty that intercepted this signal as sent to the subprocess and did something else before running a clean shutdown? If so, would you mind posting your script (or, better, filing it on stackoverflow.com)? I should have mentioned earlier that Java itself has a friendlier solution to this problem: shutdown hooks. A hook could do whatever you liked, including getting all stack traces or dumping threads including more sophisticated information such as locks. With such a hook inserted into your program (if you indeed control it, or can write in-process plugins for it), there is no need for any special wrapper script. 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-53858) Deadlock on EC2 resources
Title: Message Title Mason Donahue commented on JENKINS-53858 Re: Deadlock on EC2 resources We are currently using one cloud, but multiple configurations within that (same AMI, but machine types and labels differ). 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-53947) Evergreen instance fails to start with "sh: tsc: not found" error
Title: Message Title R. Tyler Croy started work on JENKINS-53947 Change By: R. Tyler Croy 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title
Francisco A. R. Vivas edited a comment on JENKINS-28877
Re: Bitbucket Plugin unable to parse Bitbucket webhook response json
[~kcuser], I have the same problem with "Approved" pull request event option.As far as I can see here is where Jenkins Bitbucket Plugin fails:[https://github.com/jenkinsci/bitbucket-plugin/blob/ce068b7f2cbf5250aa6d54c3acdd455d45b56246/src/main/java/com/cloudbees/jenkins/plugins/BitbucketPayloadProcessor.java#L24]I have captured the request and repeated here as a curl:{code}curl -X POST \ http://URL/bitbucket-hook/ \ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/json; charset=utf-8' \ -H 'Postman-Token: 3d72a314-48e1-45ff-832a-950d43a7435d' \ -H 'X-Event-Key: pr:reviewer:approved' \ -H 'X-Request-Id: 0d6f5c89-f29b-4c8a-9fc4-a6fd1846bafb' \ -d '{"eventKey":"pr:reviewer:approved","date":"2018-10-08T14:29:51+0200","actor":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"pullRequest":{"id":2,"version":5,"title":"test edited online with Bitbucket","description":"abaöldflj","state":"OPEN","open":true,"closed":false,"createdDate":1538055333000,"updatedDate":153809000,"fromRef":{"id":"refs/heads/feature/checkitagain","displayId":"feature/checkitagain","latestCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","repository":{"slug":"bitbucket-test","id":1960,"name":"bitbucket-test","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"DVSPRT","id":346,"name":"Development Support","description":" Everything related to development support, build system, development infrastructure. See https://confluence.tomtomgroup.com/x/bpB_K and https://tttjira.ttg.global:8441/browse/DVSPRT ","public":false,"type":"NORMAL"},"public":false}},"toRef":{"id":"refs/heads/master","displayId":"master","latestCommit":"ad359c8a9ba1eaf0bd2adec3aa37492c63966afb","repository":{"slug":"bitbucket-test","id":1960,"name":"bitbucket-test","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"DVSPRT","id":346,"name":"Development Support","description":" Everything related to development support, build system, development infrastructure. See https://confluence.tomtomgroup.com/x/bpB_K and https://tttjira.ttg.global:8441/browse/DVSPRT ","public":false,"type":"NORMAL"},"public":false}},"locked":false,"author":{"user":{"name":"otherUserReplaced","emailAddress":"otherUserReplaced","id":11708,"displayName":"otherUserReplaced","active":true,"slug":"otherUserReplaced","type":"NORMAL"},"role":"AUTHOR","approved":false,"status":"UNAPPROVED"},"reviewers":[{"user":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"lastReviewedCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","role":"REVIEWER","approved":true,"status":"APPROVED"}],"participants":[]},"participant":{"user":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"lastReviewedCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","role":"REVIEWER","approved":true,"status":"APPROVED"},"previousStatus":"UNAPPROVED"}'{code}And has the same response that Bitbucket receive:{code:java}net.sf.json.JSONException: JSONObject["user"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPostServicePayload(BitbucketPayloadProcessor.java:128) at
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title
Francisco A. R. Vivas updated an issue
Jenkins / JENKINS-53946
Bitbucket plugin unable to parse a Pull Request JSON Object
Change By:
Francisco A. R. Vivas
I have created this issue after reading JENKINS-28877 and JENKINS-29096. Please, pay attention to the JSON provided as body for the CURL request to test its way of works. I have configured a Webhook in Bitbucket Server 13.1 to be triggered by Approved event. I have received a HTTP 500 error, and get the same response with the next CURL code. Here is the error from Bitbucket UI:{code:java}net.sf.json.JSONException: JSONObject["user"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPostServicePayload(BitbucketPayloadProcessor.java:128) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPayload(BitbucketPayloadProcessor.java:37) at com.cloudbees.jenkins.plugins.BitbucketHookReceiver.doIndex(BitbucketHookReceiver.java:54) 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.IndexDispatcher.dispatch(IndexDispatcher.java:26) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) 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:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:239) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:215) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at
[JIRA] (JENKINS-53947) Evergreen instance fails to start with "sh: tsc: not found" error
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53947
Evergreen instance fails to start with "sh: tsc: not found" error
Change By:
Baptiste Mathus
h3. Problem statementFollowing the official documentation, and running{noformat}docker volume create jenkins-evergreen-data && \docker pull jenkins/evergreen:docker-cloud && \docker run --name evergreen \--restart=always \-ti \-p 8080:80 \-v /var/run/docker.sock:/var/run/docker.sock \-v jenkins-evergreen-data:/evergreen/data \-e LOG_LEVEL=debug \jenkins/evergreen:docker-cloud{noformat}The client fails with to start with the following error : {noformat}> evergreen-client@1.0.0 prestart /evergreen/client> tscsh: tsc: not foundnpm ERR! file shnpm ERR! code ELIFECYCLEnpm ERR! errno ENOENTnpm ERR! syscall spawnnpm ERR! evergreen-client@1.0.0 prestart: `tsc`npm ERR! spawn ENOENTnpm ERR! npm ERR! Failed at the evergreen-client@1.0.0 prestart script.npm ERR! This is probably not a problem with npm. There is likely additional logging output above.{noformat}h3. Expected behaviorThe Evergreen instance should be able to come with a ready to use Jenkins.It seems like there recent js->typescript migration is responsible for this. But then we want to understand why our CI did let that go green :-\.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title
Francisco A. R. Vivas updated an issue
Jenkins / JENKINS-53946
Bitbucket plugin unable to parse a Pull Request JSON Object
Change By:
Francisco A. R. Vivas
I have created this issue after reading JENKINS-28877 and JENKINS-29096. Please, pay attention to the JSON provided as body for the CURL request to test its way of works. I have configured a Webhook in Bitbucket Server 13.1 to be triggered by Approved event. I have received a HTTP 500 error, and get the same response with the next CURL code. Here is the error from Bitbucket UI:{code:java}net.sf.json.JSONException: JSONObject["user"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPostServicePayload(BitbucketPayloadProcessor.java:128) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPayload(BitbucketPayloadProcessor.java:37) at com.cloudbees.jenkins.plugins.BitbucketHookReceiver.doIndex(BitbucketHookReceiver.java:54) 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.IndexDispatcher.dispatch(IndexDispatcher.java:26) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) 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:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:239) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:215) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at
[JIRA] (JENKINS-53947) Evergreen instance fails to start with "sh: tsc: not found" error
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53947
Evergreen instance fails to start with "sh: tsc: not found" error
Change By:
Baptiste Mathus
h3. Problem statementFollowing the official documentation, and running{noformat}docker volume create jenkins-evergreen-data && \docker pull jenkins/evergreen:docker-cloud && \docker run --name evergreen \--restart=always \-ti \-p 8080:80 \-v /var/run/docker.sock:/var/run/docker.sock \-v jenkins-evergreen-data:/evergreen/data \-e LOG_LEVEL=debug \jenkins/evergreen:docker-cloud{noformat}The client fails with to start with the following error :
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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title
Francisco A. R. Vivas edited a comment on JENKINS-28877
Re: Bitbucket Plugin unable to parse Bitbucket webhook response json
[~kcuser], I have the same problem with "Approved" pull request event option.As far as I can see here is where Jenkins Bitbucket Plugin fails:[https://github.com/jenkinsci/bitbucket-plugin/blob/ce068b7f2cbf5250aa6d54c3acdd455d45b56246/src/main/java/com/cloudbees/jenkins/plugins/BitbucketPayloadProcessor.java#L24]I have captured the request and repeated here as a curl:{code}curl -X POST \ http:// ttbsbld102.dev.ttw:8080 URL /bitbucket-hook/ \ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/json; charset=utf-8' \ -H 'Postman-Token: 3d72a314-48e1-45ff-832a-950d43a7435d' \ -H 'X-Event-Key: pr:reviewer:approved' \ -H 'X-Request-Id: 0d6f5c89-f29b-4c8a-9fc4-a6fd1846bafb' \ -d '{"eventKey":"pr:reviewer:approved","date":"2018-10-08T14:29:51+0200","actor":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"pullRequest":{"id":2,"version":5,"title":"test edited online with Bitbucket","description":"abaöldflj","state":"OPEN","open":true,"closed":false,"createdDate":1538055333000,"updatedDate":153809000,"fromRef":{"id":"refs/heads/feature/checkitagain","displayId":"feature/checkitagain","latestCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","repository":{"slug":"bitbucket-test","id":1960,"name":"bitbucket-test","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"DVSPRT","id":346,"name":"Development Support","description":"Everything related to development support, build system, development infrastructure. See https://confluence.tomtomgroup.com/x/bpB_K and https://tttjira.ttg.global:8441/browse/DVSPRT","public":false,"type":"NORMAL"},"public":false}},"toRef":{"id":"refs/heads/master","displayId":"master","latestCommit":"ad359c8a9ba1eaf0bd2adec3aa37492c63966afb","repository":{"slug":"bitbucket-test","id":1960,"name":"bitbucket-test","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"DVSPRT","id":346,"name":"Development Support","description":"Everything related to development support, build system, development infrastructure. See https://confluence.tomtomgroup.com/x/bpB_K and https://tttjira.ttg.global:8441/browse/DVSPRT","public":false,"type":"NORMAL"},"public":false}},"locked":false,"author":{"user":{"name":"otherUserReplaced","emailAddress":"otherUserReplaced","id":11708,"displayName":"otherUserReplaced","active":true,"slug":"otherUserReplaced","type":"NORMAL"},"role":"AUTHOR","approved":false,"status":"UNAPPROVED"},"reviewers":[{"user":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"lastReviewedCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","role":"REVIEWER","approved":true,"status":"APPROVED"}],"participants":[]},"participant":{"user":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"lastReviewedCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","role":"REVIEWER","approved":true,"status":"APPROVED"},"previousStatus":"UNAPPROVED"}'{code}And has the same response that Bitbucket receive:{code:java}net.sf.json.JSONException: JSONObject["user"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPostServicePayload(BitbucketPayloadProcessor.java:128) at
[JIRA] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title
Francisco A. R. Vivas edited a comment on JENKINS-28877
Re: Bitbucket Plugin unable to parse Bitbucket webhook response json
[~kcuser], I have the same problem with "Approved" pull request event option.As far as I can see here is where Jenkins Bitbucket Plugin fails:[https://github.com/jenkinsci/bitbucket-plugin/blob/ce068b7f2cbf5250aa6d54c3acdd455d45b56246/src/main/java/com/cloudbees/jenkins/plugins/BitbucketPayloadProcessor.java#L24]I have captured the request and repeated here as a curl:{code}curl -X POST \ http://ttbsbld102.dev.ttw:8080/bitbucket-hook/ \ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/json; charset=utf-8' \ -H 'Postman-Token: 3d72a314-48e1-45ff-832a-950d43a7435d' \ -H 'X-Event-Key: pr:reviewer:approved' \ -H 'X-Request-Id: 0d6f5c89-f29b-4c8a-9fc4-a6fd1846bafb' \ -d '{"eventKey":"pr:reviewer:approved","date":"2018-10-08T14:29:51+0200","actor":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"pullRequest":{"id":2,"version":5,"title":"test edited online with Bitbucket","description":"abaöldflj","state":"OPEN","open":true,"closed":false,"createdDate":1538055333000,"updatedDate":153809000,"fromRef":{"id":"refs/heads/feature/checkitagain","displayId":"feature/checkitagain","latestCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","repository":{"slug":"bitbucket-test","id":1960,"name":"bitbucket-test","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"DVSPRT","id":346,"name":"Development Support","description":"Everything related to development support, build system, development infrastructure. See https://confluence.tomtomgroup.com/x/bpB_K and https://tttjira.ttg.global:8441/browse/DVSPRT","public":false,"type":"NORMAL"},"public":false}},"toRef":{"id":"refs/heads/master","displayId":"master","latestCommit":"ad359c8a9ba1eaf0bd2adec3aa37492c63966afb","repository":{"slug":"bitbucket-test","id":1960,"name":"bitbucket-test","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"DVSPRT","id":346,"name":"Development Support","description":"Everything related to development support, build system, development infrastructure. See https://confluence.tomtomgroup.com/x/bpB_K and https://tttjira.ttg.global:8441/browse/DVSPRT","public":false,"type":"NORMAL"},"public":false}},"locked":false,"author":{"user":{"name":"otherUserReplaced","emailAddress":"otherUserReplaced","id":11708,"displayName":"otherUserReplaced","active":true,"slug":"otherUserReplaced","type":"NORMAL"},"role":"AUTHOR","approved":false,"status":"UNAPPROVED"},"reviewers":[{"user":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"lastReviewedCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","role":"REVIEWER","approved":true,"status":"APPROVED"}],"participants":[]},"participant":{"user":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"lastReviewedCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","role":"REVIEWER","approved":true,"status":"APPROVED"},"previousStatus":"UNAPPROVED"}'{code}And has the same response that Bitbucket receive:{code:java}net.sf.json.JSONException: JSONObject["user"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPostServicePayload(BitbucketPayloadProcessor.java:128) at
[JIRA] (JENKINS-53947) Evergreen instance fails to start with "sh: tsc: not found" error
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53947 Evergreen instance fails to start with "sh: tsc: not found" error Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-08 15:25 Priority: Blocker 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-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Francisco A. R. Vivas created an issue Jenkins / JENKINS-53946 Bitbucket plugin unable to parse a Pull Request JSON Object Issue Type: Bug Assignee: Unassigned Components: bitbucket-plugin Created: 2018-10-08 15:24 Priority: Minor Reporter: Francisco A. R. Vivas I have created this issue after reading JENKINS-28877 and JENKINS-29096. Please, pay attention to the JSON provided as body for the CURL request to test its way of works. I have configured a Webhook in Bitbucket Server 13.1 to be triggered by Approved event. I have received a HTTP 500 error, and get the same response with the next CURL code. Here is the error from Bitbucket UI: net.sf.json.JSONException: JSONObject["user"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPostServicePayload(BitbucketPayloadProcessor.java:128) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPayload(BitbucketPayloadProcessor.java:37) at com.cloudbees.jenkins.plugins.BitbucketHookReceiver.doIndex(BitbucketHookReceiver.java:54) 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.IndexDispatcher.dispatch(IndexDispatcher.java:26) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at
[JIRA] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title
Francisco A. R. Vivas commented on JENKINS-28877
Re: Bitbucket Plugin unable to parse Bitbucket webhook response json
K C, I have the same problem with "Approved" pull request event option. As far as I can see here is where Jenkins Bitbucket Plugin fails: https://github.com/jenkinsci/bitbucket-plugin/blob/ce068b7f2cbf5250aa6d54c3acdd455d45b56246/src/main/java/com/cloudbees/jenkins/plugins/BitbucketPayloadProcessor.java#L24 I have captured the request and repeated here as a curl:
curl -X POST \
http://ttbsbld102.dev.ttw:8080/bitbucket-hook/ \
-H 'Cache-Control: no-cache' \
-H 'Content-Type: application/json; charset=utf-8' \
-H 'Postman-Token: 3d72a314-48e1-45ff-832a-950d43a7435d' \
-H 'X-Event-Key: pr:reviewer:approved' \
-H 'X-Request-Id: 0d6f5c89-f29b-4c8a-9fc4-a6fd1846bafb' \
-d '{"eventKey":"pr:reviewer:approved","date":"2018-10-08T14:29:51+0200","actor":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"pullRequest":{"id":2,"version":5,"title":"test edited online with Bitbucket","description":"abaöldflj","state":"OPEN","open":true,"closed":false,"createdDate":1538055333000,"updatedDate":153809000,"fromRef":{"id":"refs/heads/feature/checkitagain","displayId":"feature/checkitagain","latestCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","repository":{"slug":"bitbucket-test","id":1960,"name":"bitbucket-test","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"DVSPRT","id":346,"name":"Development Support","description":"Everything related to development support, build system, development infrastructure. See https://confluence.tomtomgroup.com/x/bpB_K and https://tttjira.ttg.global:8441/browse/DVSPRT","public":false,"type":"NORMAL"},"public":false}},"toRef":{"id":"refs/heads/master","displayId":"master","latestCommit":"ad359c8a9ba1eaf0bd2adec3aa37492c63966afb","repository":{"slug":"bitbucket-test","id":1960,"name":"bitbucket-test","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"DVSPRT","id":346,"name":"Development Support","description":"Everything related to development support, build system, development infrastructure. See https://confluence.tomtomgroup.com/x/bpB_K and https://tttjira.ttg.global:8441/browse/DVSPRT","public":false,"type":"NORMAL"},"public":false}},"locked":false,"author":{"user":{"name":"otherUserReplaced","emailAddress":"otherUserReplaced","id":11708,"displayName":"otherUserReplaced","active":true,"slug":"otherUserReplaced","type":"NORMAL"},"role":"AUTHOR","approved":false,"status":"UNAPPROVED"},"reviewers":[{"user":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"lastReviewedCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","role":"REVIEWER","approved":true,"status":"APPROVED"}],"participants":[]},"participant":{"user":{"name":"authorUserReplaced","emailAddress":"authorReplaced","id":13761,"displayName":"authorReplaced","active":true,"slug":"authorUserReplaced","type":"NORMAL"},"lastReviewedCommit":"d5b55683288bc89c23609f3087a02b6daf7eef06","role":"REVIEWER","approved":true,"status":"APPROVED"},"previousStatus":"UNAPPROVED"}'
And has the same response
[JIRA] (JENKINS-35708) EC2 Plugin: Ability to round robin EC2 availability zones
Title: Message Title David Fluck commented on JENKINS-35708 Re: EC2 Plugin: Ability to round robin EC2 availability zones Mikael Gaunin Sorry for the wait! I did, yeah. I should be able to rebase that shortly. Thank you! 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-35708) EC2 Plugin: Ability to round robin EC2 availability zones
Title: Message Title Mikael Gaunin commented on JENKINS-35708 Re: EC2 Plugin: Ability to round robin EC2 availability zones Hi David Fluck, we have a good chance to see your PR #295 reviewed soon since new maintainers work actively on this plugin! \o/ Did you see Matt Sicker 's comment on your PR? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34354) Custom Slack Notification is dropped when there is a combined Slack notification
Title: Message Title Kurt Madel resolved as Fixed Jenkins / JENKINS-34354 Custom Slack Notification is dropped when there is a combined Slack notification Change By: Kurt Madel Status: Open Resolved Resolution: Fixed Released As: 2.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53606) SafeRestart Exception
Title: Message Title
Scott Lavender updated an issue
Jenkins / JENKINS-53606
SafeRestart Exception
Change By:
Scott Lavender
Comment:
I am getting a similar error when my Jenkins Chef cookbook attempts a safe-restart after adding plugins, etc. This works with the same cookbook code using Jenkins 2.121.3.{code:java} Recipe: efx_jenkins::master * jenkins_command[safe-restart] action execute Error executing action `execute` on resource 'jenkins_command[safe-restart]' Mixlib::ShellOut::ShellCommandFailed Expected process to exit with [0], but received '255' Begin output of "java" -jar "/tmp/kitchen/cache/jenkins-cli.jar" -s http://10.23.23.98:8080/gcs-kitchen-jenkins/ -"remoting" -i "/tmp/kitchen/cache/jenkins-key" safe-restart STDOUT: STDERR: Oct 08, 2018 1:53:13 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Chunked connection to http://10.23.23.98:8080/gcs-kitchen-jenkins/ java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) Caused by: java.io.EOFExceptionat java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155)at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861)at java.io.ObjectInputStream.(ObjectInputStream.java:357)at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)at hudson.remoting.Command.readFrom(Command.java:140)at hudson.remoting.Command.readFrom(Command.java:126)at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@4f8e5cde:Chunked connection to http://10.23.23.98:8080/gcs-kitchen-jenkins/": channel is already closedat hudson.remoting.Channel.send(Channel.java:717)at hudson.remoting.ProxyOutputStream.doClose(ProxyOutputStream.java:174)at hudson.remoting.ProxyOutputStream.error(ProxyOutputStream.java:169)at hudson.remoting.ProxyOutputStream.close(ProxyOutputStream.java:160)at hudson.cli.Connection.close(Connection.java:269)at hudson.cli.CLI.authenticate(CLI.java:800)at hudson.cli.CLI._main(CLI.java:620)at hudson.cli.CLI.main(CLI.java:426) Caused by: java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
[JIRA] (JENKINS-53606) SafeRestart Exception
Title: Message Title
Scott Lavender commented on JENKINS-53606
Re: SafeRestart Exception
I am getting a similar error when my Jenkins Chef cookbook attempts a safe-restart after adding plugins, etc. This works with the same cookbook code using Jenkins 2.121.3.
Recipe: efx_jenkins::master
* jenkins_command[safe-restart] action execute
Error executing action `execute` on resource 'jenkins_command[safe-restart]'
Mixlib::ShellOut::ShellCommandFailed
Expected process to exit with [0], but received '255'
Begin output of "java" -jar "/tmp/kitchen/cache/jenkins-cli.jar" -s http://10.23.23.98:8080/gcs-kitchen-jenkins/ -"remoting" -i "/tmp/kitchen/cache/jenkins-key" safe-restart
STDOUT:
STDERR: Oct 08, 2018 1:53:13 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run
SEVERE: I/O error in channel Chunked connection to http://10.23.23.98:8080/gcs-kitchen-jenkins/
java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861)
at java.io.ObjectInputStream.(ObjectInputStream.java:357)
at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)
at hudson.remoting.Command.readFrom(Command.java:140)
at hudson.remoting.Command.readFrom(Command.java:126)
at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@4f8e5cde:Chunked connection to http://10.23.23.98:8080/gcs-kitchen-jenkins/": channel is already closed
at hudson.remoting.Channel.send(Channel.java:717)
at hudson.remoting.ProxyOutputStream.doClose(ProxyOutputStream.java:174)
at hudson.remoting.ProxyOutputStream.error(ProxyOutputStream.java:169)
at hudson.remoting.ProxyOutputStream.close(ProxyOutputStream.java:160)
at hudson.cli.Connection.close(Connection.java:269)
at hudson.cli.CLI.authenticate(CLI.java:800)
at hudson.cli.CLI._main(CLI.java:620)
at hudson.cli.CLI.main(CLI.java:426)
Caused by: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155)
at
[JIRA] (JENKINS-53606) SafeRestart Exception
Title: Message Title
Scott Lavender commented on JENKINS-53606
Re: SafeRestart Exception
I get a similar exception when my Jenkins Chef cookbook attempts a safe-restart after configuring the newly created master instance. The only difference being that i'm using the remoting option. This same cookbook works with version 2.121.3
Recipe: efx_jenkins::master
* jenkins_command[safe-restart] action execute
Error executing action `execute` on resource 'jenkins_command[safe-restart]'
Mixlib::ShellOut::ShellCommandFailed
Expected process to exit with [0], but received '255'
Begin output of "java" -jar "/tmp/kitchen/cache/jenkins-cli.jar" -s http://10.23.23.98:8080/gcs-kitchen-jenkins/ -"remoting" -i "/tmp/kitchen/cache/jenkins-key" safe-restart
STDOUT:
STDERR: Oct 08, 2018 1:53:13 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run
SEVERE: I/O error in channel Chunked connection to http://10.23.23.98:8080/gcs-kitchen-jenkins/
java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861)
at java.io.ObjectInputStream.(ObjectInputStream.java:357)
at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)
at hudson.remoting.Command.readFrom(Command.java:140)
at hudson.remoting.Command.readFrom(Command.java:126)
at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@4f8e5cde:Chunked connection to http://10.23.23.98:8080/gcs-kitchen-jenkins/": channel is already closed
at hudson.remoting.Channel.send(Channel.java:717)
at hudson.remoting.ProxyOutputStream.doClose(ProxyOutputStream.java:174)
at hudson.remoting.ProxyOutputStream.error(ProxyOutputStream.java:169)
at hudson.remoting.ProxyOutputStream.close(ProxyOutputStream.java:160)
at hudson.cli.Connection.close(Connection.java:269)
at hudson.cli.CLI.authenticate(CLI.java:800)
at hudson.cli.CLI._main(CLI.java:620)
at hudson.cli.CLI.main(CLI.java:426)
Caused by: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)
at
[JIRA] (JENKINS-51577) Windows service wrapper for slave.jar can not connect to a SSL configured master
Title: Message Title Roman Donchenko commented on JENKINS-51577 Re: Windows service wrapper for slave.jar can not connect to a SSL configured master Note that it's possible to fix this without modifying WinSW itself. You can add: "Switch.System.Net.DontEnableSchUseStrongCrypto=false"/> to the section of jenkins-slave.exe.config. This will enable TLS 1.2 (and disable SSL 3.0) if WinSW is executed with .NET Framework 4.6 or later. 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-53945) Adding a new configuration to the azure-vm-agents-plugin to enable MSI
Title: Message Title Tom Ganor created an issue Jenkins / JENKINS-53945 Adding a new configuration to the azure-vm-agents-plugin to enable MSI Issue Type: New Feature Assignee: Azure DevOps Attachments: MSI_config.png Components: azure-vm-agents-plugin Created: 2018-10-08 13:38 Labels: plugin jenkins configuration slave Priority: Critical Reporter: Tom Ganor Adding a new configuration to the azure-vm-agents-plugin that can be modified when a VM is deployed. The new configuration should provide us the ability to enable MSI (in azure portal it is under "settings" -> "Identity (Preview)" -> "status") - a screenshot is attached. Add Comment
[JIRA] (JENKINS-53499) Improve tests to avoid race condition for updates during startup
Title: Message Title Baptiste Mathus updated JENKINS-53499 Jenkins / JENKINS-53499 Improve tests to avoid race condition for updates during startup Change By: Baptiste Mathus Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov edited a comment on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body h3. Summary of findings:I was able to work around this using [a few different methods|https://github.com/akomakom/jenkins-scripts/tree/master/pipeline-timeout-prekill]: * A *shell script* that traps and cleans up before kill (not cross-platform) * A *groovy script* that traps and cleans up before kill * A pure pipeline *DSL script* that uses parallel closure to do the same without an external script (at the cost of uglier output) 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-53857) No option to disable build continuation when computer forcefully restarted
Title: Message Title Marley Kudiabor commented on JENKINS-53857 Re: No option to disable build continuation when computer forcefully restarted Appears to duplicate https://issues.jenkins-ci.org/browse/JENKINS-50892 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-53857) No option to disable build continuation when computer forcefully restarted
Title: Message Title Marley Kudiabor commented on JENKINS-53857 Re: No option to disable build continuation when computer forcefully restarted Oleg Nenashev We have multiple pipeline jobs and they all get stuck. What would you recommend? 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-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Michel Zanini edited a comment on JENKINS-53920 Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again When you mean permissions you mean AWS permissions?I don't think that could be the issue because when I downgrade to 1.39 it starts working.The permissions are the same with both versions, and one works the other not. 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-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Michel Zanini commented on JENKINS-53920 Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again When you mean permissions you mean AWS permissions? I don't think that could be the issue because when I downgrade to 1.39 it starts working. The permissions are the same with both versions, and works the other not. 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-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-53920 Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again I am not sure if it is your bug, but I found one ec2-plugin does not have enough permission to restart the stopped instance, the AWS call is failing without logs. I am looking for the permissions that is missing 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-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Michel Zanini commented on JENKINS-53920 Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again I have tried removing tags, iamInstanceProfile and some other things and still the bug reproduces. 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-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Michel Zanini commented on JENKINS-53920 Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again This is my EC2 plugin configuration: ami-0287cfa6afebea61f slave eu-west-1a sg-0669475f23a632a23 /var/lib/jenkins T3Medium true false ec2 java ansible EXCLUSIVE 2 developer subnet-0475d56ca5686569c 5 arn:aws:iam::213123213123:instance-profile/system-jenkins-master-role-policy true false 2 true Name system-dev-jenkins-slave : slave Environment system-dev AvailabilityZone a Profile private ServiceName system-jenkins-slave ServiceOwner System true true false "hudson.plugins.ec2.UnixData"> 999 2147483647 false false 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
[JIRA] (JENKINS-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title
Michel Zanini edited a comment on JENKINS-53920
Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Q. Do you have a custom tags ? - A. Yes I have a few, but I have tried with no declared tags and also is not working Q. Do you have a description for the in the configuration for the pool ? - A. Yes, its just "slave". Q. Are you using Default or VPC configuration in Ec2? - A. I am using a VPC that is not default (also, on my EC2 plugin config I am asking the slave to be created on a security group that is not the default) Q. Are the data of the filter correct for the Filter search ? - A. This is what I have on logs:{code:}{Filters: [{Name:image-id,Values: [ami-0287cfa6afebea61f]}, {Name: instance-type,Values:[t3.medium]}, {Name: key-name,Values: [developer]}, {Name:availability-zone,Values: [eu-west-1a]}, {Name: subnet-id,Values:[subnet-0475d56ca5686569c]}, {Name: instance.group-id,Values:[sg-0669475f23a632a23]}, {Name: tag:Name,Values: [system-dev-jenkins-slave :slave]}, {Name: tag:AvailabilityZone,Values: [a]}, {Name:tag:Environment,Values: [system-dev]}, {Name: tag:Profile,Values: [private]},{Name: tag:ServiceName,Values: [system-jenkins-slave]}, {Name:tag:ServiceOwner,Values: [System]}, {Name: tag:jenkins_slave_type,Values:[demand_slave]}],InstanceIds: [],} {code}All of the values above seems correct including the tags.I have tried removing all tags and trying without, but the result has being the same.You were not able to reproduce the issue?Thanks for looking into this.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title
Michel Zanini commented on JENKINS-53920
Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Do you have a custom tags ?
Yes I have a few, but I have tried with no declared tags and also is not working Do you have a description for the in the configuration for the pool ?
Yes, its just "slave". Are you using Default or VPC configuration in Ec2?
I am using a VPC that is not default (also, on my EC2 plugin config I am asking the slave to be created on a security group that is not the default) Are the data of the filter correct for the Filter search ?
This is what I have on logs:
{Filters: [{Name:
image-id,Values: [ami-0287cfa6afebea61f]}, {Name: instance-type,Values:
[t3.medium]}, {Name: key-name,Values: [developer]}, {Name:
availability-zone,Values: [eu-west-1a]}, {Name: subnet-id,Values:
[subnet-0475d56ca5686569c]}, {Name: instance.group-id,Values:
[sg-0669475f23a632a23]}, {Name: tag:Name,Values: [system-dev-jenkins-slave :
slave]}, {Name: tag:AvailabilityZone,Values: [a]}, {Name:
tag:Environment,Values: [system-dev]}, {Name: tag:Profile,Values: [private]},
{Name: tag:ServiceName,Values: [system-jenkins-slave]}, {Name:
tag:ServiceOwner,Values: [System]}, {Name: tag:jenkins_slave_type,Values:
[demand_slave]}],InstanceIds: [],}
All of the values above seems correct including the tags. I have tried removing all tags and trying without, but the result has being the same. You were not able to reproduce the issue? Thanks for looking into this.
Add Comment
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov edited a comment on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body It appears to be the way Bash works. The very first example [here|https://www.tldp.org/LDP/Bash-Beginners-Guide/html/sect_12_02.html] shows that although it is possible to trap the signal and prevent the bash shell from exiting, it is not possible to prevent the currently executing shell command (sleep in this case) from also receiving the signal, hence the while loop. I was able to create a groovy wrapper script using the approach [suggested here|https://stackoverflow.com/a/8851685/1735931] and that works correctly (both options in this answer work). UPDATE: the trick with bash is to [background the main process|https://unix.stackexchange.com/a/146770/199293]... 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov edited a comment on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body h3. Summary of findings:I was able to work around this using [a few different methods|https://github.com/akomakom/jenkins-scripts/tree/master/pipeline-timeout-prekill]: * A * shell script * that traps and cleans up before kill * A * groovy script * that traps and cleans up before kill * A pure pipeline * DSL block script* that uses parallel closure to do the same without an external script (at the cost of uglier output) 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov closed an issue as Won't Do Jenkins / JENKINS-53315 Timeout step should support a closure to execute prior to killing body Change By: Alexander Komarov Status: Open Closed Resolution: Won't Do 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-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body Summary of findings: I was able to work around this using a few different methods: A shell script that traps and cleans up before kill A groovy script that traps and cleans up before kill A pure pipeline DSL block that uses parallel closure to do the same without an external script (at the cost of uglier output) 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-53944) Findbugs pulls in a very old Xerces library version
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53944 Findbugs pulls in a very old Xerces library version Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 2018-10-08 12:17 Priority: Minor Reporter: Alex Taylor Looking at the pom I can see that the findbugs plugin pulls in 2.9.1 of the xerces library. Is it possible to step this up to a newer version? This caused an issue in the pipeline maven plugin which was difficult to track down. Add Comment
[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title Taras Postument commented on JENKINS-39464 Re: Pipeline with parallel and no stages does not get visualised correctly Vivek Pandey I'm facing the same problem. Any progress here? See my complete issue described here: JENKINS-39464 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-53933) set file permission on ssh key when on windows to enable OpenSSH client
Title: Message Title Mark Waite assigned an issue to Joseph Petersen Jenkins / JENKINS-53933 set file permission on ssh key when on windows to enable OpenSSH client Change By: Mark Waite Assignee: Mark Waite Joseph Petersen 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-53941) new feature
Title: Message Title Mark Waite updated JENKINS-53941 Insufficiently described. I assume this was being used as a demonstration by someone. Jenkins / JENKINS-53941 new feature Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53941) new feature
Title: Message Title Mark Waite updated JENKINS-53941 Jenkins / JENKINS-53941 new feature 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-53941) new feature
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-53941 new feature 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-48955) master-slave connection getting terminated once in every 12 hours and recovered after 1 minute
Title: Message Title Eugene Chepurniy commented on JENKINS-48955 Re: master-slave connection getting terminated once in every 12 hours and recovered after 1 minute Ivan Fernandez Calvo I'm going to give this solution a chance and provide a feedback here. Thanks for staying in touch. 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-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title
FABRIZIO MANFREDI edited a comment on JENKINS-53920
Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
It seems the filter for get the list of the nodes is not working properly, can you tell me the value of the tags in the amazon console of the stop instance and the running instances ? do you have a custom tags ? do you have a description for the in the configuration for the pool ? The description is used to build a unique tags for the search and it seems empty: the tag should be tag name:jenkins_slave_type value:demand_[description] Are you using Default or VPC configuration in Ec2? Are the data of the filter correct for the Filter search ? [ \ {Name: image-id,Values:[ami-123123213123]},{Name: instance-type,Values: [t3.medium]} ,{Name: key-name,Values: [developer]} ,{Name: availability-zone,Values: [eu-west-1a]} , \ {Name: subnet-id,Values: [subnet-1]},{Name: instance.group-id,Values: [sg-1]} ,{Name: tag:jenkins_slave_type,Values: [demand_Slave]} ],InstanceIds: [],}
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-53943) Parallel jobs run on the same node, though they have 2 other nodes to run on
Title: Message Title Xavi Albillos updated an issue Jenkins / JENKINS-53943 Parallel jobs run on the same node, though they have 2 other nodes to run on Change By: Xavi Albillos Attachment: Jenkinsfile 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-53943) Parallel jobs run on the same node, though they have 2 other nodes to run on
Title: Message Title Xavi Albillos created an issue Jenkins / JENKINS-53943 Parallel jobs run on the same node, though they have 2 other nodes to run on Issue Type: Bug Assignee: Unassigned Attachments: modchrome.png Components: core Created: 2018-10-08 11:10 Labels: schedule Priority: Critical Reporter: Xavi Albillos In my multi-branch pipeline, I set a parallel stage where one or two stages will be skipped. I do this because I can't nest parallel stages. The problem is, when this happens, I have 2 jobs running on one node, while the other 2 nodes are idle. This should not be happening and I have no way to control this, as they should be scheduled to balance load... All stages are marked with agent any. Add Comment
[JIRA] (JENKINS-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Elie Kassis edited a comment on JENKINS-53900
Re: Stage graph in Blue Ocean not showing all stages for large workflows
[~sophistifunk], you can check the attached pipeline code on which we are facing the issue.Noting that in the example you provided there the no sequential stages inside the parallel nodes.*{color:#0747a6}In addition your code that launch parallel stages is totally different then the one we are using . Can you please tell us how using your way to have sequential stages inside parallel nodes?{color}*
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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Elie Kassis commented on JENKINS-53900 Re: Stage graph in Blue Ocean not showing all stages for large workflows Josh McDonald, you can check the attached pipeline code on which we are facing the issue. Noting that in the example you provided there the no sequential stages inside the parallel one. 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53900 Stage graph in Blue Ocean not showing all stages for large workflows Change By: Elie Kassis Attachment: pipeline_example.groovy 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Elie Kassis updated an issue
Jenkins / JENKINS-53900
Stage graph in Blue Ocean not showing all stages for large workflows
Change By:
Elie Kassis
Stage graph in Blue Ocean not showing all stages for large workflows. As shown in below pipeline the last 2 parallel stages are missing in Blue Ocean noting that they were executed. you can find the code as per the attached. !image-2018-10-04-13-00-11-064.png|width=581,height=138! {code:java}pipeline { agent any stages { stage('Prepare Workflow') { steps {script { //get Reference println("Getting References")} } } stage('Generate Debug Job') { steps {script { println("Generate Debug Job")} } } stage('Pushing 2 Tests and 2 Debug jobs') { //failFast true parallel {stage('TE1') { stages { stage('PUSH TE1') { steps {script { println("PUSH TE1")} } } stage('Archive Logs') { steps {script { println("Archive TE1 Logs")} } } stage('Insert Metrics') { steps {script { println("Insert TE1 Metrics in DB")} } } stage('Compare Metrics') { steps {script { println("Compare Metrics TE1 vs REF")} } } }}stage('TE2') { stages { stage('PUSH TE2') { steps {script { println("PUSH TE2")} } } stage('Archive Logs') { steps {script { println("Archive TE2 Logs")} } } stage('Insert Metrics') { steps {script { println("Insert TE2 Metrics in DB")} } } stage('Compare Metrics') { steps {script { println("Compare Metrics TE2 vs REF")} } } }}stage('HEAD DEBUG') { stages { stage('PUSH HEAD DEBUG') { steps {script { println("PUSH HEAD DEBUG")} } } stage('DEPLOY CLIENT HEAD') { steps {script { println("Deploying Client HEAD")} } } }}stage('REF DEBUG') { stages { stage('PUSH REF DEBUG') { steps {script { println("PUSH REF DEBUG")} } } stage('DEPLOY CLIENT REF') { steps {script { println("Deploying Client REF")} } } }} } } stage('CrossChecking') { steps {script { println("CrossChecking")} } } stage('SetReferences') { steps {script { println("Set References")} } } stage('Head vs Head-1') { steps {script { println("Head vs Head-1")} } } stage('Send MAIL and Insert JIRA') { parallel {stage('Sending Mail') { stages { stage('Send MAIL') { steps {script { println("Sending Mail")} } } }}stage('Inserting Jira') { stages { stage('Insert JIRA') { steps {script { println
[JIRA] (JENKINS-53740) Introduce a way how to disable deferred Wipeout
Title: Message Title Pavel Janoušek updated JENKINS-53740 Merged upstream. Jenkins / JENKINS-53740 Introduce a way how to disable deferred Wipeout Change By: Pavel Janoušek Status: In Review Resolved Resolution: Done 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Elie Kassis updated an issue
Jenkins / JENKINS-53900
Stage graph in Blue Ocean not showing all stages for large workflows
Change By:
Elie Kassis
Stage graph in Blue Ocean not showing all stages for large workflows. As shown in below pipeline the last 2 parallel stages are missing in Blue Ocean noting that they were executed. !image-2018-10-04-13-00-11-064.png|width=581,height=138! {code:java}pipeline { agent any stages { stage('Prepare Workflow') { steps {script { //get Reference println("Getting References")} } } stage('Generate Debug Job') { steps {script { println("Generate Debug Job")} } } stage('Pushing 2 Tests and 2 Debug jobs') { //failFast true parallel { stage('TE1') { stages { stage('PUSH TE1') { steps {script { println("PUSH TE1")} } } stage('Archive Logs') { steps {script { println("Archive TE1 Logs")} } } stage('Insert Metrics') { steps {script { println("Insert TE1 Metrics in DB")} } } stage('Compare Metrics') { steps {script { println("Compare Metrics TE1 vs REF")} } } }}stage('TE2') { stages { stage('PUSH TE2') { steps {script { println("PUSH TE2")} } } stage('Archive Logs') { steps {script { println("Archive TE2 Logs")} } } stage('Insert Metrics') { steps {script { println("Insert TE2 Metrics in DB")} } } stage('Compare Metrics') { steps {script { println("Compare Metrics TE2 vs REF")} } } }}stage('HEAD DEBUG') { stages { stage('PUSH HEAD DEBUG') { steps {script { println("PUSH HEAD DEBUG")} } } stage('DEPLOY CLIENT HEAD') { steps {script { println("Deploying Client HEAD")} } } }}stage('REF DEBUG') { stages { stage('PUSH REF DEBUG') { steps {script { println("PUSH REF DEBUG")} } } stage('DEPLOY CLIENT REF') { steps {script { println("Deploying Client REF")} } } }} } } stage('CrossChecking') { steps {script { println("CrossChecking")} } } stage('SetReferences') { steps {script { println("Set References")} } } stage('Head vs Head-1') { steps {script { println("Head vs Head-1")} } } stage('Send MAIL and Insert JIRA') { parallel {stage('Sending Mail') { stages { stage('Send MAIL') { steps {script { println("Sending Mail")} } } }}stage('Inserting Jira') { stages { stage('Insert JIRA') { steps {script { println "Inserting
[JIRA] (JENKINS-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Elie Kassis updated an issue
Jenkins / JENKINS-53900
Stage graph in Blue Ocean not showing all stages for large workflows
Change By:
Elie Kassis
Stage graph in Blue Ocean not showing all stages for large workflows. As shown in below pipeline the last 2 parallel stages are missing in Blue Ocean noting that they were executed. !image-2018-10-04-13-00-11-064.png|width=581,height=138! {code:java}pipeline { options { timeout(time: 4, unit: 'HOURS') ansiColor('xterm') } // agent any agent { node { label 'pacpte_dell1114srv' } } stages { stage('Prepare Workflow') { steps {script { timestamps { //get Reference println("Getting References") }} } } stage('Generate Debug Job') { steps {script { timestamps { println("Generate Debug Job") }} } } stage('Pushing 2 Tests and 2 Debug jobs') { //failFast true parallel { stage('TE1') { stages { stage('PUSH TE1') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE1") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE1 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE1 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE1 vs REF") }} } } } } stage('TE2') { stages { stage('PUSH TE2') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE2") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE2 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE2 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE2 vs REF") }} } } } } stage('HEAD DEBUG') { stages { stage('PUSH HEAD DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') } steps {script { timestamps { println("PUSH HEAD DEBUG") }} } } stage('DEPLOY CLIENT HEAD') { steps {script { timestamps { println("Deploying Client HEAD") }} } } } } stage('REF DEBUG') { stages { stage('PUSH REF DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') }
[JIRA] (JENKINS-53942) Jobs using Artifactory plugin are disappeared post the plugin upgrade
Title: Message Title Pushkala Suriyanarayanan created an issue Jenkins / JENKINS-53942 Jobs using Artifactory plugin are disappeared post the plugin upgrade Issue Type: Bug Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2018-10-08 10:34 Environment: Jenkins version 2.121.3; Artifactory Plugin version 2.15.0 and above causes the issue, Operating system is RedHat Linux Priority: Blocker Reporter: Pushkala Suriyanarayanan The jobs which uses artifactory plugin are not visible and the other jobs seems to be crashed(Not able to configure) post the artifactory plugin upgrade to version 2.15.0 or above.. We have to upgrade the atifactory plugin inorder to fix the JEP-200 issue.. Jenkins version is 2.121.3; Artifactory Plugin version 2.15.0 and above causes the issue, Operating system is RedHat Linux.. Add Comment
[JIRA] (JENKINS-53675) Exclusion annotation for access-modifier-checker
Title: Message Title Steve Arch resolved as Fixed Jenkins / JENKINS-53675 Exclusion annotation for access-modifier-checker Change By: Steve Arch Status: Open Resolved Resolution: Fixed Released As: access-modifier:1.16 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-53906) Jenkins fails to start with Exception after update to 2.144
Title: Message Title Frank Shimizu updated JENKINS-53906 Fixed by downgrading to a non-corrupt gradle plugin version. Jenkins / JENKINS-53906 Jenkins fails to start with Exception after update to 2.144 Change By: Frank Shimizu Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
