[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when buliding tag
Title: Message Title
Yo-An Lin updated an issue
Jenkins / JENKINS-55330
multi-branch pipeline project: github tag not found when buliding tag
Change By:
Yo-An Lin
The git tag was firstly pushed to GitHub and the commits are pushed later. However, Jenkins failed to get updated tag metadata through the GitHub API.This also happens when we re-tag a tag and force pushed to GitHub to rewrite the commit.We tried to use cURL to get the tag via the GitHub API and which works fine, we got the correct tag response.However, Jenkins still failed to the tag data.{code:java}14:36:53 Connecting to https://api.github.com using myuser/** (myuser-github username/password with personal token)java.io.FileNotFoundException:https://api.github.com/repos/xx//git/refs/tags/v0.13.3 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3/git/refs/#get-a-reference"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1457) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) 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) {code}
Add Comment
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when buliding tag
Title: Message Title Yo-An Lin commented on JENKINS-55330 Re: multi-branch pipeline project: github tag not found when buliding tag Tag update makes Jenkins failed to get correct tag information. Currently we can only create a new tag to bypass this bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when buliding tag
Title: Message Title Yo-An Lin created an issue Jenkins / JENKINS-55330 multi-branch pipeline project: github tag not found when buliding tag Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2018-12-26 08:07 Environment: Jenkins 2.150.1 LTS Labels: plugin Priority: Major Reporter: Yo-An Lin The tag was firstly pushed to GitHub and the commits are pushed later. However, Jenkins failed to get updated tag metadata through the GitHub API. This also happens when we re-tag a tag and force pushed to GitHub to rewrite the commit. We tried to use cURL to get the tag via the GitHub API and which works fine, we got the correct tag response. However, Jenkins still failed to the tag data. 14:36:53 Connecting to https://api.github.com using myuser/** (myuser-github username/password with personal token)java.io.FileNotFoundException:https://api.github.com/repos/xx//git/refs/tags/v0.13.3 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Re
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when buliding tag
Title: Message Title
Yo-An Lin updated an issue
Jenkins / JENKINS-55330
multi-branch pipeline project: github tag not found when buliding tag
Change By:
Yo-An Lin
The git tag was firstly pushed to GitHub and the commits are pushed later.However, Jenkins failed to get updated tag metadata through the GitHub API.This also happens when we re-tag a tag and force pushed to GitHub to rewrite the commit.We tried to use cURL to get the tag via the GitHub API and which works fine, we got the correct tag response.However, Jenkins still failed to the tag data. It seems like Jenkins cached the API response and didn't invalidate the cache. {code:java}14:36:53 Connecting to https://api.github.com using myuser/** (myuser-github username/password with personal token)java.io.FileNotFoundException:https://api.github.com/repos/xx//git/refs/tags/v0.13.3 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3/git/refs/#get-a-reference"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1457) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) 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) {code}
Add Comment
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when buliding tag
Title: Message Title
Yo-An Lin updated an issue
Jenkins / JENKINS-55330
multi-branch pipeline project: github tag not found when buliding tag
Change By:
Yo-An Lin
The git tag was firstly pushed to GitHub and the commits are pushed later.However, Jenkins failed to get updated tag metadata through the GitHub API.This also happens when we re-tag a tag and force pushed to GitHub to rewrite the commit.We tried to use cURL with the same credential to get the tag via the GitHub API and which works fine, we got the correct tag response.However, Jenkins still failed to the tag data. It seems like Jenkins cached the API response and didn't invalidate the cache.{code:java}14:36:53 Connecting to https://api.github.com using myuser/** (myuser-github username/password with personal token)java.io.FileNotFoundException:https://api.github.com/repos/xx//git/refs/tags/v0.13.3 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3/git/refs/#get-a-reference"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1457) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) 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) {code}
Add Comment
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when buliding tag
Title: Message Title
Yo-An Lin updated an issue
Jenkins / JENKINS-55330
multi-branch pipeline project: github tag not found when buliding tag
Change By:
Yo-An Lin
The git tag was firstly pushed to GitHub and the commits are pushed later.However, Jenkins failed to get updated tag metadata through the GitHub API.This also happens when we re-tag a tag and force pushed to GitHub to rewrite the commit.We tried to use cURL with the same credential to get the tag via the GitHub API and which works fine, we got the correct tag response.However, Jenkins still failed to the tag data. It seems like Jenkins cached the API response and didn't invalidate the cache.{code:java}14:36:53 Connecting to https://api.github.com using myuser/** (myuser-github username/password with personal token)java.io.FileNotFoundException:https://api.github.com/repos/xx//git/refs/tags/v0.13.3 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285) Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3/git/refs/#get-a-reference"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1457) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) 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) {code}
Add Comment
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when buliding tag
Title: Message Title
Yo-An Lin updated an issue
Jenkins / JENKINS-55330
multi-branch pipeline project: github tag not found when buliding tag
Change By:
Yo-An Lin
The git tag was firstly pushed to GitHub and the commits are pushed later.However, Jenkins failed to get updated tag metadata through the GitHub API.This also happens when we re-tag a tag and force pushed to GitHub to rewrite the commit.We tried to use cURL with the same credential to get the tag via the GitHub API and which works fine, we got the correct tag response.However, Jenkins still failed to the tag data. It seems like Jenkins cached the API response and didn't invalidate the cache. {code :java }14:36:53 Connecting to https://api.github.com using myuser/** (myuser-github username/password with personal token)java.io.FileNotFoundException:https://api.github.com/repos/xx//git/refs/tags/v0.13.3 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3/git/refs/#get-a-reference"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1457) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) 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) {code}
Add Comment
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when building a tag
Title: Message Title Yo-An Lin updated an issue Jenkins / JENKINS-55330 multi-branch pipeline project: github tag not found when building a tag Change By: Yo-An Lin Summary: multi-branch pipeline project: github tag not found when buliding building a tag Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when buliding tag
Title: Message Title
Yo-An Lin updated an issue
Jenkins / JENKINS-55330
multi-branch pipeline project: github tag not found when buliding tag
Change By:
Yo-An Lin
The git tag was firstly pushed to GitHub and the commits are pushed later. "Fetch Tags" is already enabled, However, Jenkins failed to get updated tag metadata through the GitHub API.This also happens when we re-tag a tag and force pushed to GitHub to rewrite the commit.We tried to use cURL with the same credential to get the tag via the GitHub API and which works fine, we got the correct tag response. However, Jenkins still failed to the tag data. It seems like Jenkins cached the API response and didn't invalidate the cache.{code}14:36:53 Connecting to https://api.github.com using myuser/** (myuser-github username/password with personal token)java.io.FileNotFoundException:https://api.github.com/repos/xx//git/refs/tags/v0.13.3 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625) at org.kohsuke.github.Requester.parse(Requester.java:607) at org.kohsuke.github.Requester._to(Requester.java:285)Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3/git/refs/#get-a-reference"} at org.kohsuke.github.Requester.handleApiError(Requester.java:699) at org.kohsuke.github.Requester._to(Requester.java:306) at org.kohsuke.github.Requester.to(Requester.java:247) at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1457) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) 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) {code}
Add Comment
[JIRA] (JENKINS-43540) builds/lastSuccessfulBuild symlink is not created
Title: Message Title Andor Herendi commented on JENKINS-43540 Re: builds/lastSuccessfulBuild symlink is not created Hello Guys! Is this still a thing? I've checked the codebase and they altered the behavior in this commit. For me, it seems the noSymLink and symlinkEscapeHatch environment variables are no longer in use or not making any difference for the code. By default, the code tries to create the links and if it isn't supported by the filesystem, then it catches the exception and logs its content into the log files. If my assumptions are correct and noSymLink and symlinkEscapeHatch doesn't alters the behavior elsewhere, then we should remove these two variables from this page, because these are no longer supported or used. I also planning to move Jenkins' home to such a filesystem (Azure Files) where the symlinks are not supported. Did you saw any side-effects while using Jenkins? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when building a tag
Title: Message Title
Yo-An Lin commented on JENKINS-55330
Re: multi-branch pipeline project: github tag not found when building a tag
This is related to the okhttp used by the GitHub branch source plugin: src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java LINE 393
OkHttpClient client = new OkHttpClient().setProxy(getProxy(host));
if (cacheDir != null) {
Cache cache = new Cache(cacheDir, cacheSize * 1024L * 1024L);
client.setCache(cache);
}
And here is the related part of the okhttp client https://github.com/square/okhttp/wiki/Recipes#response-caching
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55331) Shelving fails if the optional Folder plugin is absent
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-55331 Shelving fails if the optional Folder plugin is absent Issue Type: Bug Assignee: Pierre Beitz Components: shelve-project-plugin Created: 2018-12-26 09:35 Priority: Minor Reporter: Pierre Beitz Try to shelve a project from a fresh Jenkins installation without the Folder plugin installed Observe that the project won't be shelved In the logs: Executor threw an exception java.lang.ClassNotFoundException: com.cloudbees.hudson.plugins.folder.AbstractFolder at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) Caused: java.lang.NoClassDefFoundError: com/cloudbees/hudson/plugins/folder/AbstractFolder at org.jvnet.hudson.plugins.shelveproject.ShelveProjectExecutable.createListOfFoldersToBackup(ShelveProjectExecutable.java:123) at org.jvnet.hudson.plugins.shelveproject.ShelveProjectExecutable.archiveProject(ShelveProjectExecutable.java:63) at org.jvnet.hudson.plugins.shelveproject.ShelveProjectExecutable.run(ShelveProjectExecutable.java:47) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)
[JIRA] (JENKINS-48881) Stage still shown with NaNy NaNd when condition returns false
Title: Message Title Akashdeep Thakur commented on JENKINS-48881 Re: Stage still shown with NaNy NaNd when condition returns false This issue needs to be fixed. NaNy NaNd does not look good on build dashboard Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when building a tag
Title: Message Title Yo-An Lin commented on JENKINS-55330 Re: multi-branch pipeline project: github tag not found when building a tag When I use cURL to call the GitHub API, I got this: HTTP/1.1 200 OK Server: GitHub.com Date: Wed, 26 Dec 2018 09:35:06 GMT Content-Type: application/json; charset=utf-8 Content-Length: 386 Status: 200 OK X-RateLimit-Limit: 5000 X-RateLimit-Remaining: 4999 X-RateLimit-Reset: 1545820506 Cache-Control: private, max-age=60, s-maxage=60 Vary: Accept, Authorization, Cookie, X-GitHub-OTP ETag: "x" Last-Modified: Wed, 26 Dec 2018 05:04:44 GMT X-Poll-Interval: 300 X-OAuth-Scopes: repo X-Accepted-OAuth-Scopes: repo X-GitHub-Media-Type: github.v3; format=json Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type Access-Control-Allow-Origin: * Strict-Transport-Security: max-age=31536000; includeSubdomains; preload X-Frame-Options: deny X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin Content-Security-Policy: default-src 'none' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55331) Shelving fails if the optional Folder plugin is absent
Title: Message Title Pierre Beitz started work on JENKINS-55331 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55331) Shelving fails if the optional Folder plugin is absent
Title: Message Title Pierre Beitz updated JENKINS-55331 Jenkins / JENKINS-55331 Shelving fails if the optional Folder plugin is absent Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42369) agent docker parameters do not honor the current environment
Title: Message Title
Anatoliy Vlassov commented on JENKINS-42369
Re: agent docker parameters do not honor the current environment
Same issue. I am using a dockerfile agent and there is no way (or I don't know one) to pass environment variables to the "docker build" command. Example:
pipeline {
environment {
SSH_KEY = credentials('ssh-key')
}
agent {
dockerfile {
additionalBuildArgs "--build-arg SSH_KEY=${SSH_KEY}"
}
}
stages {
stage('Test') {
steps {
sh 'go test'
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when building a tag
Title: Message Title
Yo-An Lin commented on JENKINS-55330
Re: multi-branch pipeline project: github tag not found when building a tag
} else if (head instanceof GitHubTagSCMHead) {
GitHubTagSCMHead tagHead = (GitHubTagSCMHead) head;
GHRef tag = ghRepository.getRef("tags/" + tagHead.getName());// <- using cached response
String sha = tag.getObject().getSha();
if ("tag".equalsIgnoreCase(tag.getObject().getType())) {
// annotated tag object
GHTagObject tagObject = ghRepository.getTagObject(sha);
// we want the sha of the tagged commit not the tag object
sha = tagObject.getObject().getSha();
}
return new GitTagSCMRevision(tagHead, sha);
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53939) Plot plugin configuration in pipeline script - run job on remote node - graph not shown
Title: Message Title
Lubov Shilin commented on JENKINS-53939
Re: Plot plugin configuration in pipeline script - run job on remote node - graph not shown
We made it to work:
It cleared the file should be located in workspace/ folder, so configured as file: "SpeedResults.csv",
In addition plot creation should be the separate stage with its own step. It worked when we configured as follows:
stage ('Building plot') {
agent {node }
steps {
plot csvFileName: 'plot-041d39c5-d0b5-46b4-8465-55c5f2a48b2d.csv',
csvSeries: [[
width: 1600,
height: 1600,
displayTableFlag: false,
exclusionValues: '',
file: 'SpeedResults.csv',
inclusionFlag: 'OFF',
url: '']],
group: 'InternetSpeedTestGroup',
keepRecords: true,
numBuilds: '50',
style: 'lineSimple',
title: 'Cellact COM Internet Speed Test',
yaxis: 'Speed(mbps)'
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and
[JIRA] (JENKINS-55332) Some info is missing in pipeline log after upgrading Jenkins from 2.89 to 2.138
Title: Message Title Royce Shen created an issue Jenkins / JENKINS-55332 Some info is missing in pipeline log after upgrading Jenkins from 2.89 to 2.138 Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-12-26 10:16 Priority: Major Reporter: Royce Shen The log produced by pipeline jobs is no longer prefixed with the name of the step that produces them. This makes analyzing logs from pipelines including parallel steps very hard. Please restore the old behavior. For example: The log before upgrading: [inmlcx] c:\python272_x64\python.exe -Wall ..\make.inc\compile.py -d V:\release\s3\12.23.000\04328\projmake.inc\inmlcx\ -f V:\release\s3\12.23.000\04328\projmake.inc\sphinxinjectiondirective.py >>>& V:\release\s3\12.23.000\04328\projmake.inc\inmlcx.err >>>& V:\release\s3\12.23.000\04328\.\inmlcx.err [inmlcs] V:\release\s3\12.23.000\04328\make.inc\inmlcs\S2_inmlcs.env\Scripts\python.exe -Wall -O ..\make.inc\compile.py -d V:\release\s3\12.23.000\04328\make.inc\inmlcs\ -f V:\release\s3\12.23.000\04328\make.inc\makezip.py >>>& V:\release\s3\12.23.000\04328\make.inc\inmlcs.err >>>& V:\release\s3\12.23.000\04328\.\inmlcs.err [rlg] gcc -iquote/v/release/s3/12.23.000/04328/servlang/ -iquote/v/release/s3/12.23.000/04328/servlang - [inmlcx] c:\python272_x64\python.exe -Wall -O ..\make.inc\compile.py -d V:\release\s3\12.23.000\04328\projmake.inc\inmlcx\ -f V:\release\s3\12.23.000\04328\projmake.inc\lintproj.py >>>& V:\release\s3\12.23.000\04328\projmake.inc\inmlcx.err >>>& V:\release\s3\12.23.000\04328\.\inmlcx.err Log After: c:\python272_x64\python.exe -Wall ..\make.inc\compile.py -d V:\release\s3\12.23.000\04328\projmake.inc\inmlcx\ -f V:\release\s3\12.23.000\04328\projmake.inc\sphinxinjectiondirective.py >>>& V:\release\s3\12.23.000\04328\projmake.inc\inmlcx.err >>>& V:\release\s3\12.23.000\04328\.\inmlcx.err V:\release\s3\12.23.000\04328\make.inc\inmlcs\S2_inmlcs.env\Scripts\python.exe -Wall -O ..\make.inc\compile.py -d V:\release\s3\12.23.000\04328\make.inc\inmlcs
[JIRA] (JENKINS-33090) Ease bundles management by the administrator
Title: Message Title Arnaud Héritier stopped work on JENKINS-33090 Change By: Arnaud Héritier Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55023) Remote ssh slave disconnection
Title: Message Title Dayanand Biradar updated an issue Jenkins / JENKINS-55023 Remote ssh slave disconnection Change By: Dayanand Biradar Environment: Jenkins master 2.53 JDK openjdk version "1.8.0_191" OS:Ubuntu 16.04.1 LTSSlave java version "1.7.0_79" OS: fedora 20 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55023) Remote ssh slave disconnection
Title: Message Title Dayanand Biradar commented on JENKINS-55023 Re: Remote ssh slave disconnection Hi Ivan Fernandez Calvo, we are using ssh-slave plugin version 1.23 and it working fine with JDK 7 on Fedora 20 machines but experiencing slave disconnections while running the jobs with the above error log. Regards, Daya Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55023) Remote ssh slave disconnection
Title: Message Title Dayanand Biradar updated an issue Jenkins / JENKINS-55023 Remote ssh slave disconnection Change By: Dayanand Biradar Environment: Jenkins master 2.53 JDK openjdk version "1.8.0_191" OS:Ubuntu 16.04.1 LTSSlave java version "1.7.0_79" OS: fedora 20 ssh-slave plugin version 1.23 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55333) Add Deployment feature for Tomcat 9
Title: Message Title Nitinkumar Thakkar created an issue Jenkins / JENKINS-55333 Add Deployment feature for Tomcat 9 Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-12-26 10:33 Environment: 2.138.3 Jenkins build on Windows 10 under JDK 1.8 Priority: Major Reporter: Nitinkumar Thakkar All of our environments for deploying web based application are under Tomcat 9. This includes test, stage and production. For the current support, we downgraded our tests to Tomcat 8 to manage automated build. However, we cannot do the same for Stage and Production due to the dependency on other projects. We need a feature to deploy wars automatically on tomcat 9. As I see we don't have that option under the container selection for deploying war / ear doesn't have 9 as an option. Add Comment
[JIRA] (JENKINS-55328) recordIssues and ScanForIssues in Pipeline get NPE Errors
Title: Message Title Sylvain G. commented on JENKINS-55328 Re: recordIssues and ScanForIssues in Pipeline get NPE Errors Fo my case, PMD header file cannot contains namespace. (namespace in project, excepts spring, are not permitted in my working envirnomnent. Header looks like this "1.0" encoding="UTF-8"?> "5.4.1" timestamp="2018-12-25T12:09:50.888"> Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when building a tag
Title: Message Title Yo-An Lin commented on JENKINS-55330 Re: multi-branch pipeline project: github tag not found when building a tag Pull request https://github.com/jenkinsci/github-branch-source-plugin/pull/197 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54403) Job fail when GitHub tag was recreated
Title: Message Title Yo-An Lin commented on JENKINS-54403 Re: Job fail when GitHub tag was recreated Pull request for fixing this issue https://github.com/jenkinsci/github-branch-source-plugin/pull/197 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55330) multi-branch pipeline project: github tag not found when building a tag
Title: Message Title
Yo-An Lin edited a comment on JENKINS-55330
Re: multi-branch pipeline project: github tag not found when building a tag
When I use cURL to call the GitHub API to get an existing tag , I got this:{code}HTTP/1.1 200 OKServer: GitHub.comDate: Wed, 26 Dec 2018 09:35:06 GMTContent-Type: application/json; charset=utf-8Content-Length: 386Status: 200 OKX-RateLimit-Limit: 5000X-RateLimit-Remaining: 4999X-RateLimit-Reset: 1545820506Cache-Control: private, max-age=60, s-maxage=60Vary: Accept, Authorization, Cookie, X-GitHub-OTPETag: "x"Last-Modified: Wed, 26 Dec 2018 05:04:44 GMTX-Poll-Interval: 300X-OAuth-Scopes: repoX-Accepted-OAuth-Scopes: repoX-GitHub-Media-Type: github.v3; format=jsonAccess-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP,X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes,X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-TypeAccess-Control-Allow-Origin: *Strict-Transport-Security: max-age=31536000; includeSubdomains; preloadX-Frame-Options: denyX-Content-Type-Options: nosniffX-XSS-Protection: 1; mode=blockReferrer-Policy: origin-when-cross-origin, strict-origin-when-cross-originContent-Security-Policy: default-src 'none'{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38825) MultiJob does not build Pipeline jobs
Title: Message Title Yoram Michaeli commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs Fixed in 1.32 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27734) Allow shelving of folder
Title: Message Title Pierre Beitz started work on JENKINS-27734 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27734) Allow shelving of folder
Title: Message Title Pierre Beitz updated JENKINS-27734 Jenkins / JENKINS-27734 Allow shelving of folder Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55331) Shelving fails if the optional Folder plugin is absent
Title: Message Title Pierre Beitz updated JENKINS-55331 Jenkins / JENKINS-55331 Shelving fails if the optional Folder plugin is absent Change By: Pierre Beitz Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55331) Shelving fails if the optional Folder plugin is absent
Title: Message Title Pierre Beitz updated JENKINS-55331 Jenkins / JENKINS-55331 Shelving fails if the optional Folder plugin is absent Change By: Pierre Beitz Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55334) Document the list of `RecepientProvider` classes available for Jenkins pipelines
Title: Message Title Evgeny Arshinov updated an issue Jenkins / JENKINS-55334 Document the list of `RecepientProvider` classes available for Jenkins pipelines Change By: Evgeny Arshinov Summary: Please document Document the list of `RecepientProvider` classes available for Jenkins pipelines Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55334) Please document the list of `RecepientProvider` classes available for Jenkins pipelines
Title: Message Title Evgeny Arshinov created an issue Jenkins / JENKINS-55334 Please document the list of `RecepientProvider` classes available for Jenkins pipelines Issue Type: Improvement Assignee: David van Laatum Components: email-ext-plugin Created: 2018-12-26 14:13 Environment: - Jenkins 2.95 - Email Extension Plugin 2.61 Priority: Major Reporter: Evgeny Arshinov How a plugin user should know the list of available `RecepientProvider`'s? Googling and downloading the source code are by no means convenient. I could not find a complete list in the official documentation: https://wiki.jenkins.io/display/JENKINS/Email-ext+plugin https://jenkins.io/doc/pipeline/steps/email-ext/ Add Comment
[JIRA] (JENKINS-55334) Document the list of `RecepientProvider` classes available for Jenkins pipelines
Title: Message Title Evgeny Arshinov commented on JENKINS-55334 Re: Document the list of `RecepientProvider` classes available for Jenkins pipelines Please excuse me if I forgot something when filing this ticket. I've read the How to report an issue page but I still could have missed something. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18377) Improve the performance when listing many jobs
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-18377 Improve the performance when listing many jobs Change By: Oleg Nenashev Labels: gsoc-2019-project-idea performance plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46619) [JDK9] Illegal reflective access from FilePath
Title: Message Title Devin Nusbaum commented on JENKINS-46619 Re: [JDK9] Illegal reflective access from FilePath Baptiste Mathus I think that before https://github.com/jenkinsci/jenkins/pull/3135, you would get this error just from starting Jenkins, whereas now you would only get it if methods are actively called that use particular methods inside of PosixAPI#jnr, but I'm not sure what those methods are or whether they are called in normal Jenkins usage and so still a problem. Once we know the answer to that, I think we could close this issue and open new ones as needed. I don't think there is any way for the jnr-posix library to become fully compliant with reflective access without changes to Java APIs, see https://github.com/jnr/jnr-posix/issues/110 as an example, so I think the long-term approach would be to detach the library and rewrite places that need it to use pure Java APIs where possible to reduce our dependency on jnr-posix. See JENKINS-46725 (which I think should be reopened)/https://github.com/jenkinsci/jenkins/pull/3511 for more info. IIRC the majority of uses are just to get the current Process ID, which was added in Java 9 to the java.lang.Process API, so with some kind of new API/multi-release JAR to use the Process API on Java 9+ with a fallback on older versions of Java we might be able to get rid of most of the uses. Part of the issue here is that we expose the jnr-posix API directly in Jenkins core, so plugins can use anything it provides. With backwards compatibility in mind, we probably need to investigate all usages of PosixAPI in plugins to understand what would need to be switched. We should also check which APIs that we currently use throw reflective access exceptions, since if they aren't thrown for any of the calls in core or major plugins than detaching the library is not as urgent. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscrib
[JIRA] (JENKINS-49733) The email-ext-plugin Pipeline integration is not very ergonomic
Title: Message Title Evgeny Arshinov commented on JENKINS-49733 Re: The email-ext-plugin Pipeline integration is not very ergonomic Shouldn't the new syntax be documented on the documentation pages (with examples)? https://wiki.jenkins.io/display/JENKINS/Email-ext+plugin https://jenkins.io/doc/pipeline/steps/email-ext/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55335) Support scripted pipelines in `ListRecipientProvider`
Title: Message Title
Evgeny Arshinov created an issue
Jenkins / JENKINS-55335
Support scripted pipelines in `ListRecipientProvider`
Issue Type:
Improvement
Assignee:
David van Laatum
Attachments:
freestyle job configuration.png
Components:
email-ext-plugin
Created:
2018-12-26 14:59
Priority:
Major
Reporter:
Evgeny Arshinov
https://github.com/jenkinsci/email-ext-plugin/blob/ac54d2684668d12eae40189a55a30e677a813b03/src/main/java/hudson/plugins/emailext/plugins/recipients/ListRecipientProvider.java#L60
@Override public boolean isApplicable(Classextends Job> jobType) {
return !jobType.getName().equals("org.jenkinsci.plugins.workflow.job.WorkflowJob");
}
I wonder what is the problem with supporting `WorkflowJob` here? I believe, it is the job class used in scripted pipelines. Pipeline script
node {
emailext recipientProviders: [[$class: 'ListRecipientProvider']]
}
gives me the following error:
java.lang.IllegalArgumentException: The following recipient providers do not support org.je
[JIRA] (JENKINS-55335) Support scripted pipelines in `ListRecipientProvider`
Title: Message Title Evgeny Arshinov updated an issue Jenkins / JENKINS-55335 Support scripted pipelines in `ListRecipientProvider` Change By: Evgeny Arshinov Environment: - Jenkins 2.95 - Email Extension Plugin 2.61 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55335) Support scripted pipelines in `ListRecipientProvider`
Title: Message Title Evgeny Arshinov commented on JENKINS-55335 Re: Support scripted pipelines in `ListRecipientProvider` Without `ListRecipientProvider` there is no way to send email notifications to a fixed recipients list that does not fall into any predefined recipientProviders category (see `recipientProvides` on https://jenkins.io/doc/pipeline/steps/email-ext/). This issue is a blocker for us, preventing the use of the plugin in our scripted pipeline jobs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27079) ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title
Yan Pak commented on JENKINS-27079
Re: ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
I had the same problem. Every n-th build was failed with ClassCastException error. I have resolved this issue by changing code in the hudson.scm.SubversionSCM.java Source code I took there http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/subversion/2.12.1/ Was:
boolean created;
try {
created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));
} finally {
os.close();
}
if(!created)
createEmptyChangeLog(changelogFile, listener, "log");
Become:
boolean created = false;
try {
if(baseline instanceof SVNRevisionState){
created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));
}
} finally {
os.close();
}
if(!created)
createEmptyChangeLog(changelogFile, listener, "log");
As you can see I added class check. I don't know is it absolutely right way to fix this problem, cause I don't have a whole application architecture view in my mind. It's strange that sometimes argument for new SubversionChangeLogBuilder got not castable to SVNRevisionState. Think this is flaw in the class modelling or plugin development. Good thing that the algorythm of this method permits also no creation of changes log (the purpoise of this failing (sometimes) method is the creation of a changes log after a checkout or an update operation), so I can think that if baseline do not casting into SVNRevisionState then result of this method should not be look as succesful creation of changes log object (created is false). My solution is simple. I don't know why developers still didn't realize this way. I hope, they are looking for class modelling flaw as I mentioned above, or something deeper, if any. Hope I will soon accepted as project member and could pull a request with my changes into Github. Now I have my own fixed subversion.jpi If want - write me there. I tested my solution. Works fine! No more errors like FATAL: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState If anybody will want to take
Add Comment
[JIRA] (JENKINS-27079) ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title
Yan Pak edited a comment on JENKINS-27079
Re: ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
I had the same problem. Every n-th build was failed with ClassCastException error.I have resolved this issue by changing code in the hudson.scm.SubversionSCM.javaSource code I took here [http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/subversion/2.12.1/] Was: {code:java}boolean created;try {created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));} finally {os.close();}if(!created)createEmptyChangeLog(changelogFile, listener, "log");{code} Become: {code:java}boolean created = false;try {if(baseline instanceof SVNRevisionState){created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));}} finally {os.close();}if(!created)createEmptyChangeLog(changelogFile, listener, "log");{code}As you can see I added class check.I don't know is it absolutely right way to fix this problem, cause I don't have a whole application architecture view in my mind. It's strange that sometimes argument for new SubversionChangeLogBuilder got not castable to SVNRevisionState. Think this is flaw in the class modelling or plugin development.Good thing that the algorythm of this method permits also +no+ creation of changes log (the purpoise of this failing (sometimes) method is the creation of a changes log after a checkout or an update operation), so I can think that if baseline do not casting into SVNRevisionState then result of this method should not be look as succesful creation of changes log object (+created+ is false). My solution is simple. I don't know why developers still didn't realize this way. I hope, they are looking for class modelling flaw as I mentioned above, or something deeper, if any. Hope I will soon accepted as project member and could pull a request with my changes into Github. Now I have my own fixed subversion.jpi :) If want - write me there.I tested my solution. *Works fine!* *No more errors* like FATAL: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState If anybody will want to take
Add Comment
[JIRA] (JENKINS-27079) ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title
Yan Pak edited a comment on JENKINS-27079
Re: ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
I had the same problem. Every n-th build was failed with ClassCastException error.I have resolved this issue by changing code in the hudson.scm.SubversionSCM.javaSource code I took there here [http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/subversion/2.12.1/] Was: {code:java}boolean created;try {created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));} finally {os.close();}if(!created)createEmptyChangeLog(changelogFile, listener, "log");{code}Become: {code:java}boolean created = false;try {if(baseline instanceof SVNRevisionState){created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));}} finally {os.close();}if(!created)createEmptyChangeLog(changelogFile, listener, "log");{code}As you can see I added class check.I don't know is it absolutely right way to fix this problem, cause I don't have a whole application architecture view in my mind. It's strange that sometimes argument for new SubversionChangeLogBuilder got not castable to SVNRevisionState. Think this is flaw in the class modelling or plugin development.Good thing that the algorythm of this method permits also +no+ creation of changes log (the purpoise of this failing (sometimes) method is the creation of a changes log after a checkout or an update operation), so I can think that if baseline do not casting into SVNRevisionState then result of this method should not be look as succesful creation of changes log object (+created+ is false). {color:#808080} {color} My solution is simple. I don't know why developers still didn't realize this way. I hope, they are looking for class modelling flaw as I mentioned above, or something deeper, if any.Hope I will soon accepted as project member and could pull a request with my changes into Github. Now I have my own fixed subversion.jpi :) If want - write me there.I tested my solution. *Works fine!**No more errors* likeFATAL: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionStateIf anybody will want to take
Add Comment
[JIRA] (JENKINS-27079) ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title
Yan Pak edited a comment on JENKINS-27079
Re: ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
I had the same problem. Every n-th build was failed with ClassCastException error.I have resolved this issue by changing code in the hudson.scm.SubversionSCM.javaSource code I took here [http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/subversion/2.12.1/] Was:{code:java}boolean created;try {created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));} finally {os.close();}if(!created)createEmptyChangeLog(changelogFile, listener, "log");{code} Become:{code:java}boolean created = false;try {if(baseline instanceof SVNRevisionState){created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));}} finally {os.close();}if(!created)createEmptyChangeLog(changelogFile, listener, "log");{code}As you can see I added class check.I don't know is it absolutely right way to fix this problem, cause I don't have a whole application architecture view in my mind. It's strange that sometimes argument for new SubversionChangeLogBuilder got not castable to SVNRevisionState. Think this is flaw in the class modelling or plugin development.Good thing that the algorythm of this method permits also +no+ creation of changes log (the purpoise of this failing (sometimes) method is the creation of a changes log after a checkout or an update operation), so I can think that if baseline do not casting into SVNRevisionState then result of this method should not be look as succesful creation of changes log object (+created+ is false). My solution is simple. I don't know why developers still didn't realize this way. I hope, they are looking for class modelling flaw as I mentioned above, or something deeper, if any. Hope I will soon accepted as project member and could pull a request with my changes into Github. Now I have my own fixed subversion.jpi :) If want - write me there here .I tested my solution. *Works fine!* *No more errors* like FATAL: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState If anybody will want to take
Add Comment
[JIRA] (JENKINS-54353) Jenkinsfile Runner: Replace the JUnit implementation but something production-focused
Title: Message Title Francisco Fernández updated JENKINS-54353 Jenkins / JENKINS-54353 Jenkinsfile Runner: Replace the JUnit implementation but something production-focused Change By: Francisco Fernández Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55170) Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55170 Failure to load flow node: FlowNode was not found in storage for head Change By: Devin Nusbaum Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27079) ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title
Yan Pak edited a comment on JENKINS-27079
Re: ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
I had the same problem. Every n-th build was failed with ClassCastException error.I have resolved solved this issue by changing code in the hudson.scm.SubversionSCM.javaSource code I took here [http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/subversion/2.12.1/] Was:{code:java}boolean created;try {created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));} finally {os.close();}if(!created)createEmptyChangeLog(changelogFile, listener, "log");{code} Become:{code:java}boolean created = false;try {if(baseline instanceof SVNRevisionState){created = new SubversionChangeLogBuilder(build, workspace, (SVNRevisionState) baseline, env, listener, this).run(externalsMap, new StreamResult(os));}} finally {os.close();}if(!created)createEmptyChangeLog(changelogFile, listener, "log");{code}As you can see I added class check.I don't know is it absolutely right way to fix this problem, cause I don't have a whole application architecture view in my mind. It's strange that sometimes argument for new SubversionChangeLogBuilder got not castable to SVNRevisionState. Think this is flaw in the class modelling or plugin development.Good thing that the algorythm of this method permits also +no+ creation of changes log (the purpoise of this failing (sometimes) method is the creation of a changes log after a checkout or an update operation), so I can think that if baseline do not casting into SVNRevisionState then result of this method should not be look as succesful creation of changes log object (+created+ is false). My So, this gives me hope that my solution is simple valid at last . I don't know why developers still didn't realize this way. I hope, they are looking for class modelling flaw as I mentioned above, or something deeper, if any. Hope I hope my pull request #228 will soon accepted as project member and could pull a request with my changes into Github . Now I have my own fixed subversion.jpi :) If want - write me here.I tested my solution. *Works fine!* *No more errors* like FATAL : _FATAL: hudson.scm.SVNRevisionState cannot be cast to hudson.scm. SVNRevisionState If anybody will want to take SVNRevisionState_
Add Comment
[JIRA] (JENKINS-45942) Bad error message/silent death with incorrectly setup permissions in the RoleBasedAuthorizationStrategy
Title: Message Title Oleg Nenashev started work on JENKINS-45942 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45942) Bad error message/silent death with incorrectly setup permissions in the RoleBasedAuthorizationStrategy
Title: Message Title Oleg Nenashev updated JENKINS-45942 Jenkins / JENKINS-45942 Bad error message/silent death with incorrectly setup permissions in the RoleBasedAuthorizationStrategy Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45942) Bad error message/silent death with incorrectly setup permissions in the RoleBasedAuthorizationStrategy
Title: Message Title Oleg Nenashev commented on JENKINS-45942 Re: Bad error message/silent death with incorrectly setup permissions in the RoleBasedAuthorizationStrategy https://github.com/jenkinsci/role-strategy-plugin/pull/49 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45485) Obtain logging of Jenkins interaction with Role system
Title: Message Title Matt Sicker commented on JENKINS-45485 Re: Obtain logging of Jenkins interaction with Role system Related to JENKINS-54082? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55126) PerfPublisher shows HTML tags ("") instead of rendered output
Title: Message Title
Eugene Schava commented on JENKINS-55126
Re: PerfPublisher shows HTML tags ("") instead of rendered output
Please check new release
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55333) Add Deployment feature for Tomcat 9
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55333 Add Deployment feature for Tomcat 9 Change By: Oleg Nenashev Labels: platform-sig Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46325) Should we use result or currentResult?
Title: Message Title Ethan Spoelstra commented on JENKINS-46325 Re: Should we use result or currentResult? According to the documentation if you are using Scripted Pipeline syntax you probably need to explicitly set the currentBuild.result so that you and Jenkins can track it between stages. https://support.cloudbees.com/hc/en-us/articles/218554077-How-to-set-current-build-result-in-Pipeline- Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55333) Add Deployment feature for Tomcat 9
Title: Message Title Oleg Nenashev commented on JENKINS-55333 Re: Add Deployment feature for Tomcat 9 > As I see we don't have that option under the container selection for deploying war / ear doesn't have 9 as an option. Could you please explain how you do it for Tomcat8? Is there a Web Interface for it somewhere. Screenshots would help Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55314) Perspective Java 12+ stories
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55314 Perspective Java 12+ stories Change By: Oleg Nenashev Labels: platform-sig Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55305) Add user creation listener-methods to SecurityListener
Title: Message Title Matt Sicker commented on JENKINS-55305 Re: Add user creation listener-methods to SecurityListener Note that this extension point would also be useful for authentication plugins to add support for notifying Jenkins of newly created accounts proactively rather than waiting for someone to attempt to log in first. That might be useful for provisioning user configuration data (e.g., new employee joins team, want to provide default settings to that user). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-8149) Git submodule fetch uses (incorrect) parent refspec
Title: Message Title Evan Wan commented on JENKINS-8149 Re: Git submodule fetch uses (incorrect) parent refspec how to set submodule's refspec, such as gerrit changes in submodule "refs/changes/:refs/changes"? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30319) SSH - Ed25519 keys not supported
Title: Message Title Michael Watters commented on JENKINS-30319 Re: SSH - Ed25519 keys not supported Perhaps it would be nice to warn users that ed25519 keys are not supported. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-55325
System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Change By:
Cyrille Le Clerc
Problem reproduce steps: # *Credentials* > *System* > Add Domain A, just has name specified. # In domain A, add a credential C, username: maven repo username, password: maven repo password. # *Manage Jenkins* > *Managed files*, create a maven global settings.xml M, add Server Credentials using credential C. # Create a Multibranch pipeline, in *Pipeline Maven Configuration* section, using config M. # Run pipeline.Build log:{ { noformat} [withMaven] using Maven global settings.xml '876cdf5c-802b-4252-a062-4b9d8602dd06' with NO Maven servers credentials provided by Jenkins {noformat } } If I create credential C and maven global settings.xml M inside Multibranch pipeline, everything goes fine: { { noformat} [withMaven] using Maven global settings.xml 'f657ec5c-cc63-4730-a133-7e58c3ea433a' with Maven servers credentials provided by Jenkins (replaceAll: true): [mavenServerId: 'supwisdom-snapshots', jenkinsCredentials: '250947bb-2ce2-4cf5-b62f-bba7e2af7df0', username: 'deployment', type: 'UsernamePasswordCredentialsImpl'], [mavenServerId: 'supwisdom-releases', jenkinsCredentials: '250947bb-2ce2-4cf5-b62f-bba7e2af7df0', username: 'deployment', type: 'UsernamePasswordCredentialsImpl'] {noformat } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-55325
System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Change By:
Cyrille Le Clerc
Problem reproduce steps: # *Credentials* > *System* > Add Domain A, just has name specified. # In domain A, add a credential C, username: maven repo username, password: maven repo password. # *Manage Jenkins* > *Managed files*, create a maven global settings.xml M, add Server Credentials using credential C. # Create a Multibranch pipeline, in *Pipeline Maven Configuration* section, using config M. # Run pipeline.Build log:{noformat}[withMaven] using Maven global settings.xml '876cdf5c-802b-4252-a062-4b9d8602dd06'with NO Maven servers credentials provided by Jenkins{noformat}If I create credential C and maven global settings.xml M inside Multibranch pipeline, everything goes fine: {noformat}[withMaven] using Maven global settings.xml 'f657ec5c-cc63-4730-a133-7e58c3ea433a' with Maven servers credentialsprovided by Jenkins (replaceAll: true):[mavenServerId: 'supwisdom-snapshots', jenkinsCredentials: '250947bb-2ce2-4cf5-b62f-bba7e2af7df0', username: 'deployment', type: 'UsernamePasswordCredentialsImpl'],[mavenServerId: 'supwisdom-releases', jenkinsCredentials: '250947bb-2ce2-4cf5-b62f-bba7e2af7df0', username: 'deployment', type: 'UsernamePasswordCredentialsImpl']{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title Cyrille Le Clerc commented on JENKINS-55325 Re: System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline Better warning message when a Maven settings "" definition is skipped because the credentials are not found https://github.com/jenkinsci/pipeline-maven-plugin/pull/194 . Daniel Qian I suspect that the credentials referenced in the Maven settings defined globally are not found. I am improving the warning message, we used to silently omit the skipping of the Maven "" definition when the Jenkins credentials where not found. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-55325
Re: System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Better warning message when a Maven settings "{{}}" definition is skipped because the credentials are not found https://github.com/jenkinsci/pipeline-maven-plugin/pull/194 .[~chanjarster] I suspect that the credentials referenced in the Maven settings defined globally are not found. I am improving the warning message, we used to silently omit the skipping of the Maven "{{}}" definition when the Jenkins credentials where not found. (i) Please note that we recommend to use human readable Ids rather than the generated ids* when defining credentials (e.g. '250947bb-2ce2-4cf5-b62f-bba7e2af7df0')* when defining config files and (global) Maven settings files (e.g. '876cdf5c-802b-4252-a062-4b9d8602dd06' )
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title Cyrille Le Clerc started work on JENKINS-55325 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55318) Maven logs are not colorized
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-55318
Maven logs are not colorized
Change By:
Cyrille Le Clerc
The fact that " {{withMaven() \ { ... \}}} " uses " {{--batch-mode}} " disables the colorization of the Maven logs introduced in Maven 3.5.x.We should also set {{-Dstyle.color=always}}.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55318) Maven logs are not colorized
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-55318
Maven logs are not colorized
Change By:
Cyrille Le Clerc
The fact that "{{withMaven(){ ... \} }}" uses "{{--batch-mode}}" disables the colorization of the Maven logs introduced in Maven 3.5.x.We should also set " {{-Dstyle.color=always}} " .
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55318) Maven logs are not colorized
Title: Message Title Cyrille Le Clerc commented on JENKINS-55318 Re: Maven logs are not colorized We will want to use Jesse Glick's improvement Switching plugin to use ConsoleAnnotator rather than ConsoleNote which requires to bump our requirements on jenkins core to 2.145 . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50366) I would like to add "--first-parent" to git log command
Title: Message Title Ben Sluis commented on JENKINS-50366 Re: I would like to add "--first-parent" to git log command I can see that the git-client-plugin has support for the --first-parent argument being passed to 'git rev-list', https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2838 I've spent a little time trying to figure out if or how this is used by this repo, git-plugin, but I haven't succeeded. Can you share any pointers or places to look to understand this code and how the git-plugin uses the git-client-plugin to fetch change sets from Git? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55336) Downstream pipeline trigger - optimisation "avoid excessive trigger" should not skip some pipeline triggers in case of failure of 'intermediate' builds
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-55336 Downstream pipeline trigger - optimisation "avoid excessive trigger" should not skip some pipeline triggers in case of failure of 'intermediate' builds Issue Type: Improvement Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-12-26 18:44 Priority: Minor Reporter: Cyrille Le Clerc For downstream pipeline triggers based on snapshots, the optimisation "avoid excessive trigger" will prevent direct trigger of pipelines if they have parent pipelines that are also triggers. +--+ | | | MY-FRAMEWORK | | | +---|--|---+ ++ | | || | +--- MY-LIBRARY | | || ++ | ++ || |+- MY-APPLICATION | +--| ++ In the sample above, "my-framework" will only trigger "my-library" and NOT trigger "my-application" because "my-application" will be triggered by "my-library". However, if an 'intermediate' build fails then the downstream pipelines that have been "skipped/omitted" never get triggered. In the sample above, "my-application" is never triggered if the build of "my-library" fails. "withMaven" should detect the failure of "my-library" and understand that "my-application" should be trigger
[JIRA] (JENKINS-55305) Add user creation listener-methods to SecurityListener
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-55305 Add user creation listener-methods to SecurityListener Change By: David Olorundare In Jenkins core, the SecurityListener class has only methods for listening to authentication-based events (e.g. login, logout, authenticated, etc), but lacks any methods for listening to Jenkins user-account creations; which are an equally important set of security-related events. Hence, the SecurityListener class requires an update with those methods that would facilitate this functionality. - To perform this update will require modifying the SecurityListener class within the jenkins-core jenkins/security package.This update will enable the Audit-Log plugin, as well as any other authentication-based plugins, to reuse the same preexisting SecurityListener class to listen for Jenkins user account creation notifications. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55337) MavenConsole tool reports errors with dead links.
Title: Message Title Mike Delaney created an issue Jenkins / JENKINS-55337 MavenConsole tool reports errors with dead links. Issue Type: Improvement Assignee: Ulli Hafner Attachments: Screen Shot 2018-12-26 at 2.03.57 PM.png, Screen Shot 2018-12-26 at 2.04.33 PM.png, Screen Shot 2018-12-26 at 2.04.47 PM.png Components: warnings-ng-plugin Created: 2018-12-26 19:14 Environment: Jenkins 2.150.1 Warning NG 1.0.0 Pipeline Maven 3.6.5 Priority: Minor Reporter: Mike Delaney When using the Pipeline Maven plugin, and Warning NG plugin, if I try to scan for MavenConsole errors, I end up with reports that end up with dead links. If I click the link from the Maven console report, I'm taken to the same page as I was on but with a slightly updated url. For example, if my jobs url is https://jenkins.mycompany.com/job/sample-job/job/feature%252Fupdate-feature-request/4/maven/NORMAL/, I end up with the url https://jenkins.mycompany.com/job/sample-job/job/feature%252Fupdate-feature-request/4/maven/NORMAL/NORMAL/, ... This is a screen shot of the console log during the operation. These are the warnings generated (notice that pom.xml is not listed in the file column). This is what expanding on of the errors looks like (these seems correct to me.)
[JIRA] (JENKINS-55335) Support scripted and declarative pipelines in `ListRecipientProvider`
Title: Message Title Evgeny Arshinov updated an issue Jenkins / JENKINS-55335 Support scripted and declarative pipelines in `ListRecipientProvider` Change By: Evgeny Arshinov Summary: Support scripted and declarative pipelines in `ListRecipientProvider` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55335) Support scripted and declarative pipelines in `ListRecipientProvider`
Title: Message Title
Evgeny Arshinov updated an issue
Jenkins / JENKINS-55335
Support scripted and declarative pipelines in `ListRecipientProvider`
Change By:
Evgeny Arshinov
[https://github.com/jenkinsci/email-ext-plugin/blob/ac54d2684668d12eae40189a55a30e677a813b03/src/main/java/hudson/plugins/emailext/plugins/recipients/ListRecipientProvider.java#L60]{code:java}@Override public boolean isApplicable(Class jobType) {return !jobType.getName().equals("org.jenkinsci.plugins.workflow.job.WorkflowJob");}{code} I wonder what is the problem with supporting `WorkflowJob` here? I believe, it is the job class used in both scripted and declarative pipelines. Pipeline script{code:java}node { emailext recipientProviders: [[$class: 'ListRecipientProvider']]}{code}gives me the following error:{code:java}java.lang.IllegalArgumentException: The following recipient providers do not support org.jenkinsci.plugins.workflow.job.WorkflowJob hudson.plugins.emailext.plugins.recipients.ListRecipientProvider at hudson.plugins.emailext.plugins.RecipientProvider.checkAllSupport(RecipientProvider.java:57) at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:186) at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:163) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:273) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 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} I am trying to make email-ext in my scripted pipeline job send email notifications to the globally configured recipients list—the same that is used in the following freestyle job:!freestyle job configuration.png|thumbnail!
Add Comment
[JIRA] (JENKINS-55335) Support scripted and declarative pipelines in `ListRecipientProvider`
Title: Message Title Evgeny Arshinov edited a comment on JENKINS-55335 Re: Support scripted and declarative pipelines in `ListRecipientProvider` - Without `ListRecipientProvider` there is no way to send email notifications to a fixed recipients list that does not fall into any predefined recipientProviders category (see `recipientProvides` on https://jenkins.io/doc/pipeline/steps/email-ext/). This issue is a blocker for us, preventing the use of the plugin in our scripted pipeline jobs. -_Update_: Nevermind, I have just discovered the `to` argument. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55335) Support scripted and declarative pipelines in `ListRecipientProvider`
Title: Message Title Evgeny Arshinov commented on JENKINS-55335 Re: Support scripted and declarative pipelines in `ListRecipientProvider` I have discovered another undocumented feature. It turned out that one can use `$DEFAULT_zzz` placeholders in pipelines, too. Also I found out that one has to explicitly pass `subject: "$DEFAULT_SUBJECT" and to: "$DEFAULT_TO"`, although it would be nice if the plugin used these values by default. Having discovered all that, we can now use email-ext in our project, despite its poor documentation. The question about `ListRecipientProvider` remains open, though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55335) Support scripted and declarative pipelines in `ListRecipientProvider`
Title: Message Title Evgeny Arshinov edited a comment on JENKINS-55335 Re: Support scripted and declarative pipelines in `ListRecipientProvider` I have discovered another undocumented feature. It turned out that one can use `$DEFAULT_zzz` placeholders in pipelines, too. Normally, such things should be covered in the documentation. Also I also found out that one has to explicitly pass `subject: "$DEFAULT_SUBJECT" and to: "$DEFAULT_TO"`, although it would be nice if the plugin used these values by default.Having discovered all that, we can now use email-ext in our project, despite its poor documentation. The question about `ListRecipientProvider` remains open, though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55338) Pipeline resume after restart fails on Java 11 with marshalling stack trace
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-55338 Pipeline resume after restart fails on Java 11 with marshalling stack trace Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-12-26 22:33 Environment: Jenkins 2.156 run from docker image for jdk11 Latest plugins for that environment (including the workflow-support special plugin from the experimental update center) Labels: java11-compatibility Priority: Minor Reporter: Mark Waite When I restart Jenkins running in a docker container using the JDK 11 image, running Pipeline jobs fail with the following stack trace: Resuming build at Wed Dec 26 15:22:40 MST 2018 after Jenkins restart Waiting to resume part of Git Plugin Folder » CERT Git Branches - Jenkinsfile (GitHub) » SECURITY-1095-tagAction-CSRF #13: ??? [Pipeline] End of Pipeline GitHub has been notified of this commit’s build result hudson.remoting.ProxyException: an exception which occurred: in object of type infra in object of type java.util.LinkedHashMap in object of type buildPlugin in field groovy.lang.Closure.delegate in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@77d43d81 in object of type org.jenkinsci.plugins.workflow.cps.CpsClosure2 in object of type java.util.HashMap in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.closures in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@
[JIRA] (JENKINS-55338) Pipeline resume after restart fails on Java 11 with marshalling stack trace
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55338
Pipeline resume after restart fails on Java 11 with marshalling stack trace
Change By:
Mark Waite
When I restart Jenkins running in a docker container using the JDK 11 image, running Pipeline jobs fail with the following stack trace:{noformat}Resuming build at Wed Dec 26 15:22:40 MST 2018 after Jenkins restartWaiting to resume part of Git Plugin Folder » CERT Git Branches - Jenkinsfile (GitHub) » SECURITY-1095-tagAction-CSRF #13: ???[Pipeline] End of PipelineGitHub has been notified of this commit’s build resulthudson.remoting.ProxyException: an exception which occurred: in object of type infra in object of type java.util.LinkedHashMap in object of type buildPlugin in field groovy.lang.Closure.delegate in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@77d43d81 in object of type org.jenkinsci.plugins.workflow.cps.CpsClosure2 in object of type java.util.HashMap in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.closures in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@35df72cb in object of type org.jenkinsci.plugins.workflow.cps.CpsThreadGroupCaused: hudson.remoting.ProxyException: java.lang.NullPointerException at com.cloudbees.groovy.cps.SerializableScript.readObject(SerializableScript.java:31) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.marshalling.reflect.JDKSpecific$SerMethods.callReadObject(JDKSpecific.java:179) at org.jboss.marshalling.reflect.SerializableClass.callReadObject(SerializableClass.java:212) at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1742) at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1711) at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1711) at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1391) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272) at org.jboss.marshalling.river.BlockUnmarshaller.readObject(BlockUnmarshaller.java:149) at org.jboss.marshalling.river.BlockUnmarshaller.readObject(BlockUnmarshaller.java:135) at org.jboss.marshalling.MarshallerObjectInputStream.readObjectOverride(MarshallerObjectInputStream.java:53) at org.jboss.marshalling.river.RiverObjectInputStream.readObjectOverride(RiverObjectInputStream.java:307) at java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:424) at java.base/java.util.HashMap.readObject(HashMap.java:1460) at java.base/jdk.internal.reflect.GeneratedMethodAccessor14.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[JIRA] (JENKINS-55338) Pipeline resume after restart fails on Java 11 with marshalling stack trace
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55338
Pipeline resume after restart fails on Java 11 with marshalling stack trace
Change By:
Mark Waite
When I restart Jenkins running in a docker container using the JDK 11 image, running Pipeline jobs fail with the following stack trace:{noformat}Resuming build at Wed Dec 26 15:22:40 MST 2018 after Jenkins restartWaiting to resume part of Git Plugin Folder » CERT Git Branches - Jenkinsfile (GitHub) » SECURITY-1095- tagAction -CSRF #13: ???[Pipeline] End of PipelineGitHub has been notified of this commit’s build resulthudson.remoting.ProxyException: an exception which occurred: in object of type infra in object of type java.util.LinkedHashMap in object of type buildPlugin in field groovy.lang.Closure.delegate in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@77d43d81 in object of type org.jenkinsci.plugins.workflow.cps.CpsClosure2 in object of type java.util.HashMap in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.closures in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@35df72cb in object of type org.jenkinsci.plugins.workflow.cps.CpsThreadGroupCaused: hudson.remoting.ProxyException: java.lang.NullPointerException at com.cloudbees.groovy.cps.SerializableScript.readObject(SerializableScript.java:31) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.marshalling.reflect.JDKSpecific$SerMethods.callReadObject(JDKSpecific.java:179) at org.jboss.marshalling.reflect.SerializableClass.callReadObject(SerializableClass.java:212) at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1742) at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1711) at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1711) at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1391) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272) at org.jboss.marshalling.river.BlockUnmarshaller.readObject(BlockUnmarshaller.java:149) at org.jboss.marshalling.river.BlockUnmarshaller.readObject(BlockUnmarshaller.java:135) at org.jboss.marshalling.MarshallerObjectInputStream.readObjectOverride(MarshallerObjectInputStream.java:53) at org.jboss.marshalling.river.RiverObjectInputStream.readObjectOverride(RiverObjectInputStream.java:307) at java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:424) at java.base/java.util.HashMap.readObject(HashMap.java:1460) at java.base/jdk.internal.reflect.GeneratedMethodAccessor14.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title Mark Waite updated JENKINS-53004 git client plugin 3.0.0-beta6 and git plugin 4.0.0-beta4 resolve this problem. Released Dec 15, 2018 Jenkins / JENKINS-53004 checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5) Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-53004 checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5) Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title Mark Waite updated JENKINS-53004 Jenkins / JENKINS-53004 checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5) Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52993) JGit 5.02 logs failure to delete a pruned branch
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-52993 JGit 5.02 logs failure to delete a pruned branch Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52993) JGit 5.02 logs failure to delete a pruned branch
Title: Message Title Mark Waite updated JENKINS-52993 Fixed in git client plugin 3.0.0-beta6, released Dec 15, 2018 Jenkins / JENKINS-52993 JGit 5.02 logs failure to delete a pruned branch Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52993) JGit 5.02 logs failure to delete a pruned branch
Title: Message Title Mark Waite updated JENKINS-52993 Jenkins / JENKINS-52993 JGit 5.02 logs failure to delete a pruned branch Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43556) Stage View shows incorrect build result
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-43556 Re: Stage View shows incorrect build result I have seen cases for which a restart solved this. Anybody able to workaround this by a restart ? I wonder if this could be due to the caching of some objects, for example [com.cloudbees.workflow.flownode.FlowNodeUtil|https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/pipeline-stage-view-2.10/rest-api/src/main/java/com/cloudbees/workflow/flownode/FlowNodeUtil.java] or [js.model.rest-api.js|https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/pipeline-stage-view-2.10/ui/src/main/js/model/rest-api.js] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55174) Pipeline: Support. NPE in build state marshalling
Title: Message Title Oleg Nenashev commented on JENKINS-55174 Re: Pipeline: Support. NPE in build state marshalling https://issues.jboss.org/browse/JBMAR-223 was created by Sam Van Oort Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55234) Mockito is not compatible with Java 11
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55234 Mockito is not compatible with Java 11 Change By: Oleg Nenashev Labels: java11 java11-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55233) email-ext: PowerMock is not compatible with Java 11
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55233 email-ext: PowerMock is not compatible with Java 11 Change By: Oleg Nenashev Labels: java11 java11-compatibility triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title Daniel Qian updated an issue Jenkins / JENKINS-55325 System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline Change By: Daniel Qian Attachment: wx20181227-105...@2x.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title Daniel Qian commented on JENKINS-55325 Re: System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline Cyrille Le Clerc That's strange, please take a look at screenshot i uploaded. Credentials are listed when define global maven settings. BTW, everything goes fine on Jenkins ver. 2.138.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title Daniel Qian edited a comment on JENKINS-55325 Re: System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline [~cleclerc] That's strange weird , please take a look at screenshot i uploaded. Credentials are listed when define global maven settings. BTW, everything goes fine on Jenkins ver. 2.138.3 --- update --- I followed your suggestion not using generated ids for credentials and maven settings. Problem solved. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55339) warnings next-generation: wiki link to issue tracker references a private filter
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-55339 warnings next-generation: wiki link to issue tracker references a private filter Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2018-12-27 05:49 Priority: Minor Reporter: Björn Pedersen The wiki points to https://issues.jenkins-ci.org/issues/?filter=10025, but Jira does not find the filter: The requested filter doesn't exist or is private. Add Comment This message was sent by A
[JIRA] (JENKINS-55340) warnings-ng: pylint parser should use new-style labels
Title: Message Title
Björn Pedersen created an issue
Jenkins / JENKINS-55340
warnings-ng: pylint parser should use new-style labels
Issue Type:
Improvement
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2018-12-27 05:56
Priority:
Trivial
Reporter:
Björn Pedersen
Currently the category for the builtin parser is set to the old-style numeric warnings ("msg_id") (W0xxx). I think it would be better to use the textual representation by default ( the "symbol"), as these are easily human-readable, while the numeric ones always require a lookup.
Add Comment
[JIRA] (JENKINS-55341) Unnecessary git fetch calls to remote repository and storing separate library in every pipeline workspace and in every build dir when using git tags
Title: Message Title Pragnesh Patel created an issue Jenkins / JENKINS-55341 Unnecessary git fetch calls to remote repository and storing separate library in every pipeline workspace and in every build dir when using git tags Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2018-12-27 07:51 Priority: Major Reporter: Pragnesh Patel When we have thousands of pipelines jobs using same version of library and also using git tags to load library than there is no meaning to check for update in git remote repo on every pipeline run, also there is no meaning to store separate library in every pipeline jobs workspace and also under every build directory. Calls to git remote repo on every pipeline run add extra loads on master when you have always large number of builds running all time. And extra storage on master makes maintenance(backup, restore in critical time) of jenkins master difficult and more time consuming. Add Comment
