[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Wisen Tanasa commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback To troubleshoot: Can you try to remove the "JQL Filter" and see if that triggers the build? (Check if you have configured Jenkins to talk to JIRA) If a build is still not triggered, can you remove the "Comment pattern" and see if that triggers the build? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7490.1584342061364%40Atlassian.JIRA.
[JIRA] (JENKINS-58167) Add option to not store affected files
Title: Message Title Sladyn Nunes commented on JENKINS-58167 Re: Add option to not store affected files Ulli Hafner I would like to get started with this issue, any pointers on getting started with this ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.200218.1561384768000.7488.1584342061265%40Atlassian.JIRA.
[JIRA] (JENKINS-61471) A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type
Title: Message Title
sgao thaich updated an issue
Jenkins / JENKINS-61471
A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found
Change By:
sgao thaich
Publishing fails after upgrading from 2.0.3 to 2.0.5 with com.sun.jersey.api.client.ClientHandlerException. {code:java}agent {archiveArtifacts artifacts: file.txtpublishConfluence pageName: 'My page', spaceName: 'SpaceABC', attachArchivedArtifacts: true}{code} {code:java}com.sun.jersey.api.client.ClientHandlerException: A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:630) at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:586) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:686) at com.sun.jersey.api.client.WebResource.get(WebResource.java:193) at com.atlassian.confluence.rest.client.AbstractRemoteService.getOption(AbstractRemoteService.java:181) at com.atlassian.confluence.rest.client.AbstractRemoteService.lambda$getFutureOption$1(AbstractRemoteService.java:77) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}A curl GET to myconfluence.com/rest/api/space/SpaceABC with the same basic authentication user gives med a valid json response for the space. What is the request the plugin is performing for uploading attachments? Does it need any special priviledge in confluence?
Add Comment
[JIRA] (JENKINS-61471) A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type
Title: Message Title
sgao thaich updated an issue
Jenkins / JENKINS-61471
A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found
Change By:
sgao thaich
Publishing fails after upgrading from 2.0.3 to 2.0.5 with com.sun.jersey.api.client.ClientHandlerException. {code:java}agent {archiveArtifacts artifacts: file.txtpublishConfluence pageName: 'My page', spaceName: 'SpaceABC', attachArchivedArtifacts: true}{code} {code:java}com.sun.jersey.api.client.ClientHandlerException: A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:630) at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:586) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:686) at com.sun.jersey.api.client.WebResource.get(WebResource.java:193) at com.atlassian.confluence.rest.client.AbstractRemoteService.getOption(AbstractRemoteService.java:181) at com.atlassian.confluence.rest.client.AbstractRemoteService.lambda$getFutureOption$1(AbstractRemoteService.java:77) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code} A It seems to fail when fetching the space, but a curl GET to myconfluence.com/rest/api/space/SpaceABC with the same basic authentication user gives med a valid json response for the space .What is the request the plugin is performing for uploading attachments? Does it need any special priviledge in confluence?
Add Comment
[JIRA] (JENKINS-61471) A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type
Title: Message Title
sgao thaich updated an issue
Jenkins / JENKINS-61471
A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found
Change By:
sgao thaich
Publishing fails after upgrading from 2.0.3 to 2.0.5 with com.sun.jersey.api.client.ClientHandlerException. {code:java}agent {archiveArtifacts artifacts: file.txtpublishConfluence pageName: 'My page', spaceName: 'SpaceABC', attachArchivedArtifacts: true}{code} {code:java}com.sun.jersey.api.client.ClientHandlerException: A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:630) at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:586) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:686) at com.sun.jersey.api.client.WebResource.get(WebResource.java:193) at com.atlassian.confluence.rest.client.AbstractRemoteService.getOption(AbstractRemoteService.java:181) at com.atlassian.confluence.rest.client.AbstractRemoteService.lambda$getFutureOption$1(AbstractRemoteService.java:77) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}It seems to fail when fetching the space, but a curl GET to myconfluence.com/rest/api/space/SpaceABC with the same basic authentication user gives med a valid json response. What is the request the plugin is performing for uploading attachments? Does it need any special priviledge in confluence?
Add Comment
[JIRA] (JENKINS-61487) While creating Jenkin Job,'cmd' is not recognized as an internal or external command in remote machine
Title: Message Title Vikas Gupta updated an issue Jenkins / JENKINS-61487 While creating Jenkin Job,'cmd' is not recognized as an internal or external command in remote machine Change By: Vikas Gupta Summary: While creating Jenkin Job Create Issue ,'cmd' is not recognized as an internal or external command in remote machine Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205172.1584340501000.7497.1584343080077%40Atlassian.JIRA.
[JIRA] (JENKINS-61471) A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type
Title: Message Title
sgao thaich updated an issue
Jenkins / JENKINS-61471
A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found
Change By:
sgao thaich
Publishing fails after upgrading from 2.0.3 to 2.0.5 with com.sun.jersey.api.client.ClientHandlerException. {code:java}agent {archiveArtifacts artifacts: file.txtpublishConfluence pageName: 'My page', spaceName: 'SpaceABC', attachArchivedArtifacts: true}{code} {code:java}com.sun.jersey.api.client.ClientHandlerException: A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:630) at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:586) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:686) at com.sun.jersey.api.client.WebResource.get(WebResource.java:193) at com.atlassian.confluence.rest.client.AbstractRemoteService.getOption(AbstractRemoteService.java:181) at com.atlassian.confluence.rest.client.AbstractRemoteService.lambda$getFutureOption$1(AbstractRemoteService.java:77) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}It seems to fail when fetching the space, but the response status is < 300 so we try to get a Space entity but content is html which is probably an error. A curl GET to myconfluence.com/rest/api/space/SpaceABC with the same basic authentication user gives med a valid json response.
Add Comment
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Ashok T R commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Amrut dengre, you should check All jenkins log, i hope you will catch the error there. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201336.1566200967000.7502.1584343920508%40Atlassian.JIRA.
[JIRA] (JENKINS-61451) Kubernetes plugin version 1.25.0 failed to load
Title: Message Title Sascha Vujevic updated an issue Jenkins / JENKINS-61451 Kubernetes plugin version 1.25.0 failed to load Change By: Sascha Vujevic Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205130.1584009115000.7511.1584344580087%40Atlassian.JIRA.
[JIRA] (JENKINS-61451) Kubernetes plugin version 1.25.0 failed to load
Title: Message Title Sascha Vujevic commented on JENKINS-61451 Re: Kubernetes plugin version 1.25.0 failed to load The kubernetes plugin in the version 1.25.0 can't be used with the current lts version of jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205130.1584009115000.7512.1584344640050%40Atlassian.JIRA.
[JIRA] (JENKINS-61489) New Job Screen : missing some french translations
Title: Message Title Jean-Baptiste Le Duigou started work on JENKINS-61489 Change By: Jean-Baptiste Le Duigou Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205174.1584344824000.7515.1584344880385%40Atlassian.JIRA.
[JIRA] (JENKINS-61489) New Job Screen : missing some french translations
Title: Message Title Jean-Baptiste Le Duigou updated an issue Jenkins / JENKINS-61489 New Job Screen : missing some french translations Change By: Jean-Baptiste Le Duigou Attachment: Screenshot 2020-03-16 at 08.44.20.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205174.1584344824000.7514.1584344880370%40Atlassian.JIRA.
[JIRA] (JENKINS-61489) New Job Screen : missing some french translations
Title: Message Title Jean-Baptiste Le Duigou created an issue Jenkins / JENKINS-61489 New Job Screen : missing some french translations Issue Type: Improvement Assignee: Jean-Baptiste Le Duigou Attachments: Screenshot 2020-03-16 at 08.44.20.png Components: core Created: 2020-03-16 07:47 Priority: Minor Reporter: Jean-Baptiste Le Duigou The new job screen is missing some translations (see screenshot). I will work on that in the next few days. Add Comment
[JIRA] (JENKINS-61487) While creating Jenkin Job,'cmd' is not recognized as an internal or external command in remote machine
Title: Message Title Vikas Gupta commented on JENKINS-61487 Re: While creating Jenkin Job,'cmd' is not recognized as an internal or external command in remote machine I have used JDK 11 for creating a Jenkins job. Thanks, Vikas Gupta Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205172.1584340501000.7516.1584345480048%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance after update
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance after update I noticed the msBuild warnings parser also does the job for me and thus removed one of the "grep"-layers. Unforunately the problem still persists. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201861.156818559.7517.1584345720046%40Atlassian.JIRA.
[JIRA] (JENKINS-61490) Support for 'wildcard' filtering with select repositories
Title: Message Title Bert Meedendorp created an issue Jenkins / JENKINS-61490 Support for 'wildcard' filtering with select repositories Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2020-03-16 08:17 Priority: Major Reporter: Bert Meedendorp I would like to propose an improvement of the selection option with the select button "Select repositories", to give this option to select the repositories with wildcards. In addition, the possibility of an option as automatic assigment for new repositories that meet the wildcard selection. Now it is a manual action for every repository. Add Comment
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-57513 Split the large databound constructors into databound setters Change By: Joseph Petersen Attachment: ec2-slave-template-2020-03-16 092547.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.199415.1558053245000.7521.1584347220427%40Atlassian.JIRA.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen commented on JENKINS-57513 Re: Split the large databound constructors into databound setters EC2 is still going down a dark road as this is still happening. https://github.com/jenkinsci/ec2-plugin/blame/master/src/main/java/hudson/plugins/ec2/SlaveTemplate.java Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.199415.1558053245000.7527.1584347220600%40Atlassian.JIRA.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen commented on JENKINS-57513 Re: Split the large databound constructors into databound setters Raihaan Shouhell please take a look Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.199415.1558053245000.7533.1584347340209%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre updated an issue Jenkins / JENKINS-58987 issue_updated trigger handler can't find "name" field in JSON Change By: Amrut dengre Comment: Hi [~ceilfors]I have configured my jenkins https url in jira's webhook. Also I am receiving "Received Webhook callback from comment. Event type: comment_created" in my jenkins logs when I add a comment in my Jira ticket.However the build is not getting triggered. Could you please help me in fixing this?We are on Jira cloud and my jenkins is running on Ec2 Instance.I have followed all the Troubleshooting steps listed on page [https://github.com/jenkinsci/jira-trigger-plugin]I am not able to understand "If you are seeing "Received Webhook callback ..." but your build is not triggered, your configuration for this plugin in Jenkins might be too restrictive, please double check." this part from troubleshooting steps.Please let me know if anything else is needed from my end.[~rlinux57],[~ashok_t_r] - Guys please guide me on this. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre updated an issue Jenkins / JENKINS-58987 issue_updated trigger handler can't find "name" field in JSON Change By: Amrut dengre Comment: My Project name in Jira is "TEST_PROJECT" and Key is "TP". Please refer amrut_config.png image to view the configuration done in jenkins job.Also find attached the webhook configuration(amrut_webhook.png) done at Jira end.Attached are the logs (amrut_jenkins_Logs)from jenkins post commenting in Jira issue . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201336.1566200967000.7563.1584347701780%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre updated an issue Jenkins / JENKINS-58987 issue_updated trigger handler can't find "name" field in JSON Change By: Amrut dengre Attachment: amrut_jenkins_Logs Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201336.1566200967000.7590.1584347702490%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre updated an issue Jenkins / JENKINS-58987 issue_updated trigger handler can't find "name" field in JSON Change By: Amrut dengre Attachment: amrut_config.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201336.1566200967000.7573.1584347702100%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre updated an issue Jenkins / JENKINS-58987 issue_updated trigger handler can't find "name" field in JSON Change By: Amrut dengre Attachment: amrut_webhook.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201336.1566200967000.7593.1584347702621%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre updated an issue Jenkins / JENKINS-58987 issue_updated trigger handler can't find "name" field in JSON Change By: Amrut dengre Comment: Hi [~ceilfors],Yes, I did saw the OpenCollective and know that you had been one of the Top Contributors to this plugin :). But just wanted to seek your guidance as what is going wrong from my end as I am seeing proper Webhook Callback Received messages in the jenkins logs.[~ashok_t_r],[~rlinux57] Any help from you guys would be much appreciated.Atleast have a look at the logs and the configs I have shared. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201336.1566200967000.7603.1584347760422%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Amrut dengre commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback Hi Wisen Tanasa, As asked I tried to remove "JQL Filter" from job config at jenkins end and kept only comment pattern as 'CODEBUILD'. But this didnt triggered the build.However when I added comment in Jira issue as 'CODEBUILD' I could see "Received Webhook callback from comment. Event type: comment_created" in jenkins logs. What do you meant by "Check if I have configured Jenkins to talk to JIRA"? Do you want me to add any new plugin to facilitate this communication? Also If I remove the 'Comment Pattern" then on which event by webhook should be called? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7612.1584348240105%40Atlassian.JIRA.
[JIRA] (JENKINS-56867) Jenkins does not allocate workspace for neither declarative pipeline nor scripted pipeline jobs
Title: Message Title Gopal Ahir commented on JENKINS-56867 Re: Jenkins does not allocate workspace for neither declarative pipeline nor scripted pipeline jobs We are also facing the same issue. Is there any update on it? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.198535.1554308056000.7614.1584348360102%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Amrut dengre commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback Hi Wisen Tanasa Since I have removed the JQL Filter and also the "comment pattern" I am getting the webhook logs for each and every comment made in Jira ticket for all the projects. So I am sure that the webhook call is being received properly but not sure what is causing build not to trigger. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7616.1584348961148%40Atlassian.JIRA.
[JIRA] (JENKINS-61491) Naginator plugin and Multi configuration job not working
Title: Message Title Javier Raez created an issue Jenkins / JENKINS-61491 Naginator plugin and Multi configuration job not working Issue Type: Bug Assignee: Nicolas De Loof Components: naginator-plugin Created: 2020-03-16 08:59 Priority: Minor Reporter: Javier Raez Using multi-configuration job, the Naginator plugin is not working. If we create a simple multi-configuration job with a sh step that generates an error, if we build it and click on retry (going inside of one of the multi-configuration builds that have failed) the jobs are not retried and we are redirected to the label configuration. Add Comment
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Wisen Tanasa commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback Amrut dengre That's great, at least you're not actually hitting network issue. Can you add back the "comment pattern", but keep the "JQL Filter"? Will it get the build triggered? I'm not quite sure why the "CODEBUILD" comment is not triggering the build, it should trigger it. On talking back to JIRA, this is required for JQL Filter to work, please see this section in the documentation: https://github.com/jenkinsci/jira-trigger-plugin#jenkins-global-configuration-one-time Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7620.1584349200515%40Atlassian.JIRA.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Raihaan Shouhell commented on JENKINS-57513 Re: Split the large databound constructors into databound setters Hey Joseph, I agree we really need to fix this issue. The whole class(SlaveTemplate) needs a rework so that not everything is final so setters would work. Matt Sicker I'm not sure how builder patterns will help this since I don't think casc will support a builder Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.199415.1558053245000.7623.1584349560233%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Amrut dengre commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback Hi Wisen Tanasa, Thanks for your promt responses. I have checked the checkbox for 'Build when comment is added to JIRA' and kept JQL Filter as ---> project = "TEST_PROJECT" and comment pattern as -> CODEBUILD but no luck. Also please find attached the Jira Trigger Configuration that I had already done before reporting the issue. Please refer once Jira_Trigger_Config.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7629.1584349980190%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Amrut dengre updated an issue Jenkins / JENKINS-61488 Jenkins Build not getting triggered even after receiving Jira Webhook Callback Change By: Amrut dengre Attachment: Jira_Trigger_Config.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7631.1584350040144%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Amrut dengre commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback I am Jira admin and have added my own credentials. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7633.1584350160096%40Atlassian.JIRA.
[JIRA] (JENKINS-60921) Revisit base typography
Title: Message Title Félix Queiruga Balado commented on JENKINS-60921 Re: Revisit base typography Can I mark this one as resolved? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204318.1580393661000.7635.1584350400258%40Atlassian.JIRA.
[JIRA] (JENKINS-48881) Stage still shown with NaNy NaNd when condition returns false
Title: Message Title Oleg Nenashev commented on JENKINS-48881 Re: Stage still shown with NaNy NaNd when condition returns false Any chance it was fixed in pipeline-stage-view-2.12 ? Does not look so taking the recent mentions in Twitter Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.187676.151558985.7638.1584350520499%40Atlassian.JIRA.
[JIRA] (JENKINS-61485) throttle Concurrent build not working when triggered from another job
Title: Message Title Aravind M updated an issue Jenkins / JENKINS-61485 throttle Concurrent build not working when triggered from another job Change By: Aravind M Attachment: Capture.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205170.1584335888000.7656.1584350940141%40Atlassian.JIRA.
[JIRA] (JENKINS-61485) throttle Concurrent build not working when triggered from another job
Title: Message Title Aravind M updated an issue Jenkins / JENKINS-61485 throttle Concurrent build not working when triggered from another job Change By: Aravind M Hi Team, I have installed throttle concurrent build plugin recently to run only 3 jenkins pipeline job in parallel and the remaining should wait in queue. When i trigger the job manually it works as expected but when I trigger the throttle job from another jenkins job using curl command or jenkins trigger parameter the throttle build job doesn't wait in queue and job is not even getting triggered if already 3 jobs were running. Kindly fix this The return code using curl command is 302 and please find attachment for the same. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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 disc
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Félix Queiruga Balado commented on JENKINS-61478 Re: "Apply" (and similar) banners look really bad with larger header bar It would make sense to revisit the banner. Can someone add it to the https://issues.jenkins-ci.org/browse/JENKINS-60919 epic and mark this as an improvement? We can triage it on the SIG meeting. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205161.1584140786000.7660.1584351180113%40Atlassian.JIRA.
[JIRA] (JENKINS-58167) Add option to not store affected files
Title: Message Title Ulli Hafner commented on JENKINS-58167 Re: Add option to not store affected files One thing to start with is to have a look at the coverage-api plugin and see which options they provide for the user. Then we can discuss if we are heading for the simple solution (boolean flag) or a more sophisticating approach. One question for the latter one is: should this be solved in my plugin? Or should this be part of a source code renderer plugin that handles such a thing for all Jenkins plugins that show source code in some form. I discussed this in the coverage API Gitter channel a couple of weeks ago. I think providing a plugin would definitely be the best way but also the most complex one. I think this would be a GSoC project on its own... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.200218.1561384768000.7663.1584351300331%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-61478 "Apply" (and similar) banners look really bad with larger header bar Change By: Félix Queiruga Balado Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205161.1584140786000.7665.1584351300364%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Félix Queiruga Balado edited a comment on JENKINS-61478 Re: "Apply" (and similar) banners look really bad with larger header bar It would make sense to revisit the banner. Can someone add it to the https://issues.jenkins-ci.org/browse/JENKINS-60919 epic and mark this as an improvement? We can triage it on the SIG meeting. *Edit:* nevermind, I did that Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205161.1584140786000.7667.1584351360131%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Daniel Beck commented on JENKINS-61478 Re: "Apply" (and similar) banners look really bad with larger header bar an improvement So you're saying the banner doesn't look any more broken now than it did in 2.221 before the UI refresh? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205161.1584140786000.7669.1584351780209%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Amrut dengre commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback Hi Wisen Tanasa, I just checked 'All Logs' in jenkins and could see below error - Error while serving https://.udchalo.com/jira-trigger-webhook-receiver/ org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) Any thoughts how to fix this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7672.1584351840112%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Amrut dengre updated an issue Jenkins / JENKINS-61488 Jenkins Build not getting triggered even after receiving Jira Webhook Callback Change By: Amrut dengre Comment: Hi [~ceilfors],I just checked 'All Logs' in jenkins and could see below error -Error while serving https://.udchalo.com/jira-trigger-webhook-receiver/ org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360)Any thoughts how to fix this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7676.1584351960215%40Atlassian.JIRA.
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title g hs1 commented on JENKINS-61476 Re: Can't stay logged in with latest versions. What issue is that? JENKINS-61029 Yep, your session will have expired by then, then the menu cannot load. Nope, I'm referring to when logged in, as well. Further, menus must be able to load regardless of session since users can be allowed to perform actions without logging in. Which is the latest known good version wrt being logged in? 2.221? Which is the first known bad one? 2.224? 217, as mentioned. 224, as also mentioned. I haven't tried anything in between, yet. Between the last known good, and first broken release, do you change plugin versions too? Or is the Jenkins (core) version the only thing that's changed to break/repair it? I updated the swarm plugin, which went from 217 to 218 due to the aforementioned critical issue. I can't remember if there were other updates. It's possible there were a couple but it wasn't a long list if so. They'd been updated fairly recently. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Amrut dengre commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback Any thoughts for fixing this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205173.1584341702000.7680.1584352080204%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Amrut dengre commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback Hi Wisen Tanasa, Just checked the 'All Logs' in jenkins from UI and can see below error - Error while serving https://.udchalo.com/jira-trigger-webhook-receiver/ org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.AttachmentJsonParser.parse(AttachmentJsonParser.java:35) at com.atlassian.jira.rest.client.internal.json.AttachmentJsonParser.parse(AttachmentJsonParser.java:27) at com.atlassian.jira.rest.client.internal.json.JsonWeakParserForJsonObject.parse(JsonWeakParserForJsonObject.java:39) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parseOptionalArray(IssueJsonParser.java:166) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:222) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser.parse(WebhookChangelogEventJsonParser.groovy:35) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:63) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook$processEvent.callCurrent(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.doIndex(JiraWebhook.groovy:51) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) Add Comment This message was sent by Atlassia
[JIRA] (JENKINS-60972) Rename the root breadcrumb
Title: Message Title Félix Queiruga Balado commented on JENKINS-60972 Re: Rename the root breadcrumb It would be great if you can work on this one! TBH there's no good support for breadcrumbs atm in Jenkins. They are just generated iterating through request ancestors, something that I guess is provided by Stapler (https://github.com/jenkinsci/jenkins/blob/07c48b03fb4c651e7314e7adbe3a0ef0fe249586/core/src/main/resources/lib/layout/breadcrumbBar.jelly#L44). A hacky way to do it that comes to mind could be to check if the ancestor points to the rootURL, then it could be replaced. That said, I'd favour using some Java code to do this. If we get a Breadcrumbs module going on, then we can expand it in the future with some utilities like: Get the last breadcrumb item. Check if a breadcrumb item is the current one (good for styling purposes). Prepend/append items to the breadcrumbs. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204437.1580894909000.7683.1584352200166%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Félix Queiruga Balado commented on JENKINS-61478 Re: "Apply" (and similar) banners look really bad with larger header bar I'm saying I don't consider it a bug. But it's OK, I'll mark it back as a bug and we can talk about it on the next SIG meeting, maybe we could even get some designs going. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205161.1584140786000.7685.1584352320102%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-61478 "Apply" (and similar) banners look really bad with larger header bar Change By: Félix Queiruga Balado Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205161.1584140786000.7687.1584352380176%40Atlassian.JIRA.
[JIRA] (JENKINS-61492) jenkins-test-harness test fails due "Comparison method violates its general contract!"
Title: Message Title Igor Fraa created an issue Jenkins / JENKINS-61492 jenkins-test-harness test fails due "Comparison method violates its general contract!" Issue Type: Bug Assignee: Unassigned Components: jenkins-test-harness Created: 2020-03-16 09:53 Environment: org.jenkins-ci.tools:gradle-jpi-plugin:0.38.0 Priority: Minor Reporter: Igor Fraa I'm trying to build https://github.com/jenkinsci/jira-trigger-plugin A number of tests in com.ceilfors.jenkins.plugins.jiratrigger.JiraCommentTriggerTest fail due ... Caused by: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) ... 8 more Caused by: java.lang.IllegalArgumentException: Comparison method violates its general contract! at java.util.ComparableTimSort.mergeLo(ComparableTimSort.java:744) ... More detailed stacktrace is at https://pastebin.com/GLw24FxF Also I have strange errors in gradle logs that may be related: 1.011 [id=31] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 1.130 [id=45] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Inspecting plugin /var/folders/v6/wny8k4yn4zq2n9cwdfq6glvhgn/T/jenkins6752789759896791797tmp/jira-trigger.jpl java.util.zip.ZipException: error in opening zip file
[JIRA] (JENKINS-61492) jenkins-test-harness test fails due "Comparison method violates its general contract!"
Title: Message Title
Igor Fraa updated an issue
Jenkins / JENKINS-61492
jenkins-test-harness test fails due "Comparison method violates its general contract!"
Change By:
Igor Fraa
I'm trying to build [https://github.com/jenkinsci/jira-trigger-plugin] A number of tests in com.ceilfors.jenkins.plugins.jiratrigger.JiraCommentTriggerTest fail due {code:java}...Caused by: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) ... 8 moreCaused by: java.lang.IllegalArgumentException: Comparison method violates its general contract! at java.util.ComparableTimSort.mergeLo(ComparableTimSort.java:744)...{code}More detailed stacktrace is at [https://pastebin.com/GLw24FxF]Also I have some strange errors in gradle logs that which may be related to the test failures :{code:java} 1.011 [id=31] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 1.130 [id=45] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Inspecting plugin /var/folders/v6/wny8k4yn4zq2n9cwdfq6glvhgn/T/jenkins6752789759896791797tmp/jira-trigger.jpljava.util.zip.ZipException: error in opening zip file{code}and{code:java} 1.568 [id=35] WARNING hudson.ClassicPluginStrategy#createClassJarFromWebInfClasses: Created /var/folders/v6/wny8k4yn4zq2n9cwdfq6glvhgn/T/jenkins6752789759896791797tmp/ui-samples-plugin/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness 1.581 [id=35] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 1.864 [id=42] WARNING hudson.ExtensionFinder$Sezpoz#scout: Failed to scout hudson.model.Hudson$DescriptorImpljava.lang.IncompatibleClassChangeError: hudson.model.Hudson and hudson.model.Hudson$DescriptorImpl disagree on InnerClasses attribute{code}more complete log is at [https://pastebin.com/7iyzSXEv]Jenkins-test-harness is used as following: [https://github.com/jenkinsci/jira-trigger-plugin/blob/7895e4f3b90fe7f8a7c2b98e69eb6a6c614e2e22/src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraCommentTriggerTest.groovy#L38]
Add Comment
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi Ashok T R, I could see below error in All Jenkins log. ust checked the 'All Logs' in jenkins from UI and can see below error - Error while serving https://.udchalo.com/jira-trigger-webhook-receiver/ org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.AttachmentJsonParser.parse(AttachmentJsonParser.java:35) at com.atlassian.jira.rest.client.internal.json.AttachmentJsonParser.parse(AttachmentJsonParser.java:27) at com.atlassian.jira.rest.client.internal.json.JsonWeakParserForJsonObject.parse(JsonWeakParserForJsonObject.java:39) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parseOptionalArray(IssueJsonParser.java:166) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:222) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser.parse(WebhookChangelogEventJsonParser.groovy:35) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:63) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook$processEvent.callCurrent(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.doIndex(JiraWebhook.groovy:51) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) Add Comment This me
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre edited a comment on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi [~ashok_t_r],I could see below error in All Jenkins log. ust Just checked the 'All Logs' in jenkins from UI and can see below error - Error while serving [https://.udchalo.com/jira-trigger-webhook-receiver/|https://.udchalo.com/jira-trigger-webhook-receiver/] org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.AttachmentJsonParser.parse(AttachmentJsonParser.java:35) at com.atlassian.jira.rest.client.internal.json.AttachmentJsonParser.parse(AttachmentJsonParser.java:27) at com.atlassian.jira.rest.client.internal.json.JsonWeakParserForJsonObject.parse(JsonWeakParserForJsonObject.java:39) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parseOptionalArray(IssueJsonParser.java:166) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:222) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser.parse(WebhookChangelogEventJsonParser.groovy:35) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:63) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook$processEvent.callCurrent(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.doIndex(JiraWebhook.groovy:51) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) Add Comment
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Ashok T R,Usama Tariq, Please assist me in applying below fix. Short term fix: fill in "name" variable with hardcoded value to satisfy the older version of JRJC. what exactly needs to be done here? Is it that we need to hadcode something in webhook URL at Jira side? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201336.1566200967000.7714.1584352800284%40Atlassian.JIRA.
[JIRA] (JENKINS-61383) Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning
Title: Message Title Why Name commented on JENKINS-61383 Re: Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning Well, some more info. We tried an alternative algorithm. All we do is we compare for each reference file of sorted (by lines) warning for source_file_x to current warning file 1) The error id, error message, and the source line contents (NOT the line number). This simple algorithm is giving quite excellent results for our case (currently as POC). The only 'flaws' that we found 1) Someone changed the source code line but did not resolved the issue This will be shown in our algorithm as resolved on one hand and a new error will be reported for the same line on the other hand. For our case this is perfectly ok. It is true that the real error was not resolved. However since someone bothered to touch the line, then from our point of view we can mark it as new, since the code is active it is better to show the error. BUT this triggered a new idea that will be described below. 2) Reordering content the source file without real change might cause real noise. Well in the POC we did not find such a case in our code base, and we tend to think that this is rare enough and will be accepted by users as known limitation. However once we will find such a case and assuming users will treat it as a bug we will enhance the simple algorithm to overcome it. New idea: The case that the line was changed but the problem exists although acceptable by users is still interesting to be identified for data mining. It seems that we would like to add another category to the [new, resolved, outstanding]: touched. So resolved means that the problem really solved and touched means that the line was changed therefore the full comparison fails but since the same error type still being reported for the line we will tag it as touched. So in the case of changed line instead of getting 2 messages: resolved + new. We will get only one : touched We still did not implement it, but soon will. What do you think? Add Comment
[JIRA] (JENKINS-61383) Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning
Title: Message Title Why Name edited a comment on JENKINS-61383 Re: Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning Well, some more info.We tried an alternative algorithm.All we do is we compare do diff for each reference file of sorted (by lines) warning for source_file_x to current warning file1) The source_file_name, error id, error message, and the source line contents (NOT the line number). This simple algorithm is giving quite excellent results for our case (currently as POC).The only 'flaws' that we found1) Someone changed the source code line but did not resolved the issue * This will be shown in our algorithm as resolved on one hand and a new error will be reported for the same line on the other hand. * For our case this is perfectly ok. It is true that the real error was not resolved. However since someone bothered to touch the line, then from our point of view we can mark it as new, since the code is active it is better to show the error. * BUT this triggered a new idea that will be described below. 2) Reordering content the source file without real change might cause real noise. * Well in the POC we did not find such a case in our code base, and we tend to think that this is rare enough and will be accepted by users as known limitation. * However once we will find such a case and assuming users will treat it as a bug we will enhance the simple algorithm to overcome it. New idea:The case that the line was changed but the problem exists although acceptable by users is still interesting to be identified for data mining.It seems that we would like to add another category to the [new, resolved, outstanding]: touched.So resolved means that the problem really solved and touched means that the line was changed therefore the full comparison fails but since the same error type still being reported for the line we will tag it as touched. So in the case of changed line instead of getting 2 messages: resolved + new. We will get only one : touched We still did not implement it, but soon will.What do you think? Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title Daniel Beck commented on JENKINS-61476 Re: Can't stay logged in with latest versions. Further, menus must be able to load regardless of session since users can be allowed to perform actions without logging in. Menus are loaded using POST requests, and if your sessions expired in the mean time, the CSRF protection will reject requests with a CSRF crumb that doesn't match the session. And since you keep getting logged out, I would guess that happens even without you noticing immediately, and the only visible result is that menus don't open. The browser console will bring certainty, HTTP 403 would be expected for POST requests if the session is expired. I can't remember if there were other updates. It's possible there were a couple but it wasn't a long list if so. They'd been updated fairly recently. To clarify, is the following correct: You updated Jenkins from 2.217 to 2.224, and some plugins. It broke. You downgraded Jenkins from 2.224 to 2.217. It works again. Or is it rather You updated Jenkins from 2.217 to 2.224, and some plugins. It broke. You downgraded Jenkins from 2.224 to 2.217 and reverted the plugin updates. It works again. I can't go beyond 221 as the swarm issue will break our builds. Another thing confusing me. Swarm Plugin should break in 2.220 (not 2.221), and be fixed through an update to 3.18, which should work for any version of Jenkins. Do you use the auto-discovery feature that was removed? As general information, anything interesting in the Jenkins log? Add Comment
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Ashok T R commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Amrut dengre, this has to be fixed in plugin side i hope. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201336.1566200967000.7731.1584353520359%40Atlassian.JIRA.
[JIRA] (JENKINS-61429) Unable to move/reorder steps within a job
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-61429 Unable to move/reorder steps within a job Change By: Baptiste Mathus Released As: (towards) 2.226 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205106.1583931628000.7759.1584353761877%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Baptiste Mathus updated JENKINS-61224 Jenkins / JENKINS-61224 "Monitors" terminology should not be used in GUI Change By: Baptiste Mathus Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.226 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204778.158264254.7741.1584353761569%40Atlassian.JIRA.
[JIRA] (JENKINS-61429) Unable to move/reorder steps within a job
Title: Message Title Baptiste Mathus updated JENKINS-61429 Jenkins / JENKINS-61429 Unable to move/reorder steps within a job Change By: Baptiste Mathus Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205106.1583931628000.7762.1584353762010%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Baptiste Mathus updated JENKINS-61224 Jenkins / JENKINS-61224 "Monitors" terminology should not be used in GUI Change By: Baptiste Mathus Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204778.158264254.7748.1584353761711%40Atlassian.JIRA.
[JIRA] (JENKINS-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Daniel Beck updated JENKINS-54662 Jenkins / JENKINS-54662 hudson.model.UsageStatistics not compatible with CasC plugin Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: 2.226 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.195453.1542317055000.7769.1584354180937%40Atlassian.JIRA.
[JIRA] (JENKINS-61424) Missing french translation on main page
Title: Message Title Daniel Beck updated JENKINS-61424 Jenkins / JENKINS-61424 Missing french translation on main page Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: 2.226 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205087.1583914912000.7774.1584354181039%40Atlassian.JIRA.
[JIRA] (JENKINS-61465) Make Functions#checkAnyPermission work on objects that aren't AccessControlled
Title: Message Title Daniel Beck updated JENKINS-61465 Jenkins / JENKINS-61465 Make Functions#checkAnyPermission work on objects that aren't AccessControlled Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: 2.226 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205146.1584097006000.7776.1584354181061%40Atlassian.JIRA.
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title
g hs1 commented on JENKINS-61476
Re: Can't stay logged in with latest versions.
We seem to be speaking different languages here, somehow. I don't know why this isn't clear... {quote}To clarify, is the following correct:{quote} Neither. I went 217 -> 224 -> 225. At least the swarm plugin was updated on the way to 224. I said I'd revert if a fix wasn't found and, that being the case, I can't revert further than 221 because of Jenkins-61029. I haven't reverted anything yet. If we can't find a solution quickly I'll have to because things are currently painful. As general information, anything interesting in the Jenkins log?{quote} Today I found this, which may be relevant except that no-one was around yesterday to try and login, as far as I know, so it's a little odd in that respect. I don't know what these reports refer to, as yet.
Mar 15, 2020 5:48:01 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTrigger
New Stapler routing rules result in the URL "/authentication/login/" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "staticMethod jenkins.model.Jenkins getAuthentication". Learn more: https://jenkins.io/redirect/stapler-routing
Mar 15, 2020 5:48:28 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTrigger
New Stapler routing rules result in the URL "/version" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "staticMethod jenkins.model.Jenkins getVersion". Learn more: https://jenkins.io/redirect/stapler-routing
Mar 15, 2020 5:48:37 PM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleException
Caught unhandled exception with ID d8fa20da-b17a-4988-8a26-81718dd12060 java.lang.IllegalArgumentException: /..\pixfir~1\how_to_login.html at org.kohsuke.stapler.TokenList.(TokenList.java:66) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:667) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFil
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title
g hs1 edited a comment on JENKINS-61476
Re: Can't stay logged in with latest versions.
We seem to be speaking different languages here, somehow. I don't know why this isn't clear... \{quote}To clarify, is the following correct:\{quote}Neither. I went 217 -> 224 -> 225. At least the swarm plugin was updated on the way to 224. I said I'd revert if a fix wasn't found and, that being the case, I can't revert further than 221 because of Jenkins-61029. I haven't reverted anything yet. If we can't find a solution quickly I'll have to because things are currently painful. As general information, anything interesting in the Jenkins log?\{quote} Today I found this, which may be relevant except that no-one was around yesterday to try and login, as far as I know, so it's a little odd in that respect. I don't know what these reports refer to, as yet.{code:java}Mar 15, 2020 5:48:01 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTriggerNew Stapler routing rules result in the URL "/authentication/login/" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "staticMethod jenkins.model.Jenkins getAuthentication". Learn more: https://jenkins.io/redirect/stapler-routingMar 15, 2020 5:48:28 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTriggerNew Stapler routing rules result in the URL "/version" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "staticMethod jenkins.model.Jenkins getVersion". Learn more: https://jenkins.io/redirect/stapler-routingMar 15, 2020 5:48:37 PM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleExceptionCaught unhandled exception with ID d8fa20da-b17a-4988-8a26-81718dd12060 java.lang.IllegalArgumentException: /..\pixfir~1\how_to_login.html at org.kohsuke.stapler.TokenList.(TokenList.java:66) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:667) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFi
[JIRA] (JENKINS-61299) breaking forward slash inserted in download with proget jenkins plugin
Title: Message Title
Andrew Sumner commented on JENKINS-61299
Re: breaking forward slash inserted in download with proget jenkins plugin
Finally back up and running, would love to say I've finished unpacking, but still lots to do I've tried a number of different combinations and haven't been able to duplicate your issue. This is the latest incarnation of my script, can you try it out (you might need to update feed name, etc) and let me know what happens? node { bat ''' DEL *.TXT /Q DEL *.upack /Q ECHO Build Tag: %BUILD_TAG% > Example.txt ''' script { deployLocation = "deploy" } uploadProgetPackage artifacts: 'Example.txt', feedName: 'Example', groupName: 'jenkins/pipleline', packageName: 'JenkinsPackage', version: "1.0.${BUILD_NUMBER}" downloadProgetPackage downloadFolder: "${WORKSPACE}/${deployLocation}", downloadFormat: 'pkg', feedName: 'Example', groupName: 'jenkins/pipleline', packageName: 'JenkinsPackage', version: "1.0.${BUILD_NUMBER}" }
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.204879.1583187475000.7783.1584355080209%40Atlassian.JIRA.
[JIRA] (JENKINS-61384) warnings-ng plugin doesn't copy files from workspace if source directory is given
Title: Message Title Juergen Lorenz commented on JENKINS-61384 Re: warnings-ng plugin doesn't copy files from workspace if source directory is given Sorry for the late answer. I will try to explain how we use the cppcheck and the plugin. In our call to the cppcheck, we go (via makefile) to the folder "source" and give only the filenames and the directories of the include's as arguments. So the xml-file contains the filename for files in the folder "source", absolute paths for headers in the include folder of the project and absolute paths for headers in the include folder of other libraries (at a server). Before we use your warnings-ng plugin, we use cppcheck plugin to publish the results. Because this plugin need it (maybe in an old version), we add the absolute path to the filenames via a perl script. So we had absolute paths for all files. In the warnings-ng plugin I saw as tooltip the subfolders (under the workspace dir), if the extra soure directory was left empty. And the subfolders under the common root, if the extra soure directory was set to this common root. But I find a way to copy the files, as you suggest. And it works fine. So, if nobody else need the multiple roots (and maybe I misunderstand how this works), we can close this JIRA. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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-issu
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Amrut dengre commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Ashok T R Please assist me in fixing this. Shall I uninstall the Jira Trigger Plugin and install it back? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.198679.155502593.7788.1584355440403%40Atlassian.JIRA.
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title Daniel Beck commented on JENKINS-61476 Re: Can't stay logged in with latest versions. Those log messages look like your Jenkins is on an untrusted network and getting scanned/attacked using generic scripts. Doesn't seem related. I can't revert further than 221 because of Jenkins-61029 The updated Swarm Plugin should work with any version of Jenkins of the past two years, and the linked problem only occurs when using an older version of Swarm Plugin and Jenkins 2.220 or newer. So this should not affect your choice of core release at all unless you insist on a plugin downgrade. What security realm are you using? E.g. Active Directory, LDAP, Jenkins local user database, …? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205157.1584115782000.7804.1584355620159%40Atlassian.JIRA.
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title g hs1 commented on JENKINS-61476 Re: Can't stay logged in with latest versions. OK, I didn't expect the latest plugin to work with versions of core prior to 220 because of the change that occurred in 220 and broke the plugin. Are you sure that that's the case? We are and always have been using LDAP Please read before asking. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205157.1584115782000.7807.1584355980131%40Atlassian.JIRA.
[JIRA] (JENKINS-9430) zip of workspace folders does garble filenames with german characters.
Title: Message Title Johannes Schmieder commented on JENKINS-9430 Re: zip of workspace folders does garble filenames with german characters. Can be closed. Works as expected. Tested with Jenkis Version 2.204.5 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.139597.1303139737000.7814.1584356340546%40Atlassian.JIRA.
[JIRA] (JENKINS-60505) Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55
Title: Message Title Anda Sorina Laakso commented on JENKINS-60505 Re: Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55 I was not able to reproduce the issue. In case the error still persists, please send me the console output from Jenkins. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203596.1576509162000.7810.1584356340478%40Atlassian.JIRA.
[JIRA] (JENKINS-60505) Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55
Title: Message Title Anda Sorina Laakso resolved as Fixed Jenkins / JENKINS-60505 Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55 Change By: Anda Sorina Laakso Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203596.1576509162000.7816.1584356340584%40Atlassian.JIRA.
[JIRA] (JENKINS-58167) Add option to not store affected files
Title: Message Title Sladyn Nunes commented on JENKINS-58167 Re: Add option to not store affected files Yeah I seen the thread on gitter, well then I guess I should move on to picking another issue, since the scope for the implementation is pretty wide. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.200218.1561384768000.7820.1584356400191%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/from does not exist
Title: Message Title Kalle Niemitalo created an issue Jenkins / JENKINS-61493 Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/from does not exist Issue Type: Improvement Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2020-03-16 12:03 Priority: Minor Reporter: Kalle Niemitalo After upgrading to Bitbucket Server 7.0.1, we get this kind of error for every pull request in multibranch projects in which Jenkins has been configured to build the result of merging the pull request: ERROR: Could not do lightweight checkout, falling back to heavyweight java.io.FileNotFoundException: URL: /rest/api/1.0/projects/SISU/repos/rahti-hybrid/browse/Jenkinsfile?at=pull-requests%2F771%2Fmerge&start=0&limit=500 at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getRequest(BitbucketServerAPIClient.java:831) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getFileContent(BitbucketServerAPIClient.java:1123) at com.cloudbees.jenkins.plugins.bitbucket.filesystem.BitbucketSCMFile.content(BitbucketSCMFile.java:98) at jenkins.scm.api.SCMFile.contentAsString(SCMFile.java:335) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:107) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427) git ls-remote origin shows that Bitbucket Server now publishes "refs/pull-requests/771/from" but not "refs/pull-requests/771/merge", even though the pull request has no merge conflicts (the target branch even has no new commits)
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Kalle Niemitalo updated an issue Jenkins / JENKINS-61493 Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist Change By: Kalle Niemitalo Summary: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/ from merge does not exist Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205179.1584360231000.7826.1584360300210%40Atlassian.JIRA.
[JIRA] (JENKINS-27082) Sparse checkouts and submodules: Error on checkout, submodule missing
Title: Message Title ASHOK MOHANTY commented on JENKINS-27082 Re: Sparse checkouts and submodules: Error on checkout, submodule missing I am getting the same error - when trying to use 'sparsecheckout' to checkout only a directory not full git-project. > git config core.sparsecheckout # timeout=10 > git config core.sparsecheckout true # timeout=10 > git read-tree -mu HEAD # timeout=10 Command "git read-tree -mu HEAD" returned status code 128: stdout: stderr: fatal: Not a valid object name HEAD git plugin 4.0.0 , git-client 3.0.0 , gitlab-plugin 1.4.3 . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.160872.1424699584000.7828.1584360360264%40Atlassian.JIRA.
[JIRA] (JENKINS-27082) Sparse checkouts and submodules: Error on checkout, submodule missing
Title: Message Title
ASHOK MOHANTY edited a comment on JENKINS-27082
Re: Sparse checkouts and submodules: Error on checkout, submodule missing
I am getting the same error - when trying to use 'sparsecheckout' to checkout only a directory not full git-project.{code:java} > git config core.sparsecheckout # timeout=10 > git config core.sparsecheckout true # timeout=10 > git read-tree -mu HEAD # timeout=10Command "git read-tree -mu HEAD" returned status code 128:stdout: stderr: fatal: Not a valid object name HEAD{code}git plugin 4.0.0 , git-client 3.0.0 , gitlab-plugin 1.4.3 . OR do we have any alternate solution to checkout directory (not complete project) in Jenkins job.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.160872.1424699584000.7836.1584360480237%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title
Kalle Niemitalo updated an issue
Jenkins / JENKINS-61493
Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Change By:
Kalle Niemitalo
After upgrading to Bitbucket Server 7.0.1, we get this kind of error for every pull request in multibranch projects in which Jenkins has been configured to build the result of merging the pull request:{noformat} ERROR: Could not do lightweight checkout, falling back to heavyweight java.io.FileNotFoundException: URL: /rest/api/1.0/projects/ SISU REDACTED /repos/ rahti-hybrid redacted /browse/Jenkinsfile?at=pull-requests%2F771%2Fmerge&start=0&limit=500 at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getRequest(BitbucketServerAPIClient.java:831) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getFileContent(BitbucketServerAPIClient.java:1123) at com.cloudbees.jenkins.plugins.bitbucket.filesystem.BitbucketSCMFile.content(BitbucketSCMFile.java:98) at jenkins.scm.api.SCMFile.contentAsString(SCMFile.java:335) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:107) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427){noformat}{{git ls-remote origin}} shows that Bitbucket Server now publishes "refs/pull-requests/771/from" but not "refs/pull-requests/771/merge", even though the pull request has no merge conflicts (the target branch even has no new commits). This might be related to ["the switch from a 3-way diff to a 2-way diff in pull requests"|https://confluence.atlassian.com/bitbucketserver/bitbucket-server-7-0-release-notes-990546638.html#BitbucketServer7.0releasenotes-Amodifiedbehaviorfordiffs] in Bitbucket Server 7.0.0.Jenkins then does the heavyweight checkout and successfully merges the pull request, so the project ultimately builds OK, but the heavyweight checkout consumes a lot of time and disk space.I don't know whether there is any simple way to fix this in the bitbucket-branch-source plugin. If Bitbucket Server has deliberately ceased publishing "refs/pull-requests/*/merge", perhaps the plugin could do a three-way merge on Jenkinsfile only, rather than on the entire tree. That would require a REST API for getting the commit ID of a merge base though, and I don't know whether such a thing exists.
[JIRA] (JENKINS-60902) Upgrade sshd-module to use SSHD 2.x
Title: Message Title Oleg Nenashev commented on JENKINS-60902 Re: Upgrade sshd-module to use SSHD 2.x Just an update here, 2.222.x LTS has happened recently. If we want to land an incompatible change, it would be great to do so in one month or so so that we can get plugins verified and, if needed, fixed before the next LTS Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204292.1580299553000.7846.1584360540239%40Atlassian.JIRA.
[JIRA] (JENKINS-61494) ‘Pipeline script from SCM’ do not get triggered by github webhooks from the pipeline script repo
Title: Message Title James Robson created an issue Jenkins / JENKINS-61494 ‘Pipeline script from SCM’ do not get triggered by github webhooks from the pipeline script repo Issue Type: Bug Assignee: Mark Waite Components: git-plugin, github-plugin Created: 2020-03-16 12:14 Environment: Jenkins: 2.204.5 git plugin: 4.2.2 github plugin: 1.29.5 Priority: Minor Reporter: James Robson I have 1 code repo that should be triggering jobs, and a separate repo for a jenkins pipeline library. There are 2 jenkins jobs that use the ‘GitHub hook trigger for GITScm polling’ build trigger, both are pipeline jobs using the ‘Pipeline script from SCM’ with the repository configured to point to the code repo and the ‘Branches to build’ set to ‘origin/develop’. The pipeline library is used inside the pipelines for these jobs. I would expect these jobs to have their polling triggered by pushes to the code repo, however they are only being triggered by pushes to the jenkins pipeline library repo. Using a log recorder set to get FINEST logs I can see: Received PushEvent for https://github.com/ Considering to poke Skipped because it doesn't have a matching repository. ... Received PushEvent for https://github.com/ Considering to poke Poked So something in jenkins seems to think these jobs do not use the code repository, but when a scan is triggered I see the following in the ‘Polling Log’: Started by event from 192.30.252.97 ... > git ls-remote -h https://github.com/ # timeout=10 So the repo poll is using the code repo, and the list of commits that show up in the ‘Changes’ list are from the code repo. It seems to be only these 2 jobs that are affected, no other job is being triggered by pushes to the pipeline library repo. If I change the job to have the pipeline script entered direct
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61480 Dark Theme Change By: Oleg Nenashev Labels: user-experience ux Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205164.1584202104000.7852.1584361080133%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Oleg Nenashev commented on JENKINS-61480 Re: Dark Theme A simple way to do so is to create a new theme for https://plugins.jenkins.io/simple-theme-plugin/ so that others can enable it. But it would work for all users of a Jenkins instance at once. Right now Jenkins does not support user-selected themes, but technically it could be added. CC Félix Queiruga Balado Jeremy Hartley, might be a topic for UX SIG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205164.1584202104000.7854.1584361320146%40Atlassian.JIRA.
[JIRA] (JENKINS-61425) Role Based access strategy - not consistent
Title: Message Title Oleg Nenashev started work on JENKINS-61425 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205089.1583915334000.7856.1584361500157%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title
Kalle Niemitalo updated an issue
Jenkins / JENKINS-61493
Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Change By:
Kalle Niemitalo
After upgrading to Bitbucket Server 7.0.1, we get this kind of error for every pull request in multibranch projects in which Jenkins has been configured to build the result of merging the pull request:{noformat} ERROR: Could not do lightweight checkout, falling back to heavyweight java.io.FileNotFoundException: URL: /rest/api/1.0/projects/REDACTED/repos/redacted/browse/Jenkinsfile?at=pull-requests%2F771%2Fmerge&start=0&limit=500 at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getRequest(BitbucketServerAPIClient.java:831) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getFileContent(BitbucketServerAPIClient.java:1123) at com.cloudbees.jenkins.plugins.bitbucket.filesystem.BitbucketSCMFile.content(BitbucketSCMFile.java:98) at jenkins.scm.api.SCMFile.contentAsString(SCMFile.java:335) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:107) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427){noformat}{{git ls-remote origin}} shows that Bitbucket Server now publishes "refs/pull-requests/771/from" but not "refs/pull-requests/771/merge", even though the pull request has no merge conflicts (the target branch even has no new commits). This might be related to ["the switch from a 3-way diff to a 2-way diff in pull requests"|https://confluence.atlassian.com/bitbucketserver/bitbucket-server-7-0-release-notes-990546638.html#BitbucketServer7.0releasenotes-Amodifiedbehaviorfordiffs] in Bitbucket Server 7.0.0.Jenkins then does the heavyweight checkout and successfully merges the pull request, so the project ultimately builds OK, but the heavyweight checkout consumes a lot of time and disk space. I don't know whether there is There might not be any simple way to fix improve this in the bitbucket-branch-source plugin. If Bitbucket Server has deliberately ceased publishing "refs/pull-requests/*/merge", perhaps the plugin could do a three-way merge on Jenkinsfile only, rather than on the entire tree. That would require - One way might be to use the REST API to get Jenkinsfile from the target branch ([/rest/api/1.0/projects/\{projectKey\}/repos/\{repositorySlug\}/browse/\{path:.*\}|https://docs.atlassian.com/bitbucket-server/rest/7.0.1/bitbucket-rest.html#idp208]) and any Jenkinsfile changes of the pull request as a patch ([/rest/api/1.0/projects/\{projectKey\}/repos/\{repositorySlug\}/pull-requests/\{pullRequestId\}.patch|https://docs.atlassian.com/bitbucket-server/rest/7.0.1/bitbucket-rest.html#idp289] gives the standard diff format but does not support limiting to a single file; [/rest/api/1.0/projects/\{projectKey}/repos/\{repositorySlug}/pull-requests/\{pullRequest
[JIRA] (JENKINS-61402) Jenkins Docker Start Up Very Slow
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61402 Jenkins Docker Start Up Very Slow Change By: Oleg Nenashev Component/s: _unsorted Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205056.1583771459000.7858.1584361560221%40Atlassian.JIRA.
[JIRA] (JENKINS-61470) When I assign users to roles, changes are not applied until Jenkins restart
Title: Message Title Oleg Nenashev commented on JENKINS-61470 Re: When I assign users to roles, changes are not applied until Jenkins restart Something has changed recently, likely influence of the Jenkins Core Updates Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205151.1584105999000.7864.1584361620196%40Atlassian.JIRA.
[JIRA] (JENKINS-61470) When I assign users to roles, changes are not applied until Jenkins restart
Title: Message Title Oleg Nenashev started work on JENKINS-61470 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205151.1584105999000.7862.1584361620163%40Atlassian.JIRA.
[JIRA] (JENKINS-61316) role-strategy-plugin shows all users for all users
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61316 role-strategy-plugin shows all users for all users Change By: Oleg Nenashev Labels: plugin role_strategy security Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204902.1583276654000.7866.1584361680137%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Kalle Niemitalo commented on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist Mentioned in BSERV-11477 (comment). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205179.1584360231000.7868.1584361860114%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Kalle Niemitalo updated an issue Jenkins / JENKINS-61493 Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist Change By: Kalle Niemitalo Environment: Jenkins 2.204.5Bitbucket Branch Source Plugin 2.7.0Bitbucket Server 7.0.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205179.1584360231000.7870.1584361980196%40Atlassian.JIRA.
[JIRA] (JENKINS-61316) role-strategy-plugin shows all users for all users
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61316 role-strategy-plugin shows all users for all users Change By: Oleg Nenashev Component/s: core Component/s: role-strategy-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204902.1583276654000.7874.1584362400355%40Atlassian.JIRA.
[JIRA] (JENKINS-61316) role-strategy-plugin shows all users for all users
Title: Message Title Oleg Nenashev commented on JENKINS-61316 Re: role-strategy-plugin shows all users for all users Currently Jenkins user listing is tied to the Overall/read permission, so all users with such permission will be able to see users. It is managed by the Jenkins Core, so there is nothing what could be done on the plugin level. P.S: FTR you assigned the issue to yourself while creating it, so I have never received a notification Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204902.1583276654000.7872.1584362400312%40Atlassian.JIRA.
[JIRA] (JENKINS-61316) role-strategy-plugin shows all users for all users
Title: Message Title Oleg Nenashev updated JENKINS-61316 I believe it is a full duplicate of JENKINS-18884 (thanks to Daniel Beck for the link) Jenkins / JENKINS-61316 role-strategy-plugin shows all users for all users Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.c
[JIRA] (JENKINS-61316) role-strategy-plugin shows all users for all users
Title: Message Title Oleg Nenashev updated JENKINS-61316 Jenkins / JENKINS-61316 role-strategy-plugin shows all users for all users Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204902.1583276654000.7878.1584362460454%40Atlassian.JIRA.
[JIRA] (JENKINS-18884) Seperate Permission for People View to close Security Hole with AD Plugin
Title: Message Title Vladimír Čamaj commented on JENKINS-18884 Re: Seperate Permission for People View to close Security Hole with AD Plugin Created at 2013-07-23 10:03 Are you serious? What is the chance this security hole will be resolved this month? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.150331.1374573798000.7881.1584363480511%40Atlassian.JIRA.
