[JIRA] (JENKINS-50725) Active Choice Reactive Parameter list without scroll bar
Title: Message Title
Jani Rautio edited a comment on JENKINS-50725
Re: Active Choice Reactive Parameter list without scroll bar
Made workaround for this with Simple Theme plugin and Extra CSS setting.div[id^="ecp_choice-parameter-"] \{ overflow-y: visible !important; height: auto !important; } ...closing item.
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-50725) Active Choice Reactive Parameter list without scroll bar
Title: Message Title
Jani Rautio commented on JENKINS-50725
Re: Active Choice Reactive Parameter list without scroll bar
Made workaround for this with Simple Theme plugin and Extra CSS setting. div[id^="ecp_choice-parameter-"] { overflow-y: visible !important; height: auto !important; } ...closing item.
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-50808) Backport new UC CA into LTS
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-50808 Backport new UC CA into LTS Change By: Oliver Gondža Labels: lts 2.107.3 - candidate 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-46386) Agent sometimes fails to launch in custom cloud provider
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-46386 Agent sometimes fails to launch in custom cloud provider Change By: Oliver Gondža Labels: lts 2.107.3 - candidate 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-49401) Race condition can prevent setup wizard from initializing properly
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-49401 Race condition can prevent setup wizard from initializing properly Change By: Oliver Gondža Labels: lts 2.107.3 - candidate 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-50324) User without READ cannot logout from CLI with remoting
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-50324 User without READ cannot logout from CLI with remoting Change By: Oliver Gondža Labels: lts 2.107.3 - candidate 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-50748) Caught exception evaluating in configureSecurity - NullPointerException
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-50748 Caught exception evaluating in configureSecurity - NullPointerException Change By: Oliver Gondža Labels: lts 2.107.3 - candidate fixed regression 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-50635) NUnit plugin does not fail build on test-runner error
Title: Message Title Alex Earl commented on JENKINS-50635 Re: NUnit plugin does not fail build on test-runner error It looks like debug mode is only available if you connect via a debugger, so that doesn't help much. I'll just try running your file through the xslt transform locally. 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-47925) tfs plugin receives null as a commit id when triggered via jenkins service hook "code pushed"
Title: Message Title John Lozano commented on JENKINS-47925 Re: tfs plugin receives null as a commit id when triggered via jenkins service hook "code pushed" +1 On this issue, i know tfs-git doesn't get a lot of love, but this bit me today. Kellie Jos, your workaround saved me, thanks! 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-10218) Copy from Windows-Slave doesn't work
Title: Message Title Alex Earl commented on JENKINS-10218 Re: Copy from Windows-Slave doesn't work What is different about those two agents? 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-21311) Queue item cancellation via REST api works but returns a 404
Title: Message Title Martin d'Anjou edited a comment on JENKINS-21311 Re: Queue item cancellation via REST api works but returns a 404 Running into this bug as I am adding the feature to cancel a queue item to the [jenkins-rest|https://github.com/cdancy/jenkins-rest/pull/4] java library. I use Jenkins 2.107.1. 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-21311) Queue item cancellation via REST api works but returns a 404
Title: Message Title Martin d'Anjou commented on JENKINS-21311 Re: Queue item cancellation via REST api works but returns a 404 Running into this bug as I am adding the feature to cancel a queue item to the jenkins-rest java library. 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-50857) Docker agent on windows fails with Cannot run program "id"
Title: Message Title Jonathan Kuleff updated an issue Jenkins / JENKINS-50857 Docker agent on windows fails with Cannot run program "id" Change By: Jonathan Kuleff Environment: Windows Server Code 2016 , Jenkins 2.89.4 Pipeline: Declarative 1.2.8 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-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Jonathan Kuleff updated an issue Jenkins / JENKINS-50886 Declarative pipeline with pollSCM triggers 2 builds Change By: Jonathan Kuleff Priority: Minor Major 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-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title
Jonathan Kuleff updated an issue
Jenkins / JENKINS-50886
Declarative pipeline with pollSCM triggers 2 builds
Change By:
Jonathan Kuleff
I have a multibranch declarative pipeline with a pollSCM trigger to poll every 2 minutes. Whenever there is a change to the branch in BitBucket it triggers correctly but about 2 minutes later it triggers again. I'm not sure if this is a bug or some configuration error on my behalf. I've attached a screenshot of the duplicate builds and poll log for one of the duplicate builds. Below is the top of me my declarative pipeline for reference to how I am setting it up.{code:java}pipeline { agent none environment { APPVERSION = '0.1.0' NUGET_API_KEY = credentials('build-server-nuget-id-readonly') } triggers { // poll repo every 2 minute for changes pollSCM('*/2 * * * *') } options { // add timestamps to output timestamps() overrideIndexTriggers(false) buildDiscarder(logRotator(numToKeepStr: '10')) skipStagesAfterUnstable() durabilityHint('PERFORMANCE_OPTIMIZED') }...}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50857) Docker agent on windows fails with Cannot run program "id"
Title: Message Title Jonathan Kuleff updated an issue Jenkins / JENKINS-50857 Docker agent on windows fails with Cannot run program "id" Change By: Jonathan Kuleff Priority: Minor Critical 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-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Jonathan Kuleff updated an issue Jenkins / JENKINS-50886 Declarative pipeline with pollSCM triggers 2 builds Change By: Jonathan Kuleff Labels: bitbucket declarative pipeline, pollscm 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-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title
Jonathan Kuleff created an issue
Jenkins / JENKINS-50886
Declarative pipeline with pollSCM triggers 2 builds
Issue Type:
Bug
Assignee:
Vincent Latombe
Attachments:
jenkins polling log.txt, jenkins-duplicate-example.png
Components:
bitbucket-plugin, pipeline, pollscm-plugin
Created:
2018-04-19 01:58
Environment:
Official Jenkins Container (on AWS ECS) Jenkins 2.89.4 Pipeline: Declarative 1.2.8,
Priority:
Minor
Reporter:
Jonathan Kuleff
I have a multibranch declarative pipeline with a pollSCM trigger to poll every 2 minutes. Whenever there is a change to the branch in BitBucket it triggers correctly but about 2 minutes later it triggers again. I'm not sure if this is a bug or some configuration error on my behalf. I've attached a screenshot of the duplicate builds and poll log for one of the duplicate builds. Below is the top of me declarative pipeline for reference to how I am setting it up.
pipeline {
agent none
environment {
APPVERSION = '0.1.0'
NUGET_API_KEY = credentials('build-server-nuget-id-readonly')
}
triggers {
// poll repo every 2 minute for changes
pollSCM('*/2 * * * *')
}
options {
// add timestamps to output
timestamps()
overrideIndexTriggers(false)
buildDiscarder(logRotator(numToKeepStr: '10'))
skipStagesAfterUnstable()
[JIRA] (JENKINS-50885) BlueOcean should have an optional dependency on JIRA plugin
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-50885 BlueOcean should have an optional dependency on JIRA plugin Issue Type: Bug Assignee: Michael Neale Components: blueocean-plugin Created: 2018-04-19 01:06 Priority: Minor Reporter: Vivek Pandey blueocean-jira plugin is a mandatory plugin installed using blueocean aggregator plugin. We should allow users to be able to uninstall it. This is going to help users who are struggling with jira plugin issues. Add Comment This
[JIRA] (JENKINS-50883) Blue ocean:GitHub Webhook is not created after new pipeline creation
Title: Message Title Isaac Cohen created an issue Jenkins / JENKINS-50883 Blue ocean:GitHub Webhook is not created after new pipeline creation Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin, github-branch-source-plugin Created: 2018-04-18 23:43 Environment: Jenkins: 2.107.1 Blue Ocean: 1.5.0 GitHub Pipeline for Blue Ocean: 1.5.0 GitHub Branch Source Plugin: 2.3.3 GitHub Plugin: 1.29.0 Branch API Plugin: 2.0.19 Priority: Critical Reporter: Isaac Cohen Related to JENKINS-48035, when I create a new Pipeline for GitHub in Blue Ocean, it doesn't register any webhooks. Using the latest versions of all plugins. In order to register the webhooks I am forced to use the workaround via: Manage Jenkins > GitHub plugin > Advanced > Re-register hooks for all jobs > webhook in GitHub is finally generated. Add Comment
[JIRA] (JENKINS-29188) api URL for REST API is not available for flowGraphTable
Title: Message Title Damien Jiang edited a comment on JENKINS-29188 Re: api URL for REST API is not available for flowGraphTable We're trying to do analytics on the runtime of each node using a combination of the Blue Ocean REST API, the normal Jenkins REST API, and the /wfapi routes. We've run into problems collecting all the information we want: for each node, we want its: * name (from Blue Ocean API) * start time (from Blue Ocean API) * runtime (from Blue Ocean API, but runtime for nodes in parallel steps is inaccurate, as described here : https://issues.jenkins-ci.org/browse/JENKINS-38536 ) * computer (Jenkins slave) the node runs on.This last piece of data isn't accessible from the Blue Ocean API, since it [excludes stages and parallels/blocks|https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest#get-pipeline-steps], and we need to find the log for the `Allocate Node` block to find the computer, as far as I know?So, we: * Use `api/json?tree=actions[nodes[displayName,id,parents]]` to get a list of _all_ workflow steps * map `Allocate node : Start` steps to the nodes found in Blue Ocean (kind of fuzzy, since parallel steps aren't allocated a node but appear in Blue Ocean, while the `Declarative: Post Actions` step is allocated a node, but doesn't appear in Blue Ocean) * use `/execution/node/[node_id]/wfapi/log` to read the log for the `Allocate node : Start` step and actually get the computer nameIt seems like an API version of the flowGraphTable would simplify this process by an awful lot, since all the information we want (other than the logs for Allocate Node steps) can be found by actually viewing the flowGraphTable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-29188) api URL for REST API is not available for flowGraphTable
Title: Message Title Damien Jiang edited a comment on JENKINS-29188 Re: api URL for REST API is not available for flowGraphTable We're trying to do analytics on the runtime of each node using a combination of the Blue Ocean REST API, the normal Jenkins REST API, and the /wfapi routes. We've run into problems collecting all the information we want: for each node, we want its: * name (from Blue Ocean API) * start time (from Blue Ocean API) * runtime (from Blue Ocean API, but runtime for nodes in parallel steps is inaccurate, as described here) * computer (Jenkins slave) the node runs on.This last piece of data isn't accessible from the Blue Ocean API, since it [excludes stages and parallels/blocks|https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest#get-pipeline-steps], and we need to find the log for the `Allocate Node` block to find the computer, as far as I know?So, we: * Use `api/json?tree=actions[nodes[displayName,id,parents]]` to get a list of _all_ workflow steps * map `Allocate node : Start` steps to the nodes found in Blue Ocean (kind of fuzzy, since parallel steps aren't allocated a node but appear in Blue Ocean, while the `Declarative: Post Actions` step is allocated a node, but doesn't appear in Blue Ocean) * use `/execution/node/[node_id]/wfapi/log` to read the log for the `Allocate node : Start` step and actually get the computer nameIt seems like an API version of the flowGraphTable would simplify this process by an awful lot, since all the information we want (other than the logs for Allocate Node steps) can be found by actually viewing the flowGraphTable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-50507 Re: withMaven must not trigger its own project Visualisation glitch is fixed in 3.5.4-beta-1, TODO add URL once published https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.5.4-beta-1/pipeline-maven-3.5.4-beta-1.hpi[~dantran] can you please test?Can you verify if you actually get the job trigger of if it was "just" this visualisation glitch? 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-50852) Maven report: remove duplicate dependencies list
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-50852 Re: Maven report: remove duplicate dependencies list Fixed in 3.5.4-beta-1, TODO add URL once published https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.5.4-beta-1/pipeline-maven-3.5.4-beta-1.hpi[~dantran] can you please test? 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-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc commented on JENKINS-50507 Re: withMaven must not trigger its own project Visualisation glitch is fixed in 3.5.4-beta-1, TODO add URL once published 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-50852) Maven report: remove duplicate dependencies list
Title: Message Title Cyrille Le Clerc updated JENKINS-50852 Jenkins / JENKINS-50852 Maven report: remove duplicate dependencies list Change By: Cyrille Le Clerc 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-50852) Maven report: remove duplicate dependencies list
Title: Message Title Cyrille Le Clerc commented on JENKINS-50852 Re: Maven report: remove duplicate dependencies list Fixed in 3.5.4-beta-1, TODO add URL once published 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-50852) Maven report: remove duplicate dependencies list
Title: Message Title Cyrille Le Clerc updated JENKINS-50852 Jenkins / JENKINS-50852 Maven report: remove duplicate dependencies list Change By: Cyrille Le Clerc 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-50852) Maven report: remove duplicate dependencies list
Title: Message Title Cyrille Le Clerc started work on JENKINS-50852 Change By: Cyrille Le Clerc 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-50507) withMaven must not trigger its own project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50507 Re: withMaven must not trigger its own project Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/3634b6796e4fe951cb31561180b5386fb867f3e3 Log: Merge pull request #145 from jenkinsci/JENKINS-50507 JENKINS-50507 If a pipeline consumes the artifacts it produces, the… Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/13799d43290f...3634b6796e4f 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-50507) withMaven must not trigger its own project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50507 Re: withMaven must not trigger its own project Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/7381b37cec69011574e33db01c17e237884fde7b Log: JENKINS-50507 Fix javadocs 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-50882) Declarative Directive Generator is a 404 in multibranch Pipeline
Title: Message Title Andrew Bayer commented on JENKINS-50882 Re: Declarative Directive Generator is a 404 in multibranch Pipeline Pretty sure I can fix this 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-50881) Accessing the job config xml via the .../config.xml URL results in a XML Parsing Error
Title: Message Title Rich Duncan closed an issue as Not A Defect It was a browser issue Jenkins / JENKINS-50881 Accessing the job config xml via the .../config.xml URL results in a XML Parsing Error Change By: Rich Duncan Status: Open Closed 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-50882) Declarative Directive Generator is a 404 in multibranch Pipeline
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-50882 Declarative Directive Generator is a 404 in multibranch Pipeline Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-04-18 21:30 Environment: Jenkins 2.107.2 Declarative: 1.2.9 Priority: Minor Reporter: Christopher Orr Clicking "Pipeline Syntax" in the sidebar and then "Declarative Directive Generator" works for a Pipeline, but not for a Multibranch Pipeline. In the latter case, a 404 page is shown. This seems to happen in all cases, regardless of whether the jobs are defined at the top-level, or within a folder, e.g.: Fine: - /job/pipeline/directive-generator/ - /job/folder/job/pipeline/directive-generator/ 404: - /job/mb-pipeline/directive-generator/ - /job/folder/job/mb-pipeline/directive-generator/ Add Comment
[JIRA] (JENKINS-50881) Accessing the job config xml via the .../config.xml URL results in a XML Parsing Error
Title: Message Title Rich Duncan created an issue Jenkins / JENKINS-50881 Accessing the job config xml via the .../config.xml URL results in a XML Parsing Error Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-04-18 21:24 Environment: Jenkins 2.117 (out of the box configuration) Priority: Critical Reporter: Rich Duncan If a job has the URL http://host/job/jobName Browsing to the URL http://host/job/jobName/config.xml should show the job's configuration xml. Currently this results in the following error: XML Parsing Error: XML declaration not well-formed Location: http://localhost:8082/job/test/config.xml Line Number 1, Column 16: ---^ If the job was created by a recent version of Jenkins, for example 2.107 or later, the XML header will be:
[JIRA] (JENKINS-50190) Add option to not build dockerfile, if it already exists on the agent
Title: Message Title Christopher Orr closed an issue as Won't Do Jenkins / JENKINS-50190 Add option to not build dockerfile, if it already exists on the agent Change By: Christopher Orr Status: Open Closed 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. 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-50880) Create a new option for running when condition before stage input
Title: Message Title Erik Elkins updated an issue Jenkins / JENKINS-50880 Create a new option for running when condition before stage input Change By: Erik Elkins Summary: Create a new stage option for running when condition before stage input 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-50880) Create a new stage option for running when condition before stage input
Title: Message Title
Erik Elkins created an issue
Jenkins / JENKINS-50880
Create a new stage option for running when condition before stage input
Issue Type:
New Feature
Assignee:
Erik Elkins
Components:
pipeline-model-definition-plugin
Created:
2018-04-18 21:13
Priority:
Minor
Reporter:
Erik Elkins
Currently, when using the "stage-level" input (here: https://jenkins.io/doc/book/pipeline/syntax/#input) the when condition of the stage is evaluated after the input is gathered. We should add an option so the when condition is evaluated before the input is gathered. Something like:
stage('Production Deploy') {
agent { label 'linux' }
when {
branch "master"
beforeInput: true
}
input { message 'Deploy to Production?' }
steps {
echo 'Deploying to Production ... '
}
}
Use cases
Evaluate the when condition before the input has been gathered.
In scope
Declarative pipeline only
Only used for input at stage level https://jenkins.io/doc/book/pipeline/syntax/#input
[JIRA] (JENKINS-49309) All SSH slaves unexpectedly disconnect when one job finishes
Title: Message Title Dion Gonano commented on JENKINS-49309 Re: All SSH slaves unexpectedly disconnect when one job finishes Done, i'll let you know how it goes 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-50879) The secretVolume is not mounted to "jnlp" container in the multicontainer pod
Title: Message Title
Igor Kolomiyets created an issue
Jenkins / JENKINS-50879
The secretVolume is not mounted to "jnlp" container in the multicontainer pod
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-04-18 20:38
Environment:
Jenkins 2.117 Kubernetes Plugin 1.5.2 Kubernetes 1.9.5 or OpenShift 3.7.0 with Kubernetes 1.7.6
Priority:
Major
Reporter:
Igor Kolomiyets
The Kubernetes Plugin stopped mounting secret volumes to a "jnlp" container after plugin was upgraded to the version 1.5.2. The sample pod template definition:
podTemplate(label: 'jpod', cloud: 'OpenShift', serviceAccount: 'jenkins-sa',
containers: [
containerTemplate(name: 'java', image: 'openjdk:alpine', ttyEnabled: true, command: 'cat'),
containerTemplate(name: 'docker', image: 'docker:dind', ttyEnabled: true, command: 'cat', privileged: true,
envVars: [secretEnvVar(key: 'DOCKER_USERNAME', secretName: 'docker-hub-credentials', secretKey: 'username'),
]),
containerTemplate(name: 'kubectl', image: 'roffe/kubectl', ttyEnabled: true, command: 'cat'),
containerTemplate(name: 'sonarqube', image: 'iktech/sonarqube-scanner', ttyEnabled: true, command: 'cat'),
],
volumes: [
secretVolume(mountPath: '/etc/.ssh', secretName: 'ssh-home'),
secretVolume(mountPath: '/opt/sonar-scanner/conf', secretName: 'sonar-scanner.properties'),
secretVolume(secretName: 'docker-hub-credentials', mountPath: '/etc/.secret'),
hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock')
]
) {
.
[JIRA] (JENKINS-50315) Editable mode not offering selection once a selection has been made
Title: Message Title Serge Landry updated an issue Jenkins / JENKINS-50315 Editable mode not offering selection once a selection has been made Change By: Serge Landry The editable mode that now offers dynamic filtering as you type in the field has a user unfriendly issue.The dynamic filtering of the combo box items as you type is okay. But once an item has been selected, the "filtering state" of the combo box stays, resulting in having only the selected item displayed in the combo box. All selected items of the combo box should be displayed once a valid selection has been made, otherwise you need to clear out the field in order to have all your items displayed and selectable again.This is especially obvious when, for instance, you configure your Extensible Choice as Editable, with the Default Choice as the Top Most Value. The result is that your combo box is shown with the top most item, but with absolutely no way to make a selection, as if the combo box only had the top most item available. It took me quite a few minutes to realize that I had to clear the field, which is not the most user friendly or obvious way of interacting with the combo box. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49736) Remote ssh slave disconnection
Title: Message Title Chris Amis commented on JENKINS-49736 Re: Remote ssh slave disconnection I said earlier that the 1G connection made things better, after some time now with not another occurence I think it fixed it. I did not just change the switch, we stripped the whole lot down and rebuilt it in a new home, we check all cables were nice and snug and so on. My guess is that we must have had a bad connection and the jenkins SSH connection was really susceptible (remember that the tests would run the full 60 hours if I ran them from a cmd prompt on the jenkins machine). Chris 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-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Francois Aichelbaum commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel The ones prior to 12 December as this was the apparent last update without issue we did. The next one (for us) was beginning for January and things got even worse following the rush for Kernel updates, hardware firmware updates and even more with VMware patches. 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-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Francois Aichelbaum edited a comment on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel The ones prior to 12 December , 12th as this was the apparent last update without issue we did.The next one (for us) was beginning for January and things got even worse following the rush for Kernel updates, hardware firmware updates and even more with VMware patches. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Christian Höltje commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found I was able to be reproduced 100% until I made the system properties change. I'm afraid to clear that system properties because this is a production system that really can't afford anymore down time. It started as an intermediate thing, but became higher and higher probability until yesterday when it was 100%. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Christian Höltje edited a comment on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found I was able to be reproduced reproduce it 100% until I made the system properties change.I'm afraid to clear that system properties property because this is a production system that really can't afford anymore down time.It started as an intermediate thing, but became higher and higher probability until yesterday when it was 100%. 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-50872) Mapped drives are not accessible to "Execute Windows Batch Command"
Title: Message Title Benjamin Wagner commented on JENKINS-50872 Re: Mapped drives are not accessible to "Execute Windows Batch Command" I was able to fix this with the groovy console using println "net use z: [drive mapping]".execute().getText() But this still seems like it must be an issue 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-50878) Move 'Upstream Build' and 'Downstream job' on top of Maven report
Title: Message Title dan tran created an issue Jenkins / JENKINS-50878 Move 'Upstream Build' and 'Downstream job' on top of Maven report Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-04-18 20:04 Priority: Minor Reporter: dan tran I think those reports are much more interesting than the list of deploy artifacts since they are already in main page build Also, my list is too long, take me many clicks to scroll down to what want to see Add Comment
[JIRA] (JENKINS-50507) withMaven must not trigger its own project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50507 Re: withMaven must not trigger its own project Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/be091060674771772d073245f24805a01d52c4c9 Log: JENKINS-50507 If a pipeline consumes the artifacts it produces, then don't display the pipeline in the list of upstream builds or downstream pipelines. 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-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Vassilena Treneva commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Francois Aichelbaum, do you know which version of the server/ssh plugin does NOT have this issue? 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-50877) Add a way to cancel queued builds for deleted branches
Title: Message Title Sean Morse created an issue Jenkins / JENKINS-50877 Add a way to cancel queued builds for deleted branches Issue Type: Improvement Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-04-18 19:57 Priority: Minor Reporter: Sean Morse It would be nice to have the ability to set a behavior for when branches are deleted(Most our developers delete branches on merge from pull requests), all their associated build jobs currently queued are also deleted. Currently I've run into a number of cases where a build job was in the queue and when it came around to checkout the branch was no longer available so the build would fail creating unnecessary noise. Add Comment
[JIRA] (JENKINS-50876) Workspace Whitespace Replacement Plugin not working on Jenkins ver. 2.107.2
Title: Message Title Jason Meredith created an issue Jenkins / JENKINS-50876 Workspace Whitespace Replacement Plugin not working on Jenkins ver. 2.107.2 Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2018-04-18 19:54 Priority: Major Reporter: Jason Meredith Your plugin https://wiki.jenkins.io/display/JENKINS/Workspace+Whitespace+Replacement+Plugin no longer works. I am using jenkins version 2.107.2. Plugin is installed however new projects and existing projects all have spaces in their workspace directory name. Add Comment
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Francois Aichelbaum commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel As said on the other thread, we already went through those that you can find on Internet and they solved nothing as it was working before a change in the 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-50875) multiple jobDSL() pipeline steps clobber each other.
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-50875 multiple jobDSL() pipeline steps clobber each other. Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-04-18 19:48 Environment: Jenkins 2.89.4 ace-editor-1.1 ansicolor-0.5.2 ant-1.8 antisamy-markup-formatter-1.5 apache-httpcomponents-client-4-api-4.5.3-2.1 artifactory-2.15.1 authentication-tokens-1.3 badge-1.2 blueocean-1.4.2 blueocean-autofavorite-1.2.2 blueocean-bitbucket-pipeline-1.4.2 blueocean-commons-1.4.2 blueocean-config-1.4.2 blueocean-core-js-1.4.2 blueocean-dashboard-1.4.2 blueocean-display-url-2.2.0 blueocean-events-1.4.2 blueocean-git-pipeline-1.4.2 blueocean-github-pipeline-1.4.2 blueocean-i18n-1.4.2 blueocean-jira-1.4.2 blueocean-jwt-1.4.2 blueocean-personalization-1.4.2 blueocean-pipeline-api-impl-1.4.2 blueocean-pipeline-editor-1.4.2 blueocean-pipeline-scm-api-1.4.2 blueocean-rest-1.4.2 blueocean-rest-impl-1.4.2 blueocean-web-1.4.2 bouncycastle-api-2.16.2 branch-api-2.0.18 build-keeper-plugin-1.3 build-pipeline-plugin-1.5.8 buildtriggerbadge-2.9 cli-commander-0.3 cloudbees-bitbucket-branch-source-2.2.10 cloudbees-folder-6.4 command-launcher-1.2 conditional-buildstep-1.3.6 config-file-provider-2.18 copyartifact-1.39.1 credentials-2.1.16 credentials-binding-1.16 cucumber-reports-3.15.0 cvs-2.14 display-url-api-2.2.0 docker-commons-1.11 docker-java-api-3.0.14 docker-plugin-1.1.3 docker-workflow-1.15.1 durable-task-1.22 email-ext-2.62 extended-read-permission-2.0 extensible-choice-parameter-1.5.0 external-monitor-job-1.7 favorite-2.3.1 ghprb-1.40.0 git-3.8.0 git-client-2.7.1 git-server-1.7 github-1.29.0 github-api-1.90 github-branch-source-2.3.3 github-oauth-0.29 gradle-1.28 groovy-postbuild-2.4 handlebars-1.1.1 handy-uri-templates-2-api-2.1.6-1.0 htmlpublisher-1.15 http_request-1.8.22 ibm-ucdeploy-publisher-1.2.7 icon-shim-2.0.3 ivy-1.28 jackson2-api-2.8.11.1 jacoco-3.0.1 javadoc-1.4 jenkins-design-language-1.4.2 jira-2.5 job-dsl-1.68 jobConfigHistory-2.18 jquery-1.12.4-0 jquery-detached-1.2.1 jsch-0.1.54.2 junit-1.24 kubernetes-1.5 kubernetes-credentials-0.3.1 label-linked-jobs-5.1.2 ldap-1.20 lockable-resources-2.2 mailer-1.21 mapdb-api-1.0.9.0 mask-passwords-2.11.0 matrix-auth-2.2 matrix-project-1.12 maven-plugin-3.1.2 mercurial-2.3 metrics-3.1.2.11 momentjs-1.1.1 monitoring-1.71.0 next-build-number-1.5 pam-auth-1.3 parameterized-trigger-2.35.2 pegdown-formatter-1.3 performance-3.6 pipeline-build-step-2.7 pipeline-github-lib-1.0 pipeline-graph-analysis-1.6
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Sam Van Oort commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Georg Henzler Executors have nothing to do with this, and this issue is generally within the scope of a single build, so limiting the maximum number should have no impact – except when restarting Jenkins, where there might be enough of a bottleneck due to loading FlowExecutions to hit the 1 minute timeout. Maybe if you had maybe 10x as many Pipelines as CPU cores on the master, or really complex Program state – in this case we'd be blocking on the code here: https://github.com/jenkinsci/workflow-job-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java#L1024 Do you have a message like this in your logs? WARNING, failed to wait for $someRun to be loaded (and then a stack trace). More likely there's something subtly wrong with the concurrency/error-handling model here – some of what I'm doing right now to untangle some nasty issues in these guts may help – and there was a change in the last release of workflow-cps that might help if you don't have it already (it caught more exceptions and prevented threads from potentially waiting forever). 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-50874) When access to gitlab URL fails, log the URL used
Title: Message Title Pawel Veselov created an issue Jenkins / JENKINS-50874 When access to gitlab URL fails, log the URL used Issue Type: Improvement Assignee: Mohamed El Habib Components: gitlab-oauth-plugin Created: 2018-04-18 19:34 Priority: Minor Reporter: Pawel Veselov I'm getting problems authenticating against our gitlab. I get an SSL exception from Java. Though I assume Java fails to access some of the gitlab URLs, I would like to know which one, as there shouldn't be any certificate related problems. So, if the plugin could catch the exception, and re-wrap it with the URL that failed to load, it would be great. Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1959) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1514) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026) at sun.security.ssl.Handshaker.process_record(Handshaker.java:961) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1072) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397) at
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found Can this be reproduced? From the description it is not clear if this happens every time. Also, the XML 1.1 change was not introduced until Jenkins 2.105 and it appears this is being reported for jenkins 2.89. 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-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Those are overall recommendations, check it your Agents satisfy those recommendations, they resolve the 90% of Agents issues 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli updated an issue Jenkins / JENKINS-50867 SAX2 driver class org.apache.xerces.parsers.SAXParser not found Change By: mike cirioli Comment: thanks for the heads up [~oleg_nenashev] - i will take a look into this tonight 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-49309) All SSH slaves unexpectedly disconnect when one job finishes
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-49309 Re: All SSH slaves unexpectedly disconnect when one job finishes try to set the JVM options to -Xmx512m -Xms512m and increase the executors, I think that the slave.jar process launches an Out Of memory error. 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-50873) When a test method is named `owner`, test results can't be viewed
Title: Message Title Rahul Somasunderam created an issue Jenkins / JENKINS-50873 When a test method is named `owner`, test results can't be viewed Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2018-04-18 19:15 Priority: Minor Reporter: Rahul Somasunderam Clicking on the test method causes a redirect to the build home. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Francois Aichelbaum commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Hi Ivan I'm curious why your pinpointing in the various thread regarding this issue that we all need to review our TCP stack optimization whereas it used to work and stop after some update of either your code or the Linux kernel As it also impacts Windows and Mac OS machines, I guess the culprit might not be the kernel or the TCP stack optim. 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-50872) Mapped drives are not accessible to "Execute Windows Batch Command"
Title: Message Title
Benjamin Wagner updated an issue
Jenkins / JENKINS-50872
Mapped drives are not accessible to "Execute Windows Batch Command"
Change By:
Benjamin Wagner
This issue is specific to "Execute Windows batch command" build step in Jenkins Core.The slave machine has a given drive ( [ Z: ) ] mapped.On my windows 7 slaves, I can use the mapped drive in this without issue.On windows 10, I am told:The system cannot find the drive specifiedIn an attempt to work around this, I have attempted to use "net use" to list the mapped drives available through this Jenkins job, and have also attempted to use "net use" to map the drive.To do this, I have set my Windows Batch Command to the following:{code:java}net usenet use z: [Drive mapping] /P:Yes{code}Executing the job at this point gives me the following incredibly confusing console output:{code:java}c:\workspace\Pull Jobs test\label\SSW106416>net use New connections will be remembered.There are no entries in the list.c:\workspace\Pull Jobs test\label\SSW106416>net use z: \\[Drive mapping] /P:Yes z: has a remembered connection to \\[Drive mapping]. Do youwant to overwrite the remembered connection? (Y/N) [Y]: No valid response was provided.{code} I have also had the job execute "whoami" to confirm that I am using a properly authorized user to execute the batch commands. Am I missing something here? These all work locally on the slave, but however jenkins runs these batch commands seems to break it.
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-50872) Mapped drives are not accessible to "Execute Windows Batch Command"
Title: Message Title Benjamin Wagner created an issue Jenkins / JENKINS-50872 Mapped drives are not accessible to "Execute Windows Batch Command" Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-04-18 19:10 Environment: Windows 7 - 64 bit Java(TM) SE Runtime Environment (build 1.8.0_161-b12) Jenkins version 2.107.2 Problem is with a Slave running Windows 10 - 64 bit connected via command line (javaws [Path]/slave-agent.jnlp) org.jenkins-ci.main:jenkins-war:2.107.2 org.jenkins-ci:crypto-util:1.1 commons-httpclient:commons-httpclient:3.1-jenkins-1 aopalliance:aopalliance:1.0 org.kohsuke.stapler:stapler-jelly:1.254 com.google.inject:guice:4.0 org.jenkins-ci.modules:slave-installer:1.6 org.springframework:spring-dao:1.2.9 org.jenkins-ci.modules:instance-identity:2.1 org.jenkins-ci:constant-pool-scanner:1.2 org.connectbot.jbcrypt:jbcrypt:1.0.0 org.jenkins-ci.modules:ssh-cli-auth:1.4 org.ow2.asm:asm-commons:5.0.3 org.jenkins-ci:symbol-annotation:1.1 com.github.jnr:jnr-constants:0.9.8 org.jenkins-ci.modules:windows-slave-installer:1.9.2 commons-digester:commons-digester:2.1 org.jenkins-ci:winstone:4.1.2 commons-io:commons-io:2.4 org.kohsuke:trilead-putty-extension:1.2 commons-codec:commons-codec:1.9 net.sf.kxml:kxml2:2.3.0 org.kohsuke:libzfs:0.8 org.jenkins-ci.ui:jquery-detached:1.2 org.kohsuke.stapler:json-lib:2.4-jenkins-2 org.jvnet.robust-http-client:robust-http-client:1.2 org.ow2.asm:asm:5.0.3 net.java.sezpoz:sezpoz:1.12 org.kohsuke.stapler:stapler-adjunct-timeline:1.5 org.slf4j:log4j-over-slf4j:1.7.25 org.jenkins-ci:version-number:1.4 org.codehaus.groovy:groovy-all:2.4.11 org.jvnet.hudson:commons-jelly-tags-define:1.0.1-hudson-20071021 org.jenkins-ci:jmdns:3.4.0-jenkins-3 commons-lang:commons-lang:2.6 org.springframework:spring-jdbc:1.2.9 org.codehaus.woodstox:wstx-asl:3.2.9 org.jenkins-ci.main:jenkins-core:2.107.2 org.springframework:spring-core:2.5.6.SEC03 org.springframework:spring-aop:2.5.6.SEC03 org.samba.jcifs:jcifs:1.3.17-kohsuke-1 org.jenkins-ci:bytecode-compatibility-transformer:1.8 org.jenkins-ci.main:remoting:3.17 org.apache.ant:ant:1.9.2 com.sun.solaris:embedded_su4j:1.1 org.jenkins-ci.main:cli:2.107.2 javax.inject:javax.inject:1 org.jenkins-ci.modules:upstart-slave-installer:1.1 org.apache.commons:commons-compress:1.10 commons-beanutils:commons-beanutils:1.8.3 org.jvnet.localizer:localizer:1.24 org.fusesource.jansi:jansi:1.11 org.jenkins-ci.modules:sshd:2.4 org.springframework:spring-beans:2.5.6.SEC03 javax.xml.stream:stax-api:1.0-2 org.slf4j:slf4j-jdk14:1.7.25 org.jvnet.hudson:activation:1.1.1-hudson-1
[JIRA] (JENKINS-50852) Maven report: remove duplicate dependencies list
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-50852 Maven report: remove duplicate dependencies list Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-49309) All SSH slaves unexpectedly disconnect when one job finishes
Title: Message Title Dion Gonano commented on JENKINS-49309 Re: All SSH slaves unexpectedly disconnect when one job finishes I've been running it with one executor for a while now with no disconnection issues 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-49309) All SSH slaves unexpectedly disconnect when one job finishes
Title: Message Title Dion Gonano commented on JENKINS-49309 Re: All SSH slaves unexpectedly disconnect when one job finishes slave configuration vagrant /media/disk1/jenkins/ 1 NORMAL "hudson.slaves.RetentionStrategy$Always"/> "hudson.plugins.sshslaves.SSHLauncher" plugin="ssh-slaves@1.24"> 192.168.11.10 22 vagrant 0 0 "hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy"> false vagrant-slave 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-49309) All SSH slaves unexpectedly disconnect when one job finishes
Title: Message Title Dion Gonano commented on JENKINS-49309 Re: All SSH slaves unexpectedly disconnect when one job finishes If Xms and Xmx are the java memory parameters i haven't configured anything. I thought Jenkins ssh'd in and started the slave JVM with the correct params. 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-49309) All SSH slaves unexpectedly disconnect when one job finishes
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-49309 Re: All SSH slaves unexpectedly disconnect when one job finishes the config.xml of the Agent is returned by the JENKINS_URL/computer/NAME_OF_AGENT/config.xml https://stackoverflow.com/questions/14763079/what-are-the-xms-and-xmx-parameters-when-starting-jvms 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-49309) All SSH slaves unexpectedly disconnect when one job finishes
Title: Message Title Dion Gonano edited a comment on JENKINS-49309 Re: All SSH slaves unexpectedly disconnect when one job finishes [~ifernandezcalvo] Can you be more specific about which config or how to get it? I attached a pic of the slave config page in jenkins .what is the Xmx and Xms? 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-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50327 Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest Could you attach also the configuration of backend and frontend on nginx? replace IP/names with 192.168.1.X/svn.example.com 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-49309) All SSH slaves unexpectedly disconnect when one job finishes
Title: Message Title Dion Gonano commented on JENKINS-49309 Re: All SSH slaves unexpectedly disconnect when one job finishes Ivan Fernandez Calvo Can you be more specific about which config or how to get it? I attached a pic of the slave config page in jenkins 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-50852) Maven report: remove duplicate dependencies list
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50852 Re: Maven report: remove duplicate dependencies list Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/13799d43290fd7a8beee5164d8dcc7f6701cfd5c Log: Merge pull request #144 from jenkinsci/JENKINS-50852 JENKINS-50852 Deduplicate pipeline build dependencies list Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/3e2ec160f600...13799d43290f 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found thanks for the heads up Oleg Nenashev - i will take a look into this tonight 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Georg Henzler commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException We also had this problem again today... reading Jesse Glick's comment in https://issues.jenkins-ci.org/browse/JENKINS-35710?focusedCommentId=268398=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-268398 I suspect adding more slaves does not help (as the stacktrace clearly points to CPS, and according the comment that always runs on master)... but I suppose using https://github.com/jenkinsci/throttle-concurrent-builds-plugin to ensure only a maximum of builds run in parallel globally could help. Sam Van Oort before trying, do you think this is a valid way of getting rid of the problem? (asking before trying as this is not easy to 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-19465) Slave hangs while being launched
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-19465 Re: Slave hangs while being launched It is recommended to use JDK nearest and in the same major version of Jenkins instance and Agents It is recommended to tune the TCP stack on of Jenkins instance and Agents On Linux http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/usingkeepalive.html On Windows https://blogs.technet.microsoft.com/nettracer/2010/06/03/things-that-you-may-want-to-know-about-tcp-keepalives/ On Mac https://www.gnugk.org/keepalive.html You should check for hs_err_pid error files in the root fs of the agent http://www.oracle.com/technetwork/java/javase/felog-138657.html#gbwcy Check the logs in the root fs of the agent It is recommended to set the initial heap of the Agent to at least 512M (-Xmx512m -Xms512m), you could start with 512m and lower the value until you find a proper value to your Agents. Disable energy save options that suspend, or hibernate the host Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-19465) Slave hangs while being launched
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-19465 Re: Slave hangs while being launched Overall recommendations: * It is recommended to use JDK nearest and in the same major version of Jenkins instance and Agents* It is recommended to tune the TCP stack on of Jenkins instance and Agents** On Linux http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/usingkeepalive.html** On Windows https://blogs.technet.microsoft.com/nettracer/2010/06/03/things-that-you-may-want-to-know-about-tcp-keepalives/** On Mac https://www.gnugk.org/keepalive.html* You should check for hs_err_pid error files in the root fs of the agent http://www.oracle.com/technetwork/java/javase/felog-138657.html#gbwcy* Check the logs in the root fs of the agent* It is recommended to set the initial heap of the Agent to at least 512M (-Xmx512m -Xms512m), you could start with 512m and lower the value until you find a proper value to your Agents.* Disable energy save options that suspend, or hibernate the host 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-50853) Windows JNLP slave permissions errors, works manually via RDP cmd
Title: Message Title
Antony Gelberg updated an issue
Jenkins / JENKINS-50853
Windows JNLP slave permissions errors, works manually via RDP cmd
Change By:
Antony Gelberg
We can bring up a slave and connect successfully:{{Apr 17, 2018 11:55:18 PM null }}\{\{FINER: Node windows-server-2012 (i-09233a1df87ee74c0)(i-09233a1df87ee74c0) is ready windows-server-2012 (i-09233a1df87ee74c0) booted at 1523569187000 Connecting to ip-172-16-2-40.ec2.internal(172.16.2.40) with WinRM as Administrator Connected with WinRM. Creating tmp directory if it does not exist slave.jar sent remotely. Bootstrapping it <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.17 This is a Windows agent Agent successfully connected and online}}But there is a difference between running commands from the RDP desktop as Administrator, and from the slave connected via JNLP (which also seems to be Administrator, according to the output of `whoami`).Running commands from RDP:{{C:\Windows\system32>whoami}} {{win-4iqcddh05vj\administrator}}{{C:\Windows\system32>psexec}} {{web.sandbox.MUNGED.com iisreset /restart}} {{PsExec v2.2 - Execute processes remotely}} {{Copyright (C) 2001-2016 Mark Russinovich}} {{Sysinternals - www.sysinternals.com}} {{Attempting stop...}} {{Internet services successfully stopped}} {{Attempting start...}} {{Internet services successfully restarted}} {{iisreset exited on web.sandbox.MUNGED.com with error code 0.}} However, running the following code from the same server, via JNLP / Pipeline, results in a `handle is invalid` error:{{environment \{}} {{ SERVER = 'web.sandbox.MUNGED.com'}} {{}}} {{steps \{}} {{ bat "whoami"}} {{ bat "psexec $\{SERVER} iisreset /restart"}} {{}}} Results in:{{00:19:24 [control-pipeline] Running batch script}} \{\{00:19:28 }} {{00:19:28 c:\jenkins\workspace\control-pipeline>whoami}} {{00:19:28 win-4iqcddh05vj\administrator}} {{[Pipeline] bat}} {{00:19:34 [control-pipeline] Running batch script}} \{\{00:19:38 }} \{\{00:19:38 c:\jenkins\workspace\control-pipeline>psexec web.sandbox.MUNGED.com iisreset /restart }} \{\{00:19:38 }} {{00:19:38 PsExec v2.2 - Execute processes remotely}} {{00:19:38 Copyright (C) 2001-2016 Mark Russinovich}} {{00:19:38 Sysinternals - www.sysinternals.com}} \{\{00:19:38 }} {{00:19:38 The handle is invalid.}} {{00:19:38 Connecting to web.sandbox.MUNGED.com...}} {{Couldn't access web.sandbox.MUNGED.com:}} {{00:19:40 Connecting to web.sandbox.MUNGED.com...}} We also see different behaviour between the two when running Powershell steps, but I left those out of here due to the convoluted nature of Powershell configuration. I'm sure it's the same root cause. Please let me know what extra information I can provide to help debug this. I set to Major as I don't see a workaround. Edit: I finally found a difference between (note the arrow). RDP: {{C:\Windows\system32>query session}}{{ SESSIONNAME USERNAME ID STATE TYPE DEVICE}}{{ services 0 Disc}}{{ console 1 Conn}}{{>rdp-tcp#12 Administrator 2 Active}}{{ rdp-tcp 65536 Listen}}And Jenkins JNLP:{{18:18:16
[JIRA] (JENKINS-49193) Failed known_hosts verification for SSH agent
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-49193 Re: Failed known_hosts verification for SSH agent Did you imported the public key of the Agent in ~/.ssh/known_hosts? 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-50853) Windows JNLP slave permissions errors, works manually via RDP cmd
Title: Message Title
Antony Gelberg updated an issue
Jenkins / JENKINS-50853
Windows JNLP slave permissions errors, works manually via RDP cmd
Change By:
Antony Gelberg
We can bring up a slave and connect successfully:{{Apr 17, 2018 11:55:18 PM null }}\{\{FINER: Node windows-server-2012 (i-09233a1df87ee74c0)(i-09233a1df87ee74c0) is ready windows-server-2012 (i-09233a1df87ee74c0) booted at 1523569187000 Connecting to ip-172-16-2-40.ec2.internal(172.16.2.40) with WinRM as Administrator Connected with WinRM. Creating tmp directory if it does not exist slave.jar sent remotely. Bootstrapping it <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.17 This is a Windows agent Agent successfully connected and online}}But there is a difference between running commands from the RDP desktop as Administrator, and from the slave connected via JNLP (which also seems to be Administrator, according to the output of `whoami`).Running commands from RDP:{{C:\Windows\system32>whoami}} {{win-4iqcddh05vj\administrator}}{{C:\Windows\system32>psexec}}{{web.sandbox.MUNGED.com iisreset /restart}}{{PsExec v2.2 - Execute processes remotely}}{{Copyright (C) 2001-2016 Mark Russinovich}}{{Sysinternals - www.sysinternals.com}}{{Attempting stop...}}{{Internet services successfully stopped}}{{Attempting start...}}{{Internet services successfully restarted}}{{iisreset exited on web.sandbox.MUNGED.com with error code 0.}} However, running the following code from the same server, via JNLP / Pipeline, results in a `handle is invalid` error:{{environment \{}}{{ SERVER = 'web.sandbox.MUNGED.com'}}{{}}}{{steps \{}}{{ bat "whoami"}}{{ bat "psexec $\{SERVER} iisreset /restart"}}{{}}} Results in:{{00:19:24 [control-pipeline] Running batch script}} \{\{00:19:28 }} {{00:19:28 c:\jenkins\workspace\control-pipeline>whoami}} {{00:19:28 win-4iqcddh05vj\administrator}} {{[Pipeline] bat}} {{00:19:34 [control-pipeline] Running batch script}} \{\{00:19:38 }} \{\{00:19:38 c:\jenkins\workspace\control-pipeline>psexec web.sandbox.MUNGED.com iisreset /restart }} \{\{00:19:38 }} {{00:19:38 PsExec v2.2 - Execute processes remotely}} {{00:19:38 Copyright (C) 2001-2016 Mark Russinovich}} {{00:19:38 Sysinternals - www.sysinternals.com}} \{\{00:19:38 }} {{00:19:38 The handle is invalid.}} {{00:19:38 Connecting to web.sandbox.MUNGED.com...}} {{Couldn't access web.sandbox.MUNGED.com:}} {{00:19:40 Connecting to web.sandbox.MUNGED.com...}} We also see different behaviour between the two when running Powershell steps, but I left those out of here due to the convoluted nature of Powershell configuration. I'm sure it's the same root cause. Please let me know what extra information I can provide to help debug this. I set to Major as I don't see a workaround. Edit: I finally found a difference between RDP:
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Sam Van Oort started work on JENKINS-46507 Change By: Sam Van Oort 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-49309) All SSH slaves unexpectedly disconnect when one job finishes
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-49309 Re: All SSH slaves unexpectedly disconnect when one job finishes Connection to 127.0.0.1 closed by remote host. The loopback device, Could you attach the config file of this Agent? Is it running on the same Jenkins instance? Did you set the Xmx and Xms JVM parameters? 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Jarrett B commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException +1 Same here 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-50638
Re: windows agent via SSH - Slave JVM has terminated. Exit code
I think that I know what happens, clean up the suffix and prefix field and put exactly this one in the prefix field {code}/bin/bash -c "cd "/cygdrive/d/CI/jenkins-ssh" && java -Djava.util.logging.config.file=/cygdrive/d/CI/jenkins-ssh/logging.properties -jar slave.jar";{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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code I think that I know what happens, clean up the suffix and prefix field and put exactly this one /bin/bash -c "cd "/cygdrive/d/CI/jenkins-ssh" && java -Djava.util.logging.config.file=/cygdrive/d/CI/jenkins-ssh/logging.properties -jar slave.jar"; 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-50864) kubernetes-cli-plugin is not working.
Title: Message Title Max Laverse started work on JENKINS-50864 Change By: Max Laverse 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-50864) kubernetes-cli-plugin is not working.
Title: Message Title Max Laverse stopped work on JENKINS-50864 Change By: Max Laverse 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-50864) kubernetes-cli-plugin is not working.
Title: Message Title Max Laverse assigned an issue to Sunil Chauraha Jenkins / JENKINS-50864 kubernetes-cli-plugin is not working. Change By: Max Laverse Assignee: Max Laverse Sunil Chauraha 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-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc commented on JENKINS-50507 Re: withMaven must not trigger its own project > will see the fix for the visualisation glitch soon? less things to be confused I hope so, it's not very complex to solve. 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-50852) Maven report: remove duplicate dependencies list
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50852 Re: Maven report: remove duplicate dependencies list Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/22b28c4a7732f34d5d8c89d728999a4db6aa91b4 Log: JENKINS-50852 Deduplicate pipeline build dependencies list 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-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Overall recommendations: It is recommended to use JDK nearest and in the same major version of Jenkins instance and Agents It is recommended to tune the TCP stack on of Jenkins instance and Agents On Linux http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/usingkeepalive.html On Windows https://blogs.technet.microsoft.com/nettracer/2010/06/03/things-that-you-may-want-to-know-about-tcp-keepalives/ On Mac https://www.gnugk.org/keepalive.html You should check for hs_err_pid error files in the root fs of the agent http://www.oracle.com/technetwork/java/javase/felog-138657.html#gbwcy It is recommended to set the initial heap of the Agent to at least 512M (-Xmx512m -Xms512m), you could start with 512m and lower the value until you find a proper value to your Agents. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-50616 Re: JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Summary of the review: https://github.com/jenkinsci/ruby-runtime-plugin is an obsolete repository. At some point the code has been moved to https://github.com/jenkinsci/jenkins.rb/blob/master/java-runtime , and currently there is a split-brain between repositories Although we have proposed fixes, both me and Jesse Glick failed to quickly setup environment for jenkins.rb fix and release We have contacted the maintainer of jenkins.rb to get his help with these fixes Jesse Glick What would you say if we add this particular whitelist entry to the core? It should not make the things much worse since we whitelist other entries there. 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-49118) SSH Slaves 1.25 Breaks
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-49118 Re: SSH Slaves 1.25 Breaks What JDK version you use on the Jenkins instance and on the Agents? It is recommended to use nearest, and in the same major version 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-49736) Remote ssh slave disconnection
Title: Message Title Francois Aichelbaum commented on JENKINS-49736 Re: Remote ssh slave disconnection Hi Ivan Fernandez Calvo On our side, we have the very exact same issues since beginning of January and kernel patches for Spectre/Meltdown. Sysctl on Jenkins (core) and the various slaves) have been tweaked multiple times without luck. Your figures are not the best for our setup and the number of jobs we run, but though, did not help either when we used such (those values are very conservative but are not of the best use in production environments with high load. Cheers 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Oleg Nenashev commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found CC mike cirioli. It may be related to the XML 1.1 migration which changed drivers in XStream 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-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest
Title: Message Title Richard van der Klooster commented on JENKINS-50327 Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest Apache 2.4.7. I see we have nginx in front of it. DAV svn SVNParentPath /var/lib/svn/repos #Here we define repository based auth settings file AuthzSVNAccessFile authfile # (removed actual filename) 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-50009) SSH connection reports a garbage before a command execution
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50009 Re: SSH connection reports a garbage before a command execution Authentication successful. SSH connection reports a garbage before a command execution. Check your .bashrc, .profile, and so on to make sure it is quiet. try with clean .bashrc and .profile files, it should be some command inside then that breaks the connection 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-49736) Remote ssh slave disconnection
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-49736 Re: Remote ssh slave disconnection Did you try to tune the keepalive int the TCP stack? the default values are terrible sysctl -w net.ipv4.tcp_keepalive_time=120 sysctl -w net.ipv4.tcp_keepalive_intvl=30 sysctl -w net.ipv4.tcp_keepalive_probes=8 sysctl -w net.ipv4.tcp_fin_timeout=30 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-50765) Harden support-core against XXE attacks
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50765 Re: Harden support-core against XXE attacks Code changed in jenkins User: Devin Nusbaum Path: src/main/java/com/cloudbees/jenkins/support/configfiles/SecretHandler.java src/test/java/com/cloudbees/jenkins/support/configfiles/SecretHandlerTest.java http://jenkins-ci.org/commit/support-core-plugin/59261ba0355b403f42e6a8f205f87a6d5758d3d9 Log: Merge pull request #141 from dwnusbaum/harden-against-xxe JENKINS-50765 Defend SecretHandler from XXE attacks Compare: https://github.com/jenkinsci/support-core-plugin/compare/132c99f32b29...59261ba0355b 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Could you try the other one? because seems like the slave.jar process die || echo "KO - retcode $?" 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.
