[JIRA] (JENKINS-16287) Race condition in 'build' CLI command
Krzysztof Malinowski created JENKINS-16287 Race condition in build CLI command Issue Type: Bug Assignee: Unassigned Components: cli Created: 09/Jan/13 8:50 AM Description: I started a build through jenkins-cli.jar with option to show console and wait for start. It waited to start as long as the build was in queue, but when the build started to build, jenkins-cli exits with exception that log was not found. It seems to me like a race condition between build start, log creation and checking for log in jenkins-cli. $ java -jar ~/jenkins-cli.jar build project -p build=value -s -v -w Started project #188 java.io.FileNotFoundException: /jenkins/jenkins_home/jobs/project/builds/2013-01-09_09-43-12/log (No such file or directory) at java.io.RandomAccessFile.open(Native Method) at java.io.RandomAccessFile.init(RandomAccessFile.java:216) at org.kohsuke.stapler.framework.io.LargeText$FileSession.init(LargeText.java:397) at org.kohsuke.stapler.framework.io.LargeText$2.open(LargeText.java:120) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:210) at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:151) at hudson.model.Run.writeWholeLogTo(Run.java:1253) at hudson.cli.BuildCommand.run(BuildCommand.java:150) at hudson.cli.CLICommand.main(CLICommand.java:229) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) 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 hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) 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 hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95) 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) Environment: Jenkins 1.498 on RHEL 5 x86_64 Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski 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-16266) Direct link to console output (without first cliking on job) creates a 404
cedd burge commented on JENKINS-16266 Direct link to console output (without first cliking on job) creates a 404 Yep, 1.492. Sorry about the duplicate request, I didn't find the other one. I'll downgrade to 1.484 for the time being. Cheers. Cedd. 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-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach commented on JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp This is why I've posted a link and set this issue to resolved aready. 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-15655) Bad $PATH variable on AIX
Yury Pukhalsky updated JENKINS-15655 Bad $PATH variable on AIX Change By: Yury Pukhalsky (09/Jan/13 10:04 AM) Description: Wheniinvokeataskonaixbyssh,igetwrongvalueof$PATHvariable.Firstofall,/binisprependedtoitautomatically.Formeitsbadbecausetheresawrongversionofutilityin/bin,thegoodoneisin/usr/local/bin.Second,elementsofthePATHvariableiconfigureinthenodepropertiesarebeingdoubledintheresultingPATH.Heresthevalueofthevariableas see seen fromtheinvokedscript:/bin:/usr/local/bin:/usr/local/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java14/jre/bin:/usr/java14/bin:/usr/vac/bin:/opt/freeware/bin:/usr/vac/bin:/opt/freeware/binWhileinthenodeproperties(envvars)theconfigurationis:/usr/local/bin:$PATH:/usr/vac/bin:/opt/freeware/bin 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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Markus Meisterernst commented on JENKINS-14193 EnvInject doesnt pass variables defined in prebuild step if maven project is used Hi, maven is a real pain in the ass. And this bug really adds on to it. So could you repriotize your work, please, or unassign it so someone else is able to supply a fix. Thx and sorry for my complaints. 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-15860) Mail body for two simultaneous mails get mixed
Xavier Nodet commented on JENKINS-15860 Mail body for two simultaneous mails get mixed Thanks. I'll try it. A way to reproduce the issue would be to have two jobs started on the same agent, and disconnect the agent. This triggers simultaneous build failures. It just happened to us, and one of the two mails I got had the other's body... 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-16234) Plugin does not currently work for Clearcase Base
Vincent Latombe commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Hello, according to IBM documentation, -stgloc -auto, -vws are valid both for Clearcase Base and UCM http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_ref.doc/topics/ct_mkview.htm Could you clarify which version of Clearcase you are using ? 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-14900) Copying from workspace drops files matching Ant's default excludes
Dave Hunt commented on JENKINS-14900 Copying from workspace drops files matching Ants default excludes I was afraid you'd say that Fred! I would appreciate you looking at this and giving me any pointers. I have already attempted to fix it myself, but so far had little success. 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-16288) CheckStyle Plugin for Jenkins
Capgemini Axa created JENKINS-16288 CheckStyle Plugin for Jenkins Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: checkstyle Created: 09/Jan/13 11:54 AM Description: The CheckStyle Plugin for Jenkins seems to be unreliable. Without any modifications in the code, the plugins logs warnings. These warnings automatically get fixed in the next build. Is there a way out to correct these warnings? Fix Versions: current Project: Jenkins Labels: plugin Priority: Major Reporter: Capgemini Axa 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-16288) CheckStyle Plugin for Jenkins
Ulli Hafner commented on JENKINS-16288 CheckStyle Plugin for Jenkins Can you add some more details? And which versions are you using? Which build type? Do you mean new warnings? 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-15156) Builds Disappear from Build History after Completion
Martin Wiklundh commented on JENKINS-15156 Builds Disappear from Build History after Completion I made a copy of a broken project and the copy seems to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16289) Please bundle uninstaller with Jenkins Mac install
David Stark created JENKINS-16289 Please bundle uninstaller with Jenkins Mac install Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 09/Jan/13 12:23 PM Description: The Jenkins installer .pkg provided at http://mirrors.jenkins-ci.org/osx/latest installs Jenkins as a service, but provided no uninstall script or instructions. There appears to be an uninstall script at https://issues.jenkins-ci.org/browse/JENKINS-11776 . Could you include, in the install, this uninstall script or some other clearly visible way of uninstalling Jenkins? Environment: Mac OS X 10.6.8 Project: Jenkins Labels: mac Priority: Major Reporter: David Stark 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-16288) CheckStyle Plugin for Jenkins
Capgemini Axa commented on JENKINS-16288 CheckStyle Plugin for Jenkins The build for checkstyle plugin is launched every morning. So,for example yesterday morning, there were 15 warnings...(high and low), this morning it showed 35 warnings even though no code had been modified between yesterday and today. The warnings should have been 15 today. The version is 3.32 and the one installed is 2.14 in jenkins. The checkstyle jar used to generate the results is checkstyle5.0.jar 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-15068) Save/update password for a user seems impossible on JDK1.5
Jean Blanchard commented on JENKINS-15068 Save/update password for a user seems impossible on JDK1.5 This is indeed fixed by replacing the JBCrypt jar with one compiled with JDK5. See https://code.google.com/p/jbcrypt/issues/detail?id=7 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-15156) Builds Disappear from Build History after Completion
Martin Wiklundh edited a comment on JENKINS-15156 Builds Disappear from Build History after Completion I made a copy of a broken project and the copy seems to work. Edit: No, it broke after some hours. 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-15156) Builds Disappear from Build History after Completion
Martin Wiklundh edited a comment on JENKINS-15156 Builds Disappear from Build History after Completion I made a copy of a broken project and the copy seems to work. Edit: Renaming the copy broke it, but renaming back again gave the history back. 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-16233) EnvInject plugin using a cached value for ${WORKSPACE}
Dave Hunt
commented on JENKINS-16233
EnvInject plugin using a cached value for ${WORKSPACE}
I suspect this is related to JENKINS-15658
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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted IPv6 is enabled by default for WS 2008R2, although we are not using it. I disabled it and got the same error trying to send email when I ran my test build. 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted I'm running out of ideas...I can't replicate this locally. I don't have access to a Windows box with IPv6 capabilities, but since you disabled it in your test and you still see issues, it seems like that wouldn't be the issue. Can you try enabling the mail.debug property and posting the log output from that (it should go to the Jenkins log). 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-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves
Michael Prokop created JENKINS-16290 git parameter plugin doesnt support Jenkins slave setup with git repos checked out only on slaves Issue Type: Bug Assignee: Unassigned Components: git-parameter Created: 09/Jan/13 3:57 PM Description: The "Known Limitations / Bugs" section on https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin mentions: There is a problem when you want to build your project for a first time and you don't have any suitable workspace which works with git, then the list to chose from is empty, but it will work after the first build This is true for a single node Jenkins setup, but if building on slaves then the git checkout/repos usually is present only on the slaves and the 'git fetch -t' by the git parameter plugin will never succeed. 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
[JIRA] (JENKINS-16291) Support automatic proxy configuration
Jesse Glick created JENKINS-16291 Support automatic proxy configuration Issue Type: New Feature Assignee: stephenconnolly Components: async-http-client, core Created: 09/Jan/13 4:00 PM Description: For installations using WPAD or otherwise where it would be awkward to statically configure a single proxy server, it would be desirable to support java.net.useSystemProxies as http://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html describes. This would be an option in hudson.ProxyConfiguration, possibly requiring a restart once selected since this system property appears to be read just once when java.net classes are first used. When set, open and similar calls would just use java.net calls without further ado (in fact it is unclear why the current code does not simply set a ProxySelector and thus bypass the need for such methods). jenkins.plugins.asynchttpclient.AHCUtils would also need to take note of this field; if set, it would need to call java.net.ProxySelector to pick a proxy. It is unfortunately designed incorrectly in that it assumes a single proxy, whereas ProxySelector asks for a particular host and protocol, since it is common for corporate LANs to use proxies for some hosts but not others; may suffice to deprecate this simplistic method and for the benefit of old clients have it pick nowhere.net and HTTP as a typical pair. Project: Jenkins Labels: proxy Priority: Major Reporter: Jesse Glick 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-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Duane Bronson commented on JENKINS-16273 Slaves cannot connect to master through JNLP after upgrading to 1.498 @Jesse: This is broken for the "Logged-in users can do anything" authorization policy. The help on that suggest that this is not "security" but instead record keeping, so it really shouldn't be locked down like this. Could we allow slaves access to jnlp in this mode? Or, allow a --auth user:password option to the slave start command which doesn't seem to work right now. Context help on "Logged-in users can do anything" from the configureSecurity page: "This mode is useful to force users to log in before taking actions, so that you can keep record of who has done what. This setting can be also used in public-facing Jenkins, where you only allow trusted users to have user accounts." 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-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Duane Bronson reopened JENKINS-16273 Slaves cannot connect to master through JNLP after upgrading to 1.498 Change By: Duane Bronson (09/Jan/13 4:19 PM) Resolution: NotADefect 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
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted What version of the Mailer plugin is installed on your system? If it is 1.2, can you please try upgrading to 1.4 and see if that changes anything? 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-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Jesper Jensen commented on JENKINS-16273 Slaves cannot connect to master through JNLP after upgrading to 1.498 The slave agent windows service install is also broken by this change. 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted We're still trying to figure out how to enable mail.debug in Windows... 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-5682) when keeping past reports, project should link to latest build report
Kyle Leinen updated JENKINS-5682 when keeping past reports, project should link to latest build report Change By: Kyle Leinen (09/Jan/13 4:31 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted How do you start Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11689) HTMLPublisher does not publish latest report to project page if build fails
Kyle Leinen commented on JENKINS-11689 HTMLPublisher does not publish latest report to project page if build fails Any updates on this? I am very interested in getting this corrected or having a setting added to switch the 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
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted It starts automatically as a service when the server boots. 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-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token
Jesse Glick updated JENKINS-16273 Slaves forbidden to request JNLP anonymously but no clear way to pass API token @nerdmachine: regardless of what the help on “Logged-in users can do anything” may suggest, it is a true security policy and it means that any operation requiring authentication—even GET requests which do produce any “records” to keep—must be accompanied by a valid login token. I do not know much about the Windows service; someone who understands this code will need to evaluate how it should be provided with an API token. Without any special (Windows-specific) tool you can always download a *.jnlp file, run it manually, and when prompted ask to save it as a service; this is just a feature of Java WebStart. Change By: Jesse Glick (09/Jan/13 4:54 PM) Summary: Slaves cannotconnect forbidden to masterthrough request JNLP afterupgrading anonymouslybutnoclearway to 1.498 passAPItoken Labels: jnlpregressionsecurityslave Environment: 1.498+, WindowsServer2008R2 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-16272) LTS 1.480.2 breaks launching slaves via jnlp
Jesse Glick commented on JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp @sbreitbach please use “Not a Defect” as “Fixed” implies that some code change was made to produce a 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach reopened JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp Change By: Steffen Breitbach (09/Jan/13 4:58 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach resolved JENKINS-16272 as Not A Defect LTS 1.480.2 breaks launching slaves via jnlp Change By: Steffen Breitbach (09/Jan/13 4:58 PM) Status: Reopened Resolved 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach closed JENKINS-16272 as Not A Defect LTS 1.480.2 breaks launching slaves via jnlp Change By: Steffen Breitbach (09/Jan/13 4:58 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
[JIRA] (JENKINS-11102) Give the possibility to monitor all branches as Git plugin
Jesse Glick commented on JENKINS-11102 Give the possibility to monitor all branches as Git plugin @marc_swingler understood that you do not need e.g. lastStableBuild/artifact/x.jar to be meaningful since you would use the repo for that. But the lack of clear meaning for the job status (i.e. status of last build) remains; see http://stackoverflow.com/questions/13019222/is-there-a-branch-specific-badge-icon/13031723#13031723 for some discussion. Anyway, given the lack to date of a proper solution in Jenkins core the best that can be done in an SCM plugin is to offer this kind of feature and hope for the best. 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-9965) Nunit plugin does not display graph when fingerprinting is used on the xml report
Jesse Jacob commented on JENKINS-9965 Nunit plugin does not display graph when fingerprinting is used on the xml report The disappearing graph has been a source of embarrassment over the last year as I've taught various groups to use Jenkins and have to explain to people that you have to click "Save" until the graph comes back on an otherwise very polished product, so I've put up $50 US to anyone who can fix it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/122/nunit-plugin-does-not-display-graph-when-fingerprinting-is-used-on-the-xml-report). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! 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-16292) Set Release date to now() for Post Build Step 'Mark a JIRA Version as Released'
Miles Tillinger created JENKINS-16292 Set Release date to now() for Post Build Step Mark a JIRA Version as Released Issue Type: Improvement Assignee: Unassigned Components: jira Created: 09/Jan/13 5:08 PM Description: This would be nice as an option, because in some development workflows we don't set the Release date for a version in advance, but like to know historically when a version was Released. Project: Jenkins Priority: Major Reporter: Miles Tillinger 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted We already have Mailer 1.4 installed. The Plugin Manager currently shows no updates available. 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-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base 7.something, I believe. -stgloc: Requires a shared drive on a server. -auto: Requires a storage location to be set up. -vws: UNC Path name starting with server. Requires a share to be set up. Also allowable for a snapshot view: NONE OF THE ABOVE. View files are created in current working directory. See examples at end of the page. The site I am at has the following issues: No server share is set up. No NAS is set up for this Admin won't set up Storage Locations. As a result, only local directories can be used here. This patch should NOT disable the -vws option btw, so sites that require/are using it will still work properly with this patch. This is to allow for sites on Base Clearcase that do not have Shares or NAS systems to be able to download Snapshots properly. 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-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Should have been more clear with my last post - the examples in question are at the bottom of the page of the link you sent me. 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Edit the jenkins.xml file in the root of the service installation. It has an area for parameters to the JVM. Add -Dmail.debug=true there. 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-14833) Jenkins variables are not expanded in Coverity plugin
Brett Delle Grazie
commented on JENKINS-14833
Jenkins variables are not expanded in Coverity plugin
+1
--strip-path ${WORKSPACE}
or similar is extremely useful when using nodes with differing paths
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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill
commented on JENKINS-16163
NullPointerException when sending post build emails - all triggers appear to be impacted
I modified jenkins.xml as follows and restarted Jenkins.
arguments-Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Dmail.debug=true -jar "%BASE%\jenkins.war" --httpPort=8080/arguments
Here's the debug statements from the jenkins.out.log file:
DEBUG: JavaMail version 1.4.4
DEBUG: successfully loaded resource: /META-INF/javamail.default.providers
DEBUG: Tables of loaded providers
DEBUG: Providers Listed By Class Name: {com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], com.sun.mail.smtp.SMTPTransport=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc], com.sun.mail.imap.IMAPSSLStore=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3SSLStore=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], com.sun.mail.imap.IMAPStore=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3Store=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc]}
DEBUG: Providers Listed By Protocol: {imaps=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], imap=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], smtps=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], pop3=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc], pop3s=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], smtp=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]}
DEBUG: successfully loaded resource: /META-INF/javamail.default.address.map
DEBUG: getProvider() returning javax.mail.ProviderTRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc
DEBUG SMTP: useEhlo true, useAuth false
DEBUG SMTP: trying to connect to host "smtp.hp.com", port 25, isSSL false
DEBUG: JavaMail version 1.4.4
DEBUG: successfully loaded resource: /META-INF/javamail.default.providers
DEBUG: Tables of loaded providers
DEBUG: Providers Listed By Class Name: {com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], com.sun.mail.smtp.SMTPTransport=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc], com.sun.mail.imap.IMAPSSLStore=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3SSLStore=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], com.sun.mail.imap.IMAPStore=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3Store=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc]}
DEBUG: Providers Listed By Protocol: {imaps=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], imap=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], smtps=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], pop3=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc], pop3s=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], smtp=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]}
DEBUG: successfully loaded resource: /META-INF/javamail.default.address.map
DEBUG: getProvider() returning javax.mail.ProviderTRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc
DEBUG SMTP: useEhlo true, useAuth false
DEBUG SMTP: trying to connect to host "smtp.hp.com", port 25, isSSL false
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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted It looks like it never connects. Do you need to setup secure connection? 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-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token
Trevor A commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but no clear way to pass API token @Pei-Tang, @Jesper: For what it's worth, we found that the Windows service install wasn't broken per se but that it failed if the service already existed. We were able to log onto one of our Windows build servers, manually uninstall the service, rename or delete jenkins-slave.exe and jenkins-slave.xml, reboot the system, and then successfully reinstall the service by logging in as an admin, downloading the .jnlp file, and using the Java WebStart to install it. However, even after reinstalling the service the build slave was unable to register with master server because the service was trying to retrieve the the .jnlp from the master each time it started and was being denied. I have not tried manually running the .jnlp file outside the browser and installing as suggested 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
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Can you try telneting to your smtp server on port 25 and see if you get an EHLO or any response at all? 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-16293) Perforce plugin to check for changes without sync
Uma shankar created JENKINS-16293 Perforce plugin to check for changes without sync Issue Type: Task Affects Versions: current Assignee: Rob Petti Components: perforce Created: 09/Jan/13 6:52 PM Description: I am not sure, what feature i am expecting is already available or not. But here are my request: I want perforce plugin to work in such a way that, if i provide a View map (Ex: //project/main/...), and enable build trigger as "Poll SCM", it should check for any changes but not sync the files from perforce to workspace. If changes found run the script which is provided to run bat/shell. The main question is i never want sync code but want to trigger build if any changes in given depot. It is urgent requirement. I would be thankful if anyone can respond ASAP. Thank you. Due Date: 14/Jan/13 12:00 AM Environment: Windows, Linux Fix Versions: current Project: Jenkins Priority: Major Reporter: Uma shankar 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-6123) View Storage Location should be a required parameter
Steve Davidson commented on JENKINS-6123 View Storage Location should be a required parameter Additional discussion on JENKINS-16234 on this topic, including links to Clearcase documentation. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Niklaus Giger commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space It is looking good. Running since January 06, 00:37 AM without any PermGen errors. It seems that this nasty problem has been fixed for me! I think you are entitled now to collect your 100$ on freedomsponsors. Thanks a lot for your help! 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted It took a while to get the telnet client installed, then it wouldn't connect. A coworker suggested we temporarily disable the anti-virus protection and it opened up. Jenkins was then able to send emails. Hopefully we'll be able to configure our anti-virus software to allow access to port 25 of the smtp server. 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill
edited a comment on JENKINS-16163
NullPointerException when sending post build emails - all triggers appear to be impacted
I modified jenkins.xml as follows and restarted Jenkins.
arguments-Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Dmail.debug=true -jar "%BASE%\jenkins.war" --httpPort=8080/arguments
Here's the debug statements from the jenkins.out.log file:
DEBUG: JavaMail version 1.4.4
DEBUG: successfully loaded resource: /META-INF/javamail.default.providers
DEBUG: Tables of loaded providers
DEBUG: Providers Listed By Class Name: {com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], com.sun.mail.smtp.SMTPTransport=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc], com.sun.mail.imap.IMAPSSLStore=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3SSLStore=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], com.sun.mail.imap.IMAPStore=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3Store=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc]}
DEBUG: Providers Listed By Protocol: {imaps=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], imap=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], smtps=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], pop3=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc], pop3s=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], smtp=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]}
DEBUG: successfully loaded resource: /META-INF/javamail.default.address.map
DEBUG: getProvider() returning javax.mail.ProviderTRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc
DEBUG SMTP: useEhlo true, useAuth false
DEBUG SMTP: trying to connect to host "smtp.myreallybigcompany.com", port 25, isSSL false
DEBUG: JavaMail version 1.4.4
DEBUG: successfully loaded resource: /META-INF/javamail.default.providers
DEBUG: Tables of loaded providers
DEBUG: Providers Listed By Class Name: {com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], com.sun.mail.smtp.SMTPTransport=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc], com.sun.mail.imap.IMAPSSLStore=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3SSLStore=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], com.sun.mail.imap.IMAPStore=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3Store=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc]}
DEBUG: Providers Listed By Protocol: {imaps=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun Microsystems, Inc], imap=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], smtps=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun Microsystems, Inc], pop3=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc], pop3s=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun Microsystems, Inc], smtp=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]}
DEBUG: successfully loaded resource: /META-INF/javamail.default.address.map
DEBUG: getProvider() returning javax.mail.ProviderTRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc
DEBUG SMTP: useEhlo true, useAuth false
DEBUG SMTP: trying to connect to host "smtp.myreallybigcompany.com", port 25, isSSL false
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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted So is this not an issue for you then? 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Hopefully not. We're having some unrelated network issues at the moment, so I have yet to determine if we'll be able to make our setting stick (assuming we're allowed to do it). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted I don't know how previous versions of the plugin were able to send email if the virus scanner is blocking the port. That is not something I can really work around. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford resolved JENKINS-13617 as Fixed 64-bit java.lang.OutOfMemoryError: PermGen space Change By: Johno Crawford (09/Jan/13 8:13 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
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford closed JENKINS-13617 as Fixed 64-bit java.lang.OutOfMemoryError: PermGen space Change By: Johno Crawford (09/Jan/13 8:13 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
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I don't mind at all, here it is https://github.com/johnou/ivy-plugin/commit/16f68088e6c3c0485a3f056c08ece1610e6f3cd3.patch . I am using master too. I assume there must be something wrong with your development environment, you could try moving your local ~/.m2/repository folder and then "mvn compile". I have found that sometimes I run into conflicts because of artifacts which were downloaded from another repo. 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-5682) when keeping past reports, project should link to latest build report
mcrooney commented on JENKINS-5682 when keeping past reports, project should link to latest build report Hi Kyle. Anyone is welcome to work on this, just create a pull request with a test and I'll merge it in and perform a new release. 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Me too 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted @Jim Yanko have you had a chance to enable debug mode? Your failure was slightly different from Richard's I believe. 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-14550) Checksum mismatch while updating with Subversion Plugin 1.42
Ben Hines commented on JENKINS-14550 Checksum mismatch while updating with Subversion Plugin 1.42 this still occurs with 1.44 /jenkins 1.498 btw. Very frustrating 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-6130) Update manager should collect plug-ins to install in a set
evernat resolved JENKINS-6130 as Duplicate Update manager should collect plug-ins to install in a set duplicates JENKINS-10569 Change By: evernat (09/Jan/13 10:46 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
[JIRA] (JENKINS-8334) maven-plugin insists on Surefire to run tests
John Bito commented on JENKINS-8334 maven-plugin insists on Surefire to run tests I like kutzi's pull request. 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74
commented on JENKINS-15779
Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
We have resolved compilation problem. I don't know why I'm the only one who got this, but It seems to be a Java bug:
http://stackoverflow.com/questions/4829576/javac-error-inconvertible-types-with-generics
So if the IvyBuild.java is changed in this way it compiles OK:
diff --git a/src/main/java/hudson/ivy/IvyBuild.java b/src/main/java/hudson/ivy/IvyBuild.java
index fbe04d6..d98fb80 100644
a/src/main/java/hudson/ivy/IvyBuild.java
+++ b/src/main/java/hudson/ivy/IvyBuild.java
@@ -498,8 +498,13 @@ public class IvyBuild extends AbstractIvyBuildIvyModule, IvyBuild {
}
public void buildEnvVars(AbstractBuild?, ? build, EnvVars env) {
-env.put("IVY_MODULE_NAME", ((IvyModule) build.getParent()).getModuleName().name);
-env.put("IVY_MODULE_ORGANISATION", ((IvyModule) build.getParent()).getModuleName().organisation);
+//env.put("IVY_MODULE_NAME", ((IvyModule) build.getParent()).getModuleName().name);
+//env.put("IVY_MODULE_ORGANISATION", ((IvyModule) build.getParent()).getModuleName().organisation);
+Object o = build.getParent();
+ModuleName n = ( ( IvyModule ) o ).getModuleName() ;
+env.put("IVY_MODULE_NAME", n.name);
+env.put("IVY_MODULE_ORGANISATION", n.organisation);
+
}
}
}
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-16293) Perforce plugin to check for changes without sync
Rob Petti commented on JENKINS-16293 Perforce plugin to check for changes without sync This option already exists. It is called "Disable Syncing Only". 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-16293) Perforce plugin to check for changes without sync
Rob Petti resolved JENKINS-16293 as Not A Defect Perforce plugin to check for changes without sync Change By: Rob Petti (10/Jan/13 1:20 AM) Status: Open Resolved 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
[JIRA] (JENKINS-11102) Give the possibility to monitor all branches as Git plugin
Marc Swingler commented on JENKINS-11102 Give the possibility to monitor all branches as Git plugin @Jesse Nice post on stack. You hit the nail on the head there per build history mirroring the VCS tree. An API like you describe would be ideal. Hopefully it's an item we can bring to the attention of Kohsuke and the community. That being said, I don't think feature clash should prevent the Mercurial plugin from moving forward in the meantime. E.g. It's fairly intuitive to avoid use of 'discard all but latest stable' if you're building from multiple branches. In a similar vein I need to avoid certain features or other plugins when using the Maven Release Plugin-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
[JIRA] (JENKINS-16237) Extended email plugin no longer sends messages on latest
Slide-O-Mix commented on JENKINS-16237 Extended email plugin no longer sends messages on latest Can you try setting the following property and see if the email goes out? mail.smtp.quitwait=false 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-15655) Bad $PATH variable on AIX
Thorsten Löber commented on JENKINS-15655 Bad $PATH variable on AIX looks simmilar to JENKINS-15061 ? 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-15655) Bad $PATH variable on AIX
Thorsten Löber edited a comment on JENKINS-15655 Bad $PATH variable on AIX That's also a major issue for us - it's painful and error prone to define the whole path in the nodes' setting 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-12934) Subversion Tag plugin tries to copy from invalid source path
Harry Cool commented on JENKINS-12934 Subversion Tag plugin tries to copy from invalid source path Hi Friends, Is anyone able to fix this issue? Even I'm getting the same error. I am not able to perform SVN tagging after the successful build. Here is what I am getting in the output. BUILD SUCCESSFUL Remote Module Location: http://10.10.10.10/MY-SVN-REP/Project1/trunk/ENVS@203. Tag Base URL: http://10.10.10.10/MY-SVN-REP/Project2/tags/TEST_DEPLOYMENT. There was no old tag at http://10.10.10.10/MY-SVN-REP/Project2/tags/TEST_DEPLOYMENT. Subversion copy failed. svn: File not found: revision 203, path '/Project1/trunk/ENVS/Project1/trunk/ENVS' svn: '/MY-SVN-REP/!svn/bc/203/Project1/trunk/ENVS' path not found: 404 Not Found (http://10.10.10.10) Build step 'Perform Subversion tagging on successful build' marked build as failure Finished: SUCCESS The error message from the plugin shows that apparently it tries to copy from an invalid source path (Invalid Remote module location) Can anyone share some light on 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
