[JIRA] (JENKINS-43143) [Regression] Parameters no longer available in credentials for environment
Title: Message Title Andrew Bayer updated JENKINS-43143 Jenkins / JENKINS-43143 [Regression] Parameters no longer available in credentials for environment Change By: Andrew Bayer 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-43143) [Regression] Parameters no longer available in credentials for environment
Title: Message Title Andrew Bayer started work on JENKINS-43143 Change By: Andrew Bayer 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-43169) Jenkins should log clear error wehn parrallel sync attempted with P4Java
Title: Message Title
Karl Wirth commented on JENKINS-43169
Re: Jenkins should log clear error wehn parrallel sync attempted with P4Java
Reproduction steps: (1) Submit 5x30MB files from a workspace. (2) Add following config: {{ p4 configure set net.parallel.max=5 }} p4 configure set net.parallel.threads=2 p4 configure set net.parallel.batch=2 p4 configure set net.parallel.batchsize=1024 p4 configure set net.parallel.min=2 (3) Create new job that does a sync of the above files. (4) Job will fail with no obvious error.
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-41521) LDAP caching broken
Title: Message Title
Keith Baitsell edited a comment on JENKINS-41521
Re: LDAP caching broken
Here's the logs:Mar 28, 2017 5:05:04 PM FINE org.acegisecurity.ldap.DefaultInitialDirContextFactory connectCreating InitialDirContext with environment \{java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.referral=follow, java.naming.security.principal=uid=ldap.binding,ou=Users,o= 57388cc359a3e5f954639c04 1212121212 ,dc=jumpcloud,dc=com, com.sun.jndi.ldap.connect.timeout=6, com.sun.jndi.ldap.connect.pool=true, com.sun.jndi.ldap.read.timeout=6, java.naming.provider.url="" java.naming.security.authentication=simple, java.naming.security.credentials=**}Mar 28, 2017 5:05:04 PM FINER jenkins.security.BasicHeaderRealPasswordAuthenticatorAuthentication request for user: build.manager failed: org.acegisecurity.AuthenticationServiceException: Unable to connect to LDAP server; nested exception is javax.naming.CommunicationException: ldap.jumpcloud.com:636 [Root exception is javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake]; nested exception is org.acegisecurity.ldap.LdapDataAccessException: Unable to connect to LDAP server; nested exception is javax.naming.CommunicationException: ldap.jumpcloud.com:636 [Root exception is javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake]Mar 28, 2017 5:05:04 PM FINE jenkins.security.BasicHeaderProcessorAuthentication of BASIC header failed
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
[JIRA] (JENKINS-41521) LDAP caching broken
Title: Message Title
Keith Baitsell commented on JENKINS-41521
Re: LDAP caching broken
Here's the logs: Mar 28, 2017 5:05:04 PM FINE org.acegisecurity.ldap.DefaultInitialDirContextFactory connect Creating InitialDirContext with environment {java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.referral=follow, java.naming.security.principal=uid=ldap.binding,ou=Users,o=57388cc359a3e5f954639c04,dc=jumpcloud,dc=com, com.sun.jndi.ldap.connect.timeout=6, com.sun.jndi.ldap.connect.pool=true, com.sun.jndi.ldap.read.timeout=6, java.naming.provider.url="" java.naming.security.authentication=simple, java.naming.security.credentials=**} Mar 28, 2017 5:05:04 PM FINER jenkins.security.BasicHeaderRealPasswordAuthenticator Authentication request for user: build.manager failed: org.acegisecurity.AuthenticationServiceException: Unable to connect to LDAP server; nested exception is javax.naming.CommunicationException: ldap.jumpcloud.com:636 [Root exception is javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake]; nested exception is org.acegisecurity.ldap.LdapDataAccessException: Unable to connect to LDAP server; nested exception is javax.naming.CommunicationException: ldap.jumpcloud.com:636 [Root exception is javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake] Mar 28, 2017 5:05:04 PM FINE jenkins.security.BasicHeaderProcessor Authentication of BASIC header failed
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
[JIRA] (JENKINS-43169) Jenkins should log clear error wehn parrallel sync attempted with P4Java
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-43169 Jenkins should log clear error wehn parrallel sync attempted with P4Java Issue Type: Improvement Assignee: Karl Wirth Components: p4-plugin Created: 2017/Mar/28 5:06 PM Priority: Major Reporter: Karl Wirth If the Helix server is configured for parallel syncs the Jenkins sync can fail with no clear error in the job. Looking into the Jenkins log you find: com.perforce.p4java.exception.ConnectionException: No metadata defined for RPC function encoding: client-ReceiveFiles The solution is that P4Java does not yet support parallel sync so p4/P4.EXE must be used configured in the parralel sync options section of the job, and the binary needs to exist on all build slaves. Add Comment
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jon Whitcraft commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Sascha Vujevic Unfortunately there is no way to do that. I pinged Carlos Sanchez about this a few weeks ago and he added the component label but I have not heard anything else. It would be nice to get this fixed. it's really annoying when trying to debug issues. 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-41521) LDAP caching broken
Title: Message Title Keith Baitsell commented on JENKINS-41521 Re: LDAP caching broken I spun up a bare jenkins install in vagrant and pointed authentication at my LDAP provider. I created a small job that just echoes "hello world" and call it via curl using basic auth and ldap credentials. If I add one job, it gets added, worked, and exits nicely. When I put that curl in a for loop and try to do them one after the other, it will add the first few but eventually stops working with the following error: "Error 401 Invalid password/token for user: b8sell" I have enabled caching in the LDAP plugin and get the same behavior. Is this not working from a lack of caching? 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-43168) Performance publisher throws NPE when publishing jmeter results
Title: Message Title Sahar jzb created an issue Jenkins / JENKINS-43168 Performance publisher throws NPE when publishing jmeter results Issue Type: Bug Assignee: vergnes Components: jmeter, performance-plugin Created: 2017/Mar/28 4:55 PM Priority: Major Reporter: Sahar jzb I have a post-build action set to publish results via performance plugin. I get the following NPE after my jmeter tests are done: java.lang.NullPointerException at hudson.plugins.performance.PerformancePublisher.perform(PerformancePublisher.java:333) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1758) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:405) Build step 'Publish Performance test result report' marked build as failure
[JIRA] (JENKINS-41521) LDAP caching broken
Title: Message Title Keith Baitsell updated an issue Jenkins / JENKINS-41521 LDAP caching broken Change By: Keith Baitsell Summary: LDAPS LDAP caching broken 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Roch Devost commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Where exactly is this option? I have looked everywhere and cannot seem to find it. I am using the `checkout scm` step in Blue Ocean rc3 if that helps. 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-41325) Promotions dissapear without a trace
Title: Message Title Jakub Bochenski commented on JENKINS-41325 Re: Promotions dissapear without a trace OK, I was (wrongly) assuming using job-dsl results in the exact same configuration as if I used the web form to create a job manually. I see this is not true, depending on how a particular step is implemented – thanks for pointing it out. 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-40608) Job Summary Of Changes disappeared in version 1.4.12
Title: Message Title Ben Langton commented on JENKINS-40608 Re: Job Summary Of Changes disappeared in version 1.4.12 Sorry for the long delay. I finally got back to upgrading again and looking at this. Using P4 Plugin 1.5.1, I still had the issue; the job was correctly triggered when there was a change, however the list of changes showed "No changes". (This particular job parses the from the job/build/api/xml URL to determine what it does next, so it was a problem for me). The issue is now resolved for me; it seems to have been fixed by deleting the local workspace folder, submitting a change to Perforce, and allowing the P4 plugin to completely resync the workspace. Thanks! 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-40127) GDSL for Declarative
Title: Message Title Gijs L commented on JENKINS-40127 Re: GDSL for Declarative In which repo is the code for the (Intellij IDEA) GDSL? I'd want to have a look 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-43022) Not correct exclude path to domains
Title: Message Title Mark Waite commented on JENKINS-43022 Re: Not correct exclude path to domains The git client plugin is likely where the change will be needed. 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-43022) Not correct exclude path to domains
Title: Message Title juan francisco sanchez ramos commented on JENKINS-43022 Re: Not correct exclude path to domains ok Mark Waite , the correct url to pull request is https://github.com/jenkinsci/credentials-plugin or https://github.com/jenkinsci/git-plugin ? Thanks p.d: We will seek all possible ways 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-43072) jenkinsci/jnlp not connecting to master
Title: Message Title Zalan Meggyesi edited a comment on JENKINS-43072 Re: jenkinsci/jnlp not connecting to master Kenneth, do you have a possible workaround, perhaps? I just ran into this and it rendered my cluster unusable. For me, both parameters are doubled up, not just the MAC. 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-43022) Not correct exclude path to domains
Title: Message Title juan francisco sanchez ramos updated an issue Jenkins / JENKINS-43022 Not correct exclude path to domains Change By: juan francisco sanchez ramos Sprint: Blue Ocean up next 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-43022) Not correct exclude path to domains
Title: Message Title juan francisco sanchez ramos updated an issue Jenkins / JENKINS-43022 Not correct exclude path to domains Change By: juan francisco sanchez ramos Sprint: Blue Ocean up next 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-43022) Not correct exclude path to domains
Title: Message Title Mark Waite commented on JENKINS-43022 Re: Not correct exclude path to domains Nothing new. Other items are currently higher priority. I'd love to have additional help with the plugin. If you're able to propose a pull request for the plugin, it tends to proceed more quickly than if I do 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-43163) xcrun's deprecated PackageApplication is removed from Xcode 8.3
Title: Message Title Andy H commented on JENKINS-43163 Re: xcrun's deprecated PackageApplication is removed from Xcode 8.3 Pull request 76 appears to be a solution to this issue: https://github.com/jenkinsci/xcode-plugin/pull/76/commits/de240a9c2e192fba7d8c6d7509b9e8c00b102307 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-43072) jenkinsci/jnlp not connecting to master
Title: Message Title Zalan Meggyesi commented on JENKINS-43072 Re: jenkinsci/jnlp not connecting to master Kenneth, do you have a possible workaround, perhaps? I just ran into this and it rendered my cluster unusable. 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-40934) LogActionImpl listener inefficient; poor performance queuing large parallel workloads
Title: Message Title Sam Van Oort updated JENKINS-40934 Updating to note it is merged in now, pending next release. Jenkins / JENKINS-40934 LogActionImpl listener inefficient; poor performance queuing large parallel workloads Change By: Sam Van Oort Status: In Review 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.
[JIRA] (JENKINS-43022) Not correct exclude path to domains
Title: Message Title juan francisco sanchez ramos commented on JENKINS-43022 Re: Not correct exclude path to domains something new? Stephen Connolly or Mark Waite ? . Thanks 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-43167) Erro ao usar Trigger a remote parameterized job
Title: Message Title Ricardo Gomes created an issue Jenkins / JENKINS-43167 Erro ao usar Trigger a remote parameterized job Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger-plugin Created: 2017/Mar/28 2:42 PM Priority: Major Reporter: Ricardo Gomes Ao executar o Trigger a remote parameterized job recebo a mensagem de erro abaixo. [Current build status] check if current [SUCCESS] is worse or equals then [SUCCESS] and better or equals then [SUCCESS] Regular _expression_ run condition: _expression_=[snapshot], Label=[snapshot] Run condition [And] enabling perform for step [Trigger a remote parameterized job] Remote Jenkins server returned empty response or invalid JSON - but we can still proceed with the remote build. ERROR: Build step failed with exception java.lang.NullPointerException at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.isRemoteJobParameterized(RemoteBuildConfiguration.java:1167) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:488) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder.perform(SingleConditionalBuilder.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at
[JIRA] (JENKINS-28907) option to treat merge commiters as regular commiters
Title: Message Title Kevin Burnett commented on JENKINS-28907 Re: option to treat merge commiters as regular commiters we investigated this a bit. we found that the only difference between these two, for our repos, was that the git log included some extra commits due to it defaulting to "rev.always_show_header = 1". git whatchanged --no-merges --format="commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b" git log --raw --no-merges --format="commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b" there is a check in the git source code where it doesn't set rev.always_show_header to true when --diff-filter is used. so if we set diff filter to not actually filter (by including everything), the git whatchanged and git log commands return identical output for us. so the final equivalent git log command is this: git log --diff-filter=ACDMRTUXB --raw --no-merges --format="commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b" so, to include merge commits, we can simply remove the --no-merges from the git log, leaving us with: git log --diff-filter=ACDMRTUXB --raw --format="commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b" pull request at https://github.com/jenkinsci/git-client-plugin/pull/237 that uses this approach and adds merge commits! Add Comment
[JIRA] (JENKINS-26930) Emulator fails to start with bogus error message
Title: Message Title
Pedro Melo edited a comment on JENKINS-26930
Re: Emulator fails to start with bogus error message
Same issue here but I moved a bit further along. You can use {{$ANDROID_HOME/emulator/emulator}} and bypass the (for some reason) broken 32bit test. If you use that {{emulator}}, I get this error message:{{emulator: ERROR: This AVD's configuration is missing a kernel file! Please ensure the file "kernel-ranchu" is in the same location as your system image.}} Apparently android-25 arm64 system images are missing the kernel-ranchu files, they are present on android-24.I still would like to know what is the problem with the 32-bit check though... Edit: for context - using Android SDK 7.1.1 inside a Docker container for build and automated tests
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-43166) Java File Class in Pipeline Script on Linux Server and Windwos Agent
Title: Message Title Marc Vollmer created an issue Jenkins / JENKINS-43166 Java File Class in Pipeline Script on Linux Server and Windwos Agent Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2017/Mar/28 2:37 PM Labels: pipeline jenkins Priority: Major Reporter: Marc Vollmer I'm running a Jenkins Server on a Linux System with multiple Agents. One Agent is on a Windows Server System. I'm running a pipeline script with a Node Block for the Windows Agent. Inside the Node Block I construct the following path: this.steps.pwd() + "/soemdir/test" The constructed path (as String) outputs as: E:\jenkins\workspace\group\job/somedir/test Now I create a File object: File fPath = new File(this.steps.pwd() + "/soemdir/test") I now get Errors that the path not exists. Outputting getAbsolutePath results in:
[JIRA] (JENKINS-43083) Investigate how to improve unit and integration tests and avoid relying on E2E (ATH)
Title: Message Title Cliff Meyers commented on JENKINS-43083 Re: Investigate how to improve unit and integration tests and avoid relying on E2E (ATH) Couple of useful reads I found over the weekend that seem to be pro-Jest: https://www.codementor.io/vijayst/unit-testing-react-components-jest-or-enzyme-du1087lh8 https://blog.grommet.io/post/2016/09/01/how-we-landed-on-jest-snapshot-testing-for-_javascript_ And at least one contrarian opinion: https://www.reddit.com/r/reactjs/comments/46cwj3/whats_february_2016s_best_alternative_to_jest_i/ I am not sold on it, although I do think it might be worth taking a look at. Happy to discuss more. 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-26930) Emulator fails to start with bogus error message
Title: Message Title Pedro Melo commented on JENKINS-26930 Re: Emulator fails to start with bogus error message Same issue here but I moved a bit further along. You can use $ANDROID_HOME/emulator/emulator and bypass the (for some reason) broken 32bit test. If you use that emulator, I get this error message: emulator: ERROR: This AVD's configuration is missing a kernel file! Please ensure the file "kernel-ranchu" is in the same location as your system image. Apparently android-25 arm64 system images are missing the kernel-ranchu files, they are present on android-24. I still would like to know what is the problem with the 32-bit check though... 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-43162) Git-parameter plugin: "Retrieving Git References..."
Title: Message Title Daniel Majano updated an issue Jenkins / JENKINS-43162 Git-parameter plugin: "Retrieving Git References..." Change By: Daniel Majano Environment: Git-parameter-plugin 0.4GitLab 6.7.3Jenkins 1.602 Git-plugin 1.1 Hi family,i have the following enviroment:Git-parameter-plugin 0.4GitLab 6.7.3Jenkins 1.602 Git-plugin 1.1 I have created a maven job, which with the git-parameter plugin, I choose a GitLab branch and execute a maven command. The job goes perfect but i have configured a second maven job with a different gitlab repository and after the first build for create the workspace, only appear "Retrieving Git References...", i only see this in the log:Mar 28, 2017 3:42:03 PM INFO net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContentsgenerateContents contenttype PT_BRANCH RemoteConfig [http://myurl/myproject/myrepo.git]The thing is, if i configure a static parameter and i write the branch, the job works perfectly.Thanks to all by the help. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-35216) The process cannot access the file because it is being used by another process. while making build in jenkins
Title: Message Title
John Lewis commented on JENKINS-35216
Re: The process cannot access the file because it is being used by another process. while making build in jenkins
I just got this message with Jenkins 2.51. Fresh install. Windows 7. No jobs created. Attempting to create a job with this procedure: http://www.spinnaker.io/docs/jenkins-script-execution-stage Here is the command using cygwin curl: curl -X POST 'http://:@/createItem?name=runSpinnakerScript' -H 'Content-Type: application/xml' --data-binary '/cygdrive/c/Users/userid/Downloads/@scriptJobConfig.xml'{{}} I had to disable "Prevent Cross Site Request Forgery exploits". Stack tracejava.nio.file.FileSystemException: C:\Users\userid\.jenkins\jobs\runSpinnakerScript\config.xml: The process cannot access the file because it is being used by a nother process. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source) at java.nio.file.Files.deleteIfExists(Unknown Source) at hudson.Util.tryOnceDeleteFile(Util.java:287) at hudson.Util.tryOnceDeleteRecursive(Util.java:364) at hudson.Util.tryOnceDeleteContentsRecursive(Util.java:383) at hudson.Util.tryOnceDeleteRecursive(Util.java:363) at hudson.Util.deleteRecursive(Util.java:341) Caused: java.io.IOException: Unable to delete 'C:\Users\userid\.jenkins\jobs\runSpinnakerScript'. Tried 3 times (of a ma ximum of 3) waiting 0.1 sec between attempts. at hudson.Util.deleteRecursive(Util.java:346) at hudson.model.ItemGroupMixIn.createProjectFromXML(ItemGroupMixIn.java:305) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:189) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:3795) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) 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:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at
[JIRA] (JENKINS-43165) artifactory-plugin 2.9.2 throws exceptions and breaks our builds
Title: Message Title
Bryan Hunt updated an issue
Jenkins / JENKINS-43165
artifactory-plugin 2.9.2 throws exceptions and breaks our builds
Change By:
Bryan Hunt
We upgraded artifactory-plugin from 2.9.1 to 2.9. 1 2 and now we are getting the following exceptions. Reverting back to 2.9.1 fixes our builds. {code:java}[main] ERROR org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseRepositoryListener - Failed while enforcing Artifactory artifact resolverorg.codehaus.plexus.component.repository.exception.ComponentLookupException: com.google.inject.ProvisionException: Guice provision errors:1) Error in requirement: public org.eclipse.aether.internal.impl.DefaultArtifactResolver org.eclipse.aether.internal.impl.DefaultArtifactResolver.setLoggerFactory(org.eclipse.aether.spi.log.LoggerFactory) at ClassRealm[plexus.core, parent: null] while locating org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseArtifactResolver1 error role: org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseArtifactResolver roleHint: at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:264) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:240) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:234) at org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseRepositoryListener.enforceArtifactoryResolver(ArtifactoryEclipseRepositoryListener.java:71) at org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseRepositoryListener.contextualize(ArtifactoryEclipseRepositoryListener.java:258) at org.eclipse.sisu.plexus.PlexusLifecycleManager.contextualize(PlexusLifecycleManager.java:322) at org.eclipse.sisu.plexus.PlexusLifecycleManager.manageLifecycle(PlexusLifecycleManager.java:297) at org.eclipse.sisu.plexus.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:143) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:109) at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1054) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:59) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:997) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1047) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:993) at
[JIRA] (JENKINS-43165) artifactory-plugin 2.9.2 throws exceptions and breaks our builds
Title: Message Title Bryan Hunt created an issue Jenkins / JENKINS-43165 artifactory-plugin 2.9.2 throws exceptions and breaks our builds Issue Type: Bug Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2017/Mar/28 2:15 PM Priority: Major Reporter: Bryan Hunt We upgraded artifactory-plugin from 2.9.1 to 2.9.1 and now we are getting the following exceptions. Reverting back to 2.9.1 fixes our builds. [main] ERROR org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseRepositoryListener - Failed while enforcing Artifactory artifact resolver org.codehaus.plexus.component.repository.exception.ComponentLookupException: com.google.inject.ProvisionException: Guice provision errors: 1) Error in requirement: public org.eclipse.aether.internal.impl.DefaultArtifactResolver org.eclipse.aether.internal.impl.DefaultArtifactResolver.setLoggerFactory(org.eclipse.aether.spi.log.LoggerFactory) at ClassRealm[plexus.core, parent: null] while locating org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseArtifactResolver 1 error role: org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseArtifactResolver roleHint: at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:264) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:240) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:234) at org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseRepositoryListener.enforceArtifactoryResolver(ArtifactoryEclipseRepositoryListener.java:71) at org.jfrog.build.extractor.maven.resolver.ArtifactoryEclipseRepositoryListener.contextualize(ArtifactoryEclipseRepositoryListener.java:258) at org.eclipse.sisu.plexus.PlexusLifecycleManager.contextualize(PlexusLifecycleManager.java:322) at
[JIRA] (JENKINS-43164) ₱₱AFFORDABLE009¶¶::: 1::800::844::0887::: QuickBooks Tech Support Number ...QuickBooks technical Support Number... QuickBooks 24/7 support Number
Title: Message Title dulhan kumari created an issue Jenkins / JENKINS-43164 ₱₱AFFORDABLE009¶¶::: 1::800::844::0887::: QuickBooks Tech Support Number ...QuickBooks technical Support Number... QuickBooks 24/7 support Number Issue Type: Bug Assignee: Anthony Dahanne Components: accelerated-build-now-plugin Created: 2017/Mar/28 2:11 PM Environment: ₱₱AFFORDABLE009¶¶::: 1::800::844::0887::: QuickBooks Tech Support Number ...QuickBooks technical Support Number... QuickBooks 24/7 support Number Priority: Minor Reporter: dulhan kumari ₱₱AFFORDABLE009¶¶::: 1::800::844::0887::: QuickBooks Tech Support Number ...QuickBooks technical Support Number... QuickBooks 24/7 support Number +1-800-844-0887 Quickbooks phone number Quickbooks customer service number 1800 844 0887 Open Hours USA 1800 844 0887 Quickbooks technical support phone number 24*7 TEXAS 800 844 0887 Quickbooks support phone number 24*7 FLORIDA 1800-844-0887 Quickbooks tech support phone number 24*7 USA 1800 844 0887 Quickbooks phone number 24*7 TEXAS 800 844 0887 Quickbooks technical support number 24*7 FLORIDA 1800-844-0887 Quickbooks customer support phone number 24*7 USA 1800 844 0887 Quickbooks customer service phone number 24*7 TEXAS 800 844 0887 phone number for Quickbooks 24*7 FLORIDA 1800-844-0887 Quickbooks support number 24*7 USA 1800 844 0887 phone number for Quickbooks technical support 24*7 TEXAS 800 844 0887 Quickbooks phone number Texas 24*7 FLORIDA 1800-844-0887 Quickbooks number 24*7 USA 1800 844 0887 Quickbooks help phone number 24*7 TEXAS 800 844 0887 Quickbooks customer service number 24*7 FLORIDA 1800-844-0887 Quickbooks contact number 24*7 USA 1800 844 0887 Quickbooks customer support number 24*7 TEXAS 800 844 0887 Quickbooks tech support number 24*7 FLORIDA 1800-844-0887 phone number
[JIRA] (JENKINS-43163) xcrun's deprecated PackageApplication is removed from Xcode 8.3
Title: Message Title Petra A created an issue Jenkins / JENKINS-43163 xcrun's deprecated PackageApplication is removed from Xcode 8.3 Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 2017/Mar/28 2:05 PM Environment: Xcode 8.3, macOS 10.12.3 Priority: Critical Reporter: Petra A I've updated the Xcode (to version 8.3) today and now all my Jenkins iOS builds are failing. This is the error: xcrun: error: unable to find utility "PackageApplication", not a developer tool or in PATH It looks like PackageApplication is removed from Xcode 8.3. In Xcode 8.2 there was a warning: PackageApplication is deprecated, use `xcodebuild -exportArchive` instead. Xcode Plugin should change the way it builds IPA file. Add Comment
[JIRA] (JENKINS-42951) Local-part based user mapping results in confused changelogs
Title: Message Title Yoann Dubreuil commented on JENKINS-42951 Re: Local-part based user mapping results in confused changelogs Not much to add, making the option to use email addresses as ID the default is the most sensible thing to do I think. Even after the SECURITY-372 fix, we can send email to a wrong person if an organization uses more than one domain in its email suffix and there are collisions on the short name. What ensures the security fix is that the wrong person is also known to Jenkins, so this is much less a concern than sending email to a random person over the internet. I tested the following scenario while I was analyzing the security issue: user1 is known to the security realm and has email us...@divisona.company.org a commit done by user1@divisonB.company.org is built => Git plugin looks up user1 from the security realm and adds it to the culprits an email is sent to user1@divisonA.company.org This case may not be often encountered but is still a data leak. Making email addresses as ID the default will prevent that. 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
[JIRA] (JENKINS-43162) Git-parameter plugin: "Retrieving Git References..."
Title: Message Title Daniel Majano created an issue Jenkins / JENKINS-43162 Git-parameter plugin: "Retrieving Git References..." Issue Type: Bug Assignee: Daniel Majano Components: git-parameter-plugin, gitlab-plugin Created: 2017/Mar/28 1:55 PM Environment: Git-parameter-plugin 0.4 GitLab 6.7.3 Jenkins 1.602 Labels: git-parameter jenkins gitlab Priority: Minor Reporter: Daniel Majano Hi family, i have the following enviroment: Git-parameter-plugin 0.4 GitLab 6.7.3 Jenkins 1.602 I have created a maven job, which with the git-parameter plugin, I choose a GitLab branch and execute a maven command. The job goes perfect but i have configured a second maven job with a different gitlab repository and after the first build for create the workspace, only appear "Retrieving Git References...", i only see this in the log: Mar 28, 2017 3:42:03 PM INFO net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents generateContents contenttype PT_BRANCH RemoteConfig http://myurl/myproject/myrepo.git The thing is, if i configure a static parameter and i write the branch, the job works perfectly. Thanks to all by the help.
[JIRA] (JENKINS-41118) Allow custom workspaces in declarative pipeline
Title: Message Title Michael Gunn updated an issue Jenkins / JENKINS-41118 Allow custom workspaces in declarative pipeline Change By: Michael Gunn Comment: Doesn't this solution mean you can't have top level agent as none which seems to be the 'workaround' to avoid inputs blocking?https://issues.jenkins-ci.org/browse/JENKINS-37515Seems that either there needs to be a fix so inputs don't block (without the workaround) or this or another fix allows you to set the workspace even if the top level agent is NONE.If this can already be done (agent of none + custom workspace set) can anyone supply that syntax? 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-43161) Audit Trail Plugin : Failed Loading plugin Audit Trail v2.2 (audit-trail)
Title: Message Title Dean Pearce commented on JENKINS-43161 Re: Audit Trail Plugin : Failed Loading plugin Audit Trail v2.2 (audit-trail) Actually, deleting the existing reference XML configuration file (/var/lib/jenkins/audit-trail.xml) resolved the issue, the plugin loaded successfully after that. 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-41912) Investigate running ATH on all supported browsers
Title: Message Title Yoann Dubreuil commented on JENKINS-41912 Re: Investigate running ATH on all supported browsers As long as we can get a Windows license, it shouldn't be that hard I think. I think James Nord could help me on 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-43161) Audit Trail Plugin : Failed Loading plugin Audit Trail v2.2 (audit-trail)
Title: Message Title Dean Pearce created an issue Jenkins / JENKINS-43161 Audit Trail Plugin : Failed Loading plugin Audit Trail v2.2 (audit-trail) Issue Type: Bug Assignee: Unassigned Components: audit-trail-plugin Created: 2017/Mar/28 1:28 PM Environment: Jenkins ver. 2.32.3 CentOS 6 JDK 1.8 Priority: Minor Reporter: Dean Pearce Running into an error after upgrading Jenkins from 1.651.3 to 2.32.3. I am running the latest JDK 1.8. Mar 28, 2017 9:20:49 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin Audit Trail v2.2 (audit-trail) java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:521) at hudson.PluginManager$2$1$1.run(PluginManager.java:517) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1085) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Unable to read /var/lib/jenkins/audit-trail.xml at hudson.XmlFile.unmarshal(XmlFile.java:161) at hudson.Plugin.load(Plugin.java:264) at
[JIRA] (JENKINS-43023) Provide URL of triggered job
Title: Message Title Flemming Steffensen commented on JENKINS-43023 Re: Provide URL of triggered job We also use one top-level job which calls a number of sub-jobs. In some cases we call the same sub-job several times, with different parameters. It would be nice if build-numbers are always associated with the links to sub-projects. And even more nice if the LED status were associated with the actual sub-project. 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-34726) Copy console output of triggered job into console of current job
Title: Message Title Flemming Steffensen commented on JENKINS-34726 Re: Copy console output of triggered job into console of current job We use wget to copy the console output from the triggered job. It would be nice to just have an option to tick to either copy the entire subprojects console output either to a separate file or to the console. 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-23855) Add build step before other step
Title: Message Title Aleks Milut commented on JENKINS-23855 Re: Add build step before other step Still a nice and valid feature request for jenkins 2.x 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-43158) git-lfs support
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-43158 git-lfs support Change By: Mark Waite 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-43158) git-lfs support
Title: Message Title Mark Waite commented on JENKINS-43158 Re: git-lfs support Large file support was added in git plugin 3.1.0, released 4 Mar 2017. The git plugin defaults are not changed when new capabilities are released, lest the new capability break some existing behavior. You'll need to configure your job with the "Additional Behaviour" to "Git LFS pull after checkout". Git LFS support in the git plugin and git client plugin requires that git LFS be installed on each agent, and it only officially supports command line git. 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-43141) fails to connect to jira
Title: Message Title marlene cote commented on JENKINS-43141 Re: fails to connect to jira yes we have a reverse proxy in front of jira. also we use secure ssl certs for jira. 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-41118) Allow custom workspaces in declarative pipeline
Title: Message Title Michael Gunn commented on JENKINS-41118 Re: Allow custom workspaces in declarative pipeline Doesn't this solution mean you can't have top level agent as none which seems to be the 'workaround' to avoid inputs blocking? https://issues.jenkins-ci.org/browse/JENKINS-37515 Seems that either there needs to be a fix so inputs don't block (without the workaround) or this or another fix allows you to set the workspace even if the top level agent is NONE. If this can already be done (agent of none + custom workspace set) can anyone supply that syntax? 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-43141) fails to connect to jira
Title: Message Title marlene cote commented on JENKINS-43141 Re: fails to connect to jira JIRA plugin 2.2.1 JIRA Trigger Plugin 0.3.0 jira-ext Plugin 0.6.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-29038) recursively update submodules does not recursively sync first
Title: Message Title Adam Kapos commented on JENKINS-29038 Re: recursively update submodules does not recursively sync first Would be nice to get this 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-38542) NullPointerException loading Pipeline Job with dynamic gerrit triggers
Title: Message Title
Max P commented on JENKINS-38542
Re: NullPointerException loading Pipeline Job with dynamic gerrit triggers
Same error with all latests plugin. Workaround: wrap line 553 in GerritTrigger.java with try-catch:
try {
logger.trace("GerritTrigger.cancelTimer(): {0}", job.getName());
} catch (NullPointerException e) {
logger.trace("Not found job name");
}
and it now works as expected
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-43129) When integrated with octane and jenkins pipeline build number increased incorrectly
Title: Message Title Laurent TOURREAU commented on JENKINS-43129 Re: When integrated with octane and jenkins pipeline build number increased incorrectly This issue is duplicated 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-43129) When integrated with octane and jenkins pipeline build number increased incorrectly
Title: Message Title Laurent TOURREAU closed an issue as Duplicate Jenkins / JENKINS-43129 When integrated with octane and jenkins pipeline build number increased incorrectly Change By: Laurent TOURREAU Status: Open Closed Resolution: Duplicate 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-43118) User can access the Pipeline editor without a repository
Title: Message Title Brent Laster commented on JENKINS-43118 Re: User can access the Pipeline editor without a repository Is there doc somewhere that describes what the "Pipeline Playground" refers to? Also, Keith Zantow , are you saying that the ctrl/cmd-s combo brings up the save dialog? Is there a place the key combos are doc'd - for Windows and Mac? Thanks. 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-43160) Please make locale settings
Title: Message Title Lior Goikhburg created an issue Jenkins / JENKINS-43160 Please make locale settings Issue Type: Bug Assignee: Unassigned Components: locale-plugin Created: 2017/Mar/28 12:32 PM Priority: Minor Reporter: Lior Goikhburg I'd be useful if users had an option in their profile to set the locale for themselves. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43160) Please make locale settings in users profile
Title: Message Title Lior Goikhburg updated an issue Jenkins / JENKINS-43160 Please make locale settings in users profile Change By: Lior Goikhburg Summary: Please make locale settingsin users profile 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-43159) maven-spy log contains invalid XML
Title: Message Title Ollie Robertshaw updated an issue Jenkins / JENKINS-43159 maven-spy log contains invalid XML Change By: Ollie Robertshaw 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-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak stopped work on JENKINS-39332 Change By: Yafim Kazak Status: In Progress Open 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-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak closed an issue as Won't Fix Currently, to solve this - please do not install LeanFT and LoadRunner on the same machine. Jenkins / JENKINS-39332 ApiSlRuntimeErrors.UnsafeCode error during analysis Change By: Yafim Kazak Status: Open Closed Resolution: Won't 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
[JIRA] (JENKINS-43159) maven-spy log contains invalid XML
Title: Message Title Ollie Robertshaw updated an issue Jenkins / JENKINS-43159 maven-spy log contains invalid XML Change By: Ollie Robertshaw Summary: Generated invalid XML in maven-spy log contains invalid 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-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak commented on JENKINS-39332 Re: ApiSlRuntimeErrors.UnsafeCode error during analysis Hi, after long investigation - we have discovered that currently, you shouldn't install LeanFT and LoadRunner on same machine. 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 Alex Radinsky commented on JENKINS-37324 Re: We would like a more meaningful description of a step I'm on rc3 and don't see any change. Do I need to specify the name for each step or something? How it should work and parse the command I execute? 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-43159) Generated invalid XML in maven-spy log
Title: Message Title Ollie Robertshaw commented on JENKINS-43159 Re: Generated invalid XML in maven-spy log Attached log up to the failure. Afterwards would maybe require too much work to sanitize. 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-30698) HP Application Automation Tools - "Error: Timeout for Analysis passed"
Title: Message Title Yafim Kazak closed an issue as Fixed Jenkins / JENKINS-30698 HP Application Automation Tools - "Error: Timeout for Analysis passed" Change By: Yafim Kazak 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-43159) Generated invalid XML in maven-spy log
Title: Message Title
Ollie Robertshaw updated an issue
Jenkins / JENKINS-43159
Generated invalid XML in maven-spy log
Change By:
Ollie Robertshaw
Our maven-spy-*.log file is being generated with broken XML, for example: {code:java}..{code} This happens with other elements too; in this particular case, re-running the job leads to exactly the same malformed XML.This ultimately leads to an error: {code:java}ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /media/ephemeral0/jenkins/workspace/iMain-Pipeline_release_1.44-HEHP3JF3JUC3QDIC42A5YMRMVQTJR3HJ4P7IFHLSMEGVJNWC55SA@tmp/withMaven21be2166/maven-spy-20170328-094339-928.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 246; columnNumber: 16; Element type "ExecutionEvent" must be followed by either attribute specifications, ">" or "/>".{code}
Add Comment
This message was sent by Atlas
[JIRA] (JENKINS-43159) Generated invalid XML in maven-spy log
Title: Message Title Ollie Robertshaw updated an issue Jenkins / JENKINS-43159 Generated invalid XML in maven-spy log Change By: Ollie Robertshaw Attachment: event spy log sanitized 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-43159) Generated invalid XML in maven-spy log
Title: Message Title Ollie Robertshaw updated an issue Jenkins / JENKINS-43159 Generated invalid XML in maven-spy log Change By: Ollie Robertshaw Summary: Invalid Generated invalid XML in maven-spy log generated 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-43159) Invalid maven-spy log generated
Title: Message Title Ollie Robertshaw created an issue Jenkins / JENKINS-43159 Invalid maven-spy log generated Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2017/Mar/28 12:23 PM Environment: Java 8 Maven 3.3 Jenkins 2.51 Pipeline 2.5 Pipeline Maven Integration Plugin 2.0 Priority: Minor Reporter: Ollie Robertshaw Our maven-spy-*.log file is being generated with broken XML, for example: ... " class=" type="org.apache.maven.lifecycle.internal.DefaultExecutionEvent" _time="ProjectStarted"2017-03-28 12:05:43.464"> ... This happens with other elements too; in this particular case, re-running the job leads to exactly the same malformed XML. This ultimately leads to an error: ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /media/ephemeral0/jenkins/workspace/iMain-Pipeline_release_1.44-HEHP3JF3JUC3QDIC42A5YMRMVQTJR3HJ4P7IFHLSMEGVJNWC55SA@tmp/withMaven21be2166/maven-spy-20170328-094339-928.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 246; columnNumber: 16; Element type "ExecutionEvent" mus
[JIRA] (JENKINS-43152) Not able to run ALM tests using "Execute functional tests from HP ALM"
Title: Message Title Yafim Kazak assigned an issue to xiwen zhao Jenkins / JENKINS-43152 Not able to run ALM tests using "Execute functional tests from HP ALM" Change By: Yafim Kazak Assignee: Ofir Shaked xiwen zhao 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-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Joe Harte edited a comment on JENKINS-41127 Re: Multiple pipeline instances running concurrently when concurrent execution disabled Saw this yet again. Haven't seen the problem in hundreds of builds since my last comment above, and today I see that Jenkins pulled the next 2 builds from the queue and ran them concurrently, event though concurrent building in explicitly disabled. Using latest version of Pipeline plugins available at time of writing, and Jenkins version 2.49 [~jglick] FYI 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-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Joe Harte edited a comment on JENKINS-41127 Re: Multiple pipeline instances running concurrently when concurrent execution disabled Saw this yet again. Haven't seen the problem in hundreds of builds since my last comment above, and today I see that Jenkins pulled the next 2 builds from the queue and ran them concurrently, event though concurrent building in explicitly disabled. Using latest version of Pipeline plugins available at time of writing, and Jenkins version 2.49 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-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Joe Harte updated an issue Jenkins / JENKINS-41127 Multiple pipeline instances running concurrently when concurrent execution disabled Change By: Joe Harte Environment: Jenkins 2.7.1 Jenkins 2.49 Pipeline plugin 2.4 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-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Joe Harte commented on JENKINS-41127 Re: Multiple pipeline instances running concurrently when concurrent execution disabled Saw this yet again. Haven't seen the problem in hundreds of builds since my last comment above, and today I see that Jenkins pulled the next 2 builds from the queue and ran them concurrently, event though concurrent building in explicitly disabled. 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-43156) Provide Node and NPM to Path does not work
Title: Message Title Stephan Krull commented on JENKINS-43156 Re: Provide Node and NPM to Path does not work @Nikolas Falco: OK, sorry for missing the note and all these issues. I can understand your frustration. Will try to build your extra branch. 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-40154) groovy date arithmetics do not work in pipeline
Title: Message Title
Sergey Galkin commented on JENKINS-40154
Re: groovy date arithmetics do not work in pipeline
The same picture almost The code
import groovy.time.TimeCategory
now = new Date()
use(TimeCategory) {
ydate = now - 1.days
}
is working fine but in one perfect day stop working with error
Started by timer
[Pipeline] End of Pipeline
groovy.lang.MissingPropertyException: No such property: days for class: java.lang.Integer
Possible solutions: class
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)
at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:33)
at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
at WorkflowScript.run(WorkflowScript:4)
at WorkflowScript.run(WorkflowScript:3)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
at sun.reflect.GeneratedMethodAccessor1794.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:324)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:78)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:236)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:224)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Finished: FAILURE
[JIRA] (JENKINS-39091) Jira plugin fails to log in to Jira site after dependency updates
Title: Message Title Radek Antoniuk commented on JENKINS-39091 Re: Jira plugin fails to log in to Jira site after dependency updates This was fixed in v 2.3 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-39091) Jira plugin fails to log in to Jira site after dependency updates
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-39091 Jira plugin fails to log in to Jira site after dependency updates Change By: Radek Antoniuk Labels: jira-plugin-2.3 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-43141) fails to connect to jira
Title: Message Title Radek Antoniuk assigned an issue to marlene cote please add valid information on what plugin are you using exactly and what version? Jenkins / JENKINS-43141 fails to connect to jira Change By: Radek Antoniuk Assignee: Radek Antoniuk marlene cote 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-42895) Pipeline stage view is not showing the stages visually
Title: Message Title
Alexander Olofsson edited a comment on JENKINS-42895
Re: Pipeline stage view is not showing the stages visually
Ran into this issue as well,Jenkins ver. 2.52, CentOS 7.3.1611, OpenJDK 1.8.0_121The GET for https://jenkins.fqdn/job/.../wfapi/runs?fullStages=true&_=1490691857430 fails with a 500 error and the following stack trace;{code}java.lang.IllegalStateException: Hit a BlockStartNode with no record of the start! at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.hitParallelStart(ForkScanner.java:554) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:584) at org.jenkinsci.plugins.workflow.graphanalysis.AbstractFlowScanner.next(AbstractFlowScanner.java:212) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:566) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:764) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:635) at com.cloudbees.workflow.rest.external.RunExt.createNew(RunExt.java:318) at com.cloudbees.workflow.rest.external.RunExt.create(RunExt.java:306) at com.cloudbees.workflow.rest.external.JobExt.create(JobExt.java:131) at com.cloudbees.workflow.rest.endpoints.JobAPI.doRuns(JobAPI.java:72) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30)Caused: java.lang.RuntimeException: Unexpected exception while serving JSON at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)...{code} I discovered a way to replicate this as well, just run the following pipeline and this will break;{code:groovy}// Worksstage('Stage A') {echo "A"}// Worksstage('Stage B') {parallel a: {echo "B.A"}, b: {echo "B.B"}}// Breaksstage('Stage C') {def steps = [:]// Empty mapparallel steps}{code}
Add Comment
[JIRA] (JENKINS-42895) Pipeline stage view is not showing the stages visually
Title: Message Title
Alexander Olofsson edited a comment on JENKINS-42895
Re: Pipeline stage view is not showing the stages visually
Ran into this issue as well,Jenkins ver. 2.52, CentOS 7.3.1611, OpenJDK 1.8.0_121The GET for https://jenkins.fqdn/job/.../wfapi/runs?fullStages=true&_=1490691857430 fails with a 500 error and the following stack trace;{code}java.lang.IllegalStateException: Hit a BlockStartNode with no record of the start! at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.hitParallelStart(ForkScanner.java:554) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:584) at org.jenkinsci.plugins.workflow.graphanalysis.AbstractFlowScanner.next(AbstractFlowScanner.java:212) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:566) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:764) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:635) at com.cloudbees.workflow.rest.external.RunExt.createNew(RunExt.java:318) at com.cloudbees.workflow.rest.external.RunExt.create(RunExt.java:306) at com.cloudbees.workflow.rest.external.JobExt.create(JobExt.java:131) at com.cloudbees.workflow.rest.endpoints.JobAPI.doRuns(JobAPI.java:72) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30)Caused: java.lang.RuntimeException: Unexpected exception while serving JSON at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)...{code}I discovered a way to replicate this as well, just run the following pipeline and this will break;{code :groovy }// Worksstage('Stage A') {echo "A"}// Worksstage('Stage B') {parallel a: {echo "B.A"}, b: {echo "B.B"}}// Breaksstage('Stage C') {def steps = [:]// Empty mapparallel steps}{code}
Add Comment
[JIRA] (JENKINS-43141) fails to connect to jira
Title: Message Title Radek Antoniuk assigned an issue to Radek Antoniuk Jenkins / JENKINS-43141 fails to connect to jira Change By: Radek Antoniuk Assignee: Dan Alvizu Radek Antoniuk 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-43141) fails to connect to jira
Title: Message Title Radek Antoniuk edited a comment on JENKINS-43141 Re: fails to connect to jira It seems you have a timeout, check your connectivity. Are you using a proxy? 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-43141) fails to connect to jira
Title: Message Title Radek Antoniuk commented on JENKINS-43141 Re: fails to connect to jira It seems you have a timeout, check your connectivity. 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-43155) Multiple links and graphics when there are several branches
Title: Message Title Jochen A. Fürbacher commented on JENKINS-43155 Re: Multiple links and graphics when there are several branches Yes, Pipeline Multibranch Plugin 2.14. 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-43158) git-lfs support
Title: Message Title Shane O'Hanlon created an issue Jenkins / JENKINS-43158 git-lfs support Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2017/Mar/28 11:00 AM Priority: Minor Reporter: Shane O'Hanlon Issue: User reported that only pointer files were getting pulled into workspace when pulling down large files - no ability to use git-lfs in the plugin. Could git-lfs support be added to this plugin? Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-43155) Multiple links and graphics when there are several branches
Title: Message Title Ulli Hafner commented on JENKINS-43155 Re: Multiple links and graphics when there are several branches Is there another plugin involved to build multiple branches? 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-26583) Env-inject plugin suppress variables contributed by extension points
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-26583 Env-inject plugin suppress variables contributed by extension points Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-26583) Env-inject plugin suppress variables contributed by extension points
Title: Message Title Oleg Nenashev commented on JENKINS-26583 Re: Env-inject plugin suppress variables contributed by extension points I have no short-time plans to work on this, unfortunately. No time && the plugin is open for adoption for more then one year 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-26583) Env-inject plugin suppress variables contributed by extension points
Title: Message Title Nikolas Falco commented on JENKINS-26583 Re: Env-inject plugin suppress variables contributed by extension points This bug it's a real pain in the @$$, I have 8/9 bug open on nodejs component due to 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-43156) Provide Node and NPM to Path does not work
Title: Message Title Nikolas Falco closed an issue as Fixed This sound like duplicate of one of these JENKINS-27170 JENKINS-41762 JENKINS-42323 JENKINS-41857 JENKINS-43066 Do you have EnvInject plugin installed? If yes than you fall in JENKINS-26583 The workaround reported in our wiki page is remove EnvInject plugin, or make a custom build of workaround-26583 branch. (this branch will never merge into master, it's a EnvInject plugin issue not nodejs) Jenkins / JENKINS-43156 Provide Node and NPM to Path does not work Change By: Nikolas Falco Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43157) stage and pipeline view is empty
Title: Message Title Tian Peng updated an issue Jenkins / JENKINS-43157 stage and pipeline view is empty Change By: Tian Peng Priority: Minor Blocker 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-42895) Pipeline stage view is not showing the stages visually
Title: Message Title Alexander Olofsson commented on JENKINS-42895 Re: Pipeline stage view is not showing the stages visually Ran into this issue as well, Jenkins ver. 2.52, CentOS 7.3.1611, OpenJDK 1.8.0_121 The GET for https://jenkins.fqdn/job/.../wfapi/runs?fullStages=true&_=1490691857430 fails with a 500 error and the following stack trace; java.lang.IllegalStateException: Hit a BlockStartNode with no record of the start! at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.hitParallelStart(ForkScanner.java:554) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:584) at org.jenkinsci.plugins.workflow.graphanalysis.AbstractFlowScanner.next(AbstractFlowScanner.java:212) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:566) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:764) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:635) at com.cloudbees.workflow.rest.external.RunExt.createNew(RunExt.java:318) at com.cloudbees.workflow.rest.external.RunExt.create(RunExt.java:306) at com.cloudbees.workflow.rest.external.JobExt.create(JobExt.java:131) at com.cloudbees.workflow.rest.endpoints.JobAPI.doRuns(JobAPI.java:72) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30) Caused: java.lang.RuntimeException: Unexpected exception while serving JSON at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) ... Add Comment
[JIRA] (JENKINS-43157) stage and pipeline view is empty
Title: Message Title Tian Peng updated an issue Jenkins / JENKINS-43157 stage and pipeline view is empty Change By: Tian Peng The stage and pipeline view shows during running of a job.But they just disappear after the running complete.The log:WARNING: Error while serving [ http:// /blue/rest/organizations/jenkins/pipelines/on-build-config/runs/6/nodes/|http:// 10.62.59.175:8080/blue/rest/organizations/jenkins/pipelines/on-build-config/runs/6/nodes/ ] java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor604.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) 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:812) at
[JIRA] (JENKINS-43156) Provide Node and NPM to Path does not work
Title: Message Title
Stephan Krull updated an issue
Jenkins / JENKINS-43156
Provide Node and NPM to Path does not work
Change By:
Stephan Krull
I have updated the NodeJS Plugin yesterday from version 0.2.2 to 1.1.3 on our Jenkins instance. Afterwards I upgraded Jenkins from 2.32.1 to 2.32.3.We have several FreeStyle jobs that are building with Node.js with the following configuration: * set up the path with the corresponding Node.js version, using no specific nprmrc file:!Screenshot from 2017-03-28 10-45-41.png! * then have a shell execution build step running some node or npm commands, you could test with{code:java}node -version{code} After restart of Jenkins all of our jobs fail, it seems like the plugin is not able to prepare the build environment correctly. And here is the console output: !image-2017-03-28-11-09-14-187.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"
[JIRA] (JENKINS-43156) Provide Node and NPM to Path does not work
Title: Message Title Stephan Krull updated an issue Jenkins / JENKINS-43156 Provide Node and NPM to Path does not work Change By: Stephan Krull Attachment: image-2017-03-28-11-09-14-187.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-39818) When using multiple scm repositories, ScmName should be honored
Title: Message Title jbq assigned an issue to jbq Jenkins / JENKINS-39818 When using multiple scm repositories, ScmName should be honored Change By: jbq Assignee: Julien Pivotto jbq 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-43157) stage and pipeline view is empty
Title: Message Title Tian Peng commented on JENKINS-43157 Re: stage and pipeline view is empty My Jenkins version: 2.32.1 plugins: Blue Ocean 1.0.0-rc1 Blue Ocean Pipeline Editor 0.2-rc1 BlueOcean Display URL plugin 1.5.1 blueocean-autofavorite 0.6 bouncycastle API Plugin 2.16.0 Branch API Plugin 2.0.8 Credentials Plugin 2.1.13 Display URL API 1.1.1 Favorite 2.0.4 Folders Plugin 6.0.3 Git plugin 3.1.0 GitHub Branch Source Plugin 2.0.4 Mailer Plugin 1.19 Pipeline Graph Analysis Plugin 1.3 Pipeline: API 2.12 Pipeline: Groovy 2.29 Pipeline: Input Step 2.5 Pipeline: Job 2.10 Pipeline: Model Definition 1.1.1 Pipeline: Nodes and Processes 2.10 Pipeline: Stage Step 2.2 Pipeline: Step API 2.9 Pipeline: Supporting APIs 2.13 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message
[JIRA] (JENKINS-43062) SSH Host Key Verifiers are not configured for all SSH slaves
Title: Message Title Alex Radinsky commented on JENKINS-43062 Re: SSH Host Key Verifiers are not configured for all SSH slaves I just sit 'Save', on each of the nodes without changing anything and the message went away Worked for me as well 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-43157) stage and pipeline view is empty
Title: Message Title Tian Peng created an issue Jenkins / JENKINS-43157 stage and pipeline view is empty Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/28 8:55 AM Priority: Minor Reporter: Tian Peng The stage and pipeline view shows during running of a job. But they just disappear after the running complete. The log: WARNING: Error while serving http://10.62.59.175:8080/blue/rest/organizations/jenkins/pipelines/on-build-config/runs/6/nodes/ java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor604.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at
