[JIRA] (JENKINS-60116) Overall/Administer permission required to configure jobs
Title: Message Title roy zhou commented on JENKINS-60116 Re: Overall/Administer permission required to configure jobs is there any fix released? we are on 1.1.0 but during configure on the pipeline job, we still facing the permission issue although developer already have job config permission in their folder. 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.202963.1573262524000.176.1585206420220%40Atlassian.JIRA.
[JIRA] (JENKINS-42422) Add support for directory caching in pod jobs
Title: Message Title Tristan FAURE commented on JENKINS-42422 Re: Add support for directory caching in pod jobs I also have the same issue : https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jenkinsci-users/X61BK83LHLU/hztGcbkvBgAJ I don't really know travis but what i assume it is equivalent to https://docs.gitlab.com/ee/ci/caching/ about Carlos Sanchez comments : we did not find either how to create pvc in the yaml syntax it was always overrident when we tried stashu / unstash or archiveArtifacts could help us but how can configure it to store in a pv ? how long the data is kept if there are no unstash ? 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.179329.1488410958000.187.1585207920465%40Atlassian.JIRA.
[JIRA] (JENKINS-42422) Add support for directory caching in pod jobs
Title: Message Title Tristan FAURE edited a comment on JENKINS-42422 Re: Add support for directory caching in pod jobs I also have the same issue : [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jenkinsci-users/X61BK83LHLU/hztGcbkvBgAJ]I don't really know travis but what i assume it is equivalent to [https://docs.gitlab.com/ee/ci/caching/]about [~csanchez] comments : * we did not find either how to create pvc in the yaml syntax it was always overrident when we tried * stashu / unstash or archiveArtifacts could help us but how can configure it to store in a pv ? how long the data is kept if there are no unstash ? 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.179329.1488410958000.198.1585207980448%40Atlassian.JIRA.
[JIRA] (JENKINS-42422) Add support for directory caching in pod jobs
Title: Message Title Tristan FAURE edited a comment on JENKINS-42422 Re: Add support for directory caching in pod jobs I also have the same issue : [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jenkinsci-users/X61BK83LHLU/hztGcbkvBgAJ]I don't really know travis but i assume it is equivalent to [https://docs.gitlab.com/ee/ci/caching/]about [~csanchez] comments : * we did not find either how to create pvc in the yaml syntax it was always overrident when we tried * stashu stash / unstash or archiveArtifacts could help us but how can configure it to store in a pv ? how long the data is kept if there are no unstash ? ** +edit:+ as we want data available across jobs, stash unstash does not seem relevant 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.179329.1488410958000.222.1585215120532%40Atlassian.JIRA.
[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title Ben M updated an issue Jenkins / JENKINS-60979 Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory Change By: Ben M Comment: [~kwhetstone] it happens when using the plugin installation manager.This does not happen when either not using the liberty feature "transportsecurity" or when not using java >= 9.I think this issue can be closed here, I will open one at openliberty on github instead. 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.204447.1580906476000.234.1585215360327%40Atlassian.JIRA.
[JIRA] (JENKINS-61670) Attribute like e.g. class gets lost from HTML code in description fields
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61670 Attribute like e.g. class gets lost from HTML code in description fields Change By: Daniel Beck Issue Type: Bug Improvement 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.205403.1585077195000.252.1585219740153%40Atlassian.JIRA.
[JIRA] (JENKINS-61677) Mark PR as Needs Work when build fails
Title: Message Title Ilya Vassilevsky commented on JENKINS-61677 Re: Mark PR as Needs Work when build fails Yes, I was imagining a "Jenkins" user and sending API requests on behalf of that user. It will look like the butler himself has marked the PR as "Needs Work" LOL. 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.205414.1585126338000.254.1585219800211%40Atlassian.JIRA.
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Ian Williams updated an issue Jenkins / JENKINS-61660 Lack of spacing between setup wizard form errors Change By: Ian Williams Introduced PIntroduced in 2.217+ I believe.There is no spacing between form errors on the setup wizard, as shown in the picture:!Captura de pantalla 2020-03-23 a las 11.10.50.png!There should be at least 0.5rem of spacing between them. 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.205390.1585039651000.257.1585220040151%40Atlassian.JIRA.
[JIRA] (JENKINS-60143) Behaviour SSH Checkout not working after Jenkins restart
Title: Message Title Vincent Letarouilly commented on JENKINS-60143 Re: Behaviour SSH Checkout not working after Jenkins restart I'm using the Checkout over SSH trait and still have the same issue when Jenkins is restarting. It is pretty annoying for us at the moment because we are setting up a new Jenkins instance and we are restarting it a lot when installing other plugins or doing some tests. Jenkins version 2.227 gitlab-branch-source-plugin version 1.4.4 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.203004.1573562285000.260.1585220700321%40Atlassian.JIRA.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Xianpeng Shen commented on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration I have the same issue in Jenkins ver. 2.176.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.164818.1441065243000.266.1585220880498%40Atlassian.JIRA.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Xianpeng Shen edited a comment on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration I have the same issue in on Jenkins ver. 2.176.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.164818.1441065243000.282.1585221300428%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Hi Erez Arbell - I fully understand and I hope things are OK with you. As soon as there is anything I can do to help, please let me know. 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.190940.1527360591000.324.158500405%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth closed an issue as Postponed More invstigation required. Will return to this at a later date. Jenkins / JENKINS-51552 Cannot replay pipelines - files are read-only Change By: Karl Wirth Status: Open Closed Resolution: Postponed 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 vi
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title
Kenneth Rogers commented on JENKINS-58656
Re: Wrapper process leaves zombie when no init process present
I have been unable to reproduce the `Resource temporarily unavailable.` error when attempting to run pipelines that simulate the situation described. I created a cluster in GKE using the gcloud cli. gcloud container clusters create --machine-type=n1-standard-2 --cluster-version=latest. Installed Cloudbees Core for Modern Platforms version 2.204.3.7 (latest public release at the time I started testing) using Helm. Used kubectl get nodes to find the names of the nodes and gcloud beta compute ssh to connect to the nodes via ssh. Then running watch 'ps fauxwww | fgrep Z' to watch for zombie processes on each node. Using groovy while (true) { sh 'sleep 1' } I was able to produce zombie processes on the node the build agent was assigned to. The process ran for 5 hours 17 minutes before using all the process resources. After the processes were exhausted the job exited with an error message that there were not processes available. After the pod running the job exited the zombie processes on the node were removed and the node continued to function. Using `while :; do /usr/bin/sleep .01; done` as a way to generate subprocesses I've tested as the direct parameter of an `sh` step in a pipeline using both `jenkins/jnlp-slave` and `cloudbees/cloudbees-core-agent` images. Neither produced any zombie processes on the worker nodes of the Kubernetes cluster. To induce another layer of subprocess I also put that `while` line into a file and had the `sh` process execute that file, but it also did not produce any zombie processes on the worker nodes. Additionally I made that while loop a step in a Makefile and executed it that way, which also did not produce any zombies on the nodes.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60294) TFS plugin: Can't reuse workspace and 100% CPU
Title: Message Title
Stefan Drissen commented on JENKINS-60294
Re: TFS plugin: Can't reuse workspace and 100% CPU
I was testing with a pipeline script in the job configuration without using the Jenkinsfile from scm and had everything working fine. My next step was to use the Jenkinsfile directly from scm and then I ran into this same "interesting" behavior of the tfs plugin. To work-around the absence of the lightweight checkout (our branch has 24 000 files totaling 1 GB) I have cloaked all but the branch folder, added the option skipDefaultCheckout true to the pipeline and then do the actual checkout in a stage:
pipeline {
options {
skipDefaultCheckout true
}
stages {
stage( 'pre-build' ) {
agent {
label 'master'
}
steps {
checkout(
[
$class: 'TeamFoundationServerScm',
credentialsConfigurer: [$class: 'AutomaticCredentialsConfigurer'],
serverUrl: 'https://',
projectPath: "${branch}",
localPath: 'tfs',
useOverwrite: true,
useUpdate: true,
workspaceName: "Jenkins-${JOB_BASE_NAME}-tfs"
]
)
dir( 'tfs' ) {
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61691) Git SCM details not getting saved
Title: Message Title aaron axisa created an issue Jenkins / JENKINS-61691 Git SCM details not getting saved Issue Type: Bug Assignee: Mark Waite Components: core, git-plugin, multiple-scms-plugin Created: 2020-03-26 13:11 Environment: jenkins version 2.224 tried latest version of git plugin and tried also downgrading to no avail. Priority: Blocker Reporter: aaron axisa I have a project being setup on Jenkins. For some reason however, I input my scm details (git in this case but have tried going at it through the multiple scm plugin) It start to shows the usual errors before I select the credentials, select the credentials, and all looks fine I click apply and save. the saved notification appears. However if I exit and re-configure the same job, the SCM settings have vanished completely. (if I run the job it doesn't try to pull and just fails later when it doesn't find my pom.xml) Add Comment
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig moved an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Thomas Patzig Project: Infrastructure Jenkins Key: INFRA JENKINS - 2554 61692 Workflow: classic default workflow JNJira + In-Review Component/s: core Component/s: proxy Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig updated an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Thomas Patzig Environment: Jenkins ver. 2.222.1 just plain Jenkinsno plugins 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.205516.1585227401000.450.1585228560067%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig updated an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Thomas Patzig Environment: Jenkins ver. 2.222.1just plain Jenkinsno plugins user is an active directory user 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.205516.1585227401000.451.1585228620112%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title
Thomas Patzig updated an issue
Jenkins / JENKINS-61692
"HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Change By:
Thomas Patzig
today I have test to deployed the latest LTS version: Jenkins ver. 2.222.1as I want to configure my proxy it crashs directly on "Validate Proxy" !screenshot-1.png|thumbnail! before that new LTS version I use Jenkins ver. 2.204.5 were this working fine !screenshot-2.png|thumbnail! {code:java}java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) at hudson.security.ChainedSer
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title
Thomas Patzig updated an issue
Jenkins / JENKINS-61692
"HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Change By:
Thomas Patzig
today I have test to deployed the latest LTS version: Jenkins ver. 2.222.1as I want to configure my proxy it crashs directly on "Validate Proxy" user is an AD user, have already try: u...@domain.tlddomain\useruser=> same behavior !screenshot-1.png|thumbnail! before that new LTS version I use Jenkins ver. 2.204.5 were this working fine !screenshot-2.png|thumbnail! {code:java}java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslat
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title
Thomas Patzig updated an issue
Jenkins / JENKINS-61692
"HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Change By:
Thomas Patzig
today I have test to deployed the latest LTS version: Jenkins ver. 2.222.1as I want to configure my proxy it crashs directly on "Validate Proxy"user is an AD user, have already try:u...@domain.tlddomain\useruser=> same behavior !screenshot-1.png|thumbnail! before that new LTS version I use Jenkins ver. 2.204.5 were this working fine !screenshot-2.png|thumbnail! {code:java}java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationF
[JIRA] (JENKINS-61691) Git SCM details not getting saved
Title: Message Title Mark Waite updated JENKINS-61691 Jenkins 2.224 has a critical regression which discards the SCM configuration when it is saved. Fixed by updating to Jenkins 2.225 or later. My apologies for that regression in the weekly Jenkins release. Jenkins / JENKINS-61691 Git SCM details not getting saved Change By: Mark Waite Status: Open Fixed but Unreleased 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 group a
[JIRA] (JENKINS-61691) Git SCM details not getting saved
Title: Message Title Mark Waite updated JENKINS-61691 Jenkins / JENKINS-61691 Git SCM details not getting saved Change By: Mark Waite Status: Fixed but Unreleased 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.205517.1585228281000.458.1585229400509%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig updated an issue Jenkins / JENKINS-61693 using git multi branch pipeline through proxy leads to fatal: unable to access Change By: Thomas Patzig Summary: using git multi branch pipeline through proxy leads to fatal: unable to access 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.205518.1585229665000.462.1585229700847%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads fatal: unable to access
Title: Message Title Thomas Patzig created an issue Jenkins / JENKINS-61693 using git multi branch pipeline through proxy leads fatal: unable to access Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2020-03-26 13:34 Environment: latest Jenkins LTS Jenkins ver. 2.222.1 git plugin multi branch pipeline need proxy to use SCM (bitbucket) Priority: Minor Reporter: Thomas Patzig Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig updated an issue Jenkins / JENKINS-61693 using git multi branch pipeline through proxy leads to fatal: unable to access Change By: Thomas Patzig Attachment: screenshot-1.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.205518.1585229665000.464.1585229940323%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title
Thomas Patzig updated an issue
Jenkins / JENKINS-61693
using git multi branch pipeline through proxy leads to fatal: unable to access
Change By:
Thomas Patzig
{code:java}Started by user testuser[Thu Mar 26 14:22:58 CET 2020] Starting branch indexing... > git.exe --version # timeout=10using GIT_ASKPASS to set credentials Setting http proxy: proxy.*.com:8080 > git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git # timeout=10ERROR: [Thu Mar 26 14:22:58 CET 2020] Could not update folder level actions from source 4ad1ee05-7f07-477a-a003-aa5b11127210hudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128:stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1944) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1935) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:3360) at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:1121) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:848) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:598) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1032) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)[Thu Mar 26 14:22:58 CET 2020] Finished branch indexing. Indexing took 0.5 secFATAL: Failed to recompute children of Infrastructurehudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128:stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1944) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1935) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:3360) at jenkins.plugins.git.AbstractGitSC
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick updated JENKINS-61409 Jenkins / JENKINS-61409 Websocket connections crash if message size is greater than 64Kb Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.229 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.205063.1583801943000.473.158523850%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title
Thomas Patzig updated an issue
Jenkins / JENKINS-61693
using git multi branch pipeline through proxy leads to fatal: unable to access
Change By:
Thomas Patzig
have update from Jenkins LTS Jenkins ver. 2.204.5 to the latest LTS: Jenkins ver. 2.222.1now my git multi branch pipeline through proxy doesn't work anymore !screenshot-1.png|thumbnail! {code:java}Started by user testuser[Thu Mar 26 14:22:58 CET 2020] Starting branch indexing... > git.exe --version # timeout=10using GIT_ASKPASS to set credentials Setting http proxy: proxy.*.com:8080 > git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git # timeout=10ERROR: [Thu Mar 26 14:22:58 CET 2020] Could not update folder level actions from source 4ad1ee05-7f07-477a-a003-aa5b11127210hudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128:stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1944) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1935) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:3360) at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:1121) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:848) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:598) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1032) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)[Thu Mar 26 14:22:58 CET 2020] Finished branch indexing. Indexing took 0.5 secFATAL: Failed to recompute children of Infrastructurehudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128:stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1944) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.laun
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig updated an issue Jenkins / JENKINS-61693 using git multi branch pipeline through proxy leads to fatal: unable to access Change By: Thomas Patzig Priority: Minor Blocker 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.205518.1585229665000.479.1585230120400%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title
Thomas Patzig updated an issue
Jenkins / JENKINS-61693
using git multi branch pipeline through proxy leads to fatal: unable to access
Change By:
Thomas Patzig
have update from Jenkins LTS Jenkins ver. 2.204.5 to the latest LTS: Jenkins ver. 2.222.1 now my git multi branch pipeline through proxy doesn't work anymore {code:java}Started by user testuser[Thu Mar 26 14:22:58 CET 2020] Starting branch indexing... > git.exe --version # timeout=10using GIT_ASKPASS to set credentials Setting http proxy: proxy.*.com:8080 > git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git # timeout=10ERROR: [Thu Mar 26 14:22:58 CET 2020] Could not update folder level actions from source 4ad1ee05-7f07-477a-a003-aa5b11127210hudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128:stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1944) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1935) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:3360) at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:1121) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:848) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:598) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1032) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)[Thu Mar 26 14:22:58 CET 2020] Finished branch indexing. Indexing took 0.5 secFATAL: Failed to recompute children of Infrastructurehudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128:stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1944) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliG
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb Oliver Gondža remember that if backporting to 2.222.x, we would want to create a component backport so as to get something like remoting.version=4.2.1. Otherwise we would be including https://github.com/jenkinsci/remoting/pull/369 in LTS, which includes a couple of production source code changes, albeit small (Util.mkdirs → Files.createDirectories). 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.205063.1583801943000.482.1585230300247%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title
Thomas Patzig updated an issue
Jenkins / JENKINS-61693
using git multi branch pipeline through proxy leads to fatal: unable to access
Change By:
Thomas Patzig
have update from Jenkins LTS Jenkins ver. 2.204.5 to the latest LTS: Jenkins ver. 2.222.1now my git multi branch pipeline through proxy doesn't work anymore !screenshot-1.png|thumbnail! with Jenkins ver. 2.204.5 it was working fine: !screenshot-2.png|thumbnail! {code:java}Started by user testuser[Thu Mar 26 14:22:58 CET 2020] Starting branch indexing... > git.exe --version # timeout=10using GIT_ASKPASS to set credentials Setting http proxy: proxy.*.com:8080 > git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git # timeout=10ERROR: [Thu Mar 26 14:22:58 CET 2020] Could not update folder level actions from source 4ad1ee05-7f07-477a-a003-aa5b11127210hudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128:stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1944) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1935) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:3360) at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:1121) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:848) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:598) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1032) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)[Thu Mar 26 14:22:58 CET 2020] Finished branch indexing. Indexing took 0.5 secFATAL: Failed to recompute children of Infrastructurehudson.plugins.git.GitException: Command "git.exe ls-remote --symref -- https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git" returned status code 128:stdout: stderr: fatal: unable to access 'https://bitbucket.mydev.com/scm/ici/infrastructuredotnet.git/': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(Cli
[JIRA] (JENKINS-27082) Sparse checkouts and submodules: Error on checkout, submodule missing
Title: Message Title ASHOK MOHANTY commented on JENKINS-27082 Re: Sparse checkouts and submodules: Error on checkout, submodule missing Thanks Mark. Yes I am trying to use submodule (sparse checkout). But ya found the git version is 1.8.x, will upgrade to 1.9.x and re-try. FYI - OS is "Oracle Linux Server 7.7". 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.160872.1424699584000.494.1585230360535%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig updated an issue Jenkins / JENKINS-61693 using git multi branch pipeline through proxy leads to fatal: unable to access Change By: Thomas Patzig Attachment: screenshot-2.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.205518.1585229665000.496.1585230360558%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access maybe there is a similar issue 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.205518.1585229665000.500.1585230480130%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Mark Waite commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access Did you also change the version of the Jenkins git plugin in that upgrade? As far as I understand from JENKINS-51039, proxy settings are ignored by 'lightweight checkout' and other multibranch pipeline 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.205518.1585229665000.502.1585230540123%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61693 using git multi branch pipeline through proxy leads to fatal: unable to access Change By: Mark Waite Assignee: Mark Waite 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.205518.1585229665000.504.1585230600117%40Atlassian.JIRA.
[JIRA] (JENKINS-27082) Sparse checkouts and submodules: Error on checkout, submodule missing
Title: Message Title Mark Waite commented on JENKINS-27082 Re: Sparse checkouts and submodules: Error on checkout, submodule missing ASHOK MOHANTY if you are upgrading to a newer version of git, please consider upgrading to a much more recent version than 1.9.x. Git 2.26.0 recently released. Git 2.26.0 and the preceding 25+ releases are significant improvements over command line git 1.9. 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.160872.1424699584000.512.1585230780612%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access Mark Waite I don't do an upgrade. I test a fresh setup of Jenkins. Add proxy server and add plugins... 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.205518.1585229665000.514.1585230840129%40Atlassian.JIRA.
[JIRA] (JENKINS-61051) Jobs are started on master instead of EC2 slaves randomly
Title: Message Title Laszlo Gaal commented on JENKINS-61051 Re: Jobs are started on master instead of EC2 slaves randomly Just ran into this again. Jeff Thompson: yeah, it looks like either a timing problem or a race. As a workaround I installed roadblocks on the master that should fail such an errant job very early in the startup/config phase, before it has a chance to consume all memory and trigger an OOM-kill. We'll see if it's enough; I'd really hate to downgrade the plugin 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.204531.158142564.519.1585230960306%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig edited a comment on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access [~markewaite]I don't do an upgrade. I test a fresh setup of Jenkins. Add proxy server and add plugins... I'm not sure with the other issue: JENKINS-51039but it happened with: lts 2.107.2my setup works with Jenkins LTS ver. 2.204.5and works no longer with Jenkins LTS ver. 2.222.1 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.205518.1585229665000.521.1585231260223%40Atlassian.JIRA.
[JIRA] (JENKINS-61051) Jobs are started on master instead of EC2 slaves randomly
Title: Message Title Gabor V commented on JENKINS-61051 Re: Jobs are started on master instead of EC2 slaves randomly Any idea who can work on this bug from the ec2 plugin team? To whom should we assign 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.204531.158142564.523.1585231260255%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks will not reliably work with JCasC
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-61694 Groovy Hooks will not reliably work with JCasC Issue Type: Bug Assignee: Oleg Nenashev Components: core Created: 2020-03-26 14:01 Priority: Minor Reporter: Oleg Nenashev After introduction a new milestones in the core, JCasC and Groovy hooks will not be aligned properly after https://github.com/jenkinsci/configuration-as-code-plugin/pull/1262 . We need to apply a fix in the Jenkins core to ensure that JCasC and Groovy Hooks still interact in a predictable way. Proposal: Revert https://github.com/jenkinsci/jenkins/commit/ab12f71a48901ab3b78521382057a03e166fe668 to the orifginal state so that init hook behaves as before: after all initialization steps Document Groovy Hooks and explicitly document the state Consider introducing new hooks for specific items like post-job-initialization Add Comment
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Mark Waite commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access Based on the bug report that you linked ( "Validate Proxy" crashs immediately with NullPointerException" class="issue-link" data-issue-key="JENKINS-61692" style="color: #3b73af; text-decoration: none">JENKINS-61692 ), I would guess that the proxy settings are not defined, since the validation failed with an NPE. If you're willing to experiment, you could try inserting the proxy definition from the working Jenkins configuration files of 2.204.5 into the XML config files of Jenkins 2.222.1. That might avoid the validation failure and assure that a proxy is defined. 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.205518.1585229665000.528.1585231380198%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks will not reliably work with JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61694 Groovy Hooks will not reliably work with JCasC Change By: Oleg Nenashev Labels: jcasc-compatibility 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.205519.1585231269000.529.1585231380243%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks will not reliably work with JCasC
Title: Message Title Oleg Nenashev started work on JENKINS-61694 Change By: Oleg Nenashev 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.205519.1585231269000.531.1585231440257%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks will not reliably work with JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61694 Groovy Hooks will not reliably work with JCasC Change By: Oleg Nenashev Priority: Minor Major 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.205519.1585231269000.530.1585231440215%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access ...ok, let me try 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.205518.1585229665000.532.1585231440268%40Atlassian.JIRA.
[JIRA] (JENKINS-61695) Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ...
Title: Message Title Prabin Shrestha created an issue Jenkins / JENKINS-61695 Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ... Issue Type: Task Assignee: Unassigned Components: maven-plugin Created: 2020-03-26 14:34 Environment: Jenkins 2.190.3, Windows, Chrome browser, carriage return Priority: Minor Reporter: Prabin Shrestha Recently I had upgraded Jenkins 2.150.2 to 2.190.3 . When I browse Jenkins using Chrome, or Firefox, the spaces between environment variables set in the text area of Maven_Opts remove and squeeze into one line after saving the Jenkins configuration and causing the build to break. But there is no any issue while browsing from Internet Explorer and Microsoft Edge. Is there anyone who can provide me solution for this issue ? Add Comment
[JIRA] (JENKINS-61695) Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ...
Title: Message Title Prabin Shrestha assigned an issue to Prabin Shrestha Jenkins / JENKINS-61695 Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ... Change By: Prabin Shrestha Assignee: Prabin Shrestha 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.205520.1585233242000.543.1585233420062%40Atlassian.JIRA.
[JIRA] (JENKINS-61695) Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ...
Title: Message Title Prabin Shrestha assigned an issue to Unassigned Jenkins / JENKINS-61695 Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ... Change By: Prabin Shrestha Assignee: Prabin Shrestha 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.205520.1585233242000.544.1585233480055%40Atlassian.JIRA.
[JIRA] (JENKINS-61696) Replace "top page"
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61696 Replace "top page" Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-26 15:08 Priority: Minor Reporter: Josh Soref I installed some plugins using the plugin manager, which eventually took me to: http://jenkins.example.com/updateCenter/ Installing Plugins/Upgrades Go back to the top page (you can start using the installed plugins right away) I don't think "top page" is a term Jenkins generally uses. Add Comment
[JIRA] (JENKINS-46540) "Open Blue Ocean" button disappers when "Block inheritance of global authorization matrix" is set in a folder
Title: Message Title James Pressley commented on JENKINS-46540 Re: "Open Blue Ocean" button disappers when "Block inheritance of global authorization matrix" is set in a folder Is there any movement on this? Users are complaining the blue ocean button is not there. I have resorted to inheriting the permissions and adding but this is not ideal 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.184858.150410200.564.1585236540257%40Atlassian.JIRA.
[JIRA] (JENKINS-61697) Cannot contact node: java.lang.InterruptedException
Title: Message Title Evan Arbeitman created an issue Jenkins / JENKINS-61697 Cannot contact node: java.lang.InterruptedException Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: support_2020-03-26_15.15.15.zip Components: pipeline, ssh-slaves-plugin Created: 2020-03-26 15:30 Priority: Minor Reporter: Evan Arbeitman Hi, We are experiencing the following error when running pipeline jobs: // Cannot contact node: java.lang.InterruptedException I came across these issues and both suggests upgrading the pipeline plugins: https://issues.jenkins-ci.org/browse/JENKINS-43038 https://issues.jenkins-ci.org/browse/JENKINS-46507 However, I'm hesitant to upgrade due to all the related dependencies that need to be upgraded as well. Can you confirm which plugin needs to be upgraded? There are several "pipeline" related plugins Ive attached a support bundle for one of the jobs that failed for this reason. Would appreciate if anyone can take a look
[JIRA] (JENKINS-61698) Configuration accepts invalid values -- ArrayIndexOutOfBoundsException during runtime
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-61698 Configuration accepts invalid values -- ArrayIndexOutOfBoundsException during runtime Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-26 16:07 Environment: Jenkins ver. 2.204.2 ec2 plugin 1.49.1 Priority: Major Reporter: Jakub Bochenski When trying to provision a new agent the plugin would start and then terminate an EC2 instance several times before succeeding in the end. I have no explanation for this behavior. Might be related to JENKINS-61343 Might be because the plugin somehow allocates "2 computer(s)" even though the instance cap is 1. Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log bootstrap() Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log Getting keypair... Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log Using private key j4a-ec2-ssh-key (SHA-1 fingerprint a7:b4:70:08:35:11:e3:cf:4b:f5:92:57:b8:02:7f:c6:8e:54:52:02) Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log Authenticating as admin Mar 06, 2020 3:05:22 PM INFO hudson.slaves.NodeProvisioner lambda$update$6 EC2 (ec2) - ec2 (ami-028d96c69234f9d1a) provisioning successfully completed. We have now 2 computer(s) Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log Connecting to 10.20.4.41 on port 22, with timeout 1. Mar 06, 2020 3:05:29 PM INFO hudson.plugins.ec2.EC2Cloud log Connected via SSH. Mar 06, 2020 3:05:29 PM INFO hudson.plugins.ec2.EC2Cloud log connect fresh as root Mar 06, 2020 3:05:29 PM INFO hudson.plugins.ec2.EC2Cloud log
[JIRA] (JENKINS-61698) Configuration accepts invalid values -- ArrayIndexOutOfBoundsException during runtime
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61698
Configuration accepts invalid values -- ArrayIndexOutOfBoundsException during runtime
Change By:
Jakub Bochenski
When trying to provision a new agent You can enter double comma into the plugin would start and then terminate an EC2 instance several times before succeeding in the end block devices field (E . I have no explanation for this behavior g . Might be related to JENKINS {{/dev/xvdb=:20,,/dev/sdf=snap - 61343Might 1234}} . It will be because accepted, later the plugin somehow allocates "2 computer(s)" even though the instance cap is 1. will fail with: {code}Mar 06 26 , 2020 3: 05 55 : 22 57 PM INFO SEVERE hudson. plugins triggers . ec2.EC2Cloud log SafeTimerTask run bootstrap() Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@1bbf83bc failed Mar 06, 2020 3 java.lang.ArrayIndexOutOfBoundsException : 05:22 PM INFO 1 at hudson.plugins.ec2. EC2Cloud logGetting keypair util . DeviceMappingParser . parse(DeviceMappingParser . Mar 06, 2020 3 java : 05:22 PM INFO 45) at hudson.plugins.ec2. EC2Cloud logUsing private key j4a-ec2-ssh-key SlaveTemplate.setupCustomDeviceMapping ( SHA-1 fingerprint a7 SlaveTemplate.java : b4:70:08:35:11:e3:cf:4b:f5:92:57:b8:02:7f:c6:8e:54:52:02 904 ) Mar 06, 2020 3:05:22 PM INFO at hudson.plugins.ec2. EC2Cloud logAuthenticating as adminMar 06, 2020 3 SlaveTemplate.setupBlockDeviceMappings(SlaveTemplate.java : 05:22 PM INFO 1070) at hudson. slaves plugins . NodeProvisioner lambda$update$6EC2 ( ec2 ) - ec2 (ami-028d96c69234f9d1a) provisioning successfully completed . We have now 2 computer SlaveTemplate.provisionOndemand ( s SlaveTemplate.java:607 ) Mar 06, 2020 3:05:22 PM INFO at hudson.plugins.ec2. EC2Cloud logConnecting to 10 SlaveTemplate . 20 provisionOndemand(SlaveTemplate . 4.41 on port 22, with timeout 1.Mar 06, 2020 3 java : 05:29 PM INFO 585) at hudson.plugins.ec2. EC2Cloud logConnected via SSH SlaveTemplate . Mar 06, 2020 3 provision(SlaveTemplate.java : 05:29 PM INFO 540) at hudson.plugins.ec2.EC2Cloud logconnect fresh as rootMar 06, 2020 3 .getNewOrExistingAvailableSlave(EC2Cloud.java : 05:29 PM INFO 589) at hudson.plugins.ec2.EC2Cloud logConnecting to 10 . 20 provision(EC2Cloud . 4 java:615) at com . 41 on port 22, with timeout 1 cloudbees . Mar 06, 2020 3:05:30 PM INFO hudson jenkins .plugins. ec2 amazonecs . EC2Cloud logConnected via SSH ECSProvisioningStrategy . Mar 06, 2020 3 apply(ECSProvisioningStrategy.java : 05:30 PM INFO 58) at hudson. plugins slaves . ec2 NodeProvisioner . EC2Cloud logCreating tmp directory update ( /tmp NodeProvisioner.java:332 ) if it does not exist Mar 06, 2020 3:05:30 PM INFO at hudson. plugins slaves . ec2 NodeProvisioner . EC2Cloud logVerifying: access$900(NodeProvisioner. java -fullversionMar 06, 2020 3 : 05:30 PM INFO 63) at hudson. plugins slaves . ec2 NodeProvisioner$NodeProvisionerInvoker . EC2Cloud logVerifying doRun(NodeProvisioner.java : which scp 819) Mar 06, 2020 3:05:3
[JIRA] (JENKINS-61699) NotExportableException in com.nirima.jenkins.plugins.docker.DockerTemplate on job/(.*)/api/json
Title: Message Title Paul Stanley created an issue Jenkins / JENKINS-61699 NotExportableException in com.nirima.jenkins.plugins.docker.DockerTemplate on job/(.*)/api/json Issue Type: Bug Assignee: Nicolas De Loof Components: docker-plugin Created: 2020-03-26 16:17 Environment: Jenkins Version: 2.204.2 Docker Plugin Version: 1.1.9 Priority: Major Reporter: Paul Stanley Calls to https:///job//api/json result in an exception with the message DockerTemplate doesn’t have @ExportBean. This occurs when the “Define a Docker template” option is used in the configuration. Stacktrace: org.kohsuke.stapler.export.NotExportableException: class com.nirima.jenkins.plugins.docker.DockerTemplate doesn't have @ExportedBean at org.kohsuke.stapler.export.Property.writeValue(Property.java:298) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:153) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:302) at org.kohsuke.stapler.export.Property.writeBuffered(Property.java:174) at org.kohsuke.stapler.export.Property.writeValue(Property.java:234) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:153) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:219) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:219) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:219) at
[JIRA] (JENKINS-61695) Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ...
Title: Message Title Prabin Shrestha updated an issue Jenkins / JENKINS-61695 Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ... Change By: Prabin Shrestha Recently I had upgraded Jenkins 2.150.2 to 2.190.3 . When I browse Jenkins using am seeing issue setting the Maven_Opts(in Build/Advanced) in Chrome, or Firefox, the spaces edge browsers. I give space between environment variables set in the text area of Maven_Opts remove and squeeze into one line after maven options. After saving the Jenkins configuration , the spaces between the options are truncated and causing the build to break. But there is no any Before saving the configuration -Ddriver.name=chromeDriver -Dvm.count=0 -Dbuildid=$BUILD_NUMBER After saving the configuration -Ddriver.name=chromeDriver-Dvm.count=0-Dbuildid=$BUILD_NUMBER Same issue while browsing from Internet Explorer and Microsoft Edge exists when the options are given in new line Before saving the configuration -Ddriver . Is there anyone who can provide me solution for this name=chromeDriver -Dvm.count=0 -Dbuildid=$BUILD_NUMBER After saving the configuration -Ddriver.name=chromeDriver-Dvm.count=0-Dbuildid=$BUILD_NUMBERNote: This issue ? is not seen in Internet Explorer Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61695) Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ...
Title: Message Title Prabin Shrestha updated an issue Jenkins / JENKINS-61695 Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ... Change By: Prabin Shrestha Issue Type: Task 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.205520.1585233242000.594.1585240020228%40Atlassian.JIRA.
[JIRA] (JENKINS-61695) Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ...
Title: Message Title Prabin Shrestha updated an issue Jenkins / JENKINS-61695 Maven_Opts text area squeezes into one line in Jenkins Build Configuration using browsers Chrome, Firefox, ... Change By: Prabin Shrestha Recently I had upgraded Jenkins 2.150.2 to 2.190.3 . I am seeing issue setting the Maven_Opts(in Build/Advanced) in Chrome, Firefox, edge browsers. I give space between the maven options. After saving the configuration, the spaces between the options are truncated and causing the build to break.Before saving the configuration -Ddriver.name=chromeDriver -Dvm.count=0 -Dbuildid=$BUILD_NUMBER After saving the configuration -Ddriver.name=chromeDriver-Dvm.count=0-Dbuildid=$BUILD_NUMBER Same issue exists when the options are given in new line Before saving the configuration -Ddriver.name=chromeDriver -Dvm.count=0 -Dbuildid=$BUILD_NUMBER After saving the configuration -Ddriver.name=chromeDriver-Dvm.count=0-Dbuildid=$BUILD_NUMBERNote: This issue is not seen in Internet Explorer Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60530) Adding gitlab MR comment from Jenkinsfile does not work
Title: Message Title Tadeusz Kleszcz commented on JENKINS-60530 Re: Adding gitlab MR comment from Jenkinsfile does not work It is important but not critical. Our use case: We are calculating code coverage during Jenkins build and also the difference between code coverage in source and target branch. Then we are using addGitLabMRComment to add a comment to the GitLab with code coverage statistics. It allows us to easily view of how code coverage will be affected during code review. Some time ago we have switched to Gitlab Branch Source plugin for easier job maintenance in Jenkins and from this time it stopped working. 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.203631.1576689781000.597.1585240140418%40Atlassian.JIRA.
[JIRA] (JENKINS-60530) Adding gitlab MR comment from Jenkinsfile does not work
Title: Message Title Tadeusz Kleszcz updated an issue Jenkins / JENKINS-60530 Adding gitlab MR comment from Jenkinsfile does not work Change By: Tadeusz Kleszcz Priority: Critical Major 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.203631.1576689781000.599.1585240140466%40Atlassian.JIRA.
[JIRA] (JENKINS-61700) Windows upload needs required build_version parameter
Title: Message Title
Sven Jost created an issue
Jenkins / JENKINS-61700
Windows upload needs required build_version parameter
Issue Type:
Bug
Assignee:
Mez Pahlan
Components:
appcenter-plugin
Created:
2020-03-26 16:58
Environment:
LTS Jenkins & .82 version of appcenter plugin
Priority:
Minor
Reporter:
Sven Jost
The upload of a zip file to a UWP/Windows App results in a 400 because build_version is not set:
Creating an upload resource for app.
Create upload resource for app successful.
Uploading app to resource.
io.jenkins.plugins.appcenter.AppCenterException: Upload app to resource unsuccessful: HTTP 400 Bad Request: \{"error":"Error: Missing required params from body: build_version, Service id: 9355f89b-f8f6-42e8-961e-68c4ee11946b"}
at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:23)
at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:37)
at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:71)
Caused: java.util.concurrent.CompletionException
at java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:326)
at java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:338)
at java.util.concurrent.CompletableFuture.uniRelay(CompletableFuture.java:911)
at java.util.concurrent.CompletableFuture$UniRelay.tryFire(CompletableFuture.java:899)
at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
at io.jenk
[JIRA] (JENKINS-61697) Cannot contact node: java.lang.InterruptedException
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-61697 Cannot contact node: java.lang.InterruptedException Change By: Ivan Fernandez Calvo 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205522.1585236635000.605.1585242000461%40Atlassian.JIRA.
[JIRA] (JENKINS-61697) Cannot contact node: java.lang.InterruptedException
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61697 Re: Cannot contact node: java.lang.InterruptedException the short answer is yes if you have a version with more than 6 months a year, there is a lot of improvements relates to stability, log reporting, remoting, ... , the long answer is Which Jenkins core version you have and with plugin version you have, then if you core version is old the problem it is to upgrade a whole Jenkins instance and all the jobs and plugins related, so I'd suggest taking the time and test everything on a test environment and when you are confident make the upgrade. In any case, this is more a support question not an issue please use the google groups for that. https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue 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.205522.1585236635000.603.1585242000405%40Atlassian.JIRA.
[JIRA] (JENKINS-61700) Windows upload needs required build_version parameter
Title: Message Title Sven Jost commented on JENKINS-61700 Re: Windows upload needs required build_version parameter The PR is here: https://github.com/jenkinsci/appcenter-plugin/pull/50 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.205525.1585241897000.698.1585246800121%40Atlassian.JIRA.
[JIRA] (JENKINS-61690) When Running Gcloud commands on jenkins windows agent getting error like "This may be due to network connectivity issues. Please check your network settings, and the status of t
Title: Message Title Mark Waite closed an issue as Not A Defect The Jenkins issue tracker is used to report issues, not to request configuration help. Please use the Jenkins mailing lists and chat channels to request configuration help. Jenkins / JENKINS-61690 When Running Gcloud commands on jenkins windows agent getting error like "This may be due to network connectivity issues. Please check your network settings, and the status of the service you are trying to reach." Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61701) Prometheus plugin exports 0 builds on all slaves
Title: Message Title
Sir Tumbleweed created an issue
Jenkins / JENKINS-61701
Prometheus plugin exports 0 builds on all slaves
Issue Type:
Bug
Assignee:
Marky Jackson
Components:
prometheus-plugin
Created:
2020-03-26 20:37
Environment:
Jenkins ver. 2.204.5 prometheus plugin 2.0.6
Priority:
Minor
Reporter:
Sir Tumbleweed
I wanted to create a dashboard panel to analyze our per-node usage (as they do different things, depending on tags and I might need to scale out differently). Unfortunately, for all nodes (but the master) the plugin exports the following block (with different node name, of course):
jenkins_node_mynode_builds{quantile="0.5",} 0.0
jenkins_node_mynode_builds{quantile="0.75",} 0.0
jenkins_node_mynode_builds{quantile="0.95",} 0.0
jenkins_node_mynode_builds{quantile="0.98",} 0.0
jenkins_node_mynode_builds{quantile="0.99",} 0.0
jenkins_node_mynode_builds{quantile="0.999",} 0.0
jenkins_node_mynode_builds_count 0.0
[JIRA] (JENKINS-61701) Prometheus plugin exports 0 builds on all slaves
Title: Message Title Sir Tumbleweed updated an issue Jenkins / JENKINS-61701 Prometheus plugin exports 0 builds on all slaves Change By: Sir Tumbleweed Environment: Jenkins ver. 2.204.5 (LTS) prometheus plugin 2.0.6 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.205526.1585255071000.709.1585255140244%40Atlassian.JIRA.
[JIRA] (JENKINS-61701) Prometheus plugin exports 0 builds on all slaves
Title: Message Title Marky Jackson commented on JENKINS-61701 Re: Prometheus plugin exports 0 builds on all slaves I have been planning on adding some more to this. I will add this to my upcoming roadmap 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.205526.1585255071000.712.1585255260247%40Atlassian.JIRA.
[JIRA] (JENKINS-61701) Prometheus plugin exports 0 builds on all slaves
Title: Message Title Sir Tumbleweed commented on JENKINS-61701 Re: Prometheus plugin exports 0 builds on all slaves Wow, what a response time. I appreciate your work, thank you very 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.205526.1585255071000.714.1585255380113%40Atlassian.JIRA.
[JIRA] (JENKINS-61701) Prometheus plugin exports 0 builds on all slaves
Title: Message Title Marky Jackson commented on JENKINS-61701 Re: Prometheus plugin exports 0 builds on all slaves Most welcome 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.205526.1585255071000.717.1585255680218%40Atlassian.JIRA.
[JIRA] (JENKINS-61702) Unable to configure new vSphere Nodes
Title: Message Title Adam Talbot created an issue Jenkins / JENKINS-61702 Unable to configure new vSphere Nodes Issue Type: Bug Assignee: Unassigned Attachments: LaunchMethod.png, newSlave.diff, SlaveCreation.png Components: vsphere-cloud-plugin Created: 2020-03-26 21:09 Environment: Jenkins version 2.222.1 vsphere-cloud version 2.23 Priority: Major Reporter: Adam Talbot In vSphere 2.23, the option to create a new Node of the type "Slave virtual computer running under vSphere Cloud" is missing. Additionally, when cloning an existing Node, not all UI components are included and it appears that the launch information is missing. This results in VM launches of this Node failing with a NullPointerException. Attached screenshots of the UI components that are now missing. Also attached a diff of a functional slave configuration and a cloned slave configuration. After reverting the vSphere plugin to version 2.21, we are able to create new vSphere nodes and the launch method option exists again. We suspect that at least the launch method issue could be related to this commit here: https://github.com/jenkinsci/vsphere-cloud-plugin/commit/35f498f3e74cbcf0b977bd2e660c415980d83705#diff-0bfb9f53ca66d82c91b12317c69f0aa9
[JIRA] (JENKINS-61702) Unable to configure new vSphere Nodes
Title: Message Title Adam Talbot updated an issue Jenkins / JENKINS-61702 Unable to configure new vSphere Nodes Change By: Adam Talbot Attachment: newSlave.diff 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.205527.1585256984000.719.1585257540076%40Atlassian.JIRA.
[JIRA] (JENKINS-61702) Unable to configure new vSphere Nodes
Title: Message Title Adam Talbot updated an issue Jenkins / JENKINS-61702 Unable to configure new vSphere Nodes Change By: Adam Talbot Attachment: newSlave.diff 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.205527.1585256984000.720.1585257660062%40Atlassian.JIRA.
[JIRA] (JENKINS-61677) Mark PR as Needs Work when build fails
Title: Message Title Martin Henschke closed an issue as Won't Do Jenkins / JENKINS-61677 Mark PR as Needs Work when build fails Change By: Martin Henschke Status: Open Closed Assignee: Kristy Hughes Martin Henschke Resolution: Won't Do 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.205414.1585126338000.723.1585259460411%40Atlassian.JIRA.
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title Mark Waite started work on JENKINS-61684 Change By: Mark Waite 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.205421.1585146861000.725.1585261140335%40Atlassian.JIRA.
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-61684 Git client plugin automated tests fail with MinGit on Windows Change By: Mark Waite Assignee: Mark Waite 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.205421.1585146861000.724.1585261140286%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61694 Groovy Hooks may run before or after JOB_CONFIG_ADAPTED Change By: Oleg Nenashev Summary: Groovy Hooks will not reliably work with JCasC may run before or after JOB_CONFIG_ADAPTED 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.205519.1585231269000.726.1585264200072%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
Title: Message Title Oleg Nenashev commented on JENKINS-61694 Re: Groovy Hooks may run before or after JOB_CONFIG_ADAPTED https://github.com/jenkinsci/jenkins/pull/4606 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.205519.1585231269000.729.1585264260219%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61694 Groovy Hooks may run before or after JOB_CONFIG_ADAPTED Change By: Oleg Nenashev After introduction a new milestones in the core, JCasC and Groovy hooks will not be aligned properly may run before or after [https://github JOB_CONFIG_ADAPTED depending on how graph is executed . com/jenkinsci/configuration-as-code-plugin/pull/1262] . We need to apply a fix in the Jenkins core to ensure that JCasC and Groovy Hooks still interact in a predictable way.Proposal: * Revert [https://github.com/jenkinsci/jenkins/commit/ab12f71a48901ab3b78521382057a03e166fe668] to the orifginal state so that init hook behaves as before: after all initialization steps * Document Groovy Hooks and explicitly document the state * Consider introducing new hooks for specific items like post-job-initialization 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 Gr
[JIRA] (JENKINS-61694) Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
Title: Message Title Oleg Nenashev updated JENKINS-61694 Jenkins / JENKINS-61694 Groovy Hooks may run before or after JOB_CONFIG_ADAPTED Change By: Oleg Nenashev 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.205519.1585231269000.728.1585264260206%40Atlassian.JIRA.
[JIRA] (JENKINS-61703) This is a test issue
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-61703 This is a test issue Issue Type: Bug Assignee: Marky Jackson Components: anchore-container-scanner-plugin Created: 2020-03-26 23:40 Environment: This is a test issue Priority: Minor Reporter: Marky Jackson This is a test issue Add Comment
[JIRA] (JENKINS-61703) This is a test issue
Title: Message Title Marky Jackson updated JENKINS-61703 Jenkins / JENKINS-61703 This is a test issue Change By: Marky Jackson Status: Open 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.205528.1585266046000.736.1585266300234%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Oleg Nenashev Labels: 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.205516.1585227401000.738.1585266780184%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title
Oleg Nenashev commented on JENKINS-61692
Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
There is no recent changes in Secret.java or Stapler which would cause that behavior AFAICT. I assume that the nll check is missing in the code, but I am not sure what causes it to be passed
static {
Stapler.CONVERT_UTILS.register(new org.apache.commons.beanutils.Converter() {
public Secret convert(Class type, Object value) {
306: return Secret.fromString(value.toString());
} }, Secret.class); }
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.205516.1585227401000.740.1585267140125%40Atlassian.JIRA.
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title Mark Waite updated JENKINS-61684 Jenkins / JENKINS-61684 Git client plugin automated tests fail with MinGit on Windows Change By: Mark Waite 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.205421.1585146861000.741.1585268760156%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Daniel Beck commented on JENKINS-61692 Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException https://jenkins.io/doc/upgrade-guide/2.222/#redesigned-password-form-field ? 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.205516.1585227401000.747.1585271220243%40Atlassian.JIRA.
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-61684 Git client plugin automated tests fail with MinGit on Windows Change By: Mark Waite 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.205421.1585146861000.758.1585273260293%40Atlassian.JIRA.
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title Mark Waite updated JENKINS-61684 Jenkins / JENKINS-61684 Git client plugin automated tests fail with MinGit on Windows Change By: Mark Waite Status: In Review Resolved 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.205421.1585146861000.757.1585273260226%40Atlassian.JIRA.
[JIRA] (JENKINS-61704) jenkins pipeline job no permission to config bitbucket-server-integration plugin
Title: Message Title roy zhou created an issue Jenkins / JENKINS-61704 jenkins pipeline job no permission to config bitbucket-server-integration plugin Issue Type: Bug Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-03-27 03:25 Environment: Jenkins: 2.204.2.2 Folder plugin: 6.9 Bitbucket server integration plugin: 1.1.0 Priority: Major Reporter: roy zhou We are using foler level permission and application teams are granted with job configure permission, they can create jenkins pipeline job using the git plugin. When we switch to the Bitbucket server integration plugin it keeps showing no job configure permission. The issue only happen when we use the plugin in pipeline jobs, freestyle job does not have the issue. I found similar issue reported in Jenkins-60116 and Jenkins-60490 and the 2 tickets are closed. we already at the latest version of the plugin but still have the issue. PS: the jenkins admin can set up pipeline job with Bitbucket server integration plugin but it is giving the privilege permission to application team and violate our design.
[JIRA] (JENKINS-61596) http client in jenkins swarm badly verifies hostname in SSL certificate
Title: Message Title Basil Crow assigned an issue to Basil Crow Jenkins / JENKINS-61596 http client in jenkins swarm badly verifies hostname in SSL certificate Change By: Basil Crow Assignee: Basil Crow 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.205293.1584662414000.790.1585279680573%40Atlassian.JIRA.
[JIRA] (JENKINS-61596) http client in jenkins swarm badly verifies hostname in SSL certificate
Title: Message Title Basil Crow started work on JENKINS-61596 Change By: Basil Crow 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.205293.1584662414000.788.1585279680544%40Atlassian.JIRA.
[JIRA] (JENKINS-61596) http client in jenkins swarm badly verifies hostname in SSL certificate
Title: Message Title Basil Crow updated JENKINS-61596 Jenkins / JENKINS-61596 http client in jenkins swarm badly verifies hostname in SSL certificate Change By: Basil Crow 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.205293.1584662414000.792.1585279680595%40Atlassian.JIRA.
[JIRA] (JENKINS-61596) http client in jenkins swarm badly verifies hostname in SSL certificate
Title: Message Title Basil Crow updated JENKINS-61596 This seems to be fixed by jenkinsci/swarm-plugin#190. Jenkins / JENKINS-61596 http client in jenkins swarm badly verifies hostname in SSL certificate Change By: Basil Crow 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
[JIRA] (JENKINS-60143) Behaviour SSH Checkout not working after Jenkins restart
Title: Message Title ipleten commented on JENKINS-60143 Re: Behaviour SSH Checkout not working after Jenkins restart Here is a similar issue https://issues.jenkins-ci.org/browse/JENKINS-59753 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.203004.1573562285000.797.1585279860201%40Atlassian.JIRA.
[JIRA] (JENKINS-44115) Enable Remoting working directories by default in Swarm plugin
Title: Message Title Basil Crow updated JENKINS-44115 Released in 3.19. Jenkins / JENKINS-44115 Enable Remoting working directories by default in Swarm plugin Change By: Basil Crow Status: Fixed but Unreleased Resolved Assignee: Basil Crow Released As: 3.19 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to th
[JIRA] (JENKINS-61596) http client in jenkins swarm badly verifies hostname in SSL certificate
Title: Message Title Basil Crow updated JENKINS-61596 Released in 3.19. Can you please confirm that this release addresses the problem? Thank you! Jenkins / JENKINS-61596 http client in jenkins swarm badly verifies hostname in SSL certificate Change By: Basil Crow Status: Fixed but Unreleased Resolved Released As: 3.19 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+unsub
