[JIRA] (JENKINS-57958) Add changelog for 2.176.1 LTS release
Title: Message Title Harald Albers updated JENKINS-57958 resoved by https://github.com/jenkins-infra/jenkins.io/pull/2326 Jenkins / JENKINS-57958 Add changelog for 2.176.1 LTS release Change By: Harald Albers 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.199939.1560255613000.25763.1560322920439%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57958) Add changelog for 2.176.1 LTS release
Title: Message Title Harald Albers updated JENKINS-57958 Jenkins / JENKINS-57958 Add changelog for 2.176.1 LTS release Change By: Harald Albers 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.199939.1560255613000.25765.1560322980206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57918) SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1
Title: Message Title Sascha Kolberg commented on JENKINS-57918 Re: SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1 After a rollback of all recently updated plugins, setting changelog: false, makes checkout work again and the build can run. ... puzzling 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.199890.1560007155000.25766.1560323100061%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57979) A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and p
Title: Message Title Olivier Vernin moved an issue Jenkins / JENKINS-57979 A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. Change By: Olivier Vernin Project: Infrastructure Jenkins Key: INFRA JENKINS - 2134 57979 Workflow: classic default workflow JNJira + In-Review Component/s: core Component/s: ci Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57602) NPE in Support Core Plugin when reporting agents
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-57602 NPE in Support Core Plugin when reporting agents Change By: Baptiste Mathus Assignee: Emilio Escobar 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.199526.1558523885000.25793.1560325560203%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55486) If lock() creates a new resource, there should be a choice to make it temporary
Title: Message Title ethorsa commented on JENKINS-55486 Re: If lock() creates a new resource, there should be a choice to make it temporary There's a pending PR on Github addressing 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.196616.1547046002000.25795.1560325860261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Kieron Kierzo commented on JENKINS-57955 Re: Clean and sync incorrectly follows junction/directory symlinks on Windows Hi Karl, Thanks for your detailed response. I have added it to a always run in a post step, the issue is that its not always reliable to run. e.g. I've had a power-cut , had java run out of heap space, network disconnects, switching from jnpl3 to jnpl4, plugins doing odd stuff and users making breaking changes to the pipeline script affecting it getting to the end. Its not common but not as uncommon as id like, but it only needs to happen once and the build misses getting to the end and then the next run removes the build dependencies. Thanks a lot for your time. 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.199936.1560247579000.25801.1560325920561%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Karl Wirth commented on JENKINS-57955 Re: Clean and sync incorrectly follows junction/directory symlinks on Windows Hi Kieron Kierzo, Thanks and I'm happy to help. I'll make sure the developers see the feedback about the the workaround not being robust. 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.199936.1560247579000.25803.1560326280592%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57594) email-ext: get culprits per repo
Title: Message Title eric for 1A salenc for 1A commented on JENKINS-57594 Re: email-ext: get culprits per repo Finaly I found a solution In Jenkins Configuration: Pipeline libraries Never check Include @Library changes in job recent changes option 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.199518.1558509365000.25805.1560328200740%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57918) SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1
Title: Message Title Laurent Soest commented on JENKINS-57918 Re: SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1 Hi I have the same issue. "SCM checkout fails for Gerrit Repo." As a workaround I downgraded Pipeline SCM Step Plugin to 2.7 and it is working again. 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.199890.1560007155000.25812.1560328920605%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57980) Wrong links in /manage
Title: Message Title Štefan Kušnír created an issue Jenkins / JENKINS-57980 Wrong links in /manage Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-06-12 08:46 Environment: Jenkins ver. 2.180 RHEL 7 Priority: Trivial Reporter: Štefan Kušnír There are incorrect links in /manage site e.g. Configure Global Security: /configureSecurity which is redirecting wit 302 code to /configureSecurity/ Configure Credentials: /configureCredentials which is redirecting wit 302 code to /configureCredentials/ ... It cause useless redirection and with incorrect Apache configuration cause redirect from https to http protocol. Add Comment
[JIRA] (JENKINS-57980) Incorrect links in /manage
Title: Message Title Štefan Kušnír updated an issue Jenkins / JENKINS-57980 Incorrect links in /manage Change By: Štefan Kušnír Summary: Wrong Incorrect links in /manage Labels: core jenkins management 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.199965.1560329204000.25814.1560329340064%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47748) Second archiveArtifacts step fails silently with compress-artifacts-plugin
Title: Message Title Lubo Varga commented on JENKINS-47748 Re: Second archiveArtifacts step fails silently with compress-artifacts-plugin I am using scripted pipeline, where there are multiple parallel build steps (owasp dependency check, mvn test, code coverage) and they could run on different nodes/dockers, so I need to call archiveArtifacts multiple times. Is there any methodical workaround for situations like these? 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.186239.150945526.25817.1560329880678%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37657) plugin pom overloads a standard mojo config file for other things
Title: Message Title James Nord closed an issue as Duplicate even though the duplicate is the other way around the other issue has some comments so closing this one Jenkins / JENKINS-37657 plugin pom overloads a standard mojo config file for other things Change By: James Nord Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173782.1472059295000.25819.1560330300361%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title Fauzan commented on JENKINS-57779 Re: Bitbucket plugin JSONObject["username"] not found Thanks Deniis!! 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.199726.1559290809000.25821.1560331140891%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Dénes Zsolt commented on JENKINS-57899 Re: Jira site configuration lost after a reboot I experienced the same with the previous version, also.:/ 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.199864.1559853126000.25829.1560332460157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Dénes Zsolt edited a comment on JENKINS-57899 Re: Jira site configuration lost after a reboot I experienced the same with the previous version, also.:/ 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.199864.1559853126000.25831.1560332460182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48058) plugin pom overloads maven properties for evil things
Title: Message Title James Nord commented on JENKINS-48058 Re: plugin pom overloads maven properties for evil things the javadoc issue was removed in https://github.com/jenkinsci/plugin-pom/pull/109/files 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.186620.1510830451000.25834.1560332580146%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50837) [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3
Title: Message Title Srinivas M commented on JENKINS-50837 Re: [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3 Bruno P. Kinoshita, I am also facing same issue. Do you have any update on the resolution with ETA or any workaround fix for temporary? Based on my analysis, once I select item after entering a filter value and repeat it with number of selections with as many filter values, then clear the final value from filter text field before you trigger the build. It's holding all the items that are selected with all your previous filter options into the build parameter value. If we can clear this field value before entering the build, then it might solve? 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.189951.1523953451000.25839.1560333660179%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57981) extend build history in Dashboard view
Title: Message Title Rainer Haseneder created an issue Jenkins / JENKINS-57981 extend build history in Dashboard view Issue Type: Improvement Assignee: Unassigned Attachments: Jenkins_displayed_build_history_too_short.png Components: core Created: 2019-06-12 10:02 Labels: user-experience jenkins Priority: Minor Reporter: Rainer Haseneder Build history in Dashboard view shows only the last 30 builds. Sometimes I needed to go back further in history and see the last 60, 80 or 100 in the build history. As we print also the branch name into the build info which then shows up in the build history I could immediately identify the job which concerned a certain branch that I have to analyze. As for now I have to open the console log and modify the build number which is part of the URL in order to identify the build that belongs to the branch I have to analyze. This is tedious. It would be nice if there was a way to configure this limit which is currently 30. Used Jenkins version: 2.164.3
[JIRA] (JENKINS-57981) extend build history in Dashboard view
Title: Message Title Rainer Haseneder updated an issue Jenkins / JENKINS-57981 extend build history in Dashboard view Change By: Rainer Haseneder Attachment: Jenkins_displayed_build_history_too_short.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.199966.1560333732000.25842.1560333780224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors
Title: Message Title Kevin Nelson commented on JENKINS-57595 Re: with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors This is happening on my install as well. I'm raising the priority to Blocker, since it is currently impacting our organization's ability to use Jenkins at 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199519.1558510674000.25845.1560334140807%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors
Title: Message Title Kevin Nelson updated an issue Jenkins / JENKINS-57595 with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors Change By: Kevin Nelson Priority: Minor Blocker 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.199519.1558510674000.25852.1560334140973%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57982) Can we give only build permission to a specific user and by not giving read permission
Title: Message Title Saheta B created an issue Jenkins / JENKINS-57982 Can we give only build permission to a specific user and by not giving read permission Issue Type: Bug Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2019-06-12 10:12 Priority: Critical Reporter: Saheta B Can we give only build permission to a specific user and by not giving read permission My requirement is, a specific user should be able to build a project from command line but he should not be able to view the project from the UI. Add Comment
[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors
Title: Message Title Kevin Nelson commented on JENKINS-57595 Re: with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors To clarify our symptoms a bit: We're using the GitHub OAuth plugin with a GitHub Enterprise install. I'm able to configure the GitHub integration successfully, and use "Logged-in users can do anything" without issue. I can save this, reload the page and everything works fine. When I select the Matrix-based security radio, I am able to add exactly one user, and set all permissions, and save successfully. When I try to add more than one user, or when I try to add subsequent users after the first one, I am hit with the "No valid crumb was included in the request" error. 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.199519.1558510674000.25859.1560334380529%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors
Title: Message Title Kevin Nelson updated an issue Jenkins / JENKINS-57595 with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors Change By: Kevin Nelson Component/s: matrix-auth-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.199519.1558510674000.25868.1560334560427%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors
Title: Message Title Kevin Nelson edited a comment on JENKINS-57595 Re: with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors To clarify our symptoms a bit:We're using Jenkins 2.176.1 (LTS), the GitHub OAuth Authentication 0.32 plugin with a GitHub Enterprise install , and Matrix Authorization Strategy Plugin 2 . 4.2. I'm able to configure the GitHub integration successfully, and use "Logged-in users can do anything" without issue. I can save this, reload the page and everything works fine.When I select the Matrix-based security radio, I am able to add exactly one user, and set all permissions, and save successfully. When I try to add more than one user, or when I try to add subsequent users after the first one, I am hit with the "No valid crumb was included in the request" error. 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.199519.1558510674000.25875.1560334740350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57983) Create CONTRIBUTING guidelines for Promoted Builds
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57983 Create CONTRIBUTING guidelines for Promoted Builds Issue Type: Improvement Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2019-06-12 10:24 Priority: Minor Reporter: Oleg Nenashev There is no CONTRIBUTING guidelines in the repo. Please add ones Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57984) hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from ip
Title: Message Title Vasu G created an issue Jenkins / JENKINS-57984 hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from ip Issue Type: Bug Assignee: Ivo Verberk Components: nomad-plugin Created: 2019-06-12 10:37 Environment: Jenkins Master version : 2.145 Java version on master : 1.8 Java version on nomad slave(docker conatiner 1.8) Nomad plugin version: 0.6.1 Master OS : Amazon Linux AMI 2017.09 Slave OS: Ubuntu 18.04 Priority: Blocker Reporter: Vasu G Hi All, 1)Whenever a change in repo, pull request builder trigger the Jenkins jobs(target branch defined in jobs specification) 2)We are using Jenkins pipeline both frontend and backend test run in parallel. 3) Jenkins will allocate nomad slave to run our frontend and backend task(In Nomad Job template we specify the cpu, memory and docker images to run). 4) We are experiencing the "hudson.remoting.ChannelClosedException:" at frequent times. Jenkins Console log: [Backend] -> 0.0624s Cannot contact jenkins-519afe492c4efa: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from ip-10-0-0-10.ec2.internal/10.0.0.10:44176 failed. The channel is closing down or has closed down[Backend] -> 0.0624sCannot contact jenkins-519afe492c4efa: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from ip-10-0-0-10.ec2.internal/10.0.0.10:44176 failed. The channel is closing down or has closed down[Frontend] Cannot contact jenkins-519afe4939b540: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from ip-10-0-0-10.ec2.internal/10.0.0.10:34472 failed. The channel is closing down or has closed down[Frontend] Could not
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57877 PromotionBadge compatibility with pipelines Change By: Oleg Nenashev [Note]: Pipeline Steps are not incorporated in this task.PromotionBadge class is to be made pipeline compatible:Required changes during the course: * Refactor the PromotionBadge class * Make a new interface analogous to Promotion.java * Refactor both ManualCondition and GroovyCondition which are the implementations of buildEnvVars . * There is a "addPromotionBadge()" pipeline step which demonstrates the compatibility * There is is a documentation sample which shows how to use the feature in 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199840.1559812947000.25883.1560335880516%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47748) Second archiveArtifacts step fails silently with compress-artifacts-plugin
Title: Message Title Oliver Gondža commented on JENKINS-47748 Re: Second archiveArtifacts step fails silently with compress-artifacts-plugin This is just not implemented in compress-artifacts plugin. It should not be that difficult as underlying truezip library appears to support that. Help wanted! 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.186239.150945526.25887.1560335940232%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57927) Cleanup JCasC for external workspace manager
Title: Message Title Martin d'Anjou updated an issue Jenkins / JENKINS-57927 Cleanup JCasC for external workspace manager Change By: Martin d'Anjou Labels: gsoc-2019 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.199900.1560140494000.25891.1560336120232%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57925) Summary of Cloud feature EWM and start of JCasC
Title: Message Title Martin d'Anjou updated an issue Jenkins / JENKINS-57925 Summary of Cloud feature EWM and start of JCasC Change By: Martin d'Anjou Labels: gsoc-2019 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.199898.1560140338000.25895.1560336180379%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57926) Have a meeting on what plugins to work on JCasC
Title: Message Title Martin d'Anjou updated an issue Jenkins / JENKINS-57926 Have a meeting on what plugins to work on JCasC Change By: Martin d'Anjou Labels: gsoc-2019 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.199899.1560140393000.25893.1560336180336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57903 New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Change By: Oleg Nenashev Before implementing the promotion-conditions(Self and Manual Conditions), it seems necessary to build new abstract/classes for the following existing classes. * PromotionProcess * PromotionCondition * PromotionConditionDescriptorFor readability ease all these classes are being added by the word "Pipeline" as their prefix.Three new analogous classes are being made retaining some of the original functions and will timely be updated as other classes start depending on them. Acceptance criteria: * The classes are created, and they can be used in further APIs. Ther eis is no user-facing feature for now * The classes are marked as Restricted so that they not a part of API. It will change eventually * There is basic test automation that these classes really work 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.199868.1559891975000.
[JIRA] (JENKINS-57985) NPE after update from 2.7 to 2.9
Title: Message Title Alexander Willhaug created an issue Jenkins / JENKINS-57985 NPE after update from 2.7 to 2.9 Issue Type: Bug Assignee: Unassigned Components: workflow-scm-step-plugin Created: 2019-06-12 10:56 Environment: Jenkins 2.180 Priority: Minor Reporter: Alexander Willhaug Jenkinsfile timestamps { catchError { node { stage("checkout") { deleteDir() checkout(scm) openshiftImageStream name: 'nodejs-8-rhel7', namespace: 'x', tag: '1', verbose: 'false' } ... } // End node } // End catchError } // End timestamps [Pipeline] stage [Pipeline] { (checkout) [Pipeline] deleteDir [Pipeline] checkout 08:26:52 Cloning the remote Git repository [Pipeline] openshiftImageStream 08:26:55 08:26:55 08:26:55 The "OpenShift ImageStreams" SCM will return the last revision state stored in Jenkins for the image stream "nodejs-8-rhel7" and tag "1" from the project "xxx". 08:26:55Last revision: [ImageStreamRevisionState [commitId=sha256:eb31358824ad8af1550729526c48334df0a20fab86ae83d56a6d40a9933718cc]] [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] } [Pipeline] // node [Pipeline] } 08:26:55 java.lang.NullPointerException 08:26:55 at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.ja
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Arjo Poldervaart commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Same issue here, we use symlinks a lot and are not able to upgrade at the moment to the latest LTS because of this issue. Is there a temporary workaround that can be made on a local Jenkins install? 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.197816.1550852223000.25901.1560337260165%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57761) Create JCasC tests for metrics plugin
Title: Message Title Ramon Leon updated JENKINS-57761 Released as metrics-4.0.2.4 Jenkins / JENKINS-57761 Create JCasC tests for metrics plugin Change By: Ramon Leon Status: In Review Resolved Resolution: Done Released As: 4.0.2.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199707.1559209728000.25905.1560337560109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47748) Second archiveArtifacts step fails silently with compress-artifacts-plugin
Title: Message Title Kalle Niemitalo commented on JENKINS-47748 Re: Second archiveArtifacts step fails silently with compress-artifacts-plugin Lubo Varga, a workaround might be to stash the files from each node and unstash all of them to the same node, then archive them from there using only one archiveArtifacts 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.186239.150945526.25908.1560337681402%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57579) New "unstable" step is not visualizing stage as unstable
Title: Message Title Reinhold Füreder commented on JENKINS-57579 Re: New "unstable" step is not visualizing stage as unstable Thanks: it works like a charm! 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.199495.1558434359000.25912.1560337740182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56875) Missing parameters due to SECURITY-170
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-56875 Missing parameters due to SECURITY-170 Change By: Adam Gabryś Attachment: build-missing.txt Attachment: build-ok.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198544.155436857.25918.1560340380128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56875) Missing parameters due to SECURITY-170
Title: Message Title Adam Gabryś commented on JENKINS-56875 Re: Missing parameters due to SECURITY-170 We've hit it a few times since April. I compared build.xml of two builds of the same jobs (parameters values are very similar): build-missing.txt build-ok.txt I see only important differences in hudson.model.ParametersAction node. 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.198544.155436857.25920.1560340440190%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57833) All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log
Title: Message Title Martin Dönicke commented on JENKINS-57833 Re: All builds with maven pipeline plugin fail with java.lang.AbstractMethodError while parsing event spy log We had the same issue after updating the the pipeline-maven-plugin find -iname "xerces*.jar" ./plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar ./plugins/emma/WEB-INF/lib/xercesImpl-2.9.1.jar ./plugins/jdepend/WEB-INF/lib/xercesImpl-2.11.0.jar ./plugins/build-pipeline-plugin/WEB-INF/lib/xercesImpl-2.9.1.jar ./plugins/discard-old-build/WEB-INF/lib/xercesImpl-2.6.2.jar Removing the plugin discard-old-build (since we didn't use it anyway) has solved the issue on our side. 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.199790.1559631863000.25923.1560343620300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Matthew Smeeth commented on JENKINS-57945 Re: p4 sync corrupts symlinks Hi Michael, Do you possibly have text files nested within your symlinks? for example: //depot/path/symlink#1 (symlink) //depot/path/symlink/textfile#1 (text) 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.199921.1560203497000.25926.1560344100181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Michael Rose commented on JENKINS-57945 Re: p4 sync corrupts symlinks No. The symlink is to a file. There is no version where it was a folder. 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.199921.1560203497000.25930.1560344400377%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57986) NPE doTestConnection
Title: Message Title Dam Guerin created an issue Jenkins / JENKINS-57986 NPE doTestConnection Issue Type: Bug Assignee: Martin Reinhardt Components: rocket-chat-notifier-plugin Created: 2019-06-12 12:59 Priority: Minor Reporter: Dam Guerin Currently, for any error in doTestConnection, the code in catch, RocketChatNotifier.java, l599. However, in this catch, the following condition is incorrect. if (e.getCause() != null && e.getCause().getClass() == SSLHandshakeException.class || e.getCause().getClass() == ValidatorException.class) Indeed, the third part of this, is not protect by the first part. In other terms, we can have an NPE when e.getCause() returns null because the condition "e.getCause().getClass() == ValidatorException.class" is eval. Add Comment
[JIRA] (JENKINS-45264) extra field if influx-db publish fails
Title: Message Title Aleksi Simell commented on JENKINS-45264 Re: extra field if influx-db publish fails I know it's been almost 2 years since the creation of this ticket, but a similar feature is already implemented into the plugin. Use the "Expose Exceptions" choice in the global configuration if you want to fail builds when this plugin fails or just log the exception and move on. Also, in a pipeline you can set the build status yourself if you try-catch the InfluxDB step. Would either of these options be sufficient for this 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.183398.1499075326000.25934.1560344460111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda commented on JENKINS-57747 Re: Add form validation for gitlab gold and ultimate server urls This can be fixed by fetching a single project from projects endpoint. 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.199692.1559151818000.25942.1560345901536%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title Tommy Tynjä commented on JENKINS-38062 Re: "Create Delivery Pipeline version" errors Backwards compatibility for delivery pipeline plugin 0.9.9 and older has been dropped as of 92d7fc6 by removing support for resolving version ParametersAction. Will be part of the next release of the delivery pipeline 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.174214.1473344854000.25937.1560345901211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57943) Rename package
Title: Message Title Parichay Barpanda updated JENKINS-57943 Jenkins / JENKINS-57943 Rename package Change By: Parichay Barpanda 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.199919.156020204.25944.1560346440275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57948) Use regex to compare name field in jcasc
Title: Message Title Parichay Barpanda updated JENKINS-57948 Jenkins / JENKINS-57948 Use regex to compare name field in jcasc Change By: Parichay Barpanda 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.199925.1560215792000.25943.1560346440234%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57889) Add HashTable or HashMap for GitLabServer faster access
Title: Message Title Parichay Barpanda updated JENKINS-57889 Removed HashMaps as there are not necessary. As Joseph said, On a big team they would use an individual Jenkins instance as well. Also usually most people have a CI user that they can just give access to their projects. Jenkins / JENKINS-57889 Add HashTable or HashMap for GitLabServer faster access Change By: Parichay Barpanda Status: In Review Closed 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.199853.1559837778000.25945.1560346680093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda updated JENKINS-57747 Jenkins / JENKINS-57747 Add form validation for gitlab gold and ultimate server urls Change By: Parichay Barpanda Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199692.1559151818000.25947.1560346740871%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57889) Add HashTable or HashMap for GitLabServer faster access
Title: Message Title Parichay Barpanda commented on JENKINS-57889 Re: Add HashTable or HashMap for GitLabServer faster access See https://github.com/baymac/gitlab-branch-source-plugin/pull/15 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.199853.1559837778000.25946.1560346740571%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57987) Unable to add environment variable for jcasc token
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57987 Unable to add environment variable for jcasc token Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-12 13:42 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda See https://github.com/baymac/gitlab-branch-source-plugin/pull/16 Add Comment
[JIRA] (JENKINS-57947) More secured method to manage credentials in JCasC yaml
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57947 More secured method to manage credentials in JCasC yaml Change By: Parichay Barpanda Summary: Managing More secured method to manage credentials in JCasC yaml 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.199924.1560215713000.25950.1560347040141%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57987) Unable to add environment variable for jcasc token
Title: Message Title Parichay Barpanda started work on JENKINS-57987 Change By: Parichay Barpanda 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199972.1560346953000.25949.1560347040115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'
Title: Message Title Ilguiz Latypov edited a comment on JENKINS-54008 Re: Loading library fails - Error fetching remote repo 'origin' Ah sorry I targeted a wrong bug. I thought it was related to my frustration with the git plugin showing an error implying connectivity issues,{noformat}fatal: Could not read from remote repository{noformat}I think if the git plugin could add this trace message before invoking git,{noformat}echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."{noformat}dozens of devops would be happier.My problem resolved when I saw that I was using a wrong credential, which did not agree with the error message. Oh and whoever suggested to try a bare {{git@git../repo.git}} URL on StackOverflow: this ignored the port number after the host name (we use a TCP port for reasons unknown). The " proper " {{ssh:// git@ HOST:PORT/REPO.git}} URL worked. 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.194621.1539241642000.25955.1560347460544%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57988) UI not reflecting the state of the list of servers
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57988 UI not reflecting the state of the list of servers Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-12 14:02 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda When duplicated server names are found, only the older server name is stored in the list of servers and it is serialized back to the xml. But the UI does not reflect the same. The UI still holds different entries for servers with same names. When Jenkins is restarted the UI reflects the state of the list. Add Comment
[JIRA] (JENKINS-57988) UI not reflecting the state of the list of servers
Title: Message Title Parichay Barpanda started work on JENKINS-57988 Change By: Parichay Barpanda 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199973.1560348132000.25957.1560348180184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57988) UI not reflecting the state of the list of servers
Title: Message Title Parichay Barpanda commented on JENKINS-57988 Re: UI not reflecting the state of the list of servers Joseph says he might have a solution. 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.199973.1560348132000.25958.1560348420043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen Labels: P4_B P4_A 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.199936.1560247579000.25960.1560348780217%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57989) Add support of plugin caching on the filesystem
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57989 Add support of plugin caching on the filesystem Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-12 14:21 Priority: Minor Reporter: Oleg Nenashev Marky Jackson to detalize the feature request Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57990) Avoid filtering contents without sensible data and do per-content anonymization
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-57990 Avoid filtering contents without sensible data and do per-content anonymization Issue Type: Bug Assignee: Ramon Leon Components: support-core-plugin Created: 2019-06-12 14:34 Priority: Minor Reporter: Ramon Leon Change the behavior of the Contents to avoid filtering when it's not needed. And change the way it's anonymized by delegating it to the component to avoid losing the structure of the information. Should be filtered NodesContent: include labels and filesystem path AboutUser AgentsConfigFile (secrets encrypted but maybe other sensitive info) BuildQueue: name of the job ConfigFileComponent (secrets encrypted but maybe other sensitive info) EnvironmentVariables JenkinsLogs
[JIRA] (JENKINS-57990) Avoid filtering contents without sensible data and do per-content anonymization
Title: Message Title Ramon Leon started work on JENKINS-57990 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199975.1560350087000.25965.1560350160104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Jonathan B commented on JENKINS-53952 Re: Linux slaves are not starting anymore Any updates on this? This failure to start spot instances makes it infeasible for us to upgrade past 1.39, but the occasional deadlocks when spawning instances (fixed in 1.42, apparently https://issues.jenkins-ci.org/browse/JENKINS-54187) are extremely disruptive. 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.194555.1539041035000.25968.1560350466711%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57987) Unable to add environment variable for jcasc token
Title: Message Title Parichay Barpanda commented on JENKINS-57987 Re: Unable to add environment variable for jcasc token To populate environment variable, if your using mvn hpi:run you can do GITLAB_PERSONAL_ACCESS_TOKEN="MYTOKEN" mvn hpi:run Or inside IntelliJ run configuration, you can add the environment variable 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.199972.1560346953000.25985.1560350520386%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57987) Unable to add environment variable for jcasc token
Title: Message Title Parichay Barpanda commented on JENKINS-57987 Re: Unable to add environment variable for jcasc token To populate environment variable, if your using mvn hpi:run you can do GITLAB_PERSONAL_ACCESS_TOKEN="MYTOKEN" mvn hpi:run Or inside IntelliJ run configuration, you can add the environment variable 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.199972.1560346953000.25986.1560350520400%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57987) Unable to add environment variable for jcasc token
Title: Message Title Parichay Barpanda updated JENKINS-57987 Jenkins / JENKINS-57987 Unable to add environment variable for jcasc token Change By: Parichay Barpanda 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199972.1560346953000.25988.1560350581731%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57987) Unable to add environment variable for jcasc token
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57987 Unable to add environment variable for jcasc token Change By: Parichay Barpanda Comment: To populate environment variable, if your using {color:#FF}{{mvn hpi:run}}{color} you can do {{GITLAB_PERSONAL_ACCESS_TOKEN="MYTOKEN" mvn hpi:run }}Or inside {color:#FF}IntelliJ{color} run configuration, you can add the environment variable 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.199972.1560346953000.25987.1560350581208%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57988) UI not reflecting the state of the list of servers
Title: Message Title Parichay Barpanda assigned an issue to Joseph Petersen Jenkins / JENKINS-57988 UI not reflecting the state of the list of servers Change By: Parichay Barpanda Assignee: Parichay Barpanda Joseph Petersen 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.199973.1560348132000.25990.1560350582560%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Karl Wirth edited a comment on JENKINS-57945 Re: p4 sync corrupts symlinks [~mrose] Thanks again. Problem reproduced. Reproduction steps:(1) mkdir linktest(2) cd linktest(3) mkdir source(4) mkdir links(5) cd source(6) echo Content > target.txt( 4 7 ) cd ../links(8) ln -s ../source/ target.txt link( 5 9 ) cd ..(10) p4 add * ... && p4 submit -d "Adding links"( 6 11 ) Create a new pipeline job that maps the 'linktest' directory. For example:{code:java}pipeline { agent { label 'master' } stages {stage("Repro") { steps {script {// Try same sync with checkout and p4sync. Swap by commenting out command not being tested. // p4sync charset: 'none', credential: 'Jenkins', populate: forceClean(have: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false), source: depotSource('//depot/testlink/...')checkout perforce(credential: 'Jenkins', populate: forceClean(have: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false), workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}', pinHost: false, spec: clientSpec(allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: '//depot/testlink/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}/...')))// List directory contentssh 'ls -lR'} }} }}{code}( 7 12 ) When job runs with 'p4sync' the 'link' file is a plain text file containing the word 'target.txt':{code:java}-r--r--r-- 1 jenkins jenkins 20 Jun 11 10 12 15 : 27 51 link{code}When job runs with 'checkout' the file is a symlink:{code:java}lrwxrwxrwx 1 jenkins jenkins 20 Jun 11 10 12 15 : 33 53 link -> ../source/ target.txt {code} Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda updated JENKINS-57747 Jenkins / JENKINS-57747 Add form validation for gitlab gold and ultimate server urls Change By: Parichay Barpanda 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199692.1559151818000.26001.1560352740099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57991) Improve the error message when the credentials of the remote Jenkins are not correct
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-57991 Improve the error message when the credentials of the remote Jenkins are not correct Issue Type: Improvement Assignee: Unassigned Components: job-import-plugin Created: 2019-06-12 15:41 Priority: Minor Reporter: Pierre Beitz Current situation does an error difficult to decrypt because the plugin doesn't check for the response status code: 2019-06-12 11:14:33.668+ [id=86689] SEVERE o.j.c.p.j.client.RestApiClient#getRemoteItems: Failed to list job from remote org.xml.sax.SAXParseException; lineNumber: 10; columnNumber: 3; The element type "hr" must be terminated by the matching end-tag "". at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) at org.jenkins.ci.plugins.jobimport.client.RestApiClient.getRemoteItems(RestApiClient.java:34) at org.jenkins.ci.plugins.jobimport.JobImportAction.doQueryInternal(JobImportAction.java:278) at org.jenkins.ci.plugins.jobimport.JobImportAction.doQuery(JobImportAction.java:174) Proposed fix checking for this status code: Jun 12, 2019 5:36:04 PM org.jenkins.ci.plugins.jobimport.client.RestApiClient getRemoteItems SEVERE: Failed to list job from remote /SEVERE: Failed to list job from remote /org.acegisecurity.AccessDeniedException: Remote Jenkins denied access. P
[JIRA] (JENKINS-57991) Improve the error message when the credentials of the remote Jenkins are not correct
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-57991 Improve the error message when the credentials of the remote Jenkins are not correct Change By: Pierre Beitz Assignee: Pierre Beitz 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.199976.1560354097000.26006.1560354120212%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57835) Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'
Title: Message Title Fraser Adair updated an issue Jenkins / JENKINS-57835 Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake' Change By: Fraser Adair Summary: Jenkins - Subversion - ' svn: E170001: HTTP proxy authorization failed ' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake' 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.199793.1559640434000.26010.1560354720249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Karl Wirth commented on JENKINS-57945 Re: p4 sync corrupts symlinks Hi Michael Rose - Matthew Smeeth was uanble to repro this on 2.166 so I just tried upgrading my Jenkins to 2.164.2 and it seems to have solved the problem. Therefore this looks like a Jenkins bug or at least related to the version of Java it ships with or other dependencies. Are you able to upgrade jenkins to confirm 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.199921.1560203497000.26009.1560354720229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57835) Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'
Title: Message Title Fraser Adair updated an issue Jenkins / JENKINS-57835 Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake' Change By: Fraser Adair Connectivity between Jenkins and Subversion fails intermittently with 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: 'Remote host closed connection during handshake' error these errors . When error appears it seems any further attempts result in same errors and Appears the only way to recover appears to be to restart Jenkins. Can happen a few times a day but can also go several days without issue.Trying to understand why receiving these intermittent issues and how to resolve. 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.199793.1559640434000.26013.1560354780422%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57988) UI not reflecting the state of the list of servers
Title: Message Title Parichay Barpanda updated JENKINS-57988 Jenkins / JENKINS-57988 UI not reflecting the state of the list of servers Change By: Parichay Barpanda 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199973.1560348132000.26015.1560354780446%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57991) Improve the error message when the credentials of the remote Jenkins are not correct
Title: Message Title Pierre Beitz updated JENKINS-57991 Jenkins / JENKINS-57991 Improve the error message when the credentials of the remote Jenkins are not correct Change By: Pierre Beitz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199976.1560354097000.26012.1560354780411%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57991) Improve the error message when the credentials of the remote Jenkins are not correct
Title: Message Title Pierre Beitz started work on JENKINS-57991 Change By: Pierre Beitz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199976.1560354097000.26011.1560354780368%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57835) Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'
Title: Message Title Fraser Adair updated an issue Jenkins / JENKINS-57835 Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake' Change By: Fraser Adair 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.199793.1559640434000.26016.1560354840086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Meterian Bot commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Same here. Very frustrating as v0.31 is affected by this vulnerability: https://jenkins.io/security/advisory/2019-04-30/#SECURITY-443 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.198903.1556022985000.26019.1560355320960%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Meterian Bot edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Same here. Very frustrating as v0.31 is affected by this vulnerability: [ https://jenkins.io/security/advisory/2019-04-30/#SECURITY-443 ]But downgrading to 0.31 gives us back a configuration page that you can save 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.198903.1556022985000.26042.1560355321305%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52205) Add support of JCasC plugin to the Locale Plugin
Title: Message Title Oleg Nenashev stopped work on JENKINS-52205 Change By: Oleg Nenashev Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191965.1530087692000.26064.1560355380316%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52205) Add support of JCasC plugin to the Locale Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52205 Add support of JCasC plugin to the Locale Plugin Change By: Oleg Nenashev Labels: jcasc-compatibility stalled-pr Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191965.1530087692000.26065.1560355380336%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 Isaac Lew commented on JENKINS-43656 Re: Allow SSH Agent to be used with Promted Build Plugin Hello, I'm running into this issue as well. Are there any known workarounds? 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.26071.1560355740318%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU
Title: Message Title Jeff Thompson commented on JENKINS-56581 Re: org.jenkinsci.remoting.protocol.IOHub takes 100% CPU That is a surprising amount of messages, all with the same timestamp. I still have no idea what's going on with it, though. If you can gather any further information and diagnosis, please share 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198196.1552647394000.26077.1560357060384%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Abel Berhane commented on JENKINS-55013 Re: support for App Center Hi there Mez. I hope that things are going well. I have added the App Center Plugin and attempted to run a job. Question, will you be making continued updates to this plugin before the full depreciation of HockeyApp in November? 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.196049.1543936697000.26081.1560357960431%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan commented on JENKINS-55013 Re: support for App Center Hi Abel Berhane good question. For the HockeyApp plugin no. I'm not going to support that or allow updates to it. If something critical comes up I'll take a look but the intention is to drop it. For the AppCenter plugin yes I will. And I'm also open to pull requests if people want to contribute. 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.196049.1543936697000.26092.1560359100401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Dave Miller commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. I just upgraded to 1.10.0 to address a different issue, and I'm trying to understand why commit 283834eabea30f31cde59b1ab3b743a01b2f47cb, which claims to be associated with this ticket, is now throwing un-actionable "Severe warnings" when it finds duplicate SyncIDs. Why do duplicate syncIDs justify a severe log entry, what do they have to to with this ticket, and how should they be addressed? These "Severe warnings" are dramatically clogging our server logs. Paul Allen? 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.196127.154418064.26143.1560362700443%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56343) Intermittent java.io.NotSerializableException when running scripts in parallel
Title: Message Title Marcello de Sales commented on JENKINS-56343 Re: Intermittent java.io.NotSerializableException when running scripts in parallel def releasePrs = prMergesMessages.collectEntries{ prShaMessage -> def separate = prShaMessage.split(":") [separate[0], separate[1]] }.collect{ entry -> def matcher = entry.value =~ /(?#[0-9]+)/ def pr = matcher.find() ? matcher.group("prNumber") : "none" matcher = null [commitId: entry.key, prNumber: pr] } We've been getting this on the same problem around the Matcher... I got the problem to be resolved for a while by setting the matcher to null... However, today we started experiencing the intermittent behavior without code changes... I'm deciding to add a try/catch in this block with the hopes to not see this error again, but it's definitely difficult to spot the bug the first time due to the horrible logs... (See below) The code is in a shared library already and it breaks all of our different DSL-based builds... n exception which occurred: in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@63468bc9 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.LoopBlockScopeEnv@16c46b7c in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@63fd3e95 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@47149d74 in field com.cloudbees.groovy.cps.Continuable.e in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@24b7f5ac in field org.jenkinsci.plugins.workflow.cps.CpsThread.program in object org.jenkinsci.plugins.workflow.cps.CpsThread@3b872106 in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@606f1e48 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@606f1e48 Also: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.cancel(CpsBodyExecution.java:253) at org.jenkinsci.plugins.workflow.steps.BodyExecution.cancel(BodyExecution.java:76) at org.jenkinsci.plugins.workflow.cps.steps.ParallelStepExecution.stop(ParallelStepExecution.java:67) at org.jenkinsci.plugins.workflow.cps.CpsThread.stop(CpsThread.java:296) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$6.onSuccess(CpsFlowExecution.java:1151) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$6.onSuccess(CpsFlowExecution.java:1140) Caused: java.io.NotSerializableException: java.util.regex.Matcher at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:926) at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65) at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56) at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50) at org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179) at j
[JIRA] (JENKINS-55353) Upgrade Jenkins core to 2.138.4
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-55353 Upgrade Jenkins core to 2.138.4 Change By: Josh Soref After tested the plugin to compile against different Jenkins core versions, I have detected some changes that I have to make to test it. * Update Jenkins file to compile an test on Jenkins core 2.150.1, 2.164.1, and 2.168 (2 LTS and last weekly)* Compile and test weekly with JDK 11* Upgrade Jenkins core to 2.150.1, I will support 2 LTS versions* Remove JDKInstaler JDKInstaller references, is not used in ssh-slaves and it is no longer in Jenkins core, it is in tool-jdk plugin* Remove deprecated constructors, all these constructors were marked with a warning in logs 6 months ago.* Remove unused code* Remove old fields related to deprecated constructors* Fix tests after changes* Remove deprecated package depencency dependency javax.xml.bind* fix Inconsistent synchronization of hudson.plugins.sshslaves.SSHLauncher.host 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.196456.1546023241000.2615
[JIRA] (JENKINS-57992) QueueItemAuthenticatorMonitor.blurb is confusing for Windows users
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57992 QueueItemAuthenticatorMonitor.blurb is confusing for Windows users Issue Type: Task Assignee: Josh Soref Components: core Created: 2019-06-12 18:27 Priority: Minor Reporter: Josh Soref https://github.com/jenkinsci/jenkins/blob/5562b2fec6428b730a7b88ad6390a7ed741ba792/core/src/main/resources/jenkins/security/QueueItemAuthenticatorMonitor/message.properties#L1 blurb = Builds in Jenkins run as the virtual SYSTEM user with full permissions by default. \ On Windows, there's a SYSTEM account. Usually, users create per task accounts, e.g. a Jenkins account, and run services with those accounts. Because the Windows SYSTEM account (and is the equivalent of Unix root), it's very confusing to see a warning as the current warning displays. Add Comment
[JIRA] (JENKINS-57988) UI not reflecting the state of the list of servers
Title: Message Title Parichay Barpanda updated JENKINS-57988 By adding persistent descriptor and saving in setter. Jenkins / JENKINS-57988 UI not reflecting the state of the list of servers Change By: Parichay Barpanda 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.199973.1560348132000.26162.1560365880363%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda updated JENKINS-57747 Fixed it by fetching public projects from /projects endpoint. Jenkins / JENKINS-57747 Add form validation for gitlab gold and ultimate server urls Change By: Parichay Barpanda 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.199692.1559151818000.26160.1560365880262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57987) Unable to add environment variable for jcasc token
Title: Message Title Parichay Barpanda updated JENKINS-57987 Had a misunderstanding between global properties and environment variable. Jenkins / JENKINS-57987 Unable to add environment variable for jcasc token Change By: Parichay Barpanda 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.199972.1560346953000.26163.1560365940085%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57976) Add JCasC configuration instructions to README
Title: Message Title Parichay Barpanda updated JENKINS-57976 Added a basic instruction, will improve in future releases. Jenkins / JENKINS-57976 Add JCasC configuration instructions to README Change By: Parichay Barpanda 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.199960.1560285873000.26164.1560366000191%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57686) Add Java 8 functional interfaces for behavioural design pattern
Title: Message Title Parichay Barpanda updated JENKINS-57686 Added stream apis for gitlab servers filter methods Jenkins / JENKINS-57686 Add Java 8 functional interfaces for behavioural design pattern Change By: Parichay Barpanda 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.199621.1558824827000.26165.1560366000477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57947) [FUTURE] More secured method to manage credentials in JCasC yaml
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57947 [FUTURE] More secured method to manage credentials in JCasC yaml Change By: Parichay Barpanda Summary: [FUTURE] More secured method to manage credentials in JCasC yaml 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.199924.1560215713000.26166.1560366060237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.