[JIRA] (JENKINS-38220) Support for EC2 instance profile credentials
Title: Message Title John La Barge commented on JENKINS-38220 Re: Support for EC2 instance profile credentials Need this as well. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174381.1473894967000.13487.1587178140353%40Atlassian.JIRA.
[JIRA] (JENKINS-61954) /runs/ REST api failing to return after update to Jenkins 2.222.1
Title: Message Title Rick commented on JENKINS-61954 Re: /runs/ REST api failing to return after update to Jenkins 2.222.1 /runs/?start=0=85 is not belong to pipeline-restful-api-plugin I believe Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205836.1587155449000.13485.1587174360187%40Atlassian.JIRA.
[JIRA] (JENKINS-61924) json parsing error when fetching branches from github
Title: Message Title
Mike Erickson edited a comment on JENKINS-61924
Re: json parsing error when fetching branches from github
{{I have the same problem for 1 repo (others work)}}Jenkins 2.232git 4.2.2git-client 3.2.1git-server 1.9github 1.29.5github-api 1.111github-branch-source 2.6.0github-organization-folder 1.6 ERROR: [Fri Apr 17 15:03:39 PDT 2020] Could not fetch sources from navigator org.jenkinsci.plugins.github_branch_source.GitHubSCMNavigator@21f39e43com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (StringReader); line: 1, column: 2] at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1840) at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:712) at com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:637) at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1916) at com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:772) at com.fasterxml.jackson.databind.ObjectReader._initForReading(ObjectReader.java:357) at com.fasterxml.jackson.databind.ObjectReader._bindAndClose(ObjectReader.java:1704) at com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:1261) at org.kohsuke.github.GitHubResponse.parseBody(GitHubResponse.java:85) at org.kohsuke.github.GitHubPageIterator.lambda$fetch$0(GitHubPageIterator.java:145) at org.kohsuke.github.GitHubClient.createResponse(GitHubClient.java:406) at org.kohsuke.github.GitHubClient.sendRequest(GitHubClient.java:360)Caused: org.kohsuke.github.HttpException: Server returned HTTP response code: 200, message: '304 Not Modified' for URL: [ https://github.xxx/api/v3/repos/xxx/contents/?ref=refs%2Fheads%2Fmaster ] at org.kohsuke.github.GitHubClient.interpretApiError(GitHubClient.java:445) Edit: I tried this but no luck [https://superuser.com/questions/1459241/jenkins-and-github-enterprise-2-17-failing-pull-request-builds-only]I made a commit on the repo (just changed a readme file) and it re-scanned and it worked.
Add Comment
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan commented on JENKINS-61955 Re: No valid crumb was included in the request Reverting Tomcat to 9.0.30 fixed the issue. Not sure about my Tomcat path forward at this point. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13480.1587168060123%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) createProject() and getItemsByFullName() handle nested folders inconsistently
Title: Message Title Calvin Park commented on JENKINS-61956 Re: createProject() and getItemsByFullName() handle nested folders inconsistently Thank you for checking. Thoughts on making createProject handle subfolders? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205840.1587161495000.13478.1587166740125%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) createProject() and getItemsByFullName() handle nested folders inconsistently
Title: Message Title
Daniel Beck commented on JENKINS-61956
Re: createProject() and getItemsByFullName() handle nested folders inconsistently
Is this a regression?
Tried it back to 1.620, a 5 years old release, doesn't work.
println Jenkins.instance.getItemByFullName("foo/bar")
Jenkins.instance.createProject(com.cloudbees.hudson.plugins.folder.Folder.class, "foo/bar")
println Jenkins.instance.getItemByFullName("foo/bar")
Output is
null
null
So no regression here for any sensible definition of the term. Nobody cares what happened >5 years ago.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Daniel Beck commented on JENKINS-61955 Re: No valid crumb was included in the request Yes the Reverse Proxy warning shows up. We disabled as a False Positive. What specifically does fail? Your web browser's network console should be able to show you the request that fails and the response will explain what's wrong. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13472.1587166020123%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan commented on JENKINS-61955 Re: No valid crumb was included in the request Yes the Reverse Proxy warning shows up. We disabled as a False Positive. CSRF has always been on. We do not have a reverse proxy but we are behind an F5 LTM and also use the SAML plugin to enable PIV authentication to the F5 APM module - not sure if any of that is in play here. Checking on timing of upgrades... Jenkins was upgraded first on 3/26 Tomcat was upgraded on 3/28 This is our Infrastructure Dev environment (not used by developers). Our prod environment is currently running Jenkins 2.222.1 and Tomcat 9.0.30 with no issues. We can make changes and save them. Prod also has same F5 LTM and SAML/PIV setup. I am scheduled to upgrade prod to 9.0.31 this weekend but I think I need to wait until this is resolved. I am going to revert to Tomcat 9.0.30 if for no other reason than to rule it out Also getting a random webpage error pop-up uploaded above Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13442.1587165720113%40Atlassian.JIRA.
[JIRA] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Title: Message Title John La Barge commented on JENKINS-5853 Re: Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key This feature is needed for me too. Enterprises do not allow access to pem files generally. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.135942.126782350.13427.1587165660682%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan updated an issue Jenkins / JENKINS-61955 No valid crumb was included in the request Change By: Kevin Sheehan Attachment: webpageerror.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13439.1587165660897%40Atlassian.JIRA.
[JIRA] (JENKINS-61924) json parsing error when fetching branches from github
Title: Message Title
Mike Erickson commented on JENKINS-61924
Re: json parsing error when fetching branches from github
I have the same problem for 1 repo (others work) Jenkins 2.232 git 4.2.2 git-client 3.2.1 git-server 1.9 github 1.29.5 github-api 1.111 github-branch-source 2.6.0 github-organization-folder 1.6 ERROR: [Fri Apr 17 15:03:39 PDT 2020] Could not fetch sources from navigator org.jenkinsci.plugins.github_branch_source.GitHubSCMNavigator@21f39e43 com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (StringReader); line: 1, column: 2] at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1840) at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:712) at com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:637) at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1916) at com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:772) at com.fasterxml.jackson.databind.ObjectReader._initForReading(ObjectReader.java:357) at com.fasterxml.jackson.databind.ObjectReader._bindAndClose(ObjectReader.java:1704) at com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:1261) at org.kohsuke.github.GitHubResponse.parseBody(GitHubResponse.java:85) at org.kohsuke.github.GitHubPageIterator.lambda$fetch$0(GitHubPageIterator.java:145) at org.kohsuke.github.GitHubClient.createResponse(GitHubClient.java:406) at org.kohsuke.github.GitHubClient.sendRequest(GitHubClient.java:360) Caused: org.kohsuke.github.HttpException: Server returned HTTP response code: 200, message: '304 Not Modified' for URL: https://github.xxx/api/v3/repos/xxx/contents/?ref=refs%2Fheads%2Fmaster at org.kohsuke.github.GitHubClient.interpretApiError(GitHubClient.java:445)
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61956) createProject() and getItemsByFullName() handle nested folders inconsistently
Title: Message Title Calvin Park commented on JENKINS-61956 Re: createProject() and getItemsByFullName() handle nested folders inconsistently Is this a regression? Our folder creation script had been working for a few years and now it fails with this problem. I'm not sure what changed since we rarely upgrade master Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205840.1587161495000.13422.1587164220189%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) createProject() and getItemsByFullName() handle nested folders inconsistently
Title: Message Title
Daniel Beck edited a comment on JENKINS-61956
Re: createProject() and getItemsByFullName() handle nested folders inconsistently
Looks like {{createProject}} is missing a call to {{Jenkins#checkGoodName}} but that's about it. While it would be more convenient to have a "createByFullName" that splits at the last {{/}}, finds the folder for the first part and inserts the item named the second part, that's a quick utility method.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205840.1587161495000.13419.1587163800134%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) createProject() and getItemsByFullName() handle nested folders inconsistently
Title: Message Title Daniel Beck commented on JENKINS-61956 Re: createProject() and getItemsByFullName() handle nested folders inconsistently Looks like createProject is missing a call to Jenkins#checkGoodName but that's about it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205840.1587161495000.13417.1587163740122%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan updated an issue Jenkins / JENKINS-61955 No valid crumb was included in the request Change By: Kevin Sheehan When saving anything, the No Valid Crumb error occurs. I can run jobs and browse without issue. Cannot modify a job or make save changes anywhere under Manage Jenkins.I am not calling an API - just using the UI. I am not behind a reverse proxy.I have recently upgraded Tomcat from 9.0.30 to 9.0.31.Tomcat configured for TLS on port 443 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13406.1587162300134%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Daniel Beck commented on JENKINS-61955 Re: No valid crumb was included in the request Is a reverse proxy warning shown to admins on /manage, or is the "Reverse Proxy Setup" monitor disabled in Configure System » Administrative Monitors Configuration? Was CSRF protection enabled before updating to Jenkins 2.222.1? Did it work before you updated Tomcat, and was that Jenkins 2.222.1 already, or did you do both at the same time? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13408.1587162300195%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) createProject() and getItemsByFullName() handle nested folders inconsistently
Title: Message Title
Calvin Park updated an issue
Jenkins / JENKINS-61956
createProject() and getItemsByFullName() handle nested folders inconsistently
Change By:
Calvin Park
{code:java}String nested = "one/two"// Creates a single folder named "one/two" with / embedded in the namecreateProject(Folder.class, nested)// Looks for a subfolder named "two" inside a folder named "one"getItemByFullName(nested){code}As a result, this code fails{code:java}import com.cloudbees.hudson.plugins.folder.FolderString folder = "nested/folders"create_folder_if_missing(folder)create_folder_if_missing(folder)void create_folder_if_missing(String folder) { def item = Jenkins.instance.getItemByFullName(folder) if (item == null) {println(folder + " not found. Creating.")Jenkins.instance.createProject(Folder.class, folder)println("Created " + folder) } else {println(folder + " found. Skipping.") }}{code}with the result{code:java}nested/folders not found. Creating.Created nested/foldersnested/folders not found. Creating.java.lang.IllegalArgumentException: nested/folders already exists at hudson.model.Items.verifyItemDoesNotAlreadyExist(Items.java:641){code}I think {{createProject(Folder.class, nested)}} should change its behavior to look for slashes and create subfolders, rather than allowing a slash in a folder name. At this point it's impossible to search for a folder with a slash in the name using {{getItemByFullName()}} function.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61956) createProject() and getItemsByFullName() handle nested folders inconsistently
Title: Message Title
Calvin Park created an issue
Jenkins / JENKINS-61956
createProject() and getItemsByFullName() handle nested folders inconsistently
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2020-04-17 22:11
Environment:
Jenkins 2.164.2 Folders plugin 6.9
Priority:
Minor
Reporter:
Calvin Park
String nested = "one/two"
// Creates a single folder named "one/two" with / embedded in the name
createProject(Folder.class, nested)
// Looks for a subfolder named "two" inside a folder named "one"
getItemByFullName(nested)
As a result, this code fails
import com.cloudbees.hudson.plugins.folder.Folder
String folder = "nested/folders"
create_folder_if_missing(folder)
create_folder_if_missing(folder)
void create_folder_if_missing(String folder) {
def item = Jenkins.instance.getItemByFullName(folder)
if (item == null) {
println(folder + " not found. Creating.")
Jenkins.instance.createProject(Folder.class, folder)
println("Created " + folder)
}
else {
println(folder + " found. Skipping.")
}
}
with the result
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan updated an issue Jenkins / JENKINS-61955 No valid crumb was included in the request Change By: Kevin Sheehan When saving anything, the No Valid Crumb error occurs. I can run jobs and browse without issue. Cannot modify a job or make save changes anywhere under Manage Jenkins.I am not calling an API - just using the UI. I am not behind a reverse proxy.I have recently upgraded Tomcat from 9.0.30 to 9.0.31. Tomcat configured for TLS on port 443 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13403.1587160860067%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan updated an issue Jenkins / JENKINS-61955 No valid crumb was included in the request Change By: Kevin Sheehan Attachment: response headers.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13402.1587160800312%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan updated an issue Jenkins / JENKINS-61955 No valid crumb was included in the request Change By: Kevin Sheehan Attachment: Request Headers.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13401.1587160800104%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan commented on JENKINS-61955 Re: No valid crumb was included in the request Tomcat stdout log: 17-Apr-2020 17:16:12.196 INFO [https-openssl-nio-443-exec-5] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:416) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan created an issue Jenkins / JENKINS-61955 No valid crumb was included in the request Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-17 21:07 Environment: Jenkins 2.222.1 Tomcat 9.0.31 Windows Server 2012R2 Priority: Major Reporter: Kevin Sheehan When saving anything, the No Valid Crumb error occurs. I can run jobs and browse without issue. Cannot modify a job or make save changes anywhere under Manage Jenkins. I am not calling an API - just using the UI. I am not behind a reverse proxy. I have recently upgraded Tomcat from 9.0.30 to 9.0.31. Add Comment
[JIRA] (JENKINS-61953) Build Blocker plugin - Validate regex does not work
Title: Message Title Len Isac updated an issue Jenkins / JENKINS-61953 Build Blocker plugin - Validate regex does not work Change By: Len Isac I have my regexes defined under 'Blocking Jobs'. When I try clicking on 'Validate regex' I see a quick pop saying "Checking" then it immediately disappears. !image-2020-04-17-15-59-06-607.png! Does this search for all jobs defined under $JENKINS_HOME/jobs? Or is it relative to the current job's directory? In any case, the above does not seem to work for me. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205835.158715346.13334.1587155520071%40Atlassian.JIRA.
[JIRA] (JENKINS-61954) /runs/ REST api failing to return after update to Jenkins 2.222.1
Title: Message Title Ryan Fenton-Garcia created an issue Jenkins / JENKINS-61954 /runs/ REST api failing to return after update to Jenkins 2.222.1 Issue Type: Bug Assignee: Rick Attachments: image-2020-04-17-14-30-14-354.png Components: pipeline-restful-api-plugin Created: 2020-04-17 20:30 Environment: Windows Server: 2016 Jenkins: 2.222.1 Labels: blueocean pipeline restFul REST Priority: Minor Reporter: Ryan Fenton-Garcia We have a web page we built that queries jenkins rest API's to populate some data. We used to get a list of the current running pull requests by going to the /runs/ page, but it seems like after updating to 2.222.1 that doesn't always work. More specifically, we used to access /runs/?start=0=85 which worked perfectly fine until upgrading. Now we have to use /runs/?start=0=50 or less to actually get a response back from the end point. It's also worth noting that accessing /runs/ without any parameters at all also doesn't even return. We can also see the ton of threads from these requests that basically build, never return, and look like they aren't doing anything.
[JIRA] (JENKINS-42940) Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet
Title: Message Title Devin Nusbaum started work on JENKINS-42940 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179951.1490019942000.13327.1587154440722%40Atlassian.JIRA.
[JIRA] (JENKINS-42940) Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet
Title: Message Title Devin Nusbaum commented on JENKINS-42940 Re: Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet This was also reported as JENKINS-61019. I reproduced it in a test and filed a PR to fix this in a way that still results in the body being cancelled, see jenkinsci/workflow-basic-steps-plugin#112. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179951.1490019942000.13323.1587154440664%40Atlassian.JIRA.
[JIRA] (JENKINS-42940) Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet
Title: Message Title Devin Nusbaum updated JENKINS-42940 Jenkins / JENKINS-42940 Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179951.1490019942000.13329.1587154440753%40Atlassian.JIRA.
[JIRA] (JENKINS-42940) Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-42940
Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet
Change By:
Devin Nusbaum
In case the timeout occurs, and Jenkins is restarted during the grace period if waits for the inner block to terminate, then the build hangs forever with this exception in the Jenkins log: Mär 10, 2017 3 {noformat}2020-03-13 02 : 49 09 : 10 PM org 40 . jenkinsci 575+ [id=1502] WARNING o . plugins j . workflow p . flow w . f. FlowExecutionList$ItemListenerImpl$1 # onFailure WARNUNG : Failed to load CpsFlowExecution[Owner[ hang devops-gate / 1 master/blackbox-self-service/25907 : hang devops-gate/master/blackbox-self-service # 1 25907 ]]java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel(TimeoutStepExecution.java: 94 151 ) at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.setupTimer(TimeoutStepExecution.java: 88 139 ) at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.onResume(TimeoutStepExecution.java: 57 90 ) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1.onSuccess(FlowExecutionList.java:185) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1.onSuccess(FlowExecutionList.java:180) ... {noformat} Reproducability of this issue relies on a block that does not immediately Exit. For example: {code} node \ {timeout (time: 10, unit: 'SECONDS') \ { build job: 'hang2', parameters: [ new StringParameterValue('A','B') ], quietPeriod: 0}} {code} with a second Pipeline Job hang2: {code} retry(3) \ { sleep 300} {code} Creates this console log: {noformat} Gestartet durch Benutzer RK[Pipeline] nodeRunning on host in /$JENKINS_HOME/workspace/hang[Pipeline] \ {[Pipeline] timeoutTimeout set to expire in 10 Sekunden[Pipeline] \ {[Pipeline] build (Building hang2)Scheduling project: hang2Starting building: hang2 #1Cancelling nested steps due to timeoutResuming build at Fri Mar 10 15:49:00 CET 2017 after Jenkins restartWaiting to resume hang #1|: ???Waiting to resume hang #1|: host ist offlineWaiting to resume hang #1|: host ist offlineReady to run at Fri Mar 10 15:49:10 CET 2017Timeout expired 3,7 Sekunden ago {noformat} ... and then it hangs forever.Reason: when onResume() is called, the timer is expired, so cancel() is called, and since it already tried to cancel, forcible is true, and then killer is null, causing an NPE.Fix: Check killer for null on line 94 in cancel() in TimeoutStepExecution().Rationale for Major, not minor bug: breaks restart resiliense.
[JIRA] (JENKINS-42940) Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-42940 Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179951.1490019942000.13313.1587154020706%40Atlassian.JIRA.
[JIRA] (JENKINS-61019) java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-61019 java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel Change By: Devin Nusbaum Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204490.1581107937000.13304.1587154020600%40Atlassian.JIRA.
[JIRA] (JENKINS-42940) Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-42940 Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet Change By: Devin Nusbaum Summary: [fix included] Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179951.1490019942000.13311.1587154020686%40Atlassian.JIRA.
[JIRA] (JENKINS-60769) Cannot Install Recommended Plugins and Updates Give 503 Error
Title: Message Title sri saladi commented on JENKINS-60769 Re: Cannot Install Recommended Plugins and Updates Give 503 Error Hi Is there a solution for this? Can jenkins plugin install be customized to retry? This issue is blocking from updating plugins. The only turn-around which is taking lot of time is to manually download and upload to plugin folder and restart jenkins but with so many dependencies, its a time taking job. Any help would be appreciated Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204030.157902723.13307.1587154020636%40Atlassian.JIRA.
[JIRA] (JENKINS-61019) java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel
Title: Message Title Devin Nusbaum closed an issue as Duplicate Thanks for the report! I'm going to close this as a duplicate of JENKINS-42940, which is the same issue, but I have a PR on the way to fix it. Jenkins / JENKINS-61019 java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel Change By: Devin Nusbaum Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-61953) Build Blocker plugin - Validate regex does not work
Title: Message Title Len Isac updated an issue Jenkins / JENKINS-61953 Build Blocker plugin - Validate regex does not work Change By: Len Isac Attachment: image-2020-04-17-15-59-06-607.png Attachment: image-2020-04-17-15-58-59-876.png I have my regexes defined under 'Blocking Jobs'. When I try clicking on 'Validate regex' I see a quick pop saying "Checking" then it immediately disappears. The block doesn't appear to be working for me though !image-2020-04-17-15-59-06-607 . png! I'm using just:.*.* Does it this search for all jobs defined under $JENKINS_HOME/jobs? Or is it relative to the current job's directory? In any case, the above does not seem to work for me. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61953) Build Blocker plugin - Validate regex does not work
Title: Message Title Len Isac created an issue Jenkins / JENKINS-61953 Build Blocker plugin - Validate regex does not work Issue Type: Bug Assignee: Unassigned Components: build-blocker-plugin Created: 2020-04-17 19:57 Priority: Minor Reporter: Len Isac I have my regexes defined under 'Blocking Jobs'. When I try clicking on 'Validate regex' I see a quick pop saying "Checking" then it immediately disappears. The block doesn't appear to be working for me though. I'm using just: .. Does it search for all jobs defined under $JENKINS_HOME/jobs? Or is it relative to the current job's directory? In any case, the above does not seem to work for me. Add Comment
[JIRA] (JENKINS-61575) Method is no longer whitelisted
Title: Message Title Devin Nusbaum commented on JENKINS-61575 Re: Method is no longer whitelisted I filed INFRA-2581 to remove all of the duplicates. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205272.1584622708000.13296.1587151500601%40Atlassian.JIRA.
[JIRA] (JENKINS-61584) Method java.util.regex.Matcher find is no longer whitelisted
Title: Message Title Devin Nusbaum commented on JENKINS-61584 Re: Method java.util.regex.Matcher find is no longer whitelisted I filed INFRA-2581 to remove all of the duplicates. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205281.158462305.13294.1587151500578%40Atlassian.JIRA.
[JIRA] (JENKINS-61952) Matcher.find() and Matcher.group(String) are no longer whitelisted
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-61952 Matcher.find() and Matcher.group(String) are no longer whitelisted Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205833.1587150538000.13286.1587151020177%40Atlassian.JIRA.
[JIRA] (JENKINS-61952) Matcher.find() and Matcher.group(String) are no longer whitelisted
Title: Message Title Devin Nusbaum started work on JENKINS-61952 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205833.1587150538000.13287.1587151020294%40Atlassian.JIRA.
[JIRA] (JENKINS-61952) Matcher.find() and Matcher.group(String) are no longer whitelisted
Title: Message Title Devin Nusbaum updated JENKINS-61952 Jenkins / JENKINS-61952 Matcher.find() and Matcher.group(String) are no longer whitelisted Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205833.1587150538000.13288.1587151020306%40Atlassian.JIRA.
[JIRA] (JENKINS-61584) Method java.util.regex.Matcher find is no longer whitelisted
Title: Message Title Devin Nusbaum commented on JENKINS-61584 Re: Method java.util.regex.Matcher find is no longer whitelisted Reinhold Füreder I think this usually happens when Jira is having problems when someone tries to submit an issue, for some reason the status of all the tickets is broken and only an admin can fix them. I will file an INFRA ticket to ask an admin to delete all of them. I cloned them into JENKINS-61952 as a new issue which does not have a broken status. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205281.158462305.13284.1587150900172%40Atlassian.JIRA.
[JIRA] (JENKINS-61952) Matcher.find() and Matcher.group(String) are no longer whitelisted
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-61952
Matcher.find() and Matcher.group(String) are no longer whitelisted
Change By:
Devin Nusbaum
Originally reported by [~wolniewicz] in JENKINS-61575, but that issue appears to be broken so I cloned it here. We have upgraded the plugin from 1.66 -> 1.68 Since version 1.68 method java.util.regex.Matcher find is not longer whitelisted:[https://github.com/jenkinsci/script-security-plugin/commit/d5e107b1bd780314bc13ebed401ab3b8a22ec9a4#diff-bd6a93804fc62863a4d7460e35733302]Was this made on purpose or all mentioned methods were removed by accident?{code:java}method java.util.regex.Matcher findmethod java.util.regex.Matcher group java.lang.String{code} We had to manually approve mentioned methods on our production servers.Could you please add mentioned methods to default approve list?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-61952) Matcher.find() and Matcher.group(String) are no longer whitelisted
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-61952 Matcher.find() and Matcher.group(String) are no longer whitelisted Issue Type: Bug Assignee: Unassigned Components: script-security-plugin Created: 2020-04-17 19:08 Environment: Jenkins ver. 2.204.2 script-security-plugin 1.68 Priority: Minor Reporter: Devin Nusbaum We have upgraded the plugin from 1.66 -> 1.68 Since version 1.68 method java.util.regex.Matcher find is not longer whitelisted: https://github.com/jenkinsci/script-security-plugin/commit/d5e107b1bd780314bc13ebed401ab3b8a22ec9a4#diff-bd6a93804fc62863a4d7460e35733302 Was this made on purpose or all mentioned methods were removed by accident? method java.util.regex.Matcher find method java.util.regex.Matcher group java.lang.String We had to manually approve mentioned methods on our production servers. Could you please add mentioned methods to default approve list?
[JIRA] (JENKINS-61575) Method is no longer whitelisted
Title: Message Title Devin Nusbaum commented on JENKINS-61575 Re: Method is no longer whitelisted I think this was an accident. It looks like this issue has a bunch of dupes, maybe it was filed while Jira was having an issue or something, so I cannot change the status. I am going to clone this issue and ask an admin to clone this issue and the duplicates. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205272.1584622708000.13279.1587150480261%40Atlassian.JIRA.
[JIRA] (JENKINS-61592) Enable auto refresh button os missing
Title: Message Title Daniel Beck commented on JENKINS-61592 Re: Enable auto refresh button os missing Erwin Dondorp The former, over the long term we want to get to the latter. Implementation-wise it's always been a mess, and the option wasn't used all that much. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205289.1584636825000.13275.1587150300290%40Atlassian.JIRA.
[JIRA] (JENKINS-61592) Enable auto refresh button os missing
Title: Message Title Erwin Dondorp commented on JENKINS-61592 Re: Enable auto refresh button os missing Daniel Beck Was the function removed because the refresh-function from the browser should be used instead, or that Jenkins now always keeps is screens up-to-date? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205289.1584636825000.13269.1587149940363%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title Baptiste Mathus updated JENKINS-61854 Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Released As: ldap plugin 1.23 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.13255.1587146820778%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title Baptiste Mathus commented on JENKINS-61854 Re: "Test Ldap Settings" button stopped functioning. Phaneendra Nagaruru William Gillaspy thanks for the report. It has been fixed and just released in version 1.23. Could you please check and confirm it does fix the issue for you? Thanks again. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.13249.1587146820678%40Atlassian.JIRA.
[JIRA] (JENKINS-61951) build.bat' is not recognized as an internal or external command, operable program or batch file.
Title: Message Title
Narayanasamy Ramaiah edited a comment on JENKINS-61951
Re: build.bat' is not recognized as an internal or external command, operable program or batch file.
stage('Parallel Regression') { buildnumber = buildno()generateAndUnzipTAFBuild ={ ws("$codeBase/16.5.1") { bat "d2unitybuild.bat" }}commonCode ={ generateAndUnzipTAFBuild() } node(' 16.5PatchNode1 node1 ') { commonCode Stories }}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205832.158714518.13246.1587145620219%40Atlassian.JIRA.
[JIRA] (JENKINS-61951) build.bat' is not recognized as an internal or external command, operable program or batch file.
Title: Message Title
Narayanasamy Ramaiah edited a comment on JENKINS-61951
Re: build.bat' is not recognized as an internal or external command, operable program or batch file.
stage('Parallel Regression') { stage('Parallel Regression') { buildnumber = buildno()generateAndUnzipTAFBuild ={ ws("$codeBase/16.5.1") { bat "d2unitybuild.bat" } } commonCode = { { generateAndUnzipTAFBuild() } node('16.5PatchNode1') { commonCode Stories } }
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205832.158714518.13244.1587145620188%40Atlassian.JIRA.
[JIRA] (JENKINS-61951) build.bat' is not recognized as an internal or external command, operable program or batch file.
Title: Message Title
Narayanasamy Ramaiah commented on JENKINS-61951
Re: build.bat' is not recognized as an internal or external command, operable program or batch file.
stage('Parallel Regression') {stage('Parallel Regression') { buildnumber = buildno() generateAndUnzipTAFBuild = { ws("$codeBase/16.5.1") { bat "d2unitybuild.bat" } } commonCode = { generateAndUnzipTAFBuild() } node('16.5PatchNode1') { commonCode Stories } }
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205832.158714518.13242.1587145440117%40Atlassian.JIRA.
[JIRA] (JENKINS-61951) build.bat' is not recognized as an internal or external command, operable program or batch file.
Title: Message Title Narayanasamy Ramaiah created an issue Jenkins / JENKINS-61951 build.bat' is not recognized as an internal or external command, operable program or batch file. Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: image-2020-04-17-23-05-07-256.png Components: batch-task-plugin, pipeline Created: 2020-04-17 17:39 Environment: Jenkins ver. 2.190.1 Priority: Blocker Reporter: Narayanasamy Ramaiah unable to run the bat file from pipeline in slave node- in few nodes its working and in few nodes it doesnt build.bat' is not recognized as an internal or external command, operable program or batch file. Add Comment
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title
David Rodriguez edited a comment on JENKINS-61943
Re: Jenkins2, P4 Plugin: Error must create client ' to access local files
Hi Karl, I really appreciate the quick response to my issue. What I'm attempting to do is test upgrading our Jenkins1 (v1.651.2) environment to Jenkins2 (v2.222.1) before upgrading our production jenkin server and slaves. I was hoping that the upgrade was simply allowing the new p4@1.10.12 plugin manage the necessary scm class changes to create the p4 client to run the job without having to make additional changes. Note that we are NOT using P4Maven for our Perforce jobs.{color:#de350b} {color:#172b4d} Below is a snippet from the jenkins1 job config.xml versus the jenkins2 job config.xml after the upgrade. Note that the jenkins1 job.xml specifies the p4client and the jenkins2 job.xml does NOT . Is there a reason for that? I also attached the jenkins1 job config.xml and build log before the upgrade for your review.{color} {color} {color:#00875a} Snippet from the jenkins1 job config.xml 'scm class' for plugin="perforce@1.3.35" *BEFORE the upgrade.*The scm class specifies the tag {color:#de350b} {color} ci-admin-ui-4.2{color:#de350b} .{color} {color} {code:java} 2compil0f0kqlwaRgSE9uduYTPfa3AlrK8xqw==p4proxy:1667--> ci-admin-ui-4.2//depot/kernel/04.02/wars/admin-ui/... //ci-admin-ui-4.2/...noallwrite clobber nocompress unlocked nomodtime rmdir2012.2falsefalsefalsetruefalsefalsefalsefalsefalsefalsetruetruefalsefalsefalsetruefalsefalsefalsefalse-10true${basename}-${hash}localfalsetruefalsefalsefalse {code} {color:#00875a} Below is a snippet from the jenkins2 job config.xml 'scm class' plugin="p4@1.10.12" *AFTER the upgrade*The new scm class does *NOT* specify the {color:#de350b} {color} ** {color} {code:java} p4-userpass none true false jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER} falsetruefalsefalsefalsefalseLOCAL//depot/kernel/04.02/wars/admin-ui/... //${P4_CLIENT}/...WRITABLEtruetrue false false truefalse411024true true false {code}
Add Comment
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title
David Rodriguez commented on JENKINS-61943
Re: Jenkins2, P4 Plugin: Error must create client ' to access local files
Hi Karl, I really appreciate the quick response to my issue. What I'm attempting to do is test upgrading our Jenkins1 (v1.651.2) environment to Jenkins2 (v2.222.1) before upgrading our production jenkin server and slaves. I was hoping that the upgrade was simply allowing the new p4@1.10.12 plugin manage the necessary scm class changes to create the p4 client to run the job without having to make additional changes. Note that we are NOT using P4Maven for our Perforce jobs. Below is a snippet from the jenkins1 job config.xml versus the jenkins2 job config.xml after the upgrade. Note that the jenkins1 job.xml specifies the p4client and the jenkins2 job.xml does NOT . Is there a reason for that? I also attached the jenkins1 job config.xml and build log before the upgrade for your review. Snippet from the jenkins1 job config.xml 'scm class' for plugin="perforce@1.3.35" BEFORE the upgrade. The scm class specifies the tag ci-admin-ui-4.2 .
"hudson.plugins.perforce.PerforceSCM" plugin="perforce@1.3.35">
2
compil
0f0kqlwaRgSE9uduYTPfa3AlrK8xqw==
p4proxy:1667
--> ci-admin-ui-4.2
//depot/kernel/04.02/wars/admin-ui/... //ci-admin-ui-4.2/...
noallwrite clobber nocompress unlocked nomodtime rmdir
2012.2
false
false
false
true
false
false
false
false
false
false
true
true
false
false
false
true
false
false
false
false
-1
0
true
${basename}-${hash}
local
false
true
false
false
false
Below is a snippet from the jenkins2 job config.xml 'scm class' plugin="p4@1.10.12" AFTER the upgrade The new scm class does NOT specify the **
"org.jenkinsci.plugins.p4.PerforceScm" plugin="p4@1.10.12">
p4-userpass
"org.jenkinsci.plugins.p4.workspace.ManualWorkspaceImpl">
none
true
false
jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}
false
true
false
false
false
false
LOCAL
//depot/kernel/04.02/wars/admin-ui/... //${P4_CLIENT}/...
WRITABLE
true
"org.jenkinsci.plugins.p4.populate.AutoCleanImpl">
true
false
false
true
false
4
1
1024
true
true
false
[JIRA] (JENKINS-58729) Extended security settings plugin cannot be configured
Title: Message Title Matt Sicker closed an issue as Fixed Jenkins / JENKINS-58729 Extended security settings plugin cannot be configured Change By: Matt Sicker Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201024.1564489867000.13215.1587141540179%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) Allow version HTTP header to be hidden
Title: Message Title Matt Sicker closed an issue as Fixed Jenkins / JENKINS-56217 Allow version HTTP header to be hidden Change By: Matt Sicker Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.13210.1587141420498%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: David Rodriguez Attachment: jenkins-1.651.2-job-config.xml Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.13208.1587140220284%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: David Rodriguez Attachment: jenkins-1.651.2-job-config.xml Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.13206.1587140220255%40Atlassian.JIRA.
[JIRA] (JENKINS-59056) Report displays raw HTML if CDATA terms are used
Title: Message Title Ioannis Moutsatsos commented on JENKINS-59056 Re: Report displays raw HTML if CDATA terms are used Adam Olejar you can apply the setting at the command used to startup Jenkins. This is what my command line looks like: java -Xrs -Xmx2048m -XX:MaxPermSize=512m -Dhudson.model.DirectoryBrowserSupport.CSP= -Dorg.kohsuke.stapler.jelly.CustomJellyContext.escapeByDefault="false" -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "path/to/jenkins/jenkins.war" --httpPort=8080 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201412.1566489784000.13204.1587139920203%40Atlassian.JIRA.
[JIRA] (JENKINS-61950) Environment variables with '$' have '$$' when used in sh step inside a container step.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61950 Environment variables with '$' have '$$' when used in sh step inside a container step. Change By: Jesse Glick Labels: kubernetes-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205830.1587134969000.13202.1587138120157%40Atlassian.JIRA.
[JIRA] (JENKINS-61938) Can aws-secrets-manager-credentials-provider-plugin be configured to use a credential binding for authentication?
Title: Message Title Chris Kilding edited a comment on JENKINS-61938 Re: Can aws-secrets-manager-credentials-provider-plugin be configured to use a credential binding for authentication? I have looked at having the plugin depend on the AWS Global Configuration plugin, which allows an AWS key pair credential to be selected in the Jenkins UI.This would be the most appropriate place to get the AWS credential from, as the user would only have to specify it once for all their AWS-using plugins. Unfortunately it needs a good cleanup to make it more generic (I think it was extracted from the S3 plugin, and this shows), before I could use it as a dependency. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205818.1587074068000.13197.1587137760103%40Atlassian.JIRA.
[JIRA] (JENKINS-61938) Can aws-secrets-manager-credentials-provider-plugin be configured to use a credential binding for authentication?
Title: Message Title Chris Kilding commented on JENKINS-61938 Re: Can aws-secrets-manager-credentials-provider-plugin be configured to use a credential binding for authentication? I have looked at having the plugin depend on the AWS Global Configuration plugin, which allows an AWS key pair credential to be selected in the Jenkins UI. Unfortunately it needs a good cleanup to make it more generic (I think it was extracted from the S3 plugin, and this shows), before I could use it as a dependency. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205818.1587074068000.13195.1587137700123%40Atlassian.JIRA.
[JIRA] (JENKINS-61938) Can aws-secrets-manager-credentials-provider-plugin be configured to use a credential binding for authentication?
Title: Message Title Chris Kilding commented on JENKINS-61938 Re: Can aws-secrets-manager-credentials-provider-plugin be configured to use a credential binding for authentication? Hi red, The plugin is designed the way it is because most Jenkins installations will be in the same AWS account as their secrets, and because moving Jenkins further from the secrets imposes steep costs. It will be most secure if it authenticates using IAM instance profiles (EC2) or fine-grained service roles (EKS), and it will be most reliable if it can access Secrets Manager within Amazon's internal network, so both these things are encouraged. When Jenkins is run in a different cloud from Secrets Manager, the costs become apparent: Jenkins can't use IAM instance profiles, so you must provision an AWS access key pair for Jenkins, and then guard that key pair closely, because if it is stolen then the attacker can access every secret that Jenkins can access. Jenkins can't access Secrets Manager through Amazon's network, so its Secrets Manager connection is at the mercy of the public Internet. You can improve this somewhat by establishing an AWS PrivateLink between Jenkins and Secrets Manager, but it still won't be as good. No code in this plugin can solve the data locality problem, as it arises from your cloud architecture, and can only be properly addressed by altering your cloud architecture. So before going the multi-cloud route, consider if you can: Co-locate CJOC with the secrets (move CJOC to EC2 or EKS). Co-locate the secrets with CJOC (move the secrets that CJOC needs to Google Cloud; this will only work if CJOC is the only user of those secrets). If none of the above options work then you will need to use the "escape hatch" of passing the AWS key pair to the CJOC container through environment variables or system properties. Add Comment
[JIRA] (JENKINS-61939) Duplicate warnings not eliminated/combined
Title: Message Title Timothy Brackett commented on JENKINS-61939 Re: Duplicate warnings not eliminated/combined Working on it. Problem encountered in a proprietary code base. Attempted minimal example correctly combined the one issue found twice, but in our code base I’m seeing issues repeated up to 12 times. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205819.1587074798000.13187.1587135720141%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title Basil Crow updated JENKINS-61843 Released in Timestamper 1.11.3. Jenkins / JENKINS-61843 Timestamp missing for trailing lines in view as plain text mode. Change By: Basil Crow Status: Fixed but Unreleased Resolved Released As: 1.11.3 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61950) Environment variables with '$' have '$$' when used in sh step inside a container step.
Title: Message Title
Kenneth Rogers created an issue
Jenkins / JENKINS-61950
Environment variables with '$' have '$$' when used in sh step inside a container step.
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2020-04-17 14:49
Environment:
CloudBees Core 2.222.1.1, Kubernetes plugin 1.25.2
Labels:
kubernetes-plugin
Priority:
Minor
Reporter:
Kenneth Rogers
Here's a pipeline that reproduces the bug:
podTemplate {
node(POD_LABEL) {
container("jnlp") {
stage("Run") {
env.FOO = '$string\$with\$dollars'
echo "from groovy: ${env.FOO}"
sh 'env | grep FOO'
sh 'echo from sh: $FOO'
}
}
}
}
Here's the output: from groovy: $string$with$dollars FOO=$$string$$with$$dollars from sh: $$string$$with$$dollars Note that all the dollar signs have been doubled! Note that we've included a call to env, which prints the same incorrect string, so that we can eliminate the possibility of groovy string interpolation issues. We isolated the problem to the container() function. The bug does not occur with this version of the code, where it is removed, despite that the exact same container (jnlp) is actually used:
[JIRA] (JENKINS-61340) Cannot launch windows pods
Title: Message Title Jesse Glick updated JENKINS-61340 Jenkins / JENKINS-61340 Cannot launch windows pods Change By: Jesse Glick Resolution: Fixed Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204921.1583349755000.13178.1587133020842%40Atlassian.JIRA.
[JIRA] (JENKINS-61340) Cannot launch windows pods
Title: Message Title Jesse Glick resolved as Not A Defect Jenkins / JENKINS-61340 Cannot launch windows pods Change By: Jesse Glick Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204921.1583349755000.13180.1587133020902%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Alan Wong updated an issue Jenkins / JENKINS-61949 Configuration of action triggers in an Organization folder Change By: Alan Wong Recently, we have been able to setup handling of infrastructure teardowns by using the Pipeline Delete Event in this plugin with a multi-branch project. Unfortunately, now that we are looking to switch to an organization folder for automatic multi-branch project initialization, we have lost the ability to configure this plugin for child multi-branch projects.Specifically, the GitHub Organization project does not have options for action triggers, and the child multi-branch projects that it creates do not allow us to further configure actions independently.Could this feature be added? As a side issue, due to automating this across many repositories, it might be useful for the action triggers to be programmatically determined somehow (perhaps within the Jenkinsfile itself) rather than statically configured. Or if not possible, maybe allow running against a branch of the repository that triggered the action? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Alan Wong created an issue Jenkins / JENKINS-61949 Configuration of action triggers in an Organization folder Issue Type: New Feature Assignee: Aytunc BEKEN Components: multibranch-action-triggers-plugin Created: 2020-04-17 13:56 Priority: Minor Reporter: Alan Wong Recently, we have been able to setup handling of infrastructure teardowns by using the Pipeline Delete Event in this plugin with a multi-branch project. Unfortunately, now that we are looking to switch to an organization folder for automatic multi-branch project initialization, we have lost the ability to configure this plugin for child multi-branch projects. Specifically, the GitHub Organization project does not have options for action triggers, and the child multi-branch projects that it creates do not allow us to further configure actions independently. Could this feature be added? As a side issue, due to automating this across many repositories, it might be useful for the action triggers to be programmatically determined somehow (perhaps within the Jenkinsfile itself) rather than statically configured. Add Comment
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe updated JENKINS-61930 Jenkins / JENKINS-61930 Config as Code official compatibility Change By: Vincent Latombe Status: Fixed but Unreleased Resolved Released As: kubernetes 1.25.3 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.13166.1587131160368%40Atlassian.JIRA.
[JIRA] (JENKINS-61948) SSH Remote not Populated on Manual Build
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-61948 SSH Remote not Populated on Manual Build Issue Type: Bug Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-04-17 13:45 Priority: Minor Reporter: Mark Bidewell When a build is triggered by a webhook, the git remote origin is set to the ssh url for the project. However on a manual build only the http link is included. This makes interacting with the git repo from a manual job difficult. Add Comment
[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title Riccardo Boettcher edited a comment on JENKINS-59971 Re: Unable to create folder credentials for plain-credentials-plugin Hi Daniel Spilker,I have tried to find a solution for the issue. Please have a look here [https://github.com/RiccardoBoettcher/plain-credentials-plugin/tree/JENKINS-59971]As I'm not experienced with the Jenkins plugin development yet, I don't know what is the best strategy to introduce a breaking change. May be someone can assist me with that? As visible in the screenshot, the change makes a basicStringCredential (a functional equivalent implementation of the existing StringCredentialImpl) available in the JobDSL API browser.!image-2020-04-17-15-02-22-034.png! But, this draft has still some missing parts:* when creating new credentials via the WebUI it can not be distinguished from the existing implementation for "secret text"* when selecting it as the type of a new credentials no properties are shown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202775.1572343204000.13157.1587129000251%40Atlassian.JIRA.
[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title Riccardo Boettcher edited a comment on JENKINS-59971 Re: Unable to create folder credentials for plain-credentials-plugin Hi Daniel Spilker,I have tried to find a solution for the issue. Please have a look here [https://github.com/RiccardoBoettcher/plain-credentials-plugin/tree/JENKINS-59971]As I'm not experienced with the Jenkins plugin development yet, I don't know what is the best strategy to introduce a breaking change. May be some someone can assist me with that? As visible in the screenshot, the change makes the a basicStringCredential (a functional equivalent implementation of the existing StringCredentialImpl) available in the JobDSL API browser.!image-2020-04-17-15-02-22-034.png! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202775.1572343204000.13150.1587128700284%40Atlassian.JIRA.
[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title Riccardo Boettcher edited a comment on JENKINS-59971 Re: Unable to create folder credentials for plain-credentials-plugin Hi Daniel Spilker,I have tried to find a solution for the issue. Please have a look here [https://github.com/RiccardoBoettcher/plain-credentials-plugin/tree/JENKINS-59971]As I'm not experienced with the Jenkins plugin development yet, I don't know what is the best strategy to introduce a breaking change. May be some can assist me with that? As visible in the screenshot, the change makes the basicStringCredential available in the JobDSL API browser.!image-2020-04-17-15-02-22-034.png! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202775.1572343204000.13147.1587128580348%40Atlassian.JIRA.
[JIRA] (JENKINS-61371) API tokens not persisted until user config screen is saved
Title: Message Title Jesse Glick commented on JENKINS-61371 Re: API tokens not persisted until user config screen is saved FTR: https://feedback.cloudbees.com/app/#/case/20344 https://feedback.cloudbees.com/app/#/case/23357 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205024.1583509348000.13137.1587128460188%40Atlassian.JIRA.
[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title Riccardo Boettcher commented on JENKINS-59971 Re: Unable to create folder credentials for plain-credentials-plugin Hi Daniel Spilker, I have tried to find a solution for the issue. Please have a look here https://github.com/RiccardoBoettcher/plain-credentials-plugin/tree/JENKINS-59971 As I'm not experienced with the Jenkins plugin development yet, I don't know what is the best strategy to introduce a breaking change. May be some can assist me with that? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202775.1572343204000.13131.1587128400326%40Atlassian.JIRA.
[JIRA] (JENKINS-49073) build job propagate true propagates FAIL when state is UNSTABLE
Title: Message Title Philipp Jung commented on JENKINS-49073 Re: build job propagate true propagates FAIL when state is UNSTABLE Thanks for clearing that up. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187899.1516619705000.13112.1587126180312%40Atlassian.JIRA.
[JIRA] (JENKINS-60773) Milestone aborting old builds before passing next milestone
Title: Message Title Kai Kunstmann commented on JENKINS-60773 Re: Milestone aborting old builds before passing next milestone This Issue should better be titled: "Cancelling a build should not abort older builds in sight of the same milestone". I'm having the same problem as the reporting user. I have setup a build-pipeline that waits for user approvals before deploying my application to my QA, STAGING and PRODUCTION environments, respectively. The situation is this: There are multiple builds waiting for an approval to deploy to STAGING, so all of them are currently in sight of the same previous milestone (e.g. "deployed to QA"). I abort the newest build, because it didn't pass quality requirements on QA, and should never be deployed to STAGING, but I wish for older builds at the same input-step to continue waiting for approval to deploy to STAGING. The bad build gets cancelled as expected, but the milestone plugin subsequently performs some clean-up including aborting all other builds in sight of the same milestone (namely "deployed to QA"). This is not the expected behavior, because the just cancelled build did not progress to the next milestone in order to be allowed to abort its siblings. I believe, this behaviour is due to this: https://github.com/jenkinsci/pipeline-milestone-step-plugin/blob/ab24d126caaad2c507ec0d26b7cb87d314e1f296/src/main/java/org/jenkinsci/plugins/pipeline/milestone/MilestoneStepExecution.java#L189 Which is only ever executed from here: https://github.com/jenkinsci/pipeline-milestone-step-plugin/blob/ab24d126caaad2c507ec0d26b7cb87d314e1f296/src/main/java/org/jenkinsci/plugins/pipeline/milestone/MilestoneStepExecution.java#L330 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-30106) Integration with Dimensions
Title: Message Title David Conneely commented on JENKINS-30106 Re: Integration with Dimensions The dimensionsscm-plugin for Jenkins (Jenkins Dimensions Plugin) can be used to integrate Jenkins with Dimensions CM. You can install the plugin using the Plugin Manager in Jenkins - look for 'Dimensions' in the Available plugins tab, and follow the instructions at https://plugins.jenkins.io/dimensionsscm/ This particular issue/solution is the resolution to a particular issue that an individual user of that plugin had with its usage. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164687.1440420609000.13088.1587119760151%40Atlassian.JIRA.
[JIRA] (JENKINS-61947) To make Jenkins support higher versions of java by using java's backward compatibility feature.
Title: Message Title Manoj Kumar Venkatesan created an issue Jenkins / JENKINS-61947 To make Jenkins support higher versions of java by using java's backward compatibility feature. Issue Type: New Feature Assignee: Karl-Heinz Marbaise Attachments: image-2020-04-17-15-45-37-329.png Components: java-client-api Created: 2020-04-17 10:20 Environment: Windows 10 Priority: Minor Reporter: Manoj Kumar Venkatesan The existing Jenkins version is not supporting JDK 12 or above. Getting an error as mentioned in the below screenshot Add Comment
[JIRA] (JENKINS-61885) setting the system property hudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO to true is no use to disable csrf
Title: Message Title Daniel Beck closed an issue as Not A Defect The security fix is unrelated to the now forced enablement of CSRF protection. For the latter, see https://jenkins.io/doc/upgrade-guide/2.222/#always-enabled-csrf-protection As the documentation indicates, this option will go away in the future. If you rely on it, make sure all components that rely on CSRF protection being disabled adapt to work with it enabled. Jenkins / JENKINS-61885 setting the system property hudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO to true is no use to disable csrf Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61940) Show multiple source files and all line ranges in source code view
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61940 Show multiple source files and all line ranges in source code view Change By: Ulli Hafner Epic Name: Generic Warning Locations Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205820.1587075095000.13081.1587118320296%40Atlassian.JIRA.
[JIRA] (JENKINS-61946) Replace LineRange with Location
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61946 Replace LineRange with Location Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-model Created: 2020-04-17 10:10 Priority: Major Reporter: Ulli Hafner Currently, issues refer to a line, a line range, or multiple line ranges in a single file. It would make sense to extend this concept so that issues refer to multiple locations, that may span multiple files. One parser that already supports that concept is the CPPCheck. Multiple files are currently ignored. The Gcc parser could be extended as well. Add Comment
[JIRA] (JENKINS-61940) Show multiple source files and all line ranges in source code view
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61940 Show multiple source files and all line ranges in source code view Change By: Ulli Hafner Issue Type: Improvement Epic Component/s: analysis-model Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205820.1587075095000.13070.1587117960396%40Atlassian.JIRA.
[JIRA] (JENKINS-60394) Can't load http://localhost:8080
Title: Message Title Manoj Kumar Venkatesan commented on JENKINS-60394 Re: Can't load http://localhost:8080 Hi Martino Holus and I am a new user to Jenkins and using the admin user and default password provided after Jenkins installation. In the initial stage, I was able to do operations with Jenkins using the default admin user. I configured java 12 and Gradle in Jenkins and even tried running Gradle build thrice. It worked well. But suddenly yesterday when I tried to launch Jenkins using http://localhost:8080 I came up with the same issue Could you please let me know the resolution of this issue. If you would have possibly came up with the solution Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203448.1575669122000.13064.1587117540198%40Atlassian.JIRA.
[JIRA] (JENKINS-61939) Duplicate warnings not eliminated/combined
Title: Message Title Ulli Hafner commented on JENKINS-61939 Re: Duplicate warnings not eliminated/combined Can you please provide an example? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205819.1587074798000.13061.1587117360828%40Atlassian.JIRA.
[JIRA] (JENKINS-60394) Can't load http://localhost:8080
Title: Message Title Manoj Kumar Venkatesan updated an issue Jenkins / JENKINS-60394 Can't load http://localhost:8080 Change By: Manoj Kumar Venkatesan Attachment: image-2020-04-17-15-25-38-741.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203448.1575669122000.13059.1587117360788%40Atlassian.JIRA.
[JIRA] (JENKINS-60394) Can't load http://localhost:8080
Title: Message Title Manoj Kumar Venkatesan updated an issue Jenkins / JENKINS-60394 Can't load http://localhost:8080 Change By: Manoj Kumar Venkatesan Attachment: image-2020-04-17-15-24-30-721.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203448.1575669122000.13052.1587117300244%40Atlassian.JIRA.
[JIRA] (JENKINS-42358) Internationalize creation strings
Title: Message Title Shubham Wani started work on JENKINS-42358 Change By: Shubham Wani Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179258.1488234477000.13049.1587115260213%40Atlassian.JIRA.
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm edited a comment on JENKINS-61850
Re: TFS pull request verification build uses wrong branch
Strangely, the build succeeds when the commit to be merged has been committed in the TFS Git repository itself. When the change is pushed into the TFS Git repository from a clone using a different user name and e-mail address, the pull request verification build fails as described above. Once user.name and user.email on the clone are set to be identical to the TFS Git repository, the pull request verification build after the push succeeds. This seems really strange!Another thing is that the build fails if it is triggered by a TFS branch policy validation build:{noformat}Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/verification-build@script to read Jenkinsfileusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git > git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pull/* # timeout=10skipping resolution of commit 03420e8348cfad32cb7916e537a83b4654fbce9b, since it originates from another repository > git rev-parse refs/remotes/origin/merge^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/merge^{commit} # timeout=10 > git rev-parse origin/merge^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.ERROR: Maximum checkout retry attempts reached, abortingFinished: FAILURE{noformat}However, it succeeds when it is triggered by a Jenkins Service Hook in TFS but it fails if it :{noformat}Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/verification-build@script to read Jenkinsfileusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse -- is -inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git > git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pull/* # timeout=10 > git rev-parse c607f67f5388726e9b8aa8f04768214e8f5ba5c4^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains c607f67f5388726e9b8aa8f04768214e8f5ba5c4 # timeout=10Checking out Revision c607f67f5388726e9b8aa8f04768214e8f5ba5c4 (origin/pull/19/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f c607f67f5388726e9b8aa8f04768214e8f5ba5c4 # timeout=10Commit message: "Merge pull request 19 from feature-one into master"First time build. Skipping changelog.Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/verification-build[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutusing credential
[JIRA] (JENKINS-30106) Integration with Dimensions
Title: Message Title Piyush Tank commented on JENKINS-30106 Re: Integration with Dimensions David Conneely so the above solution can be used to integrate Jenkins with Dimension ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164687.1440420609000.13044.1587111480276%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe updated JENKINS-61930 Jenkins / JENKINS-61930 Config as Code official compatibility Change By: Vincent Latombe Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.13042.1587111360311%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.13034.1587108420416%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Juergen Zimmermann commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull FYI: The classes "javax.annotation.Nonnull" and "javax.annotation.CheckForNull" are included e.g. in the Maven artifact "com.google.code.findbugs:annotations". Maybe this could be the cause. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.13038.1587108420462%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Hi David Rodriguez This looks likes it a problem in Maven (possibly P4Maven if you are using it) not P4Jenkins. We see P4Jenkins succesfully doing it's sync against a the client 'jenkins-jenkins-slave-test1-admin-ui-4.2-0' here on a node called 'ip-10-21-2-84': P4 Task: syncing files at change: 290033 (p4):cmd:... p4 sync -q /data/jenkins_home/workspace/admin-ui-4.2/...@290033 p4 sync -q /data/jenkins_home/workspace/admin-ui-4.2/...@290033 Then later on when the Maven command runs: [admin-ui-4.2] $ /data/jenkins_home/tools/apache-maven-3.6.3/bin/mvn -s /data/jenkins_home/maven_repository/settings.xml -Pmycomci clean deploy -B -U -Dit.skip=true we see the error: +LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEuhYV5Rf55ZekOlc7RKnPKH7IxMBQUcQgBdWQnJ9XnJ+TqucMoUEKGSCAEaSwAACsNFCqYA==[ERROR] Failed to execute goal com.mycom:mycom-build-info-plugin:1.0.14:create (vernum) on project admin.ui: Unable to fetch p4 head version for path/data/jenkins_home/workspace/admin-ui-4.2: P4 process `/bin/sh -c p4 -d /data/jenkins_home/workspace/admin-ui-4.2 changes -m1 ...` returned error code;rc;1;Error message;... - must create client 'ip-10-21-2-84' to access local files. -> [Help 1] ha:4Lo+a7u/lzaTkq1HGH3U8JSMfSgah36g77z15FvpSvDYYB When P4CLIENT is not set in the environment we default to using the hostname for the client (in this case 'ip-10-21-2-84'. Looking at the maven docs (https://www.perforce.com/manuals/p4maven/index.html) you may need to explicitly pass the client name onto Maven. Possibly: mvn -Dmaven.scm.perforce.clientspec.name=$P4_CLIENT .
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Labels: P4_SUPPORT jenkins plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.13036.1587108420439%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Kalle Niemitalo edited a comment on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist [BSERV-12284|https://jira.atlassian.com/browse/BSERV-12284] "Creating pull request does not reflect the stash-refs/pull-requests/<#> immediately" was moved to SHORT TERM BACKLOG on 2020-04-07. I wonder what Atlassian intends to do. It was then moved down to GATHERING INTEREST on 2020-04-14, and the priority was removed. :( Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205179.1584360231000.13025.1587107340276%40Atlassian.JIRA.
[JIRA] (JENKINS-61520) At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error.
Title: Message Title Govind Sureka commented on JENKINS-61520 Re: At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error. Hello Anda- Does this need any changes in Java settings or other? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205217.1584601273000.13023.1587107160117%40Atlassian.JIRA.
