[JIRA] [core] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Joël Royer edited a comment on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated Issue is still present in 1.549!!! I have a nested view, with one sub-view (type list view). Admin users can see nested view and its sub-view, and all jobs associated with it. Regulars users (with only Global Read permission), can't see the nested view. But they can see jobs in the tab "All". The only way I found is to assign View Read Permission to regulars users. But they can see all views, even those without 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/groups/opt_out.
[JIRA] [windows-slaves] (JENKINS-21542) Cannot launch Windows libvirt slaves due to missing method on SmbFileInputStream
Johan Cronje created JENKINS-21542 Cannot launch Windows libvirt slaves due to missing method on SmbFileInputStream Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: windows-slaves Created: 29/Jan/14 8:38 AM Description: When we upgraded from 1.545 to 1.549, we found that we could no longer launch our Windows slaves using the 'DCOM' method. Unfortunately we cannot use JNLP because these are libvirt slaves, and choosing JNLP causes the instances to not even start up (due to issues like JENKINS-8004). What is happening is this: libvirt starts the slave Jenkins logs in to the slave It then tries to query the Java version ... and it all goes pear-shaped from here. The stack trace is: Error while launching instance on Hypervisor qemu+ssh://root@node2:22/system?no_verify=1no_tty=1. java.lang.NoSuchMethodError: jcifs.smb.SmbFileInputStream.setTimeout(J)V at org.jvnet.hudson.remcom.WindowsRemoteProcessLauncher.openForRead(WindowsRemoteProcessLauncher.java:282) at org.jvnet.hudson.remcom.WindowsRemoteProcessLauncher.launch(WindowsRemoteProcessLauncher.java:140) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:233) at hudson.plugins.libvirt.VirtualMachineLauncher.launch(VirtualMachineLauncher.java:136) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) So it seems as though the jcifs used is maybe the wrong version (I see that it was patched some time in 2011 to include the 'setTimeout' function). Maybe it was reverted/removed? What could be the cause of this? Project: Jenkins Priority: Critical Reporter: Johan Cronje 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/groups/opt_out.
[JIRA] [core] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Klaus Azesberger edited a comment on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated I'm not sure yet, but we recently discovered that the folder plugin (there is also a non-enterprise one) could maybe become handy in these cases instead of using the nested view plugin. hth 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/groups/opt_out.
[JIRA] [core] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Klaus Azesberger commented on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated I'm not sure yet, but we recently discovered that the folder plugin (there is also a non-enterprise one) could maybe come handy in these cases instead of using the nested view plugin. hth 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/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-21494) Credentials are not injected in the settings via the environment variable
Olivier Billard commented on JENKINS-21494 Credentials are not injected in the settings via the environment variable I provided a pull request for this fix. 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/groups/opt_out.
[JIRA] [clearcase] (JENKINS-21100) Parametrize config spec configuration
Tomasz Ptak
closed JENKINS-21100 as Not A Defect
Parametrize config spec configuration
Hi Waldek,
Actually, you can use parameters in form ${PARAM} - Vincent explained it to me, it's just not documented.
Change By:
Tomasz Ptak
(29/Jan/14 9:30 AM)
Status:
Open
Closed
Resolution:
NotADefect
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/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-21543) Likely stuck timed out the build after 0 minutes
Ed Randall created JENKINS-21543 Likely stuck timed out the build after 0 minutes Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: build-timeout Created: 29/Jan/14 10:08 AM Description: The job was set to: Abort the build if it's stuck Likely stuck 09:49:36 Started by user anonymous 09:49:36 EnvInject - Loading node environment variables. 09:49:36 Building remotely on slave-02 in workspace /home/jenkins/jenkins-slave/workspace/static_data_client_functions.checkin 09:49:36 Checking out a fresh workspace because there's no workspace at /home/jenkins/jenkins-slave/workspace/static_data_client_functions.checkin 09:49:36 Cleaning local Directory . 09:49:36 Checking out svn://host.../path/.../trunk at revision '2014-01-29T09:49:36.068 +' 09:49:37 A src 09:49:37 A src/test 09:49:37 A src/test/java ... etc ... 09:49:38 A src/main/resources 09:49:38 A pom.xml 09:49:38 U. 09:49:38 At revision 984 09:49:38 no revision recorded for svn://host.../path.../trunk in the previous build 09:49:38 static_data_client_functions.checkin $ /home/jenkins/tools/maven/bin/mvn clean install --update-snapshots --batch-mode 09:49:40 Build timed out (after 0 minutes). Marking the build as aborted. 09:49:40 Build was aborted 09:49:40 Build Aborted. Not looking for any TestNG results. 09:49:40 Finished: ABORTED Environment: Centos 6.5 Linux jenkins-master 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux JDK 1.7.0_51 Jenkins 1.532.1 build timeout plugin 1.12.2 Jenkins master/slave configuration (all builds take place on slaves) Project: Jenkins Priority: Major Reporter: Ed Randall 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-21544) Copy Artifact Plugin: support fallback to unstable builds when using Upstream build that triggered this job
Michael Prokop created JENKINS-21544 Copy Artifact Plugin: support fallback to unstable builds when using Upstream build that triggered this job Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: copyartifact Created: 29/Jan/14 10:11 AM Description: The 'Upstream build that triggered this job' option provides a feature named 'Use "Last successful build" as fallback'. It would be great if there would be also something like 'Use "Last successful or unstable build" as fallback'. This would be handy e.g. if you have a long running job A which is unstable and the artifacts of job A are re-used in another job B. But this job B is WIP and needs to be re-triggered multiple times (manually) and you don't want to re-run job A until you get a "successful build" but instead just fall back to the latest stable or unstable build. Thanks for the Copy Artifact Plugin! Project: Jenkins Priority: Major Reporter: Michael Prokop 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/groups/opt_out.
[JIRA] [cucumber-testresult] (JENKINS-21545) Skipped steps don't mark test as failure
The Mole created JENKINS-21545 Skipped steps dont mark test as failure Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: sampleOutput.json, StackTrace.txt Components: cucumber-testresult Created: 29/Jan/14 10:35 AM Description: A scenario is marked as passed even if there are steps that have been marked as skipped. In particulary if a StepDef annotated as @Before throws an assertion error this produces a JSON report where all the steps are skipped, however this is treated as a successful test by the reporting. Attached: Sample json output file. Sample Stack trace of a @Before stepDef throwing an assertion error. Project: Jenkins Priority: Major Reporter: The Mole 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/groups/opt_out.
[JIRA] [testswarm] (JENKINS-21546) ThinBackup throws error in Jenkins Plugin Manager
Horia Constantin created JENKINS-21546 ThinBackup throws error in Jenkins Plugin Manager Issue Type: Bug Assignee: kevin_nilson Components: testswarm, thinBackup Created: 29/Jan/14 10:35 AM Description: With this configuration, when going to Jenkins Plugin Manager, when looking at the ThinBackup plugin, in the uninstall section, I'm getting the same error as in tickets https://issues.jenkins-ci.org/browse/JENKINS-18488 https://issues.jenkins-ci.org/browse/JENKINS-20194 However, I don't have the option of removing the testswarm plugin. Environment: Jenkins ver. 1.546 ThinBackup 1.7.4 jenkins-testswarm-plugin 1.2 Project: Jenkins Labels: plugin Priority: Major Reporter: Horia Constantin 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/groups/opt_out.
[JIRA] [grails] (JENKINS-19643) [Executor exception] java.lang.VerifyError: Incompatible argument to function
Ulli Hafner resolved JENKINS-19643 as Fixed [Executor exception] java.lang.VerifyError: Incompatible argument to function Change By: Ulli Hafner (29/Jan/14 10:48 AM) Status: Reopened 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/groups/opt_out.
[JIRA] [grails] (JENKINS-19643) [Executor exception] java.lang.VerifyError: Incompatible argument to function
Ulli Hafner commented on JENKINS-19643 [Executor exception] java.lang.VerifyError: Incompatible argument to function Ok, I released a new version with commons codec 1.8. 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/groups/opt_out.
[JIRA] [core] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Harry G. commented on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated True, we also use Folders Plugin. It avoids this bug, but introduces a different concept - with some other advantages, but lots of changes. 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/groups/opt_out.
[JIRA] [mantis] (JENKINS-16840) Unable to connect to Mantis
Dmitry Zanozin commented on JENKINS-16840 Unable to connect to Mantis The similar problem for me. I'm trying to use server named "mantis" in local network. Can't retrieve projects and categories. log contains: ... Jan 29, 2014 3:15:08 PM hudson.plugins.mantis.soap.mantis120.MantisSessionImpl init INFO: Mantis version is 1.2.X Jan 29, 2014 3:15:09 PM hudson.plugins.mantis.MantisSite isConnect WARNING: Failed to connect http://mantis/ (cause: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.). ... Mantis 1.2.11 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/groups/opt_out.
[JIRA] [envinject] (JENKINS-15507) Environment variables are not injected in parent matrix job
S Stack updated JENKINS-15507 Environment variables are not injected in parent matrix job Change By: S Stack (29/Jan/14 11:58 AM) Affects Version/s: current 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/groups/opt_out.
[JIRA] [cucumber-testresult] (JENKINS-21545) Skipped steps don't mark test as failure
teilo commented on JENKINS-21545 Skipped steps dont mark test as failure This is a bug in an old version of cucumber-jvm. with cucumber-jvm 1.1.5 I see before/after hooks recorded correctly in the json output 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/groups/opt_out.
[JIRA] [cli] (JENKINS-20128) HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
S Stack reopened JENKINS-20128 HTTP two-way remoting does not work (jenkins-cli.jar without JNLP) Solaris 10 CLI times out for any command beginning at 1.535 Last working version for CLI was Jenkins 1.534 Please see https://issues.jenkins-ci.org/browse/JENKINS-18366?focusedCommentId=193633page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-193633 Change By: S Stack (29/Jan/14 12:17 PM) Resolution: Fixed Status: Resolved Reopened 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/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-21489) URL decoding for test objects fails with special characters
jpiironen closed JENKINS-21489 as Fixed URL decoding for test objects fails with special characters Change By: jpiironen (29/Jan/14 12:23 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/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-21489) URL decoding for test objects fails with special characters
jpiironen resolved JENKINS-21489 as Fixed URL decoding for test objects fails with special characters Fixed in 1.4.1 by changing URL encoding to Jenkins's own rawEncoding() method Change By: jpiironen (29/Jan/14 12:23 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/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-21490) Split token-macro tokens further to enable more custom reporting
jpiironen closed JENKINS-21490 as Fixed Split token-macro tokens further to enable more custom reporting Change By: jpiironen (29/Jan/14 12:25 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/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-21490) Split token-macro tokens further to enable more custom reporting
jpiironen resolved JENKINS-21490 as Fixed Split token-macro tokens further to enable more custom reporting Added individual ROBOT_PASS, ROBOT_FAIL and ROBOT_TOTAL macros in 1.4.1 for showing passed, failed and total tests respectively. Change By: jpiironen (29/Jan/14 12:25 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21510) Plugin result icons on build page are broken
SCM/JIRA link daemon commented on JENKINS-21510 Plugin result icons on build page are broken Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/BuildResult.java http://jenkins-ci.org/commit/analysis-core-plugin/0526edc60d0740959cf15799169833c8deef33e2 Log: FIXED JENKINS-21510 Use context path for ball images. 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21510) Plugin result icons on build page are broken
SCM/JIRA link daemon resolved JENKINS-21510 as Fixed Plugin result icons on build page are broken Change By: SCM/JIRA link daemon (29/Jan/14 12:31 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-9150) Matrix (multi-configuraton) jobs don't work with the SVN emulate clean workspace checkout strategy
Philip Bergqvist commented on JENKINS-9150 Matrix (multi-configuraton) jobs dont work with the SVN emulate clean workspace checkout strategy I am also experiencing this issue. With a multi-configuration job the configuration workspaces are always deleted when using emulate clean. 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21512) Cli for ContextHashCode
Ulli Hafner commented on JENKINS-21512 Cli for ContextHashCode I don't understand your use case and requirements. Doesn't Jenkins build only project files that have been committed? What is static-checker-manager? The context hash codes are computed on the fly if the static analysis tool does not provide them. Can you please elaborate? 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21416) Findbugs new warnings based on last successful build when findbugs plugin is cause of unstable builds
Ulli Hafner updated JENKINS-21416 Findbugs new warnings based on last successful build when findbugs plugin is cause of unstable builds Change By: Ulli Hafner (29/Jan/14 12:57 PM) Issue Type: Bug NewFeature Priority: Major Minor 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/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-8381) Robot summary and trend graph for multi-configuration project
Benjamin Zaiser commented on JENKINS-8381 Robot summary and trend graph for multi-configuration project @jpiironen: please can you add some documentation on how to configure the plugin in a multi-configuration project. My current setup is a testautomation project with a pom.xml which has 2 submodules which contain robotframework testcases. Currently the Jenkins RF plugin is configured with **/output.xml, **/report.html, etc. Where can I see the aggregated results? 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/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
Jakub Czaplicki created JENKINS-21547 Add information to console log when a job is aborted by gerrit Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger Created: 29/Jan/14 1:00 PM Description: When a new patch set is submitted/rebased to an existing gerrit, the job triggered by the previous patch set is aborted (according to our observations). It would be very helpful to know (as in see in the console) that a job has been aborted by gerrit. Currently the console log shows: 13:35:00 Build was aborted 13:35:00 Archiving artifacts Project: Jenkins Labels: plugin Priority: Major Reporter: Jakub Czaplicki 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21416) Findbugs new warnings based on last successful build when findbugs plugin is cause of unstable builds
Ulli Hafner commented on JENKINS-21416 Findbugs new warnings based on last successful build when findbugs plugin is cause of unstable builds The reference build is the last build (overall SUCCESS or UNSTABLE) with plug-in result SUCCESS. It is not possible to use an unstable plug-in result as a reference yet. 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21416) Findbugs new warnings based on last successful build when findbugs plugin is cause of unstable builds
Ulli Hafner resolved JENKINS-21416 as Duplicate Findbugs new warnings based on last successful build when findbugs plugin is cause of unstable builds Change By: Ulli Hafner (29/Jan/14 1:01 PM) Status: Open Resolved Resolution: Duplicate 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/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-14675) Schema 'DBUSER' does not exist error in integrity plugin
Gregory Pierre commented on JENKINS-14675 Schema DBUSER does not exist error in integrity plugin I worked around the problem by rebuilding every single job twice which is cumbersome. I would be great to avoid similar problems for future upgrades. 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/groups/opt_out.
[JIRA] [git] (JENKINS-19043) jgit hangs on Updating references with large repositories
Mark Waite commented on JENKINS-19043 jgit hangs on Updating references with large repositories JGit 3.2.0 resolves this issue, at least with my 2.5 GB repository. JGit 3.2.0 is proposed to be included in the release of git client plugin after 1.6.1 and the release of git plugin after 2.0.1 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/groups/opt_out.
[JIRA] [git] (JENKINS-20286) JGit incorrectly reports changes detected when polling
Mark Waite commented on JENKINS-20286 JGit incorrectly reports changes detected when polling Another work around that may help for some is to define the "Branches to build" explicitly as a single branch name in the terms of the remote (for example, "master" rather than "*/master" or "origin/master"). It appears that the JGit implementation of the ls-remote command does not perform the same matching of wildcards as the CliGit implementation 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
SCM/JIRA link daemon commented on JENKINS-20692 Optionally show action in CHANGES token Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/content/ChangesSinceLastBuildContent.java src/test/java/hudson/plugins/emailext/plugins/content/ChangesSinceLastBuildContentTest.java http://jenkins-ci.org/commit/email-ext-plugin/6d57206bb4b541a6504d77b08ad7fcabcfe59790 Log: Fix JENKINS-20692 Added %a and %d to the pathFormat formatting options. %a will display the getName of the EditType %d will display the getDescription of the EditType If getAffectedFiles is not implemented by the SCM, then "Unknown" will be put displayed for each %a anf %d 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17655) Multijob plugin does not support Folder plugin
Ireneusz Makowski commented on JENKINS-17655 Multijob plugin does not support Folder plugin Did you released it in 1.11? 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17655) Multijob plugin does not support Folder plugin
hagzag commented on JENKINS-17655 Multijob plugin does not support Folder plugin Unfortunately no, I didn't get final feedback regarding the Folder plugin version. I have no problem releasing another in a couple of weeks of this PR fixes that - could you validate that and let me know ? Thanks HP 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17655) Multijob plugin does not support Folder plugin
Ireneusz Makowski commented on JENKINS-17655 Multijob plugin does not support Folder plugin Is this possible to release it earlier? I can validate this, but i don't have Java experience and don't have environment to build this plugin. Do you have any try branch with result of merge of it? I can validate hpi against my environment. 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/groups/opt_out.
[JIRA] [rtc] (JENKINS-21477) Enable multiple Jazz servers per project
Heather Fraser-Dube commented on JENKINS-21477 Enable multiple Jazz servers per project Thanks for the details. I've raised an enhancement request for this so that it is tracked in both places. 300164: Enable multiple Jazz servers per project 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Heather Fraser-Dube commented on JENKINS-21483 java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. I found defects for this in jazz.net 213302: Error in the log every time I start the client (Sun 1.7 VM) and 234968: SCM Daemon prints stacktrace always which was marked as a duplicate of the previous one. It has been fixed in the 4.0.2 release of RTC (CLM). So I am going to resolve this. If you are running with a more recent version of the toolkit, please re-open. 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/groups/opt_out.
[JIRA] [core] (JENKINS-11872) UnsatisfiedLinkError when installing as Windows service
David Arndt commented on JENKINS-11872 UnsatisfiedLinkError when installing as Windows service I've encountered the same bug. Running on Windows 7 (SP1) This should re-prioritized, also. It is not "minor" - it's a feature show stopper/blocker 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Heather Fraser-Dube resolved JENKINS-21483 as Fixed java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. This is a problem with the Build toolkit provided by the RTC product. The defect has been fixed in a later release of RTC. Change By: Heather Fraser-Dube (29/Jan/14 3:10 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/groups/opt_out.
[JIRA] [git] (JENKINS-20286) JGit incorrectly reports changes detected when polling
Mark Waite commented on JENKINS-20286 JGit incorrectly reports changes detected when polling A test has been submitted to my fork of the git-client-plugin repository which shows that the getHeadRev behavior is different between JGit and CliGit implementations when a wildcard is included in either the repository name or the branch name. No fix yet, just a test that confirms the difference in behavior. 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-21548) Xvfb failure does not fail build
Richard Cross created JENKINS-21548 Xvfb failure does not fail build Issue Type: Improvement Affects Versions: current Assignee: zregvart Components: xvfb Created: 29/Jan/14 3:00 PM Description: When using the Xvfb plugin, if the plugin fails to establish a connection, then the build should fail, as any tests that depend on an Xvfb display are bound to fail also. Or, at least there should be an option in the advance settings to fail the job if Xvfb fails. Currently, the plugin simply logs an error, and then proceeds with the rest of the build job. 12:28:14 Xvfb starting$ /usr/bin/Xvfb :1958 -screen 0 1024x768x24 -fbdir /buildstore/jenkins_0c9_slave/2014-01-29_12-28-139011048368266724308xvfb 12:28:14 _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed 12:28:14 _XSERVTransMakeAllCOTSServerListeners: server already running 12:28:14 12:28:14 Fatal server error: 12:28:14 Cannot establish any listening sockets - Make sure an X server isn't already running 12:28:14 unlink: No such file or directory 12:28:14 unlink failed, Invalid argument 12:28:14 ERROR: Xvfb failed to start, consult the lines above for errors 12:28:29 [8mha:WB+LCABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA= [0mCopied 1 artifact from " [8mha:sB+LCABb85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMjQLmEw0M/KT9L3TSwuSS2KL0lNzDUwjHcsLcnPTSxJTYl3K81LLsnMz0vMiQ9JLS4B2qAPABqeEK21AAA rest of build job proceeds, and inevitably fails Environment: RHEL 6.2 Project: Jenkins Labels: xvfb Priority: Major Reporter: Richard Cross 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/groups/opt_out.
[JIRA] [git] (JENKINS-20286) JGit incorrectly reports changes detected when polling
Mark Waite started work on JENKINS-20286 JGit incorrectly reports changes detected when polling Change By: Mark Waite (29/Jan/14 3:20 PM) Status: Open InProgress 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21537) Option to use Global User and Password when RTC url is overidden
Heather Fraser-Dube commented on JENKINS-21537 Option to use Global User and Password when RTC url is overidden Sounds reasonable. I've raised 300177: Option to use Global User and Password when RTC url is overridden in RTC to track this. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21550) cron trigger parsing is unfriendly (misleading error + stack trace)
Ed Randall
created JENKINS-21550
cron trigger parsing is unfriendly (misleading error + stack trace)
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
29/Jan/14 3:29 PM
Description:
I entered a simple cron _expression_ accidentally adding an extra field:
H 0 * * * *
The error message was very misleading:
Invalid input: "H 0 * * * *": line 1:10: expecting EOF, found ' '
Hitting "Save" anyway gave:
Caused by: java.lang.IllegalArgumentException: Failed to instantiate class hudson.triggers.SCMTrigger from {"scmpoll_spec":"H 0 * * * *\n","ignorePostCommitHooks":false}
at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:597)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:392)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:388)
at hudson.model.Descriptor.newInstance(Descriptor.java:567)
... 88 more
Caused by: java.lang.IllegalArgumentException: antlr.ANTLRException: Invalid input: "H 0 * * * *": line 1:10: expecting EOF, found ' '
at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:454)
at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:77)
at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:595)
... 91 more
Caused by: antlr.ANTLRException: Invalid input: "H 0 * * * *": line 1:10: expecting EOF, found ' '
at hudson.scheduler.CronTabList.create(CronTabList.java:87)
at hudson.scheduler.CronTabList.create(CronTabList.java:73)
at hudson.triggers.Trigger.init(Trigger.java:161)
at hudson.triggers.SCMTrigger.init(SCMTrigger.java:85)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:439)
... 93 more
Caused by: line 1:10: expecting EOF, found ' '
at antlr.Parser.match(Parser.java:211)
at hudson.scheduler.CrontabParser.startRule(CrontabParser.java:67)
at hudson.scheduler.CronTab.set(CronTab.java:93)
at hudson.scheduler.CronTab.init(CronTab.java:83)
at hudson.scheduler.CronTabList.create(CronTabList.java:85)
... 101 more
Environment:
Jenkins LTS 1.532.1
Linux CentOS6.5
Project:
Jenkins
Priority:
Minor
Reporter:
Ed Randall
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/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-21549) Can not resolve status for downstream jobs in folders
Patrik Boström created JENKINS-21549 Can not resolve status for downstream jobs in folders Issue Type: Bug Assignee: Unassigned Components: delivery-pipeline Created: 29/Jan/14 3:21 PM Description: Can not resolve status for downstream jobs if jobs are in a folder. Project: Jenkins Priority: Major Reporter: Patrik Boström 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/groups/opt_out.
[JIRA] [ssh] (JENKINS-21551) Installing the SSH Credentials plugin
Likith Mandali created JENKINS-21551 Installing the SSH Credentials plugin Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: ssh, ssh-credentials Created: 29/Jan/14 4:04 PM Description: ! Error hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'filter': Cannot create inner bean '(inner bean)' of type jenkins.security.ExceptionTranslationFilter while setting bean property 'filters' with key 6; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#6': Initialization of bean failed; nested exception is java.lang.NullPointerException at hudson.WebAppMain$3.run(WebAppMain.java:234) Caused by: org.jvnet.hudson.reactor.ReactorException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'filter': Cannot create inner bean '(inner bean)' of type jenkins.security.ExceptionTranslationFilter while setting bean property 'filters' with key 6; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#6': Initialization of bean failed; nested exception is java.lang.NullPointerException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:908) at jenkins.model.Jenkins.init(Jenkins.java:807) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'filter': Cannot create inner bean '(inner bean)' of type jenkins.security.ExceptionTranslationFilter while setting bean property 'filters' with key 6; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#6': Initialization of bean failed; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:230) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:287) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:126) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1245) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1010) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Alex Earl resolved JENKINS-20692 as Fixed Optionally show action in CHANGES token Added %a and %d for pathFormat option. Change By: Alex Earl (29/Jan/14 4:28 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/groups/opt_out.
[JIRA] [core] (JENKINS-11872) UnsatisfiedLinkError when installing as Windows service
Brian Brooks commented on JENKINS-11872 UnsatisfiedLinkError when installing as Windows service @David, it has been a while since I dealt with the issue. I think the workaround was to run the Jenkins installer like it was a new install. I agree with you that the "Manage Jenkins - Install as Windows Service" feature should be yanked unless its going to be maintained. 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/groups/opt_out.
[JIRA] [core] (JENKINS-11872) UnsatisfiedLinkError when installing as Windows service
David Arndt commented on JENKINS-11872 UnsatisfiedLinkError when installing as Windows service I actually get this same error when I install/run from the command line. Jenkins continues to start up, but the error stack is displayed a few times on startup... 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/groups/opt_out.
[JIRA] [cucumber-testresult] (JENKINS-21545) Skipped steps don't mark test as failure
teilo assigned JENKINS-21545 to teilo Skipped steps dont mark test as failure Change By: teilo (29/Jan/14 5:19 PM) Assignee: teilo 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/groups/opt_out.
[JIRA] [cucumber-testresult] (JENKINS-21545) Skipped steps don't mark test as failure
teilo resolved JENKINS-21545 as Wont Fix Skipped steps dont mark test as failure bug in old versions of cucumber-jvm - please updade the version used to run your tests. Change By: teilo (29/Jan/14 5:20 PM) Status: Open Resolved Resolution: WontFix 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21552) Configureable Graph
Robert Paasche created JENKINS-21552 Configureable Graph Issue Type: Improvement Assignee: npiguet Components: sloccount Created: 29/Jan/14 5:29 PM Description: On old projects (e.g trunk or master) the graph on the job page will be nearly uninterpretable. It should be possible to limit the graph to show the last 30 builds only. (like checkstyle/findbugs plugin) Project: Jenkins Priority: Trivial Reporter: Robert Paasche 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21552) Configureable Graph
Robert Paasche updated JENKINS-21552 Configureable Graph Change By: Robert Paasche (29/Jan/14 5:31 PM) Affects Version/s: current 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/groups/opt_out.
[JIRA] [maven] (JENKINS-21554) NPE after Waiting for Jenkins to finish collecting data
Daniel Tehranian created JENKINS-21554 NPE after Waiting for Jenkins to finish collecting data Issue Type: Bug Assignee: Unassigned Components: maven Created: 29/Jan/14 5:58 PM Description: Originally posted to: https://groups.google.com/forum/#!topic/jenkinsci-users/hrMipbtLjxs Hi there, We are getting this NPE intermittently at the end of successful maven builds. We are using Jenkins 509.4 LTS and Maven plugin 509.4. Any ideas on what the issue might be or how I can squeeze more info out of the logs? Thanks, Dan INFO: Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Reactor Summary: Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: metrix-service-main ... SUCCESS [8.813s] Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: metrix-service-core ... SUCCESS [3:14.939s] Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: metrix-service-dist ... SUCCESS [10.969s] Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logResult INFO: Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logResult INFO: BUILD SUCCESS Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logStats INFO: Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logStats INFO: Total time: 3:40.847s Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logStats INFO: Finished at: Sun Jan 26 12:42:30 PST 2014 Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger logStats INFO: Final Memory: 31M/686M Jan 26, 2014 12:42:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionEnded INFO: [JENKINS] Archiving /jenkins/workspace/metrix-service-main/metrix-service/metrix-service-main/metrix-service-dist/pom.xml to /jenkins/jobs/metrix-service-main/modules/com.vi$metrix-service-dist/builds/2014-01-26_12-38-41/archive/com.vi/metrix-service-dist/1.1-SNAPSHOT/metrix-service-dist-1.1-SNAPSHOT.pom [JENKINS] Archiving /jenkins/workspace/metrix-service-main/metrix-service/metrix-service-main/metrix-service-core/pom.xml to /jenkins/jobs/metrix-service-main/modules/com.vi$metrix-service-core/builds/2014-01-26_12-38-41/archive/com.vi/metrix-service-core/1.1-SNAPSHOT/metrix-service-core-1.1-SNAPSHOT.pom [JENKINS] Archiving /jenkins/workspace/metrix-service-main/metrix-service/metrix-service-main/metrix-service-core/target/metrix-service-core-1.1-SNAPSHOT.jar to /jenkins/jobs/metrix-service-main/modules/com.vi$metrix-service-core/builds/2014-01-26_12-38-41/archive/com.vi/metrix-service-core/1.1-SNAPSHOT/metrix-service-core-1.1-SNAPSHOT.jar [JENKINS] Archiving /jenkins/workspace/metrix-service-main/metrix-service/metrix-service-main/pom.xml to /jenkins/jobs/metrix-service-main/modules/com.vi$metrix-service-main/builds/2014-01-26_12-38-41/archive/com.vi/metrix-service-main/1.1-SNAPSHOT/metrix-service-main-1.1-SNAPSHOT.pom Waiting for Jenkins to finish collecting data ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException project=hudson.maven.MavenModuleSet@4b632226[metrix-service-main] project.getModules()=[hudson.maven.MavenModule@20460e4f[metrix-service-main/com.vi:metrix-service-core][metrix-service-main/com.vi:metrix-service-core][relativePath:metrix-service/metrix-service-main/metrix-service-core],
[JIRA] [git] (JENKINS-21553) Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL
Andrew Pennebaker created JENKINS-21553 Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL Issue Type: Bug Assignee: Nicolas De Loof Components: git, jobgenerator Created: 29/Jan/14 5:58 PM Description: When I try to create a Maven test job, inputting an HTTPS:// URL for the git source results in an internal server error (specifically a null pointer error). As a mitigation, I can use a GIT:// URL instead, and the internal error goes away, allowing me to continue creating the job. Project: Jenkins Labels: git, https, create, creation, job,maven, Priority: Major Reporter: Andrew Pennebaker 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-16028) COPYARTIFACT_BUILD_NUMBER_ is not set when copyartifact plugin is ran as Maven pre-build
Thiagarajan M T commented on JENKINS-16028 COPYARTIFACT_BUILD_NUMBER_ is not set when copyartifact plugin is ran as Maven pre-build I need this to be fixed for my project. Is there anyway we could get it 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/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-21555) Internal server error during job creation: HTTPS:// link to Git Lab project page for Merge Builder configuration
Andrew Pennebaker created JENKINS-21555 Internal server error during job creation: HTTPS:// link to Git Lab project page for Merge Builder configuration Issue Type: Bug Assignee: Unassigned Components: jobgenerator Created: 29/Jan/14 6:13 PM Description: When I try to create a Maven git job, and specify an HTTPS:// link to a Git Lab project page for building on Merge Requests, Jenkins experiences an internal server error (unexpected '' less-than character). As a migitation, I uncheck the Build on Merge Request option completely, and am able to continue creating the job. Project: Jenkins Labels: merge,request,job,create,creation,git,lab,gitlab,git-lab, Priority: Major Reporter: Andrew Pennebaker 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-21548) Xvfb failure does not fail build
zregvart commented on JENKINS-21548 Xvfb failure does not fail build Hi Richard, thanks for reporting the issue. Is there anything that I should be aware with regards to your build/steps? I'm asking because since JENKINS-18094 (version 1.0.8) if you receive "Xvfb failed to start, consult the lines above for errors" message in the console log your build will inevitably be aborted due to RunnerAbortedException being thrown immediately after. If you indeed are running version 1.0.8 could you create a sample build job and attach it to this issue. Thanks Zoran 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws NPE when trying to change JDK for matrix build
Tony Sweeney created JENKINS-21556 Configuration slicing plugin throws NPE when trying to change JDK for matrix build Issue Type: Bug Affects Versions: current Assignee: mdonohue Components: configurationslicing Created: 29/Jan/14 6:25 PM Description: If you try to use the configuration slicing plugin to change the JDK for a bunch of jobs using the default JDK to some other one, it throws a stack trace at the first matrix job that it encounters. This is true whether or not the JDK is one of the build axes for the job Environment: CentOS 5.9 master, assorted slaves Project: Jenkins Priority: Major Reporter: Tony Sweeney 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build
Tony Sweeney updated JENKINS-21556 Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build Change By: Tony Sweeney (29/Jan/14 6:28 PM) Summary: Configurationslicingpluginthrows NPE UnsupportedOperationException whentryingtochangeJDKformatrixbuild 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21557) Possibly too wide table on summary page
Michal Turek created JENKINS-21557 Possibly too wide table on summary page Issue Type: Bug Affects Versions: current Assignee: Michal Turek Attachments: summary_ok.png, summary_width.png Components: sloccount Created: 29/Jan/14 6:28 PM Description: Width of table on summary page depends on other areas of the page. If there is e.g. long message in a commit log, the table will be very wide. See the attached screenshots. Environment: Plugin v1.14, checked on Chrome, Firefox, Opera. Project: Jenkins Priority: Minor Reporter: Michal Turek 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws NPE when trying to change JDK for matrix build
Tony Sweeney commented on JENKINS-21556 Configuration slicing plugin throws NPE when trying to change JDK for matrix build javax.servlet.ServletException: java.lang.UnsupportedOperationException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at
[JIRA] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build
Tony Sweeney commented on JENKINS-21556 Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build It succeeds for builds that are alphabetically before the name of the offending matrix build. Given that Matrix builds have their own optional JDK build axis, it probably doesn't make much sense for the JDK slicing to even consider them as slicing candidates. 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21557) Possibly too wide table on summary page
Michal Turek started work on JENKINS-21557 Possibly too wide table on summary page Change By: Michal Turek (29/Jan/14 6:41 PM) Status: Open InProgress 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21557) Possibly too wide table on summary page
SCM/JIRA link daemon commented on JENKINS-21557 Possibly too wide table on summary page Code changed in jenkins User: Michal Turek Path: src/main/resources/hudson/plugins/sloccount/SloccountBuildAction/summary.jelly http://jenkins-ci.org/commit/sloccount-plugin/07e91e82f9b050941e55cc6644aeaad892a11502 Log: Merge pull request #31 from mixalturek/master JENKINS-21557 Possibly too wide table on summary page Compare: https://github.com/jenkinsci/sloccount-plugin/compare/a9b0d6c0bb6a...07e91e82f9b0 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21557) Possibly too wide table on summary page
SCM/JIRA link daemon commented on JENKINS-21557 Possibly too wide table on summary page Code changed in jenkins User: Michal Turek Path: src/main/resources/hudson/plugins/sloccount/SloccountBuildAction/summary.jelly http://jenkins-ci.org/commit/sloccount-plugin/b63b5abe2a137a2b66ccd43e42e54cfe706f7788 Log: JENKINS-21557 Possibly too wide table on summary page Width of table on summary page depends on other areas of the page. If there is e.g. long message in a commit log, the table will be very wide. It seems the default table width is set to 100% in CSS, change to "auto" helps. Tested in Chrome, Firefox and Opera. 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build
Tony Sweeney commented on JENKINS-21556 Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build Note that it does actually change the on-disk setting in the config.xml for the JDK for the matrix build that causes the exception. However, it still shows as its original setting if you go back in to the JDK slicing plugin. It may be significant that I'm trying to change all builds that use the (Default) JDK to a different one. 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21557) Possibly too wide table on summary page
Michal Turek resolved JENKINS-21557 as Fixed Possibly too wide table on summary page Fixed, will be released in 1.15. Change By: Michal Turek (29/Jan/14 6:45 PM) Status: InProgress Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21557) Possibly too wide table on summary page
Michal Turek closed JENKINS-21557 as Fixed Possibly too wide table on summary page Change By: Michal Turek (29/Jan/14 6:45 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17655) Multijob plugin does not support Folder plugin
hagzag commented on JENKINS-17655 Multijob plugin does not support Folder plugin If you pull the latest code into your fork and add the commit on top of it, I will be able to build an h/jpi for you to test. Just comment back once you have done it - once the h/jpi corrects these issues I can release another version so we could do this over the next few days. Tx HP 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21552) Configureable Graph
Michal Turek assigned JENKINS-21552 to Michal Turek Configureable Graph Change By: Michal Turek (29/Jan/14 8:14 PM) Assignee: npiguet MichalTurek 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21552) Configureable Graph
Michal Turek started work on JENKINS-21552 Configureable Graph Change By: Michal Turek (29/Jan/14 8:14 PM) Status: Open InProgress 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/groups/opt_out.
[JIRA] [rtc] (JENKINS-21477) Enable multiple Jazz servers per project
Heather Fraser-Dube assigned JENKINS-21477 to Unassigned Enable multiple Jazz servers per project Change By: Heather Fraser-Dube (29/Jan/14 8:24 PM) Assignee: DeluanQuintão 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/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-14675) Schema 'DBUSER' does not exist error in integrity plugin
Cletus DSouza commented on JENKINS-14675 Schema DBUSER does not exist error in integrity plugin The common theme here seems to be when migrating from an older version of the plugin to a newer version. Especially when there's been architectural changes with the way the plugin stores retrieves its cache information. While I make an attempt to prevent such changes, it can't be avoided completely. This is especially true in the past. Going forward, I don't anticipate any major changes to the plugin's architecture as it relates the the derby database. Can I get a consensus that re-creating the job and/or repeated builds (which is essentially re-creating the derby db) resolves this issue? Thanks! Cletus 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/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!
Cletus DSouza commented on JENKINS-21260 PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed! There was a community contributed change that facilitates the Integrity plugin use with the Multiple SCMs 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/groups/opt_out.
[JIRA] [security] (JENKINS-9008) SIGSEGV (JVM crash) in Jenkins native method hudson.security.PAMSecurityRealm$PAMAuthenticationProvider.authenticate
Jamshid Afshar commented on JENKINS-9008 SIGSEGV (JVM crash) in Jenkins native method hudson.security.PAMSecurityRealm$PAMAuthenticationProvider.authenticate Long shot but David, did you ever figure out the cause of this "pam" issue? I'm seeing the same org.jvnet.libpam.PAM.authenticate jvm crash, though unrelated to jenkins. Java 7 on CentOS 6.4. 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21552) Configureable Graph
SCM/JIRA link daemon commented on JENKINS-21552 Configureable Graph Code changed in jenkins User: Michal Turek Path: src/main/java/hudson/plugins/sloccount/SloccountChartBuilder.java src/main/java/hudson/plugins/sloccount/SloccountProjectAction.java src/main/java/hudson/plugins/sloccount/SloccountPublisher.java src/main/resources/hudson/plugins/sloccount/Messages.properties src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.properties http://jenkins-ci.org/commit/sloccount-plugin/111933439b6f30bce87e0b5851313e0aa56e6f45 Log: Merge pull request #32 from mixalturek/master JENKINS-21552 Configureable Graph Compare: https://github.com/jenkinsci/sloccount-plugin/compare/07e91e82f9b0...111933439b6f 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21552) Configureable Graph
SCM/JIRA link daemon commented on JENKINS-21552 Configureable Graph Code changed in jenkins User: Michal Turek Path: src/main/java/hudson/plugins/sloccount/SloccountChartBuilder.java src/main/java/hudson/plugins/sloccount/SloccountProjectAction.java src/main/java/hudson/plugins/sloccount/SloccountPublisher.java src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.properties http://jenkins-ci.org/commit/sloccount-plugin/25d14a041d99ace02362f814ceb14a32c306a1ed Log: JENKINS-21552 Configureable Graph The graph on the job page of old projects will be nearly uninterpretable, because there are too many builds. Option to limit maximum number of last successful builds displayed in the graph added to the advanced configuration. If the value is one or less (at least two builds are required to display the graph) the number will be considered as unlimited. If the value is not configured, Java will interpret it as zero (unlimited), which is fully backward compatible. 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/groups/opt_out.
[JIRA] [security] (JENKINS-9008) SIGSEGV (JVM crash) in Jenkins native method hudson.security.PAMSecurityRealm$PAMAuthenticationProvider.authenticate
David Biesack commented on JENKINS-9008 SIGSEGV (JVM crash) in Jenkins native method hudson.security.PAMSecurityRealm$PAMAuthenticationProvider.authenticate Sorry, no, I never tracked it down and simply went with the workaround I noted above. 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21552) Configureable Graph
Michal Turek closed JENKINS-21552 as Fixed Configureable Graph Change By: Michal Turek (29/Jan/14 9:38 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-21552) Configureable Graph
Michal Turek resolved JENKINS-21552 as Fixed Configureable Graph Option to limit maximum number of last successful builds displayed in the graph added to the advanced configuration. Will be released in 1.15. Change By: Michal Turek (29/Jan/14 9:37 PM) Status: InProgress Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [ldap] (JENKINS-21558) When the LDAP plugin is enabled, it locks out a user who isn't attempting to log in
Jean-Marc Ray created JENKINS-21558 When the LDAP plugin is enabled, it locks out a user who isnt attempting to log in Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ldap Created: 29/Jan/14 9:44 PM Description: Once the LDAP plugin is enabled (security is turned on, and LDAP configured) the plugin attempts to bind to LDAP with a different user name then the one we configure in the setup screen. our manager DN is something like: CN=JENKINS_SERVER,OU=Service Accounts,OU=xxx,DC=xxx,DC=com This all works, and users can log in and be authenticated (the bind for the above works). But for some reason there is a rouge attempt to also bind via a real user ID, the guy who originally set up the server. The suspicion is that at one point he put his own credentials in while initially setting it up, and it loved him so much it doesn't want to ever forget him. Does that make sense? is there a cache someplace I can check?, or something I can remove to kill an and all LDAP config to start from scratch? (disabling security and entering the data in fresh doesn't have an effect, the rouge bind lives on) Error in the logs is: WARNING: Failed to bind to LDAP: userDnCN=Veman\, Chris,OU=Users,OU=CDP,DC=TDBFG,DC=com username=veermc2 javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903AA, comment: AcceptSecurityContext error, data 52e, v1772 We wouldnt care, but the poor fella keeps getting locked out of all systems connected to our LDAP. We are at version: 1.549 of jenkins and 1.6 of the LDAP plugin. Project: Jenkins Priority: Major Reporter: Jean-Marc Ray 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/groups/opt_out.
[JIRA] [ldap] (JENKINS-21558) When the LDAP plugin is enabled, it locks out a user who isn't attempting to log in
Christiaan Veerman commented on JENKINS-21558 When the LDAP plugin is enabled, it locks out a user who isnt attempting to log in I'm the guy getting my AD account locked when security is enabled 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-12134) Copying an artifact should (optionally) fingerprint all artifacts
SCM/JIRA link daemon commented on JENKINS-12134 Copying an artifact should (optionally) fingerprint all artifacts Code changed in jenkins User: Kelsey Prantis Path: src/main/java/hudson/plugins/copyartifact/Copier.java src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/main/java/hudson/plugins/copyartifact/FilePathCopyMethod.java src/main/java/hudson/plugins/copyartifact/FingerprintingCopyMethod.java src/main/resources/hudson/plugins/copyartifact/CopyArtifact/config.jelly src/main/webapp/help-flatten-optional.html src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java http://jenkins-ci.org/commit/copyartifact-plugin/d10dad4341bc2495f469dc5cd4534bbe5e58b13c Log: JENKINS-12134 - Make fingerprinting artifacts optional. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21560) Git Client 1.5.0+ does not work with Kerberos anymore (empty password in netrc)
jam jam created JENKINS-21560 Git Client 1.5.0+ does not work with Kerberos anymore (empty password in netrc) Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 29/Jan/14 10:06 PM Description: We are using Kerberos authentication for GIT over HTTPS. We had the setup working with Jenkins plugins git-client 1.0.7 and git 1.4.0. It seems, since git-client 1.5.0 this type of authentication is broken for GIT in Jenkins. Our Jenkins uses a Kerberos keytab and its netrc contains the Jenkins' Kerberos username, but without password, example for netrc: machine git.example.com login JENKINS/jenkins.example.com Since 1.5.0 git-client tries to pass this empty/missing password to our Webserver (Apache with mod_auth_kerb) and (of course) fails at authentication (HTTP 401). Commit a3d3d54 (replace "clone" by "init+fetch" so we can configure git to use a local gitcrendentials store) introduces some new credential handling arround netrc. So I think the problem is from this commit, but I'm not 100% sure. Environment: Ubuntu 12.04 LTS amd64 Project: Jenkins Priority: Major Reporter: jam jam 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/groups/opt_out.
[JIRA] [jenkins-jira-issue-updater] (JENKINS-21559) Default GIT to run 'git clone' instead of 'git fetch'
Matt Evans created JENKINS-21559 Default GIT to run git clone instead of git fetch Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: jenkins-jira-issue-updater Created: 29/Jan/14 10:05 PM Description: Whenever we create a new build we have to enable additional behaviors and force a wipe out of the workspace and a new clone. Why does the GIT plugin do a 'git fetch' by default if it doesn't merge in the changes from origin? It just seems it would make sense if by default it did a git pull Fix Versions: current Project: Jenkins Priority: Major Reporter: Matt Evans 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21560) Git Client 1.5.0+ does not work with Kerberos anymore (empty password in netrc)
jam jam updated JENKINS-21560 Git Client 1.5.0+ does not work with Kerberos anymore (empty password in netrc) Change By: jam jam (29/Jan/14 10:10 PM) Environment: Ubuntu12.04LTSamd64 ,OracleJava1.6.0_4364-bit 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-21498) Use Upstream Project revision does not seem to be working correctly
Andrew Barnish commented on JENKINS-21498 Use Upstream Project revision does not seem to be working correctly We increased the quiet period to 60 seconds but that did not seem to make any difference. Can you suggest anything else that we could check in order to debug this 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/groups/opt_out.
[JIRA] [maven-info] (JENKINS-21450) NPE on Selected Module Last Version when Jenkins Job Name != artifactId
Emilio Jose Mena Cebrian commented on JENKINS-21450 NPE on Selected Module Last Version when Jenkins Job Name != artifactId I'm not sure if it's fixed The exception is thrown due to a null Job's configuration and I haven't found a reproducible conditions in which it's thrown 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/groups/opt_out.
[JIRA] [git] (JENKINS-21561) GIT Plugin 2.0.1 doesn't work with Jenkins Multiple SCM .3
George Baker created JENKINS-21561 GIT Plugin 2.0.1 doesnt work with Jenkins Multiple SCM .3 Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, multiple-scms Created: 29/Jan/14 10:54 PM Description: During a recent install of the configuration above I attempted to use multiple SCMs to configure two GIT repos. However whenever I selected GIT from the Add SCM drop down the screen would not display the GIT options. It would however show them for CVS and subversion. On another similar machine running Jenkins 1.534, Multiple SCMs plugin .2 (Same plugin), and GIT plugin 1.3.0 I am able to select and configure multiple GIT repos. From what I can tell the GIT options changed between 1.3 and 2.0.1. There is now a credentials drop down which the Multiple SCM plugin might not support. Environment: Mac OS X 10.8.5 Java 7, Jenkins 1.549, Git Plugin 2.0.1 Jenkins Multiple SCMs plugin .3 Project: Jenkins Priority: Blocker Reporter: George Baker 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/groups/opt_out.
[JIRA] [compact-columns] (JENKINS-21562) No context menus for build sub-pages
Andrew Johnson created JENKINS-21562 No context menus for build sub-pages Issue Type: New Feature Assignee: Jacob Robertson Components: compact-columns Created: 29/Jan/14 11:30 PM Description: The built-in Last Success/Failure columns can pop up a menu for each build shown that give quick access to the sub-pages for that build (Changes, Console Output etc). The compact columns equivalent don't provide those menus or any equivalent, which I find very useful. Project: Jenkins Priority: Minor Reporter: Andrew Johnson 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-21498) Use Upstream Project revision does not seem to be working correctly
Rob Petti edited a comment on JENKINS-21498 Use Upstream Project revision does not seem to be working correctly Does it work correctly if you start the downstream job by hand, or does it still pick up the next-to-last build of the upstream job? 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-21498) Use Upstream Project revision does not seem to be working correctly
Rob Petti commented on JENKINS-21498 Use Upstream Project revision does not seem to be working correctly Does it work correctly if you start the downstream job by hand, or does it still pick up the next-to-last build of the upstream job. 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-21498) Use Upstream Project revision does not seem to be working correctly
Rob Petti commented on JENKINS-21498 Use Upstream Project revision does not seem to be working correctly As for the mechanism used, builds are given 'tag actions' after the sync is completed. The plugin just reads from that. If it's getting the wrong build, then that would explain the behavior, but I don't know why that would happen. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20502) Cannot find any revision to build on clean workspace
cb372 commented on JENKINS-20502 Cannot find any revision to build on clean workspace @David Vo, thanks for the tip, but the version is not pinned. It's definitely running version 2.0.1. 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/groups/opt_out.
API to trigger a Release Build
Is there an API in the Release Build plug-in to trigger a release build via url? Similar to trigging a build via https://jenkins.company.com/job/JobName/build https://jenkins.company.com/job/JobName/buildWithParameters?Parm1=Value1Parm2=Value2 I've seen similar posts for people searching for api's but can't find the correct link for a plug-in to see what api's they contribute. Perhaps some standards on listing the plug-in api link in the respective plug-in doc would help? https://wiki.jenkins-ci.org/display/JENKINS/Release+Plugin The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21563) Fail build when locked file.
Dan Treble created JENKINS-21563 Fail build when locked file. Issue Type: Bug Assignee: Unassigned Components: subversion Created: 30/Jan/14 2:14 AM Description: When cancelling a build during a update, the local copy often ends up locked. The next build will throw the error "Workspace appear to be locked, so getting a fresh workspace" and re get the whole workspace. Neither the lock or the re syncing the whole workspace is ideal. This patch at least stops the workspace being wiped and re syncing: https://github.com/hudson3-plugins/subversion-plugin/commit/37ca9c134702878e6bb824dde108d63c6df043d8 Project: Jenkins Priority: Minor Reporter: Dan Treble 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/groups/opt_out.
[JIRA] [maven] (JENKINS-21541) After I upgrade to 1.547, Maven Build fails with ERROR: Failed to parse POMs java.net.SocketException: Connection reset
Senthil Kumar Chandran commented on JENKINS-21541 After I upgrade to 1.547, Maven Build fails with ERROR: Failed to parse POMs java.net.SocketException: Connection reset Can anyone help me on this please.. 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/groups/opt_out.
