[JIRA] (JENKINS-39823) Update Version History for 2.1.9 on Credentials+Plugin wiki page
Title: Message Title Jakub Czaplicki updated an issue Jenkins / JENKINS-39823 Update Version History for 2.1.9 on Credentials+Plugin wiki page Change By: Jakub Czaplicki The version history is missing for recently released 2.1.9 on https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin 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-39823) Update Version History for 2.1.9 on Credentials+Plugin wiki page
Title: Message Title Jakub Czaplicki created an issue Jenkins / JENKINS-39823 Update Version History for 2.1.9 on Credentials+Plugin wiki page Issue Type: Task Assignee: Stephen Connolly Components: credentials-plugin Created: 2016/Nov/17 1:26 PM Priority: Minor Reporter: Jakub Czaplicki Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title Jakub Czaplicki commented on JENKINS-39723 Re: BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) Possibly. This plugin has so many names that I wouldn't be surprised if the black mirrors got confused: CloudBees Docker Pipeline , docker-workflow, and now just Docker Pipeline Plugin Actually the day I've hit the issue described in this ticket, the docker-workflow plugin changed it name, so that's what probably caused the plugin not to be visible in my repo : Version history Version 1.9.1 (Nov 14, 2016) Name changed to remove word “CloudBees”. btw. I've installed docker-workflow 1.9 via HPI file, today I updated Jenkins to 2.31, and now I see that I have Docker Pipeline 1.9.1. Magic. 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-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title Jakub Czaplicki edited a comment on JENKINS-39723 Re: BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) [~jamesdumay] thanks! It's probably just a matter of missing dependancy. Installing docker-worflow.hpi v.1.9 made the dependency error disappear. I am assuming it fixes the issue. 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-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title Jakub Czaplicki edited a comment on JENKINS-39723 Re: BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) [~michaelneale]: How do I install a plugin directly ? I need an *.hpi file to upload it via Jenkins plugin manager, right ? Where can I find it and how do I make sure that's the latests version of it ? Also: when I do this won't I need to check manually if there's a new version of that plugin ? Is there a reason why the "CloudBees Docker Pipeline Plugin" is not in the main Jenkins plugin repo (http://updates.jenkins-ci.org/update-center.json) ? 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-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title Jakub Czaplicki commented on JENKINS-39723 Re: BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) James Dumay thanks! It's probably just a matter of missing dependancy. 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-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title Jakub Czaplicki edited a comment on JENKINS-39723 Re: BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) [~michaelneale]: How do I install a plugin directly ? I need an *.hpi file to upload it via Jenkins plugin manager, right ? Where can I find it and how do I make sure that's the latests version of it ? Also: when I do this won't I need to check manually if there's a new version of that plugin ?Is there a reason why the "CloudBees Docker Pipeline Plugin" is not in the main Jenkins plugin repo (http://updates.jenkins-ci.org/update-center.json) ? 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-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title Jakub Czaplicki commented on JENKINS-39723 Re: BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) How do I install a plugin directly ? I need an *.hpi file to upload it via Jenkins plugin manager, right ? Where can I find it and how do I make sure that's the latests version of it ? Also: when I do this won't I need to check manually if there's a new version of that plugin ? Is there a reason why the "CloudBees Docker Pipeline Plugin" is not in the main Jenkins plugin repo (http://updates.jenkins-ci.org/update-center.json) ? 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-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title Jakub Czaplicki created an issue Jenkins / JENKINS-39723 BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/14 6:53 PM Environment: Jenkins ver.2.30, Ubuntu Server Labels: blueocean Priority: Major Reporter: Jakub Czaplicki I have Jenkins instance that I keep updating as soon as a new version is available. This time I thought I'll give the Ocean Plugin a try. After installing https://wiki.jenkins-ci.org/display/JENKINS/Blue+Ocean+Plugin plugin, the Jenkins notification reports two errors : There are dependency errors loading some plugins: BlueOcean beta v1.0.0-b11 Pipeline: Model Definition v0.2 failed to load. Fix this plugin first. Pipeline: Model Definition v0.5 docker-workflow v1.8 is missing. To fix, install v1.8 or later. I can't find docker-workflow anywhere.
[JIRA] (JENKINS-36134) Allow users to disable/hide the test-results-analyzer-plugin per job
Title: Message Title Jakub Czaplicki created an issue Jenkins / JENKINS-36134 Allow users to disable/hide the test-results-analyzer-plugin per job Issue Type: Improvement Assignee: Varun Menon Components: test-results-analyzer-plugin Created: 2016/Jun/22 7:26 AM Priority: Minor Reporter: Jakub Czaplicki Currently the "Test Results Analyzer" link is visible in all jobs. However not all Jenkins job can be test-related (such as build automation). It would be beneficial if we could enable/disable/hide the plugin in a job configuration. Add Comment
[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki commented on JENKINS-34948 Re: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Updated the plugin to ver.1.09, rerun my Jenkins jobs a couple of times. All works as expected. The issue indeed has been fixed. I've updated https://wiki.jenkins-ci.org/display/JENKINS/Assembla+Auth+Plugin with the ver.no. 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki commented on JENKINS-34948 Re: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Hi Pavel Dotsulenko, Many thanks for quick fix! I'll install it as soon as it's available. Earlier today I updated two other plugins that had a fresh new versions: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Branch+API+Plugin At the same time I installed https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin I wanted to use it as a workaround. Now. It seems that one of the updates.. fixed the problem. The changelog in the Pipeline Multibranch Plugin says "Internal refactoring to expose multibranch functionality to other plugins" - perhaps this is what was causing the problem in the first place ? Anyhow, I am glad you've got a fix for this on your side. 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki assigned an issue to Jakub Czaplicki Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Change By: Jakub Czaplicki Assignee: Frédéric Camblor Jakub Czaplicki 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki commented on JENKINS-34948 Re: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken That's what I suspected. I've reported the issue to Assembla (they maintain the plugin). They now have created an internal ticket to look into this issue. 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki commented on JENKINS-34948 Re: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Reported the problem via https://helpdesk.assembla.com/customer/portal/emails/new on 2016-06-01 Contacted the Assembla Open Source team via email on 2016-06-02 (contact details: https://www.assembla.com/spaces/assembla-oss/team ) Link to src code: https://www.assembla.com/spaces/assembla-oss/git/source 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki commented on JENKINS-34948 Re: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Frédéric, I've assigned this ticket to you since your name was on the last assembla-auth ticket. 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki assigned an issue to Frédéric Camblor Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Change By: Jakub Czaplicki Assignee: Frédéric Camblor 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title
Jakub Czaplicki updated an issue
Jenkins / JENKINS-34948
UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Change By:
Jakub Czaplicki
Jenkins Authorization is integrated with Assembla's auth. Security Realm uses Assembla Auth Plugin.Jobs intermittently finish and fail with FAILURE status with the following error message (always the last item in the console log) :{code:java}FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationTokenjava.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationToken at com.assembla.jenkinsci.plugin.AssemblaSecurityRealm.loadUserByUsername(AssemblaSecurityRealm.java:333) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1050) at hudson.model.User.get(User.java:395) at hudson.model.User.get(User.java:364) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE{code}This behaviour didn't occur in the previous Jenkins version 1.6.x
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki updated an issue Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Change By: Jakub Czaplicki Environment: Jenkins 2.5 (installed via apt-get upgrade), master only Also: Jenkins 2.7 (installed via apt-get install) Assembla Auth Plugin 1.06 Assembla plugin 1.4 Credentials Plugin 1.27Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-74-generic x86_64) 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki commented on JENKINS-34948 Re: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Still occurs in ver.2.6 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] [assembla-plugin] (JENKINS-29882) Authentication Fails
Title: Message Title Jakub Czaplicki commented on JENKINS-29882 Re: Authentication Fails I am seeing the same issue. "Cannot connect to 'https://assembla.com': server error[401]", despite correct credentials. 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki updated an issue Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Change By: Jakub Czaplicki Summary: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Title: Message Title
Jakub Czaplicki updated an issue
Jenkins / JENKINS-34948
UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Change By:
Jakub Czaplicki
Jenkins Authorization is integrated with Assembla's auth. Security Realm uses Assembla Auth Plugin. Jobs intermittently finish and fail with the following error message:{code:java}FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationTokenjava.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationToken at com.assembla.jenkinsci.plugin.AssemblaSecurityRealm.loadUserByUsername(AssemblaSecurityRealm.java:333) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1050) at hudson.model.User.get(User.java:395) at hudson.model.User.get(User.java:364) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE{code}This behaviour didn't occur in the previous Jenkins version 1.6.x
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki updated an issue Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken Change By: Jakub Czaplicki Environment: Jenkins 2.5 (installed via apt-get upgrade), master only Authorization integrated with Assembla .Assembla Auth Plugin 1.06Assembla plugin 1.4Credentials Plugin 1.27Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-74-generic x86_64) 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki updated an issue Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken Change By: Jakub Czaplicki Environment: Jenkins 2.5 (installed via apt-get upgrade), master only Authorization integrated with Assembla .Assembla Auth Plugin 1.06Assembla plugin 1.4Credentials Plugin 1.27Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-74-generic x86_64) 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki created an issue Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken Issue Type: Bug Assignee: Unassigned Components: assembla-auth, core Created: 2016/May/19 10:42 AM Environment: Jenkins 2.5 (installed via apt-get upgrade), master only Assembla Auth Plugin 1.06 Assembla plugin 1.4 Credentials Plugin 1.27 Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-74-generic x86_64) Labels: authentication auth Priority: Major Reporter: Jakub Czaplicki Jobs intermittently finish and fail with the following error message: FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationToken java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to
[JIRA] [build-publisher-plugin] (JENKINS-22516) FileAlreadyExistsException on parallel builds
Title: Message Title Jakub Czaplicki commented on JENKINS-22516 Re: FileAlreadyExistsException on parallel builds Jenkins ver. 1.609.2 is also affected. Is there a workaround for this problem ? 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] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Jakub Czaplicki commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x Follow Alexander's solution and update the dpkg package : https://issues.jenkins-ci.org/browse/JENKINS-26240?focusedCommentId=218557page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-218557 This message is automatically generated by JIRA. 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] [ssh-slaves-plugin] (JENKINS-24323) Could not copy slave.jar into '/users/ccfw73' on slave
Jakub Czaplicki commented on JENKINS-24323 Could not copy slave.jar into /users/ccfw73 on slave Bloody hell. Is there a workaround for those who can't upgrade Jenkins and got this issue ? This message is automatically generated by JIRA. 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] [ssh-slaves-plugin] (JENKINS-24323) Could not copy slave.jar into '/users/ccfw73' on slave
Jakub Czaplicki edited a comment on JENKINS-24323 Could not copy slave.jar into /users/ccfw73 on slave The issue is within SSH Plugin (or a combination of Jenkins version and SSH Plugin version). SSH Plugin ver.1.5 had this bug. Updating SSH Plugin to ver.1.9 made the issue disappear. Jenkins ver. 1.554. Master linux, slave linux This message is automatically generated by JIRA. 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] [core] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Jakub Czaplicki commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x Is anyone actively working on this issues ? This message is automatically generated by JIRA. 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] [github-oauth-plugin] (JENKINS-14524) Slave agent authorization 401
Jakub Czaplicki commented on JENKINS-14524 Slave agent authorization 401 The issue also occurs when Active Directory is used as access control (jenkins ver. 1.554). For jenkins ver. 1.590 works OK. So somewhere between 1.554 and 1.590 the issue has been fixed for Active Dir. This message is automatically generated by JIRA. 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] [perforce-plugin] (JENKINS-20553) matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME
Jakub Czaplicki edited a comment on JENKINS-20553 matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME I've hit this issue. One of my scripts is reporting "Slashes ( / ) not allowed in ..". I've got all the most recent versions available in the Jenkins Plugin Manager as of 2014.10.30. Jenkins ver.1.585 "Perforce Plugin" ver.1.3.27 Matrix Project Plugin ver.1.4 However I see that there's a new version tagged (1.3.28) listed in the release on github (not availble in the Plugin Manager, yet): https://github.com/jenkinsci/perforce-plugin/releases/tag/perforce-1.3.28 I don't have the ability to build it myself. If only there was a CI system that would allow to download *.hpi file.. This message is automatically generated by JIRA. 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] [perforce-plugin] (JENKINS-20553) matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME
Jakub Czaplicki commented on JENKINS-20553 matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME I've hit this issue. One of my scripts is reporting "Slashes not allowed in ..". I've got all the most recent versions available in the Jenkins Plugin Manager as of 2014.10.30. Jenkins ver.1.585 "Perforce Plugin" ver.1.3.27 Matrix Project Plugin ver.1.4 However I see that there's a new version tagged (1.3.28) listed in the release on github (not availble in the Plugin Manager, yet): https://github.com/jenkinsci/perforce-plugin/releases/tag/perforce-1.3.28 I don't have the ability to build it myself. If only there was a CI system that would allow to download *.hpi file.. This message is automatically generated by JIRA. 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] [perforce-plugin] (JENKINS-20553) matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME
Jakub Czaplicki edited a comment on JENKINS-20553 matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME I've hit this issue. One of my scripts is reporting "Slashes ( / ) not allowed in ..". I've got all the most recent versions available in the Jenkins Plugin Manager as of 2014.10.30. Jenkins ver.1.585 "Perforce Plugin" ver.1.3.27 Matrix Project Plugin ver.1.4 However I see that there's a new version tagged (1.3.28) listed in the release on github (not availble in the Plugin Manager, yet): https://github.com/jenkinsci/perforce-plugin/releases/tag/perforce-1.3.28 1.3.28 is not listed in http://mirrors.jenkins-ci.org/plugins/perforce/ , and I don't have the ability to build it myself. If only there was a CI system that would allow to download *.hpi file.. This message is automatically generated by JIRA. 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] [perforce-plugin] (JENKINS-20553) matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME
Jakub Czaplicki
edited a comment on JENKINS-20553
matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME
I've hit this issue. One of my scripts is reporting "Slashes ( / ) not allowed in ..".
I've got all the most recent versions available in the Jenkins Plugin Manager as of 2014.10.30.
Jenkins ver.1.585
"Perforce Plugin" ver.1.3.27
Matrix Project Plugin ver.1.4
However I see that there's a new version tagged (1.3.28) listed in the release on github (not availble in the Plugin Manager, yet):
https://github.com/jenkinsci/perforce-plugin/releases/tag/perforce-1.3.28
1.3.28 is not listed in http://mirrors.jenkins-ci.org/plugins/perforce/ , and I don't have the ability to build it myself. If only there was a CI system that would allow to download *.hpi file..
Simple workaround is to use
#!/bin/bash
export P4CLIENT=${P4CLIENT//[\/,=]/-}
This message is automatically generated by JIRA.
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] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Jakub Czaplicki commented on JENKINS-7695 archiving throws hudson.util.IOException2: java.io.IOException: request to write 3977 bytes exceeds size in header of 41955006 I am seeing this issue in 1.555 : 11:12:54 ERROR: Failed to archive artifacts: *.log 11:12:54 java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: request to write '8192' bytes exceeds size in header of '26982170' bytes for entry 'output.log' 11:12:54 at hudson.FilePath.copyRecursiveTo(FilePath.java:2017) 11:12:54 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) 11:12:54 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) 11:12:54 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 11:12:54 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 11:12:54 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) 11:12:54 at hudson.model.Build$BuildExecution.post2(Build.java:183) 11:12:54 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) 11:12:54 at hudson.model.Run.execute(Run.java:1701) 11:12:54 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 11:12:54 at hudson.model.ResourceController.execute(ResourceController.java:88) 11:12:54 at hudson.model.Executor.run(Executor.java:231) 11:12:54 Caused by: java.util.concurrent.ExecutionException: java.io.IOException: request to write '8192' bytes exceeds size in header of '26982170' bytes for entry 'output.log' 11:12:54 at hudson.remoting.Channel$3.adapt(Channel.java:755) 11:12:54 at hudson.remoting.Channel$3.adapt(Channel.java:750) 11:12:54 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) 11:12:54 at hudson.FilePath.copyRecursiveTo(FilePath.java:2015) 11:12:54 ... 11 more 11:12:54 Caused by: java.io.IOException: request to write '8192' bytes exceeds size in header of '26982170' bytes for entry 'output.log' 11:12:54 at hudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284) 11:12:54 at hudson.util.io.TarArchiver.visit(TarArchiver.java:114) 11:12:54 at hudson.util.DirScanner.scanSingle(DirScanner.java:49) 11:12:54 at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2541) 11:12:54 at hudson.FilePath.writeToTar(FilePath.java:2053) 11:12:54 at hudson.FilePath.access$1000(FilePath.java:172) 11:12:54 at hudson.FilePath$41.invoke(FilePath.java:1994) 11:12:54 at hudson.FilePath$41.invoke(FilePath.java:1990) 11:12:54 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2462) 11:12:54 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 11:12:54 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 11:12:54 at hudson.remoting.Request$2.run(Request.java:328) 11:12:54 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 11:12:54 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 11:12:54 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 11:12:54 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 11:12:54 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 11:12:54 at java.lang.Thread.run(Thread.java:662) 11:12:54 Build step 'Archive the artifacts' changed build result to FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki commented on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Back to drawing board. Summary from https://github.com/jenkinsci/jenkins/pull/1273 : There's no jQuery available in the core Should use Behaviour.add from within BuildHistoryWidget/entries.jelly rather than modifying the generic layout page. gerrit-trigger-plugin ought to define custom parameter types, with customized presentation, rather than overloading standard textual ones This message is automatically generated by JIRA. 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] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki
commented on JENKINS-22311
Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
I did some work on this. The idea is to hide the build parameters and only show them when a user clicks on the "pending—Build #..." string, with ability to hide the long string again (and later with ability to view/expand all hidden build parameters). The working example script of what I aim for is here: http://jsfiddle.net/jakubczaplicki/WT88W/
It required modification of two files (see diffs below).
I'd like a feedback and some suggestions/help on how to improve this code, such that it can be applied to master branch.
Some notes:
Tested on Jenkins ver. 1.565
Uses jQuery 1.7.2 (which is AFAIK default jQuery version built in jenkins)
Every N seconds the BuildHistory is being refreshed. After each refresh, the parameters are hidden again.
I am aware that I used deprecated jQuery's .live() method, however the suggestion on http://www.andismith.com/blog/2011/11/on-and-off/ didn't work.
Without .live(), the jQuery script stops working after the BuildHistory list refresh
Jenkins core modification is new to me, so my change may not be following coding standards.
diff --git a/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly b/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly
index e545724..4ffd3ac 100644
--- a/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly
+++ b/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly
@@ -47,6 +47,7 @@ THE SOFTWARE.
l:stopButton href="" class="code-quote">"${rootURL}/queue/cancelItem?id=${item.id}" alt="${%cancel this build}"/
/j:if
/div
+ div class="itemsummary" id="${id}"
j:set var="cause" value="${item.getCauseOfBlockage()}"/
j:choose
j:when test="${cause!=null}"
(${%pending}—st:include it="${cause}" page="summary.jelly"/)
/j:when
j:otherwise
(${%pending})
/j:otherwise
/j:choose
- ${item.params}
+ /div
+ div class="itemparams" id="${id}"${item.params}/div
/td
/tr
/j:forEach
diff --git a/core/src/main/resources/lib/layout/layout.jelly b/core/src/main/resources/lib/layout/layout.jelly
index a8466f3..6168fb9 100644
--- a/core/src/main/resources/lib/layout/layout.jelly
+++ b/core/src/main/resources/lib/layout/layout.jelly
@@ -141,6 +140,11 @@ ${h.initPageVariables(context)}
j:forEach var="pd" items="${h.pageDecorators}"
st:include it="${pd}" page="header.jelly" optional="true" /
/j:forEach
+
+!-- itemparams == Pending Job Build Parameters --
+style type="text/css" div.itemparams { display:none; overflow: hidden; text-overflow: ellipsis; } /style
+scriptjQuery(document).ready(function() { jQuery('div.itemsummary').live( "click", function() { jQuery('#'+this.id+'.itemparams').toggle(); }); });/script
+
/head
body id="jenkins jenkins-${h.version}" class="yui-skin-sam"
!-- for accessibility, skip the entire navigation bar and etc and go straight to the head of the content --
This message is automatically generated by JIRA.
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] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki
edited a comment on JENKINS-22311
Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
I did some work on this. The idea is to hide the build parameters and only show them when a user clicks on the "pending—Build #..." string, with ability to hide the long string again (and later with ability to view/expand all hidden build parameters). The working example script of what I aim for is here: http://jsfiddle.net/jakubczaplicki/WT88W/
It required modification of two files (see diffs below).
I'd like a feedback and some suggestions/help on how to improve this code, such that it can be applied to master branch.
Some notes:
Tested on Jenkins ver. 1.565
Uses jQuery 1.7.2 (which is AFAIK default jQuery version built in jenkins)
Every N seconds the BuildHistory is being refreshed. After each refresh, the parameters are hidden again.
I am aware that I used deprecated jQuery's .live() method, however the suggestion on http://www.andismith.com/blog/2011/11/on-and-off/ didn't work.
Without .live(), the jQuery script stops working after the BuildHistory list refresh
Jenkins core modification is new to me, so my change may not be following coding standards.
Code:
diff --git a/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly b/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly
index e545724..4ffd3ac 100644
--- a/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly
+++ b/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly
@@ -47,6 +47,7 @@ THE SOFTWARE.
l:stopButton href="" class="code-quote">"${rootURL}/queue/cancelItem?id=${item.id}" alt="${%cancel this build}"/
/j:if
/div
+ div class="itemsummary" id="${id}"
j:set var="cause" value="${item.getCauseOfBlockage()}"/
j:choose
j:when test="${cause!=null}"
(${%pending}—st:include it="${cause}" page="summary.jelly"/)
/j:when
j:otherwise
(${%pending})
/j:otherwise
/j:choose
- ${item.params}
+ /div
+ div class="itemparams" id="${id}"${item.params}/div
/td
/tr
/j:forEach
diff --git a/core/src/main/resources/lib/layout/layout.jelly b/core/src/main/resources/lib/layout/layout.jelly
index a8466f3..6168fb9 100644
--- a/core/src/main/resources/lib/layout/layout.jelly
+++ b/core/src/main/resources/lib/layout/layout.jelly
@@ -141,6 +140,11 @@ ${h.initPageVariables(context)}
j:forEach var="pd" items="${h.pageDecorators}"
st:include it="${pd}" page="header.jelly" optional="true" /
/j:forEach
+
+!-- itemparams == Pending Job Build Parameters --
+style type="text/css" div.itemparams { display:none; overflow: hidden; text-overflow: ellipsis; } /style
+scriptjQuery(document).ready(function() { jQuery('div.itemsummary').live( "click", function() { jQuery('#'+this.id+'.itemparams').toggle(); }); });/script
+
/head
body id="jenkins jenkins-${h.version}" class="yui-skin-sam"
!-- for accessibility, skip the entire navigation bar and etc and go straight to the head of the content --
This message is automatically generated by JIRA.
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] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki edited a comment on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history The file and the line that require modification : https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly#L59 This message is automatically generated by JIRA. 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] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki commented on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history File and line that requires modification : https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly#L59 This message is automatically generated by JIRA. 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] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki edited a comment on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history The file and the line that require modification : https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly#L59 I suggest to use the jQuery Expander Plugin or a similar solution if jQuery is not built in in Jenkins core: http://plugins.learningjquery.com/expander/demo/index.html http://plugins.learningjquery.com/expander/index.html This message is automatically generated by JIRA. 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] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki updated JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Change By: Jakub Czaplicki (19/May/14 9:30 AM) Summary: Largenumberofbuildparametersforpendingjobs(e.g. gerrit trigger triggeredjob) cancauseunwieldybuildhistory whentherearependingjobs Environment: centos6Jenkins1.532.2 -1.555-1.563 GerritTrigger2.11.0 Priority: Minor Major Description: IfGerrittriggerscreateaqueueinthePendingJobscolumnintheprojectpage,itwillinsert buildparameters/ metadataaboutthetrigger:GERRIT_EVENT_TYPE,GERRIT_EVENT_HASH,etc.Ifthismetadataislong,itwilldistorttheprojectpagetobevisuallyunusable.Wouldlikeawaytoeitherturnof of or truncatethisdisplayofGerritmetadata. This message is automatically generated by JIRA. 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] [core] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs
Jakub Czaplicki commented on JENKINS-22311 gerrit trigger can cause unwieldy build history when there are pending jobs This issue still exist in Jenkins ver. 1.563 Gerrit Trigger ver. 2.11.1 This message is automatically generated by JIRA. 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] [core] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs
Jakub Czaplicki commented on JENKINS-22311 gerrit trigger can cause unwieldy build history when there are pending jobs After looking at the plugin code and googling a bit it seems that it's not the plugin to decide on the length of paramters shown for pending jobs. It seems that it's the jenkins core controls this. Am I right ? This message is automatically generated by JIRA. 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] [core] (JENKINS-23064) Limit the build parameters (string) shown for pending builds
Jakub Czaplicki created JENKINS-23064 Limit the build parameters (string) shown for pending builds Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 16/May/14 12:09 PM Description: When a job is triggered with a large number of parameters, the pending builds (in build history) will show all those parameters next to the build number. This makes the page very difficult to work on, requiring user to scroll horizontally a lot (even during configuration). An option that would allow user either to limit the string or the shown parameters for pending builds would be highly appreciated. Example (see also JENKINS-22311): I believe it's a feature implemented in jenkins' core. If it's a plugin please add appropriate component to this jira. Environment: Jenkins ver. 1.555 and 1.563 Project: Jenkins Labels: jenkins parameterized ui ux build-history build-queue Priority: Major Reporter: Jakub Czaplicki This message is automatically generated by JIRA. 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] [core] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs
Jakub Czaplicki edited a comment on JENKINS-22311 gerrit trigger can cause unwieldy build history when there are pending jobs After looking at the plugin code and googling a bit it seems that it's not the plugin to decide on the length of paramters shown for pending jobs. It seems that it's the jenkins core controls this. Am I right ? I've added new jira for this issue: JENKINS-23064 This message is automatically generated by JIRA. 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] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
Jakub Czaplicki commented on JENKINS-21547 Add information to console log when a job is aborted by gerrit From what we're seeing, a currently running job (triggered by gerrit) will be aborted when a new patchset is submitted. Presumably the scheduled builds are cancelled as well, which make sense. This message is automatically generated by JIRA. 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] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
Jakub Czaplicki edited a comment on JENKINS-21547 Add information to console log when a job is aborted by gerrit From what we're seeing, a currently running job (triggered by gerrit) will be aborted when a new patchset is submitted. Presumably the scheduled builds are cancelled as well, which make sense. And it indeed created the "Who aborted this and why?" kind of situation. This message is automatically generated by JIRA. 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] [postbuildscript] (JENKINS-22230) PostBuildScript updates job configuration every time job runs
Jakub Czaplicki commented on JENKINS-22230 PostBuildScript updates job configuration every time job runs I was able to reproduce the SYSTEM-job-config-update issue having the following versions: Jenkins ver. 1.553 Post-Build Script Plug-in plugin ver.0.10 Metadata plugin ver.1.1.0b The SYSTEM stopped updating job configuration after updating the Post-Build script plugin to ver.0.16: Jenkins ver. 1.553 Post-Build Script Plug-in plugin ver.0.16 Metadata plugin ver.1.1.0b It seems that the issue has been fixed somewhere between version 0.10 and 0.16. Perhaps this change was a fix: https://github.com/jenkinsci/postbuildscript-plugin/commit/b225c1b845bd8b26b153de9fda03dac5c3259b7e ? I am going to resolve this ticket now. This message is automatically generated by JIRA. 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] [postbuildscript] (JENKINS-22230) PostBuildScript updates job configuration every time job runs
Jakub Czaplicki resolved JENKINS-22230 as Wont Fix PostBuildScript updates job configuration every time job runs Change By: Jakub Czaplicki (19/Mar/14 11:34 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuildscript] (JENKINS-22230) PostBuildScript updates job configuration every time job runs
Jakub Czaplicki created JENKINS-22230 PostBuildScript updates job configuration every time job runs Issue Type: Bug Assignee: Gregory Boissinot Components: postbuildscript Created: 17/Mar/14 5:11 PM Description: When a Post-build Action is added to a job, its configuration is being updated by user SYSTEM every time the job runs. The updated value is always time. An example of how the job config diff looks like: 36 generatedtrue/generated 37 exposedToEnvironmentfalse/exposedToEnvironment 38 value -39 time1394798774448/time +39 time1394800224909/time 40 timezoneEurope/London/timezone 41 /value 42 checkedfalse/checked Another example: 39 generatedtrue/generated 40 exposedToEnvironmentfalse/exposedToEnvironment 41 value - 42time1395074512487/time + 42time1395074516623/time 43timezoneEurope/London/timezone 44 /value 45 checkedfalse/checked ... 56 parent class="metadata-tree" reference="../../.."/ 57 generatedtrue/generated 58 exposedToEnvironmentfalse/exposedToEnvironment - 59 valuejakub/value + 59 valueSYSTEM/value 60/metadata-string 61metadata-string 62 namefull-name/name 62 namefull-name/name 64 parent class="metadata-tree" reference="../../.."/ 65 generatedtrue/generated 66 exposedToEnvironmentfalse/exposedToEnvironment - 67 valuejakub/value + 67 valueSYSTEM/value 68/metadata-string 69 /children 70/metadata-tree This causes the "SCM Sync configuration plugin" repository to grow very quickly, and it also makes difficult to work out when a configuration has been changed by a user and not SYSTEM. Is it a bug ? Is it an expected behaviour ? If so how can I disable it ? Is it the PostBuildScriptListener class that's responsible for this ? publishers.remove(curPublisher.getClass()); publishers.add(curPublisher); We're currently using PostBuildScript version 0.10. Project: Jenkins Labels: postbuildscript Priority: Major Reporter: Jakub Czaplicki This message is automatically generated by JIRA. 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] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
Jakub Czaplicki created JENKINS-21547 Add information to console log when a job is aborted by gerrit Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger Created: 29/Jan/14 1:00 PM Description: When a new patch set is submitted/rebased to an existing gerrit, the job triggered by the previous patch set is aborted (according to our observations). It would be very helpful to know (as in see in the console) that a job has been aborted by gerrit. Currently the console log shows: 13:35:00 Build was aborted 13:35:00 Archiving artifacts Project: Jenkins Labels: plugin Priority: Major Reporter: Jakub Czaplicki This message is automatically generated by JIRA. 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-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail
Jakub Czaplicki commented on JENKINS-13341 Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail Just had an identical issue and switching to Oracle's JDK (1.7) indeed fixed it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17178) Upstream job name/link not listed when job at the bottom of hierarchy
Jakub Czaplicki created JENKINS-17178 Upstream job name/link not listed when job at the bottom of hierarchy Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 12/Mar/13 2:42 PM Description: When a job is at the bottom in a hierarchy of jobs, the "Upstream Projects" list is missing on its "main" page. The dependency graph doesn't show the upstream hierarchy either. Project: Jenkins Labels: jenkins ui upstream downstream Priority: Major Reporter: Jakub Czaplicki This message is automatically generated by JIRA. 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-17178) Upstream job name/link not listed when job at the bottom of hierarchy
Jakub Czaplicki updated JENKINS-17178 Upstream job name/link not listed when job at the bottom of hierarchy Change By: Jakub Czaplicki (12/Mar/13 3:45 PM) Description: Asubprojectjobdoesnt Subprojectjobsdonot showtheUpstreamProjects.Thedependencygraphdoesntshowtheupstreamhierarchyeither. This message is automatically generated by JIRA. 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-17178) Upstream job name/link not listed when job at the bottom of hierarchy
Jakub Czaplicki updated JENKINS-17178 Upstream job name/link not listed when job at the bottom of hierarchy Change By: Jakub Czaplicki (12/Mar/13 3:45 PM) Description: Whena Asubproject job isat doesntshow the bottominahierarchyofjobs,the UpstreamProjects listismissingonitsmainpage .Thedependencygraphdoesntshowtheupstreamhierarchyeither. This message is automatically generated by JIRA. 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-13238) Loading All Build History Fails
[ https://issues.jenkins-ci.org/browse/JENKINS-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Czaplicki reopened JENKINS-13238: --- The issue is still present 1.458 Loading All Build History Fails --- Key: JENKINS-13238 URL: https://issues.jenkins-ci.org/browse/JENKINS-13238 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: linux, jenkins 1.456 Reporter: Spencer Oliver Assignee: sogabe seems after the update from 1.455 to 1.456 causes an issue where pressing 'More' to expand the job Build History now fails with a 404. Calling the build history directly also causes the 404, eg. http://openocd.zylin.com/jenkins/job/openocd/buildHistory/all/ For info rolling back to 1.455 cures the problem. tested 1.457 and issue still present. jenkins own server also shows the issue: http://ci.jenkins-ci.org/view/All/job/jenkins_main_trunk/buildHistory/all/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
