[JIRA] (JENKINS-59753) Error cloning remote repo
Title: Message Title Per Östman commented on JENKINS-59753 Re: Error cloning remote repo We're seeing a similar issue, only our jobs work when triggered from GitLab push trigger (using SSH checkout), but when triggered from parameterized scheduler trigger, somehow https checkout is used (which cause failure) The same error occurs occasionally when triggering manually. Would be great to see some investigation into this! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202476.1570810205000.672.1581944820216%40Atlassian.JIRA.
[JIRA] (JENKINS-6268) Make checking for modification time of junit results be configurable and off by default
Title: Message Title Per Östman commented on JENKINS-6268 Re: Make checking for modification time of junit results be configurable and off by default This one is nine (9) years old. Come on, please fix this! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16648) changes-since-last-success plugin doesn't work
Title: Message Title Per Östman edited a comment on JENKINS-16648 Re: changes-since-last-success plugin doesn't work I too cannot find any options to configure this plugin. Using Jenkins 2 - is it verified to work in Jenkins 2? I get the same error as the reporter of this bug - a 404 Not Found, and no buiild action seem to be available. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16648) changes-since-last-success plugin doesn't work
Title: Message Title Per Östman reopened an issue See comment. Jenkins / JENKINS-16648 changes-since-last-success plugin doesn't work Change By: Per Östman Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16648) changes-since-last-success plugin doesn't work
Title: Message Title Per Östman commented on JENKINS-16648 Re: changes-since-last-success plugin doesn't work I too cannot find any options to configure this plugin. Using Jenkins 2 - is it verified to work in Jenkins 2? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41749) Using regular expression to specify what jobs to include does not seem to work
Title: Message Title Per Östman closed an issue as Fixed Jenkins / JENKINS-41749 Using regular _expression_ to specify what jobs to include does not seem to work Change By: Per Östman Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41749) Using regular expression to specify what jobs to include does not seem to work
Title: Message Title Per Östman commented on JENKINS-41749 Re: Using regular _expression_ to specify what jobs to include does not seem to work Does this mean it should be fixed in 1.4? How would one specify a filter that would only show particular branches of a multibranch pipeline job ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41749) Using regular expression to specify what jobs to include does not seem to work
Title: Message Title Per Östman created an issue Jenkins / JENKINS-41749 Using regular _expression_ to specify what jobs to include does not seem to work Issue Type: Bug Assignee: Paul Horvath Components: pipeline-aggregator-view-plugin Created: 2017/Feb/06 9:45 AM Priority: Blocker Reporter: Per Östman When trying to use a regular _expression_ to select jobs to include in this view, no jobs are shown. E g a regular _expression_ of tsas., or ^tsas. yields empty list although it should not since there is a job named "tsas_multibranch_pipe". Add Comment
[JIRA] (JENKINS-35409) Build Monitor - Ability to re-order the build card positions and save
Title: Message Title Per Östman commented on JENKINS-35409 Re: Build Monitor - Ability to re-order the build card positions and save I would also find this very useful. Sort order of cards/lozenges today seem to be based on alphbetical order of the job name. So one cannot influence this by e g changing the display name. Best would be to have a nice way to define the order of appearance of the cards. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41007) When choosing option "Notification message includes: commit list with authors and titles", two separate messages are sent
Title: Message Title Per Östman created an issue Jenkins / JENKINS-41007 When choosing option "Notification message includes: commit list with authors and titles", two separate messages are sent Issue Type: Bug Assignee: Kurt Madel Components: slack-plugin Created: 2017/Jan/11 10:48 PM Environment: Plugin: 2.1 Jenkins: 2.19.1 Priority: Major Reporter: Per Östman Repro steps: In a build job that contains tests, selecte the options listed in attached screen shot; Run the job and watch the slack messages sent Result: Two slack messages are sent, one with the build and test results combined, and one with the commit list with authors and titles Expected: One message containing all info Rationale: Since the test summary is merged into the first message, one would expect the commit list to behave in the same way.
[JIRA] (JENKINS-38657) Make this available as a pipeline step
Title: Message Title Per Östman created an issue Jenkins / JENKINS-38657 Make this available as a pipeline step Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger-plugin Created: 2016/Oct/03 10:45 AM Priority: Major Reporter: Per Östman I'd really appreciate if this plugin were made available as a pipeline step. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] [violations-plugin] (JENKINS-34205) Add support for workflow/pipeline to the violations plugin
Title: Message Title Per Östman commented on JENKINS-34205 Re: Add support for workflow/pipeline to the violations plugin Second this - please add this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [violations-plugin] (JENKINS-34205) Add support for workflow/pipeline to the violations plugin
Title: Message Title Per Östman updated an issue Jenkins / JENKINS-34205 Add support for workflow/pipeline to the violations plugin Change By: Per Östman Labels: workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim-plugin] (JENKINS-33078) The "Claim it" link does not work when apostrophe used in any failure cause
Title: Message Title Per Östman commented on JENKINS-33078 Re: The "Claim it" link does not work when apostrophe used in any failure cause I can confirm that we see the same issue. Please fix. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay-plugin] (JENKINS-27348) Add support for displaying "Display Name"
Title: Message Title Per Östman closed an issue as Fixed Jenkins / JENKINS-27348 Add support for displaying "Display Name" Change By: Per Östman Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-27841) Cannot connect to MongoDB
Title: Message Title Per Östman closed an issue as Not A Defect Jenkins / JENKINS-27841 Cannot connect to MongoDB Change By: Per Östman Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26657) File context menu missing when installing Slave under windows with jnlp
Title: Message Title Per Östman commented on JENKINS-26657 Re: File context menu missing when installing Slave under windows with jnlp We are facing this same issue. Slave on Windows Server 2012 R2, Master on CentOs. Creating a slave using web start, downloading jnlp. When running the jnlp, the dialog states "Connected", but there is no menu for installing as service, and on the master, the slave is not shown as connected I also face this issue with already defined slaves that used to work before, but are now showing as disconnected, although their windows service is running. Are there any ideas on why this is, how it can be circumvented and if there is a fix in sight? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26657) File context menu missing when installing Slave under windows with jnlp
Title: Message Title Per Östman commented on JENKINS-26657 Re: File context menu missing when installing Slave under windows with jnlp Update; after restarting the master, slaves are able to connect, but the menu option is till not visible... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor-plugin] (JENKINS-24518) Define different colors to unstable and aborted statuses
Title: Message Title Per Östman commented on JENKINS-24518 Re: Define different colors to unstable and aborted statuses It would also be useful to have a separate color if a build has been claimed - as opposed to today, where claimed builds get the same look as the colorblind mode. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim-plugin] (JENKINS-31184) Make bug ID references in claim message clickable
Title: Message Title Per Östman created an issue Jenkins / JENKINS-31184 Make bug ID references in claim message clickable Issue Type: Improvement Assignee: Christian Bremer Components: claim-plugin Created: 27/Oct/15 11:58 AM Priority: Major Reporter: Per Östman It would be really nice if when one enters a bug-ID in the claim message, the bug ID becomes clickable - like in JIRA when one enters a bug ID in the description. Add Comment This
[JIRA] [sctmexecutor-plugin] (JENKINS-28304) save build step failed
Title: Message Title Per Östman commented on JENKINS-28304 Re: save build step failed It probably is, and the workaround works for now. However, it's important to fix the root cause though... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sctmexecutor-plugin] (JENKINS-28304) save build step failed
Title: Message Title Per Östman commented on JENKINS-28304 Re: save build step failed Is anyone looking into this issue? I see the same behavior (running Jenkins 1.609.3) This effectively blocks any use of this plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sctmexecutor-plugin] (JENKINS-28304) save build step failed
Title: Message Title Per Östman updated an issue Jenkins / JENKINS-28304 save build step failed Change By: Per Östman Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [zentimestamp-plugin] (JENKINS-26958) ZenTimestamper throws ClassCastException when used in combination with the new Workflow plugin
Title: Message Title Per stman commented on JENKINS-26958 Re: ZenTimestamper throws ClassCastException when used in combination with the new Workflow plugin Bumping this. We use Zen timestamper, and wish to use workflow plugin, but this bug effectively prevents this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parallel-test-executor-plugin] (JENKINS-28285) Not possible for the test job to copy artifacts from the job calling the test job
Title: Message Title Per stman created an issue Jenkins / JENKINS-28285 Not possible for the test job to copy artifacts from the job calling the test job Issue Type: Bug Assignee: Unassigned Components: parallel-test-executor-plugin Created: 07/May/15 1:21 PM Priority: Minor Reporter: Per stman I might have understood how this plugin is supposed to be set up but; I have a job that compiles the source to binaries and archives these, and a job that performs the tests, where the latter requires the artifacts from the former. Now, since this plugin is only exposed as a build step, and there is not (to my knowledge) possible to archive the artifacts unless as a post-build step - it seems impossible for the test job to be able to retrieve the artifacts needed to execute the tests? The only way I can imagine is for the test job to be configured so that it executes in the same workspace as the compile job, but then it becomes impossible for the test job to be parallellized across multiple slaves?
[JIRA] [parallel-test-executor-plugin] (JENKINS-28285) Not possible for the test job to copy artifacts from the job calling the test job
Title: Message Title Per stman updated an issue Jenkins / JENKINS-28285 Not possible for the test job to copy artifacts from the job calling the test job Change By: Per stman Imighthave understood misunderstood howthispluginissupposedtobesetupbut;Ihaveajobthatcompilesthesourcetobinariesandarchivesthese,andajobthatperformsthetests,wherethelatterrequirestheartifactsfromtheformer.Now,sincethispluginisonlyexposedasabuildstep,andthereisnot(tomyknowledge)possibletoarchivetheartifactsunlessasapost-buildstep-itseemsimpossibleforthetestjobtobeabletoretrievetheartifactsneededtoexecutethetests?TheonlywayIcanimagineisforthetestjobtobeconfiguredsothatitexecutesinthesameworkspaceasthecompilejob,butthenitbecomesimpossibleforthetestjobtobeparallellizedacrossmultipleslaves? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-27841) Cannot connect to MongoDB
Per Östman commented on JENKINS-27841 Cannot connect to MongoDB It appears as if our DBA setup this MongoDB without need for providing credentials. This failure occurred when I tried to use BFA with credentials, but when I connect without providing credentials, it worked. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit2db-plugin] (JENKINS-27224) Generating DDL file does not work
Per Östman commented on JENKINS-27224 Generating DDL file does not work Is there anyone triaging the issues in this plugin? Environment when this occurs is CentOS (on the jenkins master) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-27841) Cannot connect to MongoDB
Per Östman created JENKINS-27841 Cannot connect to MongoDB Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 08/Apr/15 11:26 AM Description: Repro steps: Installed latest Mongo DB (3.0.1) Configured BFA to use MongoDB using correct credentials (verified URL, port credentials using the Mongo client tool) Pressed "Test Connection" Result: Could not connect javax.naming.AuthenticationException: Could not athenticate with the mongo database at com.sonyericsson.jenkins.plugins.bfa.db.MongoDBKnowledgeBase.getDb(MongoDBKnowledgeBase.java:1080) at com.sonyericsson.jenkins.plugins.bfa.db.MongoDBKnowledgeBase.getCollection(MongoDBKnowledgeBase.java:1094) at com.sonyericsson.jenkins.plugins.bfa.db.MongoDBKnowledgeBase.access$000(MongoDBKnowledgeBase.java:90) at com.sonyericsson.jenkins.plugins.bfa.db.MongoDBKnowledgeBase$MongoDBKnowledgeBaseDescriptor.doTestConnection(MongoDBKnowledgeBase.java:1235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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:123) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:43) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) 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:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at
[JIRA] [audit2db-plugin] (JENKINS-27224) Generating DDL file does not work
Per Östman updated JENKINS-27224 Generating DDL file does not work Change By: Per Östman (02/Apr/15 10:07 AM) 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/d/optout.
[JIRA] [audit2db-plugin] (JENKINS-27224) Generating DDL file does not work
Per Östman updated JENKINS-27224 Generating DDL file does not work Change By: Per Östman (02/Apr/15 10:08 AM) Priority: Critical Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit2db-plugin] (JENKINS-27224) Generating DDL file does not work
Per Östman updated JENKINS-27224 Generating DDL file does not work Change By: Per Östman (11/Mar/15 8:32 AM) Description: *Createddatabaseforplugintouse*Installedtheaudit2dbplugin*Copieddatabasedriver(SQLServerandOracle)toplugin_folder/WEB-INF/lib*ChangedownerandgroupforthetwodriverstotheaccountrunningJenkins*VerifiedthatpluginhomefolderisownedbyaccountrunningJenkins*RestartedJenkins*Configuredplugintousedatabase(triedbothOracleandSQLServer)*Verifiedtestconnectiontodatabaseworks*ClickedonbuttontogenerateDDLResult:Error:jenkins_audit2db. dll ddl (Nosuchfileordirectory)Expected:Filetobecreatedanddisplayed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay-plugin] (JENKINS-27348) Add support for displaying Display Name
Per Östman created JENKINS-27348 Add support for displaying Display Name Issue Type: Bug Assignee: Christian Pelster Components: walldisplay-plugin Created: 11/Mar/15 9:23 AM Description: Sometimes, the job name is not suitable for display - e g when the job names follow a certain scheme to allow for efficient filtering in views. In these cases, it would be handy to have an option to tell the Walldisplay to show the job's "Display Name" instead. Project: Jenkins Priority: Minor Reporter: Per Östman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit2db-plugin] (JENKINS-27224) Generating DDL file does not work
Per Östman updated JENKINS-27224 Generating DDL file does not work Change By: Per Östman (03/Mar/15 2:50 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit2db-plugin] (JENKINS-27224) Generating DDL file does not work
Per Östman created JENKINS-27224 Generating DDL file does not work Issue Type: Bug Assignee: Unassigned Components: audit2db-plugin Created: 03/Mar/15 2:50 PM Description: Created database for plugin to use Installed the audit2db plugin Copied database driver (SQLServer and Oracle) to plugin_folder/WEB-INF/lib Changed owner and group for the two drivers to the account running Jenkins Verified that plugin home folder is owned by account running Jenkins Restarted Jenkins Configured plugin to use database (tried both Oracle and SQLServer) Verified test connection to database works Clicked on button to generate DDL Result: Error: jenkins_audit2db.dll (No such file or directory) Expected: File to be created and displayed Environment: Jenkins master on CentOS 6.6 Project: Jenkins Priority: Minor Reporter: Per Östman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
