[JIRA] [core] (JENKINS-27663) Bad execution time for jobs periodically executed
Title: Message Title Ludovic Vercruysse closed an issue as Fixed We were facing performance issues on an internal instance of one of our source code repositories. Solving it solved exactly at the same time the timer issues on Jenkins. It makes me think that some Jenkins threads were trying to access to this source code repository and did not get any proper response which could have had impacted the Jenkins triggers. Jenkins / JENKINS-27663 Bad execution time for jobs periodically executed Change By: Ludovic Vercruysse Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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,
[JIRA] [build-name-setter-plugin] (JENKINS-31558) Exception on load plugin
Title: Message Title eloy coto created an issue Jenkins / JENKINS-31558 Exception on load plugin Issue Type: Bug Assignee: Lev Mishin Components: build-name-setter-plugin Created: 16/Nov/15 8:47 AM Environment: Jenkins ver. 1.638 build-name-setter 1.5.1 Build Environment Plugin 1.6 Priority: Minor Reporter: eloy coto Hi, I'm getting this error when I install Build name setter plugin. Any idea? 1) Error injecting constructor, java.lang.NoClassDefFoundError: org/jenkinsci/plugins/tokenmacro/MacroEvaluationException at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter$DescriptorImpl.(BuildNameSetter.java:73) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:427) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(Injecto
[JIRA] [build-name-setter-plugin] (JENKINS-31558) Exception on load plugin
Title: Message Title
eloy coto updated an issue
Jenkins / JENKINS-31558
Exception on load plugin
Change By:
eloy coto
Hi, I'm getting this error when I install Build name setter plugin. Any idea? {code}1) Error injecting constructor, java.lang.NoClassDefFoundError: org/jenkinsci/plugins/tokenmacro/MacroEvaluationException at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter$DescriptorImpl.(BuildNameSetter.java:73)1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:427) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:389) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:380) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:388) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at hudson.diagnosis.NullIdDescriptorMonitor.verify(NullIdDescriptorMonitor.java:68) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:913) 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/tokenmacro/MacroEvaluationException at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2625) at java.lang.Class.getMethod0(Class.java:2866) at java.lang.Class.getMethod(Class.java:1676) at hudson.model.Descriptor.(Descriptor.java:284) at hudson.tasks.BuildWrapperDescriptor.(BuildWrapperDescriptor.java:49) at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter$DescriptorImpl.(BuildNameSetter.java:73) at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter$DescriptorImpl$$FastClassByGuice$$5c4151fb.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.
[JIRA] [build-name-setter-plugin] (JENKINS-31558) Exception on load plugin
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31558 Re: Exception on load plugin eloy coto, this plugin declares token-macro as optional. I recommend you to install that plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [build-name-setter-plugin] (JENKINS-31558) Exception on load plugin
Title: Message Title
Manuel Jesús Recena Soto edited a comment on JENKINS-31558
Re: Exception on load plugin
[~eloycoto], this plugin [declares|https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin] {{token-macro}} as optional. I recommend you to install that plugin. If the plugin is installed, verify the version.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-31518) "Discard old builds" setting lost between 1.634 and 1.637
Title: Message Title mwebber commented on JENKINS-31518 Re: "Discard old builds" setting lost between 1.634 and 1.637 >> Ought to be fixed in the upcoming 1.639. Thanks for reporting and apologies for any disruption. No worries, thanks for your prompt attention to this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [build-name-setter-plugin] (JENKINS-31558) Exception on load plugin
Title: Message Title eloy coto commented on JENKINS-31558 Re: Exception on load plugin Hi Manuel Jesús Recena Soto, I've just installed token-macro and plugin start to work. Many thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31559) All Jenkins jobs are automatically launched after the restart of the Jenkins instance
Title: Message Title Ludovic Vercruysse created an issue Jenkins / JENKINS-31559 All Jenkins jobs are automatically launched after the restart of the Jenkins instance Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Nov/15 9:16 AM Priority: Critical Reporter: Ludovic Vercruysse Dear, Regularly, we face an issue with one of our Jenkins instance (based on 1.596.3): we restart the Jenkins instance on a daily basis at 00:15am CEST, and regularly (once per week), *+all +*Jenkins jobs are automatically started just after the restart of the instance, even if there was no change in the source code repositories and even if the job is not triggered. We did not see any specific message in the logs of our instance, which could allow us to have more information about this issue. Could you please provide us some help on this issue ? Best regards Add Comment
[JIRA] [build-name-setter-plugin] (JENKINS-31558) Exception on load plugin
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-31558 Exception on load plugin Change By: Manuel Jesús Recena Soto Assignee: Lev Mishin Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [build-name-setter-plugin] (JENKINS-31558) Exception on load plugin
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31558 Re: Exception on load plugin eloy coto, anyway, this behavior should be managed in a better way. Please, updated the state of this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [build-name-setter-plugin] (JENKINS-31558) Exception on load plugin
Title: Message Title Manuel Jesús Recena Soto resolved as Fixed token-macro plugin had to be installed. Jenkins / JENKINS-31558 Exception on load plugin Change By: Manuel Jesús Recena Soto Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [build-name-setter-plugin] (JENKINS-31558) Exception on load plugin
Title: Message Title eloy coto closed an issue as Fixed Jenkins / JENKINS-31558 Exception on load plugin Change By: eloy coto Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-31503) unable to send email to svn committers
Title: Message Title malik alighrair commented on JENKINS-31503 Re: unable to send email to svn committers thank you for your reply, and yes email-ext is running perfectly, but I tried to fill in the "Default user e-mail suffix" but it tried to send email to : e14...@companyname.com not to the outlook account: malik@companyname,com Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31560) displayName for slaves
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-31560 displayName for slaves Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Nov/15 9:31 AM Priority: Minor Reporter: Kanstantsin Shautsou When dealing with Cloud API you can set slave name only during creating slave time. Different users wants see different slave name and i can suggest implement displayName pattern that exists for jobs and other objects. displayName should be an additional field in Node Slave Computer that should be displayed in UI. PS. existed setName(String) is wrong for runtime usage as it screws hashCode cc stephenconnolly Add Comment
[JIRA] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Title: Message Title Tim-Christian Bloss commented on JENKINS-26545 Re: Persist build(s) log(s) in MySQL (or similar) Hi, maybe I'm not fully aware of the structure builds are stored in, but I think can understand a little bit what's the intention to store builds including build log in databases. For me it looks like Jenkins reads jobs (jobs/*/config.xml) as well as some parts of the builds of each job everytime the Jenkins master gets started. Same goes for file system based config-history. At least our splitted file system shows such activity every time the Jenkins master gets started (splitting listed later on). From what I see on our file systems, each build of most of our jobs jobs contains something like "build.xml" "log" "revision.txt" "InjectedEnvVars.txt" "changelog.xml" Maybe build/log doesn't get read permanently, but I would suspect the build.xml might contain valuable information, possibly even the txt files.. We splitted jenkins to different disks to hunt down some massive performance issues we ran into, namely /dev/sdb1 30G 1,2G 27G 5% /opt/jenkins /dev/sdg1 40G 7,0G 31G 19% /opt/jenkins/jenkins_jobs_builds ---> defined using tmpfs 4,0G 732K 4,0G 1% /opt/jenkins/temp tmpfs 4,0G 0 4,0G 0% /opt/jenkins/fingerprints /dev/sdd1 197G 6,0G 181G 4% /opt/jenkins/jobs /dev/sdc1 50G 4,2G 43G 10% /opt/jenkins/config-history When starting Jenkins master, disk activity "breaks any scale" on our monitoring on disks containing /opt/jenkins/jenkins_jobs_builds /opt/jenkins/jobs /opt/jenkins/config-history We've already cut down job history to only two builds in history for each job, otherwise we sometimes got startup times far beyond half an hour (even more than one hour as we were running Jenkins master on Windows previously). In all maven builds we disabled fingerprinting as it became possible to do so, as we needed to flush the tmpfs /opt/jenkins/fingerprints nearly once per minute before. Maybe we're an example of a company excessively using jenkins or simply "building too large projects too often" as some might think. Regarding our experiences, it would really be useful to store as much data as possible in some database, limiting data reads to just the used fields (maybe who started a build and when it happened, what were the test results and so on) instead of reading build.xml for more than 200 maven modules per single build run per job. Also regarding portability for test systems (on site integration testing before upgrading production systems) as well as high availability it would be easier to store configuration and job data in a (replicated) database rather than using a file system.
[JIRA] [core] (JENKINS-26684) Maven build step fail to launch mvn process when special chars are present in build variables
Title: Message Title vtintillier commented on JENKINS-26684 Re: Maven build step fail to launch mvn process when special chars are present in build variables Not sure if this will help in your case, but I workaround this by unchecking the "Escape Quotes in Parameter Values" option in the Gerrit Trigger Advanced Options. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-16352) Add ability to specify parameters in the crontab
Title: Message Title Baptiste Mathus commented on JENKINS-16352 Re: Add ability to specify parameters in the crontab Daniel Beck just found this issue and the plugin above. > Let the job be parameterless (or at least without these parameters), and determine day of week in the build script and adapt behavior there. Actually, for the use case that led me here, that wouldn't seem doable: in our situation, people who are going to specify those values aren't developers/very technical. It's far easier to ask them to specify cron + param=value form than to twiddle with shell-scripting. So I'd personnally like to consider this plugin get forked. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [parameterized-trigger-plugin] (JENKINS-31561) WARNING: deprecated call to Run.getEnvironment
Title: Message Title Magnus Jacobsson created an issue Jenkins / JENKINS-31561 WARNING: deprecated call to Run.getEnvironment Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 16/Nov/15 11:26 AM Priority: Minor Reporter: Magnus Jacobsson Log fills up with messages like: nov 16, 2015 12:01:23 EM hudson.model.Run getEnvironment WARNING: deprecated call to Run.getEnvironment at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.resolveProject(BuildTriggerConfig.java:259) Add Comment
[JIRA] [mailer-plugin] (JENKINS-26740) Failed to set Jenkins Identity header on email. java.lang.NullPointerException
Title: Message Title Gunasekaran Mohandoss commented on JENKINS-26740 Re: Failed to set Jenkins Identity header on email. java.lang.NullPointerException Any update on this issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [parameterized-trigger-plugin] (JENKINS-31561) WARNING: deprecated call to Run.getEnvironment
Title: Message Title Magnus Jacobsson updated an issue Jenkins / JENKINS-31561 WARNING: deprecated call to Run.getEnvironment Change By: Magnus Jacobsson Environment: Linux metaria 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC 2015 x86_64 x86_64 x86_64 GNU/LinuxJenkins ver. 1.638Parameterized Trigger plugin 2.29 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31562) remoting-2.53 has the outdated certificate
Title: Message Title Oleg Nenashev moved an issue Jenkins / JENKINS-31562 remoting-2.53 has the outdated certificate Change By: Oleg Nenashev Project: Security Issues Jenkins Key: SECURITY JENKINS - 231 31562 Workflow: Security v1.2 JNJira Status: Untriaged Open Component/s: core Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-31562) remoting-2.53 has the outdated certificate
Title: Message Title Oleg Nenashev commented on JENKINS-31562 Re: remoting-2.53 has the outdated certificate fixed the project Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31560) displayName for slaves
Title: Message Title Kanstantsin Shautsou assigned an issue to Kanstantsin Shautsou Jenkins / JENKINS-31560 displayName for slaves Change By: Kanstantsin Shautsou Assignee: Kanstantsin Shautsou Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31560) displayName for slaves
Title: Message Title
Kanstantsin Shautsou updated an issue
Jenkins / JENKINS-31560
displayName for slaves
Change By:
Kanstantsin Shautsou
When dealing with Cloud API you can set slave name only during creating slave time.Different users wants see different slave name and i can suggest implement {{displayName}} pattern that exists for jobs and other objects. {{displayName}} should be an additional mutable field in {{Node}}(?) {{Slave}}(?) {{Computer}}(?) that should be displayed in UI. PS. existed {{setName(String)}} is wrong for runtime usage as it screws {{hashCode}}cc [~stephenconnolly]
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [nodejs-plugin] (JENKINS-31485) NodeJS Invalid Tool ID
Title: Message Title Code Destroyer commented on JENKINS-31485 Re: NodeJS Invalid Tool ID Same here... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [environment-script-plugin] (JENKINS-20705) Environment Script does not work on Windows Master
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20705 Re: Environment Script does not work on Windows Master Code changed in jenkins User: Dawid Malinowski Path: src/main/java/com/lookout/jenkins/EnvironmentScript.java src/main/java/com/lookout/jenkins/commands/Commands.java src/main/java/com/lookout/jenkins/commands/PowerShell.java src/main/java/com/lookout/jenkins/commands/Shebangs.java src/main/java/com/lookout/jenkins/commands/UnixShell.java src/main/java/com/lookout/jenkins/commands/WinBatch.java src/main/resources/com/lookout/jenkins/EnvironmentScript/config.jelly src/test/java/com/lookout/jenkins/EnvironmentScriptMatrixTest.java src/test/java/com/lookout/jenkins/EnvironmentScriptTest.java http://jenkins-ci.org/commit/environment-script-plugin/2ad196af1be58fef475f9b65ae7431bd02bf7134 Log: JENKINS-20705 - Environment Script does not work on Windows Master Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [environment-script-plugin] (JENKINS-20705) Environment Script does not work on Windows Master
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20705 Re: Environment Script does not work on Windows Master Code changed in jenkins User: Dawid Malinowski Path: src/main/java/com/lookout/jenkins/EnvironmentScript.java src/main/java/com/lookout/jenkins/commands/Commands.java src/main/java/com/lookout/jenkins/commands/PowerShell.java src/main/java/com/lookout/jenkins/commands/Shebangs.java src/main/java/com/lookout/jenkins/commands/UnixShell.java src/main/java/com/lookout/jenkins/commands/WinBatch.java src/main/resources/com/lookout/jenkins/EnvironmentScript/config.jelly src/test/java/com/lookout/jenkins/EnvironmentScriptMatrixTest.java src/test/java/com/lookout/jenkins/EnvironmentScriptTest.java http://jenkins-ci.org/commit/environment-script-plugin/606fed900bd6ad6891b8dc469cbfc3e9ed4ba185 Log: Merge pull request #9 from dawidmalina/JENKINS-20705 JENKINS-20705 - Environment Script does not work on Windows Master Compare: https://github.com/jenkinsci/environment-script-plugin/compare/5104bb10dffc...606fed900bd6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [flexible-publish-plugin] (JENKINS-31410) Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed
Title: Message Title ikedam resolved as Not A Defect Jenkins / JENKINS-31410 Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed Change By: ikedam Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [copyartifact-plugin] (JENKINS-31563) Latest successful artifact cannot be copied from Maven build
Title: Message Title ritzmann created an issue Jenkins / JENKINS-31563 Latest successful artifact cannot be copied from Maven build Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 16/Nov/15 12:34 PM Environment: Jenkins 1.625.2, Copy Artifact Plugin 1.37 Priority: Major Reporter: ritzmann Steps to reproduce: Create Maven build job #1. In the build job, check "Disable automatic artifact archiving". Create build job #2. Add "Copy artifacts from another project" build step. Set "Project name" to project #1. Set "Which build" to "latest successful build". Set "Artifacts to copy" to an existing artifact in project #1, e.g. **/my.war. Build job #2 fails with this error: Unable to access upstream artifacts
[JIRA] [environment-script-plugin] (JENKINS-20705) Environment Script does not work on Windows Master
Title: Message Title Dawid Malinowski resolved as Fixed Your ticket was resolved. Thank you for your feedback. Jenkins / JENKINS-20705 Environment Script does not work on Windows Master Change By: Dawid Malinowski Status: Open Resolved Assignee: Dawid Malinowski Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [environment-script-plugin] (JENKINS-20705) Environment Script does not work on Windows Master
Title: Message Title Dawid Malinowski closed an issue as Fixed Jenkins / JENKINS-20705 Environment Script does not work on Windows Master Change By: Dawid Malinowski Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [environment-script-plugin] (JENKINS-26673) Environment Script leaves files in /tmp on Ubuntu
Title: Message Title Dawid Malinowski closed an issue as Fixed Jenkins / JENKINS-26673 Environment Script leaves files in /tmp on Ubuntu Change By: Dawid Malinowski Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [environment-script-plugin] (JENKINS-30762) Environment script fails with job name shorter than 3 characters
Title: Message Title Dawid Malinowski closed an issue as Fixed Jenkins / JENKINS-30762 Environment script fails with job name shorter than 3 characters Change By: Dawid Malinowski Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [environment-script-plugin] (JENKINS-26765) BUILD_ID is now providing BUILD_NUMBER as output
Title: Message Title Dawid Malinowski closed an issue as Not A Defect Jenkins / JENKINS-26765 BUILD_ID is now providing BUILD_NUMBER as output Change By: Dawid Malinowski Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [environment-script-plugin] (JENKINS-14794) Console output parsing for env vars is a little too loose
Title: Message Title Dawid Malinowski closed an issue as Not A Defect Jenkins / JENKINS-14794 Console output parsing for env vars is a little too loose Change By: Dawid Malinowski Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [environment-script-plugin] (JENKINS-14951) In a Matrix job, Environment Script variables are not expanded in a Parameterized Build Trigger
Title: Message Title Dawid Malinowski closed an issue as Fixed Jenkins / JENKINS-14951 In a Matrix job, Environment Script variables are not expanded in a Parameterized Build Trigger Change By: Dawid Malinowski Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31562) remoting-2.53 has the outdated certificate
Title: Message Title Jesse Glick commented on JENKINS-31562 Re: remoting-2.53 has the outdated certificate I guess this should become an acceptance test using a `DockerFixture` with a specific JRE installation, so we could catch such problems mechanically before release. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Title: Message Title Kenneth Baltrinic commented on JENKINS-26587 Re: Checkout fails with Multiple SCMs plugin on commit notification We are generally leary of pre-release stuff here. I can try to get it approved but first, where is it? I dont' see it as an attachment here, nor is it in the archive folder for the git plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Title: Message Title Kenneth Baltrinic edited a comment on JENKINS-26587 Re: Checkout fails with Multiple SCMs plugin on commit notification We are generally leary leery of pre-release stuff here. I can try to get it approved but first, where is it? I dont don ' t see it as an attachment here, nor is it in the archive folder for the git plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31562) remoting-2.53 has the outdated certificate
Title: Message Title Jesse Glick commented on JENKINS-31562 Re: remoting-2.53 has the outdated certificate Maybe also a unit test in `core` verifying that the certificate is good for at least six months or so. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31562) remoting-2.53 has the outdated certificate
Title: Message Title Oleg Nenashev commented on JENKINS-31562 Re: remoting-2.53 has the outdated certificate +1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31562) remoting-2.53 has the outdated certificate
Title: Message Title Oleg Nenashev commented on JENKINS-31562 Re: remoting-2.53 has the outdated certificate Troubleshooting and "fixes": http://java.com/en/download/help/appsecuritydialogs.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Title: Message Title Mark Waite commented on JENKINS-26587 Re: Checkout fails with Multiple SCMs plugin on commit notification The pre-release is hosted on my google drive (click the git-plugin.hpi link in the comment). If that's uncomfortable, you're also welcome to clone the sources and compile the plugin from source code. It should pass all the automated tests in the source code. If you're willing to do some searching, you may also be able to find the build on the CloudBees hosted job which compiles and tests the plugin when new commits are detected. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31564) Windows Slave service cannot be installed on Windows Service 2012 R2 due to the missing .NET3.5
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-31564 Windows Slave service cannot be installed on Windows Service 2012 R2 due to the missing .NET3.5 Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: Screen Shot 2015-11-16 at 16.19.56.png Components: core, windows-slaves-plugin Created: 16/Nov/15 1:20 PM Environment: winsw-1.19 and all others Labels: winsw Priority: Minor Reporter: Oleg Nenashev WinSW is packaged for .NET 2.0, which is missing in modern Windows versions by default. Happens on winsw-1.19, see the attachment. Issue for winsw:
[JIRA] [multiple-scms-plugin] (JENKINS-30243) NoClassDefFoundError during startup (Template Project plugin 1.5)
Title: Message Title Thorsten Kahler updated an issue Jenkins / JENKINS-30243 NoClassDefFoundError during startup (Template Project plugin 1.5) Change By: Thorsten Kahler Environment: Jenkins 1.609.2Java(TM) SE Runtime Environment (build 1.7.0_71-b14)CentOS Template Project plugin 1.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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.
FORM THE DESK OF Mr Ibrahim Aliu
Dear Friend I am Mr Ibrahim Aliu a banker from one of the international bank here in my country. Although I know that it is very hard to trust or believe people nowadays but I have developed my trust in you before deciding to share this confidential business proposal. Four years ago, most of the African politicians used our bank to launder funds to overseas through the help of their political advisers and I find out what was going because these days some of the funds where stock for politicians. I was able to divert ($15.2 Million United States dollars) to an escrow account that belong to unknown person. So I will want you to act as the depositor of the fund because the bank do not know the owner of the fund and also the claim is legal as I have make all the good arrangement to transfer the fund to foreign account if only you are ready and wiling to work with me. I will tell you the details and procedures on how the transfer will be executed immediately I hear from you. Yours sincerely, Mr Ibrahim Aliu -- You received this message because you are subscribed to the Google 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] [copyartifact-plugin] (JENKINS-12918) a job dedicated to copyartifacts from a build specified by a build paramter (ie a run parameter) fails when launched manuallyco
Title: Message Title Anentropic commented on JENKINS-12918 Re: a job dedicated to copyartifacts from a build specified by a build paramter (ie a run parameter) fails when launched manuallyco +1 to Adam's comment above, this is totally confusing the "Build selector for Copy Artifact" is useless in this case since you can't select builds from another project, whereas the "Run parameter" already does what is needed and should be reused Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [copyartifact-plugin] (JENKINS-12918) a job dedicated to copyartifacts from a build specified by a build paramter (ie a run parameter) fails when launched manuallyco
Title: Message Title Anentropic updated an issue Jenkins / JENKINS-12918 a job dedicated to copyartifacts from a build specified by a build paramter (ie a run parameter) fails when launched manuallyco Change By: Anentropic Comment: +1 to Adam's comment above, this is totally confusingthe "Build selector for Copy Artifact" is useless in this case since you can't select builds from another project, whereas the "Run parameter" already does what is needed and should be reused Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ccm-plugin] (JENKINS-31565) CCM Plugin help option ERROR: Failed to load help file: Not Found
Title: Message Title Laura Phelan created an issue Jenkins / JENKINS-31565 CCM Plugin help option ERROR: Failed to load help file: Not Found Issue Type: Bug Assignee: Bruno P. Kinoshita Components: ccm-plugin Created: 16/Nov/15 1:31 PM Environment: Jenkins ver. 1.596.3 Priority: Major Reporter: Laura Phelan In job configurations, upon clicking the blue ? icon for help in the "Publish CCM analysis results" section, I am getting the error: ERROR: Failed to load help file: Not Found Was the plugin installed correctly, or is this a bug with the plugin, as it is listed in the changelog as being implemented in version1.1 of the plugin.
[JIRA] [copyartifact-plugin] (JENKINS-12918) a job dedicated to copyartifacts from a build specified by a build paramter (ie a run parameter) fails when launched manuallyco
Title: Message Title
Anentropic commented on JENKINS-12918
Re: a job dedicated to copyartifacts from a build specified by a build paramter (ie a run parameter) fails when launched manuallyco
+1 to Adam's comment, this is confusing and frustrating
using a "Build selector for Copy Artifact" parameter is not possible because it does not provide a way to select a build from another project (the upstream and downstream options are too restrictive)
a "Run parameter" makes the necessary selection possible, and should have been reused, but it seems it is not possible for Copy Artifacts to use that kind of parameter, I tried:
"specified by a build parameter" ...already noted above doesn't work
"specific build" and $ {MY_RUN_PARAM_NAME}
as the value ...doesn't work
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-31564) Windows Slave service cannot be installed on Windows Service 2012 R2 due to the missing .NET3.5
Title: Message Title James Nord commented on JENKINS-31564 Re: Windows Slave service cannot be installed on Windows Service 2012 R2 due to the missing .NET3.5 this is not a bug. .net2 is a core windows feature in everything post XP. in 2012 you need to enable it - which is what the error message is telling you how to do. Once you enable that windows feature it all works as it should. Compare with JENKINS-30280. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-18666) Submodule reference
Title: Message Title SCM/JIRA link daemon commented on JENKINS-18666 Re: Submodule reference Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/GitSCMBackwardCompatibility.java src/main/java/hudson/plugins/git/extensions/impl/SubmoduleOption.java src/main/resources/hudson/plugins/git/extensions/impl/SubmoduleOption/config.groovy src/main/resources/hudson/plugins/git/extensions/impl/SubmoduleOption/help-reference.html http://jenkins-ci.org/commit/git-plugin/1840aff6a2422a771fba798a0b10595878eb7ff3 Log: Merge pull request #348 from nKey/submodule-reference-new [FIXED JENKINS-18666] Submodule reference Compare: https://github.com/jenkinsci/git-plugin/compare/2c2dae0e23bc...1840aff6a242 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-18666) Submodule reference
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-18666 Submodule reference Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ghprb-plugin] (JENKINS-31566) PROBLEM Report - Jenkins ver. 1.609.3
Title: Message Title Antonio D'Errico created an issue Jenkins / JENKINS-31566 PROBLEM Report - Jenkins ver. 1.609.3 Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 16/Nov/15 1:49 PM Environment: Jenkins ver. 1.609.3 Priority: Minor Reporter: Antonio D'Errico Hello, we have the problem that jenkins stops running when we open jobs which use the DSL plugin. Best regards Toni Add Comment
[JIRA] [core] (JENKINS-31567) PROBLEM Report - Jenkins ver. 1.609.3 - org.apache.http.nio.protocol.HttpAsyncRequestExecutor exception
Title: Message Title Antonio D'Errico created an issue Jenkins / JENKINS-31567 PROBLEM Report - Jenkins ver. 1.609.3 - org.apache.http.nio.protocol.HttpAsyncRequestExecutor exception Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Nov/15 1:52 PM Priority: Minor Reporter: Antonio D'Errico Hello, we have many errors like this: Nov 16, 2015 2:49:53 PM org.apache.http.nio.protocol.HttpAsyncRequestExecutor exception SEVERE: http-outgoing-1 [CLOSED] HTTP protocol exception: null java.nio.channels.ClosedChannelException at sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:257) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:300) at org.apache.http.nio.reactor.ssl.SSLIOSession.receiveEncryptedData(SSLIOSession.java:346) at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:377) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:118) at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:220) at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:284) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:613) at java.lang.Thread.run(Thread.java:745) Nov 16, 2015 2:49:53 PM org.apache.http.nio.protocol.HttpAsyncRequestExecutor exception SEVERE: http-outgoing-3 [CLOSED] HTTP protocol exception: null java.nio.channels.ClosedChannelException at sun.nio.ch.SocketChannelImpl.ensureReadOpen(So
[JIRA] [ghprb-plugin] (JENKINS-31566) PROBLEM Report - Jenkins ver. 1.609.3
Title: Message Title Antonio D'Errico commented on JENKINS-31566 Re: PROBLEM Report - Jenkins ver. 1.609.3 We have installed the Job DSL Plugin v1.38 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [urltrigger-plugin] (JENKINS-30188) URL Trigger doesn't work and gives NullPointerException
Title: Message Title Daniel Beck commented on JENKINS-30188 Re: URL Trigger doesn't work and gives NullPointerException The trigger has a null job. Could be related to an optimization that was in core between 1.621 and 1.634 before getting reverted. Does this issue occur with current LTS or main line releases? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31568) PROBLEM Report - Jenkins ver. 1.609.3 - Windows Server Slave
Title: Message Title Antonio D'Errico created an issue Jenkins / JENKINS-31568 PROBLEM Report - Jenkins ver. 1.609.3 - Windows Server Slave Issue Type: Bug Assignee: Unassigned Attachments: error-slave.PNG Components: core Created: 16/Nov/15 2:02 PM Priority: Minor Reporter: Antonio D'Errico Hello, we want to connect a Windows Server as a slave via JAVA Web Start. We get the error attached. Best regards Toni Add Comment
[JIRA] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons stopped work on JENKINS-30852 Change By: Christopher Simons Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-16352) Add ability to specify parameters in the crontab
Title: Message Title Daniel Beck commented on JENKINS-16352 Re: Add ability to specify parameters in the crontab I have nothing against a plugin, but James Wilson argued for making this a core feature. If James can commit to maintaining it, I see no problem in forking it into jenkinsci and releasing it into the Jenkins community update site. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons assigned an issue to Unassigned Jenkins / JENKINS-30852 404 Error saving a View with non URL-safe characters Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-31503) unable to send email to svn committers
Title: Message Title Alex Earl commented on JENKINS-31503 Re: unable to send email to svn committers Then the email address for thwt user in svn would need to be filled in. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-16352) Add ability to specify parameters in the crontab
Title: Message Title James Wilson commented on JENKINS-16352 Re: Add ability to specify parameters in the crontab It's been a while. The best I can remember about plugin vs core for this functionality was centered around how hard it was to create the plugin. I think it felt a bit out-of-phase as a plugin. I completely understand the hesitance to add something like this to core as it would have a relatively small audience of users. That being said, I should have taken the final step to register the plugin with Jenkins so others can discover it easier. Maybe it has a larger audience than I think. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [urltrigger-plugin] (JENKINS-30188) URL Trigger doesn't work and gives NullPointerException
Title: Message Title Magnus Jacobsson commented on JENKINS-30188 Re: URL Trigger doesn't work and gives NullPointerException Tanks Daniel for your quick response. I was running 1.628 until this morning when I upgraded to 1.638. I haven't seen the problem since, but I think it's to soon to say it's gone, because I don't know what I have done before that triggered the problem. I haven't tried the LTS (wasn't even aware that it existed). Keeping my finger crossed though. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-29705) Virtual thread dump
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29705 Re: Virtual thread dump Code changed in jenkins User: Kohsuke Kawaguchi Path: api/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadDumpAction.java cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsThreadDump/index.jelly job/src/main/java/org/jenkinsci/plugins/workflow/job/ActionFromFlowExecution.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/5e8fdbdc91f9539324a7a57e1e97ef70f813351f Log: JENKINS-29705 Exposed thread dump over HTTP Compare: https://github.com/jenkinsci/workflow-plugin/compare/12cf061e0d55^...5e8fdbdc91f9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-29705) Virtual thread dump
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29705 Re: Virtual thread dump Code changed in jenkins User: Kohsuke Kawaguchi Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/CpsThreadDumpTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsBodyExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThread.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadDump.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadGroup.java http://jenkins-ci.org/commit/workflow-plugin/12cf061e0d55143abcaef628625420abe76d35ed Log: JENKINS-29705 added thread dump support Implemented the code to obtain the whole program state dump from CpsThreadGroup. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [teamconcert-plugin] (JENKINS-30245) Missing Credentials in Global Team Concert/RTC configuration
Title: Message Title Timo Weber commented on JENKINS-30245 Re: Missing Credentials in Global Team Concert/RTC configuration Maybe this is related: After the last update of the Artifactory Plugin we experienced the same. The Artifactory Plugin now optionally supports the credentials plugin and its configuration has an empty credentialsId-Tag as default. It seems that the teamconcert plugin reads this empty tag and not his own tag. After enabling the credentials for artifactory they showed up in the teamconcert configuration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [copyartifact-plugin] (JENKINS-31569) Should be able to use a 'Run parameter' to select build to copy from
Title: Message Title Anentropic created an issue Jenkins / JENKINS-31569 Should be able to use a 'Run parameter' to select build to copy from Issue Type: New Feature Assignee: Unassigned Components: copyartifact-plugin Created: 16/Nov/15 3:11 PM Priority: Minor Reporter: Anentropic I encountered the same problem as described in https://issues.jenkins-ci.org/browse/JENKINS-12918 This plugin should be able to accept 'Run parameter' as source build to copy from. As suggested in comments there, I am opening this as a feature request. I am not a Java developer but I will try and get this associated pull request https://github.com/jenkinsci/copyartifact-plugin/pull/75 , which has languished since 2013, into a mergeable state. Hopefully I am not wasting my time. Add Comment
[JIRA] [copyartifact-plugin] (JENKINS-31569) Should be able to use a 'Run parameter' to select build to copy from
Title: Message Title Anentropic updated an issue Jenkins / JENKINS-31569 Should be able to use a 'Run parameter' to select build to copy from Change By: Anentropic I encountered the same problem as described in https://issues.jenkins-ci.org/browse/JENKINS-12918This plugin should be able to accept 'Run parameter' as source build to copy from.As suggested in comments there, I am opening this as a feature request. I am not a Java developer but I will try and get this associated pull request https://github.com/jenkinsci/copyartifact-plugin/pull/75 , which has languished since 2013, into a mergeable state. Hopefully I am not wasting my time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31160) Update Jenkins UI not to call everything a "Build"
Title: Message Title Magnus Jacobsson commented on JENKINS-31160 Re: Update Jenkins UI not to call everything a "Build" "Run" or "Execution" perhaps? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [copyartifact-plugin] (JENKINS-31569) Should be able to use a 'Run parameter' to select build to copy from
Title: Message Title Anentropic updated an issue Jenkins / JENKINS-31569 Should be able to use a 'Run parameter' to select build to copy from Change By: Anentropic I encountered the same problem as described in https://issues.jenkins-ci.org/browse/JENKINS-12918This plugin should be able to accept 'Run parameter' as source build to copy from.As suggested in comments there, I am opening this as a feature request.I am not a Java developer but I will try and get this associated pull request https://github.com/jenkinsci/copyartifact-plugin/pull/75 (which has languished since 2013 as [PR#17](https://github.com/jenkinsci/copyartifact-plugin/pull/17)) into a mergeable state. Hopefully I am not wasting my time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [copyartifact-plugin] (JENKINS-31569) Should be able to use a 'Run parameter' to select build to copy from
Title: Message Title Anentropic updated an issue Jenkins / JENKINS-31569 Should be able to use a 'Run parameter' to select build to copy from Change By: Anentropic I encountered the same problem as described in https://issues.jenkins-ci.org/browse/JENKINS-12918This plugin should be able to accept 'Run parameter' as source build to copy from.As suggested in comments there, I am opening this as a feature request.I am not a Java developer but I will try and get this associated pull request https://github.com/jenkinsci/copyartifact-plugin/pull/75 , ( which has languished since 2013 , as [PR#17](https://github.com/jenkinsci/copyartifact-plugin/pull/17)) into a mergeable state. Hopefully I am not wasting my time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [copyartifact-plugin] (JENKINS-31569) Should be able to use a 'Run parameter' to select build to copy from
Title: Message Title Anentropic updated an issue Jenkins / JENKINS-31569 Should be able to use a 'Run parameter' to select build to copy from Change By: Anentropic I encountered the same problem as described in https://issues.jenkins-ci.org/browse/JENKINS-12918This plugin should be able to accept 'Run parameter' as source build to copy from.As suggested in comments there, I am opening this as a feature request.I am not a Java developer but I will try and get this associated pull request https://github.com/jenkinsci/copyartifact-plugin/pull/75 (which has languished since 2013 as [PR#17 ]( | https://github.com/jenkinsci/copyartifact-plugin/pull/17 ] ) ) into a mergeable state. Hopefully I am not wasting my time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-31570) Checkpoints Do Cannot Be Resumed From with Global Functions - Failed to Load Persisted Workflow State
Title: Message Title Mark Baker created an issue Jenkins / JENKINS-31570 Checkpoints Do Cannot Be Resumed From with Global Functions - Failed to Load Persisted Workflow State Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 16/Nov/15 3:24 PM Environment: Jenkins Version = 1.609.3.1 Workflow Plugin Version = 1.10 Gradle Version = 2.2.1 Priority: Minor Reporter: Mark Baker When using the global class library to define functions as described here https://github.com/jenkinsci/workflow-plugin/blob/master/cps-global-lib/README.md#define-more-structured-dsl, checkpoints cannot be resumed from. The first run of the workflow will work fine, but when you try to resume from a checkpoint, the following error apears. Restored from stage 5 in #3 Running: End of Workflow java.io.IOException: Failed to load persisted workflow state at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:507) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:505) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:546) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32) at java.util.concurrent
[JIRA] [multijob-plugin] (JENKINS-31571) Last Success date on downstream builds is reporting last Success date of parent, not their own success
Title: Message Title Igor Tanfilyev created an issue Jenkins / JENKINS-31571 Last Success date on downstream builds is reporting last Success date of parent, not their own success Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 16/Nov/15 3:26 PM Priority: Minor Reporter: Igor Tanfilyev If we have multijobs and 2 builds: pass and second fail and some downstream job that passed in both cases, this job will be have last success date from first run. Add Comment
[JIRA] [core] (JENKINS-31560) displayName for slaves
Title: Message Title Kanstantsin Shautsou commented on JENKINS-31560 Re: displayName for slaves Oooops this functionality existed, not sure how i navigated on classes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31560) displayName for slaves
Title: Message Title Kanstantsin Shautsou closed an issue as Won't Do Jenkins / JENKINS-31560 displayName for slaves Change By: Kanstantsin Shautsou Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [copyartifact-plugin] (JENKINS-12918) a job dedicated to copyartifacts from a build specified by a build paramter (ie a run parameter) fails when launched manuallyco
Title: Message Title Anentropic commented on JENKINS-12918 Re: a job dedicated to copyartifacts from a build specified by a build paramter (ie a run parameter) fails when launched manuallyco I've opened a feature request here and will try and get a pull request ready https://issues.jenkins-ci.org/browse/JENKINS-31569 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [packaging] (JENKINS-31348) SuSe Service Will Not Start
Title: Message Title Sam Van Oort resolved as Fixed Fixed by merged PR: https://github.com/jenkinsci/packaging/pull/32 Available in future artifact releases Jenkins / JENKINS-31348 SuSe Service Will Not Start Change By: Sam Van Oort Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [packaging] (JENKINS-31064) JRE/JDK >= 7 requirement on Debian Installer
Title: Message Title Sam Van Oort resolved as Fixed Fixed by merged PRs, available as of next artifact release. The service not reporting failure is fixed by https://github.com/jenkinsci/packaging/pull/32 Jenkins / JENKINS-31064 JRE/JDK >= 7 requirement on Debian Installer Change By: Sam Van Oort Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-31572) Groovy tool installer versions not sorted correctly
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-31572 Groovy tool installer versions not sorted correctly Issue Type: Bug Assignee: Andrew Bayer Components: groovy-plugin Created: 16/Nov/15 3:30 PM Priority: Minor Reporter: Andrew Bayer The Groovy tool JSON (http://mirror.xmission.com/jenkins/updates/current/updates/hudson.plugins.groovy.GroovyInstaller.json, e.g.) doesn't have any natural sorting of its own - it just takes the list from https://dl.bintray.com/groovy/maven/ and spits it out in reverse order. That'd be great if that list itself was usefully sorted, but, well it's alphabetically sorted on filename. Which would be fine if the filenames all started with the same thing, but the pre-Apache ones all start with "groovy-" while the Apache ones start with "apache-groovy-", so 2.4.4 and 2.4.5 end up alphabetically ahead of 1.5.0, etc. We should sort based on the version, regardless of the source page's sorting. Add Comment
[JIRA] [integrity-plugin] (JENKINS-31492) connection problem with PTC
Title: Message Title Hector Magnanao commented on JENKINS-31492 Re: connection problem with PTC Where can I get an old version of Jenkins 1.609.1. What about the PTC plugin ? Should I stay with the latest version or not ? I will bring this up with PTC. Not sure what they need to do on their end though. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [envinject-plugin] (JENKINS-31573) New line characters are not parsing correctly
Title: Message Title John Jones created an issue Jenkins / JENKINS-31573 New line characters are not parsing correctly Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin Created: 16/Nov/15 3:45 PM Priority: Minor Reporter: John Jones If you inject a properties file with new line characters it is not parsing these correctly. Also it appears to be treating the properties file and the properties content differently. To address this issue I submitted a pull request to force parsing as a standard Java properties object and then also extracted the parsing logic to be the same for both the content box and property files. https://github.com/jenkinsci/envinject-plugin/pull/78 Add Comment
[JIRA] [core] (JENKINS-16352) Add ability to specify parameters in the crontab
Title: Message Title Baptiste Mathus edited a comment on JENKINS-16352 Re: Add ability to specify parameters in the crontab Still double-checking, but as I said we have a use-case for it here. So I'm planning to be a maintainer if I fork it. And no problem James, we all have projects and prototypes we didn't finish ;-), that's [hacker] life after all :). Cheers Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-16352) Add ability to specify parameters in the crontab
Title: Message Title Baptiste Mathus commented on JENKINS-16352 Re: Add ability to specify parameters in the crontab Still double-checking, but as I said we have a use-case for it here. So I'm planning to be a maintainer if I fork it. Cheers Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin fails on GitHub user rather than org
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-31574 GitHub branch source plugin fails on GitHub user rather than org Issue Type: Bug Assignee: Manuel Jesús Recena Soto Components: github-branch-source-plugin Created: 16/Nov/15 3:51 PM Priority: Blocker Reporter: Andrew Bayer See https://gist.github.com/abayer/757c08dcd4a41bfbda78 - creds are valid, put my user in for the owner, default repository scan, etc. Add Comment Thi
[JIRA] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin fails on GitHub user rather than org
Title: Message Title Andrew Bayer commented on JENKINS-31574 Re: GitHub branch source plugin fails on GitHub user rather than org Looks to be barfing at https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L130, fwiw. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin fails on GitHub user rather than org
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-31574 GitHub branch source plugin fails on GitHub user rather than org Change By: Andrew Bayer Environment: Jenkins core 1.625.2.0-beta-2, plugin version 1.0. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin fails on GitHub user rather than org
Title: Message Title Jesse Glick commented on JENKINS-31574 Re: GitHub branch source plugin fails on GitHub user rather than org We did not get here so it seems like the username of the credentials does not match the GitHub user name. You are supposed to have a username/password credentials item with username set to the GitHub account name, and password set to an access token. If that is the only problem, this should be downgraded and marked with the diagnosability label to give the user some hint what might be wrong. (Only a hint, since we cannot know whether they meant to type in a user name or an organization name. We might however be able to determine that their credentials do not correspond to an actual user; that could be a form validation warning in the configuration screen.) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin fails on GitHub user rather than org
Title: Message Title Andrew Bayer commented on JENKINS-31574 Re: GitHub branch source plugin fails on GitHub user rather than org Ah, password is an access token, not a password - that's not documented anywhere I could find. Lemme try. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin fails on GitHub user rather than org
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-31574 GitHub branch source plugin fails on GitHub user rather than org Change By: Manuel Jesús Recena Soto Environment: Jenkins core 1.625.2, plugin version 1.0 . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin fails on GitHub user rather than org
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-31574 GitHub branch source plugin fails on GitHub user rather than org Change By: Manuel Jesús Recena Soto Environment: Jenkins core 1.625.2 .0-beta-2 , plugin version 1.0. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin fails on GitHub user rather than org
Title: Message Title
Jesse Glick edited a comment on JENKINS-31574
Re: GitHub branch source plugin fails on GitHub user rather than org
We did not get [here|https://github.com/jenkinsci/github-branch-source-plugin/blob/8aefbc7ff3147616d39800b8f9744d3661b6f2b8/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L128] so it seems like the username of the credentials does not match the GitHub user name. You are supposed to have a username/password credentials item with username set to the GitHub account name, and password set to an access token.If that is the only problem, this should be downgraded and marked with the {{ diagnosability diagnostics }} label to give the user some hint what might be wrong. (Only a hint, since we cannot know whether they meant to type in a user name or an organization name. We might however be able to determine that their credentials do not correspond to an actual user; that could be a form validation warning in the configuration screen.)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin does not document what should be used for creds
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-31574 GitHub branch source plugin does not document what should be used for creds Yup, that did it - rewording JIRA. Change By: Andrew Bayer Summary: GitHub branch source plugin fails on GitHub user rather than org does not document what should be used for creds Priority: Blocker Major See https://gist.github.com/abayer/757c08dcd4a41bfbda78 - creds are valid username/password , put my user in for the owner, default repository scan, etc. When I change to use an access token for the password, it works, but I can't find anywhere where it says to use a username/access token rather than a username/password. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin does not document what should be used for creds
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-31574 GitHub branch source plugin does not document what should be used for creds Change By: Andrew Bayer Labels: diagnostics Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin does not document what should be used for creds
Title: Message Title Jesse Glick commented on JENKINS-31574 Re: GitHub branch source plugin does not document what should be used for creds In the configuration screen we should try to connect to the GH API using the supplied credentials. If that fails, display a form validation error. If it succeeds, check that the username matches an account; if not, display a warning (this is not necessarily fatal since the repoOwner might have been a valid organization, in which case GH is probably not going to care what the username was). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [active-directory-plugin] (JENKINS-31575) Adding SSO/Client certificate authentication against Active Directory
Title: Message Title Louis Lecaroz created an issue Jenkins / JENKINS-31575 Adding SSO/Client certificate authentication against Active Directory Issue Type: Improvement Assignee: Louis Lecaroz Attachments: jenkins_sso.png Components: active-directory-plugin Created: 16/Nov/15 4:08 PM Environment: Tested under Unix & Windows all in 64 bits Labels: SSO Certificate AD ActiveDirectory Plugin Priority: Major Reporter: Louis Lecaroz Today, there are two plugins: the active-directory-plugin & the certificate-authentication-plugin Both are great plugins. But in big infrastructures, administrators need SSO/Client certificate authentication against an Active Directory server. This means, that som
[JIRA] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin does not document what should be used for creds
Title: Message Title Antonio Muñiz edited a comment on JENKINS-31574 Re: GitHub branch source plugin does not document what should be used for creds So, what's [this ]( | https://github.com/jenkinsci/github-branch-source-plugin/blob/8aefbc7ff3147616d39800b8f9744d3661b6f2b8/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L138-L149 ) ] code for?I thought it was to process exactly that case: using a username as repo owner with unrelated credentials (other user). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-31574) GitHub branch source plugin does not document what should be used for creds
Title: Message Title Antonio Muñiz commented on JENKINS-31574 Re: GitHub branch source plugin does not document what should be used for creds So, what's [this](https://github.com/jenkinsci/github-branch-source-plugin/blob/8aefbc7ff3147616d39800b8f9744d3661b6f2b8/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L138-L149) code for? I thought it was to process exactly that case: using a username as repo owner with unrelated credentials (other user). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [active-directory-plugin] (JENKINS-31575) Adding SSO/Client certificate authentication against Active Directory
Title: Message Title Louis Lecaroz updated an issue Jenkins / JENKINS-31575 Adding SSO/Client certificate authentication against Active Directory Change By: Louis Lecaroz Attachment: jenkins_sso.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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.
