[JIRA] (JENKINS-50105) EC2 Step provisioning incorrectly specifies a label
Title: Message Title Francis Upton created an issue Jenkins / JENKINS-50105 EC2 Step provisioning incorrectly specifies a label Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2018-03-12 05:51 Priority: Minor Reporter: Francis Upton The label value is specified as the name of the slave template. Causing a new instance to be force created each time, since any existing instance won't have that label. The label value should not be specified in the provisioning. Add Comment
[JIRA] (JENKINS-46571) Update URL scheme to remove URL encoding issues
Title: Message Title Ivan Meredith commented on JENKINS-46571 Re: Update URL scheme to remove URL encoding issues Sure. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50104) ssh-agent is killed after first use in docker container
Title: Message Title Santi Villalba commented on JENKINS-50104 Re: ssh-agent is killed after first use in docker container Maybe related to JENKINS-43050. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44560) Provision AWS instance from within a pipeline
Title: Message Title Francis Upton commented on JENKINS-44560 Re: Provision AWS instance from within a pipeline The work in the EC2Step does create and return the Amazon EC2 instance, but it returns it immediately before it can be used. It also did not add the node to Jenkins, such that when it was provisioned this way it did not show up in the Jenkins UI until the node finally came up. Alicia Doblas Is this what is intended? Should the provisioning here wait for the instance to become usable before returning it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50104) ssh-agent is killed after first use in docker container
Title: Message Title Santi Villalba created an issue Jenkins / JENKINS-50104 ssh-agent is killed after first use in docker container Issue Type: Bug Assignee: Unassigned Components: ssh-agent-plugin Created: 2018-03-12 05:29 Environment: OS: various linux versions (ubuntu 14.04 + docker 17.12.0, arch linux + docker 18.02.0). Jenkins 2.89.4 installed from latest docker image (as of 20180312), with ssh-agent plugin 1.15 and run like this: docker run \ --user root \ --rm \ --name jenkins \ --detach \ --publish 8080:8080 \ --publish 5:5 \ --volume jenkins-data:/var/jenkins_home \ --volume /var/run/docker.sock:/var/run/docker.sock \ jenkinsci/blueocean (as in https://jenkins.io/doc/book/installing/#downloading-and-running-jenkins-in-docker) Plugins -- Apache HttpComponents Client 4.x API Plugin - 4.5.3-2.1 Authentication Tokens API Plugin - 1.3 Autofavorite for Blue Ocean - 1.2.2 Bitbucket Branch Source Plugin - 2.2.10 Bitbucket Pipeline for Blue Ocean - 1.4.2 Blue Ocean - 1.4.2 Blue Ocean Core JS - 1.4.2 Blue Ocean Pipeline Editor - 1.4.2 bouncycastle API Plugin - 2.16.2 Branch API Plugin - 2.0.18 Common API for Blue Ocean - 1.4.2 Config API for Blue Ocean - 1.4.2 Credentials Binding Plugin - 1.15 Credentials Plugin - 2.1.16 Dashboard for Blue Ocean - 1.4.2 Design Language - 1.4.2 Display URL API - 2.2.0 Display URL for Blue Ocean - 2.2.0 Docker Commons Plugin - 1.11 Docker Pipeline - 1.15.1 Docker Slaves Plugin - 1.0.7 Durable Task Plugin - 1.21 Events API for Blue Ocean - 1.4.2 Favorite - 2.3.1 Folders Plugin - 6.3 Git client plugin - 2.7.1 Git Pipeline for Blue Ocean - 1.4.2 Git plugin - 3.8.0 GIT server Plugin - 1.7 GitHub API Plugin - 1.90 GitHub Branch Source Plugin - 2.3.2 GitHub Pipeline for Blue Ocean - 1.4.2 GitHub plugin - 1.29.0 Handy Uri Templates 2.x API Plugin - 2.1.6-1.0 HTML Publisher plugin - 1.14 i18n for Blue Ocean - 1.4.2 Jackson 2 API Plugin - 2.8.11.1 _javascript_ GUI Lib: ACE Editor bundle plugin - 1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin - 1.2.1 JIRA Integration for Blue Ocean - 1.4.2 JIRA plugin - 2.5 JSch dependency plugin - 0.1.54.2 JUnit Plugin - 1.24 JWT for Blue Ocean - 1.4.2 Mailer Plugin - 1.20 Matrix Authorization Strategy Plugin - 2.2 Matrix Project Plugin - 1.12 Mercurial plugin - 2.3 OWASP Markup Formatter Plugin - 1.5 patch-parameter - 1.2 Personalization for Blue Ocean - 1.4.2 Pipeline Graph Analysis Plugin - 1.6 Pipeline implementation for Blue Ocean - 1.4.2 Pipeline SCM API for Blue Ocean - 1.4.2 Pipeline: API - 2.26 Pipeline:
[JIRA] (JENKINS-46571) Update URL scheme to remove URL encoding issues
Title: Message Title James Dumay commented on JENKINS-46571 Re: Update URL scheme to remove URL encoding issues Mind if we spend 20 talking about the solution here tomorrow? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46571) Update URL scheme to remove URL encoding issues
Title: Message Title Ivan Meredith commented on JENKINS-46571 Re: Update URL scheme to remove URL encoding issues James Dumay Technically you can get away with not encoding slashes. I'm not sure this is a good idea though. I think to be to spec it needs to be encoded =/ But at the very least even if proxies decode the slash, its still gonna work Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title James Dumay commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Helmi BEDOUI we still plan on fixing this but no ETA yet. Requires a big rework of how statuses are reporting in Pipeline, so its not as simple as it might seem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46571) Update URL scheme to remove URL encoding issues
Title: Message Title James Dumay commented on JENKINS-46571 Re: Update URL scheme to remove URL encoding issues Ivan Meredith how does moving to query params fix the problem we have? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47130) EC2 plugin 1.37 fails to provision previously defined slaves
Title: Message Title Francis Upton commented on JENKINS-47130 Re: EC2 plugin 1.37 fails to provision previously defined slaves I see the problem here. This was caused by the "node" field that was added to the SlaveTemplate https://github.com/jenkinsci/ec2-plugin/pull/232. The initial value of "node" was set to "true", allowing it to be provisioned normally. However, any serialized SlaveTemplates would (incorrectly) have the value of "false" which caused them to be ignored during the normal provisioning. The work of the PR did not consider this case. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47130) EC2 plugin 1.37 fails to provision previously defined slaves
Title: Message Title Francis Upton updated an issue Jenkins / JENKINS-47130 EC2 plugin 1.37 fails to provision previously defined slaves Change By: Francis Upton Summary: EC2 plugin 1.37 does not start stopped instances when provisionning fails to provision previously defined slaves Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46869) Can not register an EC2 instance as a node agent
Title: Message Title Francis Upton commented on JENKINS-46869 Re: Can not register an EC2 instance as a node agent I see the problem here. This was caused by the "node" field that was added to the SlaveTemplate https://github.com/jenkinsci/ec2-plugin/pull/232. The initial value of "note" was set to "true", allowing it to be provisioned normally. However, any serialized SlaveTemplates would (incorrectly) have the value of "false" which caused them to be ignored during the normal provisioning. The work of the PR did not consider this case. I'm going to replace this by a different mechanism which more explicitly marks pipeline step created nodes so they can be ignored. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49906) Form validation considers the rename "no op" to be an error
Title: Message Title Daniel Beck commented on JENKINS-49906 Re: Form validation considers the rename "no op" to be an error This UI is not in 2.107.x. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49906) Form validation considers the rename "no op" to be an error
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-49906 Form validation considers the rename "no op" to be an error Change By: Daniel Beck Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50103) Use of BUILD_TIMESTAMP for stage-level exact time
Title: Message Title Rex Coronel created an issue Jenkins / JENKINS-50103 Use of BUILD_TIMESTAMP for stage-level exact time Issue Type: Improvement Assignee: Steven G Brown Components: pipeline, timestamper-plugin Created: 2018-03-12 03:47 Priority: Critical Reporter: Rex Coronel Is there a way to know exactly the current timestamp for each stage in a workflow/pipeline? I'm currently using BUILD_TIMESTAMP but it only captures the timestamp of when the build started. I want to capture the exact timestamp on the end of the build. I need this for the reason that I have to include it in the e-mail when the build is finished. Add Comment
[JIRA] (JENKINS-50101) Support for declarative pipeline
Title: Message Title Allan BURDAJEWICZ updated JENKINS-50101 Jenkins / JENKINS-50101 Support for declarative pipeline Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50100) Sleep throws after calling Jenkins.instance like getItemByFullName
Title: Message Title Andrew Bayer resolved as Not A Defect As the stacktrace shows, the problem is that you’ve called getItemByFullName and now have a WorkflowJob object in scope. So when the Pipeline is next serialized (which will happen eventually regardless but is always triggered by a sleep, things fail because WorkflowJob isn’t serializable. You should avoid calling things like Jenkins.instance.getItemByFullName in the first place, but if you must, you should do so in a method annotated with @NonCPS. Methods with that annotation can’t call Pipeline steps but aren’t serialized. Jenkins / JENKINS-50100 Sleep throws after calling Jenkins.instance like getItemByFullName Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50101) Support for declarative pipeline
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-50101 Support for declarative pipeline Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50102) Support for Snippet Generator
Title: Message Title Allan BURDAJEWICZ assigned an issue to Unassigned Jenkins / JENKINS-50102 Support for Snippet Generator Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50102) Support for Snippet Generator
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-50102 Support for Snippet Generator Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46571) Update URL scheme to remove URL encoding issues
Title: Message Title Ivan Meredith started work on JENKINS-46571 Change By: Ivan Meredith Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46571) Update URL scheme to remove URL encoding issues
Title: Message Title Ivan Meredith updated an issue Jenkins / JENKINS-46571 Update URL scheme to remove URL encoding issues Change By: Ivan Meredith Sprint: Blue Ocean 1.5 - beta 3 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46571) Update URL scheme to remove URL encoding issues
Title: Message Title Ivan Meredith commented on JENKINS-46571 Re: Update URL scheme to remove URL encoding issues We could just have that in a query param as well Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44549) multibranchpipeline.branchNames is not updated when new branch is created (or deleted)
Title: Message Title Ivan Meredith assigned an issue to Ivan Meredith Jenkins / JENKINS-44549 multibranchpipeline.branchNames is not updated when new branch is created (or deleted) Change By: Ivan Meredith Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50102) Support for Snippet Generator
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-50102 Support for Snippet Generator Issue Type: Improvement Assignee: Unassigned Components: authorize-project-plugin Created: 2018-03-12 00:43 Environment: authorize-project:1.3.0 Priority: Minor Reporter: Allan BURDAJEWICZ It would be great if there was support for the Pipeline Snippet Generator. Add Comment
[JIRA] (JENKINS-50101) Support for declarative pipeline
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-50101 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50101) Support for declarative pipeline
Title: Message Title
Allan BURDAJEWICZ created an issue
Jenkins / JENKINS-50101
Support for declarative pipeline
Issue Type:
Improvement
Assignee:
Unassigned
Components:
authorize-project-plugin
Created:
2018-03-12 00:41
Environment:
authorize-project:1.3.0
Priority:
Major
Reporter:
Allan BURDAJEWICZ
It would be great if there was support for the Declarative Pipeline syntax. Something like the following:
pipeline {
agent any
options {
authorizeProject(specificUsersAuthorizationStrategy(userid: 'admin', dontRestrictJobConfiguration: false))
}
stages {
stage('Example') {
steps {
echo 'Hello World'
}
}
}
}
Add Comment
[JIRA] (JENKINS-45511) Blue Ocean Favorite bug
Title: Message Title Ivan Meredith commented on JENKINS-45511 Re: Blue Ocean Favorite bug Does favoriting in classic ui work properly? We are basically just using the favorites plugin to do favorites in blueocean so im a bit confused as to how this is happening. Unless Active Directory plugin does something funky with users. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47872) Navigating from Classic to BO: projects w/o Jenkinsfiles go to Branches tab, where no "Create Pipeline" button is shown
Title: Message Title Ivan Meredith assigned an issue to Ivan Meredith Jenkins / JENKINS-47872 Navigating from Classic to BO: projects w/o Jenkinsfiles go to Branches tab, where no "Create Pipeline" button is shown Change By: Ivan Meredith Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48293) Improvements to GitCreationTest#testSSHPrivateRepostory so we can remove @Ignore
Title: Message Title Ivan Meredith commented on JENKINS-48293 Re: Improvements to GitCreationTest#testSSHPrivateRepostory so we can remove @Ignore Karl Shultz This was @ignored because for some reason I just could not get it to auth with the key pair i had. Was very frustrating. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47489) Opening and closing run will always open with the previous node selection
Title: Message Title Josh McDonald assigned an issue to Josh McDonald Jenkins / JENKINS-47489 Opening and closing run will always open with the previous node selection Change By: Josh McDonald Assignee: Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46677) windows slave is disconnecting frequently
Title: Message Title Oleg Nenashev resolved as Incomplete Not diagnosable, not enough information: No full agent logs / master logs / versions. Feel free to reopen if you can provide the info Jenkins / JENKINS-46677 windows slave is disconnecting frequently Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-47094) Got exception when adding Jenkins windows slave.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47094 Got exception when adding Jenkins windows slave. Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46677) windows slave is disconnecting frequently
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-46677 windows slave is disconnecting frequently Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-45791) (JNLP) Mac slave went offline during build
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-45791 (JNLP) Mac slave went offline during build Change By: Oleg Nenashev Component/s: remoting Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-45791) (JNLP) Mac slave went offline during build
Title: Message Title Oleg Nenashev commented on JENKINS-45791 Re: (JNLP) Mac slave went offline during build It has been submitted to a wrong component and hence it has been never processed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-45018) Slave getting disconnected frequently
Title: Message Title Oleg Nenashev commented on JENKINS-45018 Re: Slave getting disconnected frequently It has been submitted to a wrong component and hence it has been never processed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44267) iOS slave # of executor error in pipeline as code
Title: Message Title Oleg Nenashev commented on JENKINS-44267 Re: iOS slave # of executor error in pipeline as code It has been submitted to a wrong component and hence it has been never processed. Assigned to proper components though I cannot conclude whether it is an issue or not by screenshots. I would need an API dump for such agent. Maybe some tasks are just flyweight ones Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-45018) Slave getting disconnected frequently
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-45018 Slave getting disconnected frequently Change By: Oleg Nenashev Component/s: remoting Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44267) iOS slave # of executor error in pipeline as code
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-44267 iOS slave # of executor error in pipeline as code Change By: Oleg Nenashev Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44267) iOS slave # of executor error in pipeline as code
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-44267 iOS slave # of executor error in pipeline as code Change By: Oleg Nenashev Component/s: command-launcher-plugin Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44267) iOS slave # of executor error in pipeline as code
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-44267 iOS slave # of executor error in pipeline as code Change By: Oleg Nenashev Summary: iOS salve slave # of executor error in pipeline as code Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41920) Duplicate name on Network while connecting to Windows Slave
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-41920 Duplicate name on Network while connecting to Windows Slave Change By: Oleg Nenashev Component/s: windows-slaves-plugin Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41920) Duplicate name on Network while connecting to Windows Slave
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-41920 Duplicate name on Network while connecting to Windows Slave Change By: Oleg Nenashev Assignee: João Ferreira Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-19490) Builds for same job are scheduled on different slave nodes
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce It has been submitted to a wrong component and hence it has been never processed. If it still happens on new Jenkins versions, please create a new ticket with diagnostics info Jenkins / JENKINS-19490 Builds for same job are scheduled on different slave nodes Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group
[JIRA] (JENKINS-37093) slave-agent.jnlp reverts to using http
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37093 slave-agent.jnlp reverts to using http Change By: Oleg Nenashev Component/s: remoting Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-19490) Builds for same job are scheduled on different slave nodes
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-19490 Builds for same job are scheduled on different slave nodes Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-20810) slave doesn't work
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-20810 slave doesn't work Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-20810) slave doesn't work
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce It has been submitted to a wrong component and hence it has been never processed. If it still happens on new Jenkins versions, please create a new ticket with diagnostics info Jenkins / JENKINS-20810 slave doesn't work Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-47568) POST-JENKINS-42602: move core-js i18n to core-js plugin
Title: Message Title Ivan Meredith commented on JENKINS-47568 Re: POST-JENKINS-42602: move core-js i18n to core-js plugin If we merge everything into web then this is moot anyway. Leaving it open for now though Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-23132) 4-5min delay at end of job on slave
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-23132 4-5min delay at end of job on slave Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-23132) 4-5min delay at end of job on slave
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce It has been submitted to a wrong component and hence it has been never processed. If it still happens on new Jenkins versions, please create a new ticket with diagnostics info. Jenkins / JENKINS-23132 4-5min delay at end of job on slave Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-25195) Jenkins jobs start but periodically hang on newly restarted slave
Title: Message Title Oleg Nenashev resolved as Fixed It has been submitted to a wrong component and hence it has been never processed. If it still happens on new Jenkins versions, please create a new ticket with diagnostics info Jenkins / JENKINS-25195 Jenkins jobs start but periodically hang on newly restarted slave Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-33975) On demand slave shows misleading offline cause message
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-33975 On demand slave shows misleading offline cause message Change By: Oleg Nenashev Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-25195) Jenkins jobs start but periodically hang on newly restarted slave
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-25195 Jenkins jobs start but periodically hang on newly restarted slave Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-status-plugin Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-27160) display the slave name in the main job's console output
Title: Message Title Oleg Nenashev commented on JENKINS-27160 Re: display the slave name in the main job's console output "Building on master in " in the beginning of the log IIUC the request correctly. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-27160) display the slave name in the main job's console output
Title: Message Title Oleg Nenashev resolved as Not A Defect Please reopen if I misunderstood it Jenkins / JENKINS-27160 display the slave name in the main job's console output Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-29683) On slave crash, task is often unkillable
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce It has been submitted to a wrong component and hence it has been never processed. If it still happens on new Jenkins versions, please create a new ticket with diagnostics info Jenkins / JENKINS-29683 On slave crash, task is often unkillable Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-27160) display the slave name in the main job's console output
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-27160 display the slave name in the main job's console output Change By: Oleg Nenashev Component/s: matrix-project-plugin Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-29683) On slave crash, task is often unkillable
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-29683 On slave crash, task is often unkillable Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-31466) ssl connection from jenkins master to jenkins slave
Title: Message Title Oleg Nenashev resolved as Incomplete I doubt the master has ever sent credentials to agents in CURL. All the communications now either secured by HTTPs or JNLP4 with TLS encryption Jenkins / JENKINS-31466 ssl connection from jenkins master to jenkins slave Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-31466) ssl connection from jenkins master to jenkins slave
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-31466 ssl connection from jenkins master to jenkins slave Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-31651) Severe: I/O error in channel Jenkins-1.553
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-31651 Severe: I/O error in channel Jenkins-1.553 Change By: Oleg Nenashev Component/s: remoting Component/s: slave-status-plugin Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-31651) Severe: I/O error in channel Jenkins-1.553
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce It has been submitted to a wrong component and hence it has been never processed. If it still happens on new Jenkins versions, please create a new ticket with diagnostics info Jenkins / JENKINS-31651 Severe: I/O error in channel Jenkins-1.553 Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-32514) unable to launch master-slave while jenkins running in HTTPS
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce It has been submitted to a wrong component and hence it has been never processed. Looks like an infra issue. If it still happens on new Jenkins versions, please create a new ticket with diagnostics info Jenkins / JENKINS-32514 unable to launch master-slave while jenkins running in HTTPS Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-32862) java.io.IOException: Failed to load https://ci.marlysys.lab/jenkins/computer/slave3/slave-agent.jnlp: 401 Unauthorized
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce It has been submitted to a wrong component and hence it has been never processed. If it still happens on new Jenkins versions, please create a new ticket with diagnostics info Jenkins / JENKINS-32862 java.io.IOException: Failed to load https://ci.marlysys.lab/jenkins/computer/slave3/slave-agent.jnlp: 401 Unauthorized Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-32514) unable to launch master-slave while jenkins running in HTTPS
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-32514 unable to launch master-slave while jenkins running in HTTPS Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33505) windows slave keeps disconnecting with "Trying protocol: JNLP2-connect"
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce Jenkins / JENKINS-33505 windows slave keeps disconnecting with "Trying protocol: JNLP2-connect" Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-32862) java.io.IOException: Failed to load https://ci.marlysys.lab/jenkins/computer/slave3/slave-agent.jnlp: 401 Unauthorized
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-32862 java.io.IOException: Failed to load https://ci.marlysys.lab/jenkins/computer/slave3/slave-agent.jnlp: 401 Unauthorized Change By: Oleg Nenashev Component/s: core Component/s: remoting Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33505) windows slave keeps disconnecting with "Trying protocol: JNLP2-connect"
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-33505 windows slave keeps disconnecting with "Trying protocol: JNLP2-connect" Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33505) windows slave keeps disconnecting with "Trying protocol: JNLP2-connect"
Title: Message Title Oleg Nenashev commented on JENKINS-33505 Re: windows slave keeps disconnecting with "Trying protocol: JNLP2-connect" It has been submitted to a wrong component and hence it has been never processed. If it still happens on new Jenkins versions, please create a new ticket with diagnostics info Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41268) TcpSlaveAgentListener is invalid 403: Forbidden
Title: Message Title Oleg Nenashev commented on JENKINS-41268 Re: TcpSlaveAgentListener is invalid 403: Forbidden It has been submitted to a wrong component and hence it has been never processed. Looks like an infra issue. If it still happens on new Jenkins versions, please create a new ticket Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41268) TcpSlaveAgentListener is invalid 403: Forbidden
Title: Message Title Oleg Nenashev resolved as Not A Defect Jenkins / JENKINS-41268 TcpSlaveAgentListener is invalid 403: Forbidden Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43334) Slave went offline during the build in different scenarios
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-43334 Slave went offline during the build in different scenarios Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43334) Slave went offline during the build in different scenarios
Title: Message Title Oleg Nenashev commented on JENKINS-43334 Re: Slave went offline during the build in different scenarios It has been submitted to a wrong component and hence it has been never processed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41268) TcpSlaveAgentListener is invalid 403: Forbidden
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-41268 TcpSlaveAgentListener is invalid 403: Forbidden Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43644) Platform command not found on mac ox? Jenkins integration
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce It has been submitted to a wrong component and hence it has been never processed. If it still happens on new Jenkins versions, please create a new ticket Jenkins / JENKINS-43644 Platform command not found on mac ox? Jenkins integration Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-22741) Slaves randomly not started/connected after updating Jenkins to 1.560 and slave.jar to 2.39
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce It has been submitted to a wrong component and hence it has been never processed. If it happens on newer versions, please create a new issue Jenkins / JENKINS-22741 Slaves randomly not started/connected after updating Jenkins to 1.560 and slave.jar to 2.39 Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group
[JIRA] (JENKINS-22741) Slaves randomly not started/connected after updating Jenkins to 1.560 and slave.jar to 2.39
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-22741 Slaves randomly not started/connected after updating Jenkins to 1.560 and slave.jar to 2.39 Change By: Oleg Nenashev Component/s: remoting Component/s: slave-status-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46118) hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Oleg Nenashev resolved as Won't Do The issue has been submitted to the wrong component and hence it has never been processed. The versions you refer to are not an open-source package of Jenkins. Please contact the vendor if you still suffer from it Jenkins / JENKINS-46118 hudson.remoting.ChannelClosedException: channel is already closed Change By: Oleg Nenashev Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-46118) hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-46118 hudson.remoting.ChannelClosedException: channel is already closed Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47052) JNLP Slave connection error
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47052 JNLP Slave connection error Change By: Oleg Nenashev Component/s: core Component/s: slave-utilization-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47052) JNLP Slave connection error
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47052 JNLP Slave connection error Change By: Oleg Nenashev Labels: jnlp remoting slaves windows Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-26143) Workflow Snippet Generator - Incorrect format for Input with Choice Parameter
Title: Message Title Daniel Beck updated JENKINS-26143 Jenkins / JENKINS-26143 Workflow Snippet Generator - Incorrect format for Input with Choice Parameter Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28155 Job fails with [An existing connection was forcibly closed by the remote host] Change By: Oleg Nenashev Component/s: slave-utilization Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43892) Developer would like to see all successful test results
Title: Message Title James Dumay commented on JENKINS-43892 Re: Developer would like to see all successful test results Successful test display is shipping in the next release. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43892) Developer would like to see all successful test results
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-43892 Developer would like to see all successful test results Change By: James Dumay Attachment: successful-tests.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49896) Support integration-test goal for the Invoker Publisher
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-49896 Support integration-test goal for the Invoker Publisher Change By: Cyrille Le Clerc Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49861) Disable master executors by default
Title: Message Title Baptiste Mathus started work on JENKINS-49861 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49861) Disable master executors by default
Title: Message Title Baptiste Mathus stopped work on JENKINS-49861 Change By: Baptiste Mathus Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49861) Disable master executors by default
Title: Message Title Baptiste Mathus updated JENKINS-49861 Jenkins / JENKINS-49861 Disable master executors by default Change By: Baptiste Mathus Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49896) Support integration-test goal for the Invoker Publisher
Title: Message Title Cyrille Le Clerc resolved as Fixed Fixed in pipeline-maven 3.4.3 Jenkins / JENKINS-49896 Support integration-test goal for the Invoker Publisher Change By: Cyrille Le Clerc Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50100) Sleep throws after calling Jenkins.instance like getItemByFullName
Title: Message Title
Serghei Moret updated an issue
Jenkins / JENKINS-50100
Sleep throws after calling Jenkins.instance like getItemByFullName
Change By:
Serghei Moret
Jenkins throws immediately while trying to sleep (it says sleeping but immediately throws, so the sleep doesn't happen). This happens only when the sleep command stays after Jenkins.instance.getItemByFullName method call. If I call sleep just one line before it sleeps as expected.Stack trace: {code:java} [Pipeline] sleepSleeping for 10 sec[Pipeline] End of Pipelinean exception which occurred: in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@6e3fdbf0 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@42c458b6 in field com.cloudbees.groovy.cps.Continuable.e in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@689786e7 in field org.jenkinsci.plugins.workflow.cps.CpsThread.program in object org.jenkinsci.plugins.workflow.cps.CpsThread@79ea6269 in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@ac4614b in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@ac4614bCaused: java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860) at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65) at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56) at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50) at org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344) at java.util.HashMap.internalWriteEntries(HashMap.java:1785) at java.util.HashMap.writeObject(HashMap.java:1362) at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:273) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:976) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at
[JIRA] (JENKINS-50100) Sleep throws after calling Jenkins.instance like getItemByFullName
Title: Message Title Serghei Moret created an issue Jenkins / JENKINS-50100 Sleep throws after calling Jenkins.instance like getItemByFullName Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-03-11 20:53 Labels: jenkins pipeline Priority: Major Reporter: Serghei Moret Jenkins throws immediately while trying to sleep (it says sleeping but immediately throws, so the sleep doesn't happen). This happens only when the sleep command stays after Jenkins.instance.getItemByFullName method call. If I call sleep just one line before it sleeps as expected. Stack trace: [Pipeline] sleep Sleeping for 10 sec [Pipeline] End of Pipeline an exception which occurred: in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@6e3fdbf0 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@42c458b6 in field com.cloudbees.groovy.cps.Continuable.e in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@689786e7 in field org.jenkinsci.plugins.workflow.cps.CpsThread.program in object org.jenkinsci.plugins.workflow.cps.CpsThread@79ea6269 in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@ac4614b in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@ac4614b Caused: java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860) at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65) at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56) at
[JIRA] (JENKINS-50051) Vault Plugin - Unable to retrieve secret get 404 error
Title: Message Title Stuart Whelan assigned an issue to Unassigned Jenkins / JENKINS-50051 Vault Plugin - Unable to retrieve secret get 404 error Change By: Stuart Whelan Assignee: Stuart Whelan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50031) Ansible Tower 3.3 removes authtoken from API
Title: Message Title Francois Herbert commented on JENKINS-50031 Re: Ansible Tower 3.3 removes authtoken from API Hi John, That resolves this issue, thanks for the quick resolution! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49836) Cannot view Console logs
Title: Message Title Oleg Nenashev commented on JENKINS-49836 Re: Cannot view Console logs So, somebody needs to setup proper escaping Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49588) java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)
Title: Message Title Oleg Nenashev commented on JENKINS-49588 Re: java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035) Alexander Trauzziping Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49836) Cannot view Console logs
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-49836 Cannot view Console logs Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-32599) JENKINS_HOME/users/config.xml Results in Nameless User
Title: Message Title Oleg Nenashev updated JENKINS-32599 The patch has been integrated towards 2.111 Jenkins / JENKINS-32599 JENKINS_HOME/users/config.xml Results in Nameless User Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
