[JIRA] (JENKINS-37998) Warning log "no flow execution found for pipelinejob #1"
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-37998
Re: Warning log "no flow execution found for pipelinejob #1"
[~jglick] Thanks for giving me hope ;)Frankly I must admit that I am not so sure anymore about the "_without [...] or whatever potentially unusual actions_", because it does not happen at the moment for the latest builds seemingly; and a small reproducer with just "_push button deployment (input step wrapped into timeout)_" also failed to produce these warning logs ;-( * Hm, this morning the warning logs are appearing!? (I naively guess that yesterday afternoon when I was trying to reproduce them, something was still in memory/cache or so? Again, for newly/just triggered pipeline builds these warnings are not logged)In case it is of any help, this is the pipeline script (presumably job properties and build discarder, as well as 'init' stage, or maybe everything outside 'prepare deployment' stage is not needed?):{code:java}#!/usr/bin/env groovydef jobProperties = [ buildDiscarder(logRotator(daysToKeepStr: '30', numToKeepStr: '30'))]properties(jobProperties)stage('init') { echo 'init'}boolean doDeploy = truestage('prepare deployment') { try {timeout(time:7, unit:'DAYS') { input message:'Deploy?'} } catch(err) { // timeout reached or input falsedoDeploy = false } if (doDeploy) {echo 'prepare something for deployment' }}if (doDeploy) { stage('do deployment') {echo 'doDeployment' }}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53810) Launch Agents fails with ERROR: null java.util.concurrent.CancellationException
Title: Message Title Gerd Hoffmann commented on JENKINS-53810 Re: Launch Agents fails with ERROR: null java.util.concurrent.CancellationException Interesting. Raising the timeout helped in my case too. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55854) Unable to connect checkmrax plugin and Checkmarx server was not found on the specified adress: java.net.ConnectException: Connection timed out: connect
Title: Message Title ramya bk created an issue Jenkins / JENKINS-55854 Unable to connect checkmrax plugin and Checkmarx server was not found on the specified adress: java.net.ConnectException: Connection timed out: connect Issue Type: Bug Assignee: Sergey Kadaner Components: checkmarx-plugin Created: 2019-01-30 06:57 Environment: Jenkins plugin : 2.15, Checkmarx: 8.6 Labels: plugin Priority: Critical Reporter: ramya bk After Successful installation of Jenkins, i have installed Checkmarx plugin. while testing TLS/SSL Server Certificate Validation, test connection was failed. Got the error like "Checkmarx server was not found on the specified address: java.net.ConnectException: Connection timed out: connect". please let me know how to connect Jenkins to Checkmarx. is there any ports needs to open? if yes, kindly let me know the port number to be opened?
[JIRA] (JENKINS-55853) Customized Post Build Comment ignored for multi-configuration projects
Title: Message Title Pavel Roskin created an issue Jenkins / JENKINS-55853 Customized Post Build Comment ignored for multi-configuration projects Issue Type: Bug Assignee: Unassigned Components: stash-pullrequest-builder-plugin Created: 2019-01-30 06:49 Environment: Jenkins 2.138.4, stash-pullrequest-builder-plugin 1.7.0. Labels: configuration Priority: Minor Reporter: Pavel Roskin The "Post Build Comment" settings are ignored for some jobs. Instead, Jenkins posts the default comments to Stash. I tried customizing several jobs, and I see that the customization is ignored if and only if it's a multi-configuration project. Free-style projects support customized messages. Add Comment
[JIRA] (JENKINS-55475) AntClassLoader doesn't report corrupted files
Title: Message Title Marco Jacob commented on JENKINS-55475 Re: AntClassLoader doesn't report corrupted files Yes, found it: SEVERE: Failed Inspecting plugin C:\Entwicklung\TRUNK-Photon\ee_jenkins\ee_jenkins_deploy_plugin\target\tmp\jenkins702521110614006407\the.jpl java.util.zip.ZipException: error in opening zip file Jan 30, 2019 7:31:08 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Inspecting plugin C:\Entwicklung\TRUNK-Photon\ee_jenkins\ee_jenkins_deploy_plugin\target\tmp\jenkins702521110614006407\credentials.jpi java.io.IOException: Failed to expand C:\Entwicklung\TRUNK-Photon\ee_jenkins\ee_jenkins_deploy_plugin\target\tmp\jenkins702521110614006407\credentials.jpi at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:632) Caused by: Error while expanding C:\Entwicklung\TRUNK-Photon\ee_jenkins\ee_jenkins_deploy_plugin\target\tmp\jenkins702521110614006407\credentials.jpi java.util.zip.ZipException: archive is not a ZIP archive at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:190) Caused by: java.util.zip.ZipException: archive is not a ZIP archive at org.apache.tools.zip.ZipFile.positionAtEndOfCentralDirectoryRecord(ZipFile.java:771) at org.apache.tools.zip.ZipFile.positionAtCentralDirectory(ZipFile.java:707) at org.apache.tools.zip.ZipFile.populateFromCentralDirectory(ZipFile.java:452) at org.apache.tools.zip.ZipFile.(ZipFile.java:214) at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:168) Full file: InjectedTest-output.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55475) AntClassLoader doesn't report corrupted files
Title: Message Title Marco Jacob commented on JENKINS-55475 Re: AntClassLoader doesn't report corrupted files The directory jenkins702521110614006407 is not existing in the given directory in tmp after the build is done. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55475) AntClassLoader doesn't report corrupted files
Title: Message Title Marco Jacob updated an issue Jenkins / JENKINS-55475 AntClassLoader doesn't report corrupted files Change By: Marco Jacob Attachment: InjectedTest-output.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38084) Add support to mark jobs as disabled on import
Title: Message Title Denys Digtiar edited a comment on JENKINS-38084 Re: Add support to mark jobs as disabled on import The disable on import feature was lost when Folder import feature was merged. Please see [ https://github.com/jenkinsci/job-import-plugin/commit/594157a0404b25a87ace3f50c400559fa354e0c0 ] #diff-0034cbafb00263181c56677b9739d99aL130 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38084) Add support to mark jobs as disabled on import
Title: Message Title Denys Digtiar reopened an issue The disable on import feature was lost when Folder import feature was merged. Please see https://github.com/jenkinsci/job-import-plugin/commit/594157a0404b25a87ace3f50c400559fa354e0c0 Jenkins / JENKINS-38084 Add support to mark jobs as disabled on import Change By: Denys Digtiar Resolution: Done Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49339) Add ability to get test results for a given Maven execution
Title: Message Title
Vincent Massol edited a comment on JENKINS-49339
Re: Add ability to get test results for a given Maven execution
[~cleclerc] Thanks for the hint with JENKINS-41710. It took me a while to read all the context of this issue and this lead me to find {{TestResult#getResultInRun(Run)}}.I've modified the XWiki pipeline code to find the failing tests from a {{withMaven}} execution like this:{code}/** * @return the failing tests for the current build */def getFailingTests(){def failingTestsAbstractTestResultAction testResultAction = currentBuild.rawBuild.getAction(AbstractTestResultAction.class)if (testResultAction != null) {failingTests = testResultAction.getResult().getResultInRun(currentBuild.rawBuild).getFailedTests()} else {// No tests were run in this build, nothing left to do.failingTests = []}return failingTests}{code}I've yet to verify if it works fine (i.e. no more side effects from parallel runs). However I've noticed another problem which feels weird. In the XWiki pipeline we look for failing tests and look for screenshots taken by our selenium tests and attach the screenshot to the Jenkins job page:This is what we call (full code at https://github.com/xwiki/xwiki-jenkins-pipeline/blob/3a38a609126e5e2007754d9937871a100b029a9b/vars/xwikiBuild.groovy#L467):{code}def failingTests = getFailingTests() // the method above...for (def failedTest : failingTests) { def moduleFile = failedTest.getSuiteResult().getFile().getParent().getParent()...{code}The problem is that in some cases the {{moduleFile}} for the failing test points to the wrong maven module.For example in a job I got:{noformat}21:34:45.868 [main] INFO org.xwiki.test.ui.TestDebugger - Screenshot for failing test [NotificationsIT-testNotificationDisplayerClass] saved at [/home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master/xwiki-platform-core/xwiki-platform-notifications/xwiki-platform-notifications-test/xwiki-platform-notifications-test-tests/target/screenshots/NotificationsIT-testNotificationDisplayerClass.png].{noformat}This means the failing test was in module {{xwiki-platform-notifications-test-tests}}.But {{getSuiteResult().getFile().getParent().getParent()}} returned {{/home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master/xwiki-platform-core/xwiki-platform-activeinstalls/xwiki-platform-activeinstalls-test/xwiki-platform-activeinstalls-test-tests/target}}, i.e. the {{xwiki-platform-activeinstalls-test-tests}} maven module.Any idea or direction I could check for why the failing test class ({{CaseResult}}) would give me a completely wrong file path for the surefire XML report file?Thanks a lot
Add Comment
[JIRA] (JENKINS-49339) Add ability to get test results for a given Maven execution
Title: Message Title
Vincent Massol commented on JENKINS-49339
Re: Add ability to get test results for a given Maven execution
Cyrille Le Clerc Thanks for hint with JENKINS-41710. It took me a while to read all the context of this issue and this lead me to find TestResult#getResultInRun(Run). I've modified the XWiki pipeline code to find the failing tests from a withMaven execution like this:
/**
* @return the failing tests for the current build
*/
def getFailingTests()
{
def failingTests
AbstractTestResultAction testResultAction = currentBuild.rawBuild.getAction(AbstractTestResultAction.class)
if (testResultAction != null) {
failingTests = testResultAction.getResult().getResultInRun(currentBuild.rawBuild).getFailedTests()
} else {
// No tests were run in this build, nothing left to do.
failingTests = []
}
return failingTests
}
I've yet to verify if it works fine (i.e. no more side effects from parallel runs). However I've noticed another problem which feels weird. In the XWiki pipeline we look for failing tests and look for screenshots taken by our selenium tests and attach the screenshot to the Jenkins job page: This is what we call (full code at https://github.com/xwiki/xwiki-jenkins-pipeline/blob/3a38a609126e5e2007754d9937871a100b029a9b/vars/xwikiBuild.groovy#L467):
def failingTests = getFailingTests() // the method above
...
for (def failedTest : failingTests) {
def moduleFile = failedTest.getSuiteResult().getFile().getParent().getParent()
...
The problem is that in some cases the moduleFile for the failing test points to the wrong maven module. For example in a job I got:
21:34:45.868 [main] INFO org.xwiki.test.ui.TestDebugger - Screenshot for failing test [NotificationsIT-testNotificationDisplayerClass] saved at [/home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master/xwiki-platform-core/xwiki-platform-notifications/xwiki-platform-notifications-test/xwiki-platform-notifications-test-tests/target/screenshots/NotificationsIT-testNotificationDisplayerClass.png].
This means the failing test was in module xwiki-platform-notifications-test-tests. But getSuiteResult().getFile().getParent().getParent() returned /home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master/xwiki-platform-core/xwiki-platform-activeinstalls/xwiki-platform-activeinstalls-test/xwiki-platform-activeinstalls-test-tests/target, i.e. the xwiki-platform-activeinstalls-test-tests maven module. Any idea or direction I could check for why the failing test class (CaseResult) would give me a completely wrong file path for the surefire XML report file? Thanks a lot
[JIRA] (JENKINS-55826) how to delete workspace forcely?
Title: Message Title
Hokwang Lee edited a comment on JENKINS-55826
Re: how to delete workspace forcely?
Here's my Jenkinsfile.{code:java}pipeline { options {skipDefaultCheckout() } agent {kubernetes { yaml ""} } stages {stage('Sync') { steps {container(name: 'image', shell: '/bin/bash') { checkout perforce( browser: swarm('http://1.2.3.4'), credential: '1.2.3.4_perforce', populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: templateSpec(charset: 'utf8', format: 'jenkins-${JOB_NAME}-${NODE_NAME}', pinHost: false, templateName: 'TEMPLATE__MAIN__CORE__SVR19A_5GC') )} }}stage('Build') { steps {container(name: 'image', shell: '/bin/bash') { cleanup true} }} }}{code}I always create new workspace from template workspace andwant to delete every time.I don't want run sync -f ...@0 command and revert command (don't needed)I tried to use "p4cleanup true" and "p4cleanup false" it does not work.These did unsync only. Here's output when I use "cleanup true".{code:java}P4 Task: cleanup client: jenkins-luckyhk.lee_cleanup- core image - 19.a- rw3sr-dhw00P4 Task: unsyncing client: jenkins-luckyhk.lee_cleanup- core image - 19.a- rw3sr-dhw00P4 Task: syncing files at change: 0... p4 sync -f -q /home/jenkins/workspace/luckyhk.lee_cleanup/...@0 +duration: 0m 18s... p4 client -o jenkins-luckyhk.lee_cleanup- core image - 19.a- rw3sr-dhw00 +... p4 revert /home/jenkins/workspace/luckyhk.lee_cleanup/... +P4 Task: remove client: jenkins-luckyhk.lee_cleanup- core image - 19.a- rw3sr-dhw00... p4 client -d jenkins-luckyhk.lee_cleanup- core image - 19.a- rw3sr-dhw00 -p4 client -d jenkins-luckyhk.lee_cleanup- core image - 19.a- rw3sr-dhw00Client 'jenkins-luckyhk.lee_cleanup- core image - 19.a- rw3sr-dhw00' is locked and can't be deleted.{code} I think if "cleanup true" do "p4 client -d -f" command is better than doing unsync and revert and delete,anyway I need -f option now.
Add Comment
[JIRA] (JENKINS-55826) how to delete workspace forcely?
Title: Message Title
Hokwang Lee commented on JENKINS-55826
Re: how to delete workspace forcely?
Here's my Jenkinsfile.
pipeline {
options {
skipDefaultCheckout()
}
agent {
kubernetes {
yaml """
"""
}
}
stages {
stage('Sync') {
steps {
container(name: 'image', shell: '/bin/bash') {
checkout perforce( browser: swarm('http://1.2.3.4'),
credential: '1.2.3.4_perforce',
populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false),
workspace: templateSpec(charset: 'utf8', format: 'jenkins-${JOB_NAME}-${NODE_NAME}', pinHost: false, templateName: 'TEMPLATE__MAIN__CORE__SVR19A_5GC')
)
}
}
}
stage('Build') {
steps {
container(name: 'core-rhel75', shell: '/bin/bash') {
cleanup true
}
}
}
}
}
I always create new workspace from template workspace and want to delete every time. I don't want run sync -f ...@0 command and revert command (don't needed) I tried to use "p4cleanup true" and "p4cleanup false" it does not work. These did unsync only. Here's output when I use "cleanup true".
P4 Task: cleanup client: jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00
P4 Task: unsyncing client: jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00
P4 Task: syncing files at change: 0
... p4 sync -f -q /home/jenkins/workspace/luckyhk.lee_cleanup/...@0 +
duration: 0m 18s
... p4 client -o jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00 +
... p4 revert /home/jenkins/workspace/luckyhk.lee_cleanup/... +
P4 Task: remove client: jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00
... p4 client -d jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00 -
p4 client -d jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00
Client 'jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00' is locked and can't be deleted.
I think if "cleanup true" do "p4 client -d -f" command is better than doing unsync and revert and delete, anyway I need -f option now.
Add Comment
[JIRA] (JENKINS-55826) how to delete workspace forcely?
Title: Message Title
Hokwang Lee edited a comment on JENKINS-55826
Re: how to delete workspace forcely?
Here's my Jenkinsfile.{code:java}pipeline { options {skipDefaultCheckout() } agent {kubernetes { yaml ""} } stages {stage('Sync') { steps {container(name: 'image', shell: '/bin/bash') { checkout perforce( browser: swarm('http://1.2.3.4'), credential: '1.2.3.4_perforce', populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: templateSpec(charset: 'utf8', format: 'jenkins-${JOB_NAME}-${NODE_NAME}', pinHost: false, templateName: 'TEMPLATE__MAIN__CORE__SVR19A_5GC') )} }}stage('Build') { steps {container(name: ' core-rhel75 image ', shell: '/bin/bash') { cleanup true} }} }}{code}I always create new workspace from template workspace andwant to delete every time.I don't want run sync -f ...@0 command and revert command (don't needed)I tried to use "p4cleanup true" and "p4cleanup false" it does not work.These did unsync only. Here's output when I use "cleanup true".{code:java}P4 Task: cleanup client: jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00P4 Task: unsyncing client: jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00P4 Task: syncing files at change: 0... p4 sync -f -q /home/jenkins/workspace/luckyhk.lee_cleanup/...@0 +duration: 0m 18s... p4 client -o jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00 +... p4 revert /home/jenkins/workspace/luckyhk.lee_cleanup/... +P4 Task: remove client: jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00... p4 client -d jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00 -p4 client -d jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00Client 'jenkins-luckyhk.lee_cleanup-core-19.a-rw3sr-dhw00' is locked and can't be deleted.{code} I think if "cleanup true" do "p4 client -d -f" command is better than doing unsync and revert and delete,anyway I need -f option now.
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-52522) Display more than 100 records in the workflow api
Title: Message Title Ken Lamb commented on JENKINS-52522 Re: Display more than 100 records in the workflow api Cool. Thanks again for the info! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52522) Display more than 100 records in the workflow api
Title: Message Title Natesh Kukreja commented on JENKINS-52522 Re: Display more than 100 records in the workflow api There's a pagination feature with the the Blue Ocean API, "?start=". If you have 200 records, per say, you'd add this endpoint, after you've retrieved the first 100, and would include "?start=100" at the end of your request to retrieve the next 100 records. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Mark Waite commented on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo Good catch! Thanks Tim Graham for deducing the problem. I'll run some tests with reverting that change or will discuss it with the author of the change, Oleg Nenashev. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Mark Waite edited a comment on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo Good catch! Thanks [~timo] for deducing the problem. I'll run some tests with reverting that change or will discuss it with the author of the change, [~oleg_nenashev]. Expect that a git plugin 3.9.3 will be coming soon with a fix for the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title
Mark Waite edited a comment on JENKINS-55836
Re: Unable to delete workspace due to locked git .pack file
Please provide more details to duplicate the problem.* What is {{WS-CLEANUP}} and how is it used in that job?* Is the Jenkins job a Pipeline job or a Freestyle job?* If a Freestyle job, does the same problem exist if you modify the job definition to add the "Wipe out repository and force clone" additional behavior to the git configuration of the job? \ * If a Pipeline job, does the same problem exist if you use the {{deleteDir}} step?* Is the Jenkins job configured to use command line git or JGit to clone and checkout the workspace?* What git related options are included in the job definition?* Is there an anti-virus program running on the Windows computer? If so, is the problem still visible if virus scanning is disabled for the workspace directory?I can't duplicate the problem in [my experiment|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-55836-windows-wipe-workspace/config.xml]. I don't recognize WS-CLEANUP, so I approximated it with "Wipe out repository and force clone".
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title
Mark Waite edited a comment on JENKINS-55836
Re: Unable to delete workspace due to locked git .pack file
Please provide more details to duplicate the problem.* What is {{WS-CLEANUP}} and how is it used in that job?* Is the Jenkins job a Pipeline job or a Freestyle job?* If a Freestyle job, does the same problem exist if you modify the job definition to add the "Wipe out repository and force clone" additional behavior to the git configuration of the job? \ * If a Pipeline job, does the same problem exist if you use the {{deleteDir}} step?* Is the Jenkins job configured to use command line git or JGit to clone and checkout the workspace?* What git related options are included in the job definition?* Is there an anti-virus program running on the Windows computer? If so, is the problem still visible if virus scanning is disabled for the workspace directory?I can't duplicate the problem in [my experiment|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-55836-windows-wipe-workspace/config.xml]. I don't recognize WS-CLEANUP, so I approximated it with "Wipe out repository and force clone".
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Geoff Dunn edited a comment on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo Yeah I think Tim has got it. Doing my own experimentation it seems in 3.9.1 it will ignore the Tool configuration and use /usr/bin/git on my linux slaves. With 3.9.2 it started trying to use the configured (whoops) c:\Program Files etcChanging the configuration to just "git" seems to resolve any issues I had. However deleting the tool configuration and it will try and run git.exe on the linux slave (as the tool will put a default value with git . So there is still something not quite right. exe) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Geoff Dunn commented on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo Yeah I think Tim has got it. Doing my own experimentation it seems in 3.9.1 it will ignore the Tool configuration and use /usr/bin/git on my linux slaves. With 3.9.2 it started trying to use the configured (whoops) c:\Program Files etc Changing the configuration to just "git" seems to resolve any issues I had. However deleting the tool configuration and it will try and run git.exe on the linux slave. So there is still something not quite right. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52522) Display more than 100 records in the workflow api
Title: Message Title Ken Lamb commented on JENKINS-52522 Re: Display more than 100 records in the workflow api Thanks for the info. Does the Blue Ocean API have the 100 record limit? Or is it fixed there? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52522) Display more than 100 records in the workflow api
Title: Message Title Natesh Kukreja commented on JENKINS-52522 Re: Display more than 100 records in the workflow api Hey Ken, I made a post in their Google Groups and they said that the WorkFlowPluginAPI will be not be maintained soon. They suggested I use the BlueOcean Plugin API. I was able to use the Blue Ocean API and produce the same results as the WorkFlowStagePlugin would have. I hope that helps! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52522) Display more than 100 records in the workflow api
Title: Message Title Ken Lamb commented on JENKINS-52522 Re: Display more than 100 records in the workflow api We have the same issue. I have a pipeline that generates more than 100 stageFlowNodes. I had always assumed there was a pagination API that I needed to utilize to get the remaining information. However, I just went looking for it and could not find it. Then, I found this. The fact that it has sat here for 6 months doesn't give me much hope that a resolution is soon to come. If there is a cap, can it be raised? If it cannot be raised, can the API be extended so that we can get access to the information in another way? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Mark Waite commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Please provide more details to duplicate the problem. What is WS-CLEANUP and how is it used in that job? Is the Jenkins job a Pipeline job or a Freestyle job? If a Freestyle job, does the same problem exist if you modify the job definition to add the "Wipe out repository and force clone" additional behavior to the git configuration of the job? Is the Jenkins job configured to use command line git or JGit to clone and checkout the workspace? What git related options are included in the job definition? Is there an anti-virus program running on the Windows computer? If so, is the problem still visible if virus scanning is disabled for the workspace directory? I can't duplicate the problem in my experiment. I don't recognize WS-CLEANUP, so I approximated it with "Wipe out repository and force clone". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Tim Graham commented on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo https://github.com/jenkinsci/git-plugin/commit/77967dbb349c8d1df02e4a21e0ff9d9e107e94ee may be the cause? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Title: Message Title Cyrille Le Clerc commented on JENKINS-47784 Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin Sandra Parsick your message seemed to have been truncated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55852) Active Directory 2.11 throwing NPE from it.shouldDisplay() in /updateCenter/
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-55852 Active Directory 2.11 throwing NPE from it.shouldDisplay() in /updateCenter/ Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2019-01-29 22:56 Environment: Active Directory 2.11, Jenkins 2.150.2 LTS on Windows Server 2016 Priority: Minor Reporter: Nick Jones After upgrading to the Active Directory 2.11 plugin this morning (due to https://jenkins.io/security/advisory/2019-01-28/), we started seeing the following stacktrace in logs: Jan 29, 2019 4:35:09 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.shouldDisplay() in /updateCenter/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$TlsConfigurationAdministrativeMonitor.isActivated(ActiveDirectorySecurityRealm.java:940) at jenkins.model.Jenkins.lambda$getActiveAdministrativeMonitors$0(Jenkins.java:2140) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at
[JIRA] (JENKINS-55851) npmrc Config does not appear in pipeline snippet generator
Title: Message Title Dylan Dewhurst created an issue Jenkins / JENKINS-55851 npmrc Config does not appear in pipeline snippet generator Issue Type: Bug Assignee: Tim Downey Components: pipeline-npm-plugin Created: 2019-01-29 22:47 Environment: Jenkins 2.150.2.3 pipeline-npm 0.9.2 nodejs 1.2.7 config-file-provider 3.2 Priority: Minor Reporter: Dylan Dewhurst In the pipeline Snippet Generator, the withNPM step does not generate the list of npmrc Config items. Steps to reproduce: Install pipeline-npm, nodejs, and config-file-provider plugins Create a folder Create a pipeline job inside the folder Inside the folder, go to Config Files -> add a new config. Create an Npm config file and save it Inside the pipeline job configuration, select Pipeline Script then Pipeline Syntax Under Snippet Generator, select withNPM: Provide NPM Environment Click dropdown for npmrc Config. See that there are no options listed.
[JIRA] (JENKINS-55850) How to rebuild on PR source branch change?
Title: Message Title Andrew Goldis created an issue Jenkins / JENKINS-55850 How to rebuild on PR source branch change? Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-01-29 22:02 Environment: Linux Debian - 8.11 Jenkins 2.161 org.jenkins-ci.plugins:github-branch-source:2.4.2 Labels: user-experience Priority: Minor Reporter: Andrew Goldis It is a question. When I create a PR on Github, I can see that a new build is triggered correctly. However, when I push a new commit to the source branch of the PR, it does not generate a new build. The configuration used for Branch Sources: Discover branches: exclude branches that are also filled as PRs Discover PRs: The current pull request revision What should be the right configuration to trigger rebuilds when either branch or a PR is changed?
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Glenn Herbert edited a comment on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo Similar situation. All defined nodes have a Tool Location set for (Git) Default. Works at 3.9.1, but fails at 3.9.2. It's almost as if its ignoring Tool Locations. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Glenn Herbert commented on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo Similar situation. All defined nodes have a Tool Location set for (Git) Default. Works at 3.9.1, but fails at 3.9.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53810) Launch Agents fails with ERROR: null java.util.concurrent.CancellationException
Title: Message Title Jesper Jensen commented on JENKINS-53810 Re: Launch Agents fails with ERROR: null java.util.concurrent.CancellationException Just had the same problem as described, the workaround I found was to change the timeout to 60 seconds (default 10). First time it too very long almost 60 seconds the second time only a few seconds. Hope that this helps! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55843) Folders missed due to anonymization in the bundle
Title: Message Title Ramon Leon started work on JENKINS-55843 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55849) cannot stop auto-scrolling in blue ocean console
Title: Message Title boris ivan created an issue Jenkins / JENKINS-55849 cannot stop auto-scrolling in blue ocean console Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-01-29 21:14 Environment: 1.10.2 Priority: Minor Reporter: boris ivan When I have console for an active stage open, I see the new messages added real-time to the bottom of the console window, so far so good. But if I want to scroll up to see messages printed a couple seconds ago, or scroll up so I can collapse the console window so I can view the pipeline, I'm prevented from doing so because every new log message forces the focus back down to the bottom. In legacy Jenkins, being at the bottom of the window would continue to update, but if the user scrolled up away from the bottom, it would not force focus back down to the bottom with every new message. When the messages come quickly, I'm forced to spam the 'home' key on the keyboard to try and jump up to the top and click the 'collapse' icon as quickly as possible, but not usually not quick enough. There should be some standardized way of preventing the auto scroll.
[JIRA] (JENKINS-53926) Builds hang ocassionally on resume after Jenkins restart
Title: Message Title Sven-Hendrik Haase commented on JENKINS-53926 Re: Builds hang ocassionally on resume after Jenkins restart Have you by any chance made any progress on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55848) Delete x should specify the name of x
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55848 Delete x should specify the name of x Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-01-29 20:15 Priority: Minor Reporter: Josh Soref It's helpful to identify the name of the thing being deleted, and this is usually available. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55847) unlocalized "are you sure?" in breadcrumbs
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-55847
unlocalized "are you sure?" in breadcrumbs
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2019-01-29 19:41
Priority:
Minor
Reporter:
Josh Soref
https://github.com/jenkinsci/jenkins/blob/f887a486b523145431996399d3a44e749f90c120/core/src/main/resources/lib/layout/breadcrumbs.js#L60
core/src/main/resources/lib/layout/breadcrumbs.js:if (confirm(cfg.displayName + ': are you sure?')) { // TODO I18N
Add Comment
[JIRA] (JENKINS-55230) SupportPlugin.writeBundle should gracefully handle remoting.ChannelClosedException
Title: Message Title Owen Wood commented on JENKINS-55230 Re: SupportPlugin.writeBundle should gracefully handle remoting.ChannelClosedException I can't see where this is actually triggered in master. I think this might have already been addressed in https://github.com/jenkinsci/support-core-plugin/commit/efc40215b5a25acbf4eb437943637893dd9be9e4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55230) SupportPlugin.writeBundle should gracefully handle remoting.ChannelClosedException
Title: Message Title Owen Wood closed an issue as Won't Do Jenkins / JENKINS-55230 SupportPlugin.writeBundle should gracefully handle remoting.ChannelClosedException Change By: Owen Wood Status: In Progress Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55230) SupportPlugin.writeBundle should gracefully handle remoting.ChannelClosedException
Title: Message Title Owen Wood started work on JENKINS-55230 Change By: Owen Wood Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55846) No issues found when parsing Error-Prone output from console log during gradle build
Title: Message Title Zach Olbrys created an issue Jenkins / JENKINS-55846 No issues found when parsing Error-Prone output from console log during gradle build Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-29 19:12 Environment: Jenkins: 2.150.2 warnings-ng-plugin: 2.1.2 gradle: 4.10.1 java: 1.8.0_144-b01 Priority: Minor Reporter: Zach Olbrys My Jenkins build results in the following output: [Error Prone] Sleeping for 5 seconds due to JENKINS-32191... [Error Prone] Parsing console log (workspace: 'D:\Jenkins\workspace\Develop Debug Branch Tests') [Error Prone] Attaching ResultAction with ID 'error-prone' to run 'Develop Debug Branch Tests #55'. [Error Prone] No valid reference build found that meets the criteria (NO_JOB_FAILURE - SUCCESSFUL_QUALITY_GATE) [Error Prone] All reported issues will be considered outstanding [Error Prone] Evaluating quality gates [Error Prone] -> All quality gates have been passed [Error Prone] Enabling health report (Healthy=2, Unhealthy=3, Minimum Severity=LOW) [Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) Despite several warnings being reported earlier: D:\Jenkins\workspace\Develop Debug Branch Tests\app\src\main\java\com\zao\testapp\util\json\JSONParser.java:35: warning:
[JIRA] (JENKINS-55711) java.io.FileNotFoundException with tmp file
Title: Message Title Gabe Montero resolved as Fixed Jenkins / JENKINS-55711 java.io.FileNotFoundException with tmp file Change By: Gabe Montero Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55711) java.io.FileNotFoundException with tmp file
Title: Message Title Gabe Montero commented on JENKINS-55711 Re: java.io.FileNotFoundException with tmp file v1.0.24 of this plugin has been initiated at the update center Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Shaun Thompson commented on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo I'm running into the same issue as well with 3.9.2 which is fixed by reverting to **3.9.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Shaun Thompson edited a comment on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo I'm running into the same issue as well with 3.9.2 which is fixed by reverting to ** 3.9.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51326) JEP-200 long data type rejected after upgrade to 2.107.3
Title: Message Title Oleg Nenashev commented on JENKINS-51326 Re: JEP-200 long data type rejected after upgrade to 2.107.3 https://github.com/jenkinsci/jenkins/pull/3446 is blocked by Jesse Glick due to the lack of reproducible scenario. I will close the pull request. If anybody else hits this issue, please feel free to take over the PR and to get it over the line. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51326) JEP-200 long data type rejected after upgrade to 2.107.3
Title: Message Title Oleg Nenashev stopped work on JENKINS-51326 Change By: Oleg Nenashev Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40723) Built Dockerfile images are never removed
Title: Message Title Brian J Murrell edited a comment on JENKINS-40723 Re: Built Dockerfile images are never removed [~allanlewis_youview] What's an example of _some-tag-i-understand_? Is it the same for every run of a given job, or is there some kind of serialiser in there so that you know which is the latest, etc.? Doesn't deleting all of the Jenkins produced hashy type tags mean that Jenkins won't be able to find an image to re-use for a future run of a job where the Dockerfile has not changed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40723) Built Dockerfile images are never removed
Title: Message Title Brian J Murrell commented on JENKINS-40723 Re: Built Dockerfile images are never removed Allan Lewis What's an example of some-tag-i-understand? Is it the same for every run of a given job, or is there some kind of serialiser in there so that you know which is the latest, etc.? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55463) Summay report plugin failed to transfer xml to html
Title: Message Title Lorenz Schumann commented on JENKINS-55463 Re: Summay report plugin failed to transfer xml to html I experience the same issue and would love to get this fixed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55845) Unable to login to jenkins using console
Title: Message Title Harendra Yadav created an issue Jenkins / JENKINS-55845 Unable to login to jenkins using console Issue Type: Bug Assignee: Rick Components: alauda-devops-pipeline-plugin, github-plugin Created: 2019-01-29 17:40 Environment: Its installed in My local laptop with Jenkins 2.107.3 Labels: jenkins Priority: Critical Reporter: Harendra Yadav Hi, I am new to Jenkins & trying to learn it. In process of that I have installed Jenkins in my local system & now I am unable to lunch the URL as getting below error after using username/password. URL: http://localhost:8080/jenkins HTTP ERROR 404 Problem accessing /jenkins. Reason: Not Found Powered by Jetty:// 9.4.z-SNAPSHOT Add Comment
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title Jesse Glick commented on JENKINS-44860 Re: Disable masking of usernames why wouldn't a user just update their secret to just secret text if they need to hardcode the username? In some cases, you cannot, because the credentials are also being used by other plugins which expect username/password. I have a mind to develop a full fix for this at some point, but it is on my back burner. Will likely also need dedicated support in pipeline-model-definition-plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55844) Scons plugin does not mark build status failed for non-zero script result
Title: Message Title Jay Jones created an issue Jenkins / JENKINS-55844 Scons plugin does not mark build status failed for non-zero script result Issue Type: Bug Assignee: Gregory Boissinot Attachments: image-2019-01-29-09-26-18-946.png, image-2019-01-29-09-29-59-458.png Components: scons-plugin Created: 2019-01-29 17:34 Environment: Scons plugin Release 0.4 (May 24, 2011) Jenkins ver. 2.138.1 Windows Server 2012 R2 Labels: plugin Priority: Minor Reporter: Jay Jones Running a scons script that fails (non-zero return code) , the scons plugin does not update build status to failed: Running the same script using "Execute shell plugin" correctly updates build status to failed:
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Vivek Pandey started work on JENKINS-54126 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51326) JEP-200 long data type rejected after upgrade to 2.107.3
Title: Message Title Oleg Nenashev updated JENKINS-51326 Jenkins / JENKINS-51326 JEP-200 long data type rejected after upgrade to 2.107.3 Change By: Oleg Nenashev Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51326) JEP-200 long data type rejected after upgrade to 2.107.3
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51326 JEP-200 long data type rejected after upgrade to 2.107.3 Change By: Oleg Nenashev Labels: JEP-200 stalled-pr Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54313) null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186)
Title: Message Title James Nord closed an issue as Fixed Jenkins / JENKINS-54313 null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186) Change By: James Nord Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54313) null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186)
Title: Message Title James Nord updated JENKINS-54313 available in 0.11 or higher Jenkins / JENKINS-54313 null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186) Change By: James Nord Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55712) SocketTimeoutException with kubernetes pipelines
Title: Message Title Alexander Moiseenko commented on JENKINS-55712 Re: SocketTimeoutException with kubernetes pipelines Possibly duplicates JENKINS-53532 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title oeuftete commented on JENKINS-44860 Re: Disable masking of usernames I am not sure PR 54 addresses the spirit of the request. Or really solves anything... why wouldn't a user just update their secret to just secret text if they need to hardcode the username? There is value in storing the credential as a username and a password. Usernames are going to be things like "`jenkins`, `release`, `artifactory`, `git` and `user`" as the opener and commenters have noted. The workaround noted above does not address the types of problems the user name masking causes... I believe for most users, and certainly for me, these are issues with console log processing, e.g. 00:16:31.073 [Scala Compiler] [ERROR] Can't create blame requests for some affected files: 00:16:31.073 [Scala Compiler] [ERROR] - Skipping non-workspace file /home//workspace/somebuild/someFile.scala 00:16:31.073 [Scala Compiler] [ERROR] - Skipping non-workspace file /home//workspace/somebuild/someOtherFile.scala ... where `jenkins` was filtered out in the console log. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28896) Add ProxyTask class to simplify task
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28896 Add ProxyTask class to simplify task Change By: Oleg Nenashev Labels: api stalled-pr Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28896) Add ProxyTask class to simplify task
Title: Message Title Oleg Nenashev commented on JENKINS-28896 Re: Add ProxyTask class to simplify task https://github.com/jenkinsci/jenkins/pull/1736 was a pull request for that. It is stalled, so and everybody is welcome to take it over and to get it over the finish line Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Okay so just instance of jenkins from Jenkins.get() needs to be stored by that method. Am I correct? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28361) Queue.Task has no ExportedBean attribute, but it's being exported to API
Title: Message Title Oleg Nenashev commented on JENKINS-28361 Re: Queue.Task has no ExportedBean attribute, but it's being exported to API The task got stalled, everybody is welcome to take it from there Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28361) Queue.Task has no ExportedBean attribute, but it's being exported to API
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28361 Queue.Task has no ExportedBean attribute, but it's being exported to API Change By: Oleg Nenashev Labels: stalled-pr Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55825) Team Foundation Server plugin error "the cache file is not valid and cannot be loaded"
Title: Message Title Alberto Lopez commented on JENKINS-55825 Re: Team Foundation Server plugin error "the cache file is not valid and cannot be loaded" No exist file in path FATAL: The cache file C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Team Foundation\4.0\Cache Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55842) Exceptions should be sent to Sentry as messages
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55842 Exceptions should be sent to Sentry as messages Change By: Baptiste Mathus Sprint: Evergreen - Milestone 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Ramkumar Bangaru commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once In my case, I need it as my pipeline scripts need to branch out to different path based on the status and if the status is successful, based on the output of it. It makes a lot of sense to have both status and output returned by this function. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55842) Exceptions should be sent to Sentry as messages
Title: Message Title Baptiste Mathus updated JENKINS-55842 Jenkins / JENKINS-55842 Exceptions should be sent to Sentry as messages Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55842) Exceptions should be sent to Sentry as messages
Title: Message Title Baptiste Mathus started work on JENKINS-55842 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55842) Exceptions should be sent to Sentry as messages
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-55842
Exceptions should be sent to Sentry as messages
Change By:
Baptiste Mathus
We are currently sending Java exceptions to the Sentry backend by using {{raven.captureException}} instead of {{raven.captureMessage}}: {code:java}if (data.log.exception) { this.raven.captureException(new Error(data.log.message), errorData);} else { this.raven.captureMessage(data.log.message, errorData);}{code}This makes Sentry aggregate litterally all logs that have an exceptions associated into a single event. This is because doing the {{new Error(...}} we create an exception from the place it is, and it's always the same. So Sentry somewhat rightly sees those as the same. And unfortunately, given we had marked as ignored the "SmokeTestException" one, everything got ignored the same way until recently as I was looking for that specific SmokeTestException ignored on purpose. And only by chance I finally saw in the Events tab that many unrelated events were merged there... :facepalm: Example: The title of the Sentry issue: !issue-title.png|thumbnail! !screenshot-1.png|thumbnail! and the Events tab: !last events.png|thumbnail! h3. Expected behaviorExceptions should be sent like the rest. Using the message as the title, and the exception can stay as is currently.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55842) Exceptions should be sent to Sentry as messages
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55842 Exceptions should be sent to Sentry as messages Change By: Baptiste Mathus Attachment: last events.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Oleg Nenashev commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API I do not get the question, sorry. This issue is just about adding one Getter method for a single field Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55842) Exceptions should be sent to Sentry as messages
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55842 Exceptions should be sent to Sentry as messages Change By: Baptiste Mathus Attachment: issue-title.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55842) Exceptions should be sent to Sentry as messages
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55842 Exceptions should be sent to Sentry as messages Change By: Baptiste Mathus Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API I have a doubt that getter method in AbstractCIBase should be created which assigns all the values of parameters from Jenkins.get() right? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55843) Folders missed due to anonymization in the bundle
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-55843 Folders missed due to anonymization in the bundle Issue Type: Bug Assignee: Ramon Leon Components: support-core-plugin Created: 2019-01-29 16:36 Priority: Major Reporter: Ramon Leon When the anonymization is enabled and the instance has an element with the name "/", or any other name containing the slash, the folders in the bundle are missed and instead of that, files are generated. It's possible to have such a name, for example with labels. "/", "a/b", ... In the zip, you should have: jenkins-root-configuration-files/build-failure-analyzer.xml But you get: jenkins-root-configuration-files*user_steep_lung*build-failure-analyzer.xml The / is replaced by user_steep_lung. Add Comment
[JIRA] (JENKINS-47107) p4cleanup/cleanup ignores 'true/false' flag
Title: Message Title Karl Wirth commented on JENKINS-47107 Re: p4cleanup/cleanup ignores 'true/false' flag Suggest this is fixed or 'true/false' is removed from 'cleanup' and documentation states this is a global setting (bubble text and docs). Upping to B to raise awareness. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47107) p4cleanup/cleanup ignores 'true/false' flag
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-47107 p4cleanup/cleanup ignores 'true/false' flag Change By: Karl Wirth Labels: P4_B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55826) how to delete workspace forcely?
Title: Message Title
Karl Wirth commented on JENKINS-55826
Re: how to delete workspace forcely?
Hi Hokwang Lee, I think you may be hitting the following bug - JENKINS-47107. The 'true' or 'false' is ignored and instead uses the global setting. Please check the global setting mentioned in the bug to confirm this is the problem. In my tests it doesn't matter if the workspace is 'locked'. If the global setting is set and I use 'cleanup' then the client is deleted. Example code:
pipeline {
agent { label "docker-slave" }
stages {
stage("Docker: Build")
{
steps {
echo "Hello from Docker"
p4sync charset: 'none', credential: 'JenkinsMaster',
populate: autoClean(delete: true, modtime: false,
parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'],
pin: '', quiet: false, replace: true, tidy: false),
source: templateSource('locked_template_ws')
sh "ls"
echo "Try and delete workspace"
p4cleanup false
}
}
}
}
Result in console output:
...cut...
[Pipeline] echo
Try and delete workspace
[Pipeline] cleanup
...cut...
P4 Task: remove client: jenkins-dockervm-18q1p9kkw-Pipeline_Locked_Template_Workspace-0
... p4 client -d jenkins-dockervm-18q1p9kkw-Pipeline_Locked_Template_Workspace-0 +
...cut...
Add Comment
[JIRA] (JENKINS-55416) 10s is not long enough to abort job
Title: Message Title Andrew Bayer updated JENKINS-55416 Jenkins / JENKINS-55416 10s is not long enough to abort job Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55842) Exceptions should be sent to Sentry as messages
Title: Message Title
Baptiste Mathus created an issue
Jenkins / JENKINS-55842
Exceptions should be sent to Sentry as messages
Issue Type:
Bug
Assignee:
Baptiste Mathus
Components:
evergreen
Created:
2019-01-29 16:07
Priority:
Blocker
Reporter:
Baptiste Mathus
We are currently sending Java exceptions to the Sentry backend by using raven.captureException instead of raven.captureMessage:
if (data.log.exception) {
this.raven.captureException(new Error(data.log.message), errorData);
} else {
this.raven.captureMessage(data.log.message, errorData);
}
This makes Sentry aggregate litterally all logs that have an exceptions associated into a single event. And unfortunately, given we had marked as ignored the "SmokeTestException" one, everything got ignored the same way until recently as I
Add Comment
[JIRA] (JENKINS-55153) Depends on EasySSLProtocolSocketFactory from git-client 2.0
Title: Message Title Oleg Nenashev commented on JENKINS-55153 Re: Depends on EasySSLProtocolSocketFactory from git-client 2.0 I would advice against using "org.apache.commons.httpclient" in new plugins at all. We keep it in the core for compatibility reasons only. https://github.com/jenkinsci/apache-httpcomponents-client-4-api-plugin should be used in plugins. Although it might be possible to integrate this class and to release Jenkins core with a patch, it won't help with previous LTS baselines. I recommend updating the plugin to use the new Http Client Library from the API plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37998) Warning log "no flow execution found for pipelinejob #1"
Title: Message Title Reinhold Füreder commented on JENKINS-37998 Re: Warning log "no flow execution found for pipelinejob #1" Jesse Glick Thanks for giving me hope Frankly I must admit that I am not so sure anymore about the "without [...] or whatever potentially unusual actions", because it does not happen at the moment for the latest builds seemingly; and a small reproducer with just "push button deployment (input step wrapped into timeout)" also failed to produce these warning logs ;-( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52112) Private Gitea repositories are not visible
Title: Message Title Kimon Hoffmann commented on JENKINS-52112 Re: Private Gitea repositories are not visible I'm also affected by this issue. While I initially assumed this being an issue on the gitea side (see: https://github.com/go-gitea/gitea/issues/5310), I'm now convinced that this is an issue with the Jenkins plugin, because the above mentioned issue has been fixed with Gitea v1.6.1 and the error persists. Manual verification supports this assumption, since https://gitea.server/api/v1/orgs/organization-name/repos returns the expected result for v1.6.1 ff. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54956) Github merge refs not working correctly
Title: Message Title Thomas Riccardi commented on JENKINS-54956 Re: Github merge refs not working correctly We encountered the same issue. After 5h on github.com the `/merge` ref is still unavailable it seems... The only workaround was to create a new PR. I tested: closing/reopening pushing new commits waiting 4h According to github it should eventually converge, maybe we should loop wait on jenkins side? But 4h is long, maybe there is a deadlock on github side when on github the branch is protected by waiting for jenkins CI status? Suggestion: at least the jenkins plugin should log something different than `‘Jenkinsfile’ not found`. Maybe an explicit explanation linking to here, and document the workaround: create a new PR. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title
Christopher Sullivan updated an issue
Jenkins / JENKINS-32402
Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs
Change By:
Christopher Sullivan
Comment:
I worked around this issue by using the [Authorize Project plugin|https://wiki.jenkins.io/display/JENKINS/Authorize+Project+plugin]. Instead of passing the credentials from the upstream job, I set the {{defaultValue}} of the parameter instead to globally scoped credentials.For build "Authorization" (enabled by Authorize Project), I set the job to run as a user with access to the global credentials (I would have used credentials scoped to the user only, but you can't use these as default values). When selecting "Build with Parameters" as any other user, only the user scoped credentials are available.Other users can still pass parameters to the job and successfully run it if they have the correct credentials.- If they try to run the job without specifying their own credentials, they can not access the default credentials and the job fails as desired.- (still working on restricting access to the credentials)When initiated by timer, it uses the default globally scoped credentials and successfully runs.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50365) reload pipeline script without executing the job
Title: Message Title Jonathan McCall commented on JENKINS-50365 Re: reload pipeline script without executing the job How is this fixed? I do not see a link to a closed issue that addresses the problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title jlpinardon edited a comment on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Dear all,I want to add here a user experience. The team for which I setup the CI are really in a trouble when they see a totally yellow pipeline. They don't want to make the effort to check each stage one by one to find which is OK and which is not. I can understand that, and .. .well... users or customers are always right, isn't it ? I am afraid that the proposed stage view, with a simple red note will not help. Even if a green note is added for stage with status SUCCESS.In such a situation, have in mind that users don't want to adopt the pipeline. It is a real showstopper show-stopper . And actually, they are currently asking me to come back to something which breaks the pipeline concept._So, I don't know what is the level of complexity, but to have green (or blue) color for stages ended with success, red for NOK ones and yellow for Unstable stages would be nothing else than a must have._ That will really be user friendly and avoid headache for CI guys that must battle against upset users ;). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Carsten Hilber updated an issue Jenkins / JENKINS-55836 Unable to delete workspace due to locked git .pack file Change By: Carsten Hilber Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title jlpinardon edited a comment on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Dear all,I want to add here a user experience.The team for which I setup the CI are really in a trouble when they see a totally yellow pipeline. They don't want to make the effort to check each stage one by one to find which is OK and which is not.I can understand that, and .. .well... users or customers are always right, isn't it ?I am afraid that the proposed stage view, with a simple red note will not help. Even if a green note is added for stage with status SUCCESS.In such a situation, have in mind that users don't want to adopt the pipeline. It is a real showstopper. And actually, they are asking me to come back to something which breaks the pipeline concept. So _So , I don't know what is the evel level of complexity, but to have green (or blue) color for stages ended with success, red for NOK ones and yellow dor for Unstable stage stages would be nothing else than a must have. _ That will really be user friendly and avoid headache for CI guys that must battle agains against upset users ;). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Daniel Beck assigned an issue to Unassigned Jenkins / JENKINS-55836 Unable to delete workspace due to locked git .pack file Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55841) Define custom “Publish JUnit test result report” according a specific Spring Profile(s)
Title: Message Title Manuel Jordan created an issue Jenkins / JENKINS-55841 Define custom “Publish JUnit test result report” according a specific Spring Profile(s) Issue Type: Improvement Assignee: Unassigned Components: junit-plugin, junit-realtime-test-reporter-plugin Created: 2019-01-29 14:33 Labels: plugin configuration Priority: Minor Reporter: Manuel Jordan The goal is configure manually Jenkins to indicate where to create the result reports according a specific set of profile(s). For example one for jdbc and other for jpa, thus I am able to see the time taken for each technology to execute the set of @Tests. Consider the case for multiple profiles, if I use jdbc,mysql and jdbc,h2, I need the result reports in two directories, if for jdbc-mysql and jdbc-h2 respectively. For more details please see: * Jenkins: define custom “Publish JUnit test result report” according a specific Spring Profile(s) Thank you. Add Comment
[JIRA] (JENKINS-53445) NPE and JVM Version not shown for Java 11
Title: Message Title Baptiste Mathus updated JENKINS-53445 Jenkins / JENKINS-53445 NPE and JVM Version not shown for Java 11 Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Released As: 2.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55822) Commits to base branches (i.e. master) causes PR build storm
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-55822 Commits to base branches (i.e. master) causes PR build storm Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37998) Warning log "no flow execution found for pipelinejob #1"
Title: Message Title Jesse Glick commented on JENKINS-37998 Re: Warning log "no flow execution found for pipelinejob #1" Not sure what the root cause is in your case, but FYI some variant of PR 3 would likely fix this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51770) Unable to find credential
Title: Message Title Matthew Winfield commented on JENKINS-51770 Re: Unable to find credential John Westcott should multiple credential support be available in version 0.9.1? Also how would do you specify multiple credentials in a pipeline job? I currently have a use case where I need to define 2 credentials for a job that I am trying to run from Jenkins with this plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51770) Unable to find credential
Title: Message Title Matthew Winfield edited a comment on JENKINS-51770 Re: Unable to find credential [~johnwestcottiv] should multiple credential support be available in version 0.9.1?Also how would do you specify multiple credentials in a pipeline job? I currently have a use case where I need to define 2 credentials for a job that I am trying to run from Jenkins with this plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
