[JIRA] [subversion-plugin] (JENKINS-27231) Subversion fails first revision check
sachin kung created JENKINS-27231 Subversion fails first revision check Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 04/Mar/15 8:14 AM Description: i must click twice same issue：https://issues.jenkins-ci.org/browse/JENKINS-12666 Log: hudson.util.IOException2: revision check failed on svn://xxx/xx/XX at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Authentication required for '902a3112---bd69-32ab44817266' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:62) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.createSaslClient(SVNSaslAuthenticator.java:318) at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.authenticate(SVNSaslAuthenticator.java:92) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.authenticate(SVNConnection.java:198) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.authenticate(SVNRepositoryImpl.java:1276) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1254) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:169) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184) ... 12 more Finished: FAILURE Environment: Jenkins Subversion Plug-in org.jenkins-ci.plugins:subversion:2.5 SVNKit Library org.tmatesoft.svnkit:svnkit:1.8.6 About Jenkins 1.598 OS: mac os Project: Jenkins Labels: jenkins plugin svn Priority: Major Reporter: sachin kung
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-27233) Can't use in combination with rebuild and parameterized build trigger
Nicolas De Loof created JENKINS-27233 Can't use in combination with rebuild and parameterized build trigger Issue Type: Bug Assignee: Unassigned Components: matrix-combinations-parameter-plugin Created: 04/Mar/15 8:25 AM Description: a Matrix job M is set with combinations parameter it uses parameterized build trigger to run job J as a downstream rendering job J "parameters" page fails, as [value page](https://github.com/jenkinsci/matrix-combinations-plugin/blob/master/src/main/resources/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterValue/value.groovy) expect the current project to be the MatrixProject which defined the parameter. MatrixCombinationsParameterValue contains all necessary informations (confs and values) so there's no need to rely on the MatrixProject to render. Same for [rebuild](https://github.com/jenkinsci/matrix-combinations-plugin/blob/master/src/main/resources/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterValue/rebuild.groovy) Project: Jenkins Priority: Minor Reporter: Nicolas De Loof 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] [unity3d-plugin] (JENKINS-27232) Unity 5.0.0f4 can't build
jiowchern chen created JENKINS-27232 Unity 5.0.0f4 can't build Issue Type: Improvement Assignee: lacostej Attachments: QQ截图20150304162439.png Components: unity3d-plugin Created: 04/Mar/15 8:25 AM Description: While uncertainty is an issue official or plug-ins. Use 5.0.0f4 build will stop. But 4.6.1 normal. Parameters -quit -batchmode -buildWindows64Player "$WORKSPACE\output\bin\FishHunter.exe" -projectPath "$WORKSPACE" Project: Jenkins Priority: Blocker Reporter: jiowchern chen 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-26657) File context menu missing when installing Slave under windows with jnlp
Christopher Biel commented on JENKINS-26657 File context menu missing when installing Slave under windows with jnlp Is there something new to this issue? I would like to install the new version but this does not allow 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] [maven-plugin] (JENKINS-26923) Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job
Laurent Dufour commented on JENKINS-26923 Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job Finally, it works if i remove commons-io-2.2.jar from maven lib folder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root-plugin] (JENKINS-27234) Allow access to GitHub and BitBucket hook POST payload
shorn tolley created JENKINS-27234 Allow access to GitHub and BitBucket hook POST payload Issue Type: Improvement Assignee: Jesse Glick Components: build-token-root-plugin Created: 04/Mar/15 11:02 AM Description: When using GitHub and BitBucket hooks, they both do a HTTP POST with a lot of important payload data. I couldn't figure out a way to access that data when using the build-token-root plugin. I've forked my own version that does what I want here: https://github.com/shorn/build-token-root-plugin If you're open to the idea - I'd be happy to provide a proper pull request. Project: Jenkins Priority: Minor Reporter: shorn tolley 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-25784) Select sandbox mode by default if current user lacks RUN_SCRIPTS
SCM/JIRA link daemon commented on JENKINS-25784 Select sandbox mode by default if current user lacks RUN_SCRIPTS Code changed in jenkins User: Tom Fennelly Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/config.jelly pom.xml http://jenkins-ci.org/commit/workflow-plugin/36cd9890b0a77ff6f54bb68a5b4a3303d254d23a Log: Merge pull request #67 from tfennelly/sandbox-defaulting JENKINS-25784 Defaulting of sandbox mode based on RUN_SCRIPT privs Compare: https://github.com/jenkinsci/workflow-plugin/compare/927d9a320067...36cd9890b0a7 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-25784) Select sandbox mode by default if current user lacks RUN_SCRIPTS
Tom FENNELLY resolved JENKINS-25784 as Fixed Select sandbox mode by default if current user lacks RUN_SCRIPTS Change By: Tom FENNELLY (04/Mar/15 11:13 AM) Status: In Progress 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] [subversion-plugin] (JENKINS-673) SCM "catch up" feature
Jo Shields commented on JENKINS-673 SCM "catch up" feature 7 years, and no activity beyond half-baked workarounds. So. From where I'm sat, there are two issues to resolve: A way to inject builds with given revisions, without requiring a parameterized build, OR making parameters optional so if Jenkins detects "I am missing these intermediate commits, I will add jobs to build them" it can do so without breaking workflow for non-parameterised default behaviour Maintain some knowledge of "the last master I know about". If Jenkins knows it built revision r1, then polls to discover revision r10, it needs to be able to inject builds for r2..r10 without being confused if r12 appears in the next round of polling (i.e. the record needs to be 'newest commit I know about', not 'last commit I acted upon'). This value should be user-visible in the project settings, so newly created projects don't try to catch up on 10 years of commits. Importantly, building commits in precise order is irrelevant - you care whether given commits have been tested, not when they were tested. The order becomes especially irrelevant if you use the build name plugin to use commitid for build revision names, not an incrementing numeric value as is the default. A bunch of this plumbing is already done - we can poll the SCM. Some SCM plugins clearly have knowledge of whether revisions have already been done or not (e.g. hudson/plugins/git/util/DefaultBuildChooser.java#L134). The less-implemented part is the first one - injecting the intermediate jobs into the build queue, not just the latest 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-25784) Select sandbox mode by default if current user lacks RUN_SCRIPTS
SCM/JIRA link daemon commented on JENKINS-25784 Select sandbox mode by default if current user lacks RUN_SCRIPTS Code changed in jenkins User: Tom Fennelly Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/2e48ba9981df9721e0495b4c4f79e5beed0297d5 Log: Noting JENKINS-25784 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-25958) IllegalStateException from WorkspaceActionImpl after dynamic install
Tom FENNELLY assigned JENKINS-25958 to Tom FENNELLY IllegalStateException from WorkspaceActionImpl after dynamic install Change By: Tom FENNELLY (04/Mar/15 12:02 PM) Assignee: Jesse Glick Tom FENNELLY 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-27235) Checkout strategy not attended
mturra created JENKINS-27235 Checkout strategy not attended Issue Type: Bug Assignee: Unassigned Attachments: log.txt Components: subversion-plugin Created: 04/Mar/15 12:21 PM Description: I choose "Update as much as possible with svn revert before checkout" ad checkout strategy, but jenkins delete workspace before checkout, resulting in an error deleting unversioned-file directory Checking out a fresh workspace because there's no workspace at /var/lib/myshared In the log (see attachment) you can see the stack trace: at hudson.Util.deleteRecursive(Util.java:310) at hudson.Util.deleteContentsRecursive(Util.java:212) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:80) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:170) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:133) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) Environment: Jenkins 1.597, subversion-plugin 2.5 Project: Jenkins Priority: Major Reporter: mturra 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-25958) IllegalStateException from WorkspaceActionImpl after dynamic install
Tom FENNELLY started work on JENKINS-25958 IllegalStateException from WorkspaceActionImpl after dynamic install Change By: Tom FENNELLY (04/Mar/15 12:29 PM) Status: Open In Progress 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] [google-login-plugin] (JENKINS-27117) google login plugin not working
oeuftete commented on JENKINS-27117 google login plugin not working I got mine working, but ended up changing a lot of things at once (.net added to Google Apps, might have updated the config or not, cookies clean, Google permission reset for my user), so I'm not sure what the actual fix was. 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-26096) Fixed FilePath.toComputer
Jesse Glick commented on JENKINS-26096 Fixed FilePath.toComputer Specifically: if a slave is connected and a FilePath is created on it, but then the slave is later disconnected and reconnected and someone calls toComputer on that cached path, you will get a null return value, because the old Channel is not the same as the new Channel (it is a live connection, like a java.net.Socket etc.). By comparison, FilePathPickle records the slave name permanently in channelNames even after a disconnection, so we can always figure out which slave a FilePath came from, no matter what happened to the connection subsequently. In the existing uses from Workflow, we actually do not care if the slave is disconnected now (we just want to know the node name), so FilePath.toComputer would not actually be useful at all: there is no Computer once a slave is disconnected and all its executors stop. Thus we would really want to have a more primitive method that returns a String for the node name (null if unknown for some reason, for example because the FilePath was created using some other exotic VirtualChannel); and toComputer would call that method and just look for a computer with that 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] [xcode-plugin] (JENKINS-27236) Manifest Plist URL ignores environment variables
James Newman
created JENKINS-27236
Manifest Plist URL ignores environment variables
Issue Type:
Bug
Assignee:
James Newman
Components:
xcode-plugin
Created:
04/Mar/15 1:15 PM
Description:
Manifest Plist URL ignores environment variables which means you are unable to use "${BUILD_URL}artifact" or similar when you are archiving the plist and ipa as artefacts.
Project:
Jenkins
Priority:
Minor
Reporter:
James Newman
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-27236) Manifest Plist URL ignores environment variables
James Newman started work on JENKINS-27236 Manifest Plist URL ignores environment variables Change By: James Newman (04/Mar/15 1:20 PM) Status: Open In Progress 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-27236) Manifest Plist URL ignores environment variables
James Newman commented on JENKINS-27236 Manifest Plist URL ignores environment variables Pull request created: https://github.com/jenkinsci/xcode-plugin/pull/59 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-27236) Manifest Plist URL ignores environment variables
James Newman resolved JENKINS-27236 as Fixed Manifest Plist URL ignores environment variables Resolved pending merge Change By: James Newman (04/Mar/15 1:38 PM) Status: In Progress 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] [sauce-ondemand-plugin] (JENKINS-25236) Add support for cainfo and capath in Sauce global settings
Tony Andrascik commented on JENKINS-25236 Add support for cainfo and capath in Sauce global settings Confirmed as working now. Thanks so much for the super quick fix 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] [copyartifact-plugin] (JENKINS-27237) The COPYARTIFACT_BUILD_NUMBER environment variable returns the BUILD_DISPLAY_NAME (without "#"), instead of the BUILD_NUMBER
Renato Paschoalinoto created JENKINS-27237 The COPYARTIFACT_BUILD_NUMBER environment variable returns the BUILD_DISPLAY_NAME (without "#"), instead of the BUILD_NUMBER Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 04/Mar/15 2:13 PM Description: Then Copyartifact plugin injected the environment variable COPYARTIFACT_BUILD_NUMBER<"from" project name> as BUILD_DISPLAY_NAME without the "#", instead of the BUILD_NAME. In the following example, The "from" project environment variables (called "ERGON_HADES_NG_X_GERARPACOTEXML") BUILD_DISPLAY_NAME #161 BUILD_ID 149 BUILD_NUMBER 149 The project using the copyartifact plugin COPYARTIFACT_BUILD_NUMBER_ERGON_HADES_NG_X_GERARPACOTEXML=161 Environment: Jenkins ver 1.600, Copyartifact plugin 1.35, Windows 2008 Project: Jenkins Labels: plugin copyartifact Priority: Minor Reporter: Renato Paschoalinoto This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27238) Inject parameters on manual build trigger
Marcin Z created JENKINS-27238 Inject parameters on manual build trigger Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 04/Mar/15 2:13 PM Description: In our setup we have a few stages divided by manual triggers. Now, we'd like to use these triggers to insert new parameters at the beginning of each stage, keeping others intact. Unfortunately it is impossible for us to know the values of these parameters at the beginning of the whole pipeline. Environment: Jenkins Project: Jenkins Priority: Critical Reporter: Marcin Z 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] [teamconcert-plugin] (JENKINS-26560) Too long description of BuildResutUUID that team Concert Plugin creates makes editing difficult
Heather Fraser-Dube commented on JENKINS-26560 Too long description of BuildResutUUID that team Concert Plugin creates makes editing difficult We are running Jenkins 1.596. I have builds defined with a long description for a build parameter and it wraps nicely. Seems like Jenkins has fixed their 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] [build-pipeline-plugin] (JENKINS-27239) Overriding parameters passed from upstream
Marcin Z created JENKINS-27239 Overriding parameters passed from upstream Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 04/Mar/15 2:17 PM Description: It seems that when you define a parameter in a job, its default value will override the value passed from upstream even when it is empty. This behavior only appears when using manual build triggers. Environment: Jenkins Project: Jenkins Priority: Critical Reporter: Marcin Z 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] [xunit-plugin] (JENKINS-27240) Workflow integration XUnit as a SimpleBuildStep.
Arkadiusz Skalski created JENKINS-27240 Workflow integration XUnit as a SimpleBuildStep. Issue Type: New Feature Assignee: Gregory Boissinot Components: xunit-plugin Created: 04/Mar/15 2:22 PM Description: xunit-plugin should be available as a SimpleBuildStep. Project: Jenkins Labels: workflow Priority: Minor Reporter: Arkadiusz Skalski 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-19413) StaplerRequest.getAncestor does not work for lazy block
Jesse Glick updated JENKINS-19413 StaplerRequest.getAncestor does not work for lazy block Change By: Jesse Glick (04/Mar/15 2:27 PM) Labels: jelly stapler workflow 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-27241) p4-plugin error creating workspace when not using streams
NetAppBlueDevil created JENKINS-27241 p4-plugin error creating workspace when not using streams Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 04/Mar/15 2:32 PM Description: My depot does not use streams, so I left the Streams field blank on the Manual workspace spec definition. I see the following in the jenkins log java.lang.InterruptedException: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Error detected at line 21. Unknown field name 'Stream'. at org.jenkinsci.plugins.p4.tasks.AbstractTask.setWorkspace(AbstractTask.java:63) at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:278) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1717) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins 1.600 p4-plugin 1.1.4 Project: Jenkins Priority: Blocker Reporter: NetAppBlueDevil 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] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0
Roel Harbers commented on JENKINS-21640 scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0 So, with this blocker ticket being open for more than a year, I guess we can conclude that this is not going to work anytime soon? What would be the consequences of using an ancient version of the Subversion plugin? (<2.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] [core] (JENKINS-26096) Fixed FilePath.toComputer
Daniel Beck commented on JENKINS-26096 Fixed FilePath.toComputer The "fixed" version will be unable to handle admins disconnecting nodes and shuffling names around. This should then at least be documented somewhere. 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-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
SCM/JIRA link daemon commented on JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java http://jenkins-ci.org/commit/workflow-plugin/c16a522e69791622e379f42aa049a965e3be6dc8 Log: JENKINS-25890 Refined fix to use its own thread pool, not jenkins.util.Timer. 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-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
SCM/JIRA link daemon commented on JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java http://jenkins-ci.org/commit/workflow-plugin/729984d402ebae38c2dc44ea3d72eb5f01aa6dfe Log: Merge pull request #68 from jglick/starvation-JENKINS-25890 JENKINS-25890 Use own thread pool for CpsStepContext.getProgramPromise Compare: https://github.com/jenkinsci/workflow-plugin/compare/2e48ba9981df...729984d402eb 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-26363) Input step should permit cancellation from anyone with build abort permission
SCM/JIRA link daemon resolved JENKINS-26363 as Fixed Input step should permit cancellation from anyone with build abort permission Change By: SCM/JIRA link daemon (04/Mar/15 4:02 PM) Status: In Progress 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] [workflow-plugin] (JENKINS-26363) Input step should permit cancellation from anyone with build abort permission
SCM/JIRA link daemon commented on JENKINS-26363 Input step should permit cancellation from anyone with build abort permission Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/input/InputStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputStep.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/eaa8f80a6398c76d6f62cfe43699322abd51961c Log: Merge pull request #70 from tfennelly/JENKINS-26363 [FIXED JENKINS-26363] Input step should permit cancellation from anyone with Job.CANCEL permission Compare: https://github.com/jenkinsci/workflow-plugin/compare/729984d402eb...eaa8f80a6398 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-26363) Input step should permit cancellation from anyone with build abort permission
SCM/JIRA link daemon commented on JENKINS-26363 Input step should permit cancellation from anyone with build abort permission Code changed in jenkins User: tfennelly Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/input/InputStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/85c610870b3611c81c20d46de73670f0ab39a7be Log: [FIXED JENKINS-26363 Input step should permit cancellation from anyone with Job.CANCEL permission] 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-27242) JDK Tool selections not working in Template instantiations
R. Tyler Croy moved JENKINS-27242 JDK Tool selections not working in Template instantiations Change By: R. Tyler Croy (04/Mar/15 4:07 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 252 27242 Workflow: jira JNJira Component/s: core Component/s: ci 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-25958) IllegalStateException from WorkspaceActionImpl after dynamic install
SCM/JIRA link daemon resolved JENKINS-25958 as Fixed IllegalStateException from WorkspaceActionImpl after dynamic install Change By: SCM/JIRA link daemon (04/Mar/15 4:07 PM) Status: In Progress 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] [workflow-plugin] (JENKINS-25958) IllegalStateException from WorkspaceActionImpl after dynamic install
SCM/JIRA link daemon commented on JENKINS-25958 IllegalStateException from WorkspaceActionImpl after dynamic install Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/4948e6844e234f81b19221d049083f37a952f9e7 Log: JENKINS-25958 Noting merge of #71. 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-26363) Input step should permit cancellation from anyone with build abort permission
SCM/JIRA link daemon commented on JENKINS-26363 Input step should permit cancellation from anyone with build abort permission Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/4a85acdaa89ad41f1e6f04984cc5481b959ef7f9 Log: JENKINS-26363 Noting that #70 was merged. 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-25958) IllegalStateException from WorkspaceActionImpl after dynamic install
SCM/JIRA link daemon commented on JENKINS-25958 IllegalStateException from WorkspaceActionImpl after dynamic install Code changed in jenkins User: Jesse Glick Path: support/src/main/java/org/jenkinsci/plugins/workflow/support/actions/WorkspaceActionImpl.java support/src/main/java/org/jenkinsci/plugins/workflow/support/pickles/FilePathPickle.java support/src/main/java/org/jenkinsci/plugins/workflow/support/pickles/WorkspaceListLeasePickle.java http://jenkins-ci.org/commit/workflow-plugin/f393662a3aa31f6ca4cb8abfdb6fa656a69e310a Log: Merge pull request #71 from tfennelly/JENKINS-25958 [FIXED JENKINS-25958] Check for already known Computers/Channels in FilePathPickle.Listener Compare: https://github.com/jenkinsci/workflow-plugin/compare/4a85acdaa89a...f393662a3aa3 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-27242) JDK Tool selections not working in Template instantiations
R. Tyler Croy commented on JENKINS-27242 JDK Tool selections not working in Template instantiations I've moved this to the JENKINS project, the INFRA project in JIRA is for the project's infrastructure needs 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] [dynamic-axis-plugin] (JENKINS-25660) Dynamic axis does not handle quotes in input variables
Oleg Nenashev resolved JENKINS-25660 as Fixed Dynamic axis does not handle quotes in input variables The issue has been fixed in 1.0.3 Change By: Oleg Nenashev (04/Mar/15 4:16 PM) 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.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0
Arun Thomas commented on JENKINS-21640 scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0 SCM Sync plugin is working for me. Jenkins: 1.599 Sub-version plugin: 2.5 SCM Sync Configuration plugin: 0.0.8 Environment: Windows Server 2008 Could this have been resolved? Has anyone else tried the latest plugins? 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] [dynamic-axis-plugin] (JENKINS-27243) Default value appears in axes when there's an input variable
Oleg Nenashev created JENKINS-27243 Default value appears in axes when there's an input variable Issue Type: Bug Assignee: Unassigned Components: dynamic-axis-plugin Created: 04/Mar/15 4:22 PM Description: The plugin continuously adds the 'default' axis value even if there's an existing variable in the environment.Dynamic axis source: String parameter. The issue appears on the particular job only and cannot be reproduced on others. Job reloading does not resolve the issue. Cause (just a theory, cannot be reproduced on the test server): Race condition in the plugin DynamicAxis::getValues() returns an original data container without a copiyng => risk of the data corruption somewhere System log on 1 config (reverse order): Mar 04, 2015 11:01:38 AM ca.silvermaplesolutions.jenkins.plugins.daxis.DynamicAxis FINE: Returning axis list [default, 1] Mar 04, 2015 11:01:38 AM ca.silvermaplesolutions.jenkins.plugins.daxis.DynamicAxis FINE: Variable value is '1' Mar 04, 2015 11:01:38 AM ca.silvermaplesolutions.jenkins.plugins.daxis.DynamicAxis FINE: Rebuilding axis names from variable 'NUMBER_FILES' Environment: dynamic-axis-1.0.3 jenkins-1.509.4 Project: Jenkins Labels: configuration Priority: Minor Reporter: Oleg Nenashev 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-26093) Code snippet generation for BuildTriggerStep.parameters
SCM/JIRA link daemon commented on JENKINS-26093 Code snippet generation for BuildTriggerStep.parameters Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java step-api/src/main/java/org/jenkinsci/plugins/workflow/structs/DescribableHelper.java step-api/src/test/java/org/jenkinsci/plugins/workflow/structs/DescribableHelperTest.java support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/config.jelly http://jenkins-ci.org/commit/workflow-plugin/72860e91d39712e1beecdab61d42427a4402f294 Log: JENKINS-26093 Allow parameter values to be specified using standard $class syntax. 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-26093) Code snippet generation for BuildTriggerStep.parameters
Jesse Glick resolved JENKINS-26093 as Fixed Code snippet generation for BuildTriggerStep.parameters Change By: Jesse Glick (04/Mar/15 4:41 PM) Status: In Progress 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] [workflow-plugin] (JENKINS-26093) Code snippet generation for BuildTriggerStep.parameters
SCM/JIRA link daemon commented on JENKINS-26093 Code snippet generation for BuildTriggerStep.parameters Code changed in jenkins User: Jesse Glick Path: CHANGES.md cps/src/main/java/org/jenkinsci/plugins/workflow/cps/Snippetizer.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep.java support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/DescriptorImpl/parameters.groovy support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/config.jelly http://jenkins-ci.org/commit/workflow-plugin/276eee3b7d552e031b73d440a2faf29d25dbc680 Log: JENKINS-26093 Look up the downstream parameter definitions and show their index pages. 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-26093) Code snippet generation for BuildTriggerStep.parameters
SCM/JIRA link daemon commented on JENKINS-26093 Code snippet generation for BuildTriggerStep.parameters Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/Snippetizer.java cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java step-api/src/main/java/org/jenkinsci/plugins/workflow/structs/DescribableHelper.java step-api/src/test/java/org/jenkinsci/plugins/workflow/structs/DescribableHelperTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/StaplerReferer.java support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/DescriptorImpl/parameters.groovy support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/config.jelly http://jenkins-ci.org/commit/workflow-plugin/59d5d337e70fc15a69cdc308ee052d79ab7ffbd1 Log: [FIXED JENKINS-26093] Merging #69. Conflicts: CHANGES.md Compare: https://github.com/jenkinsci/workflow-plugin/compare/4948e6844e23...59d5d337e70f 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] [copyartifact-plugin] (JENKINS-27237) The COPYARTIFACT_BUILD_NUMBER environment variable returns the BUILD_DISPLAY_NAME (without "#"), instead of the BUILD_NUMBER
Renato Paschoalinoto commented on JENKINS-27237 The COPYARTIFACT_BUILD_NUMBER environment variable returns the BUILD_DISPLAY_NAME (without "#"), instead of the BUILD_NUMBER The problem was Jenkins core, not the copyartifact plugin. I upgraded to version 1.601, and the problem was solved. Example: BUILD_DISPLAY_NAME #162 BUILD_ID 162 BUILD_NUMBER 162 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] [unity3d-plugin] (JENKINS-27232) Unity 5.0.0f4 can't build
lacostej commented on JENKINS-27232 Unity 5.0.0f4 can't build This is suprosing because I've been using many beta builds without problem (on Mac only though). It might be a editor.log problem or a buildWindows64Player argument issue. Could you try adding the editor log to a file under the worspace ? 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] [unity3d-plugin] (JENKINS-27232) Unity 5.0.0f4 can't build
lacostej edited a comment on JENKINS-27232 Unity 5.0.0f4 can't build This is suprosing because I've been using many beta builds without problem (on Mac only though). It might be a editor.log problem or a buildWindows64Player argument issue. Could you try adding the editor log argument to log to a file under the job worspace ? 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] [copyartifact-plugin] (JENKINS-27237) The COPYARTIFACT_BUILD_NUMBER environment variable returns the BUILD_DISPLAY_NAME (without "#"), instead of the BUILD_NUMBER
Renato Paschoalinoto closed JENKINS-27237 as Fixed The COPYARTIFACT_BUILD_NUMBER environment variable returns the BUILD_DISPLAY_NAME (without "#"), instead of the BUILD_NUMBER The problem was fixed in Jenkins core version 1.601. The copyartifact plugin is correct. Change By: Renato Paschoalinoto (04/Mar/15 4:51 PM) Status: Open Closed 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] [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 Don't Reconnect Until Reboot Still happens, daily. Jenkins 1.596.1 with all plugins up to date. 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 Don't Reconnect Until Reboot I will grab a thread dump the next time i see this. 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-27148) Jenkins Project Level Dashboard has rendering issue
Trisha Hanlon commented on JENKINS-27148 Jenkins Project Level Dashboard has rendering issue I seem to be having the same issue, but using Firefox on Mac. It doesn't occur on all of my projects, only random ones. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27148) Jenkins Project Level Dashboard has rendering issue
Taylor Franklin commented on JENKINS-27148 Jenkins Project Level Dashboard has rendering issue I also have the same issue, using Google Chrome on Mac. 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] [performance-plugin] (JENKINS-27244) Performance plugin archives dashBoard_*.xml
Charles Chan created JENKINS-27244 Performance plugin archives dashBoard_*.xml Issue Type: Bug Assignee: Manuel Carrasco Attachments: performance-plugin1.jpg, performance-plugin2.jpg Components: performance-plugin Created: 04/Mar/15 5:29 PM Description: After enabling the performance plugin and setting up 'Publish Performance test result report', the 'Last Successful Artifacts' will include 'dashBoard_*.xml' I am not sure how they are related, but somehow it seems to show up only when 'Publish Performance test result report' is enabled. Perhaps a side effect? -- Contents of the dashBoard_*.xml: "1.0"?> 0 0 0.0 32 13 77 Environment: Jenkins v1.565.3 performance-plugin v1.13 Project: Jenkins Priority: Major Reporter: Charles Chan 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] [performance-plugin] (JENKINS-27245) Performance graph does not appear if the slave node is offline
Charles Chan created JENKINS-27245 Performance graph does not appear if the slave node is offline Issue Type: Improvement Assignee: Manuel Carrasco Components: performance-plugin Created: 04/Mar/15 5:38 PM Description: We have a nightly Jenkins job that uses a slave to run JMeter and publish the results using the performance plugin. The slave that we use is a VM and is reset every night. In the Jenkins configuration for the node: Availability: 'Take this slave on-line when in demand and off-line when idle' In demand delay: 1 (minute) Idle delay: 60 (minutes) It is observed that when the job is completed the graph is shown (as expected). However, after the idle delay is elapsed, the slave is disconnected and goes offline and the performance graph disappears. Only by bring the node online again will the graph be available. I am not sure if this is a unique problem that affect all plugins. Could something be done to 'cache' the information on the server, similar to how the artifact, trends, etc are available even if the slave is offline? Environment: Jenkins v1.565.3 performance-plugin v1.13 Project: Jenkins Priority: Major Reporter: Charles Chan 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] [unity3d-plugin] (JENKINS-27232) Unity 5.0.0f4 can't build
lacostej edited a comment on JENKINS-27232 Unity 5.0.0f4 can't build This is suprising because I've been using many beta builds without problem (on Mac only though). It might be a editor.log problem or a buildWindows64Player argument issue. Could you try adding the editor log argument to log to a file under the job worspace ? 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] [google-login-plugin] (JENKINS-26279) google login plugin just shows a alert message on top asking username password
Thien Nguyen commented on JENKINS-26279 google login plugin just shows a alert message on top asking username password curl worked fine so I played around a bit. Had to not just clear caches in Chrome but also restart 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] [credentials-plugin] (JENKINS-27246) adding ssh credentials for jenkins to use generates an "Oops" page.
allan bailey created JENKINS-27246 adding ssh credentials for jenkins to use generates an "Oops" page. Issue Type: Bug Assignee: stephenconnolly Attachments: oops.txt Components: credentials-plugin Created: 04/Mar/15 6:18 PM Description: I try to add a global credential for Jenkins and get an 'Oops' page. specifically: Jenkins -> Credentials -> Global credentials (unrestricted) Add credentials in the form I choose "SSH Username with private key" Then select that new 'jenkins' credential. Then 'Update'. Then select "From the Jenkins master ~/.ssh". It is a passwordless id_rsa private key file. Boom. See attached oops.txt file. Environment: ec2 ubuntu 14.04 x86_64 plugins: git, ssh, ec2, cobertura, credentials, dashboard-view, s3 Project: Jenkins Labels: exception jenkins plugin Priority: Blocker Reporter: allan bailey 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] [jira-plugin] (JENKINS-27247) Issue is updated with reports that contains other unrelated issues
Travis Ly created JENKINS-27247 Issue is updated with reports that contains other unrelated issues Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 04/Mar/15 6:47 PM Description: It reports in the right task, but it would tag a whole bunch of unrelated tasks too though. Jira Issue Updater Plugin Environment: jenkins v1.578 - Windows Server Jira Issue Updater Plugin v1.9 Project: Jenkins Labels: plugin Priority: Minor Reporter: Travis Ly 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-27180) Upgrade to version 1.600 broke GIT plugin
Chris Pattersonc edited a comment on JENKINS-27180 Upgrade to version 1.600 broke GIT plugin Two workarounds that I have found 1. Copy project (start with clean build history) 2. Delete all build history from job directory (builds, lastStable, etc.) In comparing the resultant build.xml from an older build (pre 1.5) and new build (1.600), the sha has doesn't appear to be in the old build (or is in a different place in the xml doc). 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] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Joe Hansche commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I tend to agree with Christopher Orr. Out of the last ~7 builds that were attempted, these were the results: -ports 5743,5744 – Worked -ports 5849,5850 – Failed to start -ports 5705,5706 – Failed to start -ports 5886,5887 – Worked -ports 5719,5720 – Worked -ports 5619,5620 – Failed to start -ports 5866,5867 – Worked -ports 5822,5823 – Worked So this means it does not seem to be affected by the even/odd pairs. 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-27248) List Subversion Tags parameter not available in workflow
Christoph Vogtländer created JENKINS-27248 List Subversion Tags parameter not available in workflow Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 04/Mar/15 7:14 PM Description: Using the "List Subversion tags (and more)" parameter type will not expose the parameter as a Groovy variable in a workflow. The "Parameters" page shows two parameters "Repository URL" and "Tag" after a run. But the parameter name I used was SVNTAG. Building inside a free style project seems to works: SVNTAG is defined in the environment. But the parameters page also shows "Repository URL" and "Tag", not the configured name. Other parameter types (e.g. Extended Choice Parameter) will be shown correctly on the Parameters page and work together with the workflow plug in. Environment: Jenkins ver. 1.580.3 LTS Worklow plug in 1.2 Project: Jenkins Priority: Major 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] [chromedriver-plugin] (JENKINS-26524) Null Pointer Exception on github payload push AND polling to/from Jenkins
Greg Domjan commented on JENKINS-26524 Null Pointer Exception on github payload push AND polling to/from Jenkins Jenkins ver. 1.601 Windows Master, 2 Windows slave nodes. For each job using SVN - Mar 05, 2015 12:46:00 AM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.maven.MavenModuleSet@19597933[SomeModule] java.lang.NullPointerException at org.jenkinsci.plugins.chromedriver.EnvironmentContributorImpl.buildEnvironmentFor(EnvironmentContributorImpl.java:23) at hudson.model.Run.getEnvironment(Run.java:2248) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:917) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:167) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1343) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) As noted by @Mark Waite #comment-220103 seems to be chrome driver For my install chromedriver This plugin auto-installs chromedriver to all the slaves. 1.1 disabling chrome driver the issue stops happening. 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] [credentials-plugin] (JENKINS-27246) adding ssh credentials for jenkins to use generates an "Oops" page.
allan bailey commented on JENKINS-27246 adding ssh credentials for jenkins to use generates an "Oops" page. Just an update: it's not a browser issue as far as i can tell. Tested with chrome, firefox, and opera on a mac. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27239) Overriding parameters passed from upstream
Daniel Beck commented on JENKINS-27239 Overriding parameters passed from upstream Are you using the env-inject 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] [core] (JENKINS-27242) JDK Tool selections not working in Template instantiations
Daniel Beck updated JENKINS-27242 JDK Tool selections not working in Template instantiations Are paths/installers defined for the JDK? Does this issue occur with 1.601 (out of cycle bugfix release) as well? If so, please provide a minimal job config that demonstrates the problem. Change By: Daniel Beck (04/Mar/15 8:09 PM) Assignee: R. Tyler Croy 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-27242) JDK Tool selections not working in Template instantiations
Gregg Lowrimore commented on JENKINS-27242 JDK Tool selections not working in Template instantiations Yes, I have three JDKs defined in Configure System: JDK 1.7..., JDK 1.8.31_x64 and a JDK 1.8.31_x86 and my job is using a choice parameter that pulls all three of these JDKs into a choice widget for the user to choose to build with. And yet the job's output is 1) displaying that old bug of "No JDK ' ' found" and 2) ALWAYS defaults to the JAVA_HOME value that was set in the jenkins' user environment before Jenkins tool startup. I have not tried the 1.601 release yet. How/where do I get it? Will yum update find this point release? I'll try that while I wait to hear back from you 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] [credentials-plugin] (JENKINS-27246) adding ssh credentials for jenkins to use generates an "Oops" page.
allan bailey updated JENKINS-27246 adding ssh credentials for jenkins to use generates an "Oops" page. Change By: allan bailey (04/Mar/15 8:38 PM) Description: I try to add a global credential for Jenkins and get an 'Oops' page.specifically:Jenkins -> Credentials -> Global credentials (unrestricted)Add credentials in the form I choose "SSH Username with private key" Then select that new 'jenkins' credential.Then 'Update'.Then select "From the Jenkins master ~/.ssh". It is a passwordless id_rsa private key file. In the form I choose "SSH Username with private key" Boom. See attached oops.txt 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] [credentials-plugin] (JENKINS-27246) adding ssh credentials for jenkins to use generates an "Oops" page.
allan bailey updated JENKINS-27246 adding ssh credentials for jenkins to use generates an "Oops" page. Change By: allan bailey (04/Mar/15 8:40 PM) Description: I try to add a global credential for Jenkins and get an 'Oops' page.specifically:Jenkins -> Credentials -> Global credentials (unrestricted) Next: Add credentials In that form I choose "SSH Username with private key". Then select the 'OK' button.Next:Then select that new 'jenkins' credential.Then 'Update'.Then select "From the Jenkins master ~/.ssh". It is a passwordless id_rsa private key file.In the form I choose "SSH Username with private key"Boom. See attached oops.txt 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] [workflow-plugin] (JENKINS-26619) DescribableHelper does not handle GitSCMExtension
Jesse Glick assigned JENKINS-26619 to Jesse Glick DescribableHelper does not handle GitSCMExtension Change By: Jesse Glick (04/Mar/15 9:03 PM) Assignee: Nicolas De Loof Jesse Glick 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] [credentials-plugin] (JENKINS-27246) adding ssh credentials for jenkins to use generates an "Oops" page.
allan bailey commented on JENKINS-27246 adding ssh credentials for jenkins to use generates an "Oops" page. This seems to have been a misconfiguration of the nginx pass through proxy on my end. Closing this ticket. 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] [credentials-plugin] (JENKINS-27246) adding ssh credentials for jenkins to use generates an "Oops" page.
allan bailey closed JENKINS-27246 as Fixed adding ssh credentials for jenkins to use generates an "Oops" page. This was an nginx pass through proxy issue on my end. still having git/ssh issues, but that's separate. Change By: allan bailey (04/Mar/15 9:10 PM) Status: Open Closed 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] [remoting] (JENKINS-27249) Quite Period is not considered when triggering remotely
Stefan Cordes created JENKINS-27249 Quite Period is not considered when triggering remotely Issue Type: Bug Assignee: Unassigned Components: remoting Created: 04/Mar/15 9:53 PM Description: 2 Jenkins Servers: build and integrate integrate has a deploy job with a "Quiet period" of 1800 (seconds) build triggers via "Parameterized Remote Trigger Plugin" Verison 2.1.3 with "Trigger a remote parameterized job" that job. The deploy job starts immediately. Expected is that the deploy job on integrate is queued and waits for 30 minutes. Seems to be that "Trigger builds remotely (e.g., from scripts)" with "Authentication Token" akts like pressing on the "Build" link. Should be like other build triggers. Environment: Windows 2000 Server Jenkins 1.580.3 Project: Jenkins Labels: jenkins Priority: Minor Reporter: Stefan Cordes 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] [parameterized-remote-trigger-plugin] (JENKINS-27249) Quite Period is not considered when triggering remotely
Daniel Beck updated JENKINS-27249 Quite Period is not considered when triggering remotely Change By: Daniel Beck (04/Mar/15 10:09 PM) Assignee: Maurice W. Component/s: parameterized-remote-trigger-plugin Component/s: remoting 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-26748) Git plugin sometimes reports Could not checkout null with start point
vietsoft commented on JENKINS-26748 Git plugin sometimes reports Could not checkout null with start point Got same error on similar situations 10:57:11 Checking out Revision 4ffcf74053105974cf8a8663b78429ca08b42b59 (refs/remotes/origin/pr/1925/merge) 10:57:11 > git config core.sparsecheckout # timeout=10 10:57:11 > git checkout -f 4ffcf74053105974cf8a8663b78429ca08b42b59 10:57:11 FATAL: Could not checkout null with start point 4ffcf74053105974cf8a8663b78429ca08b42b59 10:57:11 hudson.plugins.git.GitException: Could not checkout null with start point 4ffcf74053105974cf8a8663b78429ca08b42b59 10:57:11 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1855) env: Cloudbees GIT client plugin v1.16.1 GIT plugin v2.3.5 Github plugin v1.10 Github pull request builder v1.16-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] [p4-plugin] (JENKINS-27250) p4 plugin does not respect line endings setting
Andrew Kruse created JENKINS-27250 p4 plugin does not respect line endings setting Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 04/Mar/15 11:12 PM Description: When setting up plugin options for a "manual (custom view) workspace, when retrieving an *.RSRC file, it writes the file to disk as unix line endings regardless of what it set in the "Line Endings" dropdown (I have tried both "local" and "win"). Have also tried setting this via p4 client on the command line before launching the build job in jenkins and jenkins overrides it. Environment: p4 plugin version v 1.1.4, jenkins version 1.599, Windows Server 2008 R2 slaves, Perforce server version 2014.1/886167 Project: Jenkins Priority: Critical Reporter: Andrew Kruse 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-27250) p4 plugin does not respect line endings setting
Andrew Kruse updated JENKINS-27250 p4 plugin does not respect line endings setting Change By: Andrew Kruse (04/Mar/15 11:16 PM) Description: When setting up plugin options for a "manual (custom view) " workspace, when retrieving an *.RSRC file, it writes the file to disk as unix line endings regardless of what it set in the "Line Endings" dropdown (I have tried both "local" and "win"). Have also tried setting this via p4 client on the command line before launching the build job in jenkins and jenkins overrides 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] [claim-plugin] (JENKINS-26364) Expose claimed failing tests via the REST API
mstave commented on JENKINS-26364 Expose claimed failing tests via the REST API The info on builds claimed may be, but not the info on tests claimed. This would be particularly helpful info to have in Jenkins-generated emails. 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-27115) GIt polling queries wrong head
Tully Foote commented on JENKINS-27115 GIt polling queries wrong head I submitted a pull-request here: https://github.com/jenkinsci/git-plugin/pull/305 For help text mentioning that foo/bar => bar I've found that the trimming does not happen if you use the full refs/heads/ I think my previous tests used refs/head/ by accident. The PR takes care of the primary issue here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27238) Inject parameters on manual build trigger
Idan Bidani commented on JENKINS-27238 Inject parameters on manual build trigger Sounds more like a feature/improvement request and not a critical priority. please adjust 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-27115) GIt polling queries wrong head
SCM/JIRA link daemon commented on JENKINS-27115 GIt polling queries wrong head Code changed in jenkins User: Tully Foote Path: src/main/resources/hudson/plugins/git/BranchSpec/help-name.html http://jenkins-ci.org/commit/git-plugin/a9e34a703da8af95c298c100e640e63335d5a868 Log: Add comment about trimming before slashes This is a follow up to https://issues.jenkins-ci.org/browse/JENKINS-27115 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-26138) Better support for workspaces
Anders Hammar commented on JENKINS-26138 Better support for workspaces If the flow graph UI isn't available in the OSS version there needs to be some other way to manage the workspace, e.g. delete 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] [google-login-plugin] (JENKINS-27117) google login plugin not working
sudhakar bellamkonda commented on JENKINS-27117 google login plugin not working I got it working by upgrading jenkins to 1.6 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] [support-core-plugin] (JENKINS-26731) Prefer Yaml over MarkDown or even Json
Nicolas De Loof updated JENKINS-26731 Prefer Yaml over MarkDown or even Json Change By: Nicolas De Loof (05/Mar/15 7:33 AM) Summary: Replace "about.md" by a (parsable) markup format Prefer Yaml over MarkDown or even Json Description: To automate support bundle analysis, we need to parse the about bundle files . md file. For sure we can parse json and markdown, but would be _so_ easier if this one uses yaml or json . json is also verbose and not so pleasant to read 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-25508) Git plugin doesn't parse changelog (false "First time build")
Or Shachar updated JENKINS-25508 Git plugin doesn't parse changelog (false "First time build") Change By: Or Shachar (05/Mar/15 7:37 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25508) Git plugin doesn't parse changelog (false "First time build")
Or Shachar updated JENKINS-25508 Git plugin doesn't parse changelog (false "First time build") Change By: Or Shachar (05/Mar/15 7:37 AM) Environment: Jenkins 1.565.2 , 1.580.3 Git-Client 1.11.0 , 1.14.1 Git plugin 2.2.7 , 2.3.4 SCM-API 0.2 SSH credentials 1.10 Credentials 1.18 Both master and slave works on RHEL 6.3 with Java 7u51 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-27251) windows slaves disconnect during build
morlajb created JENKINS-27251 windows slaves disconnect during build Issue Type: Bug Assignee: Unassigned Components: core Created: 05/Mar/15 7:39 AM Description: Matrix job execute MVN ( 3.0.5) step and the connection aborted 08:20:57 FATAL: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@2760a63e[name=studio-7-1] 08:20:57 hudson.remoting.RequestAbortedException: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@2760a63e[name=studio- I tried switch the MVN step with an ANT , it reduced dramatically the problem , but the problem still exist. Environment: Maser windows 2012R2 LTS version 15.580.1 windows slaves win7 , win81 win 2012 , win2012R2 Project: Jenkins Priority: Critical Reporter: morlajb 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-27251) windows slaves disconnect during build
morlajb updated JENKINS-27251 windows slaves disconnect during build Change By: morlajb (05/Mar/15 7:42 AM) Environment: Maser windows 2012R2 LTS version 15 1 .580.1 windows slaves win7 , win81 win 2012 , win2012R2 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] [unity3d-plugin] (JENKINS-27232) Unity 5.0.0f4 can't build
jiowchern chen updated JENKINS-27232 Unity 5.0.0f4 can't build Added -nolog Change By: jiowchern chen (05/Mar/15 7:43 AM) Attachment: consoleText.txt 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] [unity3d-plugin] (JENKINS-27232) Unity 5.0.0f4 can't build
jiowchern chen edited a comment on JENKINS-27232 Unity 5.0.0f4 can't build After adding -nolog can show the message. But in the end there is some problem. consoleText.txt can not proceed. 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.
