[JIRA] [subversion-plugin] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Ralf Mühle
edited a comment on JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
possible workaround:
define global variable (for example: SVN_REPO)
in job use "a text parameter" and set default to global variable, variable name must be different to global variable (for example SVN_REPO2)
in svn url use the variable from "text parameter" (SVN_REPO2)
doesn't work
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [subversion-plugin] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Ralf Mühle
commented on JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
possible workaround:
define global variable (for example: SVN_REPO)
in job use "a text parameter" and set default to global variable, variable name must be different to global variable (for example SVN_REPO2)
in svn url use the variable from "text parameter" (SVN_REPO2)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [subversion-plugin] (JENKINS-27909) SCM poll not working with SubVersion
Vishal Shah created JENKINS-27909 SCM poll not working with SubVersion Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 13/Apr/15 5:38 AM Description: I am new to Jenkin setup. I am using Jenkins ver. 1.608, SubVersion Plugin 1.54. I want to get the updated from SVN periodically. I have two set of Repositories. I have created two jobs one for each repository. In one of the job I set following parameters : true false false false H/5 * * * * H/5 * * * * false false With this it is polling the change in SVN every 5 mins. But if I set the job as below : true false false false H/15 * * * * false false SCM polling is not happening. I want to just check if anything in the SVN change then I want to download the new code. Environment: Jenkins ver. 1.608, SubVersion Plugin 1.54, Browser Crome Project: Jenkins Priority: Minor Reporter: Vishal Shah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [svn-tag-plugin] (JENKINS-3725) Build Parameters in SVN URL confuse svn-tag
Ravi Kumar Alagappan commented on JENKINS-3725 Build Parameters in SVN URL confuse svn-tag Appreciate any fix/work around/update on this issue. I am looking for a fix for this issue for long time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-27908) Startup fails on s390x/Linux - java.lang.UnsatisfiedLinkError: jnidispatch
Mir Sajjad Mehdi created JENKINS-27908 Startup fails on s390x/Linux - java.lang.UnsatisfiedLinkError: jnidispatch Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Apr/15 1:56 AM Description: Starting Jenkins Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at Main._main(Main.java:140) at Main.main(Main.java:98) Caused by: java.lang.UnsatisfiedLinkError: jnidispatch (/com/sun/jna/linux-s390x/libjnidispatch.so) not found in resource path at com.sun.jna.Native.loadNativeLibraryFromJar(Native.java:697) at com.sun.jna.Native.loadNativeLibrary(Native.java:674) at com.sun.jna.Native.(Native.java:115) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) at com.sun.akuma.CLibrary.(CLibrary.java:89) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:126) at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:114) at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104) at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92) at com.sun.akuma.Daemon.daemonize(Daemon.java:106) at com.sun.akuma.Daemon.all(Daemon.java:88) ... 6 more [FAILED] Environment: uname -a Linux XXX 2.6.32-358.el6.s390x #1 SMP Tue Jan 29 12:06:31 EST 2013 s390x s390x s390x GNU/Linux rpm -q jenkins jenkins-1.580.13.1-1.1.noarch java -version java version "1.6.0" Java(TM) SE Runtime Environment (build pxz6460sr9fp2-20110625_01(SR9 FP2)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux s390x-64 jvmxz6460sr9-20110624_85526 (JIT enabled, AOT enabled) J9VM - 20110624_085526 JIT - r9_20101028_17488ifx17 GC - 20101027_AA) JCL - 20110530_01 Project: Jenkins Labels: jenkins core Priority: Blocker Reporter: Mir Sajjad Mehdi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [perforce-plugin] (JENKINS-27877) Parallel sync function in Jenkins Perforce Plugin
Jerry Yu updated JENKINS-27877 Parallel sync function in Jenkins Perforce Plugin Change By: Jerry Yu (13/Apr/15 1:33 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-27905) Use of stage concurrency only allows 1 thread to be blocked at a time
Thomas Dalton edited a comment on JENKINS-27905 Use of stage concurrency only allows 1 thread to be blocked at a time Deleted previous comment because it still doesn't work even with an attempted workaround to add an "exit" stage. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-27905) Use of stage concurrency only allows 1 thread to be blocked at a time
Thomas Dalton
commented on JENKINS-27905
Use of stage concurrency only allows 1 thread to be blocked at a time
Changing the script to following (note the added "exit" stage) seems to fix the problem.
def sleep60 () {
ws {
sh "echo ${env.HOSTNAME}"
stage name: "Sleeping for 60 secs", concurrency: 1
sh "sleep 60"
stage name: "Sleep finished" // exit stage to clear stage concurrency related state
}
}
The error appears to be due to the last stage being the same name as the previous one so effectively we get 2 stages with the same name within the same flow, albeit in parallel closures.
Still not sure whether the reported issue is a real bug, or not. It would be nice not to need to inject stages in this way and for stage related state to be cleared at the end of a closure?
Note also that I had to change the name of the stage because there was a zombie "Sleep for 60 secs" stage still running! The doDelete trick didn't seem to clear it either so that's a secondary (probably more generic?) problem with being able to zap state from failed/hanging jobs.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Daniel Beck commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed Maybe this has a similar cause as JENKINS-27669? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-23442) Jenkins 1.568 can not start when monitoring plugin is installed
evernat commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed Without preventing you to give info, it can be noted that the monitoring plugin currently bundles the slf4j-api: https://github.com/jenkinsci/monitoring-plugin/blob/master/pom.xml#L49 Sl4j-api is in theory not related to java.util.logging, but I can build a specific version without that if you want to make a test. (Or you can remove WEB-INF/lib/slf4j-api-1.6.3.jar by yourself from the monitoring.hpi file with a zip manager and then uninstall / reinstall.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [subversion-plugin] (JENKINS-27898) Change Subversion plugin to allow configuration of different ways to react to working copy locked
Daniel Beck commented on JENKINS-27898 Change Subversion plugin to allow configuration of different ways to react to working copy locked As I wrote in JENKINS-17228: Sharing workspaces between jobs is essentially an anti-pattern. That said, there are several plugins allowing you to limit parallel execution of jobs, e.g. Throttle Concurrent Builds Plugin, which will prevent this issue in your situation. Hence IMO this request does not make any sense, as it does not appear to be a sensible use case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [subversion-plugin] (JENKINS-17228) Fail build when subversion workspace is locked
Daniel Beck commented on JENKINS-17228 Fail build when subversion workspace is locked Tim: Sharing workspaces between jobs is essentially an anti-pattern. That said, there are several plugins allowing you to limit parallel execution of jobs, e.g. Throttle Concurrent Builds Plugin, which will prevent this issue in your situation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [label-linked-jobs-plugin] (JENKINS-27588) Labels used in Label Factory are shown as not used
Dominique Brice
commented on JENKINS-27588
Labels used in Label Factory are shown as not used
I implemented everything discussed in this issue, including the limitation to ignore label parameters containing token/macro (${} syntax). I did not include the display of label's description on the dashboard.
Stefan Kalmelid, a new validation version of the plugin is available there. Let me know how your tests go with this version! Unless there's more bug fixing to do (I tested quite a lot already ), I intend to release this officially as the plugin's next version.
Stefan Kalmelid, Daniel Beck, I opened a new issue to think about reworking the UI/layout of the plugin's three pages. I'll be happy to get your feedback on my suggestions.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [label-linked-jobs-plugin] (JENKINS-27907) UI rework
Dominique Brice updated JENKINS-27907 UI rework Change By: Dominique Brice (12/Apr/15 6:52 PM) Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [label-linked-jobs-plugin] (JENKINS-27907) UI rework
SCM/JIRA link daemon commented on JENKINS-27907 UI rework Code changed in jenkins User: Dominique Path: src/main/resources/jenkins/plugins/linkedjobs/actions/LabelDashboardAction/index.jelly http://jenkins-ci.org/commit/label-linked-jobs-plugin/ebb13e589fec2745bf84c673df6fd45e0bd901c8 Log: Remove label's description from Dashboard for now, to be implemented with JENKINS-27907 Compare: https://github.com/jenkinsci/label-linked-jobs-plugin/compare/0c4dc2b64738...ebb13e589fec This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [label-linked-jobs-plugin] (JENKINS-27907) UI rework
Dominique Brice updated JENKINS-27907 UI rework Change By: Dominique Brice (12/Apr/15 6:50 PM) Description: Improve display of the three pages of the plugin.Some ideas: - label dashboard: instead of a single page with 5 sections, create a tabbed display with one tab per section. Similar to pluginManager section - label dashboard: display label's description - labels & computer page: remove the "Exclusive jobs" section which is redundant with Linked Jobs section, and instead display a warning in the Linked Jobs section for each label that can run on only one node - in all pages, use a two-column display like in the Configure System page to make page more readable - less links on the page? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-27895) Read a property from single value file
Daniel Beck commented on JENKINS-27895 Read a property from single value file I can't change the file to follow a property file format. This does not make any sense. Just have the build script create a file in a different format that can be understood by the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Daniel Beck commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed In your specific case it would be helpful if you mentioned what's different about that one machine from all the other ones. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Daniel Beck commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed Aidan Hobson Sayers Please provide all the information I asked for last year. Can this be reproduced with Jenkins out of the box, only installing this plugin? I can't on CentOS, but maybe you can? If not, would be interesting if anyone experiencing this could provide a full list of plugins installed. (Go to /systemInfo and scroll down.) Is Jenkins running standalone or in a container? Which Java version, OS, Jenkins version, Monitoring plugin, specifically? Does the same issue occur on the same OS, Java version when run standalone on a new Jenkins home directory, with only Monitoring plugin installed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [clearcase-plugin] (JENKINS-27104) Choosing "No History" option in Changeset still brings back history
Vincent Latombe closed JENKINS-27104 as Fixed Choosing "No History" option in Changeset still brings back history Released in 1.6 Change By: Vincent Latombe (12/Apr/15 4:34 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Vincent Latombe closed JENKINS-9703 as Fixed Find changes on a branch not working correctly with CC multisite Released in 1.6 Change By: Vincent Latombe (12/Apr/15 4:33 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [clearcase-plugin] (JENKINS-27733) java.lang.NullPointerException pointer exception using 1.5.4-SNAPSHOT
Vincent Latombe closed JENKINS-27733 as Fixed java.lang.NullPointerException pointer exception using 1.5.4-SNAPSHOT Released in 1.6 Change By: Vincent Latombe (12/Apr/15 4:33 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [clearcase-plugin] (JENKINS-26719) Intermittant exception generated using clearcase plugin & dynamic view when running mkview immediately after the rmview
Vincent Latombe started work on JENKINS-26719 Intermittant exception generated using clearcase plugin & dynamic view when running mkview immediately after the rmview Change By: Vincent Latombe (12/Apr/15 4:33 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [clearcase-plugin] (JENKINS-26719) Intermittant exception generated using clearcase plugin & dynamic view when running mkview immediately after the rmview
Vincent Latombe closed JENKINS-26719 as Fixed Intermittant exception generated using clearcase plugin & dynamic view when running mkview immediately after the rmview Released in 1.6 Change By: Vincent Latombe (12/Apr/15 4:33 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [clearcase-plugin] (JENKINS-26719) Intermittant exception generated using clearcase plugin & dynamic view when running mkview immediately after the rmview
Vincent Latombe resolved JENKINS-26719 as Fixed Intermittant exception generated using clearcase plugin & dynamic view when running mkview immediately after the rmview Change By: Vincent Latombe (12/Apr/15 4:33 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [clearcase-plugin] (JENKINS-27104) Choosing "No History" option in Changeset still brings back history
Vincent Latombe resolved JENKINS-27104 as Fixed Choosing "No History" option in Changeset still brings back history Change By: Vincent Latombe (12/Apr/15 4:34 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [clearcase-plugin] (JENKINS-27733) java.lang.NullPointerException pointer exception using 1.5.4-SNAPSHOT
Vincent Latombe resolved JENKINS-27733 as Fixed java.lang.NullPointerException pointer exception using 1.5.4-SNAPSHOT Change By: Vincent Latombe (12/Apr/15 4:33 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [label-linked-jobs-plugin] (JENKINS-27588) Labels used in Label Factory are shown as not used
SCM/JIRA link daemon commented on JENKINS-27588 Labels used in Label Factory are shown as not used Code changed in jenkins User: Dominique Path: src/main/java/jenkins/plugins/linkedjobs/actions/ComputerLinkedJobsAction.java src/main/java/jenkins/plugins/linkedjobs/actions/LabelLinkedJobsAction.java src/main/java/jenkins/plugins/linkedjobs/model/JobsGroup.java src/main/resources/jenkins/plugins/linkedjobs/actions/ComputerLinkedJobsAction/index.jelly src/main/resources/jenkins/plugins/linkedjobs/actions/LabelLinkedJobsAction/index.jelly http://jenkins-ci.org/commit/label-linked-jobs-plugin/0c4dc2b647385ad36d59758eecf1af0c689e2527 Log: JENKINS-27588 Adding support for jobs with Label parameter's default value on Label and Node pages This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [label-linked-jobs-plugin] (JENKINS-27907) UI rework
Dominique Brice created JENKINS-27907 UI rework Issue Type: Improvement Assignee: Dominique Brice Components: label-linked-jobs-plugin Created: 12/Apr/15 3:19 PM Description: Improve display of the three pages of the plugin. Some ideas: label dashboard: instead of a single page with 5 sections, create a tabbed display with one tab per section. Similar to pluginManager section labels & computer page: remove the "Exclusive jobs" section which is redundant with Linked Jobs section, and instead display a warning in the Linked Jobs section for each label that can run on only one node in all pages, use a two-column display like in the Configure System page to make page more readable less links on the page? Project: Jenkins Priority: Critical Reporter: Dominique Brice This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-27842) Support webhook events from github
Pedro Algarvio commented on JENKINS-27842 Support webhook events from github 1) We used job-dsl for each of the seed jobs. 2) I only mentioned exposing the payload because others could have some use for it I would write my own plugin if I was a java developer. I'm not, or I'd have this issue solved already. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-24958) UsernameNotFoundException when ActiveDirectory used for API and token authentication
Daniel Beck commented on JENKINS-24958 UsernameNotFoundException when ActiveDirectory used for API and token authentication Not sure what you mean by this question. I thought there was not configuration for this machine, since it is joined to a domain. To clarify, Active Directory Plugin. It has options in the security preferences. Both instances of what? The report mentions two Jenkins instances (at least that's my guess from the report mentioning two vastly different Jenkins versions). Does not apply to you. How do I do that for this process? Not sure what you mean. Just go to http://whateveryourjenkinshostnameis/whoAmI when logged in. Can you tell me how to do that? https://wiki.jenkins-ci.org/display/JENKINS/Logging One question I forgot: Does the user account you want to use actually exist in Active Directory, or only in Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-27842) Support webhook events from github
Kanstantsin Shautsou commented on JENKINS-27842 Support webhook events from github 1) job per branch is a git plugin/jenkins core issue - feel free to propose good design for handling them and then back to github-plugin. Note, this topic was discussed many times and it is known that build configuration may differ per branches, that's why everybody propose to use "job-dsl?" and store configuration in git. 2) Exposing payload data is the way to not using jenkins/plugin features at all just for your case. Just wrote plugin that will resolve your problem and use it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-27842) Support webhook events from github
Pedro Algarvio commented on JENKINS-27842 Support webhook events from github I know that there's the pull requests plugin, we use it, but history has proven(to us) that having a single job handling all pull requests is not optimal. We have no unit test history for one, ie, we can't know if the PR has fixed or added additional failures with new commits unless we search which builds belong to which pull request. Our current approach is to create a set of jobs per pull request, which will be managed by the pull requests plugin afterwards. What we need is to know when a pull request is opened/closed, so we can trigger our pull request seed job. We are currently using url triggers which even trigger for GitHub ping events(also not optimal). The same applies for branches creation/deletion, we want to be able to trigger a seed job to create/delete a set of jobs which will handle the branch. As for the push notifications, we can't let the github-plugin auto manage hooks because we have a testing/staging/production jenkins setup and only one instance can be notified of pushes with the current plugin implementation. So, ideally, we're after a push event notification which registers itself using webhooks, as opposed to the jenkins github hook app. It should do the awesome job that this plugin does for push notification, but using web hooks. As for the other web-hook events, the plugin could just trigger the job and inject the payload into the build environment(we actually don't currently need the payload, but if it's going to be done, it should be done with a future mindset). I tried hacking my way into the github-plugin to at least implement the events that I currently need as separate triggers, registering them using webhooks, but I'm not a java developer and I've lost a fair amount of time already and I didn't get it to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-24291) GitHub plugin to make parameters from webhook data
Kanstantsin Shautsou commented on JENKINS-24291 GitHub plugin to make parameters from webhook data This looks like an known issue with branch specifying https://github.com/jenkinsci/github-plugin/pull/44 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-plugin] (JENKINS-24408) docker plugin throwing NumberFormatException when trying to connect to docker from jenkins
Kanstantsin Shautsou commented on JENKINS-24408 docker plugin throwing NumberFormatException when trying to connect to docker from jenkins Please try beta release from experimental center and reopen if issue will still persist. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-plugin] (JENKINS-24408) docker plugin throwing NumberFormatException when trying to connect to docker from jenkins
Kanstantsin Shautsou resolved JENKINS-24408 as Fixed docker plugin throwing NumberFormatException when trying to connect to docker from jenkins Change By: Kanstantsin Shautsou (12/Apr/15 11:48 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-24958) UsernameNotFoundException when ActiveDirectory used for API and token authentication
Keith Davis commented on JENKINS-24958 UsernameNotFoundException when ActiveDirectory used for API and token authentication I just realized that the submitter was Jenkins Python API. I'm using a PHP and cURL. Seems like the same issue though. Basic same setup as Felix. "http://jenkinserver/job/myjob/config.xml"); curl_setopt($curl, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); curl_setopt($curl, CURLOPT_USERPWD, "username:apiToken"); curl_setopt($curl, CURLOPT_RETURNTRANSFER, true); $sOutput = curl_exec($curl); echo $sOutput ?: curl_error($curl); curl_close($curl); ?> How is Active Directory configured? Not sure what you mean by this question. I thought there was not configuration for this machine, since it is joined to a domain. What version of the plugin are you using? 1.39 (Are both instances using the same plugin version? What happens when you configure the older Jenkins version to use Active Directory?) Both instances of what? In the affected instance, are you able to use the CLI (with authentication)? Don't know how to do this. The XML/JSON API (using e.g. curl)? Yes - Change the URL to http://jenkinserver/job/myjob/api/json, same effect. The Web UI? Not sure how to do this correctly, but tried with Chrome and got redirected to the Login page. What is shown on the /whoAmI web page? How do I do that for this process? Configure a log recorder with logger hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider on level FINE. What gets logged around the time the error occurs? Can you tell me how to do that? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-plugin] (JENKINS-23301) Support unix protocol for connection
SCM/JIRA link daemon commented on JENKINS-23301 Support unix protocol for connection Code changed in jenkins User: Kanstantsin Shautsou Path: docker-plugin/src/main/resources/com/nirima/jenkins/plugins/docker/DockerCloud/help-serverUrl.html http://jenkins-ci.org/commit/docker-plugin/a921ba9c93103f61052588ca9798059063c3e050 Log: Merge pull request #203 from KostyaSha/upstream-master JENKINS-23301 Describe supported protocols in help Compare: https://github.com/jenkinsci/docker-plugin/compare/824c92a8ade0...a921ba9c9310 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-plugin] (JENKINS-23301) Support unix protocol for connection
SCM/JIRA link daemon commented on JENKINS-23301 Support unix protocol for connection Code changed in jenkins User: Kanstantsin Shautsou Path: docker-plugin/src/main/resources/com/nirima/jenkins/plugins/docker/DockerCloud/help-serverUrl.html http://jenkins-ci.org/commit/docker-plugin/7e4ec43ac823e1f7c3a3b780b93e51eb9b4be4ca Log: JENKINS-23301 Describe supported protocols in help TODO of course support more protocols. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-plugin] (JENKINS-23301) Support unix protocol for connection
Kanstantsin Shautsou updated JENKINS-23301 Support unix protocol for connection Change By: Kanstantsin Shautsou (12/Apr/15 11:32 AM) Summary: Cannot connect to Docker using Support unix protocol for connection Issue Type: Bug Improvement Priority: Blocker Major Assignee: Kanstantsin Shautsou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [docker-plugin] (JENKINS-23301) Cannot connect to Docker using unix protocol
Kanstantsin Shautsou commented on JENKINS-23301 Cannot connect to Docker using unix protocol Jesse, have you read wiki page https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin? All documentation suggests http for usage. I'm changing priority because plugin has more critical issues for usage. Will also add help note. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-4409) Hudson test case leaks temp folders
SCM/JIRA link daemon commented on JENKINS-4409 Hudson test case leaks temp folders Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/build.gradle http://jenkins-ci.org/commit/job-dsl-plugin/bee907f1b74fee7718d010d352cc051308317893 Log: added workaround for JENKINS-4409 to avoid leaking files into the system temp directory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-27842) Support webhook events from github
Kanstantsin Shautsou commented on JENKINS-27842 Support webhook events from github Pull request functionality exist in separate plugin -> "ghprb-plugin" and handle hooks separately. Not all people have ability to expose jenkins url to public network, so such functionality should also work with polling. Hooks payload and direct api calls has different contents and logic. Current hook triggering in github-plugin is pretty simple - it uses git branches matching and any other options will add overhead. Your request is still valid, but IMO pullrequest functionality should be merged in one plugin - github-plugin. This can exclude code duplication. For now i can suggest to use existed functionality and adopt your workflow for it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-pipeline-plugin] (JENKINS-21188) Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access for not-logged in users
Kanstantsin Shautsou commented on JENKINS-21188 Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access for not-logged in users Hi, your stacktrace doesn't contain a NPE. This may be a separate issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-27886) Git can't fetch from origin error
Kanstantsin Shautsou updated JENKINS-27886 Git can't fetch from origin error Change By: Kanstantsin Shautsou (12/Apr/15 11:12 AM) Summary: Unable to run scripts on Jenkins slave Git can't fetch from GitHub origin error Component/s: git-plugin Component/s: github-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-plugin] (JENKINS-27886) Unable to run scripts on Jenkins slave from GitHub
Kanstantsin Shautsou commented on JENKINS-27886 Unable to run scripts on Jenkins slave from GitHub Should be not a github-plugin issue, right error logging in git-plugin suppressed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [findbugs-plugin] (JENKINS-24743) Findbug and PMD are broken in Jenkins 1.565.2
Kanstantsin Shautsou commented on JENKINS-24743 Findbug and PMD are broken in Jenkins 1.565.2 Jar may exist but will be not used. Please check that you have no plugins that do classloading before core classloading. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-16365) allPermissions should try to load Jenkins's list of permissions
SCM/JIRA link daemon commented on JENKINS-16365 allPermissions should try to load Jenkins's list of permissions Code changed in jenkins User: Daniel Spilker Path: config/codenarc/rules.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/AbstractJobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/FileJobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/JobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/MemoryJobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/MockJobManagement.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/AbstractJobManagementSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/MockJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/247ce6b783381225ce174f8b32627f79481a7b7b Log: Merge pull request #447 from CoreMedia/mock-job-management JENKINS-16365 Added pre-set permissions Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/ff3fe16db4dd...247ce6b78338 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-16365) allPermissions should try to load Jenkins's list of permissions
SCM/JIRA link daemon commented on JENKINS-16365 allPermissions should try to load Jenkins's list of permissions Code changed in jenkins User: Daniel Spilker Path: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/MockJobManagement.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/MockJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/189d537f447f783070844dedfdda9b19287e37df Log: added pre-set permissions to FileJobManagement and MemoryJobManagement, follow-up of JENKINS-16365 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [analysis-collector-plugin] (JENKINS-27890) FindBugs report does not correctly indicate New/Fixed warnings
Ulli Hafner commented on JENKINS-27890 FindBugs report does not correctly indicate New/Fixed warnings I only find the workspace (Jenkins_HOME/jobs/your-job/workspace) but not the build folder (Jenkins_HOME/jobs/your-job/builds/your-build-number). In the latter one there are the files that the Jenkins plugin is writing. But anyway, I can try to analyze your files from the zip in order to find the created hash codes... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [nunit-plugin] (JENKINS-27906) Fail to read NUnit3 output xml
apgray updated JENKINS-27906 Fail to read NUnit3 output xml Change By: apgray (12/Apr/15 8:31 AM) Attachment: nunit-selenium-testsuite.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [nunit-plugin] (JENKINS-27906) Fail to read NUnit3 output xml
Bruno P. Kinoshita commented on JENKINS-27906 Fail to read NUnit3 output xml Can you attach the temp-junit.xml XML file as well, please? What it looks like, is that something changed in the way NUnit produces XML's, and the plug-in needs some adjustments in order to correctly parse it. Thanks. Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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-24958) UsernameNotFoundException when ActiveDirectory used for API and token authentication
Daniel Beck commented on JENKINS-24958 UsernameNotFoundException when ActiveDirectory used for API and token authentication See first comment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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.
