[JIRA] (JENKINS-58688) Separate K8s config for Cloud
Title: Message Title Long Nguyen assigned an issue to Long Nguyen Jenkins / JENKINS-58688 Separate K8s config for Cloud Change By: Long Nguyen Assignee: Pham Vu Tuan Long Nguyen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200977.1564297237000.2300.1564297260503%40Atlassian.JIRA.
[JIRA] (JENKINS-58688) Separate K8s config for Cloud
Title: Message Title Long Nguyen created an issue Jenkins / JENKINS-58688 Separate K8s config for Cloud Issue Type: Improvement Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2019-07-28 07:00 Labels: gsoc-2019 Priority: Minor Reporter: Long Nguyen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To
[JIRA] (JENKINS-58688) Separate K8s config for Cloud
Title: Message Title Long Nguyen resolved as Done Jenkins / JENKINS-58688 Separate K8s config for Cloud Change By: Long Nguyen Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200977.1564297237000.2301.1564297320103%40Atlassian.JIRA.
[JIRA] (JENKINS-58689) Remoting-Kafka-K8s-Coding-Phase-3
Title: Message Title Long Nguyen updated an issue Jenkins / JENKINS-58689 Remoting-Kafka-K8s-Coding-Phase-3 Change By: Long Nguyen Epic Name: Remoting-Kafka-K8s-Coding-Phase- 2 3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200978.156430461.2313.1564304640331%40Atlassian.JIRA.
[JIRA] (JENKINS-58689) Remoting-Kafka-K8s-Coding-Phase-3
Title: Message Title Long Nguyen assigned an issue to Long Nguyen Jenkins / JENKINS-58689 Remoting-Kafka-K8s-Coding-Phase-3 Change By: Long Nguyen Assignee: Long Vu Nguyen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200978.156430461.2312.1564304640311%40Atlassian.JIRA.
[JIRA] (JENKINS-58689) Remoting-Kafka-K8s-Coding-Phase-3
Title: Message Title Long Nguyen created an issue Jenkins / JENKINS-58689 Remoting-Kafka-K8s-Coding-Phase-3 Issue Type: Epic Assignee: Long Vu Components: remoting, remoting-kafka-plugin Created: 2019-07-28 09:03 Labels: gsoc-2019 Priority: Minor Reporter: Long Nguyen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-58689) Remoting-Kafka-K8s-Coding-Phase-3
Title: Message Title Long Nguyen updated an issue Jenkins / JENKINS-58689 Remoting-Kafka-K8s-Coding-Phase-3 Change By: Long Nguyen Sprint: GSoC 2019. Coding Phase 2 3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200978.156430461.2314.1564304700063%40Atlassian.JIRA.
[JIRA] (JENKINS-58690) Add retention strategy for Cloud
Title: Message Title Long Nguyen created an issue Jenkins / JENKINS-58690 Add retention strategy for Cloud Issue Type: New Feature Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-07-28 09:05 Labels: gsoc-2019 Priority: Major Reporter: Long Nguyen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-58691) require POST and permissions to doXXXXX methods
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-58691 require POST and permissions to doX methods Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2019-07-28 09:27 Priority: Minor Reporter: Ivan Fernandez Calvo there are some doX methods that not required any permission, we'd required the same we have in SSHLauncher doX methods. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley created an issue Jenkins / JENKINS-58692 Change in treatment of Success - Stable vs. Unstable Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-07-28 09:35 Priority: Major Reporter: Ben Cooksley We've recently noticed on our Jenkins instance (at build.kde.org) that builds which are unstable are no longer considered "Successful" by Jenkins. This means that all of our views are now broken, because we've used "Successful" as meaning it successfully built (even if tests failed). Our expectations appear to align with the Jenkins terminology guide ( https://wiki.jenkins.io/display/JENKINS/Terminology ) This behaviour appeared sometime after Jenkins 2.184, and can be viewed at https://build.kde.org/job/Applications/view/Everything%20-%20stable-kf5-qt5/job/kopete/job/stable-kf5-qt5%20SUSEQt5.12/ (Note that only Build #1 is considered Successful, even though all builds of that job had the result of being Unstable. The correct behaviour in this instance should be for the latest Successful activity for that job to be Build #4 - as it did complete successfully, even if it is unstable) Add Comment
[JIRA] (JENKINS-58693) Two jobs with the same name in folder - are not treated correctly in ALM Octane. Run created pipeline might trigger wrong job.
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-58693 Two jobs with the same name in folder - are not treated correctly in ALM Octane. Run created pipeline might trigger wrong job. Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-07-28 09:53 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200982.1564307603
[JIRA] (JENKINS-42369) agent docker parameters do not honor the current environment
Title: Message Title Jorge Machado commented on JENKINS-42369 Re: agent docker parameters do not honor the current environment I have another use case for this. Running builds with nvidia-docker we need to pass NV_GPU= 0,1 at container start ... This does not work with the environment directive Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179270.1488278418000.2321.1564310820462%40Atlassian.JIRA.
[JIRA] (JENKINS-53079) Could not copy slave.jar into '' on slave
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-53079 Could not copy slave.jar into '' on slave Change By: Ivan Fernandez Calvo Component/s: trilead-api-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193073.1534456155000.2339.1564313280164%40Atlassian.JIRA.
[JIRA] (JENKINS-53079) Could not copy slave.jar into '' on slave
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53079 Re: Could not copy slave.jar into '' on slave I've dug in how Trilead-ssh2 library implements the SSH error manage and it simply relays the error code and adds the error message described in SSH File Transfer Protocol: Status response so the implementation is correct, it depends on the implementation that the SSH server made and the error codes that it returns, if those codes are incorrect or lazy implemented the information that the Trilead-ssh2 can return has the same level of detail. So I am afraid that I can not do anything here to improve the user experience. https://github.com/jenkinsci/trilead-ssh2/blob/master/src/com/trilead/ssh2/SFTPv3Client.java#L1201 https://github.com/jenkinsci/trilead-ssh2/blob/master/src/com/trilead/ssh2/SFTPException.java https://github.com/jenkinsci/trilead-ssh2/blob/master/src/com/trilead/ssh2/sftp/ErrorCodes.java Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193073.1534456155000.2341.1564314120251%40Atlassian.JIRA.
[JIRA] (JENKINS-53079) Could not copy slave.jar into '' on slave
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-53079 Could not copy slave.jar into '' on slave Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193073.1534456155000.2343.1564314120282%40Atlassian.JIRA.
[JIRA] (JENKINS-48618) SSH Slaves should pass read timeout to TrileadSSH and gracefully handle it in the logic
Title: Message Title Ivan Fernandez Calvo closed an issue as Fixed Jenkins / JENKINS-48618 SSH Slaves should pass read timeout to TrileadSSH and gracefully handle it in the logic Change By: Ivan Fernandez Calvo Status: In Progress Closed Resolution: Fixed Released As: trilead-ssh2-build-217-jenkins-16 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187267.1513635711000.2345.1564315440198%40Atlassian.JIRA.
[JIRA] (JENKINS-50999) Repository Branch DropDown timesout
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-50999 Jenkins / JENKINS-50999 Repository Branch DropDown timesout Change By: Jose Blas Camacho Taboada Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190225.1524666248000.2347.1564315620401%40Atlassian.JIRA.
[JIRA] (JENKINS-58694) Not able to trigger build via API call
Title: Message Title
Babishan Maheswaran created an issue
Jenkins / JENKINS-58694
Not able to trigger build via API call
Issue Type:
Bug
Assignee:
Janario Oliveira
Components:
http-request-plugin
Created:
2019-07-28 14:07
Priority:
Minor
Reporter:
Babishan Maheswaran
I was trying to access jenkins via api, when api call is made in POSTMAN it is working perfectly fine, but if the same is accessed in an application(written in react), getting the following error
// code placeholder
"type": "default",
"status": 403,
"ok": false,
"headers": {
"map": {
"content-length": "813",
"x-permission-implied-by": "hudson.model.Hudson.Administer",
"x-you-are-in-group-disabled": "JENKINS-39402: use -Dhudson.security.AccessDeniedException2.REPORT_GROUP_HEADERS=true or use /whoAmI to diagnose",
"content-type": "text/html;charset=utf-8",
"x-content-type-options": "nosniff",
"date": "Sun, 28 Jul 2019 10:21:02 GMT",
"server": "Jetty(9.4.z-SNAPSHOT)",
"x-required-permission": "hudson.model.Hudson.Read",
"x-you-are-authenticated-as": "anonymous",
"x-jenkins-session": "63af948b",
"x-jenkins": "2.176.2",
"x-hudson": "1.395"
}
},
"url": "http://admin:admin@localhost:8080/api/json",
"_bodyInit": {
"_data": {
"size": 813,
"offset": 0,
"blobId": "dc017047-59b3-4dba-8762-38bc4d701714",
"__collector": null
}
},
"_bodyBlob": {
"_data": {
"size": 813,
"offset": 0,
"blobId": "dc017047-59b3-4dba-8762-38bc4d701714",
"__collector": null
}
}
}
From the above code, I tried disabling/enabling "x-you-are-in-group-disabled" but couldn't locate how/where
[JIRA] (JENKINS-58695) Allow group projects fetch for user owner
Title: Message Title Parichay Barpanda started work on JENKINS-58695 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200984.1564328712000.2378.1564328760219%40Atlassian.JIRA.
[JIRA] (JENKINS-58695) Allow group projects fetch for user owner
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58695 Allow group projects fetch for user owner Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-28 15:45 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Fetch all user projects (incld PRIVATE, PUBLIC, INTERNAL) repos from user account if `wantSubprojects()` is false. Fetch all owned projects (incld groups, subgroups) repos of which the user is the owner if `wantSubproject()` is true. Add Comment
[JIRA] (JENKINS-58695) Allow group projects fetch for user owner
Title: Message Title Parichay Barpanda updated JENKINS-58695 Jenkins / JENKINS-58695 Allow group projects fetch for user owner Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200984.1564328712000.2379.1564329000316%40Atlassian.JIRA.
[JIRA] (JENKINS-58694) Not able to trigger build via API call
Title: Message Title Babishan Maheswaran updated an issue Jenkins / JENKINS-58694 Not able to trigger build via API call Change By: Babishan Maheswaran Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200983.1564322832000.2381.1564329060197%40Atlassian.JIRA.
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Sai Kiran Challa commented on JENKINS-57796 Re: Checkmarx affected by JEP-200 I upgraded to 8.90.4 and still see the same error: ``` FATAL: Failed to deserialize response to UserRequest:com.checkmarx.jenkins.CxScanCallable@2a8aedd3: java.lang.SecurityException: Rejected: com.cx.restclient.dto.ScanResults; see https://jenkins.io/redirect/class-filter/ java.lang.SecurityException: Rejected: com.cx.restclient.dto.ScanResults; see https://jenkins.io/redirect/class-filter/ at hudson.remoting.ClassFilter.check(ClassFilter.java:77) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:135) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1866) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1749) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2040) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1571) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431) at hudson.remoting.UserRequest.deserialize(UserRequest.java:291) at hudson.remoting.UserRequest$NormalResponse.retrieve(UserRequest.java:326) at hudson.remoting.Channel.call(Channel.java:957) Caused: java.io.IOException: Failed to deserialize response to UserRequest:com.checkmarx.jenkins.CxScanCallable@2a8aedd3 at hudson.remoting.Channel.call(Channel.java:965) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at com.checkmarx.jenkins.CxScanBuilder.perform(CxScanBuilder.java:711) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)``` Add Comment
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Sai Kiran Challa updated an issue Jenkins / JENKINS-57796 Checkmarx affected by JEP-200 Change By: Sai Kiran Challa Comment: I upgraded to 8.90.4 and still see the same error: ```FATAL: Failed to deserialize response to UserRequest:com.checkmarx.jenkins.CxScanCallable@2a8aedd3: java.lang.SecurityException: Rejected: com.cx.restclient.dto.ScanResults; see [https://jenkins.io/redirect/class-filter/]java.lang.SecurityException: Rejected: com.cx.restclient.dto.ScanResults; see [https://jenkins.io/redirect/class-filter/] at hudson.remoting.ClassFilter.check(ClassFilter.java:77) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:135) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1866) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1749) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2040) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1571) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431) at hudson.remoting.UserRequest.deserialize(UserRequest.java:291) at hudson.remoting.UserRequest$NormalResponse.retrieve(UserRequest.java:326) at hudson.remoting.Channel.call(Channel.java:957)Caused: java.io.IOException: Failed to deserialize response to UserRequest:com.checkmarx.jenkins.CxScanCallable@2a8aedd3 at hudson.remoting.Channel.call(Channel.java:965) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at com.checkmarx.jenkins.CxScanBuilder.perform(CxScanBuilder.java:711) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)``` Add Comment
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Sai Kiran Challa commented on JENKINS-57796 Re: Checkmarx affected by JEP-200 That worked for me. Thank you very much for fixing it. We had a successful build for the first time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199746.1559317468000.2428.1564337820292%40Atlassian.JIRA.
[JIRA] (JENKINS-58696) Github Branch Source plugin thottle broken by unexpected rate limit headers
Title: Message Title Artem V. Navrotskiy created an issue Jenkins / JENKINS-58696 Github Branch Source plugin thottle broken by unexpected rate limit headers Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-07-28 20:03 Environment: Repositories on github.com Priority: Minor Reporter: Artem V. Navrotskiy We got some messages like: GitHub API Usage: Current quota has 3900 remaining (78 over budget). Next quota of 5000 in 59 min. Sleeping for 1 min 39 sec After investigation we found, that GitHub rate limit remaining and resetDate sometimes increase (out log part: https://gist.github.com/bozaro/1b64f3eb617af97b5f4c822cac870212). I could not figure out how to implement the correct throttling. We disable trottling (https://github.com/jenkinsci/github-branch-source-plugin/pull/237) and minimal remaining value for 14 days is 2986). So without throttling we never exceeds rate limit. Add Comment
[JIRA] (JENKINS-58159) 0 warnings found when parsing from file using IAR parser
Title: Message Title Ulli Hafner reopened an issue Jenkins / JENKINS-58159 0 warnings found when parsing from file using IAR parser Change By: Ulli Hafner Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200209.1561366965000.2440.1564352820265%40Atlassian.JIRA.
[JIRA] (JENKINS-58159) Wrong number of warnings on Windows
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-58159 Wrong number of warnings on Windows Change By: Ulli Hafner Summary: 0 Wrong number of warnings found when parsing from file using IAR parser on Windows Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200209.1561366965000.2442.1564352820292%40Atlassian.JIRA.
[JIRA] (JENKINS-58159) Wrong number of warnings on Windows
Title: Message Title Ulli Hafner commented on JENKINS-58159 Re: Wrong number of warnings on Windows I reopen the issue, since my test seems to work on Unix but not on Windows. The parser finds warnings on Windows when using UTF_16LE, however the number is not the same as the expected one (on Unix), see https://ci.jenkins.io/job/Plugins/job/analysis-model/job/master/666/ Did you also notify that behavior? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200209.1561366965000.2444.1564352940123%40Atlassian.JIRA.
[JIRA] (JENKINS-30129) 'Build Parameters' column displays uresolved environment variable
Title: Message Title Fred G closed an issue as Won't Fix Jenkins / JENKINS-30129 'Build Parameters' column displays uresolved environment variable Change By: Fred G Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164710.1440516437000.2448.1564355100479%40Atlassian.JIRA.
[JIRA] (JENKINS-30129) 'Build Parameters' column displays uresolved environment variable
Title: Message Title
Fred G resolved as Won't Fix
Sorry for the late reply (almost 4 years later *cough*). I agree, that it would be nice to see the "resolved build parameter value"in the "Build parameters" column. As you can see here: https://github.com/jenkinsci/extra-columns-plugin/blob/master/src/main/java/jenkins/plugins/extracolumns/BuildParametersColumn.java#L62-L79 the implementation reads the Parameters from the ParameterAction(s). So the "Build parameters" column shows exactly what you see on the Parameters page of a build, e.g. http:///job///parameters/. In your case, the build's parameter page also shows "${APPLICATION_DEPLOY_VERSION}", since the expansion happens during the build. Currently, I don't see a simple way to get the expanded parameter during the build and cache it. If you or someone else wants to take a stab at it, I'd happily review a pull-request, though. In the meantime, I will close this issue with WON'T FIX.
Jenkins / JENKINS-30129
'Build Parameters' column displays uresolved environment variable
Change By:
Fred G
Status:
Open Resolved
Resolution:
Won't Fix
Add Comment
This mes
[JIRA] (JENKINS-57323) "Last Console" button does not work for jobs inside a folder
Title: Message Title
Fred G commented on JENKINS-57323
Re: "Last Console" button does not work for jobs inside a folder
I've tried to reproduce this issue with Jenkins v.2.138.4 and Folders plugin 6.9.
I've created a folder and a job ("folder_job") in it. I ran the job once to get a "last console" button.
On the main dashboard I can only see the "folder_job" if I enable the "Recurse in subfolders" option under Edit View => Job Filters.
The "last console" button works as expected.
In the test folder I've also created a new view, in which I enabled the "last console" column.
The "last console" button works as expected.
Since I might have missed something, can you describe in detail how your issue can be reproduced?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199094.1556893779000.2450.1564356480255%40Atlassian.JIRA.
[JIRA] (JENKINS-57323) "Last Console" button does not work for jobs inside a folder
Title: Message Title Fred G started work on JENKINS-57323 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199094.1556893779000.2452.1564356480279%40Atlassian.JIRA.
[JIRA] (JENKINS-57323) "Last Console" button does not work for jobs inside a folder
Title: Message Title Fred G assigned an issue to Micky Meyers Jenkins / JENKINS-57323 "Last Console" button does not work for jobs inside a folder Change By: Fred G Assignee: Fred G Micky Meyers Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199094.1556893779000.2454.1564356480301%40Atlassian.JIRA.
[JIRA] (JENKINS-12728) new column: "Last successful artifacts"?
Title: Message Title Fred G updated JENKINS-12728 Jenkins / JENKINS-12728 new column: "Last successful artifacts"? Change By: Fred G Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143185.1328887243000.2461.1564357080602%40Atlassian.JIRA.
[JIRA] (JENKINS-12728) new column: "Last successful artifacts"?
Title: Message Title Fred G updated JENKINS-12728 I won't have time to work on this in the foreseeable future, but I'd happily review a pull-request. In the meantime I'm closing this issue with WON'T DO. Jenkins / JENKINS-12728 new column: "Last successful artifacts"? Change By: Fred G Status: Reopened Fixed but Unreleased Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143185.1328887243000.2457.1564357080539%40Atlassian.JIRA.
[JIRA] (JENKINS-12728) new column: "Last successful artifacts"?
Title: Message Title Fred G closed an issue as Won't Do Jenkins / JENKINS-12728 new column: "Last successful artifacts"? Change By: Fred G Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143185.1328887243000.2465.1564357140281%40Atlassian.JIRA.
[JIRA] (JENKINS-58697) Jenkins crashed after restarting post downloading and installing plugins
Title: Message Title sheetal saini created an issue Jenkins / JENKINS-58697 Jenkins crashed after restarting post downloading and installing plugins Issue Type: Bug Assignee: Technical Support Components: absint-a3-plugin Created: 2019-07-29 01:30 Environment: Amazon Ubuntu 18.04 instance Jenkins ver. 2.176.2 openjdk version "11.0.3" 2019-04-16 OpenJDK Runtime Environment (build 11.0.3+7-Ubuntu-1ubuntu218.04.1) OpenJDK 64-Bit Server VM (build 11.0.3+7-Ubuntu-1ubuntu218.04.1, mixed mode, sharing) Priority: Minor Reporter: sheetal saini java.lang.IllegalStateException: Expected 1 instance of hudson.model.User$AllUsers but got 0 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451) at hudson.model.User$AllUsers.getInstance(User.java:1080) at hudson.model.User$AllUsers.get(User.java:1098) at hudson.model.User$AllUsers.access$100(User.java:1061) at hudson.model.User.getOrCreateById(User.java:517) at hudson.model.User.getById(User.java:615) at hudson.security.HttpSessionContextIntegrationFilter2.hasInvalidSessionSeed(HttpSessionContextIntegrationFilter2.java:87) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:60) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jett
[JIRA] (JENKINS-30558) Cron based jobs are no longer triggered
Title: Message Title Pavel Roskin commented on JENKINS-30558 Re: Cron based jobs are no longer triggered I see that the socket timeout and the request timeout were introduced in the same PR. Does anybody know a reason why request timeouts are needed in presence of socket timeouts? Running HTTP requests in separate threads adds a lot of complexity. Other plugins doesn't do it. I assume every request should use a limited number of packets sent over the socket, so the socket timeout should put a limit on the request duration. I'm going to move requests back to the main thread unless I hear any objections. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165159.1442780746000.2470.1564366500441%40Atlassian.JIRA.
[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Title: Message Title Raghwendra Sonu commented on JENKINS-58534 Re: Impossible to access promotion's console output (navigation is broken from links and breadcrumbs) I am also facing this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200683.1563381278000.2483.1564370400175%40Atlassian.JIRA.
[JIRA] (JENKINS-58182) azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-58182 azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs Change By: Jie Shen Status: Open Resolved Resolution: Fixed Released As: 1.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200233.1561454364000.2486.1564370640286%40Atlassian.JIRA.
[JIRA] (JENKINS-58546) Implement 'default site' fallback mechanism to simplify configuration
Title: Message Title Rafal Myslek updated JENKINS-58546 Jenkins / JENKINS-58546 Implement 'default site' fallback mechanism to simplify configuration Change By: Rafal Myslek Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200696.1563448823000.2489.1564371600317%40Atlassian.JIRA.
[JIRA] (JENKINS-58655) Improve error handling for 403 Build / Deployment API responses
Title: Message Title Rafal Myslek updated JENKINS-58655 Jenkins / JENKINS-58655 Improve error handling for 403 Build / Deployment API responses Change By: Rafal Myslek Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200935.1564037405000.2487.1564371600245%40Atlassian.JIRA.
[JIRA] (JENKINS-58544) Implement HTTP client retries
Title: Message Title Rafal Myslek updated JENKINS-58544 Jenkins / JENKINS-58544 Implement HTTP client retries Change By: Rafal Myslek Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200694.1563448453000.2493.1564371660554%40Atlassian.JIRA.
[JIRA] (JENKINS-58545) Include Jenkins in builds/deployments payload properties
Title: Message Title Rafal Myslek updated JENKINS-58545 Jenkins / JENKINS-58545 Include Jenkins in builds/deployments payload properties Change By: Rafal Myslek Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200695.1563448611000.2491.1564371660524%40Atlassian.JIRA.
[JIRA] (JENKINS-58544) Implement HTTP client retries
Title: Message Title Rafal Myslek updated JENKINS-58544 Jenkins / JENKINS-58544 Implement HTTP client retries Change By: Rafal Myslek Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200694.1563448453000.2495.1564371660581%40Atlassian.JIRA.
[JIRA] (JENKINS-58698) Perforce sync fails for symlinks
Title: Message Title Rohit Goel created an issue Jenkins / JENKINS-58698 Perforce sync fails for symlinks Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-07-29 05:26 Environment: Jenkins 2.176.2 Java 1.8 P4 Plugin 1.10.3 Priority: Blocker Reporter: Rohit Goel We are facing problems syncing workspace on Windows for files that are symlinks. The workspace is on a Unix machine accessed through a mapped drive on Windows. Jenkins master setup is on Unix with a Windows agent for Windows builds Jul 26, 2019 11:24:02 AM SEVERE org.jenkinsci.plugins.p4.tasks.AbstractTask retryTask P4 Task: attempt: 1 Jul 26, 2019 11:24:05 AM SEVERE org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): symlink file Z:\p4workspace\testws\depot\test.cpp can't be sync'd or created with this client program. Add Comment
[JIRA] (JENKINS-58282) Heath metrics produces serious performance issues
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-58282 Re: Heath metrics produces serious performance issues Could be related and soon addressed by https://issues.jenkins-ci.org/browse/JENKINS-18377 (see also https://issues.jenkins-ci.org/browse/JENKINS-25075). In the meantime, I think that being able to define the default health metrics that are to be used when creating a folder could be a good addition. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200346.156197904.2498.1564378980145%40Atlassian.JIRA.
[JIRA] (JENKINS-58282) Heath metrics produces serious performance issues
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-58282 Re: Heath metrics produces serious performance issues proposed: https://github.com/jenkinsci/cloudbees-folder-plugin/pull/129 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200346.156197904.2501.1564379160139%40Atlassian.JIRA.
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title Jochen A. Fürbacher commented on JENKINS-58419 Re: CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200546.1562746885000.2504.1564379340239%40Atlassian.JIRA.
[JIRA] (JENKINS-50160) Can't add credentials through https
Title: Message Title Piotr Bladek commented on JENKINS-50160 Re: Can't add credentials through https I ran into same problem, Im using jenkins behind apache2 https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache In my case solution was to setup following HTTPS proxy headers properly: RequestHeader set X-Forwarded-Proto "https" RequestHeader set X-Forwarded-Port "443" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189176.1521014862000.2507.1564382820142%40Atlassian.JIRA.
