[JIRA] (JENKINS-58134) Some of the testcase status can't be parsed correctly
Title: Message Title Roy Lu commented on JENKINS-58134 Re: Some of the testcase status can't be parsed correctly https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/241 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200179.1561100594000.7012.1561359420041%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55276) HP ALM Plugin - when job is branched only branch appear in HP ALM
Title: Message Title Roy Lu commented on JENKINS-55276 Re: HP ALM Plugin - when job is branched only branch appear in HP ALM Hi Noam, In the plugin, job name is fixed as the job's name. Can't be customized to other value. We set the job's name to the 'jenkins-job-name' field. So the value updated to this field is actually a fixed value. You said 'JOB_NAME=JOB_NAME/BRANCH'. Do you mean you changed job name during the pipeline script building? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.7011.1561359360122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57603) Git Plugin: No JCasC configurator for Submodule configurations
Title: Message Title Evaristo Gutierrez updated JENKINS-57603 Jenkins / JENKINS-57603 Git Plugin: No JCasC configurator for Submodule configurations Change By: Evaristo Gutierrez 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199528.1558527868000.7007.1561358280594%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58069) PCT is not working for the CasC plugin
Title: Message Title Evaristo Gutierrez updated JENKINS-58069 Jenkins / JENKINS-58069 PCT is not working for the CasC plugin Change By: Evaristo Gutierrez 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200093.1560863829000.7008.1561358280616%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Vincent Massol commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile Awesome, thanks for both of you Jesse Glick and ikedam! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194755.1539777336000.6989.1561357320413%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title ikedam assigned an issue to Adrian Vlad Jenkins / JENKINS-54262 Groovy Postbuild requires Overall/Administer permission Change By: ikedam Assignee: ikedam Adrian 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194906.154053702.6983.1561357200793%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title ikedam resolved as Fixed Fixed in groovy-postbuild-2.5. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-54262 Groovy Postbuild requires Overall/Administer permission Change By: ikedam Status: In Progress Resolved Resolution: Fixed Released As: groovy-postbuild-2.5 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194906.154053702.6976.15613572006
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title ikedam updated an issue Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile The issue in groovy-postbuild is fixed in groovy-postbuild-2.5. (Removed groovy-postbuild from component/s) It will be available in the update center in a day. Please try that. Change By: ikedam Component/s: groovy-postbuild-plugin Released As: workflow-job 2.29 groovy-postbuild-2.5 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194755.1539777336000.6956.1561357080605%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Anda Sorina Laakso commented on JENKINS-57334 Re: "Run on planned host" from Build section not working Version 5.8 is alerady available. Could you try with that one? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199108.1557111748000.6947.1561356420664%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam closed an issue as Fixed Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild Change By: ikedam 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.6954.1561356421013%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam updated JENKINS-57917 Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild Change By: ikedam Status: In Review Resolved Resolution: Fixed Released As: groovy-postbuild-2.5 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.6952.1561356420966%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Anda Sorina Laakso edited a comment on JENKINS-57334 Re: "Run on planned host" from Build section not working Version 5.8 is alerady already available.Could you try with that one? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199108.1557111748000.6950.1561356420882%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title hhkkss edited a comment on JENKINS-58112 Re: Triggering multibranch pipeline from jira-trigger-plugin I agree with you on following {color:#ff}points{color}. but the thing is, in that case I have to create individual upstream projects for all my pipeline projects. :(. or let me know if there is any workaround to manage from single upstream job. {color:#ff}Perhaps your best bet here is to get your branch triggered by an upstream project:{color} * {color:#ff}deploy in uat job: configured with jira-trigger-plugin{color} * {color:#ff}multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: [https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change]){color} {color:#172b4d} Regarding the {color }{color :#ffab00} {color:#172b4d}{color:#ff8b00} below {color} comment, what I was trying to tell you is my pipeline is same for all the branches in the project. but it has WHEN condition's defined already. thus, deployment handle only from release branch. meaning, development branch is only to commit day to day changes. whenever, developers are ready to move the changes into SIT, then they have to merge the changes into release branch and then only entire pipeline is triggered. any triggers from development branch will not handle any deployment and it will run the build and unit testing only, so developers know that they do not have any compilation errors on the code.{color} {color} {color:#172b4d} {color} its simply like below: {code:java} { stage ('SIT Deployment'){ when { branch 'release' } steps { script {"my deployment". {code} {color:#ff8b00}To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is:{color} * {color:#ff8b00}release branch: sit deployment, uat deployment, prod deployment{color} * {color:#ff8b00}other branches: scm checkout, build, unit testing, packaging{color}{color:#ff8b00}It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate?{color} Add Comment This message was sent by Atlassian Jira (v7.
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title hhkkss edited a comment on JENKINS-58112 Re: Triggering multibranch pipeline from jira-trigger-plugin I agree with you on following {color:#ff}points{color}. but the thing is, in that case I have to create individual upstream projects for all my pipeline projects. :(. or let me know if there is any workaround to manage from single upstream job. {color:#ff}Perhaps your best bet here is to get your branch triggered by an upstream project:{color} * {color:#ff}deploy in uat job: configured with jira-trigger-plugin{color} * {color:#ff}multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: [https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change]){color} Regarding the {color:#ffab00}below comment, what I was trying to tell you is my pipeline is same for all the branches in the project. but it has WHEN condition's defined already. thus, deployment handle only from release branch. meaning, development branch is only to commit day to day changes. whenever, developers are ready to move the changes into SIT, then they have to merge the changes into release branch and then only entire pipeline is triggered. any triggers from development branch will not handle any deployment and it will run the build and unit testing only, so developers know that they do not have any compilation errors on the code.{color} its simply like below: {code:java} { stage ('SIT Deployment'){ when { branch 'release' } steps { script {"my deployment". {code} {color:#ff8b00} To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is: {color} * {color:#ff8b00}release branch: sit deployment, uat deployment, prod deployment{color} * {color:#ff8b00}other branches: scm checkout, build, unit testing, packaging{color}{color:#ff8b00}It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate?{color} Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title hhkkss edited a comment on JENKINS-58112 Re: Triggering multibranch pipeline from jira-trigger-plugin I agree with you on following {color:# FF ff }points{color}. but the thing is, in that case I have to create individual upstream projects for all my pipeline jobs projects . :(. or let me know if there is any workaround to manage from single upstream job. {color:# FF ff }Perhaps your best bet here is to get your branch triggered by an upstream project:{color} * {color:# FF ff }deploy in uat job: configured with jira-trigger-plugin{color} * {color:# FF ff }multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: [https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change]){color} Regarding the {color:#ffab00}below {color:#172b4d} comment, what I was trying to tell you is my pipeline is same for all the branches in the project. but it has WHEN condition's defined already. thus, deployment handle only from release branch. meaning, development branch is only to commit day to day changes. whenever, developers are ready to move the changes into SIT, then they have to merge the changes into release branch and then only entire pipeline is triggered. any triggers from development branch will not handle any deployment and it will run the build and unit testing only, so developers know that they do not have any compilation errors on the code.{color} {color} its simply like below: {code:java} { stage ('SIT Deployment'){ when { branch 'release' } steps { script {"my deployment". {code} {color:#ff8b00} To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is: {color} * {color:#ff8b00}release branch: sit deployment, uat deployment, prod deployment{color} * {color:#ff8b00}other branches: scm checkout, build, unit testing, packaging{color}{color:#ff8b00}It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate?{color} Add Comment This message was sent by Atlassian Jira (v7.11.2#71100
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title hhkkss commented on JENKINS-58112 Re: Triggering multibranch pipeline from jira-trigger-plugin I agree with you on following points. but the thing is, in that case I have to create individual upstream projects for all my pipeline jobs. . or let me know if there is any workaround to manage from single upstream job. Perhaps your best bet here is to get your branch triggered by an upstream project: deploy in uat job: configured with jira-trigger-plugin multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change) Regarding the below comment, what I was trying to tell you is my pipeline is same for all the branches in the project. but it has WHEN condition's defined already. thus, deployment handle only from release branch. meaning, development branch is only to commit day to day changes. whenever, developers are ready to move the changes into SIT, then they have to merge the changes into release branch and then only entire pipeline is triggered. any triggers from development branch will not handle any deployment and it will run the build and unit testing only, so developers know that they do not have any compilation errors on the code. its simply like below: { stage ('SIT Deployment'){ when { branch 'release' } steps { script {"my deployment" . To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is: release branch: sit deployment, uat deployment, prod deployment other branches: scm checkout, build, unit testing, packaging It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate? Add Comment
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title Wisen Tanasa commented on JENKINS-58112 Re: Triggering multibranch pipeline from jira-trigger-plugin Thanks for the detailed use case. A pattern matching won't suffice as you might want to trigger different workflow to different branches i.e. "Deploy in SIT" for "release branch", "Deploy in UAT" for "uat branch" (example), etc. Perhaps your best bet here is to get your branch triggered by an upstream project: deploy in uat job: configured with jira-trigger-plugin multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change) To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is: release branch: sit deployment, uat deployment, prod deployment other branches: scm checkout, build, unit testing, packaging It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200156.1561013839000.6936.1561354620097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57348) EC2 Plugin not working when AWS Keys are rotated
Title: Message Title Arun Gupta commented on JENKINS-57348 Re: EC2 Plugin not working when AWS Keys are rotated Sorry, we will test it with latest version 1.44 of EC2 Plugin and get back. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199124.1557188451000.6933.1561354020133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47207) Job's Promotion Status page does not display PROMOTED_USER_NAME
Title: Message Title Oleg Nenashev updated JENKINS-47207 Promoted Builds 3.3 is finally out Jenkins / JENKINS-47207 Job's Promotion Status page does not display PROMOTED_USER_NAME Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: Promoted Builds 3.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185615.1506631675000.6931.1561352580287%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43656) Allow SSH Agent to be used with Promted Build Plugin
Title: Message Title Oleg Nenashev updated JENKINS-43656 Jenkins / JENKINS-43656 Allow SSH Agent to be used with Promted Build Plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181069.1492525123000.6928.1561352522120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43656) Allow SSH Agent to be used with Promted Build Plugin
Title: Message Title Oleg Nenashev updated JENKINS-43656 The patch has been released in Promoted Builds 3.3 Jenkins / JENKINS-43656 Allow SSH Agent to be used with Promted Build Plugin Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Promoted Builds 3.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181069.1492525123000.6922.1561352521922%40Atlassian.JIRA. For more
[JIRA] (JENKINS-25526) Add mask password feature to the promotion plugin
Title: Message Title Oleg Nenashev updated JENKINS-25526 Build wrappers are now supported in Promoted Builds 3.3 Jenkins / JENKINS-25526 Add mask password feature to the promotion plugin Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Promoted Builds 3.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159093.1415650942000.6916.1561352521230%40Atlassian.JIRA. For mo
[JIRA] (JENKINS-25526) Add mask password feature to the promotion plugin
Title: Message Title Oleg Nenashev updated JENKINS-25526 Jenkins / JENKINS-25526 Add mask password feature to the promotion plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159093.1415650942000.6920.1561352521818%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14169) Injected env variables not available for use in processing promotion.
Title: Message Title Oleg Nenashev updated JENKINS-14169 Jenkins / JENKINS-14169 Injected env variables not available for use in processing promotion. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.144800.1340256993000.6906.1561352462380%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23977) Promoted-builds does not allow build secrets
Title: Message Title Oleg Nenashev updated JENKINS-23977 It was fixed in Promoted Builds 3.3 Jenkins / JENKINS-23977 Promoted-builds does not allow build secrets Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Promoted Builds 3.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156447.1406232862000.6909.1561352462425%40Atlassian.JIRA. For more options, visit https:/
[JIRA] (JENKINS-14169) Injected env variables not available for use in processing promotion.
Title: Message Title Oleg Nenashev updated JENKINS-14169 ADAICT Promoted Builds 3.3 fixes it by enabling EnvInject plugin build wrappers Jenkins / JENKINS-14169 Injected env variables not available for use in processing promotion. Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Promoted Builds 3.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.144800.1340256993000
[JIRA] (JENKINS-23977) Promoted-builds does not allow build secrets
Title: Message Title Oleg Nenashev updated JENKINS-23977 Jenkins / JENKINS-23977 Promoted-builds does not allow build secrets 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156447.1406232862000.6911.1561352462446%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58158) Multibranch pipeline Organization folder scans fails randomily
Title: Message Title vinoth SS assigned an issue to Steven Collins Jenkins / JENKINS-58158 Multibranch pipeline Organization folder scans fails randomily Change By: vinoth SS Assignee: Steven Collins 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200206.1561342709000.6886.1561352220125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56861) Send PMD, FB, Checkstyle metrics to influxDB
Title: Message Title Aleksi Simell commented on JENKINS-56861 Re: Send PMD, FB, Checkstyle metrics to influxDB Philipp Deuchert Possibly. The fastest way to have this available is to make a pull request of it. Otherwise the task will go to my backlog, which already has a bunch of stuff, so implementing this might take a while. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198523.1554266985000.6884.1561351260183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58158) Multibranch pipeline Organization folder scans fails randomily
Title: Message Title vinoth SS updated an issue Jenkins / JENKINS-58158 Multibranch pipeline Organization folder scans fails randomily Change By: vinoth SS 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200206.1561342709000.6881.156135077%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58156) jenkins chinese translate missing
Title: Message Title Minghui Ma assigned an issue to Minghui Ma Jenkins / JENKINS-58156 jenkins chinese translate missing Change By: Minghui Ma Assignee: zhao xx Minghui Ma 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200204.1561340855000.6880.1561348440108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58156) jenkins chinese translate missing
Title: Message Title Minghui Ma assigned an issue to zhao xx Jenkins / JENKINS-58156 jenkins chinese translate missing Change By: Minghui Ma Assignee: zhao xx 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200204.1561340855000.6878.1561348380166%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58156) jenkins chinese translate missing
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-58156 jenkins chinese translate missing Change By: Minghui Ma after upgrade to 2.176.1, some string translate to chinese missing.for example: "Manage Jenkins", What's new in 2.176 (2019-05-05) Migrate all Chinese localization resources into Localization: Chinese (Simplified) plugin. (pull 4008)中文的本地翻译都移到 插件里面了https://plugins.jenkins.io/localization-zh-cn 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200204.1561340855000.6876.1561348380108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58156) jenkins chinese translate missing
Title: Message Title Minghui Ma updated JENKINS-58156 Jenkins / JENKINS-58156 jenkins chinese translate missing Change By: Minghui Ma Status: Fixed but Unreleased 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200204.1561340855000.6875.1561348320192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58156) jenkins chinese translate missing
Title: Message Title Minghui Ma updated JENKINS-58156 Jenkins / JENKINS-58156 jenkins chinese translate missing Change By: Minghui Ma Status: Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200204.1561340855000.6874.1561348320134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54752) Ansi plugin fails to render formatted console output
Title: Message Title Xinpeng Liu commented on JENKINS-54752 Re: Ansi plugin fails to render formatted console output Met the same issue. The "View as plain text" works just fine. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195557.1542803843000.6853.1561348080519%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57348) EC2 Plugin not working when AWS Keys are rotated
Title: Message Title Raihaan Shouhell commented on JENKINS-57348 Re: EC2 Plugin not working when AWS Keys are rotated Arun Gupta you mean 1.44 does not solve your 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199124.1557188451000.6851.1561346580145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57348) EC2 Plugin not working when AWS Keys are rotated
Title: Message Title Arun Gupta commented on JENKINS-57348 Re: EC2 Plugin not working when AWS Keys are rotated We are using Jenkins 2.164.1 and this doesn't work in this version. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199124.1557188451000.6847.1561346460122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57348) EC2 Plugin not working when AWS Keys are rotated
Title: Message Title Raihaan Shouhell commented on JENKINS-57348 Re: EC2 Plugin not working when AWS Keys are rotated A fix for this was released in 1.44 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199124.1557188451000.6845.1561346100386%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58011) Support T3a instance types
Title: Message Title Raihaan Shouhell commented on JENKINS-58011 Re: Support T3a instance types This is technically already supported you need to update to a newer aws-java-sdk 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200028.1560441088000.6842.1561346040142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58097) The slave agent is not able to connect to master after disabled JNLP2 protocol
Title: Message Title Peter Jiang commented on JENKINS-58097 Re: The slave agent is not able to connect to master after disabled JNLP2 protocol Furthermore, I searched whole computer drives, but was not able to find out slave.jar file anywhere. Please let me know whom this Jira can be assigned to. It is still in "Unassigned". 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200139.1560954313000.6819.1561345980442%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Raihaan Shouhell commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM A fix got merged to master that definitely helped our masters 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190313.1525203384000.6821.1561345980485%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title hhkkss assigned an issue to hhkkss Jenkins / JENKINS-58112 Triggering multibranch pipeline from jira-trigger-plugin Change By: hhkkss Assignee: Wisen Tanasa hhkkss 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200156.1561013839000.6818.1561345440279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58158) Multibranch pipeline Organization folder scans fails randomily
Title: Message Title vinoth SS created an issue Jenkins / JENKINS-58158 Multibranch pipeline Organization folder scans fails randomily Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-06-24 02:18 Priority: Minor Reporter: vinoth SS Scanning the organization folder fails randomly, my repo project has more than 100 repos but fails in first 10-25 repos randomly.. Any fixes for this? ERROR: [Mon Jun 24 10:17:02 JST 2019] Could not fetch sources from navigator com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator@351ec6ab java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) Add Comment
[JIRA] (JENKINS-43120) when rebuild job started by timer, user build vars are empty
Title: Message Title Minghui Ma updated JENKINS-43120 Jenkins / JENKINS-43120 when rebuild job started by timer, user build vars are empty Change By: Minghui Ma Status: Fixed but Unreleased 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180234.149059217.6815.1561342680355%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43120) when rebuild job started by timer, user build vars are empty
Title: Message Title Minghui Ma assigned an issue to Minghui Ma Jenkins / JENKINS-43120 when rebuild job started by timer, user build vars are empty Change By: Minghui Ma Assignee: Minghui Ma 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180234.149059217.6813.1561342680325%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43120) when rebuild job started by timer, user build vars are empty
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-43120 when rebuild job started by timer, user build vars are empty Change By: Minghui Ma jenkins 2.32.2 userbuild vars plugin 1.5 when rebuild one job started by timer the user build vars are empty. by 2019/06/24i modify the code see https://github.com/mamh-java/build-user-vars-plugin/commits/master 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180234.149059217.6812.1561342680213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43120) when rebuild job started by timer, user build vars are empty
Title: Message Title Minghui Ma updated JENKINS-43120 Jenkins / JENKINS-43120 when rebuild job started by timer, user build vars are empty Change By: Minghui Ma Status: Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180234.149059217.6814.1561342680344%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43120) when rebuild job started by timer, user build vars are empty
Title: Message Title Minghui Ma commented on JENKINS-43120 Re: when rebuild job started by timer, user build vars are empty see https://github.com/mamh-java/build-user-vars-plugin/commits/master 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180234.149059217.6811.1561342620043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58157) "delete build" button is to long
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-58157 "delete build" button is to long Change By: Minghui Ma after upgrade to 2.176.1, "delete build" button is to long.see my attachment png picture at bleow. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200205.1561341295000.6810.1561341600270%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58157) "delete build" button is to long
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-58157 "delete build" button is to long Change By: Minghui Ma Attachment: 2.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200205.1561341295000.6809.1561341600120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58157) "delete build" button is to long
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-58157 "delete build" button is to long Change By: Minghui Ma Attachment: 2.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200205.1561341295000.6808.1561341420069%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58157) "delete build" button is to long
Title: Message Title Minghui Ma created an issue Jenkins / JENKINS-58157 "delete build" button is to long Issue Type: Bug Assignee: Unassigned Attachments: 2.png Components: core Created: 2019-06-24 01:54 Environment: 2.176.1 Priority: Major Reporter: Minghui Ma after upgrade to 2.176.1, "delete build" button is to long. see my attachment png picture at bleow. Add Comment
[JIRA] (JENKINS-58156) jenkins chinese translate missing
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-58156 jenkins chinese translate missing Change By: Minghui Ma after upgrade to 2.176.1, some string translate to chinese missing. for example: "Manage 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200204.1561340855000.6806.1561341120062%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58156) jenkins chinese translate missing
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-58156 jenkins chinese translate missing Change By: Minghui Ma Attachment: 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200204.1561340855000.6805.1561341060054%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58156) jenkins chinese translate missing
Title: Message Title Minghui Ma created an issue Jenkins / JENKINS-58156 jenkins chinese translate missing Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-06-24 01:47 Environment: 2.176.1 Priority: Major Reporter: Minghui Ma after upgrade to 2.176.1, some string translate to chinese missing. Add Comment
[JIRA] (JENKINS-58102) GlobalAnnotator does not annotate lines that are part of a multi-line color sequence
Title: Message Title Basil Crow commented on JENKINS-58102 Re: GlobalAnnotator does not annotate lines that are part of a multi-line color sequence Posted jenkinsci/timestamper-plugin#28 to address 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200145.1560960833000.6803.1561330800192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58155) Quicker slave start-up
Title: Message Title D.Schneider created an issue Jenkins / JENKINS-58155 Quicker slave start-up Issue Type: Improvement Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-06-23 17:23 Environment: Ubuntu Linux, Jenkins 2.176.1, EC2 plugin 1.43 Priority: Major Reporter: D.Schneider Great plug-in, thank you so much for all the great work! The time interval from when a job lands in the build queue until a new slave node is started to handle the job is rather long. It would be useful if we could tune how frequently the build queue is checked and how quickly new slaves are started up so we can reduce the wait time. Add Comment
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Marcello de Sales commented on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable Matt C. Wilson Can you specify the versions you tested those? I guess we can just write a script instruction to not echo anything and place the actual String in the label... have you tried that? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194144.1537309242000.6754.1561306980370%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Matt C. Wilson commented on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable A workaround that we're having success with is removing informational echo calls and instead using the `label` property on `sh`. This was recently introduced in the Pipeline: Nodes and Processes plugin - required us to upgrade. So echo Doing the thing... sh ./the_thing.sh becomes sh(script: "./the_thing.sh", label: "Doing the thing...") and has the nice side effect of reducing the number of rows overall in Blue Ocean. https://jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#sh-shell-script https://plugins.jenkins.io/workflow-durable-task-step 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194144.1537309242000.6739.1561306680401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58138) Confusing saml plugin keystore breakage
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58138 Jenkins / JENKINS-58138 Confusing saml plugin keystore breakage Change By: Ivan Fernandez Calvo Status: Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200183.1561110857000.6735.1561294270394%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58138) Confusing saml plugin keystore breakage
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58138 Jenkins / JENKINS-58138 Confusing saml plugin keystore breakage Change By: Ivan Fernandez Calvo Status: Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200183.1561110857000.6737.1561294320038%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58138) Confusing saml plugin keystore breakage
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-58138 Re: Confusing saml plugin keystore breakage finally, I'd not remove the use of the keystore in the bundle to avoid break some installations, I've added a more explanatory message. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200183.1561110857000.6733.1561294140347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58154) Enhance usability when choosing time range.
Title: Message Title Jack Shen created an issue Jenkins / JENKINS-58154 Enhance usability when choosing time range. Issue Type: Improvement Assignee: Jack Shen Components: working-hours-plugin Created: 2019-06-23 12:01 Labels: gsoc-2019 Priority: Minor Reporter: Jack Shen 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.c
[JIRA] (JENKINS-57470) Plugin Manager page does not render correctly
Title: Message Title Kayvan Tehrani commented on JENKINS-57470 Re: Plugin Manager page does not render correctly This bug is still in Jenkins version 2.176.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199330.1557860856000.6730.1561290720105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Andrew Douglas commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications Hi, Is there anything that I can do to help move this along? I'm migrating quite a few jobs from freestyle to pipelines and I would hate to lose this functionality. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.6696.1561289400827%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57470) Plugin Manager page does not render correctly
Title: Message Title Kayvan Tehrani updated an issue Jenkins / JENKINS-57470 Plugin Manager page does not render correctly Change By: Kayvan Tehrani Attachment: jenkns-error.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199330.1557860856000.6693.1561280460146%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57470) Plugin Manager page does not render correctly
Title: Message Title Kayvan Tehrani updated an issue Jenkins / JENKINS-57470 Plugin Manager page does not render correctly Change By: Kayvan Tehrani 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199330.1557860856000.6691.1561273620185%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.