[JIRA] (JENKINS-59236) The public GitLab server is no needed to add by a user.
Title: Message Title Rick created an issue Jenkins / JENKINS-59236 The public GitLab server is no needed to add by a user. Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-09-05 05:47 Priority: Minor Reporter: Rick The public GitLab server API address can be thinking that is never changing. So, I would suggest that it's not necessary for a user adding it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57248) How to create an influxdb target for jenkins pipeline project?
Title: Message Title Aleksi Simell closed an issue as Cannot Reproduce Not enough information to reproduce this, closing issue. Jenkins / JENKINS-57248 How to create an influxdb target for jenkins pipeline project? Change By: Aleksi Simell Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199012.1556626416000.6875.1567662060244%40Atlassian.JIRA.
[JIRA] (JENKINS-59235) Able to see reason when hovering on Claim icon
Title: Message Title Barbara Ang assigned an issue to Unassigned Jenkins / JENKINS-59235 Able to see reason when hovering on Claim icon Change By: Barbara Ang Assignee: Arnaud TAMAILLON Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201692.1567644653000.6873.1567644840106%40Atlassian.JIRA.
[JIRA] (JENKINS-59235) Able to see reason when hovering on Claim icon
Title: Message Title Barbara Ang updated an issue Jenkins / JENKINS-59235 Able to see reason when hovering on Claim icon Change By: Barbara Ang Currently, when you hover over the Claim icon, it will display the name of person to who claimed it and also if the person who assigned the claim (if any) . It would be good if I can also see the reason of the claim without clicking into the link. !image-2019-09-05-12-47-49-846.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.201692.1567644653000.6871.1567644720150%40Atlassian.JIRA.
[JIRA] (JENKINS-59235) Able to see reason when hovering on Claim icon
Title: Message Title Barbara Ang created an issue Jenkins / JENKINS-59235 Able to see reason when hovering on Claim icon Issue Type: Improvement Assignee: Arnaud TAMAILLON Attachments: image-2019-09-05-12-47-49-846.png Components: claim-plugin, junit-plugin, xunit-plugin Created: 2019-09-05 00:50 Labels: claim Priority: Major Reporter: Barbara Ang Currently, when you hover over the Claim icon, it will display the name of person to claimed it and also if the person who assigned the claim. It would be good if I can also see the reason of the claim without clicking into the link. Add Comment
[JIRA] (JENKINS-59210) Build exactly the commit from the webhook
Title: Message Title Oleg Varshavsky commented on JENKINS-59210 Re: Build exactly the commit from the webhook Hi Mark, I have attached a screen shot of the Jenkins log, indicating that the SHA of the Jenkinsfile is different from the SHA of the checkout step. That happened because the build was triggered by a commit from Dev-1 (reflected by the first SHA in the screen shot), but within one second, Dev-2 committed their change (reflected by the second SHA in the screen shot). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201660.1567537848000.6867.1567643880146%40Atlassian.JIRA.
[JIRA] (JENKINS-59210) Build exactly the commit from the webhook
Title: Message Title Oleg Varshavsky updated an issue Jenkins / JENKINS-59210 Build exactly the commit from the webhook Change By: Oleg Varshavsky Attachment: Screen Shot 2019-09-04 at 5.24.18 PM.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.201660.1567537848000.6865.1567643520182%40Atlassian.JIRA.
[JIRA] (JENKINS-23743) Failure on Git Polling Log when using Linux Master and Windows Slave
Title: Message Title peter ricardo commented on JENKINS-23743 Re: Failure on Git Polling Log when using Linux Master and Windows Slave Thanks for the tip, I will try here and notice about the result ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.156130.1404999348000.6861.1567641420208%40Atlassian.JIRA.
[JIRA] (JENKINS-59229) csrf protection too strict?
Title: Message Title Nathan Neulinger commented on JENKINS-59229 Re: csrf protection too strict? Either way - it's clear that the change above has likely broken tons of legacy code that already was previously broken when enabling CSRF. Tons of examples on how to use it are now likely wrong/broken. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201686.1567613166000.6858.1567637880112%40Atlassian.JIRA.
[JIRA] (JENKINS-59229) csrf protection too strict?
Title: Message Title Nathan Neulinger commented on JENKINS-59229 Re: csrf protection too strict? Started getting this on my instance as well. In my case, changing my triggering code to maintain session cookies was sufficient to get it to work. Didn't find a "nice" way to do that with curl/wget though, so wound up switching to a perl based trigger. It seems like --cookie-jar SHOULD work, but didn't for me. I believe it's related to this: https://jenkins.io/security/advisory/2019-07-17/#SECURITY-626 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201686.1567613166000.6856.1567637820193%40Atlassian.JIRA.
[JIRA] (JENKINS-59225) jenkin job stuck at clone the repository on the batch script
Title: Message Title Mark Waite updated JENKINS-59225 Please don't use bug reports to request help with technical issues. Very few people read the bug reports and those few people are the same people that maintain plugins, provide fixes for plugins, and implement other capabilities. Please use the Jenkins user mailing list or one of the chat systems to request help. A larger group of users is available to assist and is more likely to provide help. Jenkins / JENKINS-59225 jenkin job stuck at clone the repository on the batch script Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59225) jenkin job stuck at clone the repository on the batch script
Title: Message Title Mark Waite updated JENKINS-59225 Jenkins / JENKINS-59225 jenkin job stuck at clone the repository on the batch script Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201682.1567605625000.6854.1567634580522%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Mark Waite commented on JENKINS-55948 Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked Carlos Garcia I'm not aware of anything in the changes between git client plugin 2.8.0 and 2.8.2 which would cause any difference in this behavior. However, since I don't know the root of the problem, I can't be certain that 2.8.2 will work in your environment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.197357.1549280175000.6845.1567632900232%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Mark Waite commented on JENKINS-55948 Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked I've seen the problem in git client 3.0.0 pre-releases and occasionally in git client plugin 2.8.x I've corrected the description to show that the issue is most visible with git client plugin 3.0.0 pre-release versions, including the most recent pre-release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.197357.1549280175000.6838.1567632840305%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-55948 Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked Change By: Mark Waite Summary: Git client 3.0.0 pre - rc release called from git parameter plugin fails, 2.x 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.197357.1549280175000.6831.1567632780376%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked
Title: Message Title Baptiste Mathus commented on JENKINS-55948 Re: Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked Please create a new Jira issue if you encounter problems. This one is specificly about the 3.0.0-rc that is now hidden from the Update Center. BTW Mark Waite should we close this now to be clearer that this very one is resolved? Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.197357.1549280175000.6824.1567632600386%40Atlassian.JIRA.
[JIRA] (JENKINS-59210) Build exactly the commit from the webhook
Title: Message Title Mark Waite commented on JENKINS-59210 Re: Build exactly the commit from the webhook As far as I understand it, the Pipeline code strives to assure that the same SHA1 that is used to checkout the Jenkinsfile is also used to checkout the repository for the build. I remember testing in some detail that it was behaving as expected a few years ago. I've not performed those detailed tests recently, but I'm not aware of any known cases where the SHA1 that reads the Jenkinsfile is different from the SHA1 of the checkout step. Are you certain that the SHA1 of the Jenkinsfile is different than the SHA1 of the repository in the workspace? Can you provide a set of steps that confirm the SHA1 of the Jenkinsfile is different than the SHA1 of the repository in the workspace? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201660.1567537848000.6822.1567632180209%40Atlassian.JIRA.
[JIRA] (JENKINS-59234) Job config.xml parameters removed on job run
Title: Message Title Patrick Murphy created an issue Jenkins / JENKINS-59234 Job config.xml parameters removed on job run Issue Type: Bug Assignee: Unassigned Components: core, flow-plugin Created: 2019-09-04 21:10 Priority: Minor Reporter: Patrick Murphy We noticed that the parameter block of our job's config.xml sometime gets cleared when a sub job is created. Example Before:false REQUEST_DATAjenkins.groovy.scripts.path false flavour.groovy true false Afterfalse jenkins.groovy.scripts.path false flavour.groovy true false Once it happens for the first time, it seems to happen consistently until jenkins is restarted entirely and the config.xml file restored from a source repository. However, given that we have to restart jenkins, we potentially have to wait for other jobs to finish which can result in productivity loss on the team. If this is a known issue, can you point me at the correct jira. Add Comment
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Pedro Salomao resolved as Not A Defect Jenkins / JENKINS-59169 JNLP4 Connect Error - Connection closed before acknowledgement sent Change By: Pedro Salomao Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201606.1567306209000.6819.1567629360122%40Atlassian.JIRA.
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Pedro Salomao updated an issue Jenkins / JENKINS-59169 JNLP4 Connect Error - Connection closed before acknowledgement sent Solution to this problem: tunnel through the ELB as to get slave/master connected. How to do this? Go to Jenkins Master → Nodes → → Advanced → Tunnel: ernal-aef67c013ca2d11e9b6ab02485d01370-111334679.us-west-1.elb.amazonaws.com:5 (Above takes for granted that security group/inbound has also been properly configured) This assumes that you have already configured agent port static to 5 - how? Jenkins -> global security -> Agents -> TCP port for inbound agents -> Fixed: 5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201606.1567306209000.6818.1567629180065%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Andrii Petrenko edited a comment on JENKINS-59161 Re: ERROR: 530 Authentication required Sorry, guys, but nothin fixed.it works fine, when you are sending test e-mail, but nothing works when you sending notification from the job. cpuld could you please take a look? maybe the same issue there? there is no difference with SSL or not SSL ERROR: 530 Authentication requiredcom.sun.mail.smtp.SMTPSendFailedException: 530 Authentication required at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:2057) at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1580) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1097) at javax.mail.Transport.send0(Transport.java:195) at javax.mail.Transport.send(Transport.java:124) at hudson.tasks.MailSender.run(MailSender.java:130) at hudson.tasks.Mailer.perform(Mailer.java:175) at hudson.tasks.Mailer.perform(Mailer.java:138) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201598.1567204978000.6814.1567628040283%40Atlassian.JIRA.
[JIRA] (JENKINS-59184) Do not serve project icons directly from gitlab server
Title: Message Title Parichay Barpanda commented on JENKINS-59184 Re: Do not serve project icons directly from gitlab server Thanks Christian Ciach for explaining. I will commit some changes and tag you in the pr for review. Currently I am switching between places so haven't been able to be active the past week and maybe 1 week more. The skip initial build is also an important issue for us. Once I am settled (in a week) will start working on fixing it. Please feel free to report bugs, for us it is always high on priority to fix user reported bugs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201622.156742570.6812.1567627380123%40Atlassian.JIRA.
[JIRA] (JENKINS-59184) Do not serve project icons directly from gitlab server
Title: Message Title Christian Ciach commented on JENKINS-59184 Re: Do not serve project icons directly from gitlab server If anyhow possible I think the Avatar should be copied to and served by jenkins. This assumes that you can access the actual image file through the gitlab api to copy the file over. If this is not possible, then I don't have a strong opinion about how to solve this. I just think jenkins should never ever show a broken image (to be exact, the browser shows no image at all when the user isn't currently logged into gitlab). Making this configurable as a trait would be just a workaround. I still wish to see the actual avatars of the gitlab projects, but I think there should be a way to archive that even if the user is currently logged out from gitlab. If course, this is only a minor issue and not a deal breaker at all. You shouldn't make it a priority to fix this for the next release (I think it is a much bigger deal that all branches and tags are automatically built when first importing a project into jenkins, even when using "skip initial build" of the "Build strategy plugin". I will try to validate this bug tomorrow before issuing a bug report.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201622.156742570.6807.1567625460120%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Andrii Petrenko updated JENKINS-59161 Jenkins / JENKINS-59161 ERROR: 530 Authentication required Change By: Andrii Petrenko Resolution: Fixed Status: Resolved In 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.201598.1567204978000.6802.1567624740491%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Andrii Petrenko commented on JENKINS-59161 Re: ERROR: 530 Authentication required Sorry, guys, but nothin fixed. it works fine, when you are sending test e-mail, but nothing works when you sending notification from the job. cpuld you please take a look? maybe the same issue there? ERROR: 530 Authentication required com.sun.mail.smtp.SMTPSendFailedException: 530 Authentication required at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:2057) at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1580) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1097) at javax.mail.Transport.send0(Transport.java:195) at javax.mail.Transport.send(Transport.java:124) at hudson.tasks.MailSender.run(MailSender.java:130) at hudson.tasks.Mailer.perform(Mailer.java:175) at hudson.tasks.Mailer.perform(Mailer.java:138) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201598.1567204978000.6800.1567624740467%40Atlassian.JIRA.
[JIRA] (JENKINS-59184) Do not serve project icons directly from gitlab server
Title: Message Title Parichay Barpanda commented on JENKINS-59184 Re: Do not serve project icons directly from gitlab server Christian Ciach Kindly tell me how to proceed, we will be making a release this Friday and trying to add this fix to the release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201622.156742570.6795.1567624440122%40Atlassian.JIRA.
[JIRA] (JENKINS-58383) Disable aggregated analysis results
Title: Message Title Stefan Thurnherr commented on JENKINS-58383 Re: Disable aggregated analysis results +1 for being able to completely disable any aggregated charts. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200507.1562597544000.6791.1567624260169%40Atlassian.JIRA.
[JIRA] (JENKINS-59219) Found invalid crumb
Title: Message Title Kent Granström commented on JENKINS-59219 Re: Found invalid crumb @Daniel Beck. Thanks. I have written an issue pointing towards the 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.201670.156758711.6789.1567624200136%40Atlassian.JIRA.
[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException
Title: Message Title Peter Ntende commented on JENKINS-58940 Re: ActiveDirectory.updateUserCache uncaughtException In addition to the Prometheus Metrics plugin, I also had to remove to roll back influxDb, Git plugin and all git related plugins to previous versions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201284.1565805612000.6784.1567623540358%40Atlassian.JIRA.
[JIRA] (JENKINS-59233) EC2 Plugin leaking file handles
Title: Message Title
John Lengeling updated an issue
Jenkins / JENKINS-59233
EC2 Plugin leaking file handles
Change By:
John Lengeling
*When the Github Org Folder Scan runs and tries to clean up old branch and PR builds, we see errors like this ".nfsX : Device or Resource Busy". See stack trace below: * {{FATAL: Failed to recompute children of Bluton Pull Requests » bluton}}{{jenkins.util.io.CompositeIOException: Unable to delete '/opt/apache/.jenkins/jobs/Bluton Pull Requests/jobs/bluton/branches/Docker123'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.}} \ {{ at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:95)}} \ {{ at hudson.Util.deleteRecursive(Util.java:294)}} \ {{ at hudson.Util.deleteRecursive(Util.java:283)}} \ {{ at hudson.model.AbstractItem.performDelete(AbstractItem.java:792)}} \ {{ at org.jenkinsci.plugins.workflow.job.WorkflowJob.performDelete(WorkflowJob.java:652)}} \ {{ at hudson.model.AbstractItem.delete(AbstractItem.java:776)}} \ {{ at hudson.model.Job.delete(Job.java:677)}} \ {{ at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:290)}} \ {{ at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)}} \ {{ at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025)}} \ {{ at hudson.model.ResourceController.execute(ResourceController.java:97)}} \ {{ at hudson.model.Executor.run(Executor.java:429)}}{{jenkins.util.io.CompositeIOException: Unable to remove file /opt/apache/.jenkins/jobs/Bluton Pull Requests/jobs/bluton/branches/Docker123/builds/41/.nfs080f5285009d}} \ {{ at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:248)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:201)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:212)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)}} \ {{ at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:92)}} \ {{ at hudson.Util.deleteRecursive(Util.java:294)}} \ {{ at hudson.Util.deleteRecursive(Util.java:283)}} \ {{ at hudson.model.AbstractItem.performDelete(AbstractItem.java:792)}} \ {{ at org.jenkinsci.plugins.workflow.job.WorkflowJob.performDelete(WorkflowJob.java:652)}} \ {{ at hudson.model.AbstractItem.delete(AbstractItem.java:776)}} \ {{ at hudson.model.Job.delete(Job.java:677)}} \ {{ at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:290)}} \ {{ at
[JIRA] (JENKINS-59197) support-core should report available processes for master
Title: Message Title Owen Wood updated JENKINS-59197 Jenkins / JENKINS-59197 support-core should report available processes for master Change By: Owen Wood 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.201640.1567473949000.6779.1567622520341%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Paulius Bulotas commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Do you have Prometheus plugin? Downgrading from 2.0.6 to 2.0.0 solved GUI issue for us. And random NPEs when saving user etc. As per JENKINS-58940 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201579.156710687.6775.1567622400145%40Atlassian.JIRA.
[JIRA] (JENKINS-59197) support-core should report available processes for master
Title: Message Title Owen Wood commented on JENKINS-59197 Re: support-core should report available processes for master Naming it "Available CPUs:" to fit in with the existing formatting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201640.1567473949000.6772.1567622100135%40Atlassian.JIRA.
[JIRA] (JENKINS-59197) support-core should report available processes for master
Title: Message Title Owen Wood started work on JENKINS-59197 Change By: Owen Wood Status: Reopened 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.201640.1567473949000.6769.1567621980252%40Atlassian.JIRA.
[JIRA] (JENKINS-40292) More Control of p4 task logging
Title: Message Title Bruce Evans commented on JENKINS-40292 Re: More Control of p4 task logging this works nicely for me Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176946.1481141079000.6765.1567621920220%40Atlassian.JIRA.
[JIRA] (JENKINS-59233) EC2 Plugin leaking file handles
Title: Message Title
John Lengeling created an issue
Jenkins / JENKINS-59233
EC2 Plugin leaking file handles
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-09-04 18:27
Environment:
Jenkins 1.164.1 EC2 Plugin: 1.42
Labels:
filehandle-leak
Priority:
Minor
Reporter:
John Lengeling
When the Github Org Folder Scan runs and tries to clean up old branch and PR builds, we see errors like this: FATAL: Failed to recompute children of Bluton Pull Requests » bluton jenkins.util.io.CompositeIOException: Unable to delete '/opt/apache/.jenkins/jobs/Bluton Pull Requests/jobs/bluton/branches/Docker123'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. {{ at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:95)}} {{ at hudson.Util.deleteRecursive(Util.java:294)}} {{ at hudson.Util.deleteRecursive(Util.java:283)}} {{ at hudson.model.AbstractItem.performDelete(AbstractItem.java:792)}} {{ at org.jenkinsci.plugins.workflow.job.WorkflowJob.performDelete(WorkflowJob.java:652)}} {{ at hudson.model.AbstractItem.delete(AbstractItem.java:776)}} {{ at hudson.model.Job.delete(Job.java:677)}} {{ at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:290)}} {{ at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)}} {{ at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025)}} {{ at hudson.model.ResourceController.execute(ResourceController.java:97)}} {{ at hudson.model.Executor.run(Executor.java:429)}}
[JIRA] (JENKINS-59197) support-core should report available processes for master
Title: Message Title Owen Wood commented on JENKINS-59197 Re: support-core should report available processes for master I think it makes more sense to place this under the "Java" section https://github.com/jenkinsci/support-core-plugin/blob/a4b4c63641619602510966ce9821f3b434b3755d/src/main/java/com/cloudbees/jenkins/support/impl/AboutJenkins.java#L335 as we are looking at the Java Runtime. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201640.1567473949000.6759.1567621320158%40Atlassian.JIRA.
[JIRA] (JENKINS-59210) Build exactly the commit from the webhook
Title: Message Title Oleg Varshavsky commented on JENKINS-59210 Re: Build exactly the commit from the webhook Hi Mark, In a freestyle Jenkins job this is not an issue, because once the webhook fires of, it checks out the code, which is then ready to be built. However, with a Pipeline job, it is a two step process. It first checks out the Jenkinsfile, then uses it to execute the checkout stage, if defined. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201660.1567537848000.6757.1567620540148%40Atlassian.JIRA.
[JIRA] (JENKINS-59232) Jenkins blocks on start
Title: Message Title Dario Louzado created an issue Jenkins / JENKINS-59232 Jenkins blocks on start Issue Type: Bug Assignee: Unassigned Attachments: jenkins.threaddump Components: core Created: 2019-09-04 18:01 Environment: Jenkins LTS Docker Image version 2.176.3 Linux AMD 64 / Docker 18.06.3-ce, Ubuntu 16.04 Labels: plugin jenkins Priority: Major Reporter: Dario Louzado After upgrading an old version of Sonarqube Scanner plugin (2.6.x) to the newest one, jenkins blocks on startup thread: "CreationItemListener.onJenkinsStart" #42 daemon prio=5 os_prio=0 tid=0x7fc028001000 nid=0x40 waiting for monitor entry [0x7fc0d83ef000] java.lang.Thread.State: BLOCKED (on object monitor) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:316) waiting to lock <0x0006c82f45d0> (a hudson.ExtensionList$Lock) at hudson.ExtensionList.iterator(ExtensionList.java:172) at jenkins.security.ClassFilterImpl.isBlacklisted(ClassFilterImpl.java:303) at hudson.remoting.ClassFilter$1.isBlacklisted(ClassFilter.java:125) at hudson.util.XStream2$BlacklistedTypesConverter.canConvert(XStream2.java:563) at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:59)
[JIRA] (JENKINS-58618) Only ignores PRs from untrusted sources "once"
Title: Message Title Liam Newman commented on JENKINS-58618 Re: Only ignores PRs from untrusted sources "once" Fair enough, I've returned the priority to Critical. I'm not the owner/maintainer of this plugin, just effected by it. For security issues like this, you should file an issue under the Jenkins Jira "SECURITY" project. That will likely get more attention that a general functionality issue. See https://jenkins.io/security/ for details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200782.1563892757000.6754.1567619760122%40Atlassian.JIRA.
[JIRA] (JENKINS-58618) Only ignores PRs from untrusted sources "once"
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-58618 Only ignores PRs from untrusted sources "once" Change By: Liam Newman Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200782.1563892757000.6752.1567619700392%40Atlassian.JIRA.
[JIRA] (JENKINS-58683) Builds from untrusted source on Branch Indexing
Title: Message Title Liam Newman commented on JENKINS-58683 Re: Builds from untrusted source on Branch Indexing Fair enough, I've returned the priority to Critical. I'm not the owner/maintainer of this plugin, just effected by it. For security issues like this, you should file an issue under the Jenkins Jira "SECURITY" project. That will likely get more attention that a general functionality issue. See https://jenkins.io/security/ for details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200966.1564154958000.6750.1567619700356%40Atlassian.JIRA.
[JIRA] (JENKINS-56654) raw HTML text being displayed by Rich Text Publisher plugin in Dashboard view
Title: Message Title Frank Lam commented on JENKINS-56654 Re: raw HTML text being displayed by Rich Text Publisher plugin in Dashboard view Is there an update on where this issue stands? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.198286.1553152716000.6746.1567619580216%40Atlassian.JIRA.
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Pedro Salomao updated an issue Jenkins / JENKINS-59169 JNLP4 Connect Error - Connection closed before acknowledgement sent Change By: Pedro Salomao Component/s: remoting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201606.1567306209000.6743.1567617960071%40Atlassian.JIRA.
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Pedro Salomao updated an issue Jenkins / JENKINS-59169 JNLP4 Connect Error - Connection closed before acknowledgement sent Change By: Pedro Salomao Component/s: core Component/s: oauth-credentials-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.201606.1567306209000.6742.1567617780088%40Atlassian.JIRA.
[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException
Title: Message Title Ian Williams commented on JENKINS-58940 Re: ActiveDirectory.updateUserCache uncaughtException We (the OP) do not have Prometheus plugin installed, so the issue remains unresolved. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201284.1565805612000.6737.1567615440185%40Atlassian.JIRA.
[JIRA] (JENKINS-59231) Improve test coverage on the RSS feature
Title: Message Title Wadeck Follonier created an issue Jenkins / JENKINS-59231 Improve test coverage on the RSS feature Issue Type: Task Assignee: Unassigned Components: core Created: 2019-09-04 16:42 Priority: Minor Reporter: Wadeck Follonier After the recent security correction concerning jelly views/pages, the RSS feeds pages were twice reported as bugged in two different regression tickets: JENKINS-58595 and JENKINS-59167. In order to reduce this risk in the future (still hoping we covered all the cases now), it will be preferable to improve the code coverage for that feature, especially because it's close to zero before the introduction of #4188. Thank you "Hoss Man" for the feedback about the lack of this ticket, leading to confusion and lost of time. Add Comment
[JIRA] (JENKINS-59195) Plugin archetypes should suggest GitHub as a default URL
Title: Message Title Jesse Glick updated JENKINS-59195 Jenkins / JENKINS-59195 Plugin archetypes should suggest GitHub as a default URL Change By: Jesse Glick 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.201636.1567453983000.6734.1567615321215%40Atlassian.JIRA.
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title Mark Waite updated JENKINS-59206 Jenkins / JENKINS-59206 Environment variables tag name and branch name set incorrectly Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201655.1567527731000.6728.1567615320926%40Atlassian.JIRA.
[JIRA] (JENKINS-59195) Plugin archetypes should suggest GitHub as a default URL
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-59195 Plugin archetypes should suggest GitHub as a default URL Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201636.1567453983000.6730.1567615320953%40Atlassian.JIRA.
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title Mark Waite updated JENKINS-59206 Jenkins / JENKINS-59206 Environment variables tag name and branch name set incorrectly Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201655.1567527731000.6732.1567615320983%40Atlassian.JIRA.
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title MICHAEL PERZEL commented on JENKINS-59206 Re: Environment variables tag name and branch name set incorrectly Thanks, that's exactly what i need. I do think it's unclear why git_branch is set to the the tag name but I no longer have a need for this 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.201655.1567527731000.6726.1567615200108%40Atlassian.JIRA.
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Ivan Tashev commented on JENKINS-59213 Re: P4 Plugin - Errors when syncing symlinks Hey Paul Allen, thank you for the responce. The error was actually revealed after I did a full wipe and recreate of the workspace (after basically deleting local files and p4 client). I am not sure this is an OS specific issue, as I can sync the files on the same build node with P4V using the same p4 client. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201664.156755142.6719.1567614840362%40Atlassian.JIRA.
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Ivan Tashev edited a comment on JENKINS-59213 Re: P4 Plugin - Errors when syncing symlinks Hey [~p4paul], thank you for the responce. The error was actually revealed after I did a full wipe and recreate of the workspace (after basically deleting local files and p4 client). I am not sure this is an OS specific issue, as I can sync the files on the same build node with P4V using the same p4 client. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201664.156755142.6720.1567614840374%40Atlassian.JIRA.
[JIRA] (JENKINS-59230) Queue maintainance task is kicked off before global config / jobs are loaded
Title: Message Title
James Nord created an issue
Jenkins / JENKINS-59230
Queue maintainance task is kicked off before global config / jobs are loaded
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-09-04 16:28
Priority:
Minor
Reporter:
James Nord
the queue maintaince task is running before Jenkins has even loaded its configuration. The only protection in maintain is against Jenkins.getInstanceOrNull() returning null. I would have thought at a minimum the queue should not do anything before we have reached JOBS_LOADED.
Sep 04, 2019 5:15:54 PM org.eclipse.jetty.server.Server doStart
INFO: Started @2708ms
Sep 04, 2019 5:15:54 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v4.0 running: controlPort=disabled
Sep 04, 2019 5:15:55 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Sep 04, 2019 5:15:57 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Sep 04, 2019 5:15:59 PM hudson.model.Queue maintain
FINE: Queue maintenance started on hudson.model.Queue@7ebe628a with Queue.Snapshot{waitingList=[];blockedProjects=[];buildables=[];pendings=[]}
Sep 04, 2019 5:15:59 PM hudson.model.Queue updateSnapshot
FINEST: Queue.Snapshot{waitingList=[];blockedProjects=[];buildables=[];pendings=[]} ? Queue.Snapshot{waitingList=[];blockedProjects=[];buildables=[];pendings=[]}; leftItems={}
Sep 04, 2019 5:15:59 PM hudson.model.Queue updateSnapshot
FINEST: Queue.Snapshot{waitingList=[];blockedProjects=[];buildables=[];pendings=[]} ? Queue.Snapshot{waitingList=[];blockedProjects=[];buildables=[];pendings=[]}; leftItems={}
Sep 04, 2019 5:16:04 PM hudson.model.Queue maintain
FINE: Queue maintenance started on hudson.model.Queue@7ebe628a with Queue.Snapshot{waitingList=[];blockedProjects=[];buildables=[];pendings=[]}
Sep 04, 2019 5:16:04 PM
[JIRA] (JENKINS-59229) csrf protection too strict?
Title: Message Title Jan Heylen created an issue Jenkins / JENKINS-59229 csrf protection too strict? Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-04 16:06 Environment: jenkins 2.176.3 lts docker image Labels: security Priority: Major Reporter: Jan Heylen tested as follows with 2.176.2 successfully: wget -q --auth-no-challenge --user jheylen --password XX --output-document - 'http://jenkins/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,":",//crumb)' crumb=Jenkins-Crumb:1e7fe08f74e2ad6814e309af63986292 curl -X POST -H Jenkins-Crumb:1e7fe08f74e2ad6814e309af63986292 --silent --basic -u jheylen:XXX 'http://jenkins/me/descriptorByName/jenkins.security.ApiTokenProperty/generateNewToken?newTokenName=temp' API_token=1103e007f9659c28d25ee... But with 2.176.3, we get: Sep 04, 2019 3:51:40 PM hudson.security.csrf.CrumbFilter doFilter WARNING: Found invalid crumb 22bdf12008e1ee08ae29a897a00f669d. Will check remaining parameters for a valid one... Sep 04, 2019 3:51:40 PM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /descriptorByName/hudson.security.LDAPSecurityRealm$CacheConfiguration/fillTtlItems by jheylen. Returning 403. for every crumb retrieved with above workflow. Is this an issue in 2.176.3, or are we using the api/crumb in a wrong way?
[JIRA] (JENKINS-59228) Pipeline script disappears from job configuration
Title: Message Title Daniel Everett created an issue Jenkins / JENKINS-59228 Pipeline script disappears from job configuration Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-04 16:02 Environment: Jenkins 2.176.3 Plugins: Test stability history (test-stability): 2.3 Pipeline: Declarative (pipeline-model-definition): 1.3.9 JIRA plugin (jira): 3.0.9 Copy Artifact Plugin (copyartifact): 1.42.1 ruby-runtime (ruby-runtime): 0.12 Pipeline: Model API (pipeline-model-api): 1.3.9 Variant Plugin (variant): 1.3 multi-module-tests-publisher (multi-module-tests-publisher): 1.44 Bitbucket Branch Source Plugin (cloudbees-bitbucket-branch-source): 2.4.6 _javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1 REST Implementation for Blue Ocean (blueocean-rest-impl): 1.19.0 Self-Organizing Swarm Plug-in Modules (swarm): 3.17 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin (jquery-detached): 1.2.1 Build Pipeline Plugin (build-pipeline-plugin): 1.5.8 Pipeline: Supporting APIs (workflow-support): 3.3 Environment Injector Plugin (envinject): 2.2.1 WMI Windows Agents Plugin (windows-slaves): 1.4 jQuery plugin (jquery): 1.12.4-1 Cppcheck Plug-in (cppcheck): 1.25 Credentials Plugin (credentials): 2.3.0 GitHub plugin (github): 1.29.4 Pipeline: Multibranch (workflow-multibranch): 2.21 SCM API Plugin (scm-api): 2.6.3 Parameterized Trigger plugin (parameterized-trigger): 2.35.2 Display URL for Blue Ocean (blueocean-display-url): 2.3.0 Pipeline: Multibranch with defaults (pipeline-multibranch-defaults): 2.0 Extended Choice Parameter Plug-In (extended-choice-parameter): 0.78 Robot Framework plugin (robot): 2.0.0 Git Pipeline for Blue Ocean (blueocean-git-pipeline): 1.19.0 Pipeline (workflow-aggregator): 2.6 TestRail Plugin (testrail): 1.0.7-SNAPSHOT (private-c1a177aa-daneve01) Token Macro Plugin (token-macro): 2.8 Pipeline: Basic Steps (workflow-basic-steps): 2.18 Apache HttpComponents Client 4.x API Plugin (apache-httpcomponents-client-4-api): 4.5.5-3.0 JUnit Realtime Test Reporter Plugin (junit-realtime-test-reporter): 0.6 Dashboard View (dashboard-view): 2.11 Mailer Plugin (mailer): 1.26 Blue Ocean (blueocean): 1.19.0 Trilead API Plugin (trilead-api): 1.0.3 Azure Commons Plugin (azure-commons): 1.0.4 File System SCM Plugin (filesystem_scm): 2.1 Pipeline: API (workflow-api): 2.37 built-on-column (built-on-column): 1.1 Branch API Plugin (branch-api): 2.5.4 Priority Sorter Plugin (PrioritySorter): 3.6.0 Run Condition Plugin (run-condition): 1.2 Build Environment Plugin (build-environment): 1.6 xUnit plugin (xunit): 2.3.5 Bitbucket
[JIRA] (JENKINS-58683) Builds from untrusted source on Branch Indexing
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-58683 Builds from untrusted source on Branch Indexing Change By: Liam Newman Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200966.1564154958000.6711.1567611600287%40Atlassian.JIRA.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title Devin Nusbaum resolved as Fixed Blue Ocean 1.19.0 was just released with a fix for at least some aspects of this issue (see JENKINS-58085). Please try it out, and if you are still seeing the problem, post a minimal Jenkinsfile that reproduces the issue. Jenkins / JENKINS-53816 [Blue Ocean] Completed stages appear to be skipped instead of finished Change By: Devin Nusbaum Status: Reopened Resolved Resolution: Fixed Released As: blue-ocean 1.19.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Devin Nusbaum updated JENKINS-58085 Blue Ocean 1.19.0 was just released with a fix for at least some aspects of this issue. Please try it out, and if you are still seeing the problem, post a minimal Jenkinsfile that reproduces the behavior you are seeing. Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: blue-ocean 1.19.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-59227) Global Pipeline Libraries configuration lost
Title: Message Title Daniel Everett moved an issue Jenkins / JENKINS-59227 Global Pipeline Libraries configuration lost Change By: Daniel Everett Project: Infrastructure Jenkins Key: INFRA JENKINS - 2254 59227 Workflow: classic default workflow JNJira + In-Review Component/s: core Component/s: pipeline-library Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201684.1567609146000.6667.1567609260290%40Atlassian.JIRA.
[JIRA] (JENKINS-58825) Requirements FIle causes exception during config save
Title: Message Title Alex Earl commented on JENKINS-58825 Re: Requirements FIle causes exception during config save It would be helpful to anyone who wants to look into this to see the stack trace. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201138.1565095063000.6664.1567608240238%40Atlassian.JIRA.
[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException
Title: Message Title Paulius Bulotas commented on JENKINS-58940 Re: ActiveDirectory.updateUserCache uncaughtException I can confirm that downgrading Prometheus plugin solved issues we are seeing... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201284.1565805612000.6659.1567607040193%40Atlassian.JIRA.
[JIRA] (JENKINS-59226) Add support for declarative pipeline
Title: Message Title
Michael Düsterhus updated an issue
Jenkins / JENKINS-59226
Add support for declarative pipeline
Change By:
Michael Düsterhus
This plugin looks great from the description. Please add it as declarative option to the pipeline. Something like:{code:java}pipeline { options {cleanWorkspaces(runBefore: true) } ...}{code}Or directly call it in any post section as normal 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.201683.1567606546000.6656.1567606800421%40Atlassian.JIRA.
[JIRA] (JENKINS-59226) Add support for declarative pipeline
Title: Message Title Michael Düsterhus created an issue Jenkins / JENKINS-59226 Add support for declarative pipeline Issue Type: Improvement Assignee: tspengler Components: hudson-wsclean-plugin Created: 2019-09-04 14:15 Priority: Major Reporter: Michael Düsterhus This plugin looks great from the description. Please add it as declarative option to the pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Michel Zanini commented on JENKINS-36544 Re: Allow setting environment variables for dynamic ec2 slaves This would be a good addition to the plugin. I use the same AMI ID, but I create different nodes with different labels, to be able to set different box sizes for different jobs matching those labels. For example, the same AMI ID is used, to create two t3.medium with "java" label to build Java apps, and two t3.small to build node apps with "node" label. I would like to be able to set different environment variables for them, but they are the same AMI, which makes this hard. If we could set different Node environment variables, already supported by Jenkins, but not supported by this plugin that would solve this issue nicely. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.172564.1468000478000.6645.1567605901378%40Atlassian.JIRA.
[JIRA] (JENKINS-59219) Found invalid crumb
Title: Message Title Daniel Beck commented on JENKINS-59219 Re: Found invalid crumb Based on the behavior described in https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/blob/a66210fb34fbc46a8a67da437e060d20681761c6/README_jenkins.md and from what I guess https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/blob/c8cb7b1d6f4dcb8e6225ab54329c81b6d4d198b4/src/main/java/se/bjurr/prnfb/service/PrnfbVariable.java#L142...L204 does, it looks like the client obtains a crumb, but does not retain the session ID. As documented in the security advisory, we implemented the expiration of crumbs by binding them to the HTTP session, and if two subsequent requests, one for a crumb, and another to perform an action, do not use the same session cookie, they will fail. This is expected behavior. As a workaround, you should be able to install the strict-crumb-issuer plugin and configure it to not check the session ID, but only do time-based expiration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201670.156758711.6633.1567605780163%40Atlassian.JIRA.
[JIRA] (JENKINS-59225) jenkin job stuck at clone the repository on the batch script
Title: Message Title rizwan nadeem created an issue Jenkins / JENKINS-59225 jenkin job stuck at clone the repository on the batch script Issue Type: Story Assignee: Mark Waite Attachments: jenkin issue.jpg Components: credentials-plugin, git-plugin Created: 2019-09-04 14:00 Environment: Jenkins master on centos, jenkins slaves are windows 7, builds are execute from windows 7 Priority: Critical Reporter: rizwan nadeem Hi, I'm running a jenkins job in which I added the batch script to perform some steps on windows VM from where builds are executed. previously it was running smoothly and now jenkins job at stuck at cloning repository. git user has full permissions, i can manually clone a repo without issues but when running from the Jenkins so it stuck. I need really help to investigate what things are causing this issue. The job is running from Jenkin slave VM which is windows 7 because of the dot net project. Error is : C:\Git>IF EXIST ptlIDSG3MobileCoreApi RMDIR ptlIDSG3MobileCoreApi /S /Q C:\Git>git clone https://myofficial repo Cloning into 'ptlIDSG3MobileApi'... fatal: InvalidOperationException encountered. Showing a modal dialog box or form when the application is not running in UserInteractive mode is not a valid operation. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application.
[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException
Title: Message Title Julien Duchesne commented on JENKINS-58940 Re: ActiveDirectory.updateUserCache uncaughtException Weirdly, on my instances, I had that issue and the bug was caused by the update of the `Prometheus Metrics` plugin from 2.0.0 to 2.0.6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201284.1565805612000.6626.1567605420317%40Atlassian.JIRA.
[JIRA] (JENKINS-59224) Add kubernetes-client-api plugin dependency to kubernetes and credentials provider plugins
Title: Message Title Kyle Cronin started work on JENKINS-59224 Change By: Kyle Cronin 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.201681.1567604817000.6619.1567604880092%40Atlassian.JIRA.
[JIRA] (JENKINS-59224) Add kubernetes-client-api plugin dependency to kubernetes and credentials provider plugins
Title: Message Title Kyle Cronin created an issue Jenkins / JENKINS-59224 Add kubernetes-client-api plugin dependency to kubernetes and credentials provider plugins Issue Type: Improvement Assignee: Kyle Cronin Components: kubernetes-client-api-plugin, kubernetes-credentials-provider-plugin, kubernetes-plugin Created: 2019-09-04 13:46 Labels: plugin dependencies Priority: Minor Reporter: Kyle Cronin Update kubernetes-plugin and kubernetes-credentials-provider-plugin to use the new kubernetes-client-api-plugin which contains the shared kubernetes client api's used by both. Add Comment
[JIRA] (JENKINS-32689) Load statistics graph don't show the correct number of executors
Title: Message Title Amedee Van Gasse commented on JENKINS-32689 Re: Load statistics graph don't show the correct number of executors This bug also affects me. Jenkins 2.176.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167843.1454097107000.6613.1567604760555%40Atlassian.JIRA.
[JIRA] (JENKINS-59219) Found invalid crumb
Title: Message Title Kent Granström commented on JENKINS-59219 Re: Found invalid crumb @daniel beck, that's rather cheaky since we have had to roll back to 2.189. The plugin asks for a crumb for each and ever call so it must me a valid case. Can you Plz take a look at the pull-request-notifier-for-bitbucket and/or talk to the developer since there must be something wrong in either side. After going back to 2.189 it works 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.201670.156758711.6611.1567604640144%40Atlassian.JIRA.
[JIRA] (JENKINS-59150) Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information
Title: Message Title Daniel Beck commented on JENKINS-59150 Re: Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information And regarding the reported problem here, there isn't one either. The complete log messages read: Sep 04, 2019 1:27:20 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onDispatchTrigger New Stapler dispatch rules result in the URL "/gerrit-trigger/serverStatuses" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement serverStatuses". Learn more: https://jenkins.io/redirect/stapler-facet-restrictions Sep 04, 2019 1:27:20 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTrigger New Stapler routing rules result in the URL "/gerrit-trigger/serverStatuses" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "method com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement getServerStatuses". Learn more: https://jenkins.io/redirect/stapler-routing These are two different messages, for two different potential ways the request could be routed: https://github.com/jenkinsci/gerrit-trigger-plugin/blob/master/src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement/serverStatuses.jelly (affected by change in 2.176.x) https://github.com/jenkinsci/gerrit-trigger-plugin/blob/771cbf10a95b88921b7ea6d658b9849afaee5f19/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement.java#L231 (affected by change in 2.138.x) The warnings are logged in the order they are attempted, first the view, then the getter. Everything here works as intended. Add Comment
[JIRA] (JENKINS-59150) Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information
Title: Message Title Daniel Beck closed an issue as Won't Fix Don't use a gerrit-trigger version that has been obsolete since February. Jenkins / JENKINS-59150 Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information Change By: Daniel Beck Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201586.1567168518000.6544.1567603560477%40Atlassian.JIRA.
[JIRA] (JENKINS-59159) Please delete these two files so that it doesn't show up in google search
Title: Message Title Daniel Beck closed an issue as Cannot Reproduce Links seem dead, so I assume they were deleted. Don't upload confidential information to a public issue tracker. Jenkins / JENKINS-59159 Please delete these two files so that it doesn't show up in google search Change By: Daniel Beck Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201596.1567202985000.6537.1567602900524%40Atlassian.JIRA.
[JIRA] (JENKINS-44772) User Scoped credentials are not used by the "withCredentials" pipeline step
Title: Message Title
Fernando Rosado Altamirano commented on JENKINS-44772
Re: User Scoped credentials are not used by the "withCredentials" pipeline step
I will clarify, i could use user scope credential using the workarround commented on following issue ticket : https://issues.jenkins-ci.org/browse/JENKINS-38963?focusedCommentId=318189=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-318189 The use of the single quotes around '${credential_id}' is mandatory, it is not the same issue commented (overwrite a credentialID) but perhaps exists some relation.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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.182827.1496920844000.6517.1567602840493%40Atlassian.JIRA.
[JIRA] (JENKINS-59203) Upgrading Jenkins to 2.176.3 breaks service hooks integration with Visualstudio.com
Title: Message Title Daniel Beck closed an issue as Not A Defect Unfortunate, but intentional (sort of). Clients should use an API token, and not set a CSRF token. Jenkins / JENKINS-59203 Upgrading Jenkins to 2.176.3 breaks service hooks integration with Visualstudio.com Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201648.1567512011000.6513.1567602780322%40Atlassian.JIRA.
[JIRA] (JENKINS-59181) The plain HTTP request was sent to HTTPS port
Title: Message Title Daniel Beck closed an issue as Cannot Reproduce Almost certainly a bad reverse proxy configuration, https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Nginx explains how to do it. Jenkins / JENKINS-59181 The plain HTTP request was sent to HTTPS port Change By: Daniel Beck Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201619.1567421969000.6510.1567602720573%40Atlassian.JIRA.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-55787
Switch labels from entry to checkbox
Change By:
Josh Soref
This is the preferred style:!https://user-images.githubusercontent.com/2119212/51774426-47af6f00-20c0-11e9-8f58-ce82bd17dee4.png! As opposed to:!https://user-images.githubusercontent.com/2119212/51774439-539b3100-20c0-11e9-9c96-6569a173d80c.png! or !https://user-images.githubusercontent.com/2119212/51774473-6f9ed280-20c0-11e9-922c-42ea7ddedd34.png! –I'm going to point to this issue for a bunch of plugins. Note: my initial efforts relied on using {{ optionalBlock }} instead of {{ entry }} + {{ checkbox }} . Unfortunately this interacts poorly w/ the form submission magic, and so rather than continue down that path, I'm switching to moving fields {{label}}'s from the {{ entry }} to the {{ checkbox }} . The rendering won't generally change from the examples above. Please don't close this ticket when an individual PR is merged, I'm using the same ticket for many plugins.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-59219) Found invalid crumb
Title: Message Title Daniel Beck closed an issue as Not A Defect I don't know what pull-request-notifier is, but it's almost certainly a problem of a long-living, static crumb configured in the client, something no longer supported unless a compatibility option is set as described in the LTS upgrade guide referenced from the security advisory. Closing as this doesn't show there's anything wrong with Jenkins; we explicitly no longer support some use cases with long living crumbs. Jenkins / JENKINS-59219 Found invalid crumb Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59198 NullPointerException in hudson.util.Secret$1.convert Change By: Daniel Beck Summary: jenkisn配置发送测试邮件失败，报空指针异常 NullPointerException in hudson.util.Secret$1.convert Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201641.1567478279000.6500.1567602540554%40Atlassian.JIRA.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Josh Soref Issue Type: Improvement Epic Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.197176.1548453513000.6497.1567602420270%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked
Title: Message Title Carlos Garcia commented on JENKINS-55948 Re: Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked There is a new update for git-client (2.8.2). Is it safe to use? Given Jose Barragan comment, it seems not . I would like to know before updating if it will cause any issue (I have 2.8.0 and it is working fine). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197357.1549280175000.6494.1567601220435%40Atlassian.JIRA.
[JIRA] (JENKINS-59223) [Blue Ocean] Cannot write inside text parameters
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-59223 [Blue Ocean] Cannot write inside text parameters Change By: Steve Todorov Component/s: 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.201680.1567600183000.6487.1567600860278%40Atlassian.JIRA.
[JIRA] (JENKINS-44772) User Scoped credentials are not used by the "withCredentials" pipeline step
Title: Message Title Fernando Rosado Altamirano commented on JENKINS-44772 Re: User Scoped credentials are not used by the "withCredentials" pipeline step Any progress or any workaround? We want to use user scope credentials to manage releases and it is not possible to use on pipelines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.182827.1496920844000.6469.1567600740600%40Atlassian.JIRA.
[JIRA] (JENKINS-59223) [Blue Ocean] Cannot write inside text parameters
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-59223 [Blue Ocean] Cannot write inside text parameters Change By: Steve Todorov We have been experiencing a very annoying issue with the new blue ocean UI. If you have a parameterized build and there is an `input type="text"` field anywhere in the parameters - it is impossible to enter anything inside that field. Once you click inside the text input the page redirects immediately to the latest build.I have attached a short video which demonstrates the issue. Workaround: If you right click inside the input field and then right click again - the cursor will appear and you should be able to write inside the input. P.S. I'm not very sure which is the "right" component, so apologize if it's the wrong one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201680.1567600183000.6466.1567600320273%40Atlassian.JIRA.
[JIRA] (JENKINS-59223) [Blue Ocean] Cannot write inside text parameters
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-59223 [Blue Ocean] Cannot write inside text parameters Issue Type: Bug Assignee: Unassigned Attachments: cannot-write-in-inputs-2019-9-4-1567599555863.webm Components: blueocean-plugin Created: 2019-09-04 12:29 Environment: Jenkins ver. 2.192 Labels: user-experience Priority: Minor Reporter: Steve Todorov We have been experiencing a very annoying issue with the new blue ocean UI. If you have a parameterized build and there is an `input type="text"` field anywhere in the parameters - it is impossible to enter anything inside that field. Once you click inside the text input the page redirects immediately to the latest build. I have attached a short video which demonstrates the issue. P.S. I'm not very sure which is the "right" component, so apologize if it's the wrong one.
[JIRA] (JENKINS-53861) Jenkins loses all InfluxDb targets in Manage Jenkins > Configure System after restart.
Title: Message Title Aleksi Simell updated an issue Jenkins / JENKINS-53861 Jenkins loses all InfluxDb targets in Manage Jenkins > Configure System after restart. Change By: Aleksi Simell Released As: 1.20 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.194387.153842659.6463.1567598640544%40Atlassian.JIRA.
[JIRA] (JENKINS-47495) job-dsl api-viewer fails because of IllegalStateException in plugin
Title: Message Title Slavomir Kundrik started work on JENKINS-47495 Change By: Slavomir Kundrik 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.185951.1508320245000.6455.1567597201206%40Atlassian.JIRA.
[JIRA] (JENKINS-47495) job-dsl api-viewer fails because of IllegalStateException in plugin
Title: Message Title Slavomir Kundrik assigned an issue to Slavomir Kundrik Jenkins / JENKINS-47495 job-dsl api-viewer fails because of IllegalStateException in plugin Change By: Slavomir Kundrik Assignee: Slavomir Kundrik Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.185951.1508320245000.6453.1567597200744%40Atlassian.JIRA.
[JIRA] (JENKINS-59164) Function toEmailSafeString is not working
Title: Message Title Stefan Spieker updated JENKINS-59164 Jenkins / JENKINS-59164 Function toEmailSafeString is not working Change By: Stefan Spieker 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.201601.1567246385000.6425.1567595040102%40Atlassian.JIRA.
[JIRA] (JENKINS-59178) Nullpointer exception in IssuesAggregator.updateMap
Title: Message Title Kent Granström commented on JENKINS-59178 Re: Nullpointer exception in IssuesAggregator.updateMap Ulli Hafner : Have to get back to you on this one since we have serious crumb-problems with the latest version (2.193) of Jenkins itself. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201615.1567417828000.6411.1567594860463%40Atlassian.JIRA.
[JIRA] (JENKINS-59222) Interactive Retry does not document user
Title: Message Title Bernd Eckenfels created an issue Jenkins / JENKINS-59222 Interactive Retry does not document user Issue Type: Improvement Assignee: Nicolas De Loof Components: naginator-plugin Created: 2019-09-04 10:59 Labels: audit description Priority: Minor Reporter: Bernd Eckenfels When having Naginator Plugin installed a failed job has a Retry button. If this is used the Job is described with „Started by Naginator". In this specific case (not automatically retried) it should add that it was an interactive user decision to use that. Or have it somehow visible in the Job-run screen. Add Comment
[JIRA] (JENKINS-59172) Enable publishing plugin README.md on plugins.jenkins.io
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59172 Enable publishing plugin README.md on plugins.jenkins.io Change By: Oleg Nenashev Component/s: adoptopenjdk-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.201609.1567365427000.6403.1567594560139%40Atlassian.JIRA.
[JIRA] (JENKINS-56501) Filter on p4-publish when using streams
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-56501 Filter on p4-publish when using streams Change By: Paul Allen Assignee: 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.198108.1552306897000.6402.1567593420121%40Atlassian.JIRA.
[JIRA] (JENKINS-56501) Filter on p4-publish when using streams
Title: Message Title Paul Allen started work on JENKINS-56501 Change By: Paul Allen 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.198108.1552306897000.6400.1567593360191%40Atlassian.JIRA.
[JIRA] (JENKINS-59221) Filter on Populate when using streams
Title: Message Title Paul Allen created an issue Jenkins / JENKINS-59221 Filter on Populate when using streams Issue Type: Task Assignee: Paul Allen Components: p4-plugin Created: 2019-09-04 10:34 Priority: Minor Reporter: Paul Allen Similar to JENKINS-56501. Provide a list of depot or local paths that are passed to the sync command, so the whole workspace is not synced. Auto Cleanup? whole workspace or just the paths HaveList? whole workspace or just the paths Add Comment
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Fritz Elfert edited a comment on JENKINS-55787 Re: Switch labels from entry to checkbox Why is the state of this ticked resolved(fixed) ?IMO, it should be set to resolved, once * all * plugins have the PRs merged, and for the jclouds-plugin, I can say the PR is incomplete: You missed 10 more checkboxes. Therefore; not (yet) merged! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.197176.1548453513000.6396.1567593120120%40Atlassian.JIRA.
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Paul Allen commented on JENKINS-59213 Re: P4 Plugin - Errors when syncing symlinks It's possible that the older 1.10.0 release may have left a 'bad' symlink in your workspace with strange permissions. You may need to use 'administrator' permissions to clean up the file. Windows has a few types of symlinks; the plugin only supports 'symlinks' not 'junctions' JENKINS-57955. If it still causes a problem please let me know. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.201664.156755142.6394.1567593060386%40Atlassian.JIRA.
