[JIRA] [jira] (JENKINS-18166) Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7
Ben McDonie commented on JENKINS-18166 Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7 Stefan, how is this new REST plugin coming along? Any progress? I too am interested in a plugin that uses REST. I've been having all kinds of issues with the current plugin in the latest JIRA versions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15121) Invalid URL's on Project/Build pages for deployed artifacts
Ben McDonie
commented on JENKINS-15121
Invalid URL's on Project/Build pages for deployed artifacts
I use this plugin for all my deployments, and it works great.
I have one feature request that is related to this issue. It would be nice if I could configure 2 different paths... (1) The path the building node actually copies to, and (2) the path that the build page URL references.
Why do I want this?
My Jenkins master is on a Windows Server node. Many jobs build on a Mac slave node. The common location for our deployed artifacts is on a network share that we commonly access in Windows environments via \\server\share notation. On the mac, however, we simply mount the directory and deploy to /Volumes/share. Basically, each node has an env variable that uses the appropriate directory string for its environment so that all builds deploy to ${DEPLOY_PATH}/builds/${BUILD_NUMBER}/so-on-so-forth.
With this strategy, the execution of the builds work great ... in BOTH environments. The issue is the URL to the deployed artifacts on the build page. When it was built on the windows machine, the URLs look like "\\server\share" and users can click them with success. When the mac did the build, the URL says "/Volumes/share/..." and they do not work.
Could the plugin be modified in such a way to allow a workaround to 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
[JIRA] (JENKINS-13760) "Tag this build" results in "ERROR: Failed to tag, org.tmatesoft.svn.core.SVNException: svn: File not found: revision 555, path '/trunk/trunk'"
Ben McDonie commented on JENKINS-13760 "Tag this build" results in "ERROR: Failed to tag, org.tmatesoft.svn.core.SVNException: svn: File not found: revision 555, path '/trunk/trunk'" Is this at the top of anyone's list? I could really use a solution to this. I get a similar stacktrace (404 on 'trunk/trunk'). I can provide more details if someone is willing to look into it. Basically I used to have subversion plugin 1.43, but downgraded to 1.39 due to JENKINS-14550. Now with 1.39, my checkouts work, but I can no longer tag builds 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
[JIRA] (JENKINS-7103) Horizontal scrollbars on Configure page when using matrix-based security
Ben McDonie commented on JENKINS-7103 Horizontal scrollbars on Configure page when using matrix-based security Are these workarounds in any available versions of Jenkins? I've used up to 1.489 and as a Chrome user would love to see the entire "Configuration" page on one screen. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Ben McDonie commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException I am also seeing this error in 1.489 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
[JIRA] (JENKINS-15439) Jenkins build records lazy-loading failed to load some of my jobs.
Ben McDonie commented on JENKINS-15439 Jenkins build records lazy-loading failed to load some of my jobs. I am running version 1.488 and am still having issues with LazyLoading. My stack trace is in JENKINS-15642. It happens near the end of Maven builds that were triggered by SCM 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
[JIRA] (JENKINS-15642) ArrayIndexOutOfBounds exception with Maven build when triggered by SCM change
Ben McDonie updated JENKINS-15642 ArrayIndexOutOfBounds exception with Maven build when triggered by SCM change Change By: Ben McDonie (26/Oct/12 6:57 PM) Summary: ArrayOutOfBounds ArrayIndexOutOfBounds exception with Maven build when triggered by SCM change Labels: ArrayOutOfBoundsException ArrayIndexOutOfBounds lazy-loading maven scm 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
[JIRA] (JENKINS-15642) ArrayOutOfBounds exception with Maven build when triggered by SCM change
Ben McDonie created JENKINS-15642 ArrayOutOfBounds exception with Maven build when triggered by SCM change Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 26/Oct/12 6:56 PM Description: When I force the build, it succeeds. When the build is triggered by an SCM change, the job appears to build successfully until the very end of the "mvn clean install site" command where I get the following stack trace, which seems awfully familiar to some old lazily loaded job issues that I had a few versions ago... Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #3 DESC: lo=17,hi=3,size=106,size2=106 cause : Assertion error: failing to load #3 DESC: lo=17,hi=3,size=106,size2=106 Stack trace : org.apache.maven.InternalErrorException: Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #3 DESC: lo=17,hi=3,size=106,size2=106 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:98) at hudson.maven.Maven3Builder.call(Maven3Builder.java:64) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #3 DESC: lo=17,hi=3,size=106,size2=106 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:418) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:210) at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349) at hudson.model.Run.onLoad(Run.java:303) at hudson.maven.MavenModuleSetBuild.onLoad(MavenModuleSetBuild.java:140) at hudson.model.RunMap.retrieve(RunMap.java:221) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:638) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:621) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:210) at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349) at hudson.model.Run.onLoad(Run.java:303) at hudson.m
[JIRA] (JENKINS-15610) Jenkins seems confused about version
Ben McDonie resolved JENKINS-15610 as Not A Defect Jenkins seems confused about version This must have been a side-effect of leftover or cached artifacts in my glassfish domain. I deleted everything related to Jenkins and redeployed. Seems OK now. Change By: Ben McDonie (24/Oct/12 3:23 PM) Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-15610) Jenkins seems confused about version
Ben McDonie created JENKINS-15610 Jenkins seems confused about version Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: about_jenkins.png, version_bottom.png Components: versionnumber Created: 24/Oct/12 1:15 PM Description: I upgraded Jenkins to 1.487 this morning. I undeployed the old Jenkins application (1.486) from my Glassfish server. I deployed the new Jenkins WAR (1.487) to my Glassfish server. In most places, the version reads "1.486" (see attached). On the "About Jenkins" page, I get conflicting version numbers (see attached). Any help is appreciated! Environment: Windows 7 x64 Deployed on Glassfish Open Source (3.1.2.2) Project: Jenkins Labels: jenkins upgrade version Priority: Major Reporter: Ben McDonie 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
