[JIRA] [p4-plugin] (JENKINS-26455) Removing .p4config file during force clean
Paul Allen commented on JENKINS-26455 Removing .p4config file during force clean Thanks for the data. I hope the 1.1.3 release fixes the null path issue. There is a server fix for 14.2: #879410 (Bug #73373) ** 'p4 reconcile' elapsed time performance has been significantly improved when detecting files to open for add. There is still room for improvement in the plugin, for example I run the reconcile in two phases, one phase would be quicker. There are some new improvements for 15.1 where only the modtime is checked, but I have yet to take full advantage (the current MODTIME option has side-effects). 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-26601) StackOverflow Maven Job Parse Poms
Jesse Glick commented on JENKINS-26601 StackOverflow Maven Job Parse Poms BTW I am happy to merge to the rc branch to get it into 1.599, but I need someone to first confirm that the fix works. As previously noted, I encountered an unrelated error first that blocked me from testing 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/d/optout.
[JIRA] [modernstatus-plugin] (JENKINS-26554) Disabled Jobs Have No Modernized Icon (Still Gray Ball)
Oliver Vinn started work on JENKINS-26554 Disabled Jobs Have No Modernized Icon (Still Gray Ball) Change By: Oliver Vinn (30/Jan/15 3:44 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [matrix-project-plugin] (JENKINS-26712) Matrix project triggers concurrent build event if concurrent build option is off
Christoph Vogtländer created JENKINS-26712 Matrix project triggers concurrent build event if concurrent build option is off Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: jenkins_matrix_trigger_error.png Components: matrix-project-plugin Created: 30/Jan/15 4:35 PM Description: I have a Matrix project set up with a custom axis named "toolchain" with two parameters: amd64 arm32 In the project settings the "Execute concurrent builds if necessary" is off. Nonetheless, under certain conditions concurrent builds are triggered and a build is run in a "@2" directory. Steps to reproduce: trigger a new build, a trigger build is started on the master (without consuming a build executor), two builds are started on the slave (for arm32 and amd64) Info: the build for axis arm32 is much quicker than the build for amd64 trigger a second build - build is now in the queue waiting for the first build to finish when the sub build for axis arm32 finishes, the next build is executed right away without waiting for the amd64 build to be finished the second arm32 build will run in a "@2" folder like a concurrent build would the build for the second amd64 axis is queued correctly, waiting for the first build to finish When triggering a second build after the arm32 has already finished everything works fine - the whole build for both axes will stay in the queue until the amd64 axis build finishes. Environment: Jenkins ver. 1.565.3 LTS master ond Windows Server 2012, running as a Service Linux slave, connected via ssh custom shell script build steps Matrix Project Plugin versions 1.3 and 1.4 Project: Jenkins Priority: Minor Reporter: Christoph Vogtländer 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] [p4-plugin] (JENKINS-26713) P4Jenkins - Modifying Cilentspec Root
Ryan Hummer created JENKINS-26713 P4Jenkins - Modifying Cilentspec Root Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 30/Jan/15 4:43 PM Description: I am using a Matrix job to have agents sync and processes data every night. I have the axes configured as so: axes hudson.matrix.LabelAxis namenodes/name values stringrsmsnbuild120/string stringrsmsnbuild121/string /values /hudson.matrix.LabelAxis /axes The job is configured to use the Static workspace option. Upon the slaves being triggered the root of their clientspecs are changed from c:\path to c:\path\nodes\machinename. And the log prints out syncing using that path. I expect the Static workspace option to not modify my clientspec. Environment: Windows, P4Jenkins-1.1.3, Jenkins 1.580 Project: Jenkins Priority: Critical Reporter: Ryan Hummer 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] [accurev-plugin] (JENKINS-24710) Accurev changelog displays Action=Dispatch transactions
Skylar Sutton
updated JENKINS-24710
Accurev changelog displays Action="" transactions
Change By:
Skylar Sutton
(30/Jan/15 4:43 PM)
Summary:
Accurevchangelogdisplays
Action="">
Dispatch
actions
transactions
Description:
WehaveaJIRA--AccuRevsynchronizationprocesswhichrunsseveraltimesperhour(astheuseraccusync).WhileImnotintimatelyfamiliarwithoursynchprocess,theAccuRevtransactionlogindicateseverysync
uses
has
action="">
andnofilemodifications
.Previousversions(v0.6.27)oftheAccuRevJenkinsplugindidnotdisplaythesedispatchtransactionsinthechangelog,butafterupgradingtov0.6.30ourchangelogisfloodedwiththem.Documentationavailabledoesnotindicatethatthereisawaytomanuallydisable/ignorethesechangelogentries...soIwillassumethatinpreviousversionsthepluginwasignoringthemandthatfunctionalityhasbeenchanged.{code}• [JohnDoe]updatedfiletoincludehelpfilerelease1.0.10• [JaneDoe]Fixedsortedresultset.• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• ...about100more...• [accusync]{code}
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] [accurev-plugin] (JENKINS-24710) Accurev changelog displays Action=Dispatch transactions
Skylar Sutton edited a comment on JENKINS-24710 Accurev changelog displays Action="" transactions Modified description based on research into transaction types. 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] [subversion-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Tim Jaacks commented on JENKINS-26612 svn: absolutely unacceptably SLOW I can confirm this behaviour using Jenkins 1.580.3 on Ubuntu LTS 14.04. We have a quite large SVN repository here (~13 GB), which normally checks out in ~40 Minutes (natively on the Linux command line as well as via Jenkins). After upgrading the subversion-plugin in Jenkins, the checkout time increased to 10 1/2 hours. That is nearly 16 times slower. It makes no difference whether Jenkins is configured to use SVN 1.7 or 1.8. 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-26675) JVM-versions for autoinstall is not being updated
dennis Hoer updated JENKINS-26675 JVM-versions for autoinstall is not being updated Change By: dennis Hoer (30/Jan/15 4:51 PM) Description: ThelisthasnotbeenupdatedsinceJavareleasedits latests latest criticalpatches:http://mirror.xmission.com/jenkins/updates/updates/hudson.tools.JDKInstaller.json 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] [git-client-plugin] (JENKINS-26714) CliGitAPIImplTest fails when .gitconfig sets push.default = nothing
Martin dAnjou commented on JENKINS-26714 CliGitAPIImplTest fails when .gitconfig sets push.default = nothing See pull request for a proposed solution: https://github.com/jenkinsci/git-client-plugin/pull/160 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] [workflow-plugin] (JENKINS-26709) A stage with concurrency: 0 creates a zombie workflow.
Jesse Glick updated JENKINS-26709 A stage with concurrency: 0 creates a zombie workflow. Change By: Jesse Glick (30/Jan/15 3:19 PM) Priority: Major Minor Labels: robustness 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
acdha commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 We had the same problem – a quick dpkg install of http://pkg.jenkins-ci.org/debian/binary/jenkins_1.597_all.deb fixed it as well. 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] [multijob-plugin] (JENKINS-26715) Multijob plugin support for polling subjobs
Caleb Mayeux created JENKINS-26715 Multijob plugin support for polling subjobs Issue Type: Improvement Assignee: Caleb Mayeux Components: multijob-plugin Created: 30/Jan/15 5:08 PM Description: It would be nice if a multijob job could optionally poll its children in addition to itself when polling for changes. Rationale for enhancement: The multijob type is ideal for componentized builds which can be built as individual components or together as a large package, by grouping individual standalone jobs that can be built in parallel. However, those standalone components can have their own SCM checkout steps different from the multijob itself (in my case the multijob is a container with no SCM checkout), which means the multijob that contains them can't detect whether or not there are changes when polling. Super simplified scenario I'm facing: Suppose you have a multijob that is merely a container for subjobs A, B, and C. A checks out code, B builds a component, and C does some bundling. In this configuration, there is no way to poll for changes without going outside of the multijob plugin and thus losing the benefits of it. Environment: Jenkins 1.580.2, multijob-plugin 1.16, RHEL 5.5 Project: Jenkins Priority: Major Reporter: Caleb Mayeux 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] [modernstatus-plugin] (JENKINS-26554) Disabled Jobs Have No Modernized Icon (Still Gray Ball)
SCM/JIRA link daemon commented on JENKINS-26554 Disabled Jobs Have No Modernized Icon (Still Gray Ball) Code changed in jenkins User: Oliver Vinn Path: .gitignore pom.xml src/main/java/jenkinsci/plugins/modernstatus/ModernStatusFilter.java src/main/webapp/16x16/aborted.gif src/main/webapp/16x16/aborted.png src/main/webapp/16x16/blue.gif src/main/webapp/16x16/blue.png src/main/webapp/16x16/clock.gif src/main/webapp/16x16/clock.png src/main/webapp/16x16/disabled.gif src/main/webapp/16x16/disabled.png src/main/webapp/16x16/disabled_anime.gif src/main/webapp/16x16/edit-delete.gif src/main/webapp/16x16/edit-delete.png src/main/webapp/16x16/folder.gif src/main/webapp/16x16/folder.png src/main/webapp/16x16/grey.gif src/main/webapp/16x16/grey.png src/main/webapp/16x16/nobuilt.gif src/main/webapp/16x16/nobuilt.png src/main/webapp/16x16/red.gif src/main/webapp/16x16/red.png src/main/webapp/16x16/yellow.gif src/main/webapp/16x16/yellow.png src/main/webapp/24x24/aborted.gif src/main/webapp/24x24/aborted.png src/main/webapp/24x24/blue.gif src/main/webapp/24x24/blue.png src/main/webapp/24x24/clock.gif src/main/webapp/24x24/clock.png src/main/webapp/24x24/disabled.gif src/main/webapp/24x24/disabled.png src/main/webapp/24x24/disabled_anime.gif src/main/webapp/24x24/edit-delete.gif src/main/webapp/24x24/edit-delete.png src/main/webapp/24x24/folder.gif src/main/webapp/24x24/folder.png src/main/webapp/24x24/grey.gif src/main/webapp/24x24/grey.png src/main/webapp/24x24/nobuilt.gif src/main/webapp/24x24/nobuilt.png src/main/webapp/24x24/red.gif src/main/webapp/24x24/red.png src/main/webapp/24x24/yellow.gif src/main/webapp/24x24/yellow.png src/main/webapp/32x32/aborted.gif src/main/webapp/32x32/aborted.png src/main/webapp/32x32/blue.gif src/main/webapp/32x32/blue.png src/main/webapp/32x32/clock.gif src/main/webapp/32x32/clock.png src/main/webapp/32x32/disabled.gif src/main/webapp/32x32/disabled.png src/main/webapp/32x32/disabled_anime.gif src/main/webapp/32x32/edit-delete.gif src/main/webapp/32x32/edit-delete.png src/main/webapp/32x32/folder.gif src/main/webapp/32x32/folder.png src/main/webapp/32x32/grey.gif src/main/webapp/32x32/grey.png src/main/webapp/32x32/nobuilt.gif src/main/webapp/32x32/nobuilt.png src/main/webapp/32x32/red.gif src/main/webapp/32x32/red.png src/main/webapp/32x32/yellow.gif src/main/webapp/32x32/yellow.png src/main/webapp/48x48/aborted.gif src/main/webapp/48x48/aborted.png src/main/webapp/48x48/blue.gif src/main/webapp/48x48/blue.png src/main/webapp/48x48/clock.gif src/main/webapp/48x48/clock.png src/main/webapp/48x48/disabled.gif src/main/webapp/48x48/disabled.png src/main/webapp/48x48/disabled_anime.gif src/main/webapp/48x48/edit-delete.gif src/main/webapp/48x48/edit-delete.png src/main/webapp/48x48/folder.gif src/main/webapp/48x48/folder.png src/main/webapp/48x48/grey.gif src/main/webapp/48x48/grey.png src/main/webapp/48x48/nobuilt.gif src/main/webapp/48x48/nobuilt.png src/main/webapp/48x48/red.gif src/main/webapp/48x48/red.png src/main/webapp/48x48/yellow.gif src/main/webapp/48x48/yellow.png src/main/webapp/generate.sh http://jenkins-ci.org/commit/modernstatus-plugin/4a48db648f246527e79ce9a393202527dc71e752 Log: JENKINS-26554 Disabled job icon not replaced 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] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows loading jobs..
SCM/JIRA link daemon commented on JENKINS-23620 The periodic refresh shows loading jobs.. Code changed in jenkins User: dvelderp Path: src/main/webapp/walldisplay.js http://jenkins-ci.org/commit/walldisplay-plugin/f6be12fe459d214759694c11f8f6fe13c193c2a0 Log: JENKINS-23620 Fix job display distorted when multiple column display 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] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows loading jobs..
SCM/JIRA link daemon commented on JENKINS-23620 The periodic refresh shows loading jobs.. Code changed in jenkins User: Pelle Pelster Path: src/main/webapp/walldisplay.js http://jenkins-ci.org/commit/walldisplay-plugin/5c3e5b143126188b3c75a1a2a5fa32fd559e38f2 Log: Merge pull request #39 from pvelder/master JENKINS-23620 Fix job display distorted when multiple column display Compare: https://github.com/jenkinsci/walldisplay-plugin/compare/a2874733c077...5c3e5b143126 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-26675) JVM-versions for autoinstall is not being updated
dennis Hoer commented on JENKINS-26675 JVM-versions for autoinstall is not being updated Thanks Christopher 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] [xcode-plugin] (JENKINS-24980) Keychain Management issue.
Tom Jones
commented on JENKINS-24980
Keychain Management issue.
Currently plugin does this:
launcher.launch().envs(envs).cmds("/usr/bin/security", "list-keychains", "-s", keychainPath).stdout(listener).pwd(projectRoot).join();
which is the equivalent of this:
security list-keychains -s ${KEYCHAIN_PATH}
Needs to do this:
security list-keychains | xargs security list-keychains -s "${KEYCHAIN_PATH}"
And then when finished building, the plugin should do the equivalent of this:
security delete-keychain "${KEYCHAIN_PATH}"
Not entirely sure how the first part would be done in java.
Unrelated matter that this also fixes, the Keychain is left in the workspace, and its password is shown in plain text in the environment variables, which allows a developer on your team to download the keychain, unlock and extract the private keys (which raises the question, why have a password?)
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] [git-plugin] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository
Brent Johnson commented on JENKINS-22752 Initial poll (just after project creation) spawns builds for all the existing branches in repository This is an issue for me as well. We have 200+ active branches. Every time I set up a new job, it has to process all the branches which takes days. I really only want it to run for go-forward commits. Note that the git polling log shows: Started on Jan 30, 2015 12:02:07 PM Polling SCM changes on master Using strategy: Default poll Last Built Revision: Revision cd2a0430283cdbbd378900fd849caca4b2674bc1 (origin/bugfix/XYBACKLOG-12369) What I would like is an option to be able to set the "Last Built Revision" to the latest revision in the repository when I first create a new job. In the hope that git polling would only detect future commits, not run the job for all existing branches. 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] [modernstatus-plugin] (JENKINS-26554) Disabled Jobs Have No Modernized Icon (Still Gray Ball)
Oliver Vinn commented on JENKINS-26554 Disabled Jobs Have No Modernized Icon (Still Gray Ball) An oversight by me as I don't disable jobs. I'm readying an update to push that will fill this gap. Thanks for reporting. 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] [warnings-plugin] (JENKINS-26682) Can't parse jslint-formatted XML file
Ulli Hafner commented on JENKINS-26682 Cant parse jslint-formatted XML file Hmm, seems that the file is deleted while the plug-in is running. Is the build on a slave? Is the workspace mounted on a special device? Is another plugin active that accesses the file? Is the xml file still present after the Exception occured? 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] [email-ext-plugin] (JENKINS-26711) email-ext plugin converting html tags
nitin gupta created JENKINS-26711 email-ext plugin converting html tags Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 30/Jan/15 4:15 PM Description: I am trying to send an html file via this plugin and it is converting all "" as and "" as "", hence they are not actually expanding as proper html in the email. so content table , comes as table and in the email, i can see the message as "table" and no table gets created. I have plugin version 2.39, jenkins version 1.594 Project: Jenkins Priority: Critical Reporter: nitin gupta 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-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/RunIdMigrator.java core/src/test/java/jenkins/model/RunIdMigratorTest.java http://jenkins-ci.org/commit/jenkins/4a75e058bafd3cd98832a2a129c9f23c71d26f55 Log: JENKINS-26519 Attempting to improve diagnostics in case rename fails. (cherry picked from commit 0633beef0868c59a7e853731aee5f5c0745fa3fc) 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-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/RunIdMigrator.java http://jenkins-ci.org/commit/jenkins/22dc8add0e106d100a73c16cb628f1c5d1f94538 Log: JENKINS-26519 More diagnostics in case a numeric rename target already exists. (cherry picked from commit 75c8c31f2fdc98081a0446dd3ee03da7243304a1) 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-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/model/RunIdMigrator.java core/src/test/java/jenkins/model/RunIdMigratorTest.java http://jenkins-ci.org/commit/jenkins/7f82ab94a4f6247abaf9f65998360be5c3136bf8 Log: FIXED JENKINS-26519 Build record migration failed on Windows using Java 6. In this environment, Util.createSymlink and .isSymlink are implemented, but resolveSymlink is not. (cherry picked from commit 388c4b5e6ba52037cae117c5c69f9f4156d41401) Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/1debf06fe6d6...7f82ab94a4f6 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-26700) Download build artifacts as zip generates a corrupted file
Jason Sipula commented on JENKINS-26700 Download build artifacts as zip generates a corrupted file Seems for me, it affects both sub-directories as well as the entire workspace so long as the file size is 20.6MB's. Individual artifacts appear to download fine. I originally noticed this trying to download a sub-dir of the workspace, which should be ~110MB's in zip form, but it always truncates at 20.6MB's and the zip is corrupted (cannot be unzipped). Seems like it transfers are normal speeds, either 5-10Mbps+ on the local lan (assuming it's not faster due to overhead of creating the zip) and about 1Mbps over the net. You can view my scenario at: http://build.vanomaly.net/ Click into any of the recent builds (for any project) and try to use the download as zip function for the workspace or any sub 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/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-26711) email-ext plugin converting html tags
Alex Earl resolved JENKINS-26711 as Duplicate email-ext plugin converting html tags Change By: Alex Earl (30/Jan/15 4:54 PM) Status: Open Resolved Resolution: Duplicate 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] [accurev-plugin] (JENKINS-24710) Accurev changelog displays Dispatch actions
Skylar Sutton
updated JENKINS-24710
Accurev changelog displays Dispatch actions
Change By:
Skylar Sutton
(30/Jan/15 4:40 PM)
Summary:
Invalid
Accurev
changelogentries([accusync])
changelogdisplaysDispatchactions
Description:
After
WehaveaJIRA--AccuRevsynchronizationprocesswhichrunsseveraltimesperhour(astheuseraccusync).WhileImnotintimatelyfamiliarwithoursynchprocess,theAccuRevtransactionlogindicateseverysyncusesaction="">Previousversions(v0.6.27)oftheAccuRevJenkinsplugindidnotdisplaythesedispatchtransactionsinthechangelog,butafter
upgradingto
0
v0
.6.30ourchangelogisfloodedwith
emptyaccusync
them.Documentationavailabledoesnotindicatethatthereisawaytomanuallydisable/ignorethesechangelog
entries
:
...soIwillassumethatinpreviousversionsthepluginwasignoringthemandthatfunctionalityhasbeenchanged.
{code}• [JohnDoe]updatedfiletoincludehelpfilerelease1.0.10• [JaneDoe]Fixedsortedresultset.• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• [accusync]• ...about100more...• [accusync]{code}
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] [subversion-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Tim Jaacks updated JENKINS-26612 svn: absolutely unacceptably SLOW Thread dumps during SVN checkout Change By: Tim Jaacks (30/Jan/15 4:44 PM) Attachment: jstack.9869.174019.063479021 Attachment: jstack.9869.174023.295933057 Attachment: jstack.9869.174036.322157146 Attachment: jstack.9869.174040.509650263 Attachment: jstack.9869.174002.556309901 Attachment: jstack.9869.174027.694424318 Attachment: jstack.9869.174006.816727552 Attachment: jstack.9869.174031.893417175 Attachment: jstack.9869.174014.978534833 Attachment: jstack.9869.174010.994963385 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] [subversion-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Tim Jaacks edited a comment on JENKINS-26612 svn: absolutely unacceptably SLOW Attached thread dumps during SVN checkout 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] [git-client-plugin] (JENKINS-26714) CliGitAPIImplTest fails when .gitconfig sets push.default = nothing
Martin dAnjou created JENKINS-26714 CliGitAPIImplTest fails when .gitconfig sets push.default = nothing Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 30/Jan/15 4:44 PM Description: Steps to reproduce: When push.default is set to nothing like so in .gitconfig: [push] default = nothing Run the test_push_tags test: mvn -Dtest=CliGitAPIImplTest#test_push_tags test Result: Running org.jenkinsci.plugins.gitclient.CliGitAPIImplTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.762 sec FAILURE! - in org.jenkinsci.plugins.gitclient.CliGitAPIImplTest test_push_tags(org.jenkinsci.plugins.gitclient.CliGitAPIImplTest) Time elapsed: 2.725 sec ERROR! hudson.plugins.git.GitException: Command "git -c core.askpass=true push /tmp/hudson751564288875417152test" returned status code 128: stdout: stderr: fatal: You didn't specify any refspecs to push, and push.default is "nothing". at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1493) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1281) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1560) at org.jenkinsci.plugins.gitclient.GitAPITestCase.test_push_tags(GitAPITestCase.java:937) 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:606) at org.jenkinsci.plugins.gitclient.CliGitAPIImplTest.runTest(CliGitAPIImplTest.java:30) Project: Jenkins Priority: Minor Reporter: Martin dAnjou 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] [mailer-plugin] (JENKINS-26707) Email list parsing not spec compliant
Tom FENNELLY commented on JENKINS-26707 Email list parsing not spec compliant Ooops sorry about the duplicate. Router problems causing slow connection, causing me to press the create button twice 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-24155) Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot
Patricia Wright commented on JENKINS-24155 Jenkins Slaves Go Offline In Large Quantities and Dont Reconnect Until Reboot I'm still having this issue. 1.580.2 I have a large number of slaves that reboot as part of our testing process (tests complete, systems shut down). These slaves go offline in this fashion. 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-26703) For 'project-based security' don't work disable 'grants the ability to cancel a build'
Daniel Beck commented on JENKINS-26703 For project-based security dont work disable grants the ability to cancel a build Needs a security realm implementation that ignores implied dependencies. I know those exist, but I don't know a public one. Alternatively, patch your Jenkins. Neither option is that great I admit. 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] [script-security-plugin] (JENKINS-25119) Sandbox cannot handle methods Groovy provides additionally
Jesse Glick resolved JENKINS-25119 as Fixed Sandbox cannot handle methods Groovy provides additionally Change By: Jesse Glick (30/Jan/15 9:52 PM) Status: Open Resolved Assignee: ikedam JesseGlick Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [clearcase-plugin] (JENKINS-26719) Intermittant exception generated using clearcase plugin dynamic view when running mkview immediately after the rmview
John Lengeling created JENKINS-26719 Intermittant exception generated using clearcase plugin dynamic view when running mkview immediately after the rmview Issue Type: Bug Assignee: Vincent Latombe Components: clearcase-plugin Created: 30/Jan/15 11:12 PM Description: Our jobs are setup to use dynamic views and the settings are to remove view and re-create a clean view every time the job runs. I am also using a static view tag name. So we use the view name over and over. So when the job runs, the clearcase plugin will remove the dynamic view using rmview followed immediately with a mkview. We intermittently see an exception on the mkview. Draco_ML-MPH6 $ /usr/atria//bin/cleartool lsview mrfbldac_Draco_ML-MPH6 mrfbldac_Draco_ML-MPH6 /ccase_viewstg/mrfbldac/mrfbldac_Draco_ML-MPH6.vws Draco_ML-MPH6 $ /usr/atria//bin/cleartool rmview -force -tag mrfbldac_Draco_ML-MPH6 Removing references from VOB "/vobs/mrf_vob1" ... Removed references to view "/ccase_viewstg/mrfbldac/mrfbldac_Draco_ML-MPH6.vws" from VOB "/vobs/mrf_vob1". Removing references from VOB "/vobs/mrf_pvob" ... Removed references to view "/ccase_viewstg/mrfbldac/mrfbldac_Draco_ML-MPH6.vws" from VOB "/vobs/mrf_pvob". Draco_ML-MPH6 $ /usr/atria//bin/cleartool mkview -stream Draco_ML_int@/vobs/mrf_pvob -tag mrfbldac_Draco_ML-MPH6 -stgloc -auto Selected Server Storage Location "inview02_viewstg". cleartool: Error: Failed to record hostname "inview02" in storage directory "/ccase_viewstg/mrfbldac/mrfbldac_Draco_ML-MPH6.vws". Check that root or the ClearCase administrators group has permission to write to this directory. cleartool: Error: Unable to create view "/ccase_viewstg/mrfbldac/mrfbldac_Draco_ML-MPH6.vws". FATAL: UCM ClearCase failed. exit code=1 java.io.IOException: cleartool did not return the expected exit code. Command line="mkview -stream Draco_ML_int@/vobs/mrf_pvob -tag mrfbldac_Draco_ML-MPH6 -stgloc -auto", actual exit code=1 at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:152) at hudson.plugins.clearcase.ClearToolExec.mkview(ClearToolExec.java:562) at hudson.plugins.clearcase.action.UcmDynamicCheckoutAction.prepareView(UcmDynamicCheckoutAction.java:217) at hudson.plugins.clearcase.action.UcmDynamicCheckoutAction.checkout(UcmDynamicCheckoutAction.java:88) at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:383) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: FAILURE This article seems to indicate that when removing a view an immediately re-creating it causes the error when using NFS shares. The article seems to indicate that a brief delay between the rmview/mkview will resolve the issue: https://sdecorner.wordpress.com/2013/05/06/clearcaseerror-when-re-creating-a-view-on-nfs-share/ Environment: Jenkins 1.580.1, RHEL 5.7, Dynamic view, NetApp view storage, ClearCase 7.1.2.6 Project: Jenkins Labels: clearcase exception Priority: Minor Reporter:
[JIRA] [artifactory-plugin] (JENKINS-18016) Artifactory plugin adds arguments when editing a job configuration while the job is building
Brian Carr commented on JENKINS-18016 Artifactory plugin adds arguments when editing a job configuration while the job is building In our normal (and sadly complex) build jobs we invoke ant twice. First ant complies and builds the database tools, then the database tools are used to build the test database, then ant is used to run all the tests. The configuration options are added to the second / last ant invocation while they are required in the build step (first invocation). There is an additional problem in that the library location is slave specific while the job can run on multiple slaves (above the e:/Jenkins/workspace requires that all slaves be run from e:/Jenkins/ which is not the case for our slaves). Our workaround is to use %WORKSPACE% relative references on the first invocation. I would recommend that all ant invocations get relative references, e.g. %WORKSPACE%/../../caches/artifactory-plugin/2.2.7 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-26601) StackOverflow Maven Job Parse Poms
Daniel Beck commented on JENKINS-26601 StackOverflow Maven Job Parse Poms Seems to work. Rather than use Geoff Cummings' test repo, I built a simple Jenkins plugin in a project configured to use a local repo in the workspace (which always gets cleaned up), like the attached config. 1.600-SNAPSHOT build with Guice 4.0-beta5: StackOverflowError 1.600-SNAPSHOT build with Guice 4.0-beta/no_aop: Maven first downloads the internet, then I get an HPI. 1.600-SNAPSHOT from Jan 28 with Guice 4.0-beta: Maven first downloads the internet again, then I get an HPI. So it seems to resolve 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] [xcode-plugin] (JENKINS-24980) Keychain Management issue.
lacostej commented on JENKINS-24980 Keychain Management issue. Tom, a few things: WRT to adding, yes there's some code more or less ready to support it. Nice use of the xargs for adding to the list It's still not 100% atomic, but the risk is low though. I wasn't aware of the password being available in the log. I don't seem to see it in mine but I am maybe using another way of using the keychains. I checked the code and the command that use the keychain passwords are supposed to mask it when printing to the log. I also do not see the keychain in my workspace 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Steve Todorov commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 After upgrading to the latest 1.598 we had the same StackOverflow exception as everybody. Downgrading Maven Project Plugin to version 2.7.1 solves the 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] [core] (JENKINS-26718) Can't discard promoted-buids Promotions
recampbell created JENKINS-26718 Cant discard promoted-buids Promotions Issue Type: Bug Assignee: recampbell Components: core Created: 30/Jan/15 9:51 PM Description: If all OldDataMonitor entries are related to Promoted Builds, then the monitor isActivated(), but it won't be able to discard these builds. The problem is that hudson.diagnosis.OldDataMonitor.RunSaveableReference expects runs to be locatable by their externalizableId, but Promotions are broken in this respect. Project: Jenkins Priority: Minor Reporter: recampbell 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-22853) SEVERE: Trying to unexport an object that's already unexported
Martin Konrad commented on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported I'm seeing this issue for parameterized builds. If I disable parameters everything works smoothly - no errors. I'm running 1.565.2. 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-26601) StackOverflow Maven Job Parse Poms
SCM/JIRA link daemon commented on JENKINS-26601 StackOverflow Maven Job Parse Poms Code changed in jenkins User: Jesse Glick Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/a0942b88346d66770336daec7bf82063163e8001 Log: FIXED JENKINS-26601 Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899. (cherry picked from commit 00c858d403ab1f7747de0b9ce80e1eef921c41b3 into 1.599 rc) 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] [log-parser-plugin] (JENKINS-26572) Log Parser incompatible with Jenkins 1.597 (build record change)
AnneTheAgile commented on JENKINS-26572 Log Parser incompatible with Jenkins 1.597 (build record change) Do we know what to fix in the code for this? Refs; 1.[]Jenkins' Current version is after the ref'd version, ie v 1.598 (2015/01/25) ; X.Changelog | Jenkins CI ;; http://jenkins-ci.org/changelog 2.[]BUG? there are several merged issues but no release since 2010 ; X.Pull Requests · jenkinsci/log-parser-plugin ;; https://github.com/jenkinsci/log-parser-plugin/pulls?q=is%3Apr+is%3Aclosed 3.[]BUG; does not reference Github ; X.Log Parser Plugin - Jenkins - Jenkins Wiki ;; https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin 4.[]Docs about the build record change ; X.JENKINS-24380 Migration - Jenkins - Jenkins Wiki ;; https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration 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] [workflow-plugin] (JENKINS-26699) Workflow plugin silently breaks regular Groovy maps
James VL commented on JENKINS-26699 Workflow plugin silently breaks regular Groovy maps Thanks for taking the time to clarify this - I appreciate it. Didn't find the duplicate bug reort when I first searched. I wasn't sure if this feel under "fundamental limitation" or "CPS / Serialization bug". I've reverted to plain old loops in the mean time. 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-26601) StackOverflow Maven Job Parse Poms
dogfood commented on JENKINS-26601 StackOverflow Maven Job Parse Poms Integrated in jenkins_main_trunk #3961 FIXED JENKINS-26601 Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899. (Revision a0942b88346d66770336daec7bf82063163e8001) Result = SUCCESS jesse glick : a0942b88346d66770336daec7bf82063163e8001 Files : pom.xml changelog.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-26519) Build records not migrated due to “failed to rename” on Windows
dogfood commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Integrated in jenkins_main_trunk #3961 JENKINS-26519 Attempting to improve diagnostics in case rename fails. (Revision 4a75e058bafd3cd98832a2a129c9f23c71d26f55) JENKINS-26519 More diagnostics in case a numeric rename target already exists. (Revision 22dc8add0e106d100a73c16cb628f1c5d1f94538) FIXED JENKINS-26519 Build record migration failed on Windows using Java 6. (Revision 7f82ab94a4f6247abaf9f65998360be5c3136bf8) Result = SUCCESS jesse glick : 4a75e058bafd3cd98832a2a129c9f23c71d26f55 Files : core/src/main/java/jenkins/model/RunIdMigrator.java core/src/test/java/jenkins/model/RunIdMigratorTest.java jesse glick : 22dc8add0e106d100a73c16cb628f1c5d1f94538 Files : core/src/main/java/jenkins/model/RunIdMigrator.java jesse glick : 7f82ab94a4f6247abaf9f65998360be5c3136bf8 Files : core/src/test/java/jenkins/model/RunIdMigratorTest.java core/src/main/java/jenkins/model/RunIdMigrator.java changelog.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] [git-client-plugin] (JENKINS-26714) CliGitAPIImplTest fails when .gitconfig sets push.default = nothing
Martin dAnjou closed JENKINS-26714 as Wont Fix CliGitAPIImplTest fails when .gitconfig sets push.default = nothing Change By: Martin dAnjou (30/Jan/15 5:51 PM) Status: Resolved Closed 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] [multijob-plugin] (JENKINS-26715) Multijob plugin support for polling subjobs
Caleb Mayeux commented on JENKINS-26715 Multijob plugin support for polling subjobs Created pull request #62 to add this feature. 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] [modernstatus-plugin] (JENKINS-26554) Disabled Jobs Have No Modernized Icon (Still Gray Ball)
Oliver Vinn resolved JENKINS-26554 as Fixed Disabled Jobs Have No Modernized Icon (Still Gray Ball) Change By: Oliver Vinn (30/Jan/15 5:36 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ec2-plugin] (JENKINS-26716) Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary
Trevor Baker edited a comment on JENKINS-26716 Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary Very similar to JENKINS-25963. 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] [ec2-plugin] (JENKINS-26716) Jobs throttled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary
Trevor Baker updated JENKINS-26716 Jobs throttled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary Change By: Trevor Baker (30/Jan/15 6:11 PM) Summary: Jobs thottled throttled viatheThrottleConcurrentBuildspluginfailtolaunchnewec2provisionedslaveswhennecessary 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] [workflow-plugin] (JENKINS-26699) Workflow plugin silently breaks regular Groovy maps
James VL commented on JENKINS-26699 Workflow plugin silently breaks regular Groovy maps I'm realizing that now, in trying to use lists in other places. If that was in the docs somewhere I totally missed it. Shall I assume that most groovy features which work with closures are not permitted in the workflow script then? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-client-plugin] (JENKINS-26714) CliGitAPIImplTest fails when .gitconfig sets push.default = nothing
Martin dAnjou resolved JENKINS-26714 as Wont Fix CliGitAPIImplTest fails when .gitconfig sets push.default = nothing I decided that the user should change their .gitconfig rather than change the test. Change By: Martin dAnjou (30/Jan/15 5:51 PM) 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Steve Todorov edited a comment on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 After upgrading to the latest 1.598 we had the same StackOverflow exception as everybody. Downgrading Maven Project Plugin to version 2.7.1 solved the issue for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ec2-plugin] (JENKINS-26716) Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves
Trevor Baker created JENKINS-26716 Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves Issue Type: Bug Assignee: Dominik Bartholdi Components: ec2-plugin, nodelabelparameter-plugin Created: 30/Jan/15 6:00 PM Description: The EC2 plugin works great for dynamically provisioning EC2 slaves (as needed) when their label is specified under "Restrict where this project can be run," but it doesn't do anything if that label is passed in using a NodeLabel parameter. Note that this only seems to affect the EC2 provisioning step; jobs set to run on a slave via NodeLabel parameter will happily run on provisioned-by-EC2-plugin slaves that are already around. Project: Jenkins Priority: Major Reporter: Trevor Baker 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-plugin] (JENKINS-26717) Build hangs while retrieving user email from active directory
Sean Sutherland created JENKINS-26717 Build hangs while retrieving user email from active directory Issue Type: Bug Assignee: Unassigned Components: active-directory-plugin Created: 30/Jan/15 6:36 PM Description: Our post-build email notification appears to be hanging while retrieving a user's email address through active directory. Additional info: On the job page's build history, the build will show as complete, with no x button. The console output of the build will have a spinning circle indicating it is still working. On the executor list, the build still shows as running, but the x button does not have any effect thread callstack: at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:152) at java.net.SocketInputStream.read(SocketInputStream.java:122) at sun.security.ssl.InputRecord.readFully(InputRecord.java:442) at sun.security.ssl.InputRecord.read(InputRecord.java:480) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927) locked java.lang.Object@6edd1ae2 at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312) locked java.lang.Object@7610244a at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:702) at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:122) locked sun.security.ssl.AppOutputStream@52ce8b8d at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) locked java.io.BufferedOutputStream@3d45174a at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:431) locked com.sun.jndi.ldap.Connection@74c20900 at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:404) at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient.java:1200) at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3206) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:486) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:430) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:273) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:219) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:163) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:53) at hudson.plugins.active_directory.ActiveDirectoryMailAddressResolverImpl.findMailAddressFor(ActiveDirectoryMailAddressResolverImpl.java:54) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:122) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:560) at hudson.plugins.emailext.EmailRecipientUtils.getUserConfiguredEmail(EmailRecipientUtils.java:110) at hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider.addRecipients(CulpritsRecipientProvider.java:41) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:578) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:306) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:297) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:244) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at com.cloudbees.plugins.flow.FlowRun$BuildWithWorkspaceRunnerImpl.cleanUp(FlowRun.java:242) at hudson.model.Run.execute(Run.java:1805) at hudson.model.Run.run(Run.java:1697) at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:167) at
[JIRA] [artifactory-plugin] (JENKINS-24949) Artifactory plugin version 2.2.4 uses ivy-2.2.0.jar
Brian Carr commented on JENKINS-24949 Artifactory plugin version 2.2.4 uses ivy-2.2.0.jar We use ivy version 2.3 and the inclusion of ivy 2.2 causes obscure build failures which are difficult to attribute to artifactory-plugin. Sounds like unrelated ivy issues so tracking down the root cause is most time consuming. Fix is messy! We would suggest a configuration option which would allow us to specify which version of ivy to include in any and where to get the jar file. For us it would be fine to be server configuration rather than job configuration as we have standardized on the version of ivy which goes with our ant version (also standardized). 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] [ec2-plugin] (JENKINS-26716) Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary
Trevor Baker updated JENKINS-26716 Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary Change By: Trevor Baker (30/Jan/15 6:03 PM) Summary: JobsthottledviatheThrottleConcurrentBuildspluginfailtolaunchnewec2provisionedslaves whennecessary Description: TheEC2pluginworksgreatfordynamicallyprovisioningEC2 Whenconcurrentjobsarethrottledacrosscategoriesnewec2provisioned slaves (asneeded) arenotlaunched when theirlabelisspecifiedunderRestrictwherethisprojectcanberun,butitdoesntdoanythingifthatlabelispassedinusingaNodeLabelparameter theyarerequired . Note Theec2pluginshouldnotdetect that thisonlyseemstoaffect eventhoughtheremaybeexecutorsavailablethattheycannotrun the EC2provisioningstep;jobsset job(s)due to runonaslaveviaNodeLabelparameterwillhappilyrunonprovisioned-by-EC2-pluginslavesthatarealreadyaround concurrentthrottling . Thesetwopluginsshouldinteropasexpected. Assignee: DominikBartholdi Component/s: throttle-concurrent-builds-plugin Component/s: nodelabelparameter-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [analysis-core-plugin] (JENKINS-25917) Spaces in URL (from project name or view) cause invalid cookie to be saved when configuring trend graphs
Ulli Hafner updated JENKINS-25917 Spaces in URL (from project name or view) cause invalid cookie to be saved when configuring trend graphs Change By: Ulli Hafner (30/Jan/15 6:03 PM) Priority: Major Minor Labels: configurationplugin 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] [workflow-plugin] (JENKINS-26699) Workflow plugin silently breaks regular Groovy maps
Jesse Glick commented on JENKINS-26699 Workflow plugin silently breaks regular Groovy maps If that was in the docs somewhere I totally missed it. We do not generally write up obvious bugs (as opposed to fundamental limitations) in documentation. The time would be better spent fixing them. The Workflow index page links to a JIRA query of open issues. Shall I assume that most groovy features which work with closures are not permitted in the workflow script then? Closures in general work. (For example the Docker demo uses a function taking a closure as an argument.) JENKINS-26481 just notes that some built-in operations on collections taking closures do not appear to work, presumably a bug in the groovy-cps library which provides CPS-transformed code for every Groovy operator and control flow element. For these cases you currently need to use other syntactic idioms, such as plain old loops. 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-26703) For 'project-based security' don't work disable 'grants the ability to cancel a build'
Sergey Ryabov commented on JENKINS-26703 For project-based security dont work disable grants the ability to cancel a build Daniel, thank you for your answer. Do you know some solution this problem? May be exist some opportunity that can resolve this question? 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] [p4-plugin] (JENKINS-26589) p4jenkins set client root to null
dan tran reopened JENKINS-26589 p4jenkins set client root to null Still see the issue. and It is very intermittent. will manage to find a patter Change By: dan tran (31/Jan/15 12:01 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26700) Download build artifacts as zip generates a corrupted file
Jason Sipula edited a comment on JENKINS-26700 Download build artifacts as zip generates a corrupted file Seems for me, it affects both sub-directories as well as the entire workspace so long as the file size is 20.6MB's. Individual artifacts appear to download fine. I originally noticed this trying to download a sub-dir of the workspace, which should be ~110MB's in zip form, but it always truncates at 20.6MB's and the zip is corrupted (cannot be unzipped). Seems like it transfers are normal speeds, either 5-10Mbps+ on the local lan (assuming it's not faster due to overhead of creating the zip) and about 1Mbps over the net. 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] [p4-plugin] (JENKINS-26176) P4 plugin: Error Error occurred during the SSL handshake: invalid SSL session
dan tran commented on JENKINS-26176 P4 plugin: Error Error occurred during the SSL handshake: invalid SSL session you need to update your jre/lib/security to get unlimited encryption policy. Here is link to oracle jre 7 http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.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] [extensible-choice-parameter-plugin] (JENKINS-26721) FilenameChoiceListProvider cause security problems
ikedam created JENKINS-26721 FilenameChoiceListProvider cause security problems Issue Type: Bug Assignee: ikedam Components: extensible-choice-parameter-plugin Created: 31/Jan/15 2:03 AM Description: FilenameChoiceListProvider lists all files with specified patterns. This allows evil users to see lists of files on the host where Jenkins runs. Generally, it can cause security problems. Environment: extensible-choice-parameter-1.2.2 Project: Jenkins Labels: security Priority: Major Reporter: ikedam 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] [subversion-plugin] (JENKINS-26158) Active Directory authentication for Subversion plugin fails
Steven Christou started work on JENKINS-26158 Active Directory authentication for Subversion plugin fails Change By: Steven Christou (31/Jan/15 3:07 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [artifactory-plugin] (JENKINS-26720) Artifactory plugin causes exception in project/configure page
Derrick Southerland created JENKINS-26720 Artifactory plugin causes exception in project/configure page Issue Type: Bug Assignee: yossis Components: artifactory-plugin Created: 31/Jan/15 1:08 AM Description: After installing and configuring artifactory plugin, navigate to a project/configure. This stack trace is overlaied onto the configuration page javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/D:/Views/jenkins/war/WEB-INF/lib/jenkins-core-1.598.jar!/hudson/model/Job/configure.jelly:61:54: st:include hudson/maven/MavenModuleSet at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) 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:49) 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:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at
[JIRA] [email-ext-plugin] (JENKINS-24537) Email-ext: No e-mail when using other/template post-build steps
Alex Earl commented on JENKINS-24537 Email-ext: No e-mail when using other/template post-build steps Looks like it is specific to a multiconfiguration job. I created one and indeed, email-ext doesn't get called at all. Since email-ext doesn't get called, I don't think this is related to email-ext itself. It looks like template plugin's ProxyPublisher doesn't implement MatrixAggregatable, which may mean it won't work for multiconfiguration projects at all. 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] [template-project-plugin] (JENKINS-24537) No e-mail when using other/template post-build steps
Alex Earl updated JENKINS-24537 No e-mail when using other/template post-build steps This doesn't apply to email-ext. Change By: Alex Earl (31/Jan/15 1:59 AM) Summary: Email-ext: Noe-mailwhenusingother/templatepost-buildsteps Labels: email-ext multi-configurationnotificationtemplate Component/s: email-ext-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4-plugin] (JENKINS-25145) Version Jenkins Configuration In Perforce
Michael Rose commented on JENKINS-25145 Version Jenkins Configuration In Perforce I was about to create this exact feature request before stumbling upon this issue. It would be really nice to have an actually history of why configuration changes are being made. 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] [email-ext-plugin] (JENKINS-24537) Email-ext: No e-mail when using other/template post-build steps
Alex Earl commented on JENKINS-24537 Email-ext: No e-mail when using other/template post-build steps I'm unable to reproduce this. I didn't setup a multiconfig job, but I did setup a template job and it worked just fine. 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] [log-parser-plugin] (JENKINS-26572) Log Parser incompatible with Jenkins 1.597 (build record change)
AnneTheAgile commented on JENKINS-26572 Log Parser incompatible with Jenkins 1.597 (build record change) I found a reference to the code fix for another plugin 5 that needed to change with the format change; the support core. Its latest release on github has the fix. 5.[] ; X.Support Core Plugin - Jenkins - Jenkins Wiki ;; https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin Latest Release Dec 29, 2014; Jenkins v 1.554.1 Dependencies metrics (version:3.0.0) 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] [p4-plugin] (JENKINS-25602) Testing connection to an SSL server fails with 'Connection Error.'
dan tran closed JENKINS-25602 as Fixed Testing connection to an SSL server fails with Connection Error. Change By: dan tran (31/Jan/15 7:51 AM) Status: Open Closed Assignee: PaulAllen Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen
commented on JENKINS-26506
Auto cleanup and sync as well as sync only are not reliable
Are you using slave nodes or building on the jenkins master?
Do you have more than one executor or accidentally using the same workspace name for different jobs (I would suggest including ${JOB_NAME} as part of the workspace name).
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] [p4-plugin] (JENKINS-26650) Canceling an in progress build does not stop a sync.
Paul Allen commented on JENKINS-26650 Canceling an in progress build does not stop a sync. Changed to feature: Add Abort callback support from Jenkins to Perforce. 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] [p4-plugin] (JENKINS-26650) Canceling an in progress build does not stop a sync.
Paul Allen updated JENKINS-26650 Canceling an in progress build does not stop a sync. Change By: Paul Allen (30/Jan/15 1:55 PM) Issue Type: Bug NewFeature 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] [xcode-plugin] (JENKINS-24980) Keychain Management issue.
lacostej commented on JENKINS-24980 Keychain Management issue. I think I was forced to add the OTHER_CODE_SIGN_FLAGS because it appeared that if a key is in 2 keychains, but one is locked, you sometimes need to be extra specific of the one you want to use. 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] [p4-plugin] (JENKINS-26418) perforce software plugin returns Unable to update workspace when in multiconfig project
Paul Allen closed JENKINS-26418 as Cannot Reproduce perforce software plugin returns Unable to update workspace when in multiconfig project Seems ok using multiple executors on slave builds. e.g. 2 executors on an OS X slave, 2 on Linux, etc... Only way I can think this could fail is if the same workspace was being used. Change By: Paul Allen (30/Jan/15 2:02 PM) Status: Open Closed Resolution: CannotReproduce 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] [p4-plugin] (JENKINS-26373) Cannot checkout using change list
Paul Allen commented on JENKINS-26373 Cannot checkout using change list There are two ways you can do this with the new plugin: 1. pin a build to a label (under the Populate Options) 2. use a parameterized build, click on the 'Build Review' button and specify a label or change (the other fields are optional. You can also call this as a url endpoint (see Markdown file for details). 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] [p4-plugin] (JENKINS-26176) P4 plugin: Error Error occurred during the SSL handshake: invalid SSL session
Paul Allen commented on JENKINS-26176 P4 plugin: Error Error occurred during the SSL handshake: invalid SSL session Please check if your Perforce server has SSL enabled. The error suggests otherwise. Run a p4 info and look for 'Server encryption: encrypted'. If the line is not present then you can't use SSL, just untick the box and try 'Test Connection'. 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-26698) Failure to recover from exception in Publisher.needsToRunAfterFinalized
dogfood commented on JENKINS-26698 Failure to recover from exception in Publisher.needsToRunAfterFinalized Integrated in jenkins_main_trunk #3960 JENKINS-26698 Make sure BuildExecution.cleanUp always calls super, to release the workspace lease. (Revision 62af87b67a1097376b9af554421e621d32f7013f) Result = SUCCESS jesse glick : 62af87b67a1097376b9af554421e621d32f7013f Files : core/src/main/java/hudson/model/Build.java core/src/main/java/hudson/model/Run.java test/src/test/java/hudson/model/BuildExecutionTest.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] [p4-plugin] (JENKINS-26455) Removing .p4config file during force clean
Paul Allen commented on JENKINS-26455 Removing .p4config file during force clean It seems odd that it is quicker to send the whole file then calculate its MD5. What Server and plugin version are you using? 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] [p4-plugin] (JENKINS-26373) Cannot checkout using change list
Paul Allen commented on JENKINS-26373 Cannot checkout using change list The release 1.1.3 has a fix for use-case 3, where child builds will use the parent's change. 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] [mailer-plugin] (JENKINS-26606) Unable send email
Jesse Glick updated JENKINS-26606 Unable send email Change By: Jesse Glick (30/Jan/15 2:29 PM) Labels: regression 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] [mailer-plugin] (JENKINS-26606) Unable send email
Jesse Glick updated JENKINS-26606 Unable send email Change By: Jesse Glick (30/Jan/15 2:30 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26655) - error 'JSONObject[smtpServer] not found.'
Jesse Glick updated JENKINS-26655 - error JSONObject[smtpServer] not found. Change By: Jesse Glick (30/Jan/15 2:30 PM) Priority: Trivial Major Labels: jenkins Component/s: mailer-plugin Component/s: other 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] [xcode-plugin] (JENKINS-24980) Keychain Management issue.
Timothy Rundle commented on JENKINS-24980 Keychain Management issue. OK, that makes sense. I haven't tried that scenario. I still have concerns about the plugin modifying the search list. You proposed patch on pr#56 seems safer than the current implementation. Do you try to remove the keychain later or once added it stays on the search list? 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] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Jan Heimburger commented on JENKINS-26458 org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy For me the problem also occurred after upgrading from 2.4.5 to 2.5 and I also returned to 2.4.5 to fix it. Our subversion client is version 1.7 and I had set the working copy format to 1.7 in the Jenkins configuration. Obviously this setting is ignored and the working copy format is always 1.8 when checking out a fresh working copy. The error did not occur when building existing projects with SVN strategy set to update. It only occurred for new projects and after cleaning the workspace of an existing project. The error did also not occur when checking out manually into the workspace of a job and then using SVN update when building the job. 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] [p4-plugin] (JENKINS-26455) Removing .p4config file during force clean
Alexey Larsky commented on JENKINS-26455 Removing .p4config file during force clean Plugin 1.1.0, because 1.1.2 works wrong - it changes workspace root path to 'null' and clear host. p4 info Server version: P4D/LINUX26X86_64/2013.2/938876 (2014/09/23) Broker version: P4BROKER/LINUX26X86_64/2013.2/821990 Proxy version: P4P/LINUX26X86/2013.3/740675 (2013/11/11) Case Handling: insensitive 00:00:08.954 Connected to server: MyServer:1666 00:00:08.955 Connected to client: MyWorkspace 00:00:08.956 SCM Task: cleanup workspace: MyWorkspace 00:00:08.956 SCM Task: reverting all pending and shelved revisions. 00:00:08.957 ... list = revert 00:00:09.525 ... rm list | ABANDONED 00:00:09.525 ... duration: (570ms) 00:00:09.526 SCM Task: removing all non-versioned files. 00:00:09.527 ... list = reconcile -n -a 00:02:37.125 ... rm list 00:28:50.688 ... duration: 28m 41s 00:28:50.689 SCM Task: restoring all missing and changed revisions. 00:28:50.690 ... list = reconcile -n, -e, -d, -f 00:35:06.532 ... sync -f list 00:35:09.225 ... duration: 6m 18s 00:35:09.228 SCM Task: syncing files at change: 480312 00:35:09.228 ... sync k:/Projects/MyProject/...@480312 00:35:09.230 ... force update false 00:35:09.231 ... bypass have false 00:35:10.785 ... duration: 0m 1s 00:35:10.786 Calculating built changes... 00:35:13.810 Saved to file... 00:00:09.083 Connected to server: MyServer:1666 00:00:09.084 Connected to client: MyWorkspace 00:00:09.085 SCM Task: cleanup workspace: MyWorkspace 00:00:09.086 SCM Task: syncing files at change: 0 00:00:09.087 ... sync k:/Projects/MyProject/...@0 00:00:09.088 ... force update true 00:00:09.088 ... bypass have false 00:07:37.148 ... duration: 7m 28s 00:07:37.149 ... rm -rf k:/Projects/MyProject 00:07:37.152 SCM Task: syncing files at change: 480312 00:07:37.153 ... sync k:/Projects/MyProject/...@480312 00:07:37.154 ... force update true 00:07:37.154 ... bypass have false 00:16:00.027 ... duration: 8m 22s 00:16:00.028 Calculating built changes... 00:16:03.072 Saved to 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] [cli] (JENKINS-26704) SEVERE: I/O error in channel Chunked connection to http://localhost:8080/cli
Daniel Beck resolved JENKINS-26704 as Duplicate SEVERE: I/O error in channel Chunked connection to http://localhost:8080/cli Appears to duplicate JENKINS-23223. Change By: Daniel Beck (30/Jan/15 2:53 PM) Status: Open Resolved Resolution: Duplicate 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] [xcode-plugin] (JENKINS-24980) Keychain Management issue.
lacostej commented on JENKINS-24980 Keychain Management issue. Right I do nothing hence the reason for not pushing. I suspect that if we want to provide keychain management, we need to properly implement adding to search list timeout removal to search list Maybe there should be one module that deals with the keychain. And then another one that deals with xcode. The first one would find a way to tell the xcode one which keychain to use. I am unsure of the implementation given the different solutions today. This requires some changes (probably have a buildwrapper or whatever this is called in the jenkins world). I would prefer some consensus first 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] [git-plugin] (JENKINS-26680) Extraneous Forward-Slash in ssh:// path to repository
Mark Waite commented on JENKINS-26680 Extraneous Forward-Slash in ssh:// path to repository I suspect there is something in the plugin which is attempting to rewrite the URL and is adding the extra slash. I think the syntax ssh://user@hostnamne:relative_path/repo.git is ambiguous, though it seems to be understood by git. I use ssh://user@hostname:port_number/absolute_path/repo.git to allow my Jenkins job ssh access through port_number to a git repository on hostname at /absolute_path/repo.git. On my computer named "wheezy64b", I specify the URL as ssh://mwaite@wheezy64b:45022/var/lib/git/mwaite/jenkins/git-client-plugin.git I can use ssh://user@hostname:ssh/absolute_path/repo.git to allow my Jenkins job ssh access through the ssh port to a git repository on hostnanme at /absolute_path/repo.git. On my computer named "mark-pc1", I specify the URL as ssh://mwaite@mark-pc1:ssh/var/lib/git/mwaite/jenkins/git-client-plugin.git I'm impressed that the git command recognizes the relative path, since it seems like my second syntax (using the word "ssh" for the ssh port number) creates a conflicting case with your relative path case. I agree that this is a bug in the git plugin or the git client plugin, though considering the ambiguity in the ssh URL syntax, I don't think I will ever work on fixing that bug. The fix would need to identify those cases where the plugin rewrites the URL and intentionally decide not to rewrite the URL, at least for this 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26699) Workflow plugin silently breaks regular Groovy maps
Jesse Glick resolved JENKINS-26699 as Duplicate Workflow plugin silently breaks regular Groovy maps Change By: Jesse Glick (30/Jan/15 3:06 PM) Status: Open Resolved Resolution: Duplicate 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] [subversion-plugin] (JENKINS-22112) Show commiter name on build status page
Peter Marcoen assigned JENKINS-22112 to Peter Marcoen Show commiter name on build status page Change By: Peter Marcoen (30/Jan/15 9:19 AM) Assignee: PeterMarcoen 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] [subversion-plugin] (JENKINS-22112) Show commiter name on build status page
Peter Marcoen started work on JENKINS-22112 Show commiter name on build status page Change By: Peter Marcoen (30/Jan/15 9:19 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [embeddable-build-status-plugin] (JENKINS-26705) Support flat style badges
Marius Gedminas commented on JENKINS-26705 Support flat style badges Pull request at https://github.com/jenkinsci/embeddable-build-status-plugin/pull/12 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-26703) For 'project-based security' don't work disable 'grants the ability to cancel a build'
Sergey Ryabov created JENKINS-26703 For project-based security dont work disable grants the ability to cancel a build Issue Type: Bug Assignee: Unassigned Attachments: grants_cancel.JPG Components: core Created: 30/Jan/15 8:08 AM Description: I'm try set settings for 'project-based security' for disable 'grants the ability to cancel a build'. I performed initial steps in Configure Global Security page. I added 2 users, first - zzz with all grants and second - xxx with Job 'read' and 'build' grant. When i build Job as 'xxx', i can cancel a build. Project: Jenkins Priority: Minor Reporter: Sergey Ryabov 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] [embeddable-build-status-plugin] (JENKINS-19319) Distinguish between Aborted and Failed in the status icon
Marius Gedminas commented on JENKINS-19319 Distinguish between Aborted and Failed in the status icon https://github.com/jenkinsci/embeddable-build-status-plugin/pull/5/files might be useful to see where the different build states are mapped to images in the code. 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] [embeddable-build-status-plugin] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Marius Gedminas resolved JENKINS-15769 as Fixed Provide way to allow build icons without anonymous access. If I understand this issue correctly, it was fixed in version 1.4. Change By: Marius Gedminas (30/Jan/15 8:48 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
