[JIRA] (JENKINS-14597) Rundeck JobID doesn't persist when used as build publisher
Youssuf ElKalay updated JENKINS-14597 Rundeck JobID doesnt persist when used as build publisher Change By: Youssuf ElKalay (27/Jul/12 6:01 AM) Description: WhenusingtheRundeckJenkinsPluginasabuildpublisherwithinaconditionalbuild-step(eithersingleormulti-step)theJobIDfielddoesntpersisttothejobsconfigfileafterthejobconfigurationpageissaved.IhavetestedfillingouttheRundeckjobIDfieldoutsideoftheconditionalbuildpublisherfieldsandthedatadoespersist.OnasidenotetheRundeckpluginmakesacalltoRundecktoverifythecontentsofthejobID(ittakesaUUID,jobIDorjob/projectname)anddisplaysthefullnameofthejobdirectlyunderneaththefield.Imnotsureifthiscallflowiscausingissueswiththeconditionalbuildpublisher ornot . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14597) Rundeck JobID doesn't persist when used as build publisher
Youssuf ElKalay created JENKINS-14597 Rundeck JobID doesnt persist when used as build publisher Issue Type: Bug Affects Versions: current Assignee: domi Components: conditional-buildstep Created: 27/Jul/12 6:00 AM Description: When using the Rundeck Jenkins Plugin as a build publisher within a conditional build-step (either single or multi-step) the JobID field doesn't persist to the job's config file after the job configuration page is saved. I have tested filling out the Rundeck jobID field outside of the conditional build publisher fields and the data does persist. On a side note the Rundeck plugin makes a call to Rundeck to verify the contents of the jobID (it takes a UUID, job ID or job/project name) and displays the full name of the job directly underneath the field. I'm not sure if this call flow is causing issues with the conditional build publisher. Environment: CentOS 6 x86-64 JDK 1.6.x (latest version) Project: Jenkins Labels: rundeck Priority: Major Reporter: Youssuf ElKalay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14598) Crash on result parsing
Stefan Bellus created JENKINS-14598 Crash on result parsing Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: fitnesse Created: 27/Jul/12 6:04 AM Description: In one project Fitnesse trend graph is not displayed but in other it is. In project that doesn't display trend graph I trigger down stream projects and use compiler warning plugin. Here is log from jenkins.log: Apr 24, 2012 10:19:53 AM winstone.Logger logInternal SEVERE: Error while serving http://localhost:8081/jenkins/job/CCG/fitnesse/trend/countGraph/png java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor449.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) 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:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) 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:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) 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:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) 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:47) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at
[JIRA] (JENKINS-14596) Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException
Vassilena Treneva commented on JENKINS-14596 Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException I am attaching the log taken from /var/log/jenkins. I see several errors in it. Not sure if they are relevant t this problem or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14596) Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException
Vassilena Treneva updated JENKINS-14596 Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException Change By: Vassilena Treneva (27/Jul/12 6:06 AM) Attachment: jenkins.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13565) Fitnesse trend graph is not displayed on project
Stefan Bellus updated JENKINS-13565 Fitnesse trend graph is not displayed on project It is working now Change By: Stefan Bellus (27/Jul/12 6:08 AM) Assignee: StefanBellus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13565) Fitnesse trend graph is not displayed on project
Stefan Bellus closed JENKINS-13565 as Fixed Fitnesse trend graph is not displayed on project It is working. There was problem in project configuration. Change By: Stefan Bellus (27/Jul/12 6:09 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
[JIRA] (JENKINS-14599) Parmeterize node(s) in build Phases Jobs
hagzag created JENKINS-14599 Parmeterize node(s) in build Phases Jobs Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 27/Jul/12 6:27 AM Description: Whilst triggering a MultiJob, one wishes to determine on what node the Job will actually run on, and this may be quite complex when you have 3 pahses with 2 jobs in them and you want to control what will run where. You could use the "Tie this job to node" which comes in Jeknins out of the box, but then you loose the flexibility of Multi Job which basically can take you from Dev = QA = PROD where all that changes is the nodes which your process is running on. Due Date: 29/Jul/12 12:00 AM Environment: N/A Fix Versions: current Project: Jenkins Priority: Major Reporter: hagzag This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14580) Configuration of Buildresult-Trigger remains unchanged, when saved.
Gregory Boissinot started work on JENKINS-14580 Configuration of Buildresult-Trigger remains unchanged, when saved. Change By: Gregory Boissinot (27/Jul/12 6:33 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14580) Configuration of Buildresult-Trigger remains unchanged, when saved.
Gregory Boissinot updated JENKINS-14580 Configuration of Buildresult-Trigger remains unchanged, when saved. Changed to buildresult-trigger component Change By: Gregory Boissinot (27/Jul/12 6:32 AM) Component/s: buildresult-trigger Component/s: jenkins-multijob-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14580) Configuration of Buildresult-Trigger remains unchanged, when saved.
Gregory Boissinot commented on JENKINS-14580 Configuration of Buildresult-Trigger remains unchanged, when saved. I'm afraid I don't understand your issue. Please could you give me more information? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14600) Disable/enable job or phase without disabling the regular job itself
hagzag created JENKINS-14600 Disable/enable job or phase without disabling the regular job itself Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 27/Jul/12 6:35 AM Description: Whilst working with Build Phases conducted of regular jobs, we need the ability to disable a certain Job within the Phase or the Flow of the build. Although as of today disabling a certain Job will also disable it in a "CI scope" or its standalone state out of the MultiJob scope. so we need to add a check box at each phase level which will disable that certain job or Phase all together, what would be nice is to configure it once and it will be back to normal the next time you execute the MultiJob or permanent. Due Date: 31/Aug/12 12:00 AM Environment: N/A Fix Versions: current Project: Jenkins Priority: Major Reporter: hagzag This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14599) Parmeterize node(s) in build Phases Jobs
hagzag updated JENKINS-14599 Parmeterize node(s) in build Phases Jobs Change By: hagzag (27/Jul/12 6:39 AM) URL: https://github.com/jenkinsci/tikal-multijob-plugin/issues/3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14600) Disable/enable job or phase without disabling the regular job itself
hagzag updated JENKINS-14600 Disable/enable job or phase without disabling the regular job itself Change By: hagzag (27/Jul/12 6:39 AM) URL: https://github.com/jenkinsci/tikal-multijob-plugin/issues/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
[JIRA] (JENKINS-14601) Continuous job status doesn't display during MultiJob execution
hagzag created JENKINS-14601 Continuous job status doesnt display during MultiJob execution Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: jenkins-cloudformation Created: 27/Jul/12 6:57 AM Description: If multiple jobs are running on the same phase the results are not reported in the stdout untill the last job is finished. Due Date: 31/Aug/12 12:00 AM Fix Versions: current Project: Jenkins Priority: Major Reporter: hagzag This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14602) Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config
Thomas Fields created JENKINS-14602 Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config Issue Type: Bug Affects Versions: current Assignee: kutzi Components: jabber Created: 27/Jul/12 7:01 AM Description: Hi there, I'm using the Jabber plugin to notify engineers when they have broken the build. However, if you remove your Jabber ID from the user config it still manages to Jabber you regarding build breaks. This looks like a bug to me. It's like the Jabber has cached the Jabber IDs somewhere and isn't checking whether there are any user config changes. I've even tried rebooting Jenkins to no avail. Is this a bug? Can it be fixed please? Regards, Tom Environment: Windows 7. Jabber plugin 1.22. Instant messagine plugin 1.21. Project: Jenkins Priority: Major Reporter: Thomas Fields This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14603) Drag jobs in the config from phase to phase
hagzag created JENKINS-14603 Drag jobs in the config from phase to phase Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 27/Jul/12 7:05 AM Description: Self explanatory like the ability to "drag n drop" build stage in "freestyle" but in this case build Phases or jobs from one build phase to another build phase. Due Date: 31/Aug/12 12:00 AM Fix Versions: current Project: Jenkins Priority: Minor Reporter: hagzag This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14604) Fix view display of nested MultiJob's / upstream of MultiJob
hagzag created JENKINS-14604 Fix view display of nested MultiJobs / upstream of MultiJob Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 27/Jul/12 7:09 AM Description: Fix the sub multi job view = when multi job has upstream it doesn’t show the multi job hierarchy view correctly. Due Date: 31/Aug/12 12:00 AM Fix Versions: current Project: Jenkins Priority: Major Reporter: hagzag This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14580) Configuration of Buildresult-Trigger remains unchanged, when saved.
Ramakrishna Bejawar commented on JENKINS-14580 Configuration of Buildresult-Trigger remains unchanged, when saved. To make it more clear, As attached when i select a Job to monitor and trying to save then when i check it back the configuration settings will be in default state. Ex: I select "Build-Success" as my job to monitor, when i save and look back It is changed to "install-groovy-base". So here my issue is the settings are not saved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14605) Simple means to obtain logged in user's id
Daniel Kirkdorffer created JENKINS-14605 Simple means to obtain logged in users id Issue Type: Improvement Assignee: Unassigned Components: core Created: 27/Jul/12 7:18 AM Description: I've searched for a means to obtain the id of the currently logged in User, but incredibly this info is not easily queried. Existing solutions using User.current(), or Cause.UserIdCause() for triggered builds, are not reliable. User.current() results in SYSTEM whenever I try to use it. Cause.UserIdCause is only useful to me if I'm able to access it, and when I'm working with slaves it doesn't seem to be set for the master build triggered by a user. Yet, while I'm hunting around, I can see that the user id is always displaying in the top right corner of the UI, taunting me since it is the information I want, but seemingly not available. Surely this shouldn't be so hard or obtuse. If I just had the id, I could look up the User with a User.get(id) and be on my merry way. Thanks. Project: Jenkins Labels: jenkins user slave Priority: Major Reporter: Daniel Kirkdorffer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14602) Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config
kutzi commented on JENKINS-14602 Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config If there's no Jabber-ID configured per user, the plugin implies the user jabber id by other means (if I remember correctly, by concatening Jenkins user name with 'Default ID suffix' from global settings). I guess that's what you're seeing. There's no way to disable the notification for a single 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
[JIRA] (JENKINS-14602) Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config
Thomas Fields commented on JENKINS-14602 Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config There's no way to disable the notification for a single user. That's rubbish. Please consider this a feature request then. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14370) SSL Error while trying to upload to Zubhium
Andreas Katzig commented on JENKINS-14370 SSL Error while trying to upload to Zubhium Hi Gavin, sorry for getting back so late. Is this still valid? I believe they were having some SSL certificate troubles. Regards, Andreas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14606) svn-tag plugin does not support environment variables from promoted build
Christian Gmeiner created JENKINS-14606 svn-tag plugin does not support environment variables from promoted build Issue Type: Bug Assignee: k2nakamura Attachments: config.xml Components: promoted-builds, svn-tag Created: 27/Jul/12 9:04 AM Description: Parameter myversion2 (see attachment) is not useable in svn tag plugin. The tag gets names as null. Environment: Jenkins: 1.450 Jenkins promoted builds plugin: 2.6.1 Jenkins Subversion Plugin: 1.34 Jenkins Subversion Tagging Plugin: 1.16 Project: Jenkins Priority: Major Reporter: Christian Gmeiner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13855) Parallel deployment to Tomcat 7 with deploy plugin throws exception and fails the build
Daniel Barth commented on JENKINS-13855 Parallel deployment to Tomcat 7 with deploy plugin throws exception and fails the build I found the cause why the plugin was not showing up in the post build actions list: I'm doing the maven build in Eclipse and found a blog post that automatic builds must be disabled under Eclipse because it interferes with the manifest generation. http://gis-blog.leonde.de/index.php/2012/02/19/debugging-jenkins-plugins/ The plugin is working now but I still have to adjust the Hostname / URL properties of Cargo for the Tomcat manager interface. I thought the new Cargo version would automatically set the appropriate path based on GeneralPropertySet.HOSTNAME and Tomcat version, but seems so it doesn't (or I'm still missing something...). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13647) Environment variables from EnvInject plugin are not inherited/parsed by batch tasks
Julien Carsique updated JENKINS-13647 Environment variables from EnvInject plugin are not inherited/parsed by batch tasks Change By: Julien Carsique (27/Jul/12 9:39 AM) Component/s: rebuild This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14592) Plugin is parsing session id output from standard error but not standard output
SCM/JIRA link daemon commented on JENKINS-14592 Plugin is parsing session id output from standard error but not standard output Code changed in jenkins User: Ross Rowe Path: src/main/java/hudson/plugins/sauce_ondemand/BrowserAxis.java src/main/java/hudson/plugins/sauce_ondemand/PluginImpl.java src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandReportFactory.java src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandReportPublisher.java src/test/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapperTest.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/db11b54a9f1538053174940e83ef5b3b983ad789 Log: JENKINS-14592 Added some more logging, and ensure that output that doesnt include job name is parsed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14592) Plugin is parsing session id output from standard error but not standard output
Ross Rowe started work on JENKINS-14592 Plugin is parsing session id output from standard error but not standard output Change By: Ross Rowe (27/Jul/12 9:53 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13647) Environment variables from EnvInject plugin are not inherited/parsed by batch tasks
Julien Carsique reopened JENKINS-13647 Environment variables from EnvInject plugin are not inherited/parsed by batch tasks Reproduced again with Batch task 1.16 and Rebuilder 1.14: Jul 27, 2012 9:16:25 AM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException: Current Project is null at com.sonyericsson.rebuild.RebuildAction.getProject(RebuildAction.java:129) at com.sonyericsson.rebuild.RebuildAction.isRebuildAvailable(RebuildAction.java:227) at com.sonyericsson.rebuild.RebuildAction.getUrlName(RebuildAction.java:154) at org.jenkinsci.lib.envinject.service.EnvInjectActionRetriever.getEnvInjectAction(EnvInjectActionRetriever.java:32) at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:51) at hudson.plugins.batch_task.BatchRun.run(BatchRun.java:224) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Downgrading again to Batch task 1.15 as a workaround. Change By: Julien Carsique (27/Jul/12 9:53 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13647) Environment variables from EnvInject plugin are not inherited/parsed by batch tasks
Julien Carsique edited a comment on JENKINS-13647 Environment variables from EnvInject plugin are not inherited/parsed by batch tasks Reproduced again with Jenkins 1.472, Batch task 1.16 and Rebuilder 1.14: Jul 27, 2012 9:16:25 AM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException: Current Project is null at com.sonyericsson.rebuild.RebuildAction.getProject(RebuildAction.java:129) at com.sonyericsson.rebuild.RebuildAction.isRebuildAvailable(RebuildAction.java:227) at com.sonyericsson.rebuild.RebuildAction.getUrlName(RebuildAction.java:154) at org.jenkinsci.lib.envinject.service.EnvInjectActionRetriever.getEnvInjectAction(EnvInjectActionRetriever.java:32) at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:51) at hudson.plugins.batch_task.BatchRun.run(BatchRun.java:224) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Downgrading again to Batch task 1.15 as a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14497) Can't start emulator with new Android SDK Tools rev. 20.0.1
Christos Dovas commented on JENKINS-14497 Cant start emulator with new Android SDK Tools rev. 20.0.1 Hi guys, it still doesn't work with the Version 2.3 of the emulator plugin. I still get the same Error messages. Are you sure this was fixed??? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14531) CAS1 and 'Trigger builds remotely' incompatibility
James Birmingham commented on JENKINS-14531 CAS1 and Trigger builds remotely incompatibility This is exactly what I need also. Happy to help test 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
[JIRA] (JENKINS-14531) CAS1 and 'Trigger builds remotely' incompatibility
João Antunes commented on JENKINS-14531 CAS1 and Trigger builds remotely incompatibility it's working now, https://github.com/joantune/cas1-plugin give it a spin, just git clone, mvn package, maybe remove the plugin on the hudson dir and then click on advanced and upload this version. I already made a pull request so that it can be integrated in the main code base. Cheers, João Antunes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13855) Parallel deployment to Tomcat 7 with deploy plugin throws exception and fails the build
Daniel Barth commented on JENKINS-13855 Parallel deployment to Tomcat 7 with deploy plugin throws exception and fails the build Plugin is compiling / packing / working fine now. For update compatability I switched (back) from GeneralPropertySet.HOSTNAME to RemotePropertySet.URI (replaced TomcatPropertySet.MANAGER_URL for Cargo 1.2.3). Switching to GeneralPropertySet.HOSTNAME / ServletPropertySet.PORT would be cleaner because Cargo would handle the required (manager) path selection based on Tomcat version - perhaps later... I will probably make a pull request for the changes but I only tested deployment to Tomcat 7.x. Looking at the other forks I noticed that someone else already did the changes to update to Cargo 1.2.2 but didn't made a pull request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14607) URLTrigger Polling error null
Sean DeNigris created JENKINS-14607 URLTrigger Polling error null Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: urltrigger Created: 27/Jul/12 1:40 PM Description: You can see the error at https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/Pharo-2.0/urltriggerPollLog/? The configuration for the job is publicly viewable. Project: Jenkins Labels: plugin Priority: Major Reporter: Sean DeNigris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13119) How can I set an environment variable based on value of user passed parameter?
Anup Singh
commented on JENKINS-13119
How can I set an environment variable based on value of user passed parameter?
Gregory, First let me just thank you for such a prompt response. Honestly speaking I am not a big fan of open source mainly because of support. But my view is already changing.
Having said that, I did what you request me and the issue persists. complete details follow:
Started by user Anup Singh
EnvInject - Loading node environment variables.
EnvInject - Preparing an environment for the build.
EnvInject - Keeping Jenkins system variables.
EnvInject - Adding build parameters as variables.
EnvInject - Evaluation the following Groovy script content:
if ("Trunk".equals(BUILD_TYPE)) {
def map = [SVN_REPO_PATH: "trunk/ConfigManagement"]; return map
}
if ("Branches".equals(BUILD_TYPE)) {
def map = SVN_REPO_PATH: branches/${SVN_BRANCH}; return map
}
if ("Tags".equals(BUILD_TYPE)) {
def map = SVN_REPO_PATH: branches/${SVN_TAG}; return map
}
EnvInject - ERROR - SEVERE ERROR occurs: No such property: BUILD_TYPE for class: Script1
Finished: FAILURE
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14596) Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException
Vassilena Treneva updated JENKINS-14596 Upgrade to Jenkins 1.475 causes OutOfMemoryError: PermGen space Caused by: com.google.common.collect.ComputationException Change By: Vassilena Treneva (27/Jul/12 2:13 PM) Priority: Blocker Major Description: AfewdaysagoweupgradedtoJenkinsver.1.475.Sincethenalmosteverydaywegetjava.lang.OutOfMemoryError:PermGenspace.Icannotbe100%surethattheupgradeisthereason,butoursetupbehindhasnotchanged.Pleasehavealookandhelp:StatusCode:500Exception:org.apache.commons.jelly.JellyTagException:jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.475.jar!/lib/layout/layout.jelly:91:72:st:includejava.lang.OutOfMemoryError:PermGenspaceStacktrace:javax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.475.jar!/lib/layout/layout.jelly:91:72:st:includejava.lang.OutOfMemoryError:PermGenspace atorg.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) atorg.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:659) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:659) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:488) atorg.kohsuke.stapler.Stapler.service(Stapler.java:162) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:45) atwinstone.ServletConfiguration.execute(ServletConfiguration.java:248) atwinstone.RequestDispatcher.forward(RequestDispatcher.java:333) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:175) atnet.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) atorg.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
[JIRA] (JENKINS-13447) Show link to promotion jobs archived artifacts
Mauro Molinari commented on JENKINS-13447 Show link to promotion jobs archived artifacts I think I've the same problem: when I add an action to a manual promotion to archive artifacts, I don't see any element in the Jenkins UI with which I can reach the archived artifacts. Having named "Release" such a promotion job, looking at the server file system the archived artifacts are placed in ~/jobs/SemplaERA_BancaSella/promotions/Release. Could this be fixed? I don't want to archive the artifacts for ANY build, but only for the promoted ones. And if the archived artifacts are not reachable from within Jenkins, the archive functionality is quite useless. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13447) Show link to promotion jobs archived artifacts
Mauro Molinari edited a comment on JENKINS-13447 Show link to promotion jobs archived artifacts I think I've the same problem: when I add an action to a manual promotion to archive artifacts, I don't see any element in the Jenkins UI with which I can reach the archived artifacts. Having named "Release" such a promotion job, looking at the server file system the archived artifacts are placed in ~/jobs/project name/promotions/Release. Could this be fixed? I don't want to archive the artifacts for ANY build, but only for the promoted ones. And if the archived artifacts are not reachable from within Jenkins, the archive functionality is quite useless. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14609) notification-plugin not properly setting Content-Type when protocol is HTTP
Jonathan Edwards created JENKINS-14609 notification-plugin not properly setting Content-Type when protocol is HTTP Issue Type: Patch Affects Versions: current Assignee: Jonathan Edwards Components: notification Created: 27/Jul/12 3:16 PM Description: The notification plugin https://github.com/jenkinsci/notification-plugin is not properly setting the request property "Content-Type: application/json;charset=UTF-8" when submitting JSON via HTTP (see Protocol.java). As a consequence, target systems that rely on the content type are unable to properly process the POST. The patch has been tested and works properly (the target server inspects the Content-Type and loads the JSON handler). Pull request has been submitted with fix. Environment: Platform independent Fix Versions: current Project: Jenkins Priority: Major Reporter: Jonathan Edwards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13119) How can I set an environment variable based on value of user passed parameter?
Anup Singh
commented on JENKINS-13119
How can I set an environment variable based on value of user passed parameter?
Problem solved...got rid of curly braces around SVN_BRANCH and SVN_TAG. However its weird that I still has to use the $ sign in front of it but I have to use BUILD_TYPE without the preceding $.
if ("Trunk".equals(BUILD_TYPE)) {
def map = [SVN_REPO_PATH: "trunk/ConfigManagement"]; return map
}
if ("Branches".equals(BUILD_TYPE)) {
def map = [SVN_REPO_PATH: "branches/$SVN_BRANCH"]; return map
}
if ("Tags".equals(BUILD_TYPE)) {
def map = [SVN_REPO_PATH: "tags/$SVN_TAG"]; return map
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14138) New git branch has empty changelist
tsondergaard commented on JENKINS-14138 New git branch has empty changelist No, the patch only changes the behavior for the case where there is a merge target. The merge target branch is a reasonable reference for new (not built before) branches - Without it what would you consider a reasonable reference? From your comment 9/Jun/12 12:03 it is clear that you would want the changeset to be relative to 'master', but 'master' is just another branch to git. How should it know that you want change sets to be computed relative to 'master'? A change that could serve both of us would be to add a configuration option to the git plugin where you can specify that you want changesets to be computed relative to a named branch, ie you would have to check a box "Compute changesets relative to named branch" and fill in the name of the branch. That would work for both of us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14138) New git branch has empty changelist
jpschewe
commented on JENKINS-14138
New git branch has empty changelist
Am I correct in assuming that the git plugin tracks the last commit that was built for each branch? So you build the list of changes for a given branch by talking the tree of all commits on that branch since the last build. Correct?
If you have this information, then you can get the list of commits for this new branch and walk backwards until you run into a commit that has already been built. That list of commits is the change set for the new branch.
Something like this:
{{
ListString changeset = new LinkedListString();
String currentCommit = new branch HEAD
boolean done = false;
while(!done) {
for(String builtCommit : latestCommit for each known branch) {
if(history(buildCommit).contains(currentCommit)) {
done = true;
}
}
if(!done) {
changeset.add(currentCommit);
}
}
}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14606) svn-tag plugin does not support environment variables from promoted build
k2nakamura assigned JENKINS-14606 to Renjith V svn-tag plugin does not support environment variables from promoted build Change By: k2nakamura (27/Jul/12 5:04 PM) Assignee: k2nakamura RenjithV This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14470) S3 Plugin publishing fails spontaneously
Theral Mackey commented on JENKINS-14470 S3 Plugin publishing fails spontaneously This appears to be related to our using multiple S3 Profiles. We have ~18 projects on the problematic Jenkins server, most using the S3 uploader. We have 3 profiles setup in the general config area for S3. 2 are identical with the second being setup when the first set appeared to fail (adding credentials seems to temporarily get it working again as well). The other set was added for a different S3 bucket on a different project. We have noticed that when most builds go "unstable" due to S3 uploads failing, this other project still works. After restarting Jenkins to get the other projects working again, this project fails. It looks like Jenkins is switching credential sets between projects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14470) S3 Plugin switches credential profiles
Theral Mackey updated JENKINS-14470 S3 Plugin switches credential profiles Change By: Theral Mackey (27/Jul/12 5:41 PM) Summary: S3Plugin publishingfailsspontaneously switchescredentialprofiles This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11968) Extending the EnvInject plugin
Aaron Stone updated JENKINS-11968 Extending the EnvInject plugin Change By: Aaron Stone (27/Jul/12 5:57 PM) Description: Itcouldbeveryconvenientifthe started-by-envvar plugincouldbeanextensionoftheEnvInjectplugin.TheEnvInjectJenkinspluginletsyoucontrolalltheenvironmentvariablesforthejob. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11968) Plugin started-by-envvar should extend the EnvInject plugin
Aaron Stone updated JENKINS-11968 Plugin started-by-envvar should extend the EnvInject plugin Change By: Aaron Stone (27/Jul/12 5:58 PM) Summary: Extending Pluginstarted-by-envvarshouldextend theEnvInjectplugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14251) Parent injected env properties not propagated to child build jobs
cjo9900 commented on JENKINS-14251 Parent injected env properties not propagated to child build jobs Environment injected parameter created following Gregory's comments. https://github.com/jenkinsci/parameterized-trigger-plugin/pull/23 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14610) Full Admin rights needed to run slave WebStart
jminne created JENKINS-14610 Full Admin rights needed to run slave WebStart Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: master-slave Created: 27/Jul/12 6:24 PM Description: I was working with a user yesterday to set up a slave node. I granted him all slave permissions (Configure, Delete, Create, Disconnect, Connect) and he was able to create the node. But it wasn't until I granted him Overall Administer that he was able to see the WebStart button in order to start the node (didn't want to run as a service because we were experimenting on his localhost.) Environment: Windows Project: Jenkins Priority: Major Reporter: jminne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14473) Jenkins server memory leak
Anoop Karollil commented on JENKINS-14473 Jenkins server memory leak Did some analysis using Eclipse's Memory Analyzer Tool with the heap dump attached. Report zip files and a PDF attached. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14473) Jenkins server memory leak
Anoop Karollil updated JENKINS-14473 Jenkins server memory leak Change By: Anoop Karollil (27/Jul/12 7:00 PM) Attachment: heapdump_Leak_Suspects.zip Attachment: heapdump_Top_Components.zip Attachment: heapdump_Top_Consumers.zip Attachment: heapdump_top_consumers_eclipse_memory_analyser.pdf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14473) Jenkins server memory leak
Anoop Karollil updated JENKINS-14473 Jenkins server memory leak Change By: Anoop Karollil (27/Jul/12 7:01 PM) Environment: Ubuntu7.10runningon32bitdualcore.JenkinswithWinstone. Javaversion1.6.0_03,Java(TM)SERuntimeEnvironment(build1.6.0_03-b05),JavaHotSpot(TM)ServerVM(build1.6.0_03-b05,mixedmode) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
Shawn M. Jones commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder I can report I am experiencing the problem as well with 1.475. Existing jobs created before the upgrade still work fine, but I cannot use the Parameterized Trigger plugin for new jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not
Nick Jones commented on JENKINS-13892 Analysis collector marks some warnings as fixed even though they are not We're having the same issue here, only with free-form .NET (MSBuild) jobs. I get 1593 warnings (long story) with 112 new warnings and 112 fixed warnings in every build, even with no code changes. For what it's worth, the MSBuild Warnings reports 246 warnings with 244 new and 244 fixed, again for every build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14611) S3 plugins lost after service restart, must be re-entered / saved
Iristyle created JENKINS-14611 S3 plugins lost after service restart, must be re-entered / saved Issue Type: Bug Assignee: Michael Watt Components: s3 Created: 27/Jul/12 10:00 PM Description: One of my co-workers also had found an issue with the use of statics which could lead to weird behavior, that I don't think was ever addressed: https://github.com/jenkinsci/s3-plugin/commit/469c5a281e7b01b941df4947fe00939150f04d93#commitcomment-1159411 Project: Jenkins Priority: Major Reporter: Iristyle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14611) S3 plugin credentials lost after service restart, must be re-entered / saved
Iristyle updated JENKINS-14611 S3 plugin credentials lost after service restart, must be re-entered / saved Change By: Iristyle (27/Jul/12 10:00 PM) Summary: S3 plugins plugincredentials lostafterservicerestart,mustbere-entered/saved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14607) URLTrigger Polling error null
SCM/JIRA link daemon commented on JENKINS-14607 URLTrigger Polling error null Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java src/main/java/org/jenkinsci/plugins/urltrigger/service/URLTriggerService.java http://jenkins-ci.org/commit/urltrigger-plugin/7d1194c5cde7d5419d608c1fbf80b01abfafddd2 Log: Fix JENKINS-14607 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14607) URLTrigger Polling error null
Gregory Boissinot started work on JENKINS-14607 URLTrigger Polling error null Change By: Gregory Boissinot (27/Jul/12 10:22 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14607) URLTrigger Polling error null
Gregory Boissinot commented on JENKINS-14607 URLTrigger Polling error null The error is due to that you don't have choose a content nature to check. I fixed in version 0.24 the error when the previous preconditions is not valid. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14607) URLTrigger Polling error null
Gregory Boissinot resolved JENKINS-14607 as Fixed URLTrigger Polling error null Change By: Gregory Boissinot (27/Jul/12 10:24 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14612) Auto Created users: Can't change password
Chandrasekhar Gopal created JENKINS-14612 Auto Created users: Cant change password Issue Type: Bug Assignee: Unassigned Components: security Created: 27/Jul/12 10:54 PM Description: I'm using Hudson's database for user management. We've enabled the checkbox for users to sign up and create user IDs. The issue we are facing is with auto created users. When we try to add a password (or for that matter if we try to edit) to an auto created user using the Configure link on the left hand side of the user administration window, the configure screen does not open up. I tried searching the JIRA DB to see if this is a known issue. I could not find any related posts. I'd appreciate if someone can look into this. Thanks, Chandra Environment: RHEL 6.1 Tomcat 7.0.25 Jenkins v1.449 Project: Jenkins Priority: Major Reporter: Chandrasekhar Gopal This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14613) Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository'
Steve Roth created JENKINS-14613 Maven job config page loses invoke top-level maven targets setting for use private repository Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 27/Jul/12 11:14 PM Description: Using Jenkins 1.473, I am seeing an issue in a Maven project, when I use the 'Invoke top-level Maven targets' pre-build step. When I add this pre-biuld step, it comes with the 'Use private Maven repository' option checked. If I uncheck this option, and save the job, when I re-open the job, I see it is checked again. So it appears that the config page is losing my persisted setting, and always setting it back to the checked mode. The net result is that if you are using the 'Invoke top-level Maven targets' pre-build step, and dont the 'use private mavne repository' option checked, then each time you change your maven job, you need to go and uncheck that option before you click save. Project: Jenkins Priority: Minor Reporter: Steve Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
