[JIRA] (JENKINS-60011) mail to user full name not email
Title: Message Title
Hokwang Lee updated an issue
Jenkins / JENKINS-60011
mail to user full name not email
Change By:
Hokwang Lee
Hello. I am using Jenkins LTS version with email-ext and oic-auth plugin and also p4 plugin for VCS. I have keycloak for OpenID auth, and here's oic-auth setting.!image-2019-11-01-12-15-17-783.png!!image 2.png! The keypoint is Full name field.I think user name field is for loginid and full name field is for name.So when I set Full name field to "name".I can see my name at top section of Jenkins. and then, I create a job for polling per change.whenever change committed, this job will run and send email to developer using emailext plugin.I use this pipeline syntax for this.{code:java} post {always { emailext (recipientProviders: [developers()],subject: "test",body: "test" )} }{code}At this point,there was a log like Warning: user Fistname lastn...@company.com has no permission to view job #1091, but sending mail anyway Failed to create e-mail address for Firstname I think emailext plugin use fullname, not email and username field in oic-auth plugin. So I set preferred_username for full name in the upper capture.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60011) mail to user full name not email
Title: Message Title Hokwang Lee updated an issue Jenkins / JENKINS-60011 mail to user full name not email Change By: Hokwang Lee Attachment: image 2.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202831.1572585332000.6630.1572585480218%40Atlassian.JIRA.
[JIRA] (JENKINS-60011) mail to user full name not email
Title: Message Title
Hokwang Lee updated an issue
Jenkins / JENKINS-60011
mail to user full name not email
Change By:
Hokwang Lee
Hello. I am using Jenkins LTS version with email-ext and oic-auth plugin and also p4 plugin for VCS. I have keycloak for OpenID auth, and here's oic-auth setting.!image-2019-11-01-12-15-17-783.png!!image -2019-11-01-14-16-42-027 2 .png! The keypoint is Full name field.I think user name field is for loginid and full name field is for name.So when I set Full name field to "name".I can see my name at top section of Jenkins. and then, I create a job for polling per change.whenever change committed, this job will run and send email to developer using emailext plugin.I use this pipeline syntax for this.{code:java} post {always { emailext (recipientProviders: [developers()],subject: "test",body: "test" )} }{code}At this point,there was a log like Warning: user Fistname lastn...@company.com has no permission to view job #1091, but sending mail anyway Failed to create e-mail address for Firstname I think emailext plugin use fullname, not email and username field in oic-auth plugin.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60011) mail to user full name not email
Title: Message Title
Hokwang Lee updated an issue
Jenkins / JENKINS-60011
mail to user full name not email
Change By:
Hokwang Lee
Hello. I am using Jenkins LTS version with email-ext and oic-auth plugin and also p4 plugin for VCS. I have keycloak for OpenID auth, and here's oic-auth setting.!image-2019-11-01-12-15-17-783.png!!image-2019-11-01-14- 15 16 - 55 42 - 100 027 .png! The keypoint is Full name field.I think user name field is for loginid and full name field is for name.So when I set Full name field to "name".I can see my name at top section of Jenkins. and then, I create a job for polling per change.whenever change committed, this job will run and send email to developer using emailext plugin.I use this pipeline syntax for this.{code:java} post {always { emailext (recipientProviders: [developers()],subject: "test",body: "test" )} }{code}At this point,there was a log like Warning: user Fistname lastn...@company.com has no permission to view job #1091, but sending mail anyway Failed to create e-mail address for Firstname I think emailext plugin use fullname, not email and username field in oic-auth plugin.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60011) mail to user full name not email
Title: Message Title
Hokwang Lee updated an issue
Jenkins / JENKINS-60011
mail to user full name not email
Change By:
Hokwang Lee
Hello. I am using Jenkins LTS version with email-ext and oic-auth plugin and also p4 plugin for VCS. I have keycloak for OpenID auth, and here's oic-auth setting.!image-2019-11-01-12-15-17-783.png!!image-2019-11-01- 12 14 - 17 15 - 21 55 - 563 100 .png! The keypoint is Full name field.I think user name field is for loginid and full name field is for name.So when I set Full name field to "name".I can see my name at top section of Jenkins. and then, I create a job for polling per change.whenever change committed, this job will run and send email to developer using emailext plugin.I use this pipeline syntax for this.{code:java} post {always { emailext (recipientProviders: [developers()],subject: "test",body: "test" )} }{code}At this point,there was a log likeWarning: user Fistname lastn...@company.com has no permission to view job #1091, but sending mail anywayFailed to create e-mail address for Firstname I think emailext plugin use fullname, not email and username field in oic-auth plugin.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60011) mail to user full name not email
Title: Message Title
Hokwang Lee created an issue
Jenkins / JENKINS-60011
mail to user full name not email
Issue Type:
Bug
Assignee:
Alex Earl
Attachments:
image-2019-11-01-12-15-17-783.png
Components:
email-ext-plugin, oic-auth-plugin
Created:
2019-11-01 05:15
Priority:
Major
Reporter:
Hokwang Lee
Hello. I am using Jenkins LTS version with email-ext and oic-auth plugin and also p4 plugin for VCS. I have keycloak for OpenID auth, and here's oic-auth setting. The keypoint is Full name field. I think user name field is for loginid and full name field is for name. So when I set Full name field to "name". I can see my name at top section of Jenkins. and then, I create a job for polling per change. whenever change committed, this job will run and send email to developer using emailext plugin. I use this pipeline syntax for this.
post {
always {
emailext (
recipientProviders: [developers()],
subject: "test",
body: "test"
)
}
}
At this point, there was a log like Warning: user Fistname lastn...@company.com has no permission to view job #1091, but sending mail anyway Failed to create e-mail address for Firstname I think emailext plugin use fullname, not email and username field in oic-auth plugin.
[JIRA] (JENKINS-59481) Automatically label Fedora Linux agents
Title: Message Title Mark Waite updated JENKINS-59481 Jenkins / JENKINS-59481 Automatically label Fedora Linux agents Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202096.1569240781000.6622.1572583980210%40Atlassian.JIRA.
[JIRA] (JENKINS-59481) Automatically label Fedora Linux agents
Title: Message Title Mark Waite updated JENKINS-59481 Jenkins / JENKINS-59481 Automatically label Fedora Linux agents Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202096.1569240781000.6621.1572583980164%40Atlassian.JIRA.
[JIRA] (JENKINS-59481) Automatically label Fedora Linux agents
Title: Message Title Mark Waite updated JENKINS-59481 Jenkins / JENKINS-59481 Automatically label Fedora Linux agents Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202096.1569240781000.6619.1572582960085%40Atlassian.JIRA.
[JIRA] (JENKINS-59481) Automatically label Fedora Linux agents
Title: Message Title Mark Waite started work on JENKINS-59481 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202096.1569240781000.6617.1572582600072%40Atlassian.JIRA.
[JIRA] (JENKINS-59481) Automatically label Fedora Linux agents
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-59481 Automatically label Fedora Linux agents Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202096.1569240781000.6616.1572582540070%40Atlassian.JIRA.
[JIRA] (JENKINS-18834) prune should be before fetch
Title: Message Title Everett Toews commented on JENKINS-18834 Re: prune should be before fetch Can confirm this is still an issue. If the git remote prune was performed before the fetch, this wouldn't be a problem. Following the same steps as packadal, I get this error in the console. OpenShift Build my-project/deploy-my-service-1786 from ssh://g...@bitbucket.example.com:7999/ui/my-service.git Checking out git ssh://g...@bitbucket.example.com:7999/ui/my-service.git into /var/lib/jenkins/jobs/my-project/jobs/my-project-deploy-my-service/workspace@script to read Jenkinsfile using credential my-project-bitbucket-jenkins-user > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@bitbucket.example.com:7999/ui/my-service.git # timeout=10 Fetching upstream changes from ssh://g...@bitbucket.example.com:7999/ui/my-service.git > git --version # timeout=10 using GIT_SSH to set credentials my-project-bitbucket-jenkins-user > git fetch --tags --progress ssh://g...@bitbucket.example.com:7999/ui/my-service.git +refs/heads/*:refs/remotes/origin/* ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from ssh://g...@bitbucket.example.com:7999/ui/my-service.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:894) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@bitbucket.example.com:7999/ui/my-service.git +refs/heads/*:refs/remotes/origin/*" returned status code 1: stdout: stderr: From ssh://bitbucket.example.com:7999/ui/my-service * [new branch] automation/testpi-9 -> origin/automation/testpi-9 error: 'refs/remotes/origin/feature/foo' exists; cannot create 'refs/remotes/origin/feature/foo/bar' ! [new branch] feature/foo/bar -> origin/feature/foo/bar (unable to update local ref) error: some local refs could not be updated; try running 'git remote prune ssh://g...@bitbucket.example.com:7999/ui/my-service.git' to remove any old, conflicting branches at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:892) ... 8 more ERROR: Error fetching remote repo 'origin' ERROR: Maximum checkout retry attempts reached, aborting Finished: FAILURE
[JIRA] (JENKINS-18834) prune should be before fetch
Title: Message Title
Everett Toews edited a comment on JENKINS-18834
Re: prune should be before fetch
Can confirm this is still an issue. If the git remote prune was performed before the fetch, this wouldn't be a problem.Following the same steps as [~packadal], I get this error in the console.{code:java}OpenShift Build my-project/deploy-my-service-1786 from ssh://g...@bitbucket.example.com:7999/ui/my-service.gitChecking out git ssh://g...@bitbucket.example.com:7999/ui/my-service.git into /var/lib/jenkins/jobs/my-project/jobs/my-project-deploy-my-service/workspace@script to read Jenkinsfileusing credential my-project-bitbucket-jenkins-user > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@bitbucket.example.com:7999/ui/my-service.git # timeout=10Fetching upstream changes from ssh://g...@bitbucket.example.com:7999/ui/my-service.git > git --version # timeout=10using GIT_SSH to set credentials my-project-bitbucket-jenkins-user > git fetch --tags --progress ssh://g...@bitbucket.example.com:7999/ui/my-service.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://g...@bitbucket.example.com:7999/ui/my-service.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:894) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@bitbucket.example.com:7999/ui/my-service.git +refs/heads/*:refs/remotes/origin/*" returned status code 1:stdout: stderr: From ssh://bitbucket.example.com:7999/ui/my-service * [new branch] automation/testpi-9 -> origin/automation/testpi-9error: 'refs/remotes/origin/feature/foo' exists; cannot create 'refs/remotes/origin/feature/foo/bar' ! [new branch] feature/foo/bar -> origin/feature/foo/bar (unable to update local ref)error: some local refs could not be updated; try running 'git remote prune ssh://g...@bitbucket.example.com:7999/ui/my-service.git' to remove any old, conflicting branches at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:892) ... 8 moreERROR: Error fetching remote repo 'origin'ERROR: Maximum checkout retry attempts reached, abortingFinished: FAILURE{code}
[JIRA] (JENKINS-59578) Changing server configuration does not update SCM configuration
Title: Message Title Daniel Kjellin commented on JENKINS-59578 Re: Changing server configuration does not update SCM configuration Fixed in 1.0.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202218.1569821377000.6597.1572578280566%40Atlassian.JIRA.
[JIRA] (JENKINS-59578) Changing server configuration does not update SCM configuration
Title: Message Title Daniel Kjellin updated JENKINS-59578 Jenkins / JENKINS-59578 Changing server configuration does not update SCM configuration Change By: Daniel Kjellin Status: Fixed but Unreleased Closed Assignee: Kristy Hughes Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202218.1569821377000.6594.1572578280511%40Atlassian.JIRA.
[JIRA] (JENKINS-60000) Plugin ignores jenkins proxy settings
Title: Message Title Jie Shen commented on JENKINS-6 Re: Plugin ignores jenkins proxy settings This plugin does not support Jenkins proxy for now. It could be mitigated temporarily by using JVM parameters -Dhttps.proxyHost=foo -Dhttps.proxyPort=80 -Dhttp.nonProxyHosts="localhost|127.0.0.1|*.your.domain.com" when start the jenkins server. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202814.1572524567000.6575.1572575460259%40Atlassian.JIRA.
[JIRA] (JENKINS-59578) Changing server configuration does not update SCM configuration
Title: Message Title Daniel Kjellin updated JENKINS-59578 Jenkins / JENKINS-59578 Changing server configuration does not update SCM configuration Change By: Daniel Kjellin Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202218.1569821377000.6577.1572575460300%40Atlassian.JIRA.
[JIRA] (JENKINS-60000) Plugin ignores jenkins proxy settings
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-6 Plugin ignores jenkins proxy settings Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202814.1572524567000.6573.1572575280251%40Atlassian.JIRA.
[JIRA] (JENKINS-60010) GCLogs are collected twice
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60010 GCLogs are collected twice Issue Type: Improvement Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-11-01 00:18 Environment: support-core:2.62 Priority: Minor Reporter: Allan BURDAJEWICZ The GC Logs may be collected twice by the Support Core Plugin if those condition are met The Master Log Recorders is enabled (it is by default) The Garbage Collection Logs is enabled (it is not by default) The -Xloggc points to JENKINS_HOME/ We should avoid this. Add Comment
[JIRA] (JENKINS-60010) GCLogs are collected twice
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60010 GCLogs are collected twice Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202827.1572567497000.6570.1572567540326%40Atlassian.JIRA.
[JIRA] (JENKINS-60009) GCLogs component should be made Java 11 compatible
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60009 GCLogs component should be made Java 11 compatible Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202826.1572566602000.6566.1572566644331%40Atlassian.JIRA.
[JIRA] (JENKINS-60009) GCLogs component should be made Java 11 compatible
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60009 GCLogs component should be made Java 11 compatible Issue Type: Improvement Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-11-01 00:03 Environment: support-core:2.62 Priority: Major Reporter: Allan BURDAJEWICZ The GCLogs looks for the GC Logs based on the deprecated (since java 9) arguments -Xloggc. The component needs to also look for a different pattern: https://blog.gceasy.io/2017/10/17/disruptive-changes-to-gc-logging-in-java-9-what-you-need-to-do/. Add Comment
[JIRA] (JENKINS-59704) NoSuchMethodError occurs when promoting a build using parametrized trigger
Title: Message Title Mark Waite edited a comment on JENKINS-59704 Re: NoSuchMethodError occurs when promoting a build using parametrized trigger [~jdege] I think you'll need to rollback to promoted builds plugin 3.2 or earlier. I would like to know the version you select in your rollback because I intend to release git plugin 4.0 in a few days and it currently has an optional dependency on promoted builds plugin 3.2. If 3.2 does not resolve the issue for you, then that likely means I should force the git plugin 4.0 optional dependency to an older version of promoted builds plugin. [~froque] the commits that you referenced from the git plugin were first delivered in 4.0.0-beta12. They are not in earlier plugin versions, though the optional dependency on promoted builds 3.2 will be in git plugin 4.0.0 when it releases unless I hear from someone that version is not sufficient. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202405.157054141.6529.1572560460630%40Atlassian.JIRA.
[JIRA] (JENKINS-60008) Build fails due to Distribution Group in AppCenter not having Correct Permissions
Title: Message Title
Josh Brozen updated an issue
Jenkins / JENKINS-60008
Build fails due to Distribution Group in AppCenter not having Correct Permissions
Change By:
Josh Brozen
Since App Center has seemingly changed the Distribution Group and permissions model (not for the best and much different than HockeyApp - see issue raised here with App Center team: [https://github.com/microsoft/appcenter/issues/1272]), it is pretty hard to manage the App to Distribution Group relationships within App Center (especially after migration from Hockey App)We have noticed that the Jenkins builds are failing when the App Center plugin is configured with Distribution Groups that are not available/accessible for a specific application (within the App Center permission model).So, for example:!Screen Shot 2019-10-31 at 2.33.51 PM.png|thumbnail!If the "Product" group does have access to that specific app in that specific Organization, the jenkins job will build fine and return a success. However, when you add "Tech-Leads" which does not have access (again, for example), the Jenkins build will report as failed.Except, the job won't actually fail - it will just fail to distribute that build/release to that specific distribution group - we get an error like this in the console output:{code:java}Creating an upload resource.Create upload resource successful.Uploading app to resource.Upload app to resource successful.Committing resource.Committing resource successful.Distributing resource.io.jenkins.plugins.appcenter.AppCenterException: Distributing resource unsuccessful: at io.jenkins.plugins.appcenter.task.internal.DistributeResourceTask.lambda$execute$1(DistributeResourceTask.java:59) at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at retrofit2.CompletableFutureCallAdapterFactory$BodyCallAdapter$2.onResponse(CompletableFutureCallAdapterFactory.java:81) at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:129) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) 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)Caused by: retrofit2.HttpException: HTTP 400 Bad Request ... 7 moreio.jenkins.plugins.appcenter.AppCenterException: Upload to AppCenter failed. at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:56) at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:17) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at
[JIRA] (JENKINS-60008) Build fails due to Distribution Group in AppCenter not having Correct Permissions
Title: Message Title
Josh Brozen updated an issue
Jenkins / JENKINS-60008
Build fails due to Distribution Group in AppCenter not having Correct Permissions
Change By:
Josh Brozen
Since App Center has seemingly changed the Distribution Group and permissions model (not for the best and much different than HockeyApp - see issue raised here with App Center team: [https://github.com/microsoft/appcenter/issues/1272]), it is pretty hard to manage the App to Distribution Group relationships within App Center (especially after migration from Hockey App) We have noticed that the Jenkins builds are failing when the App Center plugin is configured with Distribution Groups that are not available/accessible for a specific application (within the App Center permission model) . So, for example:!Screen Shot 2019-10-31 at 2.33.51 PM.png|thumbnail!If the "Product" group does have access to that specific app in that specific Organization, the jenkins job will build fine and return a success. However, when you add "Tech-Leads" which does not have access (again, for example), the Jenkins build will report as failed. Except, the job won't actually fail - it will just fail to distribute that build/release to that specific distribution group - we get an error like this in the console output:{code:java}Creating an upload resource.Create upload resource successful.Uploading app to resource.Upload app to resource successful.Committing resource.Committing resource successful.Distributing resource.io.jenkins.plugins.appcenter.AppCenterException: Distributing resource unsuccessful: at io.jenkins.plugins.appcenter.task.internal.DistributeResourceTask.lambda$execute$1(DistributeResourceTask.java:59) at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at retrofit2.CompletableFutureCallAdapterFactory$BodyCallAdapter$2.onResponse(CompletableFutureCallAdapterFactory.java:81) at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:129) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) 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)Caused by: retrofit2.HttpException: HTTP 400 Bad Request ... 7 moreio.jenkins.plugins.appcenter.AppCenterException: Upload to AppCenter failed. at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:56) at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:17) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at
[JIRA] (JENKINS-59704) NoSuchMethodError occurs when promoting a build using parametrized trigger
Title: Message Title Mark Waite commented on JENKINS-59704 Re: NoSuchMethodError occurs when promoting a build using parametrized trigger Jeff Dege I think you'll need to rollback to promoted builds plugin 3.2 or earlier. I would like to know the version you select in your rollback because I intend to release git plugin 4.0 in a few days and it currently has an optional dependency on promoted builds plugin 3.2. If 3.2 does not resolve the issue for you, then that likely means I should force the git plugin 4.0 optional dependency to an older version of promoted builds plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202405.157054141.6501.1572558180645%40Atlassian.JIRA.
[JIRA] (JENKINS-60008) Build fails due to Distribution Group in AppCenter not having Correct Permissions
Title: Message Title Josh Brozen created an issue Jenkins / JENKINS-60008 Build fails due to Distribution Group in AppCenter not having Correct Permissions Issue Type: Improvement Assignee: Mez Pahlan Attachments: Screen Shot 2019-10-31 at 2.33.51 PM.png Components: appcenter-plugin Created: 2019-10-31 21:41 Environment: Jenkins Version 2.176.3 App Center Plug-In Version: 0.6.2 Priority: Major Reporter: Josh Brozen Since App Center has seemingly changed the Distribution Group and permissions model (not for the best and much different than HockeyApp - see issue raised here with App Center team: https://github.com/microsoft/appcenter/issues/1272), it is pretty hard to manage the App to Distribution Group relationships within App Center (especially after migration from Hockey App) We have noticed that the Jenkins builds are failing when the App Center plugin is configured with Distribution Groups that are not available/accessible for a specific application. So, for example: If the "Product" group does have access to that specific app in that specific Organization, the jenkins job will build fine and return a success. However, when you add "Tech-Leads" which does not have access (again, for example), the Jenkins build will report as failed. Except, the job won't actually fail - it will just fail to distribute that build/release to that specific distribution group - we get an error like this in the console output:
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite commented on JENKINS-59794 Re: Using a period as the branch name in .gitModules does not work. The special value of '.' depends on command line git 2.10 or later (at least according to the documentation at https://git-scm.com/docs/git-submodule/2.10.2 and at https://git-scm.com/docs/git-submodule/2.9.0 . If this is implemented, it will need to be safeguarded so that it is only used if the CLI git version is new enough to support it. Many popular operating systems do no ship git 2.10 or newer (CentOS 6,. CentOS 7, Ubuntu 16.04) and the plugins generally try to not break those older versions. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202524.1571167644000.6496.1572557940132%40Atlassian.JIRA.
[JIRA] (JENKINS-60007) Timestamper REST API doesn't work since version 1.9
Title: Message Title
T. Houdayer updated an issue
Jenkins / JENKINS-60007
Timestamper REST API doesn't work since version 1.9
Change By:
T. Houdayer
Using the REST API of the timestamper pluging doesn't work since the last update (v1.9)With timestamper v1.8, accessing the job url "https://myjenkins/job/J18.windows/2260/timestamps/" returns the elapsed times, one per line.{noformat}0.0030.0050.0050.0100.1230.1390.1400.1630.2900.5870.5880.5980.5980.5980.5980.5980.5980.5980.5980.5980.5990.5990.6141.179 1.1791.1801.1801.1801.1801.1801.1821.1821.1891.1891.1891.1891.1891.1901.1901.1941.1941.1941.2061.2061.2151.2151.2171.2381.3611.6671.6681.678 [...]{noformat} Since timestamper v1.9, accessing the job url "https://myjenkins2/job/J18.windows/1/timestamps/" returns an empty page ! Is there a possibility that the global option "enable timestamps for all Pipeline builds" introduce in the v1.9 of the plugin had inject this bug ? (this option is off in our instance).We are using the REST API timestamper to analyse the different steps duration of our builds (they have an average time build of ~2h). Using the datetime injected in the log of the builds is not really an option because we are using 4 different Jenkins instance (the older one is Jenkins v1.549 !) and we prefer not to maintain different analyse script when one do the job, and for now the simple timestamper REST API ".../timestamps/" was the only way to get the same result page for those different Jenkins versions.
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-60007) Timestamper REST API doesn't work since version 1.9
Title: Message Title T. Houdayer created an issue Jenkins / JENKINS-60007 Timestamper REST API doesn't work since version 1.9 Issue Type: Bug Assignee: Steven G Brown Components: timestamper-plugin Created: 2019-10-31 21:14 Environment: Debian GNU/Linux 9 (stretch) Jenkins v2.150.3 Plugins: jquery-detached 1.2.1 simple-theme-plugin 0.5.1 all-changes 1.5 ldap 1.20 log-parser 2.0 warnings 5.0.1 jobConfigHistory 2.20 workflow-multibranch 2.21 description-setter 1.10 junit 1.27 next-executions 1.0.12 rebuild 1.30 jackson2-api 2.9.8 preSCMbuildstep 0.3 resource-disposer 0.12 timestamper 1.9 compact-columns 1.10 workflow-api 2.33 structs 1.17 antexec 1.11 promoted-builds 3.2 nunit 0.24 run-condition 1.2 pipeline-rest-api 2.11 plain-credentials 1.5 run-selector 1.0.0 display-url-api 2.3.1 mapdb-api 1.0.9.0 credentials 2.1.18 ssh-slaves 1.29.4 last-changes 2.7.4 chucknorris 1.2 pipeline-graph-analysis 1.9 progress-bar-column-plugin 1.0 icon-shim 2.0.3 batch-task 1.19 saferestart 0.3 hidden-parameter 0.0.4 external-monitor-job 1.7 greenballs 1.15 nodelabelparameter 1.7.2 next-build-number 1.5 label-linked-jobs 5.1.2 git 3.9.3 workflow-aggregator 2.6 BlameSubversion 1.200 publish-over 0.22 build-timestamp 1.0.3 validating-string-parameter 2.4 collapsing-console-sections 1.7.0 jquery 1.12.4-0 pipeline-model-extensions 1.3.8 warnings-ng 4.0.0 parameter-separator 1.0 pipeline-milestone-step 1.3.1 fail-the-build-plugin 1.0 analysis-model-api 4.0.0 git-server 1.7 javadoc 1.5 readonly-parameters 1.0.0 matrix-project 1.14 show-build-parameters 1.0 branch-api 2.4.0 dry 3.0.0 script-security 1.58 scriptler 2.9 workflow-cps 2.67 variant 1.2 authentication-tokens 1.3 ant 1.9 uno-choice 2.1 release 2.10.2 build-timeout 1.19 git-parameter 0.9.10 workflow-job 2.32 publish-over-cifs 0.12 extended-choice-parameter 0.78 workflow-scm-step 2.7 pipeline-model-api 1.3.8 build-monitor-plugin 1.12+build.201809061734 antisamy-markup-formatter 1.5 dependency-queue-plugin 1.1 envinject-api 1.5 credentials-binding 1.18 built-on-column 1.1 scm-api 2.4.1 envinject 2.1.6 matrix-auth 2.3 pipeline-build-step 2.9 workflow-support 3.2 xunit 2.3.3 maven-plugin 3.2 slave-setup 1.10 git-client 2.7.7 apache-httpcomponents-client-4-api 4.5.5-3.0 bouncycastle-api 2.17 lockable-resources 2.5 python 1.3 active-directory 2.13 cloudbees-folder 6.8 conditional-buildstep 1.3.6 workflow-basic-steps 2.15 pipeline-stage-view 2.11 dynamicparameter 0.2.0 jdk-tool 1.2 msbuild 1.29 mailer 1.23 build-flow-plugin 0.20 any-buildstep 0.1 PrioritySorter 3.6.0
[JIRA] (JENKINS-41388) Any change to Jenkins system config via UI incorrectly sets the namespace for the kubernetes-plugin
Title: Message Title
Jukka Lehtniemi edited a comment on JENKINS-41388
Re: Any change to Jenkins system config via UI incorrectly sets the namespace for the kubernetes-plugin
I can reproduce this or very similar problem with Jenkins 2.176.3, Kubernetes plugin 1.19.2We configure the Kubernetes using JCasC and it generates {{config.xml}} without Kubernetes {{}} element. However after making any change to the global configuration using the Jenkins web UI the empty elements {{, and }} will appear in the {{config.xml}}. After this, Jenkins fails to launch Kubernetes slaves with following exception trace: { { code} INFO: Created Pod: default/my-jnlp-f0n0n }} {{ Oct 31, 2019 8:17:36 PM hudson.slaves.NodeProvisioner$2 run }} {{ INFO: Kubernetes Pod Template provisioning successfully completed. We have now 3 computer(s) }} {{ Oct 31, 2019 8:17:36 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch }} {{ WARNING: Error in provisioning; agent=KubernetesSlave name: my-jnlp-f0n0n, template=PodTemplate{inheritFrom='', name='my-jnlp', namesp }} {{ ace='', label='my-jnlp', nodeSelector='', nodeUsageMode=EXCLUSIVE, workspaceVolume=org.csanchez.jenkins.plugins.kubernetes.volumes.works }} {{ pace.DynamicPVCWorkspaceVolume@2d963013} }} {{ io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://10.96.0.1/api/v1/namespaces/default/persistentvo }} {{ lumeclaims. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. persistentvolumeclaims }} {{ is forbidden: User "system:serviceaccount:default:jenkins-master" cannot create resource "persistentvolumeclaims" in API group "" in the na }} {{ mespace "default". }} {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510) }} {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:447) }} {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:413) }} {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:372) }} {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:241) }} {{ at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:813) }} {{ at io.fabric8.kubernetes.client.dsl.base.BaseOperation.create(BaseOperation.java:328) }} {{ at io.fabric8.kubernetes.client.dsl.base.BaseOperation.create(BaseOperation.java:324) }} {{ at org.csanchez.jenkins.plugins.kubernetes.volumes.workspace.DynamicPVCWorkspaceVolume.createVolume(DynamicPVCWorkspaceVolume.java:9 }} {{ 4) }} {{ at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:130) }} {{ at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) }} {{ at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) }} {{ at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) }} {{ 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} Thus, it seems to me that the namespace='' is not equal to not having a namespace element at all in the config.xml
[JIRA] (JENKINS-41388) Any change to Jenkins system config via UI incorrectly sets the namespace for the kubernetes-plugin
Title: Message Title
Jukka Lehtniemi reopened an issue
I can reproduce this or very similar problem with Jenkins 2.176.3, Kubernetes plugin 1.19.2 We configure the Kubernetes using JCasC and it generates config.xml without Kubernetes element. However after making any change to the global configuration using the Jenkins web UI the empty elements , and will appear in the config.xml. After this, Jenkins fails to launch Kubernetes slaves with following exception trace: INFO: Created Pod: default/my-jnlp-f0n0n Oct 31, 2019 8:17:36 PM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 3 computer(s) Oct 31, 2019 8:17:36 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch WARNING: Error in provisioning; agent=KubernetesSlave name: my-jnlp-f0n0n, template=PodTemplate{inheritFrom='', name='my-jnlp', namesp ace='', label='my-jnlp', nodeSelector='', nodeUsageMode=EXCLUSIVE, workspaceVolume=org.csanchez.jenkins.plugins.kubernetes.volumes.works pace.DynamicPVCWorkspaceVolume@2d963013} io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://10.96.0.1/api/v1/namespaces/default/persistentvo lumeclaims. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. persistentvolumeclaims {{ is forbidden: User "system:serviceaccount:default:jenkins-master" cannot create resource "persistentvolumeclaims" in API group "" in the na}} mespace "default". {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510)}} {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:447)}} {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:413)}} {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:372)}} {{ at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:241)}} {{ at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:813)}} {{ at io.fabric8.kubernetes.client.dsl.base.BaseOperation.create(BaseOperation.java:328)}} {{ at io.fabric8.kubernetes.client.dsl.base.BaseOperation.create(BaseOperation.java:324)}} {{ at org.csanchez.jenkins.plugins.kubernetes.volumes.workspace.DynamicPVCWorkspaceVolume.createVolume(DynamicPVCWorkspaceVolume.java:9}} 4) {{ at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:130)}} {{ at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294)}} {{ at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)}} {{ at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)}} {{ 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)}} Thus, it seems to me that the namespace='' is not equal to not having a namespace element at all in the config.xml
Jenkins / JENKINS-41388
Any change to Jenkins system config via UI incorrectly sets the namespace for the kubernetes-plugin
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Dicom J commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Thanks, Devin Nusbaum, for very good news, I've been waiting a while for this cut... Thanks a lot all of you, participated in getting it done! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200534.1562691597000.6473.1572554640425%40Atlassian.JIRA.
[JIRA] (JENKINS-42471) "try sample Pipeline...” predates Declarative
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-42471 "try sample Pipeline...” predates Declarative Change By: Devin Nusbaum Released As: workflow-cps 2.75 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179383.148855816.6469.1572554461026%40Atlassian.JIRA.
[JIRA] (JENKINS-59425) When specifying an invalid script path the build fails with an hard-to-read exception
Title: Message Title Devin Nusbaum updated JENKINS-59425 A fix for this issue was just released in Pipeline: Groovy Plugin version 2.75. Jenkins / JENKINS-59425 When specifying an invalid script path the build fails with an hard-to-read exception Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-cps 2.75 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58620) expected to call CpsGroovyShell.evaluate but wound up catching .run
Title: Message Title Devin Nusbaum resolved as Fixed A fix for this issue was just released in Pipeline: Groovy Plugin version 2.75. Jenkins / JENKINS-58620 expected to call CpsGroovyShell.evaluate but wound up catching .run Change By: Devin Nusbaum Status: Open Resolved Resolution: Fixed Released As: workflow-cps 2.75 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod
Title: Message Title Devin Nusbaum resolved as Fixed A fix for this issue was just released in Pipeline: Groovy Plugin version 2.75. Jenkins / JENKINS-58643 CPS Mismatches on cpsScript.InvokeMethod Change By: Devin Nusbaum Status: Open Resolved Resolution: Fixed Released As: workflow-cps 2.75 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Devin Nusbaum updated JENKINS-58407 A fix for this issue was just released in Pipeline: Groovy Plugin version 2.75. Jenkins / JENKINS-58407 Fail to call a Closure stored as a class attribute/field Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-cps 2.75 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56183) Attempt to (de-)serialize anonymous class: jenkins-core-2.150.3.jar
Title: Message Title leemeador commented on JENKINS-56183 Re: Attempt to (de-)serialize anonymous class: jenkins-core-2.150.3.jar We are on 2.164 and getting a similar message in the build agent log /computer//log Agent successfully connected and online Oct 31, 2019 9:57:07 AM [ssh] Connection established in 2.247 seconds. Oct 31, 2019 10:08:07 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.FilePath$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Oct 31, 2019 10:13:39 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Oct 31, 2019 10:13:40 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Oct 31, 2019 10:14:57 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this
[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`
Title: Message Title Mez Pahlan commented on JENKINS-58699 Re: AppCenter Plugin is unable to read parameters set to `Path To App` Hi Arun Ghanta what you're looking for is not environment variable substitution which was what was resolved in the issue that this duplicates but rather supporting ANT style glob paths. There's a fix in JENKINS-59528 that you can look out for. It isn't released yet but will be shortly. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200988.1564386205000.6428.1572550440212%40Atlassian.JIRA.
[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`
Title: Message Title
Arun Ghanta edited a comment on JENKINS-58699
Re: AppCenter Plugin is unable to read parameters set to `Path To App`
Hi Mez! Thank you very much for the AppCenter Jenkins plugin.Just like Alexey the project that I'm working on generates dynamic file names. I tried below methods to publish to AppCenter and I'm getting error.*+Method 1: [Declare a variable and and call it in the path]+* {code:java} stage('Publish to App Center') sh ''' filename=$(ls -lt somepath/*.apk |cut -d'/' -f 7) echo $filename > filename ''' apkname = readFile 'filename' appCenter apiToken: 'sometoken', appName: 'some-appname', distributionGroups: 'some-group', notifyTesters: true, ownerName: 'some-owner-name', pathToApp: ' * somepath/${apkname} * ', releaseNotes: 'notes' {code} *+Method 2: [Using shell type wild card in the path]+* {code:java} stage('Publish to App Center') appCenter apiToken: 'sometoken', appName: 'some-appname', distributionGroups: 'some-group', notifyTesters: true, ownerName: 'some-owner-name', pathToApp: ' * some/*/path/*.apk * ', releaseNotes: 'notes' {code} I get below error for both:*Caused by: java.util.concurrent.ExecutionException: io.jenkins.plugins.appcenter.AppCenterException: File not found:* Please suggest any way to come around this one.Regards,Arun
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`
Title: Message Title
Arun Ghanta edited a comment on JENKINS-58699
Re: AppCenter Plugin is unable to read parameters set to `Path To App`
Hi Mez! Thank you very much for the AppCenter Jenkins plugin.Just like Alexey the project that I'm working on generates dynamic file names.I tried below methods to publish to AppCenter and I'm getting error.*+Method 1: [Declare a variable and and call it in the path]+*stage('Publish to App Center')sh '''filename=$(ls -lt somepath/*.apk |cut -d'/' -f 7)echo $filename > filename'''apkname = readFile 'filename'appCenter apiToken: 'sometoken', appName: 'some-appname', distributionGroups: 'some-group', notifyTesters: true, ownerName: 'some-owner-name', pathToApp: '*somepath/${apkname}*', releaseNotes: 'notes' *+Method 2: [Using shell type wild card in the path]+*stage('Publish to App Center')appCenter apiToken: 'sometoken', appName: 'some-appname', distributionGroups: 'some-group', notifyTesters: true, ownerName: 'some-owner-name', pathToApp: '*some/*/path/*.apk*', releaseNotes: 'notes'I get below error for both:*Caused by: java.util.concurrent.ExecutionException: io.jenkins.plugins.appcenter.AppCenterException: File not found:* Please suggest any way to come around this one. Regards,Arun
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`
Title: Message Title
Arun Ghanta commented on JENKINS-58699
Re: AppCenter Plugin is unable to read parameters set to `Path To App`
Hi Mez! Thank you very much for the AppCenter Jenkins plugin. Just like Alexey the project that I'm working on generates dynamic file names. I tried below methods to publish to AppCenter and I'm getting error. Method 1: [Declare a variable and and call it in the path] stage('Publish to App Center') sh ''' filename=$(ls -lt somepath/*.apk |cut -d'/' -f 7) echo $filename > filename ''' apkname = readFile 'filename' appCenter apiToken: 'sometoken', appName: 'some-appname', distributionGroups: 'some-group', notifyTesters: true, ownerName: 'some-owner-name', pathToApp: 'somepath/${apkname}', releaseNotes: 'notes' Method 2: [Using shell type wild card in the path] stage('Publish to App Center') appCenter apiToken: 'sometoken', appName: 'some-appname', distributionGroups: 'some-group', notifyTesters: true, ownerName: 'some-owner-name', pathToApp: 'some//path/.apk', releaseNotes: 'notes' I get below error for both: Caused by: java.util.concurrent.ExecutionException: io.jenkins.plugins.appcenter.AppCenterException: File not found: Please suggest any way to come around this one. Regards, Arun
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-60006) Cannot delete orphaned items in Multibranch pipeline
Title: Message Title
Shavkat Aynurin updated an issue
Jenkins / JENKINS-60006
Cannot delete orphaned items in Multibranch pipeline
Change By:
Shavkat Aynurin
I believe this is similar to JENKINS-58733 and JENKINS-58998 but it reproduces in 2.190.The issue I'm facing is that Multibranch Scan cannot delete orphaned projects. When I try to delete them using Jenkins UI I get the same error. Deletion is blocked by a stash being ostensibly used by someone.I don't have the necessary access to Jenkins to find who is using the file. I'm working on figuring that out.Here is the Scan log output (the error from the UI matches):{noformat}Will remove PR-1837FATAL: Failed to recompute children of AppSoft_CIjenkins.util.io.CompositeIOException: Unable to delete '/var/jenkins_home/jobs/AppSoft_CI/branches/PR-1783'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:99) at hudson.Util.deleteRecursive(Util.java:293) at hudson.Util.deleteRecursive(Util.java:282) at hudson.model.AbstractItem.performDelete(AbstractItem.java:801) at org.jenkinsci.plugins.workflow.job.WorkflowJob.performDelete(WorkflowJob.java:650) at hudson.model.AbstractItem.delete(AbstractItem.java:785) at hudson.model.Job.delete(Job.java:676) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:290) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1026) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)jenkins.util.io.CompositeIOException: Unable to remove file /var/jenkins_home/jobs/AppSoft_CI/branches/PR-1783/builds/3/stashes/.nfs95fe10b120ec at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:252) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96) at hudson.Util.deleteRecursive(Util.java:293) ...{noformat}See the attached file for the full stack trace. I marked this as Critical as it eventually will fill the disk space and block any other builds from running.
[JIRA] (JENKINS-60006) Cannot delete orphaned items in Multibranch pipeline
Title: Message Title Shavkat Aynurin created an issue Jenkins / JENKINS-60006 Cannot delete orphaned items in Multibranch pipeline Issue Type: Bug Assignee: Igal Gluh Attachments: delete-error-stack-trace.txt Components: core, multibranch-scan-webhook-trigger-plugin Created: 2019-10-31 19:16 Environment: Debian GNU/Linux 9 (stretch); Jenkins ver. 2.190.1; Multibranch 2.5.7; Priority: Critical Reporter: Shavkat Aynurin I believe this is similar to JENKINS-58733 and JENKINS-58998 but it reproduces in 2.190. The issue I'm facing is that Multibranch Scan cannot delete orphaned projects. When I try to delete them using Jenkins UI I get the same error. Deletion is blocked by a stash being ostensibly used by someone. I don't have the necessary access to Jenkins to find who is using the file. I'm working on figuring that out. Here is the Scan log output (the error from the UI matches): Will remove PR-1837 FATAL: Failed to recompute children of AppSoft_CI jenkins.util.io.CompositeIOException: Unable to delete '/var/jenkins_home/jobs/AppSoft_CI/branches/PR-1783'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:99) at hudson.Util.deleteRecursive(Util.java:293) at hudson.Util.deleteRecursive(Util.java:282) at hudson.model.AbstractItem.performDelete(AbstractItem.java:801) at
[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`
Title: Message Title Mez Pahlan closed an issue as Duplicate Jenkins / JENKINS-58699 AppCenter Plugin is unable to read parameters set to `Path To App` Change By: Mez Pahlan Status: Reopened Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200988.1564386205000.6411.1572549240265%40Atlassian.JIRA.
[JIRA] (JENKINS-59817) Swarm client hangs indefinitely while waiting for HTTP handshake to complete
Title: Message Title Basil Crow commented on JENKINS-59817 Re: Swarm client hangs indefinitely while waiting for HTTP handshake to complete I like the suggestion for an HTTP timeout. If this problem occurs again, could you get a thread dump from the Jenkins master and the Swarm client agent at the time of the hang? I would like to see the stack trace on each side of the connection. This should help pinpoint the cause of the hang. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202549.1571297034000.6409.1572549060110%40Atlassian.JIRA.
[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`
Title: Message Title Arun Ghanta updated JENKINS-58699 Jenkins / JENKINS-58699 AppCenter Plugin is unable to read parameters set to `Path To App` Change By: Arun Ghanta Resolution: Duplicate Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200988.1564386205000.6406.1572549000282%40Atlassian.JIRA.
[JIRA] (JENKINS-59978) Need ability to score Swarm nodes based on connectivity and user interaction
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-59978 Need ability to score Swarm nodes based on connectivity and user interaction Change By: Basil Crow Assignee: Basil Crow Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202782.1572375567000.6404.1572548940129%40Atlassian.JIRA.
[JIRA] (JENKINS-59073) Random InterruptedException in pipeline builds
Title: Message Title Basil Crow commented on JENKINS-59073 Re: Random InterruptedException in pipeline builds I happened to come across this bug while triaging the Swarm component. Unclear what the cause of your problem is so far. It might be related to Swarm, or it might be related to durable-task or Remoting. It would be helpful to know what versions of the Swarm plugin, Swarm client, durable-task, and workflow-durable-task you are running. From these we would be able to tell what version of Remoting you are using on each side of the connection. If these plugins aren't already up-to-date, try updating them first. The proximate cause of your problem given the above stack trace is hudson.remoting.Request.call(Request.java:177): while(response==null && !channel.isInClosed()) // I don't know exactly when this can happen, as pendingCalls are cleaned up by Channel, // but in production I've observed that in rare occasion it can block forever, even after a channel // is gone. So be defensive against that. wait(30*1000); <--- cause of interruption Here the Jenkins master is timing out after waiting for 30 seconds for some type of response from the agent over Remoting. It then throws an InterruptedException which causes the job to fail. You should try to look into the other side of the connection (the agent side) to see why it stopped responding to the master. Try turning up the logging as high as possible on the Swarm client side and see if anything suspicious is present there. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58095) Add support for configurable "Restrict jobs execution at node" and "Environment variables" equivalent of generic nodes
Title: Message Title Basil Crow commented on JENKINS-58095 Re: Add support for configurable "Restrict jobs execution at node" and "Environment variables" equivalent of generic nodes One such item is ability to pass Environment variables (and/alternately to Prepare jobs environment, from EnvInject plugin) as part of the swarm client's configuration Can you take a look at jenkinsci/swarm-plugin#80 and see if this doesn't address your use case here? The other problem is harder to work around: restriction of jobs executions, at least the option to filter by regex of the job name(s). […] filtering by full-jobname regex supported this use-case well When you say "supported" in the past tense, do you mean that you had job name regular _expression_ filtering working already with a static (non-Swarm) agent? I am trying to determine if this problem is unique to Swarm or would apply to any Jenkins agent. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou resolved as Fixed Jenkins / JENKINS-59903 durable-task v1.31 breaks sh steps in pipeline when running in a Docker container Change By: Carroll Chiou Status: In Progress Resolved Resolution: Fixed Released As: 1.33 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.6351.1572546363447%40Atlassian.JIRA.
[JIRA] (JENKINS-59838) durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/
Title: Message Title Carroll Chiou closed an issue as Incomplete Jenkins / JENKINS-59838 durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/ Change By: Carroll Chiou Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202573.1571383245000.6348.1572546300241%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou updated JENKINS-59907 Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Carroll Chiou Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6333.1572546242884%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou updated JENKINS-59907 Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Carroll Chiou Status: Fixed but Unreleased Resolved Released As: 1.33 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6335.1572546242907%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou reopened an issue Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Carroll Chiou Resolution: Incomplete Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6320.1572546242716%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou closed an issue as Incomplete Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Carroll Chiou Status: In Progress Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6296.1572546181173%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Jakub L commented on JENKINS-59907 Re: sh steps stuck indefinitely on uncommon architectures (e.g. s390x) I can confirm that v1.33 works fine on s390x. Thanks for the fix! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6282.1572545880500%40Atlassian.JIRA.
[JIRA] (JENKINS-59838) durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/
Title: Message Title Carroll Chiou commented on JENKINS-59838 Re: durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/ So you can pass in that system property multiple ways. I would recommend passing it in the JVM startup args for however you run Jenkins, or at the script console found in the manage jenkins setting. The JVM startup is where I would recommend you do it. Once that is done, I can't say to where your logs would be, because that would depend on your system and how you installed Jenkins. As for 1.33, i'm not sure why it wouldn't appear in the update center. I know you mentioned that you have issues in 1.30, but if you don't see 1.33, i would recommend downgrading to 1.30. in the plugin manager UI. Could you open a mailing list thread on the jenkinsci-users mailing list for this question? You should add the output once you enable LAUNCH_DIAGNOSTICS, and some details about whether this was working for you previously (i.e. what version of Jenkins you are running, what OS you are using on the Jenkins master and the agent being used by the shell step, etc.). The bug tracker is not the right place for general investigation of issues like this. I am going to close this issue for now, if it looks like there is a bug after you provide more info on the mailing list, we’ll reopen the ticket Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-60004) Can't generate job using DSL with projectName + projectVersion
Title: Message Title Jordan Koehn commented on JENKINS-60004 Re: Can't generate job using DSL with projectName + projectVersion I believe it's different because this is for generating a job config based off dsl code, while the other ticket is for using it in a pipeline. I can't confirm, but using it in a pipeline might work now since dependency track's 3.6 release added support for addressing a project by name/version or UUID, which you mentioned in that ticket. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202820.1572538748000.6277.1572541860143%40Atlassian.JIRA.
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Joshua Booth updated an issue Jenkins / JENKINS-55785 Incorporate clang static analysis HTML output into presentation Change By: Joshua Booth Attachment: scan-build-plist.zip Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197174.1548446754000.6269.1572540240681%40Atlassian.JIRA.
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Joshua Booth updated an issue Jenkins / JENKINS-55785 Incorporate clang static analysis HTML output into presentation Change By: Joshua Booth Attachment: scan-build-html.zip Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197174.1548446754000.6263.1572540240597%40Atlassian.JIRA.
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Joshua Booth updated an issue Jenkins / JENKINS-55785 Incorporate clang static analysis HTML output into presentation Change By: Joshua Booth Attachment: scan-build-plist.zip Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197174.1548446754000.6245.1572540061259%40Atlassian.JIRA.
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Joshua Booth edited a comment on JENKINS-55785 Re: Incorporate clang static analysis HTML output into presentation Here are the two output types that scan-build can output. plist and htmlIt appears plist is an XML format so is likely to be the preferable option. Unfortunately it appears to make a lot of files for a single pass Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197174.1548446754000.6233.1572540061114%40Atlassian.JIRA.
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Joshua Booth updated an issue Jenkins / JENKINS-55785 Incorporate clang static analysis HTML output into presentation Change By: Joshua Booth Attachment: scan-build-plist.zip Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197174.1548446754000.6239.1572540061187%40Atlassian.JIRA.
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Joshua Booth updated an issue Jenkins / JENKINS-55785 Incorporate clang static analysis HTML output into presentation Change By: Joshua Booth Attachment: scan-build-plist.zip Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197174.1548446754000.6251.1572540061325%40Atlassian.JIRA.
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Joshua Booth edited a comment on JENKINS-55785 Re: Incorporate clang static analysis HTML output into presentation Here are I have attached the two output types that scan-build can output. plist and htmlIt appears plist is an XML format so is likely to be the preferable option. Unfortunately it appears to make a lot of files for a single pass Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197174.1548446754000.6253.1572540061346%40Atlassian.JIRA.
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Joshua Booth commented on JENKINS-55785 Re: Incorporate clang static analysis HTML output into presentation Here are the two output types that scan-build can output. plist and html It appears plist is an XML format so is likely to be the preferable option. Unfortunately it appears to make a lot of files for a single pass Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197174.1548446754000.6223.157254179%40Atlassian.JIRA.
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Joshua Booth updated an issue Jenkins / JENKINS-55785 Incorporate clang static analysis HTML output into presentation Change By: Joshua Booth Attachment: scan-build-html.zip Attachment: scan-build-plist.zip Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197174.1548446754000.6217.1572539820451%40Atlassian.JIRA.
[JIRA] (JENKINS-54540) Pods stuck in error state is not cleaned up
Title: Message Title Michael Odell commented on JENKINS-54540 Re: Pods stuck in error state is not cleaned up We also saw the problem when podRetention was set to OnError (including the pods that were in Running and not Error) and switched to Never to try to get it to go away. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195312.1541679013000.6212.1572539760184%40Atlassian.JIRA.
[JIRA] (JENKINS-54540) Pods stuck in error state is not cleaned up
Title: Message Title Michael Odell commented on JENKINS-54540 Re: Pods stuck in error state is not cleaned up I see the same thing. We have podRetention set to never, but out of the probably hundreds of jobs we run per day, a handful of the pods stick around in an error state or in "Running" where only a subset of the containers are running (i.e. READY: 3/4 STATUS: Running). FWIW, our jobs don't reuse pods. I suppose if they did we might ( ? ) see this less often. Cleanup is not terribly onerous except that it has to be done every day. I have a hard time seeing how this can be classified as an enhancement rather than a bug. Given long enough, this will cause the system to stop working because of resource exhaustion. We happen to be on kubernetes 1.12.10, plugin version 1.18.3, and Jenkins version 2.176.3, but we also seen this with slightly older versions of all three, and I believe in testing with newer versions of Jenkins and plugin (but we're not running enough jobs on those newer versions to see it reliably). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195312.1541679013000.6202.1572539520189%40Atlassian.JIRA.
[JIRA] (JENKINS-60004) Can't generate job using DSL with projectName + projectVersion
Title: Message Title Steve Springett commented on JENKINS-60004 Re: Can't generate job using DSL with projectName + projectVersion This appears to be a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-57643 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202820.1572538748000.6200.1572539040194%40Atlassian.JIRA.
[JIRA] (JENKINS-60005) Use WinSW .NET 4 version for auto-upgrade instead of .NET 2
Title: Message Title Nick Jones assigned an issue to Unassigned Jenkins / JENKINS-60005 Use WinSW .NET 4 version for auto-upgrade instead of .NET 2 Change By: Nick Jones Assignee: Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202821.1572538822000.6198.1572538920123%40Atlassian.JIRA.
[JIRA] (JENKINS-60005) Use WinSW .NET 4 version for auto-upgrade instead of .NET 2
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-60005 Use WinSW .NET 4 version for auto-upgrade instead of .NET 2 Issue Type: Improvement Assignee: Jeff Thompson Components: remoting Created: 2019-10-31 16:20 Environment: Jenkins 2.190.2 LTS on Windows Server (master and agents) Priority: Minor Reporter: Nick Jones I recently updated some older agent nodes to use the latest WinSW release (2.2.0, at present) and thought I'd switch to the WinSW.NET4.exe version, as it does not require the additional jenkins-slave.exe.config file specifying this particular runtime (vs. the default of .NET 2). The agent service installed and started fine, but the Jenkins master then attempted to auto-upgrade the jenkins-slave.exe on the agent, as shown by the "Scheduled overwrite of jenkins-slave.exe on the next service startup" message in the agent log (from https://github.com/jenkinsci/windows-slave-installer-module/blob/master/src/main/java/org/jenkinsci/modules/windows_slave_installer/SlaveExeUpdater.java#L99). Sure enough, the .NET 4 version of jenkins-slave.exe I'd put onto my agents got replaced with a .NET 2 version from the Jenkins master, and then the agent service wouldn't start because I lacked a jenkins-slave.exe.config file there. I realize that the auto-update can be disabled via the org.jenkinsci.modules.windows_slave_installer.disableAutoUpdate setting on the master, but could we have the Jenkins master use the .NET 4 version of WinSW instead, so this isn't necessary?
[JIRA] (JENKINS-60005) Use WinSW .NET 4 version for auto-upgrade instead of .NET 2
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-60005 Use WinSW .NET 4 version for auto-upgrade instead of .NET 2 Change By: Nick Jones Component/s: windows-slave-installer-module Component/s: remoting Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202821.1572538822000.6196.1572538860846%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating
Title: Message Title Liam Newman reopened an issue Jenkins / JENKINS-59321 github-branch-source plugin throws InvocationTargetException when creating Change By: Liam Newman Resolution: Fixed Status: Resolved Reopened Assignee: Rick Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.6189.1572538800632%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating
Title: Message Title Liam Newman commented on JENKINS-59321 Re: github-branch-source plugin throws InvocationTargetException when creating This is not fixed yet. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.6192.1572538860598%40Atlassian.JIRA.
[JIRA] (JENKINS-60004) Can't generate job using DSL using projectName + projectVersion
Title: Message Title Jordan Koehn created an issue Jenkins / JENKINS-60004 Can't generate job using DSL using projectName + projectVersion Issue Type: Bug Assignee: Steve Springett Components: dependency-track-plugin Created: 2019-10-31 16:19 Priority: Minor Reporter: Jordan Koehn When using a job dsl script to generate jenkins jobs, dependency-track can be assigned a project with the UUID. It's more convenient for a large subset of projects to use the name+version. However when using these variables no project is assigned in the generated job. Then when running the job the following error is given [DependencyTrack] Either the projectId or the projectName and projectVersion have to be specified tested with dependency track 3.6.1, dependency track plugin 2.1.0 Add Comment
[JIRA] (JENKINS-60004) Can't generate job using DSL with projectName + projectVersion
Title: Message Title Jordan Koehn updated an issue Jenkins / JENKINS-60004 Can't generate job using DSL with projectName + projectVersion Change By: Jordan Koehn Summary: Can't generate job using DSL using with projectName + projectVersion Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202820.1572538748000.6186.1572538800593%40Atlassian.JIRA.
[JIRA] (JENKINS-59999) Problem with jenkins repository for debian
Title: Message Title Daniel Beck closed an issue as Duplicate Jenkins / JENKINS-5 Problem with jenkins repository for debian Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202812.1572520693000.6182.1572538140309%40Atlassian.JIRA.
[JIRA] (JENKINS-59996) Tests timing out sometimes
Title: Message Title Jesse Glick updated JENKINS-59996 Jenkins / JENKINS-59996 Tests timing out sometimes Change By: Jesse Glick Status: Fixed but Unreleased Resolved Released As: 1.21.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202806.1572516251000.6180.1572537960192%40Atlassian.JIRA.
[JIRA] (JENKINS-59704) NoSuchMethodError occurs when promoting a build using parametrized trigger
Title: Message Title Jeff Dege commented on JENKINS-59704 Re: NoSuchMethodError occurs when promoting a build using parametrized trigger This is a show-stopper for us, I'm trying to set up promotions on a job, and I'm getting this every time I try to re-execute a promotion. Any ideas when it will be fixed? Or what I need to roll back, and how far, to get this working? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202405.157054141.6160.1572537180586%40Atlassian.JIRA.
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-54988 jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196023.1543858712000.6157.1572536160312%40Atlassian.JIRA.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Ariel M commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis We are also facing the same issue. it's weird coz' it's working for one MS, but not for the other. is there any update for it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.146326.1350570861000.6131.1572535860677%40Atlassian.JIRA.
[JIRA] (JENKINS-60003) Publish Over SSH Plugin - Exclude Files From Clean Remote Operation
Title: Message Title Travis Abdelhamed created an issue Jenkins / JENKINS-60003 Publish Over SSH Plugin - Exclude Files From Clean Remote Operation Issue Type: New Feature Assignee: Unassigned Components: publish-over-ssh-plugin Created: 2019-10-31 15:22 Environment: Jenkins ver. 2.190.1 Publish over SSH Plugin version: 1.20.1 Priority: Major Reporter: Travis Abdelhamed Currently, within this plugin, you can provide a pattern to exclude files in which you do not want to transfer. Also within this plugin, there is an option to "Clean remote" which enables you to wipe out the remote directory before transferring files. The ask is to be able to provide an exclude pattern for the files which are being wiped from the clean remote option. So there would be two exclude patterns within the configuration. One to exclude files to transfer, and one to exclude files to delete when remote clean is enabled. Add Comment
[JIRA] (JENKINS-59992) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title
Wadeck Follonier edited a comment on JENKINS-59992
Re: "Jenkins.instance is missing" error when restarting Jenkins
Thank you [~csclutgen] for the report. Due to the stack trace, the symptoms are different from JENKINS-55070. Here the problem is revealed in [AuthorizationContainer.java#L169|https://github.com/jenkinsci/matrix-auth-plugin/blob/master/src/main/java/org/jenkinsci/plugins/matrixauth/AuthorizationContainer.java#L169].After a deeper investigation, the problem seems to be after the nullification of {{theInstance}} in [Jenkins#L3400|https://github.com/jenkinsci/jenkins/blob/06f4c89121533fd669a102c97b514534ef1ebcb7/core/src/main/java/jenkins/model/Jenkins.java#L3400-L3404]. There is a moment between the instance being null and the real restart (fraction of second) and that that time, the instance cannot be retrieved.As the HudsonIsRestarting is only used as the last filter, it has no chance to avoid other computation yet. The problem is when a filter that is applied earlier, requires to have access to {{Jenkins.get()}}.I see two opportunities to correct the problem:# Ensure every filter or class being potentially used by a filter, to not use {{Jenkins.get()}}, but instead {{Jenkins.getInstanceOrNull()}} and act correctly in case it's null. This could require a lots of work and hard time explaining the situation to people.# Prevent the regular filters to be applied when the HudsonIsRestarting is the "app" in the servletContext. To elaborate on option 2, current flow of filters to servlet:* DiagnosticThreadNameFilter* CharacterEncodingFilter* CompressionFilter* HudsonFilter** ChainedServletFilter*** HttpSessionContextIntegrationFilter2*** BasicHeaderProcessor*** AuthenticationProcessingFilter2*** RememberMeProcessingFilter*** AnonymousProcessingFilter*** ExceptionTranslationFilter*** UnwrapSecurityExceptionFilter* * CrumbFilter* * PluginServletFilter** * UserLanguages** * [...] << PluginServletFilter.addFilter (mainly for legacy plugins)* Stapler as the main ServletWe could either bypass completely the filters (HudsonFilter + CrumbFilter + PluginServletFilter) and reach directly the app (Stapler), or disabling the configured filters. If we bypass the rest of the filter, we will have troubles to deliver the asset bounded to the restart page, but this could be done "inline" and avoid any other parallel call. That could solve the > WARNING h.s.HttpSessionContextIntegrationFilter2#hasInvalidSessionSeed: Encountered IllegalStateException trying to get a user. System init may not have completed yet. Invalidating user session.But I was not able to reproduce the second warning, as I was not using the WindowsService. I imagine it's somewhat linked.
Add Comment
[JIRA] (JENKINS-60002) Tried proxying hudson.plugins.emailext.ExtendedEmailPublisherDescriptor to support a circular dependency, but it is not an interface.
Title: Message Title Stefan Völkel created an issue Jenkins / JENKINS-60002 Tried proxying hudson.plugins.emailext.ExtendedEmailPublisherDescriptor to support a circular dependency, but it is not an interface. Issue Type: Bug Assignee: Alex Earl Attachments: stacktrace.txt Components: email-ext-plugin Created: 2019-10-31 15:18 Environment: $ java -version openjdk version "1.8.0_222" OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1~deb9u1-b10) OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) PRETTY_NAME="Debian GNU/Linux 9 (stretch)" email-ext-2.68 Priority: Minor Reporter: Stefan Völkel When using a Pre-send Script, jenkins reports the following stacktrace: Oct 31, 2019 4:02:38 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error WARNING: Failed to instantiate Key[type=hudson.plugins.emailext.ExtendedEmailPublisherDescriptor, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Tried proxying hudson.plugins.emailext.ExtendedEmailPublisherDescriptor to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at
[JIRA] (JENKINS-59968) Variable expansion in string cause exception for pipelines
Title: Message Title Gunnar Strand commented on JENKINS-59968 Re: Variable expansion in string cause exception for pipelines I downgraded then plugin to get production working, but I will try to reproduce the fault and try the above as soon as I can. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202772.1572337231000.6121.1572533400121%40Atlassian.JIRA.
[JIRA] (JENKINS-59702) Views with non-ASCII characters can no longer contain a whitespace
Title: Message Title Daniel Beck updated JENKINS-59702 Jenkins / JENKINS-59702 Views with non-ASCII characters can no longer contain a whitespace Change By: Daniel Beck Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202402.1570531847000.6117.1572533220574%40Atlassian.JIRA.
[JIRA] (JENKINS-59985) Warnings Next Generation Plugin for IAR C_STAT does not report warnings
Title: Message Title Ulli Hafner commented on JENKINS-59985 Re: Warnings Next Generation Plugin for IAR C_STAT does not report warnings The IAR cstat parser has the following supported output format: https://github.com/jenkinsci/analysis-model/blob/master/src/test/resources/edu/hm/hafner/analysis/parser/iar-cstat.txt It was contributed by a volunteer Lorenz Aebi, maybe he can help? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202791.1572444215000.6115.1572533040277%40Atlassian.JIRA.
[JIRA] (JENKINS-12425) Windows service install fails with file in use
Title: Message Title Marcin Cimaszewski commented on JENKINS-12425 Re: Windows service install fails with file in use Just for future and not search after obvious things. I have reproduced that case. Steps to reproduce: master1 UI > Manage Jenkins > Manage Nodes add new node connect your agent1 to master1 via jnlp install connection as a service master2 UI > Manage Jenkins > Manage Nodes add new node connect your agent1 to master2 via jnlp try to install connection as a service Effect: Popup with statement as in description: java.io.FileNotFoundException: c:\JenkinsTest\jenkins-slave.exe (The process cannot access the file because it is being used by another process) To cross check that service is running execute from cmd: c:\JenkinsTest\jenkins-slave.exe status Resolution: Choose which master should utilize that agent and use another agent for another master Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60001) Jenkins jobs disabling itself!
Title: Message Title udaybhasker godavarty created an issue Jenkins / JENKINS-60001 Jenkins jobs disabling itself! Issue Type: Bug Assignee: Victor Martinez Components: jenkinslint-plugin Created: 2019-10-31 13:52 Environment: Jenkins ver. 1.651.3 Priority: Minor Reporter: udaybhasker godavarty we are using Jenkins Jenkins ver. 1.651.3 for deploymetns. Recently we notices a very strange behavior that all the jobs are disabling itself. We didn't not made any updates. Please help me in identifying the issue. Add Comment
[JIRA] (JENKINS-59985) Warnings Next Generation Plugin for IAR C_STAT does not report warnings
Title: Message Title Roger Smith commented on JENKINS-59985 Re: Warnings Next Generation Plugin for IAR C_STAT does not report warnings I should probably add that I am primarily an FPGA designer working in VHDL. I set up out Jenkins system initially to check our FPGA projects, compiling with Xilinx and Altera tools and simulating with ModelSim. I'm not working directly on the MCU projects and have little knowledge of IAR EWB (but I'm keen to bring as much as I can into Jenkins) and the engineers working on the MCUs normally use the GUI, not command line, so it may be that I'm missing something fundamental. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202791.1572444215000.6083.1572529620133%40Atlassian.JIRA.
[JIRA] (JENKINS-59985) Warnings Next Generation Plugin for IAR C_STAT does not report warnings
Title: Message Title Roger Smith commented on JENKINS-59985 Re: Warnings Next Generation Plugin for IAR C_STAT does not report warnings The --no_wrap_diagnostics option does not appear to be valid. Not sure if this option is only available in certain versions of IAR EWB (and not in the version for Renesas RX). If I try to use it I get the error message: ERROR, Unknown command: "--no_wrap_diagnostics" is not a valid command For the compiler, the following command is OK and gives messages which the IAR Compiler (C/C++) tool can use.: iarbuild %project_file% -make Release -log all These give errors: iarbuild %project_file% -make Release -log all --no_wrap_diagnostics iarbuild %project_file% -make Release --no_wrap_diagnostics For C-STAT, the following command runs OK (and produces a .db file) but gives no messages to the console, hence the IAR C-STAT tool thinks everything is OK: iarbuild %project_file% -cstat_analyze Release -log all These give errors: iarbuild %project_file% -cstat_analyze Release -log all --no_wrap_diagnostics iarbuild %project_file% -cstat_analyze Release --no_wrap_diagnostics Once cstat .db file has been generated, I then convert these to html with the command (again, no warnings in the console): ireport --db .\Release\Obj\cstat.db --project %project_file% --full --output .\cstat_html\cstat_result.html Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this
[JIRA] (JENKINS-59996) Tests timing out sometimes
Title: Message Title Vincent Latombe updated JENKINS-59996 Jenkins / JENKINS-59996 Tests timing out sometimes Change By: Vincent Latombe Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202806.1572516251000.6072.1572527640205%40Atlassian.JIRA.
[JIRA] (JENKINS-59702) Views with non-ASCII characters can no longer contain a whitespace
Title: Message Title Sven Kirmess commented on JENKINS-59702 Re: Views with non-ASCII characters can no longer contain a whitespace This is fixed in 2.190.2. (Probably JENKINS-59406) Thank you! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202402.1570531847000.6070.1572527520145%40Atlassian.JIRA.
[JIRA] (JENKINS-59997) Websphere deployment plugin expects ant GLOB pattern while deploying a war file to WAS 8.5
Title: Message Title krishna lakshmi commented on JENKINS-59997 Re: Websphere deployment plugin expects ant GLOB pattern while deploying a war file to WAS 8.5 Below is an update for the issue : The plugin is actually expecting a relative path , i.e., it is looking for the artifact within jenkins workspace . We will have to place the war file manually in the workspace folder or will have to run a windows batch command to place war file in workspace after the build is done. This violates the intent of devops . Plugin should be able to pick up the war file where it built and place i.e., the absolute path of the war file should be accepted. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202808.1572517883000.6067.1572526980059%40Atlassian.JIRA.
[JIRA] (JENKINS-18866) Symlink prevens backup from ThinBackup
Title: Message Title Helene W commented on JENKINS-18866 Re: Symlink prevens backup from ThinBackup Hi, I have the same issue that Piotr Krukowiecki described. All of our backups are corrupt due to errors like this: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path 'E:\JBackup'. java.io.IOException: Failed to list contents of E:\Jenkins\jobs\Experiments\jobs\Company\jobs\RollingBuildRerun\jobs\Rerun_Rolling_Build_param\lastSuccessful This also causes that the moving of old backups to ZIP files is not performed. I'm setting this bug to Blocker as the plugin is simply not usable if it does not create a backup. System data: Windows Server 2008 R2 SP1 Jenkins version 2.195 ThinBackup Plugin version 1.9 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150313.1374492663000.6062.1572526140209%40Atlassian.JIRA.
[JIRA] (JENKINS-18866) Symlink prevens backup from ThinBackup
Title: Message Title Helene W updated an issue Jenkins / JENKINS-18866 Symlink prevens backup from ThinBackup Change By: Helene W Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150313.1374492663000.6056.1572525780506%40Atlassian.JIRA.
[JIRA] (JENKINS-60000) Plugin ignores jenkins proxy settings
Title: Message Title Benjamin Herbert created an issue Jenkins / JENKINS-6 Plugin ignores jenkins proxy settings Issue Type: Bug Assignee: Azure DevOps Components: azure-credentials-plugin Created: 2019-10-31 12:22 Priority: Major Reporter: Benjamin Herbert I have an environment where Jenkins needs a proxy server to connect to the internet. I have entered the proxy into the plugins setting/configuration at Manage Jenkins > Manage Plugins > Advanced as described in https://wiki.jenkins.io/display/JENKINS/JenkinsBehindProxy. Connection does not work, as the proxy is not used. Steps to reproduce: Requirement: System that requires a proxy to access the internet. Enter proxy settings in Manage Jenkins > Manage Plugins > Advanced Add a new Credential - Kind "Microsoft Azure Service Principal" fill out: Subscription ID Client ID Client Secret Tenant ID ID Description Click on "Verify Service Principal" After some time the error appears: "The provided credentials are not valid"
