[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title Sam Gleske commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently From what I can tell in source code it doesn't actually create a concurrency lock. Lockable resources plugin queues "threads" as lightweight jobs. Eventually, the jobs get scheduled. So it doesn't work in the traditional sense of what you think of as locks in concurrent high performance programming. 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.181710.1494001199000.20477.1588378440947%40Atlassian.JIRA.
[JIRA] (JENKINS-62140) Allow use of remote file for non-multibranch pipeline
Title: Message Title Laurent Goujon commented on JENKINS-62140 Re: Allow use of remote file for non-multibranch pipeline Indeed, pipeline jobs. I haven't found why it is hidden on purpose, but it looks like it could be useful too. Isn't a pipeline job basically a multibranch job with only one branch? In my case I want to use a Jenkinsfile with a repository I cannot modify for a single job. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206059.1588359835000.20475.1588373280125%40Atlassian.JIRA.
[JIRA] (JENKINS-56329) Blueocean hanging while loading
Title: Message Title Lu Shen commented on JENKINS-56329 Re: Blueocean hanging while loading I have exactly the same problem on my Jenkins installation: Jenkins version 2.204.5 Blue Ocean plugin: 1.23.1 My Jenkins server is in corporate intranet with access to internet via http_proxy. 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.197913.1551363924000.20473.1588370220335%40Atlassian.JIRA.
[JIRA] (JENKINS-61006) AWS EC2 plugin failing to connect to Windows Slave
Title: Message Title PJ commented on JENKINS-61006 Re: AWS EC2 plugin failing to connect to Windows Slave HI FABRIZIO MANFREDI Could you please update on this ? We are seeing the same errors even after updating the plugin to the latest 1.50.1 version. 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.204476.1581025948000.20469.1588368720146%40Atlassian.JIRA.
[JIRA] (JENKINS-62138) Override by local Jenkinsfile
Title: Message Title Aytunc BEKEN updated an issue Jenkins / JENKINS-62138 Override by local Jenkinsfile Change By: Aytunc BEKEN Component/s: github-organization-folder-plugin Component/s: multibranch-action-triggers-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.206056.158834502.20463.1588368000430%40Atlassian.JIRA.
[JIRA] (JENKINS-62138) Override by local Jenkinsfile
Title: Message Title Aytunc BEKEN assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-62138 Override by local Jenkinsfile Change By: Aytunc BEKEN Assignee: Aytunc BEKEN Kohsuke Kawaguchi 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.206056.158834502.20467.1588368000531%40Atlassian.JIRA.
[JIRA] (JENKINS-62138) Override by local Jenkinsfile
Title: Message Title Aytunc BEKEN commented on JENKINS-62138 Re: Override by local Jenkinsfile I am not sure if this is related to MultiBranch Action Triggers Plugin. Therefore I will change the component to GitHub Organization 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.206056.158834502.20460.1588368000389%40Atlassian.JIRA.
[JIRA] (JENKINS-62140) Allow use of remote file for non-multibranch pipeline
Title: Message Title Aytunc BEKEN commented on JENKINS-62140 Re: Allow use of remote file for non-multibranch pipeline Hi, Thanks for the feedback. In order to understand the issue well, I need to know more, Could you please specify job type ? If it is Pipeline Job, It is hidden on purpose. Best. 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.206059.1588359835000.20457.1588367700203%40Atlassian.JIRA.
[JIRA] (JENKINS-62142) Race condition during init between jobs and agent
Title: Message Title Nigel Armstrong created an issue Jenkins / JENKINS-62142 Race condition during init between jobs and agent Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: branch-api-plugin, core, ec2-plugin, remoting Created: 2020-05-01 21:13 Environment: org.jenkins-ci.main:jenkins-war:2.222.3 org.jenkins-ci.main:remoting:4.2 ec2-plugin:1.49.1 configuration-as-code:1.39 job-dsl:1.77 Priority: Major Reporter: Nigel Armstrong There appears to be a race condition between the initialization of tasks and the initialization of nodes. This appears to be within remoting, but I have included my version of ec2 plugin because we see this on ec2 agents. We are seeing that jobs are being deleted from nodes after a reboot. This appears to be caused by branch-api-plugin WorkspaceLocatorImpl.java (When a computer comes online check for jobs that exist on the computer but do not exist in jenkins (via getItemByFullName)). It seems that either branch-api-plugin needs a change to wait for jobs to be loaded or maybe jenkins should wait for jobs to be loaded before lauching nodes. As an aside the way we found this issue is that it manifests to us a a very long startup time caused by running out of heap space because large objects were allocated when connected to nodes to receive stack traces of exceptions on the nodes caused by jenkins trying to delete the folder of a job in progress that jenkins did not have permission to delete. From here I found that this was caused by the remoting plugin trying to delete the build
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman commented on JENKINS-57411 Re: Upgrade github-branch-source-plugin to use okhttp3 The rebuilt incremental can be found at: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.7.2-rc1146.5bac543b6ba0/ This version uses okhttp3 and is compatible with github-api-plugin 1.110+. 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.199216.1557540525000.20452.1588366800514%40Atlassian.JIRA.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57411 Upgrade github-branch-source-plugin to use okhttp3 Change By: Liam Newman The latest OkHttp (v2.7.5) is over three years old. The web has come a long way. There are a significant number of Jenkins JIRA and Zendesk issues related to using this ancient library in key plugins.We should upgrade Jenkins to use OkHttp3.NOTES: * OkHttp 2.x and 3.x exist and in separate packages and can run side-by-side without conflict. However, different versions of 3.x (and okhttp3 4.x) may be incompatible if clients are using obsolete classes/methods. * OkHttp 3.12.2 is the last version that is reasonably compatible with 2.7.5. Upgrading will require some changes but not huge ones. * OkHttp 3.13.1 has some notable incompatibilities with 2.7.5, but also some better defaults. * OkHttp 3.14.1 removes UrlFactory OkHttpUrlFactory which is a serious version-incompatible API change for several plugins. The github-api library pulled in a shim that provides a workaround OkHttpUrlFactory.Early exploration of this upgrade was started to test whether it would address issues such ass as JENKINS-54126.Finding so far while using 3.12.2: * okio v2.2.x is needed for okhttp3. * Some special class loading settings are needed to get the right versions okhttp3 and okio to be loaded. * (Last updated May 29 1 , 2019): Please give this version of the plugin a try The rebuilt incremental can be found at : [ https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2. 5. 7 .2 - rc892 rc1146 . e46ec862f6f7 5bac543b6ba0 / ] This version uses okhttp3 and is compatible with github-api-plugin 1.110+. Add Comment
[JIRA] (JENKINS-62141) Allow more than one named exception to match each individual branch
Title: Message Title Nikolas Falco started work on JENKINS-62141 Change By: Nikolas Falco 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.206060.1588363949000.20443.1588364580135%40Atlassian.JIRA.
[JIRA] (JENKINS-62141) Allow more than one named exception to match each individual branch
Title: Message Title Nikolas Falco updated JENKINS-62141 Jenkins / JENKINS-62141 Allow more than one named exception to match each individual branch Change By: Nikolas Falco 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.206060.1588363949000.20444.1588364580189%40Atlassian.JIRA.
[JIRA] (JENKINS-62141) Allow more than one named exception to match each individual branch
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-62141 Allow more than one named exception to match each individual branch Issue Type: Bug Assignee: Nikolas Falco Components: branch-api-plugin Created: 2020-05-01 20:12 Priority: Major Reporter: Nikolas Falco Actually for multibranch or organisation folder when I define a different properties for different named exception that matches the same branch master for example only the first exception is considered. There are no validation error and no specific documentation that describe this strategy. Let me report some examples: 1) For !master "Suppress automatic SCm trigger" For PR-* some other property In this case the second definition is ignore since the first one matches PRs 2) Note: I implements a branchproperty to add a build action that run a build with specific parameters and a specific permission, so that only project owner can run release build and developer leader can run create support branch and prepare to next develop. For master branches i would a property named "release" and "prepare next develop" For master branches only i would define "create support branch" So job related to branch master will have release, prepare next develop and create support branch action (button on left side) but support branch job only have next develop and release
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Jesse Glick commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 I have no immediate plans to work on this—Java 11 support in Jenkins remains more or less experimental. I would recommend running on Java 8 unless you have a particular reason you must run on 11. (In which case you can continue to use TCP inbound agents.) 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.204765.1582603216000.20431.1588362900209%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Peter Loron - I haven't gotten around around to creating a github repo with a small reproducible case yet. Once we have that - the Jenkins core contributors devs are fairly responsive. I can take stab at this later today. 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.204765.1582603216000.20429.1588362300601%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Peter Loron commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Has there been any movement on this? We can't run JDK-8 and must use TLS for the traffic between agent and server. Forcing people to use an old JDK or NOT use encryption doesn't seem like a minor bug. It's a security issue. It's a hard blocker for us. 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.204765.1582603216000.20419.1588361640195%40Atlassian.JIRA.
[JIRA] (JENKINS-62140) Allow use of remote file for non-multibranch pipeline
Title: Message Title Laurent Goujon created an issue Jenkins / JENKINS-62140 Allow use of remote file for non-multibranch pipeline Issue Type: Improvement Assignee: Aytunc BEKEN Components: remote-file-plugin Created: 2020-05-01 19:03 Priority: Minor Reporter: Laurent Goujon Remote file plugin hides itself from the pipeline reference dropdown for non-multibranch jobs, but this would be a great addition too and this restriction should probably be relaxed. Add Comment This message was sent by Atl
[JIRA] (JENKINS-62127) Dynamic Axis-Values for declarative Pipeline
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-62127 Dynamic Axis-Values for declarative Pipeline Change By: Liam Newman Assignee: Kohsuke Kawaguchi Liam Newman 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.206041.1588262786000.20409.1588359300910%40Atlassian.JIRA.
[JIRA] (JENKINS-62127) Dynamic Axis-Values for declarative Pipeline
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-62127 Dynamic Axis-Values for declarative Pipeline Change By: Liam Newman Component/s: pipeline-model-definition-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.206041.1588262786000.20406.1588359300479%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61920 java.lang.ClassNotFoundException: javax.annotation.CheckForNull Change By: Daniel Beck Labels: java11 java11-compatibility regression 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.20388.1588352940574%40Atlassian.JIRA.
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title Jesse Glick resolved as Not A Defect A library is not a “custom step”, that would be implemented in Java (and there is one for HTTP calls already). You may not block the CPS VM thread. All operations must be asynchronous. Jenkins / JENKINS-61959 CpsThread(Timeout) raises InterruptedException Change By: Jesse Glick Status: Open 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 rec
[JIRA] (JENKINS-62139) Extended choice parameter array delete then add fails
Title: Message Title
Chris Anderson created an issue
Jenkins / JENKINS-62139
Extended choice parameter array delete then add fails
Issue Type:
Bug
Assignee:
vimil
Components:
extended-choice-parameter-plugin
Created:
2020-05-01 16:53
Labels:
jenkins json
Priority:
Major
Reporter:
Chris Anderson
When using array's, deleting any entry using the 'x item' button and then trying to add a new entry with '+ item' button fails. Error: jsoneditor.min.js:3 Uncaught TypeError: Cannot read property 'style' of null at HTMLButtonElement. (jsoneditor.min.js:3) However, the code runs as expected on the JSON Editor Example page (http://jeremydorn.com/) Sample Schema: { title":"Test array", "type":"object", "properties":{ "Tester": { "type":"array", "items": { "type":"object", "properties": { "myitem":\{"type":"string"} } } } } }
Add Comment
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-61959 CpsThread(Timeout) raises InterruptedException Change By: Jesse Glick Assignee: Jesse Glick 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.205843.1587205537000.20379.1588352040361%40Atlassian.JIRA.
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title Thomas Ullrich assigned an issue to Jesse Glick Jenkins / JENKINS-61959 CpsThread(Timeout) raises InterruptedException Change By: Thomas Ullrich Assignee: Jesse Glick 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.205843.1587205537000.20374.1588351320155%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Daniel Beck edited a comment on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull Everyone experiencing this is Only affects Jenkins on JDK 11, right? JDK11. 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.20365.1588348320257%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Daniel Beck commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull Everyone experiencing this is on JDK 11, right? 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.20356.1588348020322%40Atlassian.JIRA.
[JIRA] (JENKINS-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter
Title: Message Title
Hoa Nguyen edited a comment on JENKINS-40501
Re: Reactive Reference Parameter not working with "List Subversion Tags" parameter
Hi [~rpatriarche],Not sure if you are interested still, but I opted to not use to reference Jenkins svn tag params (I did not want to mess with JS to fix the loading data issue) . Instead I used the hudson.scm.listtagsparameter.ListSubversionTagsParameterDefinition class. I used the following groovy script to get the string value. I referenced a choice parameter that will pass the URL to pull tags from. Only issue is that I could not get credential ID in scope of my project, only in scope at root level. Other than that it works! {code:java}tag_param = new hudson.scm.listtagsparameter.ListSubversionTagsParameterDefinition('', TAG_URL, 'credential_id_here', '', '', '', false, false)tag_param.getTags(){code}
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.177176.1481881922000.20352.1588347180220%40Atlassian.JIRA.
[JIRA] (JENKINS-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter
Title: Message Title
Hoa Nguyen commented on JENKINS-40501
Re: Reactive Reference Parameter not working with "List Subversion Tags" parameter
Hi remi P, Not sure if you are interested still, but I opted to not use to reference Jenkins svn tag params. Instead I used the hudson.scm.listtagsparameter.ListSubversionTagsParameterDefinition class. I used the following groovy script to get the string value. I referenced a choice parameter that will pass the URL to pull tags from. Only issue is that I could not get credential ID in scope of my project, only in scope at root level. Other than that it works!
tag_param = new hudson.scm.listtagsparameter.ListSubversionTagsParameterDefinition('', TAG_URL, 'credential_id_here', '', '', '', false, false)
tag_param.getTags()
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.177176.1481881922000.20347.1588347120225%40Atlassian.JIRA.
[JIRA] (JENKINS-58466) GitLabPipeline Status cannot transition via run from running
Title: Message Title Parichay Barpanda updated JENKINS-58466 Jenkins / JENKINS-58466 GitLabPipeline Status cannot transition via run from running Change By: Parichay Barpanda Status: Open Fixed but Unreleased Resolution: Won't Fix 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.200600.1562929015000.20344.1588346940409%40Atlassian.JIRA.
[JIRA] (JENKINS-58466) GitLabPipeline Status cannot transition via run from running
Title: Message Title Parichay Barpanda commented on JENKINS-58466 Re: GitLabPipeline Status cannot transition via run from running Partially fixed by hiding the exception logs https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/89 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.200600.1562929015000.20339.1588346880313%40Atlassian.JIRA.
[JIRA] (TEST-202) test
Title: Message Title Manjeet Kumar started work on TEST-202 Change By: Manjeet Kumar 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.205854.1587350129000.20330.1588346160381%40Atlassian.JIRA.
[JIRA] (TEST-202) test
Title: Message Title Manjeet Kumar assigned an issue to Manjeet Kumar test / TEST-202 test Change By: Manjeet Kumar Assignee: Manjeet Kumar 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.205854.1587350129000.20332.1588346160413%40Atlassian.JIRA.
[JIRA] (TEST-202) test
Title: Message Title Manjeet Kumar commented on TEST-202 Re: test this is test purpose 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.205854.1587350129000.20334.1588346160472%40Atlassian.JIRA.
[JIRA] (JENKINS-62138) Override by local Jenkinsfile
Title: Message Title Dimitrios Mavrommatis created an issue Jenkins / JENKINS-62138 Override by local Jenkinsfile Issue Type: New Feature Assignee: Aytunc BEKEN Components: multibranch-action-triggers-plugin Created: 2020-05-01 14:57 Priority: Minor Reporter: Dimitrios Mavrommatis I would like, if possible, to add the option of supporting local `Jenkinsfile` inside the repository. The use case is that we are using a `GitHub Organization` job that picks up some repositories and run a specific `Jenkinsfile` that we specify from this plugin. The problem comes when we want to have some customisation or temporarily test something on one repository (or even one branch). For that reason, I thought that it might be a good idea to specify some type of hierarchy: If repository already has `Jenkinsfile` and override is enabled; it uses the local one instead of the remote one, otherwise Remote Jenkinsfile is used Add Comment
[JIRA] (JENKINS-59922) Publish should use p4 reconcile -t to detect filetype changes
Title: Message Title Karl Wirth commented on JENKINS-59922 Re: Publish should use p4 reconcile -t to detect filetype changes Updating to highlight this. Please discuss at next sprint planning meeting. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202721.1571927316000.20311.1588340100165%40Atlassian.JIRA.
[JIRA] (JENKINS-59922) Publish should use p4 reconcile -t to detect filetype changes
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59922 Publish should use p4 reconcile -t to detect filetype changes Change By: Karl Wirth Labels: P4_A P4_VERIFY 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.202721.1571927316000.20310.1588340040069%40Atlassian.JIRA.
[JIRA] (JENKINS-37739) Plugin not displaying Robot Test Summary correctly if robot framework task running in parallel in pipeline
Title: Message Title Andrej Staruch stopped work on JENKINS-37739 Change By: Andrej Staruch Status: In Progress Open 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.173871.1472384428000.20289.1588337941241%40Atlassian.JIRA.
[JIRA] (JENKINS-62089) Blue help icons feel too big
Title: Message Title Daniel Beck updated JENKINS-62089 Jenkins / JENKINS-62089 Blue help icons feel too big Change By: Daniel Beck Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.235 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.205997.1588151467000.20286.1588336380276%40Atlassian.JIRA.
[JIRA] (JENKINS-61970) Download metadata failed for timeout in jenkins master pod, then JVM is terminating
Title: Message Title Daniel Beck closed an issue as Not A Defect This is an issue tracker, not a support site. Try asking in chat, on Stack Overflow, or on the Jenkins Users mailing list. Jenkins / JENKINS-61970 Download metadata failed for timeout in jenkins master pod, then JVM is terminating 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from i
[JIRA] (JENKINS-61956) ItemGroupMixin#createProject() does not call Jenkins#checkGoodName
Title: Message Title Daniel Beck updated JENKINS-61956 Jenkins / JENKINS-61956 ItemGroupMixin#createProject() does not call Jenkins#checkGoodName Change By: Daniel Beck 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.205840.1587161495000.20280.1588335601142%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixin#createProject() does not call Jenkins#checkGoodName
Title: Message Title Daniel Beck updated JENKINS-61956 Jenkins / JENKINS-61956 ItemGroupMixin#createProject() does not call Jenkins#checkGoodName Change By: Daniel Beck 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.205840.1587161495000.20275.1588335601084%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixin#createProject() does not call Jenkins#checkGoodName
Title: Message Title Daniel Beck started work on JENKINS-61956 Change By: Daniel Beck 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.205840.1587161495000.20272.1588335601032%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixin#createProject() does not call Jenkins#checkGoodName
Title: Message Title Daniel Beck updated JENKINS-61956 Jenkins / JENKINS-61956 ItemGroupMixin#createProject() does not call Jenkins#checkGoodName Change By: Daniel Beck Status: In Review 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.205840.1587161495000.20278.1588335601119%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title Daniel Beck commented on JENKINS-61990 Re: StackOverflowError on boot related to QueueItemAuthenticatorConfiguration it automatically adds the anonymous user without any privileges and you cannot remove this. It's a contrast to our global permissions, though, which grant anonymous users the ViewStatus privilege. It seems like (sometimes) Jenkins cannot resolve this contradiction. The UI doesn't matter here, table rows (i.e. users/groups) without any permissions granted aren't saved, you can see that in config.xml that will not have entries for anonymous unless you grant permissions. 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.205880.1587466781000.20266.1588335540137%40Atlassian.JIRA.
[JIRA] (JENKINS-62088) Plugin manager loading incorrect fonts
Title: Message Title Daniel Beck updated JENKINS-62088 Jenkins / JENKINS-62088 Plugin manager loading incorrect fonts Change By: Daniel Beck Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.235 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.205996.1588144537000.20263.1588334880442%40Atlassian.JIRA.
[JIRA] (JENKINS-62056) ExtensionComponent#compareTo violates its method contract
Title: Message Title Daniel Beck updated JENKINS-62056 Jenkins / JENKINS-62056 ExtensionComponent#compareTo violates its method contract Change By: Daniel Beck Status: In Progress Fixed but Unreleased Resolution: Fixed Released As: 2.235 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.205954.158784000.20261.1588334880418%40Atlassian.JIRA.
[JIRA] (JENKINS-61986) cmd java -jar jenkins-cli -webSocket install-plugin results an ERROR
Title: Message Title Daniel Beck closed an issue as Not A Defect This hasn't been supported in years. Please read the install-plugin documentation. Jenkins / JENKINS-61986 cmd java -jar jenkins-cli -webSocket install-plugin results an ERROR 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@google
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Daniel Beck updated JENKINS-61878 Jenkins / JENKINS-61878 Improve the queue/cancelItem endpoint API documentation Change By: Daniel Beck Status: In Review Closed Resolution: Fixed Released As: 2.232 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.205746.1586766048000.20255.1588334760368%40Atlassian.JIRA.
[JIRA] (JENKINS-62137) error while converting free style jobs to declarative pipeline job.
Title: Message Title Anoop Kv created an issue Jenkins / JENKINS-62137 error while converting free style jobs to declarative pipeline job. Issue Type: Story Assignee: Mohit Dharamshi Components: convert-to-pipeline-plugin, freestyle-multibranch-plugin Created: 2020-05-01 11:25 Priority: Minor Reporter: Anoop Kv Hi Team, I am using "convertTo declarative" plugin for converting my free style jobs to declarative pipeline job. But, i am getting below message after conversion. // Unable to convert a build step referring to "org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper". Please verify and convert manually if required. // Unable to convert a build step referring to "hudson.plugins.powershell.PowerShell". Please verify and convert manually if required. Add Comment
[JIRA] (JENKINS-62136) error while converting free style jobs to declarative pipeline job.
Title: Message Title Anoop Kv created an issue Jenkins / JENKINS-62136 error while converting free style jobs to declarative pipeline job. Issue Type: Story Assignee: Mohit Dharamshi Components: convert-to-pipeline-plugin, freestyle-multibranch-plugin Created: 2020-05-01 11:25 Priority: Minor Reporter: Anoop Kv Hi Team, I am using "convertTo declarative" plugin for converting my free style jobs to declarative pipeline job. But, i am getting below message after conversion. // Unable to convert a build step referring to "org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper". Please verify and convert manually if required. // Unable to convert a build step referring to "hudson.plugins.powershell.PowerShell". Please verify and convert manually if required. Add Comment
[JIRA] (JENKINS-62116) Organization Scan recreates hooks for all repository
Title: Message Title Olivier Lamy commented on JENKINS-62116 Re: Organization Scan recreates hooks for all repository pr https://github.com/jenkinsci/github-plugin/pull/230 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.206027.158820875.20242.1588329540149%40Atlassian.JIRA.
[JIRA] (JENKINS-62135) Problems while trying to run a simple groovy scryt
Title: Message Title
Francisco yanez created an issue
Jenkins / JENKINS-62135
Problems while trying to run a simple groovy scryt
Issue Type:
Task
Assignee:
Unassigned
Components:
pipeline
Created:
2020-05-01 09:27
Environment:
I have a very simple script that I am trying to run on a windows 10 acting as my jenkins server: node { stage("postman test"){ git "https://github.com/eyanez111/Postman-newman-jenkins.git" sh "npm install" sh "npm run api-test-production" } }
Priority:
Minor
Reporter:
Francisco yanez
I have a very simple script that I am trying to run on a windows 10 acting as my jenkins server: node { stage("postman test") { git "https://github.com/eyanez111/Postman-newman-jenkins.git" sh "npm install" sh "npm run api-test-production" } } I am getting this out. I have done tons of research but I have not found anything: Started by user admin Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] node Running on Jenkins in C:\Program Files (x86)\Jenkins\workspace\jsonplaceholder_api_tests [Pipeline] { [Pipeline] stage [Pipeline] { (postman test) [Pipeline] git No credentials specified Cloning the remote Git repository Cloning repository https://github.com/eyanez111/Postman-newman-jenkins.git > git.exe init C:\Program Files (x86)\Jenkins\workspace\jsonplaceholder_api_tests # timeout=10 Fetching upstream changes from https://github.com/eyanez111/Postman-newman-jenkins.git > git.exe --version # timeout=10 > git.exe fetch --tags --force --progress -- https://github.com/eyanez111/Postman-newman-jenkins.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git.exe config remote.origin.url https://github.com/eyanez111/Postman-newman-jenkins.git # timeout=10 > git.exe config --add re
[JIRA] (JENKINS-60995) Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17
Title: Message Title Peter Waller commented on JENKINS-60995 Re: Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17 A few observations: The links seem to be missing in particular if there is any failing build within the whole pipeline. The source data exists on disk in the jenkins XML database, so I believe this is a presentation bug. Stuart Rowe did some additional investigation in this other ticket, and seems to have come close to localizing the bug. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204463.158098930.20224.1588320547818%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title James Nord commented on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning Okay, I get it. Since this plugin is refusing to use a credential that is in the wrong domain, it is a incorrect behavior related to credentials. Thus a security issue. refusing to use a credential that is in the wrong domain is the correct behaviour. knowingly using a credential that is in a domain that does not match is a security issue as it could lead to credential leaking. if you know if a plugging that fits that please raise a security issue for discussion 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.201369.1566328715000.20198.1588319760312%40Atlassian.JIRA.
