[JIRA] (JENKINS-55969) missing changelog for 2.163
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-55969 missing changelog for 2.163 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-05 07:55 Priority: Minor Reporter: Pavel Kudrys Hi guys, It seems there is missing changelog for 2.163? I'm not comfortable installing new version, without knowing what's new or different BTW, Jenkins changelog is often released few hours behind the actual Jenkins release? Is there a problem with your release mechanism or the changelog is published manually? Thanks. Add Comment
[JIRA] (JENKINS-55950) Remember me causes excessive requests to LDAP Server after changing passwords
Title: Message Title Vladimir Zdravkovic commented on JENKINS-55950 Re: Remember me causes excessive requests to LDAP Server after changing passwords Also forgot to mention that we are running the latest version: 2.163 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-55968) Facing Error Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin/
Title: Message Title Parimal Jaldawar updated an issue Jenkins / JENKINS-55968 Facing Error Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin//TDConnectivity_index.html Change By: Parimal Jaldawar Environment: Jenkins User ID: adminPassword: 3d17d3105ec342a4a6c117a3f7d465ceJob: HPALM Dear sir, we are trying to execute the Microfocus ALM test with the help of jenkins.I have shared the Jenkins credentials with you. Jenkins Version: 2.163HP ALM version: 12.50Env: RIL domainAppreciate your help to resolve the problem. Started by user [admin|http://localhost:8080/user/admin]Building in workspace C:\Program Files (x86)\Jenkins\workspace\HPALM[HPALM] $ "C:\Program Files (x86)\Jenkins\workspace\HPALM\HpToolsLauncher.exe" -paramfile props05022019123929426.txt"Started..."Timeout is set to: 30Run mode is set to: RUN_LOCALStarting test set executionTest set name: ENP_Execution_Release_Cycle_Jan_2019, Test set id: 512Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: [http://10.128.22.145:8080/qcbin//TDConnectivity_index.html]Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURERecording test resultsRunResultRecorder: didn't find any test results to recordFinished: FAILURE Add Comment
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Yair Ogen commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step For me adding an empty non-build step - doesn't solve the issue. I see links but only after the job was completed (either success or failure) 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Hari Ananthan commented on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
Thanks a lot Josh. Here is a testcase and some pictures to illustrate the bug in case the description wasn't clear. P1_1 and P1_2 show links, but P2 doesn't. I am getting around now by simply adding a dummy "stage" before P2 in that branch of the parallel stage. pipeline { agent any stages { stage('Parallel Stage') { parallel { stage('P1') { stages { stage('P1_1') { steps { build job: 'child', parameters: [[$class: 'StringParameterValue', name: 'STAGE', value: 'P1_1']] } } stage('P1_2') { steps { build job: 'child', parameters: [[$class: 'StringParameterValue', name: 'STAGE', value: 'P1_2']] } } } } stage('P2') { steps \{ build job: 'child', parameters: [[$class: 'StringParameterValue', name: 'STAGE', value: 'P2']] } } } } } }
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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Hari Ananthan updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Hari Ananthan Attachment: P1_1.JPG Attachment: P1_2.JPG Attachment: P2.JPG 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-55968) Facing Error Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin/
Title: Message Title Parimal Jaldawar commented on JENKINS-55968 Re: Facing Error Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin//TDConnectivity_index.html Name : Parimal Jaldawar Contact details: +91-7718851983 Company: Reliance Industries Ltd (Navi Mumbai) India 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-55968) Facing Error Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin/
Title: Message Title Parimal Jaldawar created an issue Jenkins / JENKINS-55968 Facing Error Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin//TDConnectivity_index.html Issue Type: Bug Assignee: Daniel Gront Attachments: Jenkins Issue.png Components: hp-application-automation-tools-plugin Created: 2019-02-05 07:16 Environment: Jenkins User ID: admin Password: 3d17d3105ec342a4a6c117a3f7d465ce Job: HPALM Priority: Critical Reporter: Parimal Jaldawar Started by user admin Building in workspace C:\Program Files (x86)\Jenkins\workspace\HPALM [HPALM] $ "C:\Program Files (x86)\Jenkins\workspace\HPALM\HpToolsLauncher.exe" -paramfile props05022019123929426.txt "Started..." Timeout is set to: 30 Run mode is set to: RUN_LOCAL Starting test set execution Test set name: ENP_Execution_Release_Cycle_Jan_2019, Test set id: 512 Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin//TDConnectivity_index.html Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE Recording test results RunResultRecorder: didn't find any test results to record Finished: FAILURE
[JIRA] (JENKINS-55859) jira-trigger-plugin not triggering build after creating issue
Title: Message Title Govind Chaudhari edited a comment on JENKINS-55859 Re: jira-trigger-plugin not triggering build after creating issue Not an Issue , since plugin only support issue_update and comments :PThe issue already raised for Proxy problem. [~ceilfors] * _Note:: Why_ _Why_ does _the plugin not support issue_creation event?_* 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-55859) jira-trigger-plugin not triggering build after creating issue
Title: Message Title Govind Chaudhari closed an issue as Not A Defect Not an Issue The issue already raised for Proxy problem. Note:: Why does the plugin not support issue_creation event? Jenkins / JENKINS-55859 jira-trigger-plugin not triggering build after creating issue Change By: Govind Chaudhari Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55556) EC2 unable to retrieve private IP (+ other buggy behaviour)
Title: Message Title Victor Chavez commented on JENKINS-6 Re: EC2 unable to retrieve private IP (+ other buggy behaviour) On Jenkins 2.150.2 EC2 plugin 1.42 we get this behavior intermittently. We oscillate between this error and the error in JENKINS-55639. With the null:22 error we additionally get the horrible side effect that the script continues to connect to the master node and runs the init script. Just by chance the init script I had in place wasn't destructive to the master. Now I have a little addition to my init script at the top: master=jenkins-master host=$(hostname -s) if [ $host == $master ] then echo "This is the master node! Exiting!!!" exit 1 else echo "Server is a spot node, apparently. Better yet, it's NOT the master node. Continuing..." fi 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-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Victor Chavez edited a comment on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id On Jenkins 2.150.2 EC2 plugin 1.42 we get this behavior intermittently. We oscillate between this and JENKINS-6. 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-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Victor Chavez commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id On 1.42 we get this behavior intermittently. We oscillate between this and JENKINS-6. 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-55967) SSH plugin injects null variable and attempts to run
Title: Message Title
Tom Farmer created an issue
Jenkins / JENKINS-55967
SSH plugin injects null variable and attempts to run
Issue Type:
Bug
Assignee:
Unassigned
Components:
ssh-plugin
Created:
2019-02-05 01:11
Environment:
2.6.1
Labels:
plugin
Priority:
Minor
Reporter:
Tom Farmer
It is putting an invalid command for every job configured to use the plugin: 20:00:38 [EnvInject] - Loading node environment variables. 20:00:38 Building on master in workspace /var/jenkins_home/workspace/mount-efs 20:00:38 [SSH] script: 20:00:38 ="" 20:00:38 JENKINS_USER_PASSWORD=** 20:00:38 20:00:38 echo ${JENKINS_USER_PASSWORD} | sudo -S – /usr/local/bin/mount_efs 20:00:38 20:00:38 [SSH] executing... 20:00:38 bash: =: command not found 20:00:38 [sudo] password for : EFS is already mounted. Exiting. 20:00:39 20:00:39 [SSH] completed 20:00:39 [SSH] exit-status: 0 20:00:39 20:00:40 Finished: SUCCESS
[JIRA] (JENKINS-55497) BlueOcean Pipeline View sometimes shows No Changes
Title: Message Title Stuart Rowe updated an issue Jenkins / JENKINS-55497 BlueOcean Pipeline View sometimes shows No Changes Change By: Stuart Rowe Comment: It seems that there is a cached run from before the changeset was populated. This data is refreshed when the 'job_run_ended' event is handled. 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Vlad Uros commented on JENKINS-55194 Re: Add logLevel to support debugging and also reduce default excessive logging Thanks for the explanation Naresh. We should be fine to close this now. Ideally for me would be not to see for example 9b30df7c-86d7-4bdf-a5ed-f956a1286686 in console output but as you said, it is some other library that is causing it. 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald reopened an issue I'll look into this a bit today. Might be more difficult than it seems tho. Fairly warned, be ye, says I. I'll keep you guys posted. Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Resolution: Fixed 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Naresh Rayapati commented on JENKINS-55194 Re: Add logLevel to support debugging and also reduce default excessive logging Vlad Uros so what are you expecting.. or what is the use case that has prompted you to ask this question and reopen this JIRA? 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Naresh Rayapati commented on JENKINS-55194 Re: Add logLevel to support debugging and also reduce default excessive logging Yes, you are right, and that is an expected behavior, sudo command prompts for password, so this plugin is opening up a unique session to interact with actual shell command, and those lines are related to that session. For the normal command we just logon to box and execute the command, but for the sudo commands we need to logon to box and up on executing the sudo command which prompts for password again, requires someone manually key in the password, which isn't ideal in case of automation and also Jenkins doesn't support shell interactions. 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-17196) Add an action that allows to reset the reference build
Title: Message Title Ulli Hafner updated JENKINS-17196 Jenkins / JENKINS-17196 Add an action that allows to reset the reference build Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22526) Health threshold rebaseline command
Title: Message Title Ulli Hafner updated JENKINS-22526 Jenkins / JENKINS-22526 Health threshold rebaseline command Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55966) Jenkins: No test Result were sent to Qtest
Title: Message Title Jose Tintaya created an issue Jenkins / JENKINS-55966 Jenkins: No test Result were sent to Qtest Issue Type: Bug Assignee: QASymphony QASymphony Attachments: log_RFT_Jenkins_Qtest.txt, rft-jenkins-2.0.hpi Components: qtest-plugin Created: 2019-02-04 20:02 Environment: Windows 10 Jenkins ver. 2.162 Rational Functional Tester 9.2.1 Labels: qtest jenkins RFT Priority: Minor Reporter: Jose Tintaya i configured Jenkins (v2.162) to execute an script from Rational Functional Tester (i used Plug in rft-jenkins-2.0.hpi). Later, i configured Jenkins to send the result of the script execution to Qtest. (i used QTestPlugin 1.4.0) When i run the job in jenkins, it execute the script (The Console Output show that the "Test Result = Pass". However, During the 'Post-Build Action' for 'Submit JUnit Test Results to qTest', it show a warning message that indicate that couln't find testResult [qTest] [WARN] No testResult action was added to project. [qTest] [WARN] No JUnit test result found. Subsequently the qTest Plugin will fail to upload a result to our server.
[JIRA] (JENKINS-55939) git-plugin v4.0.0-rc not returning "lastBuiltRevision" in BuildData
Title: Message Title Justin Pihony commented on JENKINS-55939 Re: git-plugin v4.0.0-rc not returning "lastBuiltRevision" in BuildData We just ran into this issue and it is a showstopper for us. It seems that if you use a regex then it causes each push to re-find all matching builds and re-build them all. 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-55965) Build data could not be found for git SCM
Title: Message Title java budd updated an issue Jenkins / JENKINS-55965 Build data could not be found for git SCM Change By: java budd Priority: Minor Major 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-55965) Build data could not be found for git SCM
Title: Message Title
java budd updated an issue
Jenkins / JENKINS-55965
Build data could not be found for git SCM
Change By:
java budd
Build statuses are not working for any of my pipeline jobs due to an empty list being returned from getCommitRepoMap ([https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/blob/master/src/main/java/org/jenkinsci/plugins/bitbucket/scm/GitScmAdapter.java# L50|https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/blob/master/src/main/java/org/jenkinsci/plugins/bitbucket/scm/GitScmAdapter.java# L56])I previously noticed that this warning would sometimes occur and statuses wouldn't be updated, but I am now getting this warning on every pipeline build for 2 different projects.{code:java}Feb 04, 2019 12:19:43 PM org.jenkinsci.plugins.bitbucket.scm.GitScmAdapter getCommitRepoMapWARNING: Build data could not be found{code}If there is any more information I can provide please let me know, right now I'm still trying to figuring out what caused 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title java budd commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults yeah after looking into it further I think you're right, it just looks like it's related 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-55965) Build data could not be found for git SCM
Title: Message Title
java budd updated an issue
Jenkins / JENKINS-55965
Build data could not be found for git SCM
Change By:
java budd
Build statuses are not working for any of my pipeline jobs due to an empty list being returned from getCommitRepoMap ( [ https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/blob/master/src/main/java/org/jenkinsci/plugins/bitbucket/scm/GitScmAdapter.java#L56 ] )I previously noticed that this warning would sometimes occur and statuses wouldn't be updated, but I am now getting this warning on every pipeline build for 2 different projects.{code:java}Feb 04, 2019 12:19:43 PM org.jenkinsci.plugins.bitbucket.scm.GitScmAdapter getCommitRepoMapWARNING: Build data could not be found{code}If there is any more information I can provide please let me know, right now I'm still trying to figuring out what version update caused 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-55965) Build data could not be found for git SCM
Title: Message Title java budd created an issue Jenkins / JENKINS-55965 Build data could not be found for git SCM Issue Type: Bug Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2019-02-04 19:36 Environment: CentOS: Linux staging.lan 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Jenkins: 1.6.3 Pipeline: 2.6 Priority: Minor Reporter: java budd Build statuses are not working for any of my pipeline jobs due to an empty list being returned from getCommitRepoMap (https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/blob/master/src/main/java/org/jenkinsci/plugins/bitbucket/scm/GitScmAdapter.java#L56) I previously noticed that this warning would sometimes occur and statuses wouldn't be updated, but I am now getting this warning on every pipeline build for 2 different projects. Feb 04, 2019 12:19:43 PM org.jenkinsci.plugins.bitbucket.scm.GitScmAdapter getCommitRepoMap WARNING: Build data could not be found If there is any more information I can provide please let me know, right now I'm still trying to figuring out what version update caused this.
[JIRA] (JENKINS-55964) Debian Package for Jenkins_2.163_all.deb 404's on ubuntu download
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55964 Debian Package for Jenkins_2.163_all.deb 404's on ubuntu download Change By: Oleg Nenashev Labels: installer jenkins 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Vlad Uros reopened an issue Hello Naresh. Sorry for opening this again I tested something and I am a bit confused. I executed couple of commands with and without sudo. 1. working command without sudo sshCommand remote: remote, command: "echo regards" Output is: regards 2. working command with sudo sshCommand sudo: true,remote: remote, command: "echo regards" Output is: 17362243-a06c-4421-bfb1-c15684b3ffc0 regards 3. wrong command with sudo sshCommand sudo: true,remote: remote, command: "some_command" Output is: 9b30df7c-86d7-4bdf-a5ed-f956a1286686 sudo: some_command: command not found I caught exception and it is: org.hidetake.groovy.ssh.session.BadExitStatusException: Command returned exit status 1: sudo -S -p '9b30df7c-86d7-4bdf-a5ed-f956a1286686' some_command So looks like if I use remote.logLevel = 'OFF' remote.appendName = false and sudo is set to false (default) output is not showing unique id. With sudo set to true we see it in output. Looking at exception and how sudo is executed options for sudo are: -p prompt The -p (prompt) option allows you to override the default password prompt and use a custom one. -S The -S (stdin) option causes sudo to read the password from the standard input instead of the terminal device. The password must be followed by a newline character. sudo -S -p should mean sending password, so 9b30df7c-86d7-4bdf-a5ed-f956a1286686 is somehow related to sudo and password. And as you see in output there is 9b30df7c-86d7-4bdf-a5ed-f956a1286686 which is same as in sudo -S -p '9b30df7c-86d7-4bdf-a5ed-f956a1286686' Maybe I am wrong in this. Thanks, Vlad Jenkins / JENKINS-55194 Add logLevel to support debugging and also reduce default excessive logging Change By: Vlad Uros Resolution: Fixed Status: Closed Reopened Add Comment
[JIRA] (JENKINS-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Vlad Uros updated an issue Jenkins / JENKINS-55194 Add logLevel to support debugging and also reduce default excessive logging Change By: Vlad Uros Comment: Hello Naresh.Sorry for opening this again I tested something and I am a bit confused. I executed couple of commands with and without sudo. 1. working command without sudo sshCommand remote: remote, command: "echo regards" Output is: regards2. working command with sudo sshCommand sudo: true,remote: remote, command: "echo regards" Output is: 17362243-a06c-4421-bfb1-c15684b3ffc0regards 3. wrong command with sudo sshCommand sudo: true,remote: remote, command: "some_command" Output is: 9b30df7c-86d7-4bdf-a5ed-f956a1286686sudo: some_command: command not foundI caught exception and it is:org.hidetake.groovy.ssh.session.BadExitStatusException: Command returned exit status 1: sudo -S -p '9b30df7c-86d7-4bdf-a5ed-f956a1286686' some_command So looks like if I use remote.logLevel = 'OFF'remote.appendName = falseand sudo is set to false (default) output is not showing unique id.With sudo set to true we see it in output. Looking at exception and how sudo is executed options for sudo are:-p prompt The -p (prompt) option allows you to override the default password prompt and use a custom one.-S The -S (stdin) option causes sudo to read the password from the standard input instead of the terminal device. The password must be followed by a newline character. sudo -S -p should mean sending password, so 9b30df7c-86d7-4bdf-a5ed-f956a1286686 is somehow related to sudo and password.And as you see in output there is 9b30df7c-86d7-4bdf-a5ed-f956a1286686 which is same as in sudo -S -p '9b30df7c-86d7-4bdf-a5ed-f956a1286686' Maybe I am wrong in this. Thanks,Vlad Add Comment
[JIRA] (JENKINS-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Vlad Uros commented on JENKINS-55194 Re: Add logLevel to support debugging and also reduce default excessive logging Hello Naresh. Sorry for opening this again I tested something and I am a bit confused. I executed couple of commands with and without sudo. 1. working command without sudo sshCommand remote: remote, command: "echo regards" Output is: regards 2. working command with sudo sshCommand sudo: true,remote: remote, command: "echo regards" Output is: 17362243-a06c-4421-bfb1-c15684b3ffc0 regards 3. wrong command with sudo sshCommand sudo: true,remote: remote, command: "some_command" Output is: 9b30df7c-86d7-4bdf-a5ed-f956a1286686 sudo: some_command: command not found I caught exception and it is: org.hidetake.groovy.ssh.session.BadExitStatusException: Command returned exit status 1: sudo -S -p '9b30df7c-86d7-4bdf-a5ed-f956a1286686' some_command So looks like if I use remote.logLevel = 'OFF' remote.appendName = false and sudo is set to false (default) output is not showing unique id. With sudo set to true we see it in output. Looking at exception and how sudo is executed options for sudo are: -p prompt The -p (prompt) option allows you to override the default password prompt and use a custom one. -S The -S (stdin) option causes sudo to read the password from the standard input instead of the terminal device. The password must be followed by a newline character. sudo -S -p should mean sending password, so 9b30df7c-86d7-4bdf-a5ed-f956a1286686 is somehow related to sudo and password. And as you see in output there is 9b30df7c-86d7-4bdf-a5ed-f956a1286686 which is same as in sudo -S -p '9b30df7c-86d7-4bdf-a5ed-f956a1286686' Maybe I am wrong in this. Thanks, Vlad 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
[JIRA] (JENKINS-55964) Debian Package for Jenkins_2.163_all.deb 404's on ubuntu download
Title: Message Title Stephen Byrnes created an issue Jenkins / JENKINS-55964 Debian Package for Jenkins_2.163_all.deb 404's on ubuntu download Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-04 18:39 Environment: Update to Jenkins on Ubuntu Labels: jenkins Priority: Trivial Reporter: Stephen Byrnes Err:1 https://pkg.jenkins.io/debian binary/ jenkins 2.163 404 The specified blob does not exist. E: Failed to fetch https://pkg.jenkins.io/debian/binary/jenkins_2.163_all.deb 404 The specified blob does not exist. https://pkg.jenkins.io/debian/binary/jenkins_2.163_all.deb -> BlobNotFound The specified blob does not exist. RequestId:aabe193d-501e-011b-33b8-bcdd9300 Time:2019-02-04T18:38:58.1180354Z Add Comment
[JIRA] (JENKINS-55900) Java memory mishandling identified
Title: Message Title Yevhen Bulatnikov edited a comment on JENKINS-55900 Re: Java memory mishandling identified I have created pull request [https://github.com/jenkinsci/jenkins/pull/3878]I'm not sure why Jenkins cannot build it. I don't see anything wrong there. (Now I see in classic view hudson.remoting.RequestAbortedException. I'm not sure it is related to my changes.)I used ArrayDeque for my solution. I found it more suitable. Also I see in JProfiler there Float.valueOf() is used because of my changes. It allocates some memory, but much less than before.I think maybe it would be suitable to create own class that operates with primitive floats in same way as ArrayDeque ??? 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-55900) Java memory mishandling identified
Title: Message Title Yevhen Bulatnikov updated an issue Jenkins / JENKINS-55900 Java memory mishandling identified Change By: Yevhen Bulatnikov Priority: Trivial Minor 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Hari Ananthan edited a comment on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Build Link for jobs launched inside parallel stages would be most appreciated! Without this, we are kinda stuck having to open so many windows to track what's going on. Especially since many of our stages are propagate : false and/or wait: false. EDIT : Actually the exact bug is that Links don't show up if a parallel stage has *only one build.*If parallel stage has 2 or more builds in series, then the links show up. For non-parallel stages, the URL shows up, but only after the child build is finished. So another request - create the URL link while the job is running. Some of our jobs take many minutes or hours and so having a live link would be really really useful.Thank you! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55900) Java memory mishandling identified
Title: Message Title
Yevhen Bulatnikov edited a comment on JENKINS-55900
Re: Java memory mishandling identified
Oh, finally I see what's the point of creating new arrays constantly. {code:java}@CopyOnWriteprivate volatile float[] history;{code}Documentation of this annotation states: {code:java}Represents fields that are protected for concurrency by the copy-on-write semantics.Fields marked by this annotation always holds on to an immutable collection. A change to the collection must be done by first creating a new collection object, making changes, then replacing the reference atomically.This allows code to access the field without synchronization, and greatly reduces the risk of dead-lock bugs.The field marked with this annotation usually needs to be marked as volatile.{code}So this is not so trivial to fix that I thought. I've closed my pull request for now.
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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Jesse Glick commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults java budd your issue is likely unrelated. 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-55900) Java memory mishandling identified
Title: Message Title Yevhen Bulatnikov commented on JENKINS-55900 Re: Java memory mishandling identified Oh, finally I see what's the point of creating new arrays constantly. @CopyOnWrite private volatile float[] history; Documentation of this annotation states: Represents fields that are protected for concurrency by the copy-on-write semantics. Fields marked by this annotation always holds on to an immutable collection. A change to the collection must be done by first creating a new collection object, making changes, then replacing the reference atomically. This allows code to access the field without synchronization, and greatly reduces the risk of dead-lock bugs. The field marked with this annotation usually needs to be marked as volatile. So this is not so trivial to fix that I thought. 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title java budd commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults This is not just a log spam issue, this is preventing the BitbucketBuildStatusNotifier plugin from updating build statuses, as the commit information does not exist. WARNING: Error storing the arguments for step: checkout org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDef aults at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:265) at org.jenkinsci.plugins.structs.describable.DescribableModel.(DescribableModel.java:144) at org.jenkinsci.plugins.structs.describable.DescribableModel.of(DescribableModel.java:114) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:294) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeListAndRecordMutation(ArgumentsActionImpl.java:242) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:313) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:311) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.(ArgumentsActionImpl.java:74) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:243) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:76) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) at sun.reflect.GeneratedMethodAccessor220.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[JIRA] (JENKINS-55923) CpsFlowExecution writes to logs after compression
Title: Message Title Steven Williams updated JENKINS-55923 This may have the same root cause as https://issues.jenkins-ci.org/browse/JENKINS-50199 We are on a slightly older version of the Pipeline Job plugin than the fix. Will test and soak on 2.25+ Jenkins / JENKINS-55923 CpsFlowExecution writes to logs after compression Change By: Steven Williams Status: Open Fixed but Unreleased Resolution: Incomplete 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-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Oleksandr Stovbenko commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata Downgrading versions of these plugins solved the issue: Git 4.0.0rc Git client 3.0.0rc 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Hari Ananthan commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Build Link for jobs launched inside parallel stages would be most appreciated! Without this, we are kinda stuck having to open so many windows to track what's going on. Especially since many of our stages are propagate : false and/or wait: false. For non-parallel stages, the URL shows up, but only after the child build is finished. So another request - create the URL link while the job is running. Some of our jobs take many minutes or hours and so having a live link would be really really useful. Thank you! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41902) readMavenPom / writeMavenPom does not preserve comments and formatting
Title: Message Title Oswaldo Diaz commented on JENKINS-41902 Re: readMavenPom / writeMavenPom does not preserve comments and formatting Same issue here, I'm using this plugin to update pom version automatically and when writing on pom it's using 2 spaces indentation instead of 4 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-55713) No agents created when using google compute engine and missing instance template entry
Title: Message Title
Tom Jennings commented on JENKINS-55713
Re: No agents created when using google compute engine and missing instance template entry
Deleting {{ }} from config.xml Fixed the scheduling issue I was having.
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-55941) Removing JAXB dependency from TFS-plugin
Title: Message Title Aniket Kadam commented on JENKINS-55941 Re: Removing JAXB dependency from TFS-plugin Sorry Carlos Rodríguez López I ran into this accidentally, completely up to you if you want to leave this or do it differently. Here's the PR I opened for it. https://github.com/jenkinsci/tfs-plugin/pull/220 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-55549) CppCheck Cannot load sidepanel.jelly
Title: Message Title T S commented on JENKINS-55549 Re: CppCheck Cannot load sidepanel.jelly Same issue here. Windows Server 2016 Jenkins 2.150.2 Cppcheck plugin 1.24 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-55962) Plugin Compat Tester should not be using Module patches starting from 2.163
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-55962 Plugin Compat Tester should not be using Module patches starting from 2.163 Issue Type: Improvement Assignee: Unassigned Components: plugin-compat-tester Created: 2019-02-04 15:54 Priority: Minor Reporter: Oleg Nenashev JENKINS-55681 is integrated into Jenkins 2.163, so there is no need to use external module inclusions in this version. Moreover, such inclusion may hide particular issues Add Comment This message was
[JIRA] (JENKINS-55961) Nodejs plugin installs wrong platform package when using parallel pipeline
Title: Message Title
Philip Adams created an issue
Jenkins / JENKINS-55961
Nodejs plugin installs wrong platform package when using parallel pipeline
Issue Type:
Bug
Assignee:
Nikolas Falco
Attachments:
darwin_on_windows.jpg, linux_on_mac_and_windows.jpg, windows_no_cmd.jpg
Components:
nodejs-plugin
Created:
2019-02-04 15:51
Environment:
Jenkins 2.162 NodeJS plugin 1.2.7 Latest pipeline plugins as of 04/02/2019 Jenkins Tool config: NodeJs version 8.15.0 - Install automatically - Global packages = "yarn"
Priority:
Major
Reporter:
Philip Adams
Hey, We have a Pipeline job that runs steps in parallel across three nodes - one Ubuntu, one Mac, one Windows. Some time recently (we're not exactly sure when), it started downloading the wrong node package to the machines, e.g. downloading "node-v8.15.0-darwin-x64.tar.gz" to the Windows machine. Even when it does (randomly?) select the correct package, we're unable to build, since the windows logic in NodeJSInstaller doesn't fire, so it uses an incorrect command. I've cut everything down to a minimal Jenkinsfile that reproduces the issue for us. See screenshots for the console output.
nodeLinux = 'ubuntu64-normal-amazon-1'
nodeWin = 'windows-office-devops'
nodeMac = 'devops-osx-slave'
nodejsInstallation = 'node8'
pipeline {
agent { label 'master' }
stages {
stage('Test') {
parallel {
[JIRA] (JENKINS-55950) Remember me causes excessive requests to LDAP Server after changing passwords
Title: Message Title Robert Ilg edited a comment on JENKINS-55950 Re: Remember me causes excessive requests to LDAP Server after changing passwords Yeah, that's a detail I forgot do to add. It's exactly the way you describe it. 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-55960) Missing DeclarativePipeline podTemplate parameters
Title: Message Title Mikhail Chinkov created an issue Jenkins / JENKINS-55960 Missing DeclarativePipeline podTemplate parameters Issue Type: Bug Assignee: Mikhail Chinkov Components: kubernetes-plugin Created: 2019-02-04 15:45 Environment: Jenkins: 2.138.2 Kubernetes-plugin: 1.12.4 Labels: plugin kuberentes declarative declarative-variable-and-method-resolution Priority: Major Reporter: Mikhail Chinkov The issue is that the DeclarativePipeline support on kubernetes-plugin is: Not complete - some options are missing Not aligned with Documentation - by reading docs, I assume I can use all options in declarativePipeline Example: I'm trying to introduce `slaveConnectTimeout` in my pipeline, because 100 is ridiculously small if you want to pre-warm caches or so. Here is what I get WorkflowScript: 8: Invalid config option "slaveConnectTimeout" for agent type "kubernetes". Valid config options are [activeDeadlineSeconds, cloud, containerTemplate, containerTemplates, defaultContainer, idleMinutes, inheritFrom, instanceCap, label, nodeSelector, serviceAccount, workingDir, yaml, yamlFile] @ line 8, column 13. slaveConnectTimeout 1800
[JIRA] (JENKINS-55950) Remember me causes excessive requests to LDAP Server after changing passwords
Title: Message Title Robert Ilg commented on JENKINS-55950 Re: Remember me causes excessive requests to LDAP Server after changing passwords Yeah, that's a detail I forgot do add. It's exactly the way you describe it. 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-55958) Allow executing additional action in timeout step before wrapped steps will be cancelled
Title: Message Title
Adam Gabryś updated an issue
Jenkins / JENKINS-55958
Allow executing additional action in timeout step before wrapped steps will be cancelled
Change By:
Adam Gabryś
It would be very useful to allow users to define additional steps which will be executed on timeout, but before the processes will be stopped. For example in our case we want to generate {{threaddump.log}} and {{dump.hprof}} files when the executed Java logic is frozen. It is possible to do it by using {{Time-out actions}} provided by {{Build Timeout}} plugin. Unfortunately, I cannot use it with Jenkins Declarative Pipelines.{code:java}timeout(time: 30, onTimeout: {sh """#!/bin/bashecho "Performing thread dump"for pid in \$(ps auxwwe | grep APPLICATION_ID | grep -v grep | grep BUILD_ID=${env.BUILD_ID} | awk '{print \$2}'); doecho "thread dump of \$pid"jstack \$pid > threaddump_\$pid.logdone"""}) {sh "mvn verify"}{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-55959) Archiving artifacts does not preserve execution permissions
Title: Message Title Richard Hillmann updated an issue Jenkins / JENKINS-55959 Archiving artifacts does not preserve execution permissions Change By: Richard Hillmann Archive/Unarchive artifacts removes the execution flag of generated binaries. I tried to archive a directory tree, so it might be related toSame problem than in JENKINS-13128. Actually it should be fixed with 2.120, but it still (or again?) does not work for me. 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-55959) Archiving artifacts does not preserve execution permissions
Title: Message Title Richard Hillmann updated an issue Jenkins / JENKINS-55959 Archiving artifacts does not preserve execution permissions Change By: Richard Hillmann Archive/Unarchive artifacts removes the execution flag of generated binaries. I tried to archive a directory tree, so it might be related toJENKINS-23645. Same problem than in JENKINS-13128. Actually it should be fixed with 2.120, but it still (or again?) does not work for me. 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-55959) Archiving artifacts does not preserve execution permissions
Title: Message Title Richard Hillmann created an issue Jenkins / JENKINS-55959 Archiving artifacts does not preserve execution permissions Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-04 15:39 Environment: amazonlinux: 2 Jenkins ver. 2.150.2 Priority: Minor Reporter: Richard Hillmann Archive/Unarchive artifacts removes the execution flag of generated binaries. Same problem than in JENKINS-13128. Actually it should be fixed with 2.120, but it still (or again?) does not work for me. Add Comment
[JIRA] (JENKINS-55958) Allow executing additional action in timeout step before wrapped steps will be cancelled
Title: Message Title
Adam Gabryś created an issue
Jenkins / JENKINS-55958
Allow executing additional action in timeout step before wrapped steps will be cancelled
Issue Type:
Improvement
Assignee:
Unassigned
Components:
workflow-basic-steps-plugin
Created:
2019-02-04 15:37
Priority:
Major
Reporter:
Adam Gabryś
It would be very useful to allow users to define additional steps which will be executed on timeout, but before the processes will be stopped. For example in our case we want to generate threaddump.log and dump.hprof files when the executed Java logic is frozen. It is possible to do it by using Time-out actions provided by Build Timeout plugin. Unfortunately, I cannot use it with Jenkins Declarative Pipelines.
timeout(time: 30, onTimeout: {
sh """#!/bin/bash
echo "Performing thread dump"
for pid in \$(ps auxwwe | grep APPLICATION_ID | grep -v grep | grep BUILD_ID=${env.BUILD_ID} | awk '{print \$2}'); do
echo "thread dump of \$pid"
jstack \$pid > threaddump_\$pid.log
done
"""
}) {
sh "mvn verify"
}
[JIRA] (JENKINS-55956) Remove JAXB dependency from timestamper plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55956 Remove JAXB dependency from timestamper plugin Change By: Baptiste Mathus Component/s: timestamper-plugin Component/s: notification-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-55957) Remove JAXB dependency from job-import plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55957 Remove JAXB dependency from job-import plugin Change By: Baptiste Mathus Component/s: job-import-plugin Component/s: notification-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-55957) Remove JAXB dependency from job-import plugin
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-55957 Remove JAXB dependency from job-import plugin Issue Type: Improvement Assignee: Unassigned Components: notification-plugin Created: 2019-02-04 15:33 Labels: fosdem2019 java11 newbie-friendly Priority: Trivial Reporter: Baptiste Mathus Starting with Java 9+, JAXB has been removed from the JDK. So it's a good thing to try and break/remove the dependency against from plugins who do not really use JAXB for its core feature (object de/serialization). (only used in tests for this plugin, so nothing critical) Acceptance criteria: https://github.com/jenkinsci/timestamper-plugin/search?q=javax.xml.bind_q=javax.xml.bind should yield nothing Add Comment
[JIRA] (JENKINS-55957) Remove JAXB dependency from job-import plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55957 Remove JAXB dependency from job-import plugin Change By: Baptiste Mathus Priority: Trivial Major 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-55957) Remove JAXB dependency from job-import plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55957 Remove JAXB dependency from job-import plugin Change By: Baptiste Mathus Starting with Java 9+, JAXB has been removed from the JDK. So it's a good thing to try and break/remove the dependency against from plugins who do not really use JAXB for its core feature (object de/serialization).(only used in tests for this plugin, so nothing critical)h3. Acceptance criteria:* https://github.com/jenkinsci/ timestamper job - import- plugin/search?q=javax.xml.bind_q=javax.xml.bind should yield nothing :) 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-55956) Remove JAXB dependency from timestamper plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55956 Remove JAXB dependency from timestamper plugin Change By: Baptiste Mathus Starting with Java 9+, JAXB has been removed from the JDK. So it's a good thing to try and break/remove the dependency against from plugins who do not really use JAXB for its core feature (object de/serialization). (only used in tests for this plugin, so nothing critical) h3. Acceptance criteria:* https://github.com/jenkinsci/ notification timestamper -plugin/search?q=javax.xml.bind_q=javax.xml.bind should yield nothing :) 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-55956) Remove JAXB dependency from timestamper plugin
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-55956 Remove JAXB dependency from timestamper plugin Issue Type: Improvement Assignee: Unassigned Components: notification-plugin Created: 2019-02-04 15:31 Labels: fosdem2019 java11 newbie-friendly Priority: Minor Reporter: Baptiste Mathus Starting with Java 9+, JAXB has been removed from the JDK. So it's a good thing to try and break/remove the dependency against from plugins who do not really use JAXB for its core feature (object de/serialization). Acceptance criteria: https://github.com/jenkinsci/notification-plugin/search?q=javax.xml.bind_q=javax.xml.bind should yield nothing Add Comment
[JIRA] (JENKINS-55955) Remove JAXB dependency from notification plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55955 Remove JAXB dependency from notification plugin Change By: Baptiste Mathus Starting with Java 9+, JAXB has been removed from the JDK. So it's a good thing to try and break/remove the dependency against from plugins who do not really use JAXB for its core feature (object de/serialization).https://github.com/jenkinsci/ performance notification -plugin/search?q=javax.xml.bind_q=javax.xml.bind shows the usage of JAXB. h3. Acceptance criteria:* https://github.com/jenkinsci/ performance notification -plugin/search?q=javax.xml.bind_q=javax.xml.bind should yield nothing :) 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-55956) Remove JAXB dependency from timestamper plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55956 Remove JAXB dependency from timestamper plugin Change By: Baptiste Mathus Priority: Minor Trivial 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-55955) Remove JAXB dependency from notification plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55955 Remove JAXB dependency from notification plugin Change By: Baptiste Mathus Component/s: notification-plugin Component/s: performance-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-55955) Remove JAXB dependency from notification plugin
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-55955 Remove JAXB dependency from notification plugin Issue Type: Improvement Assignee: Aniket Kadam Components: performance-plugin Created: 2019-02-04 15:30 Labels: fosdem2019 java11 newbie-friendly Priority: Minor Reporter: Baptiste Mathus Starting with Java 9+, JAXB has been removed from the JDK. So it's a good thing to try and break/remove the dependency against from plugins who do not really use JAXB for its core feature (object de/serialization). https://github.com/jenkinsci/performance-plugin/search?q=javax.xml.bind_q=javax.xml.bind shows the usage of JAXB. Acceptance criteria: https://github.com/jenkinsci/performance-plugin/search?q=javax.xml.bind_q=javax.xml.bind should yield nothing Add Comment
[JIRA] (JENKINS-55955) Remove JAXB dependency from notification plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55955 Remove JAXB dependency from notification plugin Change By: Baptiste Mathus Starting with Java 9+, JAXB has been removed from the JDK. So it's a good thing to try and break/remove the dependency against from plugins who do not really use JAXB for its core feature (object de/serialization). https://github.com/jenkinsci/notification-plugin/search?q=javax.xml.bind_q=javax.xml.bind shows the usage of JAXB. h3. Acceptance criteria:* https://github.com/jenkinsci/notification-plugin/search?q=javax.xml.bind_q=javax.xml.bind should yield nothing :) 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-55955) Remove JAXB dependency from notification plugin
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-55955 Remove JAXB dependency from notification plugin Change By: Baptiste Mathus Assignee: Aniket Kadam 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-55954) Remove unnecessary JAXB's DatatypeConverter usage
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55954 Remove unnecessary JAXB's DatatypeConverter usage Change By: Baptiste Mathus Labels: newbie-friendly 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-55941) Removing JAXB dependency from TFS-plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55941 Removing JAXB dependency from TFS-plugin Change By: Baptiste Mathus Labels: fosdem2019 java11 newbie-friendly 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-55942) Remove JAXB dependency from performance plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55942 Remove JAXB dependency from performance plugin Change By: Baptiste Mathus Labels: fosdem2019 java11 newbie-friendly 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-55087) Revert the Java 11 Experimental Update Center patches in the Docker image
Title: Message Title Oleg Nenashev commented on JENKINS-55087 Re: Revert the Java 11 Experimental Update Center patches in the Docker image https://github.com/jenkinsci/docker/pull/798 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-55087) Revert the Java 11 Experimental Update Center patches in the Docker image
Title: Message Title Oleg Nenashev updated JENKINS-55087 Jenkins / JENKINS-55087 Revert the Java 11 Experimental Update Center patches in the Docker image Change By: Oleg Nenashev 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-55087) Revert the Java 11 Experimental Update Center patches in the Docker image
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-55087 Revert the Java 11 Experimental Update Center patches in the Docker image Change By: Oleg Nenashev Assignee: 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-55087) Revert the Java 11 Experimental Update Center patches in the Docker image
Title: Message Title Oleg Nenashev started work on JENKINS-55087 Change By: Oleg Nenashev 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-55954) Remove unnecessary JAXB's DatatypeConverter usage
Title: Message Title Aniket Kadam commented on JENKINS-55954 Re: Remove unnecessary JAXB's DatatypeConverter usage This is the PR that addresses the issue. https://github.com/jenkinsci/pipeline-aws-plugin/pull/158 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-55954) Remove unnecessary JAXB's DatatypeConverter usage
Title: Message Title Aniket Kadam updated JENKINS-55954 Jenkins / JENKINS-55954 Remove unnecessary JAXB's DatatypeConverter usage Change By: Aniket Kadam 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-55954) Remove unnecessary JAXB's DatatypeConverter usage
Title: Message Title Aniket Kadam started work on JENKINS-55954 Change By: Aniket Kadam 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-55667) Configure "Job Configuration History" plugin with "Configuration as Code"
Title: Message Title Austin Dewey assigned an issue to Austin Dewey Jenkins / JENKINS-55667 Configure "Job Configuration History" plugin with "Configuration as Code" Change By: Austin Dewey Assignee: Ewelina Wilkosz Austin Dewey 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-55950) Remember me causes excessive requests to LDAP Server after changing passwords
Title: Message Title Vladimir Zdravkovic commented on JENKINS-55950 Re: Remember me causes excessive requests to LDAP Server after changing passwords Hi quick question, is there any UI issues in regards to this? Because what I found out is that while you are logged in with the "Remember me" the UI starts to lag and the entire web part of Jenkins takes a lot of time to load anything. The CPU usage on the server is at minimum so it's not the backend issues. Logging out of Jenkins and logging in back makes everything super fast again! A valid note here is that my Jenkins master is hosted locally so there shouldn't be any network latency. 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-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Gabor Farkas commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata Are there any alternatives to using this status setter? 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-55954) Remove unnecessary JAXB's DatatypeConverter usage
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-55954
Remove unnecessary JAXB's DatatypeConverter usage
Change By:
Baptiste Mathus
The plugin is using DatatypeConverter for Base 64 conversion, it could be replaced by {{java.util.Base64}} like was done in [https://github.com/jenkinsci/instance-identity-module/pull/11] h3. Acceptance criteriahttps://github.com/jenkinsci/pipeline-aws-plugin/search?q=javax.xml.bind_q=javax.xml.bind yields nothing anymore
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-54906) Custom WAR Packager should support producing Java 11-compatible JFR images
Title: Message Title Evaristo Gutierrez assigned an issue to Evaristo Gutierrez Jenkins / JENKINS-54906 Custom WAR Packager should support producing Java 11-compatible JFR images Change By: Evaristo Gutierrez Assignee: Evaristo Gutierrez 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-55954) Remove unnecessary JAXB's DatatypeConverter usage
Title: Message Title Baptiste Mathus assigned an issue to Aniket Kadam Jenkins / JENKINS-55954 Remove unnecessary JAXB's DatatypeConverter usage Change By: Baptiste Mathus Assignee: Thorsten Hoeger Aniket Kadam 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-55954) Remove unnecessary JAXB's DatatypeConverter usage
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-55954 Remove unnecessary JAXB's DatatypeConverter usage Issue Type: Improvement Assignee: Thorsten Hoeger Components: pipeline-aws-plugin Created: 2019-02-04 14:26 Priority: Major Reporter: Baptiste Mathus The plugin is using DatatypeConverter for Base 64 conversion, it could be replaced by java.util.Base64 like was done in https://github.com/jenkinsci/instance-identity-module/pull/11 Acceptance criteria https://github.com/jenkinsci/pipeline-aws-plugin/search?q=javax.xml.bind_q=javax.xml.bind yields nothing anymore Add Comment
[JIRA] (JENKINS-55946) Pipeline sh invocations run on noexec mounted filesystems will silently fail
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55946 Pipeline sh invocations run on noexec mounted filesystems will silently fail Change By: Devin Nusbaum Labels: pipeline 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-50663) Deadlock on jenkins startup
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50663 Deadlock on jenkins startup Change By: Oleg Nenashev Labels: deadlock lts-candidate threads 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-31622) Jenkins Startup Deadlock
Title: Message Title Oleg Nenashev updated JENKINS-31622 JENKINS-55361 should fix it in 2.163+ Jenkins / JENKINS-31622 Jenkins Startup Deadlock Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Jenkins 2.163 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-31622) Jenkins Startup Deadlock
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-31622 Jenkins Startup Deadlock Change By: Oleg Nenashev Labels: git jenkins lts-candidate 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-31622) Jenkins Startup Deadlock
Title: Message Title Oleg Nenashev updated JENKINS-31622 Jenkins / JENKINS-31622 Jenkins Startup Deadlock Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved 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-44564) Deadlock restarting jenkins
Title: Message Title Oleg Nenashev updated JENKINS-44564 JENKINS-55361 should fix it in Jenkins 2.163. Jenkins / JENKINS-44564 Deadlock restarting jenkins Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Jenkins 2.163 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-50663) Deadlock on jenkins startup
Title: Message Title Oleg Nenashev updated JENKINS-50663 Jenkins / JENKINS-50663 Deadlock on jenkins startup Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Assignee: michael jing 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-50663) Deadlock on jenkins startup
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50663 Deadlock on jenkins startup Change By: Oleg Nenashev Released As: JENKINS Jenkins 2.163 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-50663) Deadlock on jenkins startup
Title: Message Title Oleg Nenashev updated JENKINS-50663 JENKINS-55361 should fix it in 2.163 from what I see Jenkins / JENKINS-50663 Deadlock on jenkins startup Change By: Oleg Nenashev Status: Reopened Fixed but Unreleased Resolution: Fixed Released As: JENKINS 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-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2
Title: Message Title Oleg Nenashev updated JENKINS-54974 Jenkins / JENKINS-54974 Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2 Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved 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-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2
Title: Message Title Oleg Nenashev updated JENKINS-54974 Jenkins / JENKINS-54974 Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2 Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved 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-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54974 Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2 Change By: Oleg Nenashev Labels: lts-candidate 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-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2
Title: Message Title Oleg Nenashev updated JENKINS-54974 It should be fixed by the patch from Arnaud TAMAILLON in 2.163 Jenkins / JENKINS-54974 Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2 Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Jenkns Core 2.163 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.
