[JIRA] [email-ext] (JENKINS-21228) add shell variable into pre-send groovy script context
Mike Dubman
commented on JENKINS-21228
add shell variable into pre-send groovy script context
What do you mean it accepts "string script" only
I cannot specify the /path/to/external/script.groovy in the "pre-send textfield" as it expects groovy script to feed into evaluate()
So, current workaround is to create GroovyShell object and call its "evaluate(new File("/path/to/external/script.groovy"))
But, this work-around leads to a lot of code-copy (the external groovy script will not inherit msg,cancel, build objects which should be populated into new groovyshell object).
I would need more information as to why you can't just the attach build log feature to attach the log from the build slave.
I did not find a way to extract slave console log from file system and use wget. When email-ext is configured to run from parent, there is no easy way to fetch console logs from slave (AFAIK)
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] [mercurial] (JENKINS-21266) Unable to clone repository if Multi SCMs and Multi Configuration Project
Pietro Braghieri created JENKINS-21266 Unable to clone repository if Multi SCMs and Multi Configuration Project Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: mercurial Created: 08/Jan/14 8:39 AM Description: I created a multi configuration project which clones two mercurial repositories (I use the MultiSCM plugin).The first cloning step works fine but in the second (when the slave is invoked) the cloning of the second repository fails because the mercurial plugin invokes hg with the revision tag of the first repository. Project: Jenkins Priority: Blocker Reporter: Pietro Braghieri 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] [translation] (JENKINS-18612) Confusing behavior for not logged users (403 Forbidden)
Adam Gabryś closed JENKINS-18612 as Fixed Confusing behavior for not logged users (403 Forbidden) Fixed in 1.11. Change By: Adam Gabryś (08/Jan/14 8:50 AM) Status: Open Closed 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] [next-executions] (JENKINS-21267) show time _span_ until next execution
Michael Keppler created JENKINS-21267 show time _span_ until next execution Issue Type: New Feature Assignee: Unassigned Components: next-executions Created: 08/Jan/14 9:35 AM Description: I use the next executions to estimate whether I need to run a manually triggered build after infrastructure changes for a job, which is triggered all 4 hours anyway (to avoid it running on multiple nodes nearly at the same time). (I know there are all kinds of plugins and settings to avoid concurrent builds, but we cannot use them for this job, as it actually makes sense to have concurrent builds, if people really changed things in between). Currently I have to compare the next execution time against the reported page creation time to see how far away the next job is (which gets even more complicated due to the server being in a timezone 4.5 hours away). I therefore suggest to enhance the output to something like job name next starting time (in time away) e.g. regular maintenance 18:05:00(in 01:20:34) Feel free to leave seconds away, or to only create such output for jobs in the next n hours. Or make it just a tooltip on the absolute time, if you feel that the space might not be sufficient. Project: Jenkins Priority: Minor Reporter: Michael Keppler 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-18445) Local Integration Point
sego commented on JENKINS-18445 Local Integration Point Ok, thank you very much for the clarification. It might be helpful to put that information on the wiki page. But I'm leaving that decision to you as you would probably be the one who would have to maintain it... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-21268) No build.lxml is created when warnings plugin is used in combination with deactivated maven plugin
Marko Stefanovic created JENKINS-21268 No build.lxml is created when warnings plugin is used in combination with deactivated maven plugin Issue Type: Bug Assignee: Ulli Hafner Components: maven, warnings Created: 08/Jan/14 10:06 AM Description: The Warnings Plug-in doesn't seem to work correctly if the maven plugin is deactivated. In our case it prevented the creation of the build.xml at the end of a build. As long as Jenkins is running, all builds and their history are shown correctly, but after a restart, Jenkins can't get the necessary informations to build up the history due to missing build.xml. This results in a faulty build history (no past builds are shown). To reproduce, follow these steps: 1. Deactivate the maven plugin 2. Make sure you have the Warnings and msbuild plugin installed 3. Create a job which contains a msbuild step (we used msbuild 4.0) 4. Create a post buildstep "Scan for compiler warnings" and use "Scan console log" with "msbulid parser" In our case, with above setup, no build.xml was created if: maven was deactivated AND warnings was turned on We tested that in all other combinations a build.xml was created to make sure that the problem lies within the Warnings plugin and not maven. Environment: Windows 7, Jenkins as Service, Project: Jenkins Priority: Major Reporter: Marko Stefanovic 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-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Marko Stefanovic updated JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin Change By: Marko Stefanovic (08/Jan/14 10:07 AM) Summary: Nobuild. lxml xml iscreatedwhenwarningspluginisusedincombinationwithdeactivatedmavenplugin 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-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Marko Stefanovic updated JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin Change By: Marko Stefanovic (08/Jan/14 10:17 AM) Description: TheWarningsPlug-indoesntseemtoworkcorrectlyifthemavenpluginisdeactivated.Inourcaseitpreventedthecreationofthebuild.xmlattheendofabuild.AslongasJenkinsisrunning,allbuildsandtheirhistoryareshowncorrectly,butafterarestart,Jenkinscantgetthenecessaryinformationstobuildupthehistoryduetomissingbuild.xml.Thisresultsinafaultybuildhistory(nopastbuildsareshown).Toreproduce,followthesesteps:1.Deactivatethemavenplugin2.MakesureyouhavetheWarningsandmsbuildplugininstalled3.Createajobwhichcontainsamsbuildstep(weusedmsbuild4.0)4.CreateapostbuildstepScanforcompilerwarningsanduseScanconsolelogwithmsbulidparserInourcase,withabovesetup,nobuild.xmlwascreatedif:-mavenwasdeactivatedANDwarningswasturnedon Wetestedthatinall In othercombinations (mavenon/off,warningson/off) abuild.xmlwascreated tomakesurethat hence theproblemlieswithintheWarningspluginandnotmaven. 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-12951) Freestyle job 'Invoke Maven 3' build step can't find maven home for Maven installation installed from Apache Archives
evernat commented on JENKINS-12951 Freestyle job Invoke Maven 3 build step cant find maven home for Maven installation installed from Apache Archives Is it reproduced with a recent Jenkins version? 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-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
pedro reis commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I think I'm having the same issue: "Started by user anonymous Building remotely on Windows_vs100_slave in workspace c:\h\workspace\mxfSPEEDRAIL_GIT Fetching changes from 2 remote Git repositories Fetching upstream changes from ssh://git@host/opt/git/common/mde.git ERROR: Timeout after 10 minutes FATAL: Failed to fetch from ssh://git@host/opt/git/common/mde.git hudson.plugins.git.GitException: Failed to fetch from ssh://git@host/opt/git/common/mde.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1665) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://git@host/opt/git/common/mde.git +refs/heads/master:refs/remotes/origin/master" returned status code -1: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1099) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:69) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:218) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:224) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:229) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) 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.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source)" 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-16737) java.lang.RuntimeException: No author in changeset null
Greg BOUGEARD commented on JENKINS-16737 java.lang.RuntimeException: No author in changeset null Hi, I'm getting a quite similar error : 08/01/2014 10:00:27 Archiving artifacts 08/01/2014 10:00:27 FATAL: No author in changeset 506fc54deb5c89c43450dc60a05415198b0atree 08/01/2014 10:00:27 java.lang.RuntimeException: No author in changeset 506fc54deb5c89c43450dc60a05415198b0atree 08/01/2014 10:00:27 at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:336) 08/01/2014 10:00:27 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:414) 08/01/2014 10:00:27 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:710) 08/01/2014 10:00:27 at hudson.model.Run.execute(Run.java:1702) 08/01/2014 10:00:27 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) 08/01/2014 10:00:27 at hudson.model.ResourceController.execute(ResourceController.java:88) 08/01/2014 10:00:27 at hudson.model.Executor.run(Executor.java:231) I have checked the git-plugin code and I think the id of the commit is not well retrieved. 506fc54deb5c89c43450dc60a05415198b0a is a valid SHA1 but the id retrieved is 506fc54deb5c89c43450dc60a05415198b0atree , so the tree suffix is too much. The issue might be in the parseCommit method or maybe it can be linked to a specific git version (like the issue of maven release plugin with git 1.8.5). I'm using : git 1.7.9.5. Jenkins GIT client plugin 1.6.0 Jenkins GIT plugin 2.0 I'm not sure about the scenario to reproduce this error but there is the git log of the commit : commit 506fc54deb5c89c43450dc60a05415198b0a Author: JENKINS jenk...@xxx.com Date: Wed Jan 8 01:13:06 2014 +0100 release Langs Change-Id: I157faff2efffdb369933958dfb15842f0e9c4ff7 commit f25811f05aeb812bdf4a1c2c50d251f0e088f9f5 Author: JENKINS jenk...@xxx.com Date: Fri Jan 3 01:12:26 2014 +0100 release Langs Change-Id: I82be648aaa25dcbc81c2ace3ac2dea91eba6d425 commit 3be79c86892135e7f0d4a40642cd2710cd7013c2 Author: JENKINS jenk...@xxx.com Date: Fri Dec 27 01:13:28 2013 +0100 release Langs Change-Id: I42fbc4d166161d467602f7b3c6ef6621c9512545 I don't have a Jenkins Plug-in dev ready environment so I can't go further right now. I hope the details I gave could 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 -- 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-18678) Builds disappear some time after renaming job
Marko Stefanovic commented on JENKINS-18678 Builds disappear some time after renaming job @Oleg, Jesse Sorry for off topic posting. I created a new issue. See JENKINS-21268 for further discussion. 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] [dynamic-axis] (JENKINS-21269) Dynamic axis not filtered in build view by the Combination Filter
Alessandro Foresi created JENKINS-21269 Dynamic axis not filtered in build view by the Combination Filter Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: dynamic-axis Created: 08/Jan/14 10:58 AM Description: I've a multi-configuration job where one of the axes is dynamic. The value is taken from a globally-defined variable (term copied from help button). The job has combination filter that excludes one of the values from such dynamic axis. The Combination Filter does work when executing my multi-configuration job. This means the build runs as expected. Anyway, the build view shows all the value of the dynamic axis. I would expect to see the dynamic axis build view not to show the values for which it didn't run. Project: Jenkins Labels: plugin matrix Priority: Minor Reporter: Alessandro Foresi 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-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Ricardo Martins commented on JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ The problem is how to rollback a new installation of jenkins as a service on CentOs. =/ 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] [xcode] (JENKINS-13887) Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build
Esteban Bouza assigned JENKINS-13887 to Esteban Bouza Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build Change By: Esteban Bouza (08/Jan/14 11:46 AM) Assignee: EstebanBouza 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] [warnings] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Ulli Hafner updated JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin Is there an exception or message in the console log? Change By: Ulli Hafner (08/Jan/14 11:56 AM) Priority: Major Minor Component/s: maven 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-21270) Add licenses to jenkins core and plugins
Tom Van Eyck created JENKINS-21270 Add licenses to jenkins core and plugins Issue Type: Improvement Assignee: Alex Earl Components: email-ext, git, git-client, github-api, htmlpublisher, maven, maven2, next-build-number, parameterized-trigger, ruby-runtime, rvm, timestamper, token-macro Created: 08/Jan/14 11:55 AM Description: Hi all, we use Jenkins and quite a few of its plugins in our organization. Due to legal reasons we are required to keep track of which licenses any software we use falls under. Generally this is pretty easy. However, I'd estimate that less than half of the Jenkins core and plugin components that we use has clear license info (e.g. a license file in a github repo or a license mentioned on http://maven-repository.com). Would it be possible to have a look at this? Or is there perhaps an implicit license that applies when no license is specified? The following plugins are ones that I'm having trouble finding a license for: ruby-runtime plugin https://github.com/jenkinsci/ruby-runtime-plugin git plugin https://github.com/jenkinsci/git-plugin email-ext pluginhttps://github.com/jenkinsci/email-ext-plugin rvm plugin https://github.com/jenkinsci/rvm-plugin github api plugin https://github.com/jenkinsci/github-api-plugin git client plugin https://github.com/jenkinsci/git-client-plugin html publisher plugin https://github.com/jenkinsci/htmlpublisher-plugin maven project pluginhttps://github.com/jenkinsci/maven-plugin/tree/master multijob plugin https://github.com/jenkinsci/tikal-multijob-plugin parameterized trigger pluginhttps://github.com/jenkinsci/parameterized-trigger-plugin timestamper plugin https://github.com/jenkinsci/timestamper-plugin token macro plugin https://github.com/jenkinsci/token-macro-plugin What would be the correct way to go about collecting license information for these? I've opened a few pull requests on github with licensing info for these, but was told that writing a JIRA ticket like this might yield better results. Many thanks, Tom Project: Jenkins Priority: Major Reporter: Tom Van Eyck 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] [github-oauth] (JENKINS-20845) Github Authorization Settings, users in Participant in Organization not given READ
Leandro Lucarella commented on JENKINS-20845 Github Authorization Settings, users in Participant in Organization not given READ Vote it! BTW, for me this is a blocker. Is there any workaround besides manually setting everybody as admins? For me adding permission to any random user that authenticates to jenkins using github is not an option. 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-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Ondrej Rafaj commented on JENKINS-21057 Cannot checkout git repository with submodules: FATAL: No remotes found! I have created an additional shell build step with "git submodule update --init --recursive" ... of course I have disabled the sumodule section completely. 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-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Ondrej Rafaj
updated JENKINS-21057
Cannot checkout git repository with submodules: FATAL: No remotes found!
Change By:
Ondrej Rafaj
(08/Jan/14 12:02 PM)
Description:
h5.Stepstoreproduce#Createafree-styleproject.#SetGitRepositoryURL.Therepositoryspecifiedshouldusesubmodules.#InAdditionalBehaviours,addAdvancedsub-modulesbehavioursandcheckRecursivelyupdatesubmodules.#Buildit.h5.ExpectedresultWorkspaceshouldhavegitworkingtreeandsubmodules.h5.Actualconsolelog{code}CloningtheremoteGitrepositoryCloningrepositorygit://***/*.gitFetchingupstreamchangesfromgit://***/*.gitFetchingupstreamchangesfromgit://***/*.gitCheckingoutRevision0123456789abcdef0123456789abcdef01234567(origin/master)FATAL:Noremotesfound!hudson.plugins.git.GitException:Noremotesfound! atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.getDefaultRemote(CliGitAPIImpl.java:702) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.setupSubmoduleUrls(CliGitAPIImpl.java:863) athudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:69) athudson.plugins.git.GitSCM.checkout(GitSCM.java:882) athudson.model.AbstractProject.checkout(AbstractProject.java:1256) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) athudson.model.Run.execute(Run.java:1502) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:236){code}h5.Actual.git/config{code}[core] repositoryformatversion=0 filemode=false logallrefupdates=true{code}Thereisno[remoteorigin]nor[submodulesubmodule-name]sections.h5.WorkaroundOneofthefollowings:*Downgradegitpluginto1.5*DonotcheckRecursivelyupdatesubmodules*Donotcheckoutgitrepositorywithsubmodules
*Createashellbuildstepwith:gitsubmoduleupdate--init--recursive
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] [warnings] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Marko Stefanovic updated JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin Change By: Marko Stefanovic (08/Jan/14 12:08 PM) Attachment: no_buildXML_jenkins_err.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 -- 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] [warnings] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Marko Stefanovic commented on JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin @Ulli: Yes, there is in fact an exception. I attached the significant part of the error log. Note: in the attachment the build failed but since Warnings Plugin was configured to always parse it was triggered (and no build.xml was created). If Warnings Plugin is configured not to parse on error the build.xml is correctly created (Warnings Plugin isn't triggered). 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-21271) Perforce plugin does not provide -P option anymore
Peter Schaefer-Hutter created JENKINS-21271 Perforce plugin does not provide -P option anymore Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 08/Jan/14 12:45 PM Description: All of a sudden, some builds start failing. Closer inspection showed, that the perforce plugin stopped providing the "-P" option to p4.exe. I can't explain why. Going back to 1.3.24 didn't help (but i'm unsure if the roll-back performed correctly). Updating Jenkins to 1.546 didn't help either. The log of a successful (old) build shows: [EnvInject] - Loading node environment variables. Building on Slave WIN7 in workspace c:\jenkins\workspace\DEMO Deleting project workspace... done Using remote perforce client: Jenkins_DEMO--216826706 [DEMO] $ "c:\program files\perforce\p4" -P workspace -o Jenkins_DEMO--216826706 Note: .repository directory in workspace (if exists) is skipped during clean. Wiping workspace... Wiped workspace. Clean complete, took 5 ms [...] A failed (new) build shows: [EnvInject] - Loading node environment variables. Building on Slave WIN7 in workspace c:\jenkins\workspace\DEMO Deleting project workspace... done Using remote perforce client: Jenkins_DEMO--216826706 [DEMO] $ "c:\program files\perforce\p4.exe" workspace -o Jenkins_DEMO--216826706 Caught exception communicating with perforce. No output for: c:\program files\perforce\p4.exe workspace -o Jenkins_DEMO--216826706 com.tek42.perforce.PerforceException: No output for: c:\program files\perforce\p4.exe workspace -o Jenkins_DEMO--216826706 at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:408) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:301) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1545) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1506) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:843) at hudson.model.AbstractProject.checkout(AbstractProject.java:1415) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ERROR: Unable to communicate with perforce. No output for: c:\program files\perforce\p4.exe workspace -o Jenkins_DEMO--216826706 [...] Project: Jenkins Labels: perforce plugin Priority: Major Reporter: Peter Schaefer-Hutter 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-21270) Add licenses to jenkins core and plugins
Nicolas De Loof commented on JENKINS-21270 Add licenses to jenkins core and plugins license should be set in maven pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16737) java.lang.RuntimeException: No author in changeset null
Nicolas De Loof commented on JENKINS-16737 java.lang.RuntimeException: No author in changeset null raw log parsing is fragile, I'd like to rely on --format to make it more predictible 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] [promoted-builds] (JENKINS-20912) promoted-builds plugin NullPointerException on getParameterValues
Per Arnold Blaasmo commented on JENKINS-20912 promoted-builds plugin NullPointerException on getParameterValues I also downgraded to 2.13 and it solved our problems. 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-21272) Gerrit SSH key not working
puvanarajan mohanaram created JENKINS-21272 Gerrit SSH key not working Issue Type: Bug Assignee: rsandell Attachments: q.png Components: gerrit-trigger Created: 08/Jan/14 1:01 PM Description: I was assign the ssk file. /home/puvanarajan/.ssh/id_rsa But it is say "/home/puvanarajan/.ssh/id_rsa" does not exist. Project: Jenkins Priority: Major Reporter: puvanarajan mohanaram 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] [create-fingerprint] (JENKINS-21273) New job creation error
puvanarajan mohanaram created JENKINS-21273 New job creation error Issue Type: Bug Assignee: Unassigned Attachments: 2.png Components: create-fingerprint Created: 08/Jan/14 1:03 PM Description: When i create the new job it will display the error Project: Jenkins Priority: Major Reporter: puvanarajan mohanaram 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-21274) CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled
Timo Kamarainen created JENKINS-21274 CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: copyartifact Created: 08/Jan/14 1:16 PM Description: CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled. If Maven plugin is disabled the Copy Artifacts build step is not available to select when configuring builds. Maven plugin dependency is marked as 'optional' in Copy Artifact Plugin info, and version 1.27 used to work with disabled Maven plugin, so something has gone wrong in the 1.28 update. Project: Jenkins Labels: copyartifact maven Priority: Major Reporter: Timo Kamarainen 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-21275) hudson.plugins.git.GitException: Error performing git command ... Caused by: java.lang.NoSuchFieldError: MINUTES
András Szilárd created JENKINS-21275 hudson.plugins.git.GitException: Error performing git command ... Caused by: java.lang.NoSuchFieldError: MINUTES Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 08/Jan/14 1:33 PM Description: Hi! We have upgraded the git plugins and are facing an issue. Git-client-plugin is not compatible with Java 1.5 at the moment, since TimeUnit.MINUTES is available in Java 1.6+ only. Could you fix the plugin to be still compatible with Java 1.5? Affected source file: CliGitAPIImpl.java Error message, including stack trace: Fetching upstream changes from /directory/of/the/git/repo ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Error performing git command at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1108) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:69) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:218) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:350) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) 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:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NoSuchFieldError: MINUTES at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1095) ... 15 more ERROR: null Git upgrade was necessary for an other issue. "From" versions worked for us. Jenkins GIT client plugin 1.1.1 - 1.6.0 Jenkins GIT plugin 1.2.0 - 2.0 Git server plugin 1.1 - 1.2 Thanks! Project: Jenkins Labels: plugin exception git regression Priority: Major Reporter: András Szilárd 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-16737) java.lang.RuntimeException: No author in changeset null
Greg BOUGEARD
commented on JENKINS-16737
java.lang.RuntimeException: No author in changeset null
I'm using a gitjs shell script like this :
#!/bin/sh
TAG_START=$1
TAG_END=$2
function escape_chars {
sed -r -e 's/(["\\])/\\\1/g' -e 's/\t/ /g'
}
function format {
sha=$(git log -n1 --pretty=format:%h $1 | escape_chars)
message=$(git log -n1 --pretty=format:%s $1 | escape_chars)
author=$(git log -n1 --pretty=format:'%aN' $1 | escape_chars)
commit=$(git log -n1 --pretty=format:%H $1 | escape_chars)
date=$(git log -n1 --pretty=format:%ai $1 | escape_chars)
echo "{\"sha\":\"$sha\",\"message\":\"$message\",\"author\":\"$author\",\"commit\":\"$commit\",\"date\":\"$date\"},"
}
#echo "git log ${TAG_START}..${TAG_END}"
for hash in $(git rev-list ${TAG_START}..${TAG_END})
do
format $hash
done
maybe it can inspire you
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] [groovy-postbuild] (JENKINS-21276) Groovy postbuild interrupts postbuild execution in a template if the job has failed.
Antti Haijanen created JENKINS-21276 Groovy postbuild interrupts postbuild execution in a template if the job has failed. Issue Type: Bug Assignee: wolfs Components: groovy-postbuild Created: 08/Jan/14 1:52 PM Description: I'm using "Use publishers from another projects" and I have several post build steps in a template. If the build fails, post build steps in the template are executed until Groovy postbuild has finished and then I get: Build step 'Use publishers from another project' marked build as failure After that it will continue as normal running the remaining post build steps in the job, but discards rest of the post build steps in my template. If I remove my Groovy script from my template or the job succeeds, everything works OK. Same thing if I don't use a template. Project: Jenkins Priority: Major Reporter: Antti Haijanen 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] [www] (JENKINS-263) Preserve build order of downstream projects
Jeremy Pope reopened JENKINS-263 Preserve build order of downstream projects I am experiencing this issue having upgraded from 1.509.3 to 1.509.4. The order of jobs executed does not seem to consistent from execution to execution. Change By: Jeremy Pope (08/Jan/14 1:59 PM) Resolution: Postponed 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] [warnings] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Ulli Hafner commented on JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin Which versions are you using? I just tried with Jenkins 1.546 and a snapshot of the warnings plug-in and that works: Gestartet durch Benutzer anonymous Baue auf Master in workspace /Users/hafner/Development/jenkins/jobs/JENKINS-21268/workspace [WARNINGS] Parsing warnings in console log with parser MSBuild Finished: 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 -- 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-21277) Job cannot be built with parameters
Tamas Papp created JENKINS-21277 Job cannot be built with parameters Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 08/Jan/14 2:10 PM Description: FATAL: Null value not allowed as an environment variable: GIT_COMMIT java.lang.IllegalArgumentException: Null value not allowed as an environment variable: GIT_COMMIT at hudson.EnvVars.put(EnvVars.java:356) at hudson.EnvVars.put(EnvVars.java:74) at hudson.plugins.git.GitSCM.buildEnvVars(GitSCM.java:983) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:919) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:865) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) The jobs works if it's modified to normal and build with "Build now". We encountered the same behaviour with Git plugin 2.0 and not parameterized builds. Environment: Git plugin 2.0.1 git-client 1.6 Jenkins 1.5.45 v.1.5.46 Project: Jenkins Priority: Blocker Reporter: Tamas Papp 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-21275) hudson.plugins.git.GitException: Error performing git command ... Caused by: java.lang.NoSuchFieldError: MINUTES
Mark Waite commented on JENKINS-21275 hudson.plugins.git.GitException: Error performing git command ... Caused by: java.lang.NoSuchFieldError: MINUTES I recommend this not be fixed. https://wiki.jenkins-ci.org/display/JENKINS/Java+5+Compatibility states that as of Jenkins 1.520, Java 6 or later is required at runtime. Fixing this now will still only give the person who reported the bug a limited time before they will be unable to use Java 5. Strictly speaking, the git-client-plugin pom.xml declares that git-client-plugin needs Jenkins 1.480 as its minimum version, so there is a reasonable argument that git-client should support Java 5. It does not (as noted by this bug report). Modifying it to support Java 5 seems like wasted effort because the rest of the infrastructure does not support Java 5 as of Jenkins 1.520. I'm not the maintainer of the plugin, just an interested person, but I think that the maintainer has plenty of things to do on the plugin without attempting to make it compatible with a Java 5 runtime. 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] [warnings] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Marko Stefanovic updated JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin Change By: Marko Stefanovic (08/Jan/14 2:16 PM) Environment: Windows7,Jenkins 1.546and1.532,Jenkinsstarted asService , 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] [warnings] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Marko Stefanovic commented on JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin @Ulli: I updated "Details/Environment" with the jenkins versions i used. I get the same console log as you in both case (correct and faulty behaviour). In the faulty case the exception is logged in jenkins_err.log. The bug becomes only noticable to the user after Jenkins is restarted. Alternatively you can just look in the "LastSuccessfulBuild" folder for build.xml. It should be missing. 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-pipeline] (JENKINS-21181) Build pipeline creating stack trace after logging on as non-admin user
unguiculus commented on JENKINS-21181 Build pipeline creating stack trace after logging on as non-admin user I got this exception after upgrading from Jenkins 1.539 to 1.546 with build pipeline 1.4.2. Downgrading to 1.4.1 fixed the problem. 1.4.2 did work with Jenkins 1.539. 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] [warnings] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Marko Stefanovic updated JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin Change By: Marko Stefanovic (08/Jan/14 2:35 PM) Attachment: no_buildXml_InstalledPlugins.jpg Attachment: no_buildXml_minExample.jpg 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] [testng] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests
Gavin Gray commented on JENKINS-20985 TestNG plugin should has a possibility to use thresholds for failed tests This would be pretty useful for our company. If nobody picks it up, would it help if we took a stab? 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] [warnings] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Marko Stefanovic updated JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin Change By: Marko Stefanovic (08/Jan/14 2:40 PM) Description: TheWarningsPlug-indoesntseemtoworkcorrectlyifthemavenpluginisdeactivated.Inourcaseitpreventedthecreationofthebuild.xmlattheendofabuild.AslongasJenkinsisrunning,allbuildsandtheirhistoryareshowncorrectly,butafterarestart,Jenkinscantgetthenecessaryinformationstobuildupthehistoryduetomissingbuild.xml.Thisresultsinafaultybuildhistory(nopastbuildsareshown).Toreproduce,followthesesteps:1.Deactivatethemavenplugin2.MakesureyouhavetheWarningsandmsbuildplugininstalled3.Createajobwhichcontainsamsbuildstep(weusedmsbuild4.0)4.CreateapostbuildstepScanforcompilerwarningsanduseScanconsolelogwithmsbulidparserInourcase,withabovesetup,nobuild.xmlwascreatedif:-mavenwasdeactivatedANDwarningswasturnedonInothercombinations(mavenon/off,warningson/off)abuild.xmlwascreatedhencetheproblemlieswithintheWarningspluginandnotmaven. InAttachmentyoufindaminimalexample(no_buildXml_minExample.jpg)whereyoucanreproducethebugbyturningmavenon/off.IntheexampleyoucanseethatBuild#2ismissing-thiswasdonewithdeactivatedmaven.no_buildXml_plugins.jpgshowsourinstalledJenkinspluginsincasethereareotherunknownsideeffects. 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-21277) Job cannot be built with parameters
Tamas Papp commented on JENKINS-21277 Job cannot be built with parameters Actually there is an ugly workaround: Copy job parameterized to non-parameterized (it starts working) then reconfigure the new job to parameterized and still it works... 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-21275) hudson.plugins.git.GitException: Error performing git command ... Caused by: java.lang.NoSuchFieldError: MINUTES
Mark Waite closed JENKINS-21275 as Wont Fix hudson.plugins.git.GitException: Error performing git command ... Caused by: java.lang.NoSuchFieldError: MINUTES No further work needed on this bug. Won't be fixed. Change By: Mark Waite (08/Jan/14 2:57 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] [git-client] (JENKINS-21275) hudson.plugins.git.GitException: Error performing git command ... Caused by: java.lang.NoSuchFieldError: MINUTES
Mark Waite resolved JENKINS-21275 as Wont Fix hudson.plugins.git.GitException: Error performing git command ... Caused by: java.lang.NoSuchFieldError: MINUTES I confirmed with Nicolas De Loof that this bug won't be fixed. It is a valid bug report for users of Jenkins 1.480 through 1.519, but is not worth the effort to fix when the rest of the Jenkins community has already accepted the requirement for a Java 6 runtime. Change By: Mark Waite (08/Jan/14 2:57 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] [perforce] (JENKINS-21271) Perforce plugin does not provide -P option anymore
Peter Schaefer-Hutter commented on JENKINS-21271 Perforce plugin does not provide -P option anymore Update: I was able to trace-down the issue to the EnvInject Plugin. Disabling this plugin brings back the "-P" options. Obviously, the EnvInject Plugin clears the environment, so that the line "getEnv().getPassword()" in the perforce plugin source code returns an empty string. 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-21271) Perforce plugin does not provide -P option anymore
Peter Schaefer-Hutter resolved JENKINS-21271 as Not A Defect Perforce plugin does not provide -P option anymore Traced down the issue to the EnvInject plugin which seems to clobber the environment entries set by the perforce plugin. Change By: Peter Schaefer-Hutter (08/Jan/14 3:50 PM) Status: Open Resolved Fix Version/s: current 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] [xunit] (JENKINS-21278) java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)
James Green created JENKINS-21278 java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102) Issue Type: Bug Assignee: Gregory Boissinot Components: xunit Created: 08/Jan/14 3:44 PM Description: Following your fix to JENKINS-21094 I now get another exception: xUnit INFO - Starting to record. ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102) at org.jenkinsci.plugins.xunit.XUnitProcessor.performXUnit(XUnitProcessor.java:54) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:88) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1030) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Finished: FAILURE Project: Jenkins Priority: Major Reporter: James Green 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-21271) Perforce plugin does not provide -P option anymore
Peter Schaefer-Hutter closed JENKINS-21271 as Not A Defect Perforce plugin does not provide -P option anymore Change By: Peter Schaefer-Hutter (08/Jan/14 3:51 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] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
pedro reis commented on JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem Does the new version of priority plugin only allow priority between 1 and 5? I need at least a 1 to 10! (Old version was 1 to 100...) 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-21228) add shell variable into pre-send groovy script context
Alex Earl commented on JENKINS-21228 add shell variable into pre-send groovy script context You are correct, you can't specify a script that is outside the workspace. In the next version of the plugin you will be able to use managed scripts though, I would prefer to do this for security reasons. The managed scripts are managed through the Jenkins UI yes, but I feel this is more secure. Is the log you are talking about different from the console log of the job? If not, you can access the log directly from the build object. Its an instance of AbstractBuild which has several methods for accessing the build 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 -- 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-21270) Add licenses to jenkins core and plugins
Alex Earl commented on JENKINS-21270 Add licenses to jenkins core and plugins It can be assumed that all code falls within that license then, correct? Can you post an example in this ticket for those of us who are not Maven people? Also, what is the generally liked license for Jenkins? MIT? Apache 2? 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney created JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Issue Type: Bug Assignee: Unassigned Components: maven2 Created: 08/Jan/14 4:07 PM Description: SEVERE: Failed to record SCM polling for hudson.maven.MavenModuleSet@1118b490[testing-parent-trunk] java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING at hudson.EnvVars.put(EnvVars.java:356) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:194) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1235) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1584) at hudson.model.AbstractProject.poll(AbstractProject.java:1493) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:456) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:485) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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:619) Environment: CentoOS 5 Linux 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING There was also an error on the configure page for the build in question. I set a per-node environment variable POM_PACKING=pom on the master node, which fixes the stack trace above, but I'm also seeing this one: javax.servlet.ServletException: java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) 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:91) 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
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney edited a comment on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING There was also an error on the configure page for the build in question. I set a per-node environment variable POM_PACKING=pom on the master node, which fixes the stack trace above, but now I'm seeing this one instead: javax.servlet.ServletException: java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) 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:91) 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
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING The build of this project blows up too: Started by user Tony Sweeney [EnvInject] - Loading node environment variables. Building remotely on hudson3 in workspace S:\Hudson\workspace\auth-api-trunk FATAL: Null value not allowed as an environment variable: POM_PACKAGING java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING at hudson.EnvVars.put(EnvVars.java:356) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:194) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney updated JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING I had to back out the plugin upgrade, it broke too many of my builds. Change By: Tony Sweeney (08/Jan/14 4:48 PM) Priority: Major Critical 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] [mercurial] (JENKINS-21266) Unable to clone repository if Multi SCMs and Multi Configuration Project
Jesse Glick updated JENKINS-21266 Unable to clone repository if Multi SCMs and Multi Configuration Project Unfortunately the Multiple SCMs plugin has a lot of problems. Would take some investigation to see where the bug really lies here. Change By: Jesse Glick (08/Jan/14 4:55 PM) Component/s: multiple-scms 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] [thinBackup] (JENKINS-21262) Allow Restore of Individual Jenkins Job Configs
Thomas Fürer updated JENKINS-21262 Allow Restore of Individual Jenkins Job Configs thanks Stan, I also have think about this feature, and it will be part of the next big major release thinbackup2.x. stay tuned, I'm still working on it but of course it will take some time to release it. Change By: Thomas Fürer (08/Jan/14 5:28 PM) Issue Type: Bug NewFeature 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
Nicolas De Loof updated JENKINS-20502 Cannot find any revision to build on clean workspace Change By: Nicolas De Loof (08/Jan/14 5:29 PM) Component/s: git Component/s: ghprb 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
Nicolas De Loof resolved JENKINS-20502 as Fixed Cannot find any revision to build on clean workspace Change By: Nicolas De Loof (08/Jan/14 5:29 PM) Status: Open Resolved Assignee: HonzaBrázdil NicolasDeLoof 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-20502) Cannot find any revision to build on clean workspace
Simon Lynen commented on JENKINS-20502 Cannot find any revision to build on clean workspace Nicolas, this is great! Thanks a lot for fixing 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] [android-emulator] (JENKINS-21280) Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled
matthewlmcclure created JENKINS-21280 Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 08/Jan/14 6:03 PM Description: My notes: Jenkins killed the job after 15 minutes. I increased the job's "Timeout minutes" from 15 to 45 minutes. The emulator prompts to send usage statistics to Google on every run. I need to find a way to disable that. I don't see that problem after the first run when I run the steps ad hoc on my own machine. I bet seeing it is an artifact of how cleanly the Jenkins Android Emulator Plugin starts the emulator on every run. I hope there's a way to turn it off without compromising on starting from a clean state. The prompt comes from DDMS. The presence of a `ddms.cfg` file in `$ANDROID_SDK_HOME/.android` with the contents below prevents the prompt. #Wed Jan 08 10:23:13 EST 2014 pingId=2977280607391965849 The Jenkins Android Emulator Plugin has code that's clearly intended to set up `ddms.cfg` with `pingOptIn=false`. Is that not sufficient? Is it not executing? Is something else cleaning up `ddms.cfg` after it executes? I deleted the `.android` directory in the Jenkins job directory and re-ran the job. It prompted me to send usage statistics when the emulator launched. Before dismissing the dialog, I looked at the newly created `.android` directory. It contains a `ddms.cfg` file containing only `pingOptIn=false`, just as I would expect from reading the Android Emulator Plugin's source code. I suspect that that configuration was once sufficient to prevent the dialog and isn't sufficient anymore. It seems `pingId` is required now. Empirically, the following `ddms.cfg` is sufficient on my machine: pingId=0 I should change the Android Emulator Plugin to create `ddms.cfg` with: pingOptIn=false pingId=0 Project: Jenkins Priority: Minor Reporter: matthewlmcclure 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] [android-emulator] (JENKINS-21280) Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled
matthewlmcclure
updated JENKINS-21280
Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled
Change By:
matthewlmcclure
(08/Jan/14 6:05 PM)
Description:
Mynotes:{quote}Jenkinskilledthejobafter15minutes.IincreasedthejobsTimeoutminutesfrom15to45minutes.TheemulatorpromptstosendusagestatisticstoGoogleoneveryrun.Ineedtofindawaytodisablethat.IdontseethatproblemafterthefirstrunwhenIrunthestepsadhoconmyownmachine.IbetseeingitisanartifactofhowcleanlytheJenkinsAndroidEmulatorPluginstartstheemulatoroneveryrun.Ihopetheresawaytoturnitoffwithoutcompromisingonstartingfromacleanstate.ThepromptcomesfromDDMS.Thepresenceofa`ddms.cfg`filein`$ANDROID_SDK_HOME/.android`withthecontentsbelowpreventstheprompt.{noformat}#WedJan0810:23:13EST2014pingId=2977280607391965849{noformat}TheJenkinsAndroidEmulatorPluginhascodethatsclearlyintendedtosetup`ddms.cfg`with`pingOptIn=false`.Isthatnotsufficient?Isitnotexecuting?Issomethingelsecleaningup`ddms.cfg`afteritexecutes?Ideletedthe`.android`directoryintheJenkinsjobdirectoryandre-ranthejob.Itpromptedmetosendusagestatisticswhentheemulatorlaunched.Beforedismissingthedialog,Ilookedatthenewlycreated`.android`directory.Itcontainsa`ddms.cfg`filecontainingonly`pingOptIn=false`,justasIwouldexpectfromreadingtheAndroidEmulatorPluginssourcecode.Isuspectthatthatconfigurationwasoncesufficienttopreventthedialogandisntsufficientanymore.Itseems`pingId`isrequirednow.Empirically,thefollowing`ddms.cfg`issufficientonmymachine:{noformat}pingId=0{noformat}IshouldchangetheAndroidEmulatorPlugintocreate`ddms.cfg`with:{noformat}pingOptIn=falsepingId=0{noformat}
IexpectthatwillpreventtheusagestatisticsdialoginbotholdandnewversionsoftheAndroidSDK,assumingthat`pingOptIn=false`workedinsomeolderversion.Imusingthefollowingversionof`emulator`installedviaAndroidStudio0.4.0:
{
noformat}$/Applications/Android\Studio.app/sdk/tools/emulator-versionAndroidemulatorversion22.3.0(build_idOPENMASTER-887826)Copyright(C)2006-2011TheAndroidOpenSourceProjectandmanyothers.ThisprogramisaderivativeoftheQEMUCPUemulator(www.qemu.org).ThissoftwareislicensedunderthetermsoftheGNUGeneralPublicLicenseversion2,aspublishedbytheFreeSoftwareFoundation,andmaybecopied,distributed,andmodifiedunderthoseterms.Thisprogramisdistributedinthehopethatitwillbeuseful,butWITHOUTANYWARRANTY;withouteventheimpliedwarrantyofMERCHANTABILITYorFITNESSFORAPARTICULARPURPOSE.SeetheGNUGeneralPublicLicenseformoredetails.{noformat}{
quote}
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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney
commented on JENKINS-21279
java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Full list of plugins:
{core}
root@hudson0 plugins# ls -d *.?pi
analysis-core.jpi monitoring.jpi
ant.jpimsbuild.jpi
audit-trail.jpimstest.hpi
batch-task.jpi multi-module-tests-publisher.jpi
blame-upstream-commiters.hpi nant.hpi
build-flow-plugin.jpi next-build-number.jpi
buildgraph-view.jpinode-iterator-api.jpi
build-name-setter.hpi nunit.jpi
build-pipeline-plugin.jpi pam-auth.jpi
build-user-vars-plugin.jpi parameterized-trigger.jpi
cifs.hpi performance.hpi
ci-game.hpiphing.jpi
conditional-buildstep.jpi plot.hpi
config-file-provider.jpi pmd.jpi
configurationslicing.jpi port-allocator.jpi
copyartifact.jpi promoted-builds.jpi
credentials.jpipython.hpi
cvs.jpirelease.jpi
dashboard-view.jpi repository-connector.hpi
description-setter.jpi run-condition.jpi
disk-usage.jpi s3.jpi
doxygen.jpiscm-api.jpi
dry.jpiscm-sync-configuration.jpi
ec2.jpiscons.hpi
email-ext.jpi scp.hpi
emma.hpi sectioned-view.jpi
envinject.jpi shelve-project-plugin.jpi
external-monitor-job.jpi slave-status.hpi
findbugs.jpi sonar.jpi
ftppublisher.hpi ssh-credentials.jpi
git-client.jpi ssh-slaves.jpi
github-api.jpi subversion.jpi
github.jpi svn-release-mgr.hpi
git.jpisvn-tag.hpi
greenballs.jpi testflight.jpi
htmlpublisher.jpi testInProgress.jpi
jacoco.jpi testng-plugin.jpi
javadoc.jpitext-finder.hpi
jenkins-cloudformation-plugin.jpi throttle-concurrents.jpi
jenkins-multijob-plugin.jpitimestamper.jpi
jira.jpi token-macro.jpi
jquery.jpi translation.jpi
ldap.jpi url-change-trigger.hpi
locks-and-latches.hpi URLSCM.hpi
m2release.jpi urltrigger.jpi
m2-repo-reaper.hpi violations.hpi
mailer.jpi ws-cleanup.jpi
managed-scripts.jpixunit.jpi
matrix-auth.jpizentimestamp.jpi
maven-plugin.jpi
root@hudson0 plugins#{core}
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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Interestingly, I can't reproduce this on my test Jenkins instance, despite running the same versions of everything. 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-credentials] (JENKINS-21281) Validation button for private key passphrase field
Jesse Glick created JENKINS-21281 Validation button for private key passphrase field Issue Type: New Feature Assignee: stephenconnolly Components: ssh-credentials Created: 08/Jan/14 6:45 PM Description: When specifying a private key location (default on master, or explicit path), there should be either form validation or an explicit Validate button which checks that the private key file actually exists and can be read using the indicated passphrase (if any). Project: Jenkins 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 -- 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-monitor] (JENKINS-21282) Build monitor plugin stack trace
Ray Ryan updated JENKINS-21282 Build monitor plugin stack trace Change By: Ray Ryan (08/Jan/14 7:14 PM) Description: PerhapsbecauseImusingthefollowingregular_expression_topopulateit?(Itworksinanormalview.)(Android-|Lemonleaf\+git.squareup.com\+android\+.*\+(master|release)).*Thematchedprojectsaremostly(all?)mavenprojectsrunningonslaveservers.
[JIRA] [build-monitor] (JENKINS-21282) Build monitor plugin stack trace
Ray Ryan
updated JENKINS-21282
Build monitor plugin stack trace
Change By:
Ray Ryan
(08/Jan/14 7:18 PM)
Description:
PerhapsbecauseImusingthefollowingregular_expression_topopulateit?(Itworksinanormalview.)
{code}
(Android-|Lemonleaf\+git.squareup.com\+android\+.*\+(master|release)).*
{code}
Thematchedprojectsaremostly(all?)mavenprojectsrunningonslaveservers.
Errormessage,stacktrace:
[JIRA] [ssh-credentials] (JENKINS-21283) BasicSSHUserPrivateKey.getPassphrase breaks nullness contract of interface
Jesse Glick created JENKINS-21283 BasicSSHUserPrivateKey.getPassphrase breaks nullness contract of interface Issue Type: Bug Assignee: stephenconnolly Components: ssh-credentials Created: 08/Jan/14 7:25 PM Description: SSHUserPrivateKey.getPassphrase is documented to return null if the private key is not protected by passphrase. Yet the constructor of BasicSSHUserPrivateKey does not check for an empty passphrase, and Secret.fromString never returns null, so getPassphrase returns a non-null result even if none was specified (in this case .getPassphrase().getPlainText().isEmpty()). Project: Jenkins 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 -- 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] [warnings] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Ulli Hafner commented on JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin I see, the error is not reported in the console log, it i in Jenkins log. I now can reproduce the problem. I wonder why this worked before, the reference to MavenBuild is there since a couple of years. These references in AbstractResultAction are marked as deprecated for a long time now so I think it is save to remove them. 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] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
Magnus Sandberg commented on JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem You should be able to set any range you like on the main configuration page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21284) Add some logging to show what the sorter is doing
Magnus Sandberg created JENKINS-21284 Add some logging to show what the sorter is doing Issue Type: New Feature Assignee: Magnus Sandberg Components: prioritysorter Created: 08/Jan/14 7:51 PM Description: Add some logging to show when the sorter is invoked and what job it does. Project: Jenkins Priority: Minor Reporter: Magnus Sandberg 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] [android-emulator] (JENKINS-21280) Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled
SCM/JIRA link daemon commented on JENKINS-21280 Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled Code changed in jenkins User: Matt McClure Path: src/main/java/hudson/plugins/android_emulator/SdkInstaller.java http://jenkins-ci.org/commit/android-emulator-plugin/72ac1931eef0e23a1dcfc90d8a92b7522a294583 Log: FIXED JENKINS-21280 Update usage statistics opt out Empirically, emulator version 22.3.0 installed via Android Studio 0.4.0 requires pingId=... to opt out. pingOptIn=false, as previously implemented is not sufficient. 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] [android-emulator] (JENKINS-21280) Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled
SCM/JIRA link daemon resolved JENKINS-21280 as Fixed Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled Change By: SCM/JIRA link daemon (08/Jan/14 8: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] [android-emulator] (JENKINS-21280) Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled
SCM/JIRA link daemon commented on JENKINS-21280 Emulator prompts to send usage statistics on every job run with Keep emulators in the job workspace... enabled Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/SdkInstaller.java http://jenkins-ci.org/commit/android-emulator-plugin/b414ba54032f5be7b869af4b495c702b6a402a00 Log: Merge pull request #30 from matthewlmcclure/JENKINS-21280 FIXED JENKINS-21280 Update usage statistics opt out Compare: https://github.com/jenkinsci/android-emulator-plugin/compare/6aedbd08fa5e...b414ba54032f 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] [ec2] (JENKINS-21182) EC2 Plugin: EC2 instance starts but waits forever
Mark Fink commented on JENKINS-21182 EC2 Plugin: EC2 instance starts but waits forever Thank you so much Andrew! I struggled for a while to get more log information out of the plugin to see what is wrong. Thanks to you this mystery is resolved. Next step I will try out your suggestion and setup a slave at us-east-1 region with EC2-Classic. 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] [ec2] (JENKINS-12332) only start an EC2 instance if a build is actually going to occur, per current label expressions
Igor Okulist closed JENKINS-12332 as Fixed only start an EC2 instance if a build is actually going to occur, per current label expressions Duplicate of JENKINS-15158 propose to close. Change By: Igor Okulist (08/Jan/14 8:57 PM) Status: Open Closed 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] [parameterized-trigger] (JENKINS-10147) Add 'poll SCM' option to build step
Charles Jones commented on JENKINS-10147 Add poll SCM option to build step I too would find this useful. 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] [scm-api] (JENKINS-21288) Build with Poll SCM trigger proceeds even though no SCM change
Charles Jones created JENKINS-21288 Build with Poll SCM trigger proceeds even though no SCM change Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: SCM.PNG Components: scm-api Created: 08/Jan/14 9:36 PM Description: I have a Jenkins jobs setup to poll SCM nightly and run a build if there are changes. The problem is if there are no changes, Jenkins executes the job anyway. Here is console output of a simple job that polls SCM and then executes a single build step (shell command of "echo blah"). attached is a screenshot of the console output (also available here: http://i.imgur.com/5jQTIAe.png) You can see, even though there were no SCM changes, the build continues. The behavior I am looking for is if there is no change, the build steps are not executed. Also strange is the first thing in the output is "Started by an SCM change", followed by an indication that there was in fact no change. Environment: linux Project: Jenkins Priority: Major Reporter: Charles Jones 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-21237) Jenkins should use LaunchAgents under OSX
Sami Tikka commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX It has been years since I last played with PackageMaker but I believe it was possible to build a package that will query if you want to install for all users or for current user only. If all users is chosen, the installer will prompt for admin password. It might be possible to determine which kind of installation happened in a post install script and place the launchd plist file in a location that either makes Jenkins be a launch daemon or launch agent. However, I think it would be rude to unconditionally configure the current user's account such that after login he is immediately presented with the login screen again. It should at least be configurable (= ask the user) but how to do that with PackageMaker... I have no idea. Actually I am really tired with PackageMaker. I believe a better user experience is achieved by creating an application, a single icon the user drags where he wants and runs by double-clicking. The application can then have a conversation with the user or present a rich UI to configure and run Jenkins. If a launch agent or daemon is needed, the application can set those up. So, personally, rather than fight with the limitations of PackageMaker, I would rather improve Jenkins.app. I'm happy to collaborate on it (pull requests are welcome.) Jenkins.app is my own project but if people feel it should be in the official Jenkins git repository, I can renew my request to accept it there. I have kept it outside of the official Jenkins tree because I assumed most people were happy with the PackageMaker based installer which runs Jenkins as a launch daemon. It has it's problems but there are workarounds and plugins like the Xcode plugin which should provide some relief. 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] [prioritysorter] (JENKINS-21289) Item Logging causing NPE (2.4)
Magnus Sandberg created JENKINS-21289 Item Logging causing NPE (2.4) Issue Type: Bug Assignee: Magnus Sandberg Components: prioritysorter Created: 08/Jan/14 9:45 PM Description: Item Logging causing NPE. NPE is thrown when logger is not configured. Environment: PrioritySorter 2.4 Project: Jenkins Priority: Blocker Reporter: Magnus Sandberg 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-21237) Jenkins should use LaunchAgents under OSX
cowwoc commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX @Sami Tikka, I don't see the point of ever installing Jenkins for all users. You always want to install it for one user, be that the current user or some other user. What I'd really like to see Jenkins' official installer install into the current user, and a unification of #jenkinsapp and https://github.com/rhwood/jenkins-slave-osx for installing Jenkins outside the current user. 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] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
Magnus Sandberg commented on JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem I found an issue that might cause the 2.4 to behave badly. I will release 2.5 with a fix asap. 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] [prioritysorter] (JENKINS-21289) Item Logging causing NPE
Magnus Sandberg updated JENKINS-21289 Item Logging causing NPE Change By: Magnus Sandberg (08/Jan/14 9:59 PM) Summary: ItemLoggingcausingNPE (2.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] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Joe Knudsen commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows See issue JENKINS-20725 for an issue with the Maven Plugin that still exists in 1.509.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] [delivery-pipeline] (JENKINS-21149) Possibility to change pipeline version in later tasks or stages
Patrice Matignon edited a comment on JENKINS-21149 Possibility to change pipeline version in later tasks or stages What should be the logic for setting the version then ? If I understand correctly, using "Create Delivery Pipeline version" sets an env variable "PIPELINE_VERSION", and also passes it on as a build parameter to jobs downstream, whether or not the "set Build display name" is actually checked. Also, currently the default behavior is to use the first build's display name (whether or not it was set by the mechanism above) as the pipeline instance version. I would propose that the pipeline would look at the PIPELINE_VERSION env variable, starting from the end of the pipeline and moving backwards if necessary (to reflect the fact that you can set/override the pipeline version later in the pipeline). If that env var is not found anywhere in the pipeline instance builds, then the logic would default to the current behavior, in order to maintain backward-compatibility. Does that sound sensible? Thanks for your feedback! 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] [prioritysorter] (JENKINS-21284) Add some logging to show what the sorter is doing
SCM/JIRA link daemon commented on JENKINS-21284 Add some logging to show what the sorter is doing Code changed in jenkins User: emsa23 Path: src/main/java/jenkins/advancedqueue/sorter/AdvancedQueueSorter.java http://jenkins-ci.org/commit/priority-sorter-plugin/444dc1522a4afe96f932ce3826b0d1afa0d5202a Log: JENKINS-21284 Add some logging to show what the sorter is doing Now logging number of sorted items on FINE after sorting 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] [prioritysorter] (JENKINS-21289) Item Logging causing NPE
SCM/JIRA link daemon commented on JENKINS-21289 Item Logging causing NPE Code changed in jenkins User: emsa23 Path: src/main/java/jenkins/advancedqueue/ItemTransitionLogger.java src/main/java/jenkins/advancedqueue/sorter/AdvancedQueueSorter.java http://jenkins-ci.org/commit/priority-sorter-plugin/abc2cc591da48b6c06e78daa81c8f393eefe72ce Log: JENKINS-21289 Item Logging causing NPE getLevel() return null when no logger is configured. 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] [prioritysorter] (JENKINS-21204) Add ability to boost recently failed Jobs
SCM/JIRA link daemon commented on JENKINS-21204 Add ability to boost recently failed Jobs Code changed in jenkins User: emsa23 Path: src/main/java/jenkins/advancedqueue/priority/strategy/HealthStrategy.java src/main/resources/jenkins/advancedqueue/priority/strategy/HealthStrategy/config.jelly http://jenkins-ci.org/commit/priority-sorter-plugin/cebc7bb49aa7034ebd6da44e885b23c1343c9194 Log: JENKINS-21204 Add ability to boost recently failed Jobs Added new PriorityStrategy called HealthStrategy 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] [prioritysorter] (JENKINS-21204) Add ability to boost recently failed Jobs
Magnus Sandberg resolved JENKINS-21204 as Fixed Add ability to boost recently failed Jobs Change By: Magnus Sandberg (08/Jan/14 10:37 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] [prioritysorter] (JENKINS-21284) Add some logging to show what the sorter is doing
Magnus Sandberg resolved JENKINS-21284 as Fixed Add some logging to show what the sorter is doing Change By: Magnus Sandberg (08/Jan/14 10:37 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] [prioritysorter] (JENKINS-21204) Add ability to boost recently failed Jobs
Magnus Sandberg commented on JENKINS-21204 Add ability to boost recently failed Jobs Fixed in 2.5 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] [prioritysorter] (JENKINS-21289) Item Logging causing NPE
Magnus Sandberg resolved JENKINS-21289 as Fixed Item Logging causing NPE Fixed in 2.5 Change By: Magnus Sandberg (08/Jan/14 10:38 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] [prioritysorter] (JENKINS-21284) Add some logging to show what the sorter is doing
Magnus Sandberg commented on JENKINS-21284 Add some logging to show what the sorter is doing Fixed in 2.5 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] [artifact-diff] (JENKINS-21290) Support archive traversal
Oliver Gondža created JENKINS-21290 Support archive traversal Issue Type: New Feature Assignee: Unassigned Components: artifact-diff Created: 08/Jan/14 10:41 PM Description: Traverse .zip (and .jar) file as directories. Project: Jenkins Priority: Major Reporter: Oliver Gondža 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-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Mark Waite edited a comment on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows This problem is also visible in Jenkins 1.509.1 LTS release candidate. It appears as a stack trace WARNING: Failed to update hudson.model.FreeStyleProject@1b7e8eff[jenkins-demo] l astSuccessfulBuild permalink for jenkins-demo #24 java.nio.file.NoSuchFileException: C:\Users\Mark\.jenkins\jobs\jenkins-demo\builds\lastSuccessfulBuild.tmp at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsLinkSupport.readLink(WindowsLinkSupport.java:56) at sun.nio.fs.WindowsFileSystemProvider.readSymbolicLink(WindowsFileSystemProvider.java:636) at java.nio.file.Files.readSymbolicLink(Files.java:1382) at sun.reflect.GeneratedMethodAccessor125.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at hudson.Util.resolveSymlink(Util.java:1188) at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:146) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:118) at hudson.model.Job.getLastSuccessfulBuild(Job.java:802) at sun.reflect.GeneratedMethodAccessor213.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at
[JIRA] [cloudbees-folder] (JENKINS-20008) Need core API corresponding to ItemGroupModifier
SCM/JIRA link daemon commented on JENKINS-20008 Need core API corresponding to ItemGroupModifier Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/DirectlyModifiableTopLevelItemGroup.java core/src/main/java/jenkins/model/Jenkins.java test/src/main/java/org/jvnet/hudson/test/MockFolder.java http://jenkins-ci.org/commit/jenkins/1d21017e3b54edb36a58aa7d7658250b4f221c80 Log: FIXED JENKINS-20008 Added DirectlyModifiableTopLevelItemGroup. 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-18680) View.onJobRenamed should be deprecated
SCM/JIRA link daemon commented on JENKINS-18680 View.onJobRenamed should be deprecated Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AllView.java core/src/main/java/hudson/model/ItemGroup.java core/src/main/java/hudson/model/ListView.java core/src/main/java/hudson/model/MyView.java core/src/main/java/hudson/model/ProxyView.java core/src/main/java/hudson/model/TreeView.java core/src/main/java/hudson/model/View.java core/src/main/java/jenkins/model/Jenkins.java core/src/test/java/hudson/model/ViewTest.java test/src/main/java/org/jvnet/hudson/test/MockFolder.java test/src/test/java/hudson/model/ListViewTest.java http://jenkins-ci.org/commit/jenkins/6d3c2e0d849dd76b6507daca1cc910f75418e941 Log: FIXED JENKINS-18680 Update members of a ListView using a regular listener, not View.onJobRenamed which does not work with folders. 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] [cloudbees-folder] (JENKINS-20008) Need core API corresponding to ItemGroupModifier
SCM/JIRA link daemon commented on JENKINS-20008 Need core API corresponding to ItemGroupModifier Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Items.java core/src/main/java/hudson/model/listeners/ItemListener.java core/src/main/java/jenkins/model/DirectlyModifiableTopLevelItemGroup.java http://jenkins-ci.org/commit/jenkins/6ca99ff8c241769959dec4b31257a54a22e340a6 Log: FIXED JENKINS-20008 FIXED JENKINS-18028 FIXED JENKINS-18680 #1069: support for moving jobs into or out of folders. Compare: https://github.com/jenkinsci/jenkins/compare/dda099c19a7a...6ca99ff8c241 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.
