[JIRA] (JENKINS-13258) Set the default params in parametrized build as env variables in the SCM poll
[ https://issues.jenkins-ci.org/browse/JENKINS-13258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ttgtg ttgtg updated JENKINS-13258: -- Component/s: scm-sync-configuration Set the default params in parametrized build as env variables in the SCM poll - Key: JENKINS-13258 URL: https://issues.jenkins-ci.org/browse/JENKINS-13258 Project: Jenkins Issue Type: Improvement Components: accurev, core, scm-sync-configuration Reporter: ttgtg ttgtg Assignee: Scott Tatum use case: Be able to set the stream name (in accurev) as the parametrized input of the job and have a default value for that param used to poll SCM trigger. In this case it uses the default value to poll the accurev and uses the input when the job starts manually or by another job. -- 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
[JIRA] (JENKINS-9190) deduplicating build artifacts
[ https://issues.jenkins-ci.org/browse/JENKINS-9190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161613#comment-161613 ] yossis commented on JENKINS-9190: - This is possible in Artifactory using what we call [checksum deploy|http://wiki.jfrog.org/confluence/display/RTF/Artifactory%27s+REST+API#ArtifactorysRESTAPI-DeployArtifactbyChecksum]. Support in Jenkins plugin is coming in the next version. We'll probably use it only for artifacts bigger that 10KB. You can follow the following issue: https://issues.jfrog.org/jira/browse/BI-126. deduplicating build artifacts - Key: JENKINS-9190 URL: https://issues.jenkins-ci.org/browse/JENKINS-9190 Project: Jenkins Issue Type: Improvement Components: artifactory Affects Versions: current Reporter: Brian Murrell Assignee: yossis At least in our case, a project can produce quite a number of artifacts, some quite large and some which only change occasionally from one build to another (i.e. some artifacts change every time, some less frequently). It seems that both space and bandwidth could be saved by de-duplicating these seldom changed artifacts from one build to another. I imagine an algorithm where the server keeps a database of sums and sizes of stored artifacts and when a slave is going to send the artifacts of a build it first offers the sums and sizes of the artifacts. If the server finds potential matches, further verification of duplication could be performed (i.e. comparing random samples of the suspected duplicates) and once a duplicate has been confirmed, the server can either copy or link the artifact locally and tell the slave not to bother sending it. -- 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
[JIRA] (JENKINS-9190) deduplicating build artifacts
[ https://issues.jenkins-ci.org/browse/JENKINS-9190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Murrell reopened JENKINS-9190: I don't find having to deploy an entirely new tool a reasonable resolution to this issue. The jenkins artifact archiving process is entirely suitable for our environment -- if a bit wasteful in the storage of numerous (copies even) of duplicate artifacts. I am sure Artifactory is a great tool for people who have a need for for it, but to simply de-duplicate artifacts it feels like using a sledgehammer to drive a finishing nail. deduplicating build artifacts - Key: JENKINS-9190 URL: https://issues.jenkins-ci.org/browse/JENKINS-9190 Project: Jenkins Issue Type: Improvement Components: artifactory Affects Versions: current Reporter: Brian Murrell Assignee: yossis At least in our case, a project can produce quite a number of artifacts, some quite large and some which only change occasionally from one build to another (i.e. some artifacts change every time, some less frequently). It seems that both space and bandwidth could be saved by de-duplicating these seldom changed artifacts from one build to another. I imagine an algorithm where the server keeps a database of sums and sizes of stored artifacts and when a slave is going to send the artifacts of a build it first offers the sums and sizes of the artifacts. If the server finds potential matches, further verification of duplication could be performed (i.e. comparing random samples of the suspected duplicates) and once a duplicate has been confirmed, the server can either copy or link the artifact locally and tell the slave not to bother sending it. -- 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
[JIRA] (JENKINS-12761) tfs plugin :failed to record scm polling
[ https://issues.jenkins-ci.org/browse/JENKINS-12761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161615#comment-161615 ] jlin sai commented on JENKINS-12761: the reason is the plugin cannot support chinese ,and it has fixed. tfs plugin :failed to record scm polling - Key: JENKINS-12761 URL: https://issues.jenkins-ci.org/browse/JENKINS-12761 Project: Jenkins Issue Type: Bug Components: tfs Affects Versions: current Environment: Computer : windows xp/7 ,x86 Architecture Tomcat :Version 7.0.11 Jenkins:Version 1.450 tfs plugin:Version 1.20 Reporter: jlin sai Assignee: drewrm Labels: plugin Fix For: current Attachments: ErrorInfo.jpg I get a failure when I use the tfs plugin of Jenkins. The Source Code management tool what I use is Team Foundation Server 2010,when I manage the poll SCM in Jenkins,and want to trigger a build automatic when it detected a change between TFS server and Personal workspace , a failure hanppened ,which information is failed to record scm polling. Three months ago ,the version of tfs plugin is 1.17,I encount the failure ,and now the problem isn't resolved. I have been searched a method for a long time ,but not get it . I don't know what the reason is ,so please to help me to fixed the problem.Thank you very much! -- 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
[JIRA] (JENKINS-13456) Improve Trac publisher plugin comment
haocheng lee created JENKINS-13456: -- Summary: Improve Trac publisher plugin comment Key: JENKINS-13456 URL: https://issues.jenkins-ci.org/browse/JENKINS-13456 Project: Jenkins Issue Type: Improvement Components: trac Reporter: haocheng lee Assignee: haocheng lee I would like to add more contents when trac-publisher plugin add comment in the related issue. Basically I copied the comment format from jia plugin (https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin) ;) -- 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
[JIRA] (JENKINS-13065) Jenkins tfs Plugin: failed to record scm polling
[ https://issues.jenkins-ci.org/browse/JENKINS-13065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jlin sai resolved JENKINS-13065. Resolution: Fixed the same problem as BUG 12761 https://issues.jenkins-ci.org/browse/JENKINS-12761 Jenkins tfs Plugin: failed to record scm polling Key: JENKINS-13065 URL: https://issues.jenkins-ci.org/browse/JENKINS-13065 Project: Jenkins Issue Type: Bug Components: tfs Affects Versions: current Environment: The version of Java is 1.6.0_16 , The version of Tomcat is 7.0.26 ,The version of jenkins is 1.450-1.455 ,tfs plugin is 1.20 .The operating system is windows XP/7 Reporter: jlin sai Assignee: redsolo I get a failure when I use the tfs plugin of Jenkins. The Source Code management tool what I use is Team Foundation Server 2010,when I manage the poll SCM in Jenkins,and want to trigger a build automatic when it detected a change between TFS server and Personal workspace , a failure hanppened ,which information is failed to record scm polling.the major information are as follows. Three months ago ,the version of tfs plugin is 1.17,I encount the failure ,and now the problem isn't resolved. I have been searched a method for a long time ,but not get it . I don't know what the reason is ,so please to I want to wish you can help me to fix the problem.Thank you very much! ERROR: Failed to record SCM polling java.lang.NullPointerException at hudson.plugins.tfs.commands.DetailedHistoryCommand.parseChangeSetString(DetailedHistoryCommand.java:151) at hudson.plugins.tfs.commands.DetailedHistoryCommand.parse(DetailedHistoryCommand.java:112) at hudson.plugins.tfs.model.Project.getDetailedHistory(Project.java:43) at hudson.plugins.tfs.TeamFoundationServerScm.pollChanges(TeamFoundationServerScm.java:207) at hudson.scm.SCM.poll(SCM.java:375) at hudson.model.AbstractProject.poll(AbstractProject.java:1310) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- 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
[JIRA] (JENKINS-12761) tfs plugin :failed to record scm polling
[ https://issues.jenkins-ci.org/browse/JENKINS-12761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161618#comment-161618 ] jlin sai edited comment on JENKINS-12761 at 4/15/12 1:50 PM: - the merged file is DetailedHistoryCommand.java and KeyTextValueReader.java ,which replace the PATTERN CHANGESET KEY compile \\w to ^[\u4e00-\u9fa5],which is the range of unicode encoding chinese. was (Author: linbeisaii): the merged file is DetailedHistoryCommand.java and KeyTextValueReader.java ,which replace the compile \\w to ^[\u4e00-\u9fa5],which is the range of unicode encoding chinese. tfs plugin :failed to record scm polling - Key: JENKINS-12761 URL: https://issues.jenkins-ci.org/browse/JENKINS-12761 Project: Jenkins Issue Type: Bug Components: tfs Affects Versions: current Environment: Computer : windows xp/7 ,x86 Architecture Tomcat :Version 7.0.11 Jenkins:Version 1.450 tfs plugin:Version 1.20 Reporter: jlin sai Assignee: drewrm Labels: plugin Fix For: current Attachments: ErrorInfo.jpg I get a failure when I use the tfs plugin of Jenkins. The Source Code management tool what I use is Team Foundation Server 2010,when I manage the poll SCM in Jenkins,and want to trigger a build automatic when it detected a change between TFS server and Personal workspace , a failure hanppened ,which information is failed to record scm polling. Three months ago ,the version of tfs plugin is 1.17,I encount the failure ,and now the problem isn't resolved. I have been searched a method for a long time ,but not get it . I don't know what the reason is ,so please to help me to fixed the problem.Thank you very much! -- 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
[JIRA] (JENKINS-13411) Klocwork XML output is deprecated
[ https://issues.jenkins-ci.org/browse/JENKINS-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161619#comment-161619 ] Jacob Larfors commented on JENKINS-13411: - Hi Krzysztof, The response from Gwyn is as follows: This is indeed by design. Frankly, if you want to explore a defect, you should be doing it in the native environment, using the provided URL (from the Web API) to access Review at the right place, from where you can interact with the source, x-ref, all the nice functionality that you get there. And yes, before the question arises, reserving the line number was done specifically to avoid people trying to explore defects in environments that don't provide a rich enough infrastructure and therefore encourage developers to dismiss defects without truly understanding them (or cite them as noise, which amounts to the same thing). Also, when you say marking source with Klocwork findings, what exactly do you mean? If you would like an xml/txt report with line numbers then this can be gained from Review on the Issues page. Klocwork XML output is deprecated - Key: JENKINS-13411 URL: https://issues.jenkins-ci.org/browse/JENKINS-13411 Project: Jenkins Issue Type: New Feature Components: klocwork Reporter: Krzysztof Malinowski Assignee: gbois As http://www.klocwork.com/products/documentation/current/Kwinspectreport states: XML report is deprecated in KW 9.5 and will no longer be available. I recommend that plugin uses some other parser for the issues (csv maybe) or use web api to get the issues. -- 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
[JIRA] (JENKINS-13400) Workspace repository is not updated, and will be droped and re-cloned
[ https://issues.jenkins-ci.org/browse/JENKINS-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161621#comment-161621 ] cactusman commented on JENKINS-13400: - pull request https://github.com/jenkinsci/mercurial-plugin/pull/24 Workspace repository is not updated, and will be droped and re-cloned - Key: JENKINS-13400 URL: https://issues.jenkins-ci.org/browse/JENKINS-13400 Project: Jenkins Issue Type: Bug Components: mercurial Affects Versions: current Reporter: cactusman Assignee: cactusman If the Mercurial repository 'file://', has determined a different repository Jenkins Mercurial plugin by mistake. Therefore, the repository of the Workspace repository is not updated, and will be droped and re-cloned. Console output: [workspace] $ hg showconfig paths.default ERROR: Workspace reports paths.default as /var/hg/bar which looks different than file:///var/hg/bar so falling back to fresh clone rather than incremental update -- 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
[JIRA] (JENKINS-13446) Dependency graph points to localhost:8080
[ https://issues.jenkins-ci.org/browse/JENKINS-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161622#comment-161622 ] Tim Landscheidt commented on JENKINS-13446: --- Per https://bugzilla.wikimedia.org/show_bug.cgi?id=35982#c1, Jenkins URL is set to https://integration.mediawiki.org/ci/;, so the bug seems to be in Jenkins. Dependency graph points to localhost:8080 - Key: JENKINS-13446 URL: https://issues.jenkins-ci.org/browse/JENKINS-13446 Project: Jenkins Issue Type: Bug Components: depgraph-view Reporter: Tim Landscheidt Assignee: wolfs Priority: Trivial When looking at https://integration.mediawiki.org/ci/view/All/job/MediaWiki-postgres-phpunit/depgraph-view/? with Konqueror, Firefox or Chrome, the link in the graph points to http://localhost:8080/ci/view/All/job/MediaWiki-postgres-phpunit/. I haven't confirmed whether this bug actually lies with Jenkins and/or which plugin, but depgraph-view soundn't familiar :-). -- 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
[JIRA] (JENKINS-13457) support for hg flow
Joe Passavanti created JENKINS-13457: Summary: support for hg flow Key: JENKINS-13457 URL: https://issues.jenkins-ci.org/browse/JENKINS-13457 Project: Jenkins Issue Type: New Feature Components: mercurial Reporter: Joe Passavanti Assignee: Kohsuke Kawaguchi hg flow (https://bitbucket.org/yinwm/hgflow/wiki/Home) adds process control in Mercurial similar to git flow (https://github.com/nvie/gitflow). One of the outcomes of this process is that it creates and deletes branches all the time. For example: the releases branch in itself really doesn't have anything in it. In our process, we have mapped this to staging, so that, when we create a release, hg flow will create a branch under releases with whatever name we come up with. example: releases/rel_12 Once we deem this release as tested and ready to go live, hg flow will then merge it into the default (sometimes known as master) branch, which is where we then push out to our servers for production. It would be nice, if the Jenkins Mercurial plugin could help match this process. As it is today, when we create a new release, I have Jenkins set up with a parameter for the job, that we have to type in the current release branch every time we push an update. It would be nice if there could a checkbox or job config that would tell jenkins which of the top branches to monitor (releases,default,develop, etc.). Then the process would go as: # query hg branches and look for any branches under the branch named in the above config variable ## if its the releases branch, there should always only be 0 or 1 according to hg flow ## if 0, nothing for jenkins to do ## if more than 1, some kind of process problem, jenkins shouldn't continue # assuming there is a branch under releases, switch to it # run hg update on the branch ## if there are updates, process updates, run rest of job, capture the branch name (example: rel_15 for the branch releases/rel_15) and allow it to be a variable for post build actions (example: to be used with Jira plugin to tag tickets with the release branch for Jira changelog) ## if not, don't process rest of job -- 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
[JIRA] (JENKINS-8460) xUnit does not parse nested testsuite-tags from PHPUnit
[ https://issues.jenkins-ci.org/browse/JENKINS-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161623#comment-161623 ] Ferenc Kovacs commented on JENKINS-8460: hm. now I'm getting for the metric 'JUnit' is not valid. The result file has been skipped. for each of my sample junit.xml. could you give me a junit file which works for you? (of course all of my sample and production files are working with the built-in junit plugin just fine) I tried to test it with the latest release (non-lts) on a vanila ubuntu vm: same problem. xUnit does not parse nested testsuite-tags from PHPUnit - Key: JENKINS-8460 URL: https://issues.jenkins-ci.org/browse/JENKINS-8460 Project: Jenkins Issue Type: Improvement Components: xunit Affects Versions: current Environment: Debian Lenny, PHP 5.3.5-0.dotdeb., PHPUnit 3.5.7 Reporter: dito_ch Assignee: gbois Priority: Minor xUnit does not read the following output with nested testsuite-tags from PHPUnit: testsuites testsuite name=src/webroot/trackstar/protected/tests/unit tests=1 assertions=2 failures=0 errors=0 time=0.032417 testsuite name=DbTest file=src/protected/tests/unit/DbTest.php tests=1 assertions=2 failures=0 errors=0 time=0.032417 testcase name=testConnection class=DbTest file=src/protected/tests/unit/DbTest.php line=4 assertions=2 time=0.032417/ /testsuite /testsuite /testsuites The version without nested tags works: testsuites testsuite name=DbTest file=src/protected/tests/unit/DbTest.php tests=1 assertions=2 failures=0 errors=0 time=0.032417 testcase name=testConnection class=DbTest file=src/protected/tests/unit/DbTest.php line=4 assertions=2 time=0.032417/ /testsuite /testsuites I think it would be nice, if xUnit supports nested testsuite-tags. The workaround with a xlst is somehow cumbersome. -- 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
