[JIRA] (JENKINS-43024) Improve pagination usability
Title: Message Title Justinas Urbanavicius updated an issue Jenkins / JENKINS-43024 Improve pagination usability Change By: Justinas Urbanavicius Component/s: delivery-pipeline-plugin Component/s: build-pipeline-plugin 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-43024) Improve pagination usability
Title: Message Title Justinas Urbanavicius created an issue Jenkins / JENKINS-43024 Improve pagination usability Issue Type: Improvement Assignee: Unassigned Components: build-pipeline-plugin Created: 2017/Mar/22 9:34 AM Labels: user-experience ux pagination Priority: Minor Reporter: Justinas Urbanavicius Currently pipeline pagination is always displayed at the top only. Would be really great if you could also have it at the bottom. So we would have pagination at the top and as well at the bottom. For lengthy pipelines that have pagination enabled, you mostly scroll to bottom to scan through the builds and if you don't find the build you are looking for, you need to scroll back to the top to use the pagination. That is very uncomfortable from the user perspective - annoying really. Add Comment
[JIRA] (JENKINS-24664) Execute phing target's only if build is not in status FAILURE
Title: Message Title Justinas Urbanavicius updated an issue Jenkins / JENKINS-24664 Execute phing target's only if build is not in status FAILURE Change By: Justinas Urbanavicius Allow to execute phing targets only if build is not failed.Currently if you run xUnit and build fails, all phing targets are executes no executed not depending on this it's status. A Checkbox to run phing targets only if Build is stable would be nice. 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-37274) mercurial changelog displays changes from previous commit but not current
Title: Message Title
Justinas Urbanavicius created an issue
Jenkins / JENKINS-37274
mercurial changelog displays changes from previous commit but not current
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
mercurial-plugin
Created:
2016/Aug/09 9:18 AM
Environment:
Linux debian 7.8 x64 mercurial plugin v1.56
Labels:
changelog changes mercurial
Priority:
Minor
Reporter:
Justinas Urbanavicius
when running a build, mercurial plugin retrieves changelog of current branch and displays latest changes in that branch.
Building in workspace /var/lib/jenkins/jobs/it/jobs/sit/workspace
[workspace] $ hg showconfig paths.default
[workspace] $ hg pull --rev release
pulling from /home/hg/it
no changes found
[workspace] $ hg update --clean --rev release
13 files updated, 0 files merged, 0 files removed, 0 files unresolved
[workspace] $ hg --config extensions.purge= clean --all
[workspace] $ hg log --rev . --template {node}
[workspace] $ hg log --rev . --template {rev}
[workspace] $ hg log --rev 5b974cd24b9c3b650392b430a0e6418aaf60edd6
changeset: 7030:5b974cd24b9c
branch: release
user:Justinas Urbanavicius
date:Tue Aug 09 11:02:55 2016 +0300
summary: Not quoting a scalar starting with the "%" indicator character is deprecated since Symfony 3.1 and will throw a ParseException in 4.0
[JIRA] (JENKINS-34587) better supoort for "tip" changelogs
Title: Message Title Justinas Urbanavicius closed an issue as Fixed fixed in v1.55 Jenkins / JENKINS-34587 better supoort for "tip" changelogs Change By: Justinas Urbanavicius Status: Open Closed Resolution: Fixed 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-34587) better supoort for "tip" changelogs
Title: Message Title Justinas Urbanavicius commented on JENKINS-34587 Re: better supoort for "tip" changelogs yes it's appears to be fixed in the latest version 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] [phing-plugin] (JENKINS-35354) global tool configuration is ignored
Title: Message Title Justinas Urbanavicius closed an issue as Not A Defect Jenkins / JENKINS-35354 global tool configuration is ignored Change By: Justinas Urbanavicius Status: Open Closed Resolution: Not A Defect 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] [phing-plugin] (JENKINS-35354) global tool configuration is ignored
Title: Message Title Justinas Urbanavicius created an issue Jenkins / JENKINS-35354 global tool configuration is ignored Issue Type: Bug Assignee: sogabe Attachments: phing-global-tool-configuration.PNG Components: phing-plugin Created: 2016/Jun/04 11:10 AM Environment: linux debian x64 wheezy Labels: phing Priority: Blocker Reporter: Justinas Urbanavicius I configured phing in global tool configuration to be run from vendor folder like so: but when starting a build, jenkins cannot find phing executable [workspace] $ phing -buildfile
[JIRA] [mercurial-plugin] (JENKINS-34587) better supoort for "tip" changelogs
Title: Message Title
Justinas Urbanavicius commented on JENKINS-34587
Re: better supoort for "tip" changelogs
Started by an SCM change
Building on master in workspace /var/lib/jenkins/jobs/dev/workspace
[workspace] $ hg showconfig paths.default
[workspace] $ hg pull
pulling from /home/hg/ITUVS-Sources/ituvs
searching for changes
no changes found
[workspace] $ hg update --clean --rev tip
221 files updated, 0 files merged, 44 files removed, 0 files unresolved
[workspace] $ hg --config extensions.purge= clean --all
[workspace] $ hg log --rev . --template {node}
[workspace] $ hg log --rev . --template {rev}
[workspace] $ hg log --rev 914d0242c942f5963ce4379845f457e8cbb91449
changeset: 6823:914d0242c942
branch: PP12181
user:Justinas Urbanavicius <.>
date:Tue May 03 13:58:04 2016 +0300
summary: Task 117456
[workspace] $ hg log --template "{desc|xmlescape}{file_adds|stringify|xmlescape}{file_dels|stringify|xmlescape}{files|stringify|xmlescape}{parents}\n" --rev tip:0 --follow --prune 914d0242c942f5963ce4379845f457e8cbb91449 --encoding UTF-8 --encodingmode replace
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] [mercurial-plugin] (JENKINS-34587) better supoort for "tip" changelogs
Title: Message Title Justinas Urbanavicius created an issue Jenkins / JENKINS-34587 better supoort for "tip" changelogs Issue Type: Improvement Assignee: Jesse Glick Components: mercurial-plugin Created: 2016/May/04 5:52 AM Environment: linux debian x64 Labels: scm mercurial tip changelog Priority: Minor Reporter: Justinas Urbanavicius Every time a build is triggered, scm plugin retrieves changes and stores them in changelog. If you create a build that is executed on every newest commit, for tag "tip". Scm plugin retrieves a huge list of all commits, the list should be limited to current branch and maybe 20 latest commits, but not hundreds like it does now. If the build fails, all of the users that where in those commits get notified, but only the last commiter
[JIRA] [mercurial-plugin] (JENKINS-22825) Support latesttag in Mercurial
Title: Message Title Justinas Urbanavicius commented on JENKINS-22825 Re: Support latesttag in Mercurial A. Klitzing oh you meant the latest tag from all the tags, the newest tag so to say, i thought you need the latest revision of the repository, sorry 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] [mercurial-plugin] (JENKINS-22825) Support latesttag in Mercurial
Title: Message Title Justinas Urbanavicius commented on JENKINS-22825 Re: Support latesttag in Mercurial mercurial has a built in latest tag it's called "tip", you can specify it as the tag name and it will always build the latest comitted revision. 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] [phing-plugin] (JENKINS-19110) phing is executed incorrectly
Title: Message Title Justinas Urbanavicius commented on JENKINS-19110 Re: phing is executed incorrectly any progress on 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] [phing-plugin] (JENKINS-19110) phing is executed incorrectly
Title: Message Title Justinas Urbanavicius commented on JENKINS-19110 Re: phing is executed incorrectly i've tried all the version of plugin, and the only version that works correctly is 0.12: [build] $ phing -buildfile /var/lib/jenkins/jobs/dev/workspace/build/build.xml test -Denvironment=dev -Dbuild_number=361 -logger phing.listener.DefaultLogger Buildfile: /var/lib/jenkins/jobs/dev/workspace/build/build.xml 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] [phing-plugin] (JENKINS-19110) phing is executed incorrectly
Title: Message Title Justinas Urbanavicius commented on JENKINS-19110 Re: phing is executed incorrectly Using Jenkins v1.614, phing plugin 0.13.3, java 1.7.0_79 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] [phing-plugin] (JENKINS-19110) phing is executed incorrectly
Title: Message Title
Justinas Urbanavicius commented on JENKINS-19110
Re: phing is executed incorrectly
in the latest version of plugin 0.13.3 the issue is back and even if the phing is not configured in global settings:
output: {{usr/bin/php phing -buildfile /var/lib/jenkins/jobs/dev/workspace/build/build.xml -Denvironment=dev -Dbuild_number=356 test -logger phing.listener.DefaultLogger Could not open input file: phing}}
somehow it tires to execute phing sh script through php either it has to run phing command or /usr/bin/php phing.php it's starting to get really annoying
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] [phing-plugin] (JENKINS-19110) phing is executed incorrectly
Title: Message Title
Justinas Urbanavicius edited a comment on JENKINS-19110
Re: phing is executed incorrectly
inthelatestversionofplugin0.13.3theissueisbackandevenifthephingisnotconfiguredinglobalsettings:output:{ { code} usr/bin/phpphing-buildfile/var/lib/jenkins/jobs/dev/workspace/build/build.xml-Denvironment=dev-Dbuild_number=356test-loggerphing.listener.DefaultLoggerCouldnotopeninputfile:phing {code } } somehowittirestoexecutephingshscriptthroughphpeitherithastorunphingcommandor/usr/bin/phpphing.phpit'sstartingtogetreallyannoying
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] [phing] (JENKINS-24664) Execute phing target's only if build is not in status FAILURE
Justinas Urbanavicius created JENKINS-24664 Execute phing targets only if build is not in status FAILURE Issue Type: Improvement Affects Versions: current Assignee: sogabe Components: phing Created: 11/Sep/14 6:37 AM Description: Allow to execute phing targets only if build is not failed. Currently if you run xUnit and build fails, all phing targets are executes no not depending on this status. A Checkbox to run phing targets only if Build stable would be nice. Project: Jenkins Labels: phing failed status execute Priority: Major Reporter: Justinas Urbanavicius 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] [active-directory] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
Justinas Urbanavicius commented on JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException can't really remember but i think with angry jenkins, it looks familiar 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] [active-directory] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
Justinas Urbanavicius commented on JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException i totally agree with you. I've seen some applications that display a user friendly error and have a link or a button "more details" that then clicked, shows the stack trace and error code or more related information, that is helpful for developers. It's both user friendly and informative. 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] [active-directory] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
Justinas Urbanavicius commented on JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException yes, by saying, that it took down jenkins, i mean, i got a page, that looked mutilated, with stack trace, and i couldn't navigate from that page, except for forward back buttons on the browser, that didn't really help, until the connection got restored after a few refreshes. an error message with explanation and server's name would be really appreciated and more informative to me as the end user and anyone that does not know java. 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] [active-directory] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
Justinas Urbanavicius commented on JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException I would expect a message, saying that jenkins cannot connect to active directory, probably due to connection failure, not to take down whole jenkins CI server throwing an expection wouldn't it be more logical ? 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] [mercurial] (JENKINS-24136) Add support for build/release tagging with bookmarks
Justinas Urbanavicius created JENKINS-24136 Add support for build/release tagging with bookmarks Issue Type: New Feature Assignee: Jesse Glick Components: mercurial Created: 06/Aug/14 12:48 PM Description: Would be nice if mercurial plugin could add a biuld action, that would bookmark a successful build with specified version number, like build number, from jenkins environment variables and push to the repository. that way after a build we could see by the bookmark in repository witch revision was build, which revision is the current release. Project: Jenkins Labels: tag bookmarks release build-action Priority: Major Reporter: Justinas Urbanavicius 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] [phing] (JENKINS-20835) calling phing long running targets spawns new phing processes endlessly
Justinas Urbanavicius updated JENKINS-20835 calling phing long running targets spawns new phing processes endlessly Change By: Justinas Urbanavicius (31/Jan/14 6:31 AM) Summary: callingphinglongrunningtargets spawn spawns newphingprocesses enlessly endlessly 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] [phing] (JENKINS-20835) calling phing long running targets spawns new phing processes endlessly
Justinas Urbanavicius commented on JENKINS-20835 calling phing long running targets spawns new phing processes endlessly where are the logs physically located ? Jenkins does not show whole log, and since the issue is quite old i can't find anything about it in the short fragment that is displayed 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] [phing] (JENKINS-20835) calling phing long running targets spawns new phing processes endlessly
Justinas Urbanavicius edited a comment on JENKINS-20835 calling phing long running targets spawns new phing processes endlessly where are the logs physically located ? Jenkins does not show whole log, and since the issue is quite old i can't find anything about it in the short fragment that is displayed. ok, found it in /var/log/jenkins attaching log files 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] [tfs] (JENKINS-4021) TFS - unparseable date problem
Justinas Urbanavicius commented on JENKINS-4021 TFS - unparseable date problem I personally don't agree that implementing a heuristic parser is a good idea, it most likely will create more problems than solve. User set locale in configuration sounds as a better and more simple solution. 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] [tfs] (JENKINS-4021) TFS - unparseable date problem
Justinas Urbanavicius edited a comment on JENKINS-4021 TFS - unparseable date problem I personally don't agree that implementing a heuristic parser is a good idea, it most likely will create more problems than solve. User set locale in configuration sounds as a better and more simple solution. In some cases, then your build system is set up on a different environment, you might not even have the same locales, like building on Linux for example. 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-8152) LDAP config error
justinas Urbanavicius reopened JENKINS-8152 LDAP config error the problem is back in Jenkins v1.546 LDAP plugin v1.7 if Root DN contains a space it throws exception that root DNs must be the same javax.servlet.ServletException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'initialDirContextFactory': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.acegisecurity.ldap.DefaultInitialDirContextFactory]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: Root DNs must be the same when using multiple URLs at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) 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 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:48) 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 hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at
[JIRA] [core] (JENKINS-14960) Jenkins crash, leaving apache responding Server Unavailable
justinas Urbanavicius commented on JENKINS-14960 Jenkins crash, leaving apache responding Server Unavailable it might be related to JENKINS-20816, last time crash occurred i got this error, described in that bug report, that jenkin's ActiveDirectory plugin Failed to retrieve user information from Active Directory 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-14960) Jenkins crash, leaving apache responding Server Unavailable
justinas Urbanavicius commented on JENKINS-14960 Jenkins crash, leaving apache responding Server Unavailable It appears definitely related, every time jenkins crashes i see that error in jenkins.log. So looks like Active Directory plugin kills jenkins, IMHO that shouldn't happen, ever. 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-14960) Jenkins crash, leaving apache responding Server Unavailable
justinas Urbanavicius commented on JENKINS-14960 Jenkins crash, leaving apache responding Server Unavailable got the same issue running jenkins v1.546, although it was also in previous versions. I also installed jenkins from .deb package on linux Debian. One thing that i notices that from v 1.500 crashes seem to be gotten more frequent. And everytime jenkins goes down, only thing that can restore jenkins service restart, it's as if the jetty itself crashes, but there is no errors in /var/log/jenkins.log related to the crash, attaching log just in case. 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-14960) Jenkins crash, leaving apache responding Server Unavailable
justinas Urbanavicius updated JENKINS-14960 Jenkins crash, leaving apache responding Server Unavailable Change By: justinas Urbanavicius (09/Jan/14 7:27 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 -- 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-14960) Jenkins crash, leaving apache responding Server Unavailable
justinas Urbanavicius edited a comment on JENKINS-14960 Jenkins crash, leaving apache responding Server Unavailable got the same issue running jenkins v1.546, although it was also in previous versions. I also installed jenkins from .deb package on linux Debian. One thing that i noticed that from v 1.500 crashes seem to have gotten more frequent. And every time jenkins goes down, the only thing that can restore it, is a jenkins service restart, it's as if the jetty itself crashes, but there is no errors in /var/log/jenkins.log related to the crash, attaching log just in case. is there a way to get more info, turn on a jetty log perhaps? 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] [active-directory] (JENKINS-21297) Add cache support like in ldap plugin
justinas Urbanavicius created JENKINS-21297 Add cache support like in ldap plugin Issue Type: New Feature Assignee: Unassigned Components: active-directory Created: 09/Jan/14 7:37 AM Description: consider adding caching support like in LDAP plugin. to allow caching auth. for some time, to decrease load of Active Directory. Project: Jenkins Priority: Major Reporter: justinas Urbanavicius 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-17193) Missing Delete button
justinas Urbanavicius edited a comment on JENKINS-17193 Missing Delete button Gregory Boissinot, did you add more then one build action, xUnit being the last one ? 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-17193) Missing Delete button
justinas Urbanavicius commented on JENKINS-17193 Missing Delete button Did you add more then one build action, xUnit being the last one ? 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] [phing] (JENKINS-20835) calling phing long running targets spawn new phing processes enlessly
justinas Urbanavicius created JENKINS-20835 calling phing long running targets spawn new phing processes enlessly Issue Type: Bug Assignee: sogabe Attachments: Capture.PNG Components: phing Created: 02/Dec/13 11:24 AM Description: When calling phing long running targets jenkins spawns many processes of phing concurently, it's like a fork bomb. My server has about 52-81 processes usually, after executing phing task that copies DB from one server to another (it takes about 20minutes) i see about 1000-5000 processes executed by jenkins all calling phing and system just runs out of memory. Environment: Jenkins 1.541 Linux Debian x64 Phing v2.71 Project: Jenkins Labels: phing fork bomb Priority: Blocker Reporter: justinas Urbanavicius 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] [phing] (JENKINS-20835) calling phing long running targets spawn new phing processes enlessly
justinas Urbanavicius updated JENKINS-20835 calling phing long running targets spawn new phing processes enlessly Change By: justinas Urbanavicius (02/Dec/13 11:47 AM) Attachment: Capture.PNG 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] [ldap] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
justinas Urbanavicius created JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap, security Created: 29/Nov/13 6:50 AM Description: I suspect the ActiveDirectory server went down, and jenkins tried to authenticate currently logged on user and failed throwing this exception. Stack trace: org.acegisecurity.BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: my.domainserver.xx:389 [Root exception is java.net.ConnectException: Connection refused]] at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:309) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:193) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:137) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:30) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loadUserDetails(TokenBasedRememberMeServices.java:308) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:218) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$1.autoLogin(ActiveDirectorySecurityRealm.java:140) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) 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 hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at
[JIRA] [maven] (JENKINS-20676) Project configuration throws exception if maven module is disabled
justinas Urbanavicius created JENKINS-20676 Project configuration throws exception if maven module is disabled Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 20/Nov/13 3:12 PM Description: If you disable maven plugin, and open configuration of a project you will see jetty exception. It does not matter if project uses or not maven. Mine did not, but configuration page still tried to load maven, which was disabled as i don't use it. WARNING: Failed to load hudson.maven.MavenModuleSet java.lang.InstantiationException: java.lang.NoClassDefFoundError: Could not initialize class hudson.maven.MavenModuleSet$DescriptorImpl at net.java.sezpoz.IndexItem.instance(IndexItem.java:193) at hudson.ExtensionFinder$GuiceFinder.instantiate(ExtensionFinder.java:355) at hudson.ExtensionFinder$GuiceFinder.access$700(ExtensionFinder.java:234) at hudson.ExtensionFinder$GuiceFinder$SezpozModule$1.get(ExtensionFinder.java:531) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:66) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382) at hudson.ExtensionFinder._find(ExtensionFinder.java:151) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:317) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.getComponents(ExtensionList.java:149) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at org.jenkinsci.plugins.xunit.AliasInitializer.addAliases(AliasInitializer.java:23) 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:616) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[JIRA] [phing] (JENKINS-17668) Windows phing is broken, jenkins tries to execute phing.bat with php.exe
justinas Urbanavicius created JENKINS-17668 Windows phing is broken, jenkins tries to execute phing.bat with php.exe Issue Type: Bug Affects Versions: current Assignee: sogabe Components: phing Created: 18/Apr/13 4:18 PM Description: prior to v0.13 phing is run through phing.bat, in v0.13 phing is run through php.exe phing.bat, either .bet extension should be removed or php.exe: Console output: cmd.exe /C '"c:\php53\php.exe phing.bat -buildfile . Environment: Windows Server 2008 R2 x64 Project: Jenkins Labels: windows phing php Priority: Blocker Reporter: justinas Urbanavicius 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] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius commented on JENKINS-17353 problem with summary encoding Works as expected, see attached screen shots, 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/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius updated JENKINS-17353 problem with summary encoding Change By: justinas Urbanavicius (27/Mar/13 7:52 AM) Attachment: Jenkinsstatus.PNG Attachment: jenkinssummary.PNG 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] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius created JENKINS-17353 problem with summary encoding Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Attachments: Capture.PNG Components: mercurial Created: 26/Mar/13 9:59 AM Description: When displaying summary of changes unicode characters are displayed incorrectly. Browser encoding is set o Unicode. Environment: Windows Server 2008 R2 x64 Project: Jenkins Labels: mercurial encoding unicode Priority: Minor Reporter: justinas Urbanavicius 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] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius commented on JENKINS-17353 problem with summary encoding i commit through netbeans IDE and not sure what encoding it does use, i presume it uses utf-8, as it would be a wise choice and mercurial's rhodecode UI displays these messages correctly so i think the problem is on Jenkins side and you should definitely use UTF-8 by default. also mercurial does define encoding it defaults to UTF-8: UTF-8 strings are used to store most repository metadata. Unlike repository contents, repository metadata is 'owned and managed' by Mercurial and can be made to conform to its rules. In particular, this includes: commit messages stored in the changelog user names tags branches The following files are stored in UTF-8: .hgtags .hg/branch .hg/branchheads.cache .hg/tags.cache .hg/bookmarks 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] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius commented on JENKINS-17353 problem with summary encoding sound good, will wait for a fix file-names are not my main concern as all file-names in my repository have only latin alphabet chars. 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] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius commented on JENKINS-17353 problem with summary encoding hmm, that's strange, as i said, mercurial rhodecode reads commit messages just fine, and displays them correctly, and it runs on Linux Debian. 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] (JENKINS-17193) Missing Delete button
justinas Urbanavicius commented on JENKINS-17193 Missing Delete button v1.503 after update to v1.505 the button was still 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] (JENKINS-17192) Add support for phpunit3 coverage
justinas Urbanavicius commented on JENKINS-17192 Add support for phpunit3 coverage that explains it, i had type set to xml: type"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] (JENKINS-17193) Missing Delete button
justinas Urbanavicius commented on JENKINS-17193 Missing Delete button Try adding more post build actions and clover coverage action as last 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] (JENKINS-17193) Missing Delete button
justinas Urbanavicius updated JENKINS-17193 Missing Delete button Added screenshot with full config visible, and all actions Change By: justinas Urbanavicius (14/Mar/13 7:41 AM) Attachment: FireShotScreenCapture#001-SITConfig[Jenkins].png 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] (JENKINS-17193) Missing Delete button
justinas Urbanavicius commented on JENKINS-17193 Missing Delete button you are right it does. Should i re-register this bug with xUnit ? 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] (JENKINS-17037) Null pointer exception when publishing results
justinas Urbanavicius commented on JENKINS-17037 Null pointer exception when publishing results I'm actually using phpunit 3.7, so you are saying that phpunit3 is not compatible with clover. Shouldn't it just skip the clover generation instead of an error, and put out some kind of a warning that unsupported format ? instead of exception and failing the 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 -- 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] (JENKINS-17192) Add support for phpunit3 coverage
justinas Urbanavicius created JENKINS-17192 Add support for phpunit3 coverage Issue Type: New Feature Affects Versions: current Assignee: sogabe Components: cloverphp-plugin Created: 13/Mar/13 12:34 PM Description: Please consider adding support for PHPUnit 3.x version, it's been available quite some time now, i doubt anyone is still using PHPUnit 2 Environment: Windows server 2008 R2 x64 Project: Jenkins Labels: plugin clover phpunit Priority: Major Reporter: justinas Urbanavicius 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] (JENKINS-17193) Missing Delete button
justinas Urbanavicius created JENKINS-17193 Missing Delete button Issue Type: Bug Affects Versions: current Assignee: sogabe Attachments: Capture.PNG Components: cloverphp-plugin Created: 13/Mar/13 12:39 PM Description: if "Publish clover PHP coverage report" added as post build action, there is no way to remove it, the delete button is missing. Environment: Windows Server 2008 R2 x64 Project: Jenkins Labels: delete button post-build Priority: Minor Reporter: justinas Urbanavicius 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] (JENKINS-17037) Null pointer exception when publishing results
justinas Urbanavicius created JENKINS-17037 Null pointer exception when publishing results Issue Type: Bug Affects Versions: current Assignee: sogabe Components: cloverphp-plugin Created: 04/Mar/13 8:50 AM Description: ERROR: Publisher org.jenkinsci.plugins.cloverphp.CloverPublisher aborted due to exception java.lang.NullPointerException at org.jenkinsci.plugins.cloverphp.CloverCoverageParser.trimPaths(CloverCoverageParser.java:29) at org.jenkinsci.plugins.cloverphp.CloverCoverageParser.parse(CloverCoverageParser.java:50) at org.jenkinsci.plugins.cloverphp.CloverPublisher.processCloverXml(CloverPublisher.java:216) at org.jenkinsci.plugins.cloverphp.CloverPublisher.perform(CloverPublisher.java:189) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Finished: FAILURE Environment: Windows Server 2008 R2 x64 Project: Jenkins Priority: Major Reporter: justinas Urbanavicius 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] (JENKINS-17007) can't set password in repository URL
justinas Urbanavicius created JENKINS-17007 cant set password in repository URL Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: mercurial Created: 28/Feb/13 4:20 PM Description: if you specify username and password in repository url you get error: nonnumeric port: 'servername' $ hg clone --rev default --noupdate http://jenkins@password:servername/hg D:\www\ituvs\sit abort: error: nonnumeric port: 'servername' Environment: Windows Server 2008 R2 SP1 x64 Project: Jenkins Priority: Major Reporter: justinas Urbanavicius 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] (JENKINS-16593) Error: TF203003: You cannot specify a wildcard character for this working folder.
justinas Urbanavicius created JENKINS-16593 Error: TF203003: You cannot specify a wildcard character for this working folder. Issue Type: Bug Affects Versions: current Assignee: redsolo Components: tfs Created: 01/Feb/13 11:01 AM Description: sit $ "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\TF.exe" workspace -delete project_main2-SIT;domain\user1 -noprompt -server:http://srtfs:8080/tfs/CMP sit $ "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\TF.exe" workspace -new project_main2-SIT;domain\user1 -noprompt -server:http://srtfs:8080/tfs/CMP sit $ "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\TF.exe" workfold -map "$/ISV - 2.1 Inf systems/myproject/project_main2" . -workspace:project_main2-SIT -server:http://srtfs:8080/tfs/CMP TF203003: You cannot specify a wildcard character for this working folder. The only wildcard character allowed is an '*' to map a Team Foundation Server folder and its immediate child items to your workspace. FATAL: Executable returned an unexpected result code 100 Environment: Windows Server 2008 x64 Project: Jenkins Priority: Blocker Reporter: justinas Urbanavicius 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] (JENKINS-4021) TFS - unparseable date problem
justinas Urbanavicius commented on JENKINS-4021 TFS - unparseable date problem Any progress on this issue ? having the same problem on windows 2008 server with Jenkins 1.5 and latest plugin 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.
