[JIRA] (JENKINS-41515) Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype
Title: Message Title Pavel Georgiev edited a comment on JENKINS-41515 Re: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype This issue seems to be the cause of this one (gitab plugin : [https://github.com/jenkinsci/gitlab-plugin/issues/430|https://github.com/jenkinsci/gitlab-plugin/issues/430] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41515) Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype
Title: Message Title Pavel Georgiev commented on JENKINS-41515 Re: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype This issue seems to be the cause of this one: Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42199) withMaven() should be integrated with Takari's Maven Wrapper as it is with the "mvn" launcher
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-42199
withMaven() should be integrated with Takari's Maven Wrapper as it is with the "mvn" launcher
Change By:
Cyrille Le Clerc
"{{withMaven(){...\}}}" should integrate [Takari's Maven Wrapper|https://github.com/takari/maven-wrapper] so that usage of the launcher "{{mvnw}}" in a "{{withMaven(){...\}}}" wrapper would behave similarly to the launcher "{{mvn}}" (inject settings file, global settings file, --batch-mode...).It can probably be implemented injecting in the environment variable "{{ MAVEN_CONFIG MAVEN_OPTS }}" our Maven params.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42563) Calling super.method(...) in shared library fails with CpsCallableInvocation
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-42563
Calling super.method(...) in shared library fails with CpsCallableInvocation
Change By:
Reinhold Füreder
My goal was to create some abstractions in shared (global pipeline) library so that in the Jenkinsfile I only have the configuration of the build, whereas the re-usable build script logic is fully in the library; so very much like the Section [https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-a-more-structured-dsl.]In the shared library I use simple class inheritance, but the call to a super method fails with CpsCallableInvocation.This is the stacktrace:{noformat}hudson.remoting.ProxyException: org.codehaus.groovy.runtime.InvokerInvocationException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:100) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1218) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.superCall(DefaultInvoker.java:29) at com.acme.B1.build(file:/var/lib/jenkins/jobs/Pipeline-Using-Shared-Library/builds/187/libs/**-shared-library/src/com/acme/B1.groovy:21) at acme.b1(/var/lib/jenkins/jobs/Pipeline-Using-Shared-Library/builds/187/libs/**-shared-library/vars/acme.groovy:9) at WorkflowScript.run(WorkflowScript:18) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:54) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor273.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46) at com.cloudbees.groovy.cps.Next.step(Next.java:74) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) a
[JIRA] (JENKINS-42563) Calling super.method(...) in shared library fails with CpsCallableInvocation
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-42563 Calling super.method(...) in shared library fails with CpsCallableInvocation Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2017/Mar/08 6:40 AM Environment: Jenkins 2.49, Pipeline-Groovy Plugin 2.29 and everything related also latest versions Priority: Major Reporter: Reinhold Füreder My goal was to create some abstractions in shared (global pipeline) library so that in the Jenkinsfile I only have the configuration of the build, whereas the re-usable build script logic is fully in the library; so very much like the Section https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-a-more-structured-dsl. In the shared library I use simple class inheritance, but the call to a super method fails with CpsCallableInvocation. This is the stacktrace: hudson.remoting.ProxyException: org.codehaus.groovy.runtime.InvokerInvocationException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:100) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1218) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.superCall(DefaultInvoker.java:29) at com.acme.B1.build(file:/var/lib/jenkins/jobs/Pipeline-Using-Shared-Library/builds/187/libs/**-shared-library/src/com/acme/B1.groovy:21) at acme.b1(/var/lib/jenkins/jobs/Pipeline-Using-Shared-Library/builds/187/libs/**-shared-library/vars/acme.groovy:9) at WorkflowSc
[JIRA] (JENKINS-40429) Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
Title: Message Title Matt Evans commented on JENKINS-40429 Re: Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy" Luke Peterson The copy artifacts project name doesn't have any quotes around it. This is in the config for a freeform project that copies the artifacts from a multi-branch pipeline project. I tried putting double quotes around the project name property value but that didn't work Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40429) Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
Title: Message Title
Luke Peterson commented on JENKINS-40429
Re: Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
Make sure you're using double quotes in the parameter that contains the branchName. For example: projectName: "my-project-name/${env.BRANCH_NAME}" as opposed to projectName: 'my-project-name/${env.BRANCH_NAME}'.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42562) Error: JAVA_HOME not found in your environment
Title: Message Title Andre Richards created an issue Jenkins / JENKINS-42562 Error: JAVA_HOME not found in your environment Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2017/Mar/08 4:57 AM Environment: GitHub plugin, Chrome, Jenkins 1.642.3 Priority: Blocker Reporter: Andre Richards When running the build for my first maven project, it fails and the console says "Error: JAVA_HOME not found in your environment." I've set it in the Environmental Variables of my computer to the and mvn --v shows the variable set to C:\Program Files (x86)\Java\jre1.8.0_121. PATH is set to C:\Program Files (x86)\Maven\apache-maven-3.3.9\bin;%JAVA_HOME%\bin;. This is my first time using Jenkins so I'm not very savvy on how this all goes so I'm sorry if I'm not describing this issue accurately. Add Comment
[JIRA] (JENKINS-42549) Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-42549 Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception Change By: Mark Waite Component/s: maven-plugin Component/s: core Component/s: git-client-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-33607) getServerLicenseData: no corresponding wsdl operation
Title: Message Title Eric Lordahl commented on JENKINS-33607 Re: getServerLicenseData: no corresponding wsdl operation Caleb Chenoweth, which commit are you attempting to build? Their release path is not linear, which makes for some messy upgrades if you're running custom builds. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13107) Android NDK support not present for auto-dependency download
Title: Message Title Christopher Orr commented on JENKINS-13107 Re: Android NDK support not present for auto-dependency download I haven't done any work on this, though I see now that the new sdkmanager command-line tool does provide a way to install the NDK automatically. The plugin will need to be updated to migrate away from the deprecated android tool anyway, so we can use this tool, but it's not clear when it should be called. Nowadays, the Android Gradle plugin automatically installs the required build tools, platform and support library dependencies for you, so the functionality in this plugin isn't required (and it only works with Ant builds). But I imagine that the NDK isn't automatically installed by the plugin. So, assuming that's the case, going back to my previous question: what do you expect the workflow to look like? At what point should the NDK be installed, in which circumstances, and how? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41352) New dashboard cards
Title: Message Title Josh McDonald started work on JENKINS-41352 Change By: Josh McDonald Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Vivek Pandey commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan Stephen Connolly I guess I need github-branch-source-2.0.4-beta-1? Because in 2.0.3, I don't see this optimization as its calling GitHub.listRepositories(). So we need to do both, create single repo in OrganizationFolder and update to OrganizationFolder. For creation, I think I should be using SCMSourceEvent and for update SCMNavigatorEvent, right? An example of each use case will be very helpful as its not clear what would go for example as payload when creating an SCMEvent. Looks like I may have to create GHRepository to use GHEventPayload.Create, but then I need to create instance of GHRepository, right? this will be few round trips to GitHub, but I guess it will be used as it is later on? I think it will be lot simpler if you could provide samples on how to go about it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42561) Users should be able to custom configure the timeout on pipeline build wrappers/steps
Title: Message Title Lucas Machado updated an issue Jenkins / JENKINS-42561 Users should be able to custom configure the timeout on pipeline build wrappers/steps Change By: Lucas Machado Summary: Users should be able to custom configure the timeout on pipeline build step wrappers/steps Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42561) Users should be able to configure the timeout on pipeline build step
Title: Message Title Lucas Machado created an issue Jenkins / JENKINS-42561 Users should be able to configure the timeout on pipeline build step Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2017/Mar/08 2:01 AM Priority: Minor Reporter: Lucas Machado As part of JENKINS-32986 pipeline cps plugin has introduced a 5 min timeout for each instruction on the script. Custom scripts that are implemented as jenkins.tasks.BuildWrapper are now subject to this limitation. As BuildWrappers are a very useful and common extension point it seems to me that Jenkins administrators should be able to increase this hard coded timeout by passing a configuration (maybe a -D vm param) OR (even better) developers that are writing Build wrappers can provide something like a max timeout hint to cps treat it properly (maybe by implementing an interface or an annotation). This change on behavior from 2.4 to 2.5 pipeline jenkins broke our plugin on some use cases. As DurableSteps (that are not subject to this limitation) are "steps" not "wrappers" I cannot see how to change our implementation to some structure that acts as a wrapper without touch the 5 min limitation. Relevant commit https://github.com/jenkinsci/workflow-cps-plugin/commit/c0deed0a3b546ebcb59ea25681ed3ac8b13fe6bb
[JIRA] (JENKINS-42549) Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception
Title: Message Title Mark Waite commented on JENKINS-42549 Re: Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception As far as I can tell from the stack trace, this has nothing to do with the git plugin. If you can provide detailed steps to duplicate the problem, it will help whoever eventually needs to fix it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42549) Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-42549 Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42555) Allow host name alias for Git notifyCommit URLs
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-42555 Allow host name alias for Git notifyCommit URLs Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title Lars Lawoko commented on JENKINS-40825 Re: "Pipe not connected" errors when running multiple builds simultaneously We have been having this issue, and did an investigation. It seems to be failing on pipe write in the first "cd" command to get the workspace. From what we understand the underlying kubernetes-client library does not expose a stable connection. From what we understand the latch was implemented wrongly (?? We think). The latch is initialized once in the `container` "start" method, but a new connection is opened for each `sh` step. This causes the "waitQuietly" to pass through straight away without waiting, on all sh connections but the first. Once we fixed this the "OnOpen" callback in the websocket is never called, indicating the connection is not made, and the latch was only passed on thread interrupt. At this stage we didn't dig deeper, but hopefully this is a good starting point. Instead we switched to embedding jnlp into our main container using the "jnlp" container name "hack" to workaround this code. TL;DR Embedding jnlp into your main container using the "jnlp" container name "hack" will workaround this issue code. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41365) Pipeline with Bitbucket sources do not show Pull Requests on the Pull Requests tab
Title: Message Title E G commented on JENKINS-41365 Re: Pipeline with Bitbucket sources do not show Pull Requests on the Pull Requests tab Could it have to do with JENKINS-40581? I have the same problem and even the vanilla view does not show the PR tab. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Vivek Pandey started work on JENKINS-42450 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42560) unable to install ATH on macos
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-42560 unable to install ATH on macos Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/08 12:40 AM Priority: Major Reporter: Michael Neale When installing the ATH on osx, some users see this type of error: https://gist.github.com/sophistifunk/c73e0d635dac84d7d796559ae12c0dd7 Installing the required dependencies on OSX is not documented (and past techniques don't seem to work on fresh installs). This seems required by nodegit only. Nodegit has also been a problem (see Vivek Pandey) with failures with signatures (still trying to get the specific error message for that). Nodegit is presumably used to test multibranch (the equivalent in unit test code doesn't have this problem, it also uses a git client but doesn't seem as problematic as nodegit). Perhaps nodegit should be replaced with direct calls to the git client via shell scripting (given that seems to be mostly what it does anyway). Add Comment
[JIRA] (JENKINS-5820) Add the possibility to configure authorities based on Active Directory and View in hudson
Title: Message Title Félix Belzunce Arcos closed an issue as Fixed This issue is very old and what is more important should not have been opened against the ad-plugin. Jenkins / JENKINS-5820 Add the possibility to configure authorities based on Active Directory and View in hudson Change By: Félix Belzunce Arcos Status: Open Closed Assignee: Félix Belzunce Arcos Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-7254) Active directory groups should be selectable for maxtix based auth
Title: Message Title Félix Belzunce Arcos closed an issue as Fixed Pretty old issue. Right now you can add the ad groups you want, but you need to know the name before. List all the groups is a very bad practice, it could add thousands of groups - and what it worse I am not even sure if this might be a security issue. Jenkins / JENKINS-7254 Active directory groups should be selectable for maxtix based auth Change By: Félix Belzunce Arcos Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subs
[JIRA] (JENKINS-21318) Add ability to modify email address of user
Title: Message Title Félix Belzunce Arcos closed an issue as Fixed It will be released in 2.1 Jenkins / JENKINS-21318 Add ability to modify email address of user Change By: Félix Belzunce Arcos Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42531) Failed to parse POMs:-remote file operation failed-stackOverFlow
Title: Message Title Arnaud Héritier assigned an issue to Arnaud Héritier Jenkins / JENKINS-42531 Failed to parse POMs:-remote file operation failed-stackOverFlow Change By: Arnaud Héritier Assignee: Arnaud Héritier Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42531) Failed to parse POMs:-remote file operation failed-stackOverFlow
Title: Message Title Arnaud Héritier commented on JENKINS-42531 Re: Failed to parse POMs:-remote file operation failed-stackOverFlow Hi fadi hussein It seems you are using maven-plugin 2.13. You're issue seems to be JENKINS-41697 which is fixed in 2.15.1 Best regards Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21318) Add ability to modify email address of user
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-21318 Add ability to modify email address of user Change By: Félix Belzunce Arcos URL: https://github.com/jenkinsci/active-directory-plugin/pull/57 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21318) Add ability to modify email address of user
Title: Message Title Félix Belzunce Arcos assigned an issue to Félix Belzunce Arcos Jenkins / JENKINS-21318 Add ability to modify email address of user Change By: Félix Belzunce Arcos Assignee: Félix Belzunce Arcos Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21073) Fix forceLdaps system property
Title: Message Title Félix Belzunce Arcos closed an issue as Fixed Released since active-directory-1.34 Jenkins / JENKINS-21073 Fix forceLdaps system property Change By: Félix Belzunce Arcos Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35643) ldaps authentication fails
Title: Message Title Félix Belzunce Arcos closed an issue as Fixed Stacktrace not even related to the active directory plugin. Jenkins / JENKINS-35643 ldaps authentication fails Change By: Félix Belzunce Arcos Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/
[JIRA] (JENKINS-26899) Multiple domain authentication when not part of the same forest
Title: Message Title Félix Belzunce Arcos closed an issue as Fixed Version 2.0 provides a good multidomain support from the UI. Jenkins / JENKINS-26899 Multiple domain authentication when not part of the same forest Change By: Félix Belzunce Arcos Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more optio
[JIRA] (JENKINS-8119) Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does not
Title: Message Title Félix Belzunce Arcos closed an issue as Fixed This issue is against a very old version of the plugin and I have not seen this issue. I'm closing this ticket. Please, re-open if this issue is still happening. Jenkins / JENKINS-8119 Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does not Change By: Félix Belzunce Arcos Status: Reopened Closed Assignee: Kohsuke Kawaguchi Félix Belzunce Arcos Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-26263) Active Directory Plugin Version 1.39 is not working with Jenkins version 1.580.1
Title: Message Title Félix Belzunce Arcos closed an issue as Fixed 1.39 is very prehistory. There are not log attached and no steps about how to reproduce it. If the issue persists, please provide more information about what is the issue about and how to reproduce it. Jenkins / JENKINS-26263 Active Directory Plugin Version 1.39 is not working with Jenkins version 1.580.1 Change By: Félix Belzunce Arcos Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins I
[JIRA] (JENKINS-39776) Perform test per domain
Title: Message Title Félix Belzunce Arcos resolved as Fixed Will be released in 2.1 Jenkins / JENKINS-39776 Perform test per domain Change By: Félix Belzunce Arcos Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39776) Perform test per domain
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-39776 Perform test per domain Change By: Félix Belzunce Arcos URL: https://github.com/jenkinsci/active-directory-plugin/pull/56 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40599) AD descriptor saved without any domain make Jenkins not to start
Title: Message Title Félix Belzunce Arcos resolved as Fixed This is going to be released in version 2.1 Jenkins / JENKINS-40599 AD descriptor saved without any domain make Jenkins not to start Change By: Félix Belzunce Arcos Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit http
[JIRA] (JENKINS-18961) LDAP plugin does not support nested groups
Title: Message Title Emory Penney commented on JENKINS-18961 Re: LDAP plugin does not support nested groups Wow, that query is slow. So slow my login attempts time out when I try to use it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42559) run job button (pull-request) error -- createRunStartedToast: TypeError: Cannot read property 'self' of undefined
Title: Message Title Chance Zibolski created an issue Jenkins / JENKINS-42559 run job button (pull-request) error -- createRunStartedToast: TypeError: Cannot read property 'self' of undefined Issue Type: Bug Assignee: Unassigned Attachments: about.md Components: blueocean-plugin Created: 2017/Mar/07 11:44 PM Environment: BlueOcean 1.0.0-b25 Jenkins 2.47 Google Chrome 56.0.2924.87 MacOS 10.12.1 about.md is the about.md from the support bundle plugin. Labels: blueocean Priority: Major Reporter: Chance Zibolski When clicking the "play/run" button on a job in the blueocean to build a particular pull-request, i get the following _javascript_ error in my developer console, and server logs don't have anything at all related to this job: blueocean.js:306 Uncaught (in promise) TypeError: Cannot read property 'self' of undefined at Object.createRunStartedToast (blueocean.js:306) at blueocean.js:3734 createRunStartedToast @ blueocean.js:306 (anonymous) @ blueocean.js:3734
[JIRA] (JENKINS-39479) Jenkins does not show test result information for maven release build
Title: Message Title Thomas Spencer resolved as Not A Defect Jenkins / JENKINS-39479 Jenkins does not show test result information for maven release build Change By: Thomas Spencer Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39479) Jenkins does not show test result information for maven release build
Title: Message Title Thomas Spencer commented on JENKINS-39479 Re: Jenkins does not show test result information for maven release build After further research and testing, this is not a Jenkins or plugin issue. This is a side effect of the way the maven release plugin works. As it is doing a release, it forks new maven processes with it's own set of goals. The new processes do not have the jacoco goal in it. To have the forked processes run it, it must be passed in using parameters. The following parameters execute it as expected. -DpreparationGoals="jacoco:prepare-agent clean verify" -Dgoals="jacoco:prepare-agent deploy" Add these on to the plugin config in your job and the results will be generated during the release. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29544) Remove MavenProject Dependency
Title: Message Title Victor Martinez closed an issue as Fixed Jenkins / JENKINS-29544 Remove MavenProject Dependency Change By: Victor Martinez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29427) MsBuildBuilder cannot be cast to hudson.tasks.CommandInterpreter
Title: Message Title Victor Martinez closed an issue as Fixed Jenkins / JENKINS-29427 MsBuildBuilder cannot be cast to hudson.tasks.CommandInterpreter Change By: Victor Martinez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29418) Project dependency with ws-cleanup plugin
Title: Message Title Victor Martinez closed an issue as Fixed Jenkins / JENKINS-29418 Project dependency with ws-cleanup plugin Change By: Victor Martinez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29545) Remove WS-Cleanup Dependency
Title: Message Title Victor Martinez closed an issue as Fixed Jenkins / JENKINS-29545 Remove WS-Cleanup Dependency Change By: Victor Martinez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30725) BuildTimeOut check
Title: Message Title Victor Martinez closed an issue as Fixed Jenkins / JENKINS-30725 BuildTimeOut check Change By: Victor Martinez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29546) Remove Git Dependency
Title: Message Title Victor Martinez closed an issue as Fixed Jenkins / JENKINS-29546 Remove Git Dependency Change By: Victor Martinez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42383) Maven and javadoc Plugin dependencies are not required when using reflection
Title: Message Title Victor Martinez closed an issue as Fixed Jenkins / JENKINS-42383 Maven and javadoc Plugin dependencies are not required when using reflection Change By: Victor Martinez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42337) Timer Trigger with @ should be supported
Title: Message Title Victor Martinez closed an issue as Fixed Jenkins / JENKINS-42337 Timer Trigger with @ should be supported Change By: Victor Martinez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38616) Missing prebuilders actions when running jenkins lint
Title: Message Title Victor Martinez closed an issue as Fixed Jenkins / JENKINS-38616 Missing prebuilders actions when running jenkins lint Change By: Victor Martinez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31392) Jenkins groovy script to get triggered build number
Title: Message Title Moshe Zvi commented on JENKINS-31392 Re: Jenkins groovy script to get triggered build number One addition to the above: If you're going to use the html link in the description (thank, pixman20!), you need to enable HTML in the Markup Formatter. Manage Jenkins > Configure Global Security > Markup Formatter - select something other than text. See also: http://stackoverflow.com/questions/18867232/which-html-is-supported-in-jenkins-job-description?rq=1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42337) Timer Trigger with @ should be supported
Title: Message Title Victor Martinez resolved as Fixed Jenkins / JENKINS-42337 Timer Trigger with @ should be supported Change By: Victor Martinez Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42447) Console ouput stops logging after Linux session starts in Java
Title: Message Title Saul Figueroa updated an issue Jenkins / JENKINS-42447 Console ouput stops logging after Linux session starts in Java Change By: Saul Figueroa Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42001) Blue Ocean logo should be Jenkins
Title: Message Title Ivan Meredith updated JENKINS-42001 Jenkins / JENKINS-42001 Blue Ocean logo should be Jenkins Change By: Ivan Meredith Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42120) Revisit Git repository creation flow credential setup
Title: Message Title James Dumay commented on JENKINS-42120 Re: Revisit Git repository creation flow credential setup Thanks for the update Cliff Meyers - no rush Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42557) Reactive reference value not available to downstream AC parameter
Title: Message Title
Ioannis Moutsatsos updated an issue
Jenkins / JENKINS-42557
Reactive reference value not available to downstream AC parameter
Change By:
Ioannis Moutsatsos
There appear to be cases where the value of an input style Reactive Reference is not available to Active Choices downstream. The AC-Reactive Reference (lets call it REFA) returns formatted HTML with a simple Groovy script: {code:java}html='''xtPlan refA " name="value" value="" class="setting-input" type="text" />'''return html{code} Before a downstream AC references the REFA value, the value is updated with a _javascript_ button generated by an AC-Reactive Reference (lets call it JS_ACTION) using code like this: {code:java}html="""
/* Function modifies value of REFA */
function modifyAction() {
document.getElementById("refA").setAttribute("value",'MODIFIED BY _javascript_');
parentId=document.getElementById("refA").parentNode.id
jQuery('#'+parentId).trigger('change')
}
"""return html{code} Downstream another AC -Reactive Reference (lets call it REFB) is trying to use the value but of REFA but it seems to be null. The downstream AC REFB parameter uses code like this the one shown below to guard for when REFA does not exist . The error is only generated when REFA has a value and so it is passed to the script binding. Otherwise the logic correctly bypasses the code that is using REFA. {code:java}if (!binding.variables.containsKey("REFA")){// do something with REFA -throws an NPE only when the REFA value is set}{code}Surprisingly, the AC-Reactive Reference value is correctly passed to the build. * The problem is it can't be used to drive other AC-parameters on the UI. * I have tried to document this with a simple use case, but I don't seem able to reproduce it. Most of the ideas I had as to the underlying causes were exhausted in trying to setup a test case without a useful test. Sorry, I'll try some more , but I wanted to document this as others may experience something similar.
Add Comment
[JIRA] (JENKINS-13768) default parameter values are ignored when triggering parameterized build from groovy post-build script
Title: Message Title Jesse Glick commented on JENKINS-13768 Re: default parameter values are ignored when triggering parameterized build from groovy post-build script Core is behaving as designed. If the Groovy Postbuild plugin wishes to offer a convenience method to build another job with with some parameters set, it can do so. That would duplicate functionality already available in Pipeline, of course. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13768) default parameter values are ignored when triggering parameterized build from groovy post-build script
Title: Message Title Jesse Glick assigned an issue to wolfs Jenkins / JENKINS-13768 default parameter values are ignored when triggering parameterized build from groovy post-build script Change By: Jesse Glick Component/s: groovy-postbuild-plugin Component/s: core Assignee: wolfs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42558) Option to not include Ip addresses in support bundle
Title: Message Title Virginia Pierson created an issue Jenkins / JENKINS-42558 Option to not include Ip addresses in support bundle Issue Type: New Feature Assignee: Unassigned Components: core Created: 2017/Mar/07 9:25 PM Priority: Minor Reporter: Virginia Pierson We'd like to have the option of not including IP addresses in support bundles in order to better align with our compliance requirements. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42557) Reactive reference value not available to downstream AC parameter
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-42557 Reactive reference value not available to downstream AC parameter Change By: Ioannis Moutsatsos Summary: Reactive reference value not available and does not trigger update to downstream AC parameter Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42557) Reactive reference value not available and does not trigger update
Title: Message Title
Ioannis Moutsatsos created an issue
Jenkins / JENKINS-42557
Reactive reference value not available and does not trigger update
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Components:
active-choices-plugin
Created:
2017/Mar/07 9:22 PM
Environment:
Active-Choices v1.5.2
Priority:
Minor
Reporter:
Ioannis Moutsatsos
There appear to be cases where the value of an input style Reactive Reference is not available to Active Choices downstream. The AC-Reactive Reference (lets call it REFA) returns formatted HTML with a simple Groovy script:
html='''"xtPlan" name="value" class="setting-input" type="text" />'''
return html
Downstream another AC is trying to use the value but REFA seems to be null. The downstream AC parameter uses code like this to guard for when REFA does not exist
if (!binding.variables.containsKey("REFA")){
// do something with REFA -throws an NPE only when the REFA value is set
}
Surprisingly, the AC-Reactive Reference value is correctly passed to the build. The problem is it can't be used to drive other AC-parameters on the UI. I have tried to document this with a simple use case, but I don't seem able to reproduce it. Most of the id
[JIRA] (JENKINS-42556) TryRepeatedly fails to run as ACL.SYSTEM
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-42556 TryRepeatedly fails to run as ACL.SYSTEM Issue Type: Bug Assignee: Unassigned Components: workflow-support-plugin Created: 2017/Mar/07 9:17 PM Priority: Major Reporter: Jesse Glick Resuming build at ... after Jenkins restart [Pipeline] End of Pipeline java.io.IOException: Failed to load build state at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:610) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:608) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:651) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) at ... Caused by: org.acegisecurity.AccessDeniedException: Please login to access job ... at jenkins.model.Jenkins.getItem(Jenkins.java:2724) at jenkins.model.Jenkins.getItem(Jenkins.java:324) at jenkins.model.Jenkins.getItemByFullName(Jenkins.java:2830) at hudson.model.Run.fromExternalizableId(Run.java:2314) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.runForDisplay(ExecutorStepExecution.java:385) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.getDisplayName(ExecutorStepExecution.java:398) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.getFullDisplayName(ExecutorStepExecution.java:407) at org.jenkinsci.plugins.workflow.support.pickles.ExecutorPickle$1.printWaitingMessage(ExecutorPickle.java:116) at org.jenkinsci.plugins.workflow.support.pickles.TryRepeatedly$1.run(TryRepeatedly.java:95) at ... Presumably th
[JIRA] (JENKINS-42555) Allow host name alias for Git notifyCommit URLs
Title: Message Title michael giroux created an issue Jenkins / JENKINS-42555 Allow host name alias for Git notifyCommit URLs Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2017/Mar/07 9:12 PM Environment: Jenkins 2.32.2, Linux Redhat EL7, Java 1.8.0_121 Priority: Minor Reporter: michael giroux Recently upgraded from Atlassian Stash to Atlassian Bitbucket Server. At that time, we updated the host name from 'stash' to 'bitbucket' to provide a URL consistent with the tool name. This has the adverse effect of breaking the Stash Webhook To Jenkins in that the notifyCommit messages include the Bitbucket Server base URL which has now changed from stash.xxx.xx to bitbucket.xxx.xx. It would be nice if the Git plugin allowed to configure alias names for the git host such that notifyCommit for 'stash.xxx.xx/some/repository' would trigger polling for all associated host aliases. This would eliminate the need to do a bulk edit on the Jenkins jobs to reconfigure the git urls. Add Comment
[JIRA] (JENKINS-38132) Pipeline support
Title: Message Title Mark Bidewell commented on JENKINS-38132 Re: Pipeline support In a pipeline you can accomplish this by setting currentBuild.description in you groovy script. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
dan tran edited a comment on JENKINS-40484
Re: Unable to use withMaven step inside docker container
here is my simple pipeline script running against 2.32.3. This time it has a different error [pipeline-test] Running shell scriptenv: nohup: No such file or directory \{code :xml }pipeline \{ agent \{ docker \{ image "maven" } } stages \{ stage("run") \{ steps \{ withMaven( mavenSettingsConfig: 'maven-user', globalMavenSettingsConfig: 'maven- global', mavenLocalRepo: '.repository') \{ sh "echo hello" } } } } } {code:java} {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
dan tran edited a comment on JENKINS-40484
Re: Unable to use withMaven step inside docker container
here is my simple pipeline script running against 2.32.3. This time it has a different error [pipeline-test] Running shell script env: nohup: No such file or directory \{code:xml}pipeline \{agent \{ docker \{ image "maven" } }stages \{stage("run") \{ steps \{ withMaven( mavenSettingsConfig: 'maven-user', globalMavenSettingsConfig: 'maven-global', mavenLocalRepo: '.repository') \{ sh "echo hello"} } }}} {code:java} {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
dan tran edited a comment on JENKINS-40484
Re: Unable to use withMaven step inside docker container
here is my simple pipeline script running against 2.32.3. This time it has a different error [pipeline-test] Running shell scriptenv: nohup: No such file or directory < \{ code > fomrat=xml} pipeline \{agent \{docker \{image "maven"}}stages \{stage("run") \{steps \{withMaven( mavenSettingsConfig: 'maven-user', globalMavenSettingsConfig: 'maven-global', mavenLocalRepo: '.repository') \{sh "echo hello"} {code:java} < { code > }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
dan tran edited a comment on JENKINS-40484
Re: Unable to use withMaven step inside docker container
here is my simple pipeline script running against 2.32.3. This time it has a different error [pipeline-test] Running shell script env: nohup: No such file or directory \{code fomrat= : xml}pipeline \{agent \{ docker \{ image "maven" } }stages \{stage("run") \{ steps \{ withMaven( mavenSettingsConfig: 'maven-user', globalMavenSettingsConfig: 'maven-global', mavenLocalRepo: '.repository') \{ sh "echo hello"} } }}} {code:java} {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
dan tran edited a comment on JENKINS-40484
Re: Unable to use withMaven step inside docker container
here is my simple pipeline script running against 2.32.3. This time is it has differente a different error ( nohub not found) [pipeline-test] Running shell scriptenv: nohup: No such file or directory pipeline \{agent \{docker \{image "maven"}}stages \{stage("run") \{steps \{withMaven( mavenSettingsConfig: 'maven-user', globalMavenSettingsConfig: 'maven-global', mavenLocalRepo: '.repository') \{sh "echo hello"}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
dan tran commented on JENKINS-40484
Re: Unable to use withMaven step inside docker container
here is my simple pipeline script running against 2.32.3. This time is has differente error ( nohub not found) [pipeline-test] Running shell script env: nohup: No such file or directory pipeline { agent { docker { image "maven" } } stages { stage("run") { steps { withMaven( mavenSettingsConfig: 'maven-user', globalMavenSettingsConfig: 'maven-global', mavenLocalRepo: '.repository') { sh "echo hello" } } } } }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title dan tran updated an issue Jenkins / JENKINS-40484 Unable to use withMaven step inside docker container Change By: dan tran Attachment: image-2017-03-07-12-58-37-245.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title dan tran updated an issue Jenkins / JENKINS-40484 Unable to use withMaven step inside docker container Change By: dan tran Attachment: image-2017-03-07-12-58-37-245.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34395) Support for building tags
Title: Message Title David Kowis commented on JENKINS-34395 Re: Support for building tags Ohhh, maybe I'm wrong. https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMProbe.java#L60-L65 There's some assumptions that the ref always starts with `refs/heads` and is parsed out, so a tag will come in as `refs/heads/refs/tags/`. Obviously that isn't going to work. If the SCMProbe is the thing that actually triggers a build, this might be all that's needed to fix it. We should probably have a thing that handles the tag bit so that way we can check out an actual tag, but it's probably not good to have tag parsing logic in more than one place. Still learning things and you might get a few more play-by-play comments Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42490) 500 error when unfavoriting a Pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42490 500 error when unfavoriting a Pipeline Change By: James Dumay *Steps to reproduce*# create a multi branch pipeline# go to classic, favourite the Folder# go to Blue Ocean and try to remove it as a favourite*What should happen*A favourited folder should never show up as a favourite in Blue Ocean*Original request* I am only able to reproduce this with one specific Pipeline on ci.jenkins.io, and I'm not sure why. I think I might need to pair with [~tscherler] again to debug this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34395) Support for building tags
Title: Message Title David Kowis commented on JENKINS-34395 Re: Support for building tags tl;dr: I don't think this is actually a problem in the github-branch-source plugin (but I'm not an expert). This is hitting me too, for all the same reasons everyone is mentioning. I spent some time looking at the assigned component, but I wasn't able to find anything that actually prevented it from running a build based on tags. https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/PushGHEventSubscriber.java#L231-L243 I cannot find anything in there that would short circuit it if the options are enabled. This would, I think, trigger a build. I don't think the problem exists in here, the hook parsing logic should result in everything being found. Whatever calls this `heads` method probably gets back a list of heads including the one from the tag push event. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42554) Add steps has no "enter" action or "Add" button
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-42554 Add steps has no "enter" action or "Add" button Issue Type: Bug Assignee: James Dumay Attachments: editor-no-confirm.png Components: blueocean-pipeline-editor-plugin Created: 2017/Mar/07 8:34 PM Priority: Minor Reporter: R. Tyler Croy Basically, the only way I can tell to use the Pipeline Editor's "Add Step" is to click out of the "Add Step" modal Hitting enter doesn't "add step" which I would expect, and there's no button to add the step to the current stage. How is this supposed to be used? Add Comment
[JIRA] (JENKINS-42490) 500 error when unfavoriting a Pipeline
Title: Message Title James Dumay commented on JENKINS-42490 Re: 500 error when unfavoriting a Pipeline I found the issue It looks like you have favourited the Multibranch Folder in classic and BO counts that as a favourite (it shouldn't). When you go to unfavourite, it will try to unfavourite the "master" within the folder which throws an exception. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34021) NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140)
Title: Message Title
Jesse Glick commented on JENKINS-34021
Re: NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140)
With 2.32.3, workflow-durable-task-step 2.9, and workflow-cps 2.29, and this script
while (true) {
try {
node {
sh 'sleep 30'
}
} catch (e) {
echo "ignoring $e"
}
}
I do get some errors, mainly
java.io.IOException: cannot find current thread
at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:296)
at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:61)
at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.logger(DurableTaskStep.java:200)
at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:301)
at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:276)
at …
Everything does stop cleanly and there are no recurring warnings.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42447) Console ouput stops logging after Linux session starts in Java
Title: Message Title Saul Figueroa commented on JENKINS-42447 Re: Console ouput stops logging after Linux session starts in Java Any update for this bug? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42120) Revisit Git repository creation flow credential setup
Title: Message Title Cliff Meyers commented on JENKINS-42120 Re: Revisit Git repository creation flow credential setup This ticket is still in-progress but pending some merging and fixes in JENKINS-41397 that are currently in-progress. I think the UI work is basically done but I uncovered some unexpected behavior in the REST API while testing. Unfortunately testing this change is very time consuming given the permutations (roughly 2^5... SCM provider, repo visibility, URL scheme, credential type, credential validity). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13768) default parameter values are ignored when triggering parameterized build from groovy post-build script
Title: Message Title
jon wolfe commented on JENKINS-13768
Re: default parameter values are ignored when triggering parameterized build from groovy post-build script
+1 This is an impediment to using Groovy and feels unnatural. For example, if I create a parameter which is not configured in the build, it does not appear as an ENV var, so the creation of parameters does affect your groovy code, but the choice of defaults does not. For anyone in need of a workaround, the following can set the defaults in your groovy code:
String jobName;targetJob = myFolder.getItem(jobName);
params = [];
for (ParameterDefinition paramDefinition : targetJob.getProperty(ParametersDefinitionProperty.class).getParameterDefinitions()) \{
params += paramDefinition.getDefaultParameterValue();
\}
paramsAction = new hudson.model.ParametersAction(params)
...
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42123) No feedback when clicking "connect" when entering Github access key
Title: Message Title Cliff Meyers started work on JENKINS-42123 Change By: Cliff Meyers Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21835) Cucumber Test Result Plugin crashes on malformed output in Scenario Outline results produced by some tools
Title: Message Title Daniel Serodio commented on JENKINS-21835 Re: Cucumber Test Result Plugin crashes on malformed output in Scenario Outline results produced by some tools Unfortunately https://github.com/cucumber/cucumber/issues/700 is a 404. Does anyone know which PR that was? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21835) Cucumber Test Result Plugin crashes on malformed output in Scenario Outline results produced by some tools
Title: Message Title Daniel Serodio edited a comment on JENKINS-21835 Re: Cucumber Test Result Plugin crashes on malformed output in Scenario Outline results produced by some tools Unfortunately [https://github.com/cucumber/cucumber/issues/700] is a 404. Does anyone know which PR issue that was , and/or which Cucumber version (if any) contains the fix ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin
Title: Message Title Gabriel Loewen started work on JENKINS-34581 Change By: Gabriel Loewen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42490) 500 error when unfavoriting a Pipeline
Title: Message Title R. Tyler Croy commented on JENKINS-42490 Re: 500 error when unfavoriting a Pipeline One of these things doesn't look like the other, I have no idea how that entry was made "favorite@2.0.4"> "concurrent-hash-map"> Infra/infra-statisticstrueboolean> Infra/azure/master trueboolean> Infra/plugin-site-api/master trueboolean> Infrastructure/jenkins.io falseboolean> Core/remoting/master falseboolean> Core/jenkins_master trueboolean> Core/jenkins/master trueboolean> Infra/plugin-site-api trueboolean> Core/remoting/3.4.x falseboolean> Plugins/azure-vm-agents-plugin/master falseboolean> Infra/jenkins-infra/production trueboolean> Infrastructure/statistics trueboolean> Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You rece
[JIRA] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin
Title: Message Title Gabriel Loewen assigned an issue to Gabriel Loewen Jenkins / JENKINS-34581 Please add support for Pipelines to the Powershell plugin Change By: Gabriel Loewen Assignee: Gabriel Loewen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41904) NPE when selecting a scan credential for GitHub SCM on Pipeline Libraries
Title: Message Title Jesse Glick commented on JENKINS-41904 Re: NPE when selecting a scan credential for GitHub SCM on Pipeline Libraries 2.0.4-beta-1 on the experimental UC; not sure when Stephen Connolly plans to cut a general release. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42490) 500 error when unfavoriting a Pipeline
Title: Message Title James Dumay commented on JENKINS-42490 Re: 500 error when unfavoriting a Pipeline R. Tyler Croy yes, thats the one. Your favourites are stored in there. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42444) Mission Control Plugin is not showing Build History
Title: Message Title Andrey Shevtsov commented on JENKINS-42444 Re: Mission Control Plugin is not showing Build History Added a note about this to the wiki page Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42490) 500 error when unfavoriting a Pipeline
Title: Message Title R. Tyler Croy commented on JENKINS-42490 Re: 500 error when unfavoriting a Pipeline James Dumay, I assume you mean JENKINS_HOME/users/rtyler/config.xml ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42490) 500 error when unfavoriting a Pipeline
Title: Message Title
James Dumay commented on JENKINS-42490
Re: 500 error when unfavoriting a Pipeline
From R. Tyler Croy HAR file: Request body:
{
"favorite": false
}
So I think something odd is going on in the favorite plugin itself. R. Tyler Croy can you send me a copy of your user.xml from Jenkins.io? You can redact any secrets before you send it and if you gpg it to me I can analyze whats going on locally.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42553) Error while using Performance Publisher report plugin (java.lang.RuntimeException)
Title: Message Title
Srini Addanki created an issue
Jenkins / JENKINS-42553
Error while using Performance Publisher report plugin (java.lang.RuntimeException)
Issue Type:
Bug
Assignee:
Andrey Pokhilko
Attachments:
Screen Shot 2017-03-07 at 11.26.03 AM.png
Components:
performance-plugin
Created:
2017/Mar/07 7:27 PM
Priority:
Critical
Reporter:
Srini Addanki
I am getting below error while saving the project by adding performance publisher plugin. Plugin Version : 2.0 Jenkins Version : 1.611 Error Message: javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.performance.PerformancePublisher from {"parsers":{"glob":"*/.jtl","kind":"hudson.plugins.performance.JMeterParser$DescriptorImpl"},"modePerformancePerTestCase":true,"modeThroughput":false,"modeEvaluation":"true","modeOfThreshold":"true","failBuildIfNoResultFile":false,"errorUnstableThreshold":"0","errorFailedThreshold":"0","errorUnstableResponseTimeThreshold":"","relativeUnstableThresholdNegative":"0.0","relativeUnstableThresholdPositive":"0.0","relativeFailedThresholdNegative":"0.0","relativeFailedThresholdPositive":"0.0","compareBuildPrevious":"false","nthBuildNumber":"0","configType":"ART","ignoreFailedBuilds":false,"ignoreUnstableBuilds":false,"persistConstraintLog":false,"stapler-class":"hudson.plugins.performance.PerformancePublisher","$class":"hudson.plugins.performance.PerformancePublisher"} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
[JIRA] (JENKINS-26300) CPS interpreter fails on calls to find(), findAll() default methods
Title: Message Title Kenneth Baltrinic commented on JENKINS-26300 Re: CPS interpreter fails on calls to find(), findAll() default methods It seems that this case was closed by mistake. It was closed as a dup of 26307 but 26307 was closed as a duplicate of this, and I just hit this issue again. Seems it should be re-opened? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38752) Link to branches activity from breadcrumbs
Title: Message Title James Dumay commented on JENKINS-38752 Re: Link to branches activity from breadcrumbs Paul Dragoonis thanks so much for this contribution Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33607) getServerLicenseData: no corresponding wsdl operation
Title: Message Title Caleb Chenoweth commented on JENKINS-33607 Re: getServerLicenseData: no corresponding wsdl operation Appears to still be broken in our Jenkins environment. It seems odd that they have released multiple updates to this plugin, but have not fixed this issue. Are these new versions working for anyone? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42552) Job search not handling + characters
Title: Message Title snemetz created an issue Jenkins / JENKINS-42552 Job search not handling + characters Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/07 6:31 PM Environment: Jenkins public released docker image Jenkins v 2.32.1 Priority: Minor Reporter: snemetz I'm using the + character as a delimiter in Job names for some other automation. This has been working fine, except in 1 place. When searching for part of a job name, a search page will get generated with all the possible jobs. This page looks visually correct. But all the links go to /pluginManager/search/?q= instead of the actual job links. All of these links fail. That search module is stripping the + from the Job name, causing the resulting lookup to fail. It returns a page the says "Search for '" and says nothing matches. Which is now correct as the job name was modified. Add Comment
[JIRA] (JENKINS-40379) Option for 'Select All' against imported jobs
Title: Message Title ambar s commented on JENKINS-40379 Re: Option for 'Select All' against imported jobs +1 ... I am in the same boat, need to import dozens of jobs in one go. Need a "select all" checkbox in the UI. Can't go clicking each and every checkbox for each and every job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Zach Swanson commented on JENKINS-37324 Re: We would like a more meaningful description of a step This isn't restricted to just Blue Ocean, the same inadequate information in executing shell/bat/other steps exists in the 'standard' Pipeline Stage. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42548) Cloud Foundry Push Error
Title: Message Title R M updated an issue Jenkins / JENKINS-42548 Cloud Foundry Push Error Change By: R M Hi, I am having issues to push to Cloud Foundry through Jenkins. I am using la=test Cloud Foundry plugin (1.5). It is giving an below error. But on CF the= app is getting updated and running successfully though it is erroring out on Jenkins . Please assist. Thanks,RM *** BUILD SUCCESSFUL Total time: 5.322 secsCloud Foundry Plugin:WARNING: No manifest value for hostname. Using app name: config-servicePushing config-service app to [https://api.run.pivotal.iovotal.io/>App already exists, skipping creation.Pushing app bits.Restarting application.WARNING: Exception occurred trying to get staging logs via websocket. Switc=hing to alternate method.WARNING: Could not get staging logs with alternate method. Cannot display s=taging logs.org.cloudfoundry.client.lib.org.springframework.web.client.HttpServerErrorE=xception: 503 Service Unavailableat org.cloudfoundry.client.lib.rest.CloudControllerResponseErrorHan=dler.handleError(CloudControllerResponseErrorHandler.java:26)at org.cloudfoundry.client.lib.org.springframework.web.client.RestT=emplate.handleResponseError(RestTemplate.java:589)at org.cloudfoundry.client.lib.org.springframework.web.client.RestT=emplate.doExecute(RestTemplate.java:547)at org.cloudfoundry.client.lib.rest.LoggingRestTemplate.doExecute(L=oggingRestTemplate.java:54)at org.cloudfoundry.client.lib.org.springframework.web.client.RestT=emplate.execute(RestTemplate.java:511)at org.cloudfoundry.client.lib.org.springframework.web.client.RestT=emplate.getForObject(RestTemplate.java:248)at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.getIn=stanceInfoForApp(CloudControllerClientImpl.java:1154)at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.doGet=ApplicationStats(CloudControllerClientImpl.java:1140)at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.getRu=nningInstances(CloudControllerClientImpl.java:1119)at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.mapCl=oudApplication(CloudControllerClientImpl.java:1107)at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.getAp=plication(CloudControllerClientImpl.java:1075)at org.cloudfoundry.client.lib.CloudFoundryClient.getApplication(Cl=oudFoundryClient.java:226)at com.hpe.cloudfoundryjenkins.CloudFoundryPushPublisher.processOne=App(CloudFoundryPushPublisher.java:287)at com.hpe.cloudfoundryjenkins.CloudFoundryPushPublisher.perform(Cl=oudFoundryPushPublisher.java:188)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20=)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(Abstra=ctBuild.java:779)at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuil=dSteps(AbstractBuild.java:720)at hudson.model.Build$BuildExecution.post2(Build.java:185)at hudson.model.Ab
