[JIRA] (JENKINS-50640) Link messages together
Title: Message Title Srivardhan Hebbar assigned an issue to Out conn Jenkins / JENKINS-50640 Link messages together Change By: Srivardhan Hebbar Assignee: Srivardhan Hebbar Out conn 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-47001) Creation of "Skip" button I can catch to skip stages
Title: Message Title suren pi commented on JENKINS-47001 Re: Creation of "Skip" button I can catch to skip stages Andrew Bayer That's great if pipeline has the ability. 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-50654) cannot configure rebuildOpenMergeRequest using job-dsl
Title: Message Title
Nicos Maris created an issue
Jenkins / JENKINS-50654
cannot configure rebuildOpenMergeRequest using job-dsl
Issue Type:
Bug
Assignee:
Owen Mehegan
Components:
gitlab-plugin, job-dsl-plugin
Created:
2018-04-09 00:57
Priority:
Minor
Reporter:
Nicos Maris
triggers/gitlabPush/rebuildOpenMergeRequest('both') but the created job has value 'never'. Tested at the current latest jenkins (with latest plugins) and gitlab.
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-50378) Nodejs plugin should allow to force 32bit architecture
Title: Message Title
Philip Peitsch commented on JENKINS-50378
Re: Nodejs plugin should allow to force 32bit architecture
Just in case people weren't aware, you can also force 64 bit node to build 32 bit packages by using the "arch" and "target_arch" flags on npm. For example, part of my build looks like:
stage('Windows x86') {
agent { label 'win-vs2017' }
tools { nodejs 'NodeJS 8.9.4' }
environment {
npm_config_arch = "ia32"
npm_config_target_arch = "ia32"
}
steps {
bat "npm install"
archiveArtifacts '*.zip, *.msi'
}
}
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-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue.1. There is a "branch" build of the "branch" job running2. While its running a pull request is opened for that branch.3. Multibranch scanning gets triggered.4. The PR gets a "PR" project and a "PR" build starts running.(5. I guess the Multibranch scanning has to be triggered again.)6. Now the "branch" project gets disabled while the "branch" job is still running.The "branch" build will now never update its status to Bitbucket.This is a major issue, since the developer cannot merge its PR due to a running job.I found out that this line is the problem when updating the status at the end of the job:https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in:https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.javaI create a workaround for us since this was a blocker:https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/ commit tree / 26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8 JENKINS-45643 If there will be now "quickfix" I guess at least the description in the job config should be updated to pointing to this issue so it is clear to a new user choosing this option that he will face this race condition. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Taylor Patton commented on JENKINS-50557 Re: GCR Credentials Plugin does not work Are you sure you have both "Google OAuth Credentials plugin" and "Google Container Registry Auth Plugin" installed? Also make sure that your actual jenkins credential ID is not prepended with "gcr:". Those were my 2 mistakes 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-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue.1. There is a "branch" build of the "branch" job running2. While its running a pull request is opened for that branch.3. Multibranch scanning gets triggered.4. The PR gets a "PR" project and a "PR" build starts running.(5. I guess the Multibranch scanning has to be triggered again.)6. Now the "branch" project gets disabled while the "branch" job is still running.The "branch" build will now never update its status to Bitbucket.This is a major issue, since the developer cannot merge its PR due to a running job.I found out that this line is the problem when updating the status at the end of the job:https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in:https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.javaI create a workaround for us since this was a blocker:https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8 What already would help is to update the description in the job config pointing to this issue so it is clear to a new user choosing this option that he will face this race condition. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue.1. There is a "branch" build of the "branch" job running2. While its running a pull request is opened for that branch.3. Multibranch scanning gets triggered.4. The PR gets a "PR" project and a "PR" build starts running.(5. I guess the Multibranch scanning has to be triggered again.)6. Now the "branch" project gets disabled while the "branch" job is still running.The "branch" build will now never update its status to Bitbucket.This is a major issue, since the developer cannot merge its PR due to a running job.I found out that this line is the problem when updating the status at the end of the job:https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in:https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.javaI create a workaround for us since this was a blocker:https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8 What already would help is to update If ther will be now "quickfix" I guess at least the description in the job config should be updated to pointing to this issue so it is clear to a new user choosing this option that he will face this race condition. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue.1. There is a "branch" build of the "branch" job running2. While its running a pull request is opened for that branch.3. Multibranch scanning gets triggered.4. The PR gets a "PR" project and a "PR" build starts running.(5. I guess the Multibranch scanning has to be triggered again.)6. Now the "branch" project gets disabled while the "branch" job is still running.The "branch" build will now never update its status to Bitbucket.This is a major issue, since the developer cannot merge its PR due to a running job.I found out that this line is the problem when updating the status at the end of the job:https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in:https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.javaI create a workaround for us since this was a blocker:https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8If ther there will be now "quickfix" I guess at least the description in the job config should be updated to pointing to this issue so it is clear to a new user choosing this option that he will face this race condition. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Łukasz Jąder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Łukasz Jąder Component/s: ssh-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Benjamin Fuchs commented on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress We are also having a problem with this issue. 1. There is a "branch" build of the "branch" job running 2. While its running a pull request is opened for that branch. 3. Multibranch scanning gets triggered. 4. The PR gets a "PR" project and a "PR" build starts running. (5. I guess the Multibranch scanning has to be triggered again.) 6. Now the "branch" project gets disabled while the "branch" job is still running. The "branch" build will now never update its status to Bitbucket. This is a major issue, since the developer cannot merge its PR due to a running job. I found out that this line is the problem when updating the status at the end of the job: https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/3412b4eb5b35b9ade7a4e6cfafcdbf3375789fcb/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L101 s is of type NullSCMSource and I guess it is due to the branch being removed from "sources" in: https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.java I create a workaround for us since this was a blocker: https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/26b9f6ace3745cdd58ae1d43eb05d7eb3108f8f8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-46172) error when I change ssh server settings for authorization
Title: Message Title Łukasz Jąder resolved as Fixed This has been fixed with 2.6 version by saving SSH sites only when they have at least hostname and credentials selected. (the NPE exception handling was also improved) Jenkins / JENKINS-46172 error when I change ssh server settings for authorization Change By: Łukasz Jąder Status: In Progress 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
[JIRA] (JENKINS-10128) SSH Plugin: NullPointerException when no SSH site is specified in the job configuration
Title: Message Title Łukasz Jąder resolved as Fixed This has been fixed with 2.6 version by setting build to UNSTABLE when no SSH site is configured. Jenkins / JENKINS-10128 SSH Plugin: NullPointerException when no SSH site is specified in the job configuration Change By: Łukasz Jąder Status: In Progress 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
[JIRA] (JENKINS-25910) Nodes are not sorted on label overview page
Title: Message Title Daniel Beck updated JENKINS-25910 Merged towards 2.115. Jenkins / JENKINS-25910 Nodes are not sorted on label overview page Change By: Daniel Beck 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-50296) ThreadPools for remoting should run as SYSTEM user
Title: Message Title Daniel Beck updated JENKINS-50296 Merged towards 2.115. Jenkins / JENKINS-50296 ThreadPools for remoting should run as SYSTEM user Change By: Daniel Beck 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-50653) Gerrit trigger: time out event processing if it takes too long
Title: Message Title Sam Gruber created an issue Jenkins / JENKINS-50653 Gerrit trigger: time out event processing if it takes too long Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 2018-04-08 22:01 Priority: Minor Reporter: Sam Gruber We recently ran into an issue where the comment regex configured in our jobs could in some cases take an extremely long time to evaluate, which would end up blocking all of the event processing threads. It have been easier to track down this issue if there was a time out on event processing, and we could see those failures in the log, instead of the current behavior which is that the triggers silently stop working. Add Comment
[JIRA] (JENKINS-37996) Trend Graphs are not showing in Jenkins Pipeline job
Title: Message Title
Cyrille Le Clerc commented on JENKINS-37996
Re: Trend Graphs are not showing in Jenkins Pipeline job
Joy Sarkar Did you consider using the Pipeline Maven plugin? "withMaven() {...}" would automatically capture the JUnit reports in addition to other reports (FindBugs...). It would aslo be capable of triggering downstream jobs...
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-37996) Trend Graphs are not showing in Jenkins Pipeline job
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-37996
Trend Graphs are not showing in Jenkins Pipeline job
Change By:
Cyrille Le Clerc
The Job-level trend graphs including the latest test result link for Junit are not showing up in pipeline job. I can see the reports xml are getting generated inside **/target/surefire-reports. is it something I am missing?I have configured my "Test" stage like below:{code}stage("Test") {try {// Any maven phase that that triggers the test phase can be used here.sh 'mvn clean test -B'} catch(err) { step([$class: junit ' JUnitResultArchiver', testResults: ' **/target/surefire-reports/TEST-*.xml' ]) if (currentBuild.result == 'UNSTABLE') { currentBuild.result = 'FAILURE' } throw err} } {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
[JIRA] (JENKINS-37996) Trend Graphs are not showing in Jenkins Pipeline job
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-37996
Trend Graphs are not showing in Jenkins Pipeline job
Change By:
Cyrille Le Clerc
The Job-level trend graphs including the latest test result link for Junit are not showing up in pipeline job. I can see the reports xml are getting generated inside **/target/surefire-reports. is it something I am missing?I have configured my "Test" stage like below: {code} stage("Test") try {// Any maven phase that that triggers the test phase can be used here.sh 'mvn clean test -B'} catch(err) {step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])if (currentBuild.result == 'UNSTABLE')currentBuild.result = 'FAILURE'throw err} {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
[JIRA] (JENKINS-48491) NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-48491 NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve Change By: Sam Van Oort Assignee: Sam Van Oort 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-48491) NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve
Title: Message Title Sam Van Oort commented on JENKINS-48491 Re: NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve R. Tyler Croy I believe this should be resolved as of workflow-cps 2.47 and workflow-job 2.18 – can you give the updates a try and let us know if comes up after the update? 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-47173) Offer a high-performance storage engine for pipeline at some cost to resumability
Title: Message Title Sam Van Oort commented on JENKINS-47173 Re: Offer a high-performance storage engine for pipeline at some cost to resumability Basil Crow George C I just released workflow-cps 2.47 and workflow-job 2.18 which include a ton of fixes to related logic and likely fix the cause(s) of this – if you see this issue recur, could you please open a new JIRA issue and assign to 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort updated JENKINS-50199 Resolved as of workflow-cps 2.47 and workflow-job 2.18 Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Sam Van Oort Status: In Review Closed 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
[JIRA] (JENKINS-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title Sam Van Oort updated JENKINS-49686 Resolved as of workflow-cps 2.47 and workflow-job 2.18 Jenkins / JENKINS-49686 NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Change By: Sam Van Oort Status: In Review Closed 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
[JIRA] (JENKINS-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title Sam Van Oort updated JENKINS-50407 Resolved as of workflow-cps 2.47 and workflow-job 2.18 Jenkins / JENKINS-50407 NPE from SandboxContinuable.run0 after restart Change By: Sam Van Oort Status: In Review Closed 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
[JIRA] (JENKINS-50652) Post stages are incorrectly handled
Title: Message Title
Steve Todorov created an issue
Jenkins / JENKINS-50652
Post stages are incorrectly handled
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-04-08 18:06
Priority:
Major
Reporter:
Steve Todorov
Consider the following example:
pipeline {
agent {
label 'linux'
}
stages {
stage('Successful stage') {
steps {
script {
sh "sleep 15" // intentionally not using sleep 15 step!
}
}
}
}
post {
success {
echo "Triggered post-success"
}
failure {
echo "Triggered post-failure"
}
unstable {
echo "Triggered post-unstable"
}
aborted {
echo "Triggered post-aborted"
}
}
}
Start the build, let it go into "sleep" and abort the build. The result will be:
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] echo
Triggered post-aborted
[Pipeline] echo
Triggered post-failure
[Pipeline] }
I've also seen in the logs `post-unstable` and `post-failure`, but I am not sure how to provide a way to reproduce this. I'm not sure how that happened but I have seen it a few times on some of our builds.
[JIRA] (JENKINS-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50407 Re: NPE from SandboxContinuable.run0 after restart Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/cps/SandboxContinuable.java http://jenkins-ci.org/commit/workflow-cps-plugin/5d08569babf0249ddd3b0723bcf5671df1e48ac7 Log: JENKINS-50407 Trying to diagnose an NPE. 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-50508) 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed
Title: Message Title Cyrille Le Clerc updated JENKINS-50508 Fixed in 3.5.1-beta-1 https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.1-beta-1 Jenkins / JENKINS-50508 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed 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
[JIRA] (JENKINS-50508) 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed
Title: Message Title Cyrille Le Clerc commented on JENKINS-50508 Re: 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed Andreya Kostov, Alexander Willhaug can you please test https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.1-beta-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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-48357
Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Change By:
Cyrille Le Clerc
{noformat}java.lang.IllegalAccessError: org/apache/http/impl/client/cache/BasicHttpCacheat org.apache.http.impl.client.cache.CachingHttpAsyncClient.(CachingHttpAsyncClient.java:173)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.(ApacheAsyncHttpClient.java:239)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.(ApacheAsyncHttpClient.java:123)at com.atlassian.httpclient.apache.httpcomponents.DefaultHttpClientFactory.doCreate(DefaultHttpClientFactory.java:68)at com.atlassian.httpclient.apache.httpcomponents.DefaultHttpClientFactory.create(DefaultHttpClientFactory.java:35)at com.atlassian.jira.rest.client.internal.async.AsynchronousHttpClientFactory.createClient(AsynchronousHttpClientFactory.java:63)at com.atlassian.jira.rest.client.internal.async.AsynchronousJiraRestClientFactory.create(AsynchronousJiraRestClientFactory.java:35)at com.atlassian.jira.rest.client.internal.async.AsynchronousJiraRestClientFactory.createWithBasicHttpAuthentication(AsynchronousJiraRestClientFactory.java:42)at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:280)at hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:782)at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)Caused: java.lang.reflect.InvocationTargetException{noformat} {noformat}[WARNING] Error while serving http://localhost:8090/jenkins/descriptorByName/hudson.plugins.jira.JiraSite/validatejava.lang.reflect.InvocationTargetException at ...Caused by: java.lang.IllegalAccessError: tried to access class org.apache.http.impl.client.cache.BasicHttpCache from class org.apache.http.impl.client.cache.CachingHttpAsyncClient at org.apache.http.impl.client.cache.CachingHttpAsyncClient.(CachingHttpAsyncClient.java:173) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.(ApacheAsyncHttpClient.java:239) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.(ApacheAsyncHttpClient.java:123) at com.atlassian.httpclient.apache.httpcomponents.DefaultHttpClientFactory.doCreate(DefaultHttpClientFactory.java:68) at com.atlassian.httpclient.apache.httpcomponents.DefaultHttpClientFactory.create(DefaultHttpClientFactory.java:35) at com.atlassian.jira.rest.client.internal.async.AsynchronousHttpClientFactory.createClient(AsynchronousHttpClientFactory.java:63) at com.atlassian.jira.rest.client.internal.async.AsynchronousJiraRestClientFactory.create(AsynchronousJiraRestClientFactory.java:35) at com.atlassian.jira.rest.client.internal.async.AsynchronousJiraRestClientFactory.createWithBasicHttpAuthentication(AsynchronousJiraRestClientFactory.java:42) at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:303) at
[JIRA] (JENKINS-50130) Artifacts are not archived when the build fails using parallel executions.
Title: Message Title Tibor Digana commented on JENKINS-50130 Re: Artifacts are not archived when the build fails using parallel executions. Andrew Bayer Interesting thing is that the archived artifacts appear if the job fails continuously since the beginning. Similar to this: https://builds.apache.org/job/maven-box/job/maven-surefire/job/1512/ I would say that once it becomes blue and then red, the artifacts would not appear in the list of Build Artifacts. 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-50475) Scope import dependencies
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50475 Re: Scope import dependencies Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/test/test_maven_projects/maven_project_with_bom/my-bom/pom.xml jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/test/test_maven_projects/maven_project_with_bom/my-bom/src/main/java/com/example/demo1/Demo1Application.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/test/test_maven_projects/maven_project_with_bom/my-bom/src/test/java/com/example/demo1/Demo1ApplicationTests.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/test/test_maven_projects/maven_project_with_bom/my-jar/pom.xml jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/test/test_maven_projects/maven_project_with_bom/my-jar/src/main/java/com/example/MonoModuleMavenApp.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/test/test_maven_projects/maven_project_with_bom/my-jar/src/test/java/com/example/MonoModuleMavenAppIT.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/test/test_maven_projects/maven_project_with_bom/my-jar/src/test/java/com/example/MonoModuleMavenAppTest.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/test/test_maven_projects/maven_project_with_bom/pom.xml http://jenkins-ci.org/commit/pipeline-maven-plugin/c98d23be25d083debd107cd3caa7bde2ff7e1b1b Log: JENKINS-50475 Add support for scope "import" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50508) 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed
Title: Message Title Cyrille Le Clerc updated JENKINS-50508 Jenkins / JENKINS-50508 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed 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-50508) 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed
Title: Message Title Cyrille Le Clerc started work on JENKINS-50508 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-50508) 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50508 Re: 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/AbstractHealthAwarePublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/FindbugsAnalysisPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/TasksScannerPublisher.java http://jenkins-ci.org/commit/pipeline-maven-plugin/c5e4805e1cf299ea6beb87bf57955cb3426fb8c6 Log: Merge pull request #141 from jenkinsci/JENKINS-50508 JENKINS-50508 extract dependencies to the "Static Code Analysis Plug-ins" Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/bef24d29fab4...c5e4805e1cf2 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-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-49686 NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Change By: Sam Van Oort Component/s: workflow-job-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Sam Van Oort Component/s: workflow-job-plugin Component/s: pipeline Component/s: workflow-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50407 NPE from SandboxContinuable.run0 after restart Change By: Sam Van Oort Component/s: workflow-job-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49086) Lazy-initialize FlowNodeStorage and heads, etc
Title: Message Title Sam Van Oort closed an issue as Duplicate Handled internally by JENKINS-45585 implementation in Workflow-Job - released with version 2.18 Jenkins / JENKINS-49086 Lazy-initialize FlowNodeStorage and heads, etc Change By: Sam Van Oort Status: Open Closed Resolution: Duplicate 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
[JIRA] (JENKINS-49086) Lazy-initialize FlowNodeStorage and heads, etc
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-49086 Lazy-initialize FlowNodeStorage and heads, etc Change By: Sam Van Oort Component/s: workflow-job-plugin Component/s: workflow-cps-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50508) 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50508 Re: 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/AbstractHealthAwarePublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/FindbugsAnalysisPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/TasksScannerPublisher.java http://jenkins-ci.org/commit/pipeline-maven-plugin/c0a4a2b8f19f0388a76346fbe3073312d6056c72 Log: JENKINS-50508 extract dependencies to the "Static Code Analysis Plug-ins", to the package hudson.plugins.analysis.core or other plugins outside of org.jenkinsci.plugins.pipeline.maven.MavenPublisher sub classes to prevent class loading issues and NPE when the related plugins are not installed. 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-49170) NPE can be thrown on null triggers list
Title: Message Title Sam Van Oort closed an issue as Fixed Released with v2.18 Jenkins / JENKINS-49170 NPE can be thrown on null triggers list Change By: Sam Van Oort Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title Sam Van Oort commented on JENKINS-41845 Re: Suppress default pipeline output Implementation to add the HTML class. 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-41845) Suppress default pipeline output
Title: Message Title Sam Van Oort resolved as Fixed Resolved as of 2.18 by supporting use of the Simple Theme Plugin to hide these (they now include the pipeline-annotated class). Jenkins / JENKINS-41845 Suppress default pipeline output Change By: Sam Van Oort Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49686 Re: NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Code changed in jenkins User: Sam Van Oort Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowRunRestartTest.java src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowRunTest.java http://jenkins-ci.org/commit/workflow-job-plugin/f0c26058f31d4f159a82a3cace52935e93f20701 Log: Merge pull request #93 from svanoort/fix-resume-issues Fix resume issues JENKINS-49686 and JENKINS-50199 and JENKINS-50407 Compare: https://github.com/jenkinsci/workflow-job-plugin/compare/e11cea623f61...f0c26058f31d 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Code changed in jenkins User: Sam Van Oort Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowRunRestartTest.java src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowRunTest.java http://jenkins-ci.org/commit/workflow-job-plugin/f0c26058f31d4f159a82a3cace52935e93f20701 Log: Merge pull request #93 from svanoort/fix-resume-issues Fix resume issues JENKINS-49686 and JENKINS-50199 and JENKINS-50407 Compare: https://github.com/jenkinsci/workflow-job-plugin/compare/e11cea623f61...f0c26058f31d 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-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50407 Re: NPE from SandboxContinuable.run0 after restart Code changed in jenkins User: Sam Van Oort Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowRunRestartTest.java src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowRunTest.java http://jenkins-ci.org/commit/workflow-job-plugin/f0c26058f31d4f159a82a3cace52935e93f20701 Log: Merge pull request #93 from svanoort/fix-resume-issues Fix resume issues JENKINS-49686 and JENKINS-50199 and JENKINS-50407 Compare: https://github.com/jenkinsci/workflow-job-plugin/compare/e11cea623f61...f0c26058f31d 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-50442) Adding removeBadge(icon) and removeAllBadges() methods to remove existing badges
Title: Message Title Marc Brugger closed an issue as Fixed Jenkins / JENKINS-50442 Adding removeBadge(icon) and removeAllBadges() methods to remove existing badges Change By: Marc Brugger Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49699) Doktor plugin affected by JEP-200
Title: Message Title Siarhei Krukau commented on JENKINS-49699 Re: Doktor plugin affected by JEP-200 Oleg Nenashev I've tested this change: https://github.com/madhead/doktor/commit/d00e3f24d1b1be92391f3983405b58345b514135 and it seems to be working. I mean, listing those classes in META-INF/hudson.remoting.ClassFilter was enough. I have not seen any warnings about kotlin.collections.EmptyList. Joseph Petersen, Oleg Nenashev I decided not to depend on other plugins. This forces me to use pluginFirstClassLoader is this a bad practice or not? I've seen no issues with it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49805) Prototype error telemetry logging with a Java Util Logger configuration
Title: Message Title Baptiste Mathus commented on JENKINS-49805 Re: Prototype error telemetry logging with a Java Util Logger configuration As discussed on the chat Friday with R. Tyler Croy, we need to enrich the JEP and prototype to see if/how to have a rotating log file implem to be closer to Apache logrotate for instance. Meaning: the file to read would always be, say, file.log, and the rotated ones would be file.log.1, file.log.2, and so on. 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-50291) Customize where AsyncPeriodicWork are logged
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50291 Re: Customize where AsyncPeriodicWork are logged Code changed in jenkins User: Baptiste Mathus Path: core/src/main/java/hudson/triggers/SafeTimerTask.java http://jenkins-ci.org/commit/jenkins/d366abc1d7b2a96a4ebd3acf44d5c812a4246d48 Log: Merge pull request #3382 from batmat/JENKINS-50291-followup Log the message only once in INFO level Compare: https://github.com/jenkinsci/jenkins/compare/70c408cedf42...d366abc1d7b2 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-50073) Mockito Test for StablePluginReference
Title: Message Title Michaela Reitschuster started work on JENKINS-50073 Change By: Michaela Reitschuster 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-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure It looks like jenkins-test-harness currently depends on 1.651.1, which does not disable SSHD by default. I'm unsure of how to add configuration at setup to avoid starting SSHD. but I am suspicious that this will resolve the test issues 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-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller edited a comment on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure I am pretty sure this can be resolved by disabling the SSHD server at startup. I am not certain how to do this yet. 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-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure I am pretty sure this can be resolved by disabling the SSHD server at startup. 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-50651) Add link from SRF test run to SRF report
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-50651 Add link from SRF test run to SRF report Issue Type: Improvement Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2018-04-08 07:12 Labels: 5.3.5-beta Priority: Major Reporter: Michael Seldin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50650) Git parameter show error after cancel job in windows slave
Title: Message Title chao qian updated an issue Jenkins / JENKINS-50650 Git parameter show error after cancel job in windows slave Change By: chao qian Hi,My jenkins job run on a windows slave.I cancel a build during sync code by git plugin, and i want to submit a new build, i find the git parameter show error.[ Template_For_GithubEE/qctest1 ] Unexpected error! hudson.plugins.git.GitException: Command "git ls-remote -h git@***" returned status code 128: stdout: stderr: /home/apache-tomcat-6.0.37/temp/ssh1891823683750114718.sh: line 6: ssh: command not found fatal: The remote end hung up unexpectedly. The error don can 't reproduce be reproduced in linux slave.And i also update git parameter plugin to latest:0.9.1, window slave also have the same problem 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,
[JIRA] (JENKINS-50650) Git parameter show error after cancel job in windows slave
Title: Message Title chao qian created an issue Jenkins / JENKINS-50650 Git parameter show error after cancel job in windows slave Issue Type: Bug Assignee: Boguslaw Klimas Components: git-parameter-plugin Created: 2018-04-08 07:07 Environment: jenkins:2.7.3 git-parameter-plugin:0.8.0 Priority: Major Reporter: chao qian Hi, My jenkins job run on a windows slave. I cancel a build during sync code by git plugin, and i want to submit a new build, i find the git parameter show error. [ Template_For_GithubEE/qctest1 ] Unexpected error! hudson.plugins.git.GitException: Command "git ls-remote -h git@***" returned status code 128: stdout: stderr: /home/apache-tomcat-6.0.37/temp/ssh1891823683750114718.sh: line 6: ssh: command not found fatal: The remote end hung up unexpectedly. The error don't reproduce in linux slave. And i also update git parameter plugin to latest:0.9.1, window slave also have the same problem Add Comment
