[JIRA] (JENKINS-38622) Failed to load hudson.plugins.git.GitSCM
Title: Message Title Shoma Suzuki created an issue Jenkins / JENKINS-38622 Failed to load hudson.plugins.git.GitSCM Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Sep/30 5:56 AM Environment: # java -version openjdk version "1.8.0_66-internal" OpenJDK Runtime Environment (build 1.8.0_66-internal-b01) OpenJDK 64-Bit Server VM (build 25.66-b01, mixed mode) # uname -a Linux jenkins-x-4ktxm 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux # base on jenkinsci/docker-jnlp-slave image, running on Google Container Engine # Jenkins ver. 2.7.4 # Plugins Name ↓Version Enabled Pinned ansicolor 0.4.2 true false credentials 2.1.5 true false display-url-api 0.5 true false embeddable-build-status 1.9 true false emotional-jenkins-plugin 1.2 true false git 3.0.0 true false git-client 2.0.0 true false github 1.22.0 true false github-api 1.77 true false google-login 1.2.1 true false junit 1.18 true false mailer 1.18 true false matrix-project 1.7.1 true false plain-credentials 1.3 true false role-strategy 2.3.2 true false scm-api 1.3 true false script-security 1.23 true false slack 2.0.1 true false ssh-credentials 1.12 true false structs 1.5 true false token-macro 2.0 true false workflow-scm-step 2.2 true false workflow-step-api 2.4 true false Priority: Minor Reporter: Shoma Suzuki When opening job configure page, the fury Jenkins says "OOPS!" with the stack trace. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.7.4.jar!/lib/hudson/project/config-scm.jelly:36:91: Type org.eclipse.jgit.transport.RemoteConfig not present at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at
[JIRA] (JENKINS-37945) Mouseover on failed stage can expand beyond viewing space when in nested block
Title: Message Title Sam Van Oort commented on JENKINS-37945 Re: Mouseover on failed stage can expand beyond viewing space when in nested block PR #30 resolves the most critical part of this issue. Expect a follow-on PR to harden the CSS up a bit against box-breakage. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dominic Scheirlinck edited a comment on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit > bq. github plugin does not support secret validation on webhooks, at least last I checked.No, like I said, it does validate the secret if you provide one. It just doesn't _require_ one, nor allow other plugins to check for the presence of one. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dominic Scheirlinck commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit > github plugin does not support secret validation on webhooks, at least last I checked. No, like I said, it does validate the secret if you provide one. It just doesn't require one, nor allow other plugins to check for the presence of one. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38396) Finalize JSON format for pipeline model
Title: Message Title Michael Neale closed an issue as Fixed I consider this done. the AST is definitive. Jenkins / JENKINS-38396 Finalize JSON format for pipeline model Change By: Michael Neale Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30572) Parallel step snippet generator error
Title: Message Title Sean Flanigan commented on JENKINS-30572 Re: Parallel step snippet generator error This also affects GDSL files generated by Jenkins: // Errors on: // class org.jenkinsci.plugins.workflow.cps.steps.ParallelStep: There's no @DataBoundConstructor on any constructor of class org.jenkinsci.plugins.workflow.cps.steps.ParallelStep Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38621) Missing License
Title: Message Title Raymond Wells updated an issue Jenkins / JENKINS-38621 Missing License Change By: Raymond Wells According to https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin, plugins that do not specify a license can be assumed to fall under MIT license. Can this be specified explicitly in the pluginspec for the project a LICENSE file ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38621) Missing License
Title: Message Title Raymond Wells updated an issue Jenkins / JENKINS-38621 Missing License Change By: Raymond Wells According to https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin, plugins that do not specify a license can be assumed to fall under MIT license. Can this be specified explicitly in the POM pluginspec for the project? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38621) Missing License
Title: Message Title Raymond Wells created an issue Jenkins / JENKINS-38621 Missing License Issue Type: Bug Assignee: Javier Palacios Components: gitlab-hook-plugin Created: 2016/Sep/30 1:51 AM Priority: Minor Reporter: Raymond Wells According to https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin, plugins that do not specify a license can be assumed to fall under MIT license. Can this be specified explicitly in the POM for the project? Add Comment This message was sent by
[JIRA] (JENKINS-38620) Support common user stores for docker in builds
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-38620 Support common user stores for docker in builds Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin, pipeline Created: 2016/Sep/30 1:45 AM Labels: usability pipeline docker Priority: Major Reporter: Christian Höltje Having been working with developers using the Pipelines and docker containers, I'm seeing several user stories evolve: As a developer, I'm trying to build my code in CI using a container, so that my software builds the same everytime. As a developer, I'm trying to build my container in CI, so that my code is properly packaged and can be safely deployed. As a developer, I'm trying to run functional/integration tests in CI using containers, so I can ensure my code will work in production. As a devops engineer, I'm running arbitrary tasks in a container, so that tasks happen at appropriate times with respect to CI builds. Some of these tasks require that the default WORKSPACE and USER is used in the container. Other tasks, like building source code, may require that /etc/passwd and /etc/group are updated with the Jenkins user and group. I would propose that we break the docker pipeline interface up into two parts: A raw wrapper around docker with some simple conveniences that won't
[JIRA] (JENKINS-38620) Support common user stories for docker in builds
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-38620 Support common user stories for docker in builds Change By: Christian Höltje Summary: Support common user stores stories for docker in builds Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26920) Changing version in "Inheritance Project" causes stack overflow
Title: Message Title Raj Kiran neerukonda assigned an issue to Raj Kiran neerukonda Jenkins / JENKINS-26920 Changing version in "Inheritance Project" causes stack overflow Change By: Raj Kiran neerukonda Assignee: Raj Kiran neerukonda Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37495) Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Brandon Jacklyn edited a comment on JENKINS-37495 Re: Git Submodules having a name different to their path in working tree, failing to checkout Yeah I think my issue is actually in the git-client-plugin, but I'm not sure what version of the git-plugin this corresponds to: https://github.com/jenkinsci/git-client-plugin/blame/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L987 Edit: We are using 1.19.0 of the git-client-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37495) Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Brandon Jacklyn commented on JENKINS-37495 Re: Git Submodules having a name different to their path in working tree, failing to checkout Yeah I think my issue is actually in the git-client-plugin, but I'm not sure what version of the git-plugin this corresponds to: https://github.com/jenkinsci/git-client-plugin/blame/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L987 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37495) Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Mark Waite commented on JENKINS-37495 Re: Git Submodules having a name different to their path in working tree, failing to checkout Brandon Jacklyn based on an earlier comment I assume you must be seeing a different behavior. The earlier comment said that the problem first appeared in 3.0.0, yet you're seeing a case in an earlier plugin version. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite commented on JENKINS-38608 Re: Null value not allowed as an environment variable: GIT_URL_2 I think this likely indicates that your job has an unexpected definition of an environment variable (any environment variable) which is empty or otherwise somehow null (or possibly the empty string). Unfortunately, I can't duplicate the problem as described. Steps I took included: Create a new freestyle job Parameterize the job with a single string parameter, "GIT_URL_2", with default value field empty Configure git as the SCM for the job Add an XShell build step which runs echo $GIT_URL_2 Run the job and don't change the default parameter value Confirm the job runs to success without a stack trace or other error Confirm the value of GIT_URL_2 is not set in the output Please provide a sequence of steps which show how to duplicate the problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37495) Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Brandon Jacklyn commented on JENKINS-37495 Re: Git Submodules having a name different to their path in working tree, failing to checkout I'm having the same issue and can't upgrade to 3.0.0 (from 2.4.0). The issue is reproducible with a submodule move as shown below. The root cause is the name of the submodule in .git/config doesn't need to match the path but the git-plugin assumes that it does. This is why "git submodule update" works, but "git submodule update " does not, and the git-plugin is parsing the .git/config file for submodule names. Furthermore, my .git/config file had submodules that didn't exist in the .gitmodules file at that commit. I'm not sure if they were from other branches, or previously deleted but never cleaned up. Long story short, it doesn't seem like the .git/config file is the authoritative source of information about submodules, and neither is the .gitmodules file (people can manually edit it). I think "git ls-files --stage | grep 16" might be? Example of issue (git version 2.10.0): git init test git submodule add UI/translations/submodule git commit -m "add submodule" Content of .git/config at this point: [submodule "UI/translations/submodule"] url = "" Content of .gitmodules at this point: [submodule "UI/translations/submodule"] path = UI/translations/submodule url = "" Now we move the submodule. mkdir -p UI/translate git mv UI/translations/submodule UI/translate/submodule git commit -m "move submodule" Content of .git/config (unchanged): [submodule "UI/translations/submodule"] url = "" Content of .gitmodules (only path changed): [submodule "UI/translations/submodule"] path = UI/translate/submodule url = "" And the git-plugin then does this: git config --get-regex ^submodule >submodule.components/UI/translations/submodule.url git submodule update UI/translations/submodule error: pathspec 'UI/translations/submodule' did not match any file(s) known to git. Add
[JIRA] (JENKINS-38582) Add support for node online trigger
Title: Message Title Darryl Champagne commented on JENKINS-38582 Re: Add support for node online trigger That sounds perfect. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36795) hp automation tools - pipeline enabled
Title: Message Title Sandeep Moras commented on JENKINS-36795 Re: hp automation tools - pipeline enabled Thanks Yafim for the pointer. This helps us to start with. I was able to use this step in the pipeline to get a perf test run. stage 'Performance Testing' build 'ABC/Perf-Branch/Perf_Baseline_Test' Thank You. Will look forward for all the cool stuff you are working on on this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38618) NullPointerException when installing Android SDK
Title: Message Title Erik Fahlén created an issue Jenkins / JENKINS-38618 NullPointerException when installing Android SDK Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 2016/Sep/29 10:02 PM Environment: Mac OS 10.11.6 Jenkins 2.7.2 Android Emulator Plugin 2.15 Priority: Minor Reporter: Erik Fahlén I get a NullPointerException when trying to automatically install the Android SDK. The only other plugin I have added to Jenkins is the Node JS plugin. [android] No Android SDK found; let's install it automatically... [android] Going to install required Android SDK components... [android] Installing the 'platform-tool' SDK component(s)... $ /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android update sdk -u -a -t platform-tool /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 30: dirname: command not found /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 33: basename: command not found /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 40: dirname: command not found /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 44: dirname: command not found /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 48: basename: command not found $ /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android list sdk --extended /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 30: dirname: command not found /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 33: basename: command not found /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 40: dirname: command not found /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 44: dirname: command not found /Users/Shared/Jenkins/Home/tools/android-sdk/tools/android: line 48:
[JIRA] (JENKINS-38617) SystemExit check when running system groovy scripts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38617 Re: SystemExit check when running system groovy scripts Code changed in jenkins User: Victor Martinez Path: pom.xml src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GroovySystemExitChecker.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GroovySystemExitCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/c63106a592f71ba4810d876082a12c1960818411 Log: JENKINS-38617 System exit when running system groovy. WIP Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38617) SystemExit check when running system groovy scripts
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-38617 SystemExit check when running system groovy scripts Change By: Victor Martinez When creating Jobs its worth to define some build timeout configuration in order to avoid inaction using system groovy scripts detects whether they are using system . - https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin exit() Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38617) SystemExit check when running system groovy scripts
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-38617 SystemExit check when running system groovy scripts Change By: Victor Martinez Labels: 0.5.0 check Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38617) SystemExit check when running system groovy scripts
Title: Message Title Victor Martinez created an issue Jenkins / JENKINS-38617 SystemExit check when running system groovy scripts Issue Type: Task Assignee: Victor Martinez Components: jenkinslint-plugin Created: 2016/Sep/29 9:25 PM Labels: 0.5.0 check Priority: Minor Reporter: Victor Martinez When creating Jobs its worth to define some build timeout configuration in order to avoid inaction. https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin Add Comment
[JIRA] (JENKINS-31088) Show the project display name by default
Title: Message Title Daniel Serodio resolved as Fixed Jenkins / JENKINS-31088 Show the project display name by default Change By: Daniel Serodio Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31088) Show the project display name by default
Title: Message Title Daniel Serodio commented on JENKINS-31088 Re: Show the project display name by default There's a new PR for this, merged and released on 1.5.4. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33505) windows slave keeps disconnecting with "Trying protocol: JNLP2-connect"
Title: Message Title Blaine Bell commented on JENKINS-33505 Re: windows slave keeps disconnecting with "Trying protocol: JNLP2-connect" woops, this time changing the user name did not work, but I needed to restart the server. strange Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19834) Pipeline should use "Display Name" so it is more tidy and readable
Title: Message Title Daniel Serodio closed an issue as Duplicate Jenkins / JENKINS-19834 Pipeline should use "Display Name" so it is more tidy and readable Change By: Daniel Serodio Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33505) windows slave keeps disconnecting with "Trying protocol: JNLP2-connect"
Title: Message Title Blaine Bell commented on JENKINS-33505 Re: windows slave keeps disconnecting with "Trying protocol: JNLP2-connect" I get this same problem on windows 10 when I start the slave-agent.jnlp from another account (i.e., not jenkins), even though I run it as the user jenkins using runas /user:jenkins not sure why, but the workaround for me is to login as jenkins (this is only needed the first time, since I can create the service, and run it from there after that) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38616) Missing prebuilders actions when running jenkins lint
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38616 Missing prebuilders actions when running jenkins lint Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38616) Missing prebuilders actions when running jenkins lint
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38616 Re: Missing prebuilders actions when running jenkins lint Code changed in jenkins User: Victor Martinez Path: README.md pom.xml src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GradleWrapperChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/HardcodedScriptChecker.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GradleWrapperCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/HardcodedScriptCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/2d83215ddbf043abc3b616325a5bb9593778415b Log: [FIXED JENKINS-38616] Fixed MavenModule prebuilders when linting gradle and shell scripts Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14824) ListSubversionTagsParameterDefinition type doesn't support CLI parameter submission
Title: Message Title Anders Johnson edited a comment on JENKINS-14824 Re: ListSubversionTagsParameterDefinition type doesn't support CLI parameter submission [~aninfinite] Any status updates on this? I'd love to see this implemented. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14824) ListSubversionTagsParameterDefinition type doesn't support CLI parameter submission
Title: Message Title Anders Johnson commented on JENKINS-14824 Re: ListSubversionTagsParameterDefinition type doesn't support CLI parameter submission Victor Martinez Any status updates on this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38616) Missing prebuilders actions when running jenkins lint
Title: Message Title Victor Martinez started work on JENKINS-38616 Change By: Victor Martinez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38616) Missing prebuilders actions when running jenkins lint
Title: Message Title Victor Martinez created an issue Jenkins / JENKINS-38616 Missing prebuilders actions when running jenkins lint Issue Type: Bug Assignee: Victor Martinez Components: jenkinslint-plugin Created: 2016/Sep/29 8:53 PM Priority: Major Reporter: Victor Martinez Maven Jobs don't use builders but prebuilders therefore those lint defects are not detected accordingly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38582) Add support for node online trigger
Title: Message Title Emory Penney started work on JENKINS-38582 Change By: Emory Penney Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38582) Add support for node online trigger
Title: Message Title Emory Penney commented on JENKINS-38582 Re: Add support for node online trigger I like it, good idea. I've thrown something together for the next release. The "Advanced" settings will allow you to determine which startup scenarios you would desire: 1. Trigger when Node connects 2. Trigger when Node is brought online And you can select any combination of one or both... Although I suppose you should select at least one, otherwise the plugin won't do anything... Anyways, this sound like what you were thinking? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35184) Failed to load jenkins.util.SystemProperties on slaves due to ServletContext
Title: Message Title David Resnick updated an issue Jenkins / JENKINS-35184 Failed to load jenkins.util.SystemProperties on slaves due to ServletContext Change By: David Resnick Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Mouseover on failed stage can expand beyond viewing space when in nested block
Title: Message Title Sam Van Oort commented on JENKINS-37945 Re: Mouseover on failed stage can expand beyond viewing space when in nested block Fix looks like it resolves the basic issue. Working on testing and CSS fixes to handle longer errors. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Workflow Compatibility
Title: Message Title fahd arshad commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Workflow Compatibility Guys, any luck on this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Mouseover on failed stage can expand beyond viewing space when in nested block
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37945 Re: Mouseover on failed stage can expand beyond viewing space when in nested block Code changed in jenkins User: Sam Van Oort Path: rest-api/src/main/java/com/cloudbees/workflow/rest/external/ChunkVisitor.java http://jenkins-ci.org/commit/pipeline-stage-view-plugin/ac677da3d32e6e633e83d1b2555dc43f17a8e7c1 Log: Only store step nodes for stages - rough fix for JENKINS-37945 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Mouseover on failed stage can expand beyond viewing space when in nested block
Title: Message Title recampbell started work on JENKINS-37945 Change By: recampbell Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Mouseover on failed stage can expand beyond viewing space when in nested block
Title: Message Title Sam Van Oort commented on JENKINS-37945 Re: Mouseover on failed stage can expand beyond viewing space when in nested block Testing one of two possible fixes for the more glaring part of this right now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Mouseover on failed stage can expand beyond viewing space when in nested block
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37945 Mouseover on failed stage can expand beyond viewing space when in nested block Change By: Sam Van Oort Basically, If you have a stage with a lot of steps an error deeply nested in it blocks , and which fails, you can exceed the vertical _and_ horizontal bounds of the overlay box; screenshots should help clarify. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Mouseover on failed stage can expand beyond viewing space when in nested block
Title: Message Title Sam Van Oort commented on JENKINS-37945 Re: Mouseover on failed stage can expand beyond viewing space when in nested block Would not be an issue except that the legacy UI takes a very... questionable way of handling layout and bounding for these elements. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38615) Add user information to the restart checkbox after updating plugins
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-38615 Add user information to the restart checkbox after updating plugins Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Sep/29 7:34 PM Priority: Minor Reporter: Alex Taylor We would like to have the information of the user who hit the checkbox in the "Restart Jenkins when installation is complete and no jobs are running" that comes up after plugin updates. Any other time someone calls a restart, the user name gets recorded in the logs so it would be nice to get it for this one too. Add Comment
[JIRA] (JENKINS-37945) Mouseover on failed stage can expand beyond viewing space when in nested block
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37945 Mouseover on failed stage can expand beyond viewing space when in nested block Change By: Sam Van Oort Summary: Hover log output Mouseover on longer stages exceeds the vertical bounds of the overlay box failed stage can expand beyond viewing space when in nested block Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Hover log output on longer stages exceeds the vertical bounds of the overlay box
Title: Message Title
Sam Van Oort commented on JENKINS-37945
Re: Hover log output on longer stages exceeds the vertical bounds of the overlay box
Reproducible with something like this (include a docker.inside bit if you want the overlap too):
stage('sample') {
node {
dir('sample') {
dir('more') {
sh 'failme'
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37516) js-extensions tests failing and not run as part of prepublish
Title: Message Title Keith Zantow commented on JENKINS-37516 Re: js-extensions tests failing and not run as part of prepublish For clarification: all tests were passing here when I last committed changes to this stuff but other changes have since broken them. I'm not sure the value of having tests at all if people decide they can commit code even when tests are failing or just comment them out without understanding why. No finger pointing intended here, but when people make changes to things and tests break, they need to figure out why at the time; going back weeks later after a bunch of random stuff has been done makes it hard and time consuming to understand specifically what caused the problems. Maybe we just need these test to run as part of the main BO Maven build, since it's still included there? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33834) improve display of subproject builds
Title: Message Title Kevin Yu commented on JENKINS-33834 Re: improve display of subproject builds I think it would be extremely useful to have a link to the downstream job that is in progress. My use case is that the each axis of a upstream matrix job triggers 200 downstream jobs with different parameter such as device models. Right now, there's no way for me to go into navigate from upstream job to find out the log of specific downstream job until the build is finished. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33834) improve display of subproject builds
Title: Message Title Kevin Yu edited a comment on JENKINS-33834 Re: improve display of subproject builds I think it would be extremely useful to have a link to the downstream job that is in progress. My use case is that the each axis of a upstream matrix job triggers 200 downstream jobs with different parameter such as device models. Right now, there's no way for me to go into navigate from upstream job to find out the log of specific downstream job until the build is finished , unless I go to the downstream job and click through the 200 in progress jobs and find out based on parameter . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Hover log output on longer stages exceeds the vertical bounds of the overlay box
Title: Message Title Sam Van Oort commented on JENKINS-37945 Re: Hover log output on longer stages exceeds the vertical bounds of the overlay box This is actually far worse than it sounds at first glance, upgrading priority because it greatly reduces usability of error display and also looks terrible. This is an unintended consequence of returning more information about FlowNodes as of the v2.0 release. We need to filter down to just the StepAtomNodes for display (not start/end nodes). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Hover log output on longer stages exceeds the vertical bounds of the overlay box
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37945 Hover log output on longer stages exceeds the vertical bounds of the overlay box Change By: Sam Van Oort Labels: regression ux Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37945) Hover log output on longer stages exceeds the vertical bounds of the overlay box
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37945 Hover log output on longer stages exceeds the vertical bounds of the overlay box Change By: Sam Van Oort Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38614) Mouseover on stage logs generates gibberish with deeply nested blocks
Title: Message Title Sam Van Oort reopened an issue Jenkins / JENKINS-38614 Mouseover on stage logs generates gibberish with deeply nested blocks Change By: Sam Van Oort Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38614) Mouseover on stage logs generates gibberish with deeply nested blocks
Title: Message Title Sam Van Oort closed an issue as Fixed Actually, this really is a duplicate of JENKINS-37945 Jenkins / JENKINS-38614 Mouseover on stage logs generates gibberish with deeply nested blocks Change By: Sam Van Oort Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-38614) Mouseover on stage logs generates gibberish with deeply nested blocks
Title: Message Title Sam Van Oort resolved as Duplicate Updating status. Jenkins / JENKINS-38614 Mouseover on stage logs generates gibberish with deeply nested blocks Change By: Sam Van Oort Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35656) Inconsistent timezone display
Title: Message Title Sam Van Oort commented on JENKINS-35656 Re: Inconsistent timezone display Ben Walding To update: I'd worked on personal time to investigate this and work on a fix, and have part of the work towards a fix done. I'm pushing out what I have publicly here, so either someone else can pick up from there and do a full PR or I can return to it when I have personal time to code again - https://github.com/jenkinsci/pipeline-stage-view-plugin/pull/29 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38614) Mouseover on stage logs generates gibberish
Title: Message Title Sam Van Oort commented on JENKINS-38614 Re: Mouseover on stage logs generates gibberish This is probably because we're not doing more filtering out of BlockStart/End nodes (we should only display StepAtomNodes I think). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38614) Mouseover on stage logs generates gibberish
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-38614 Mouseover on stage logs generates gibberish Change By: Sam Van Oort Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38614) Mouseover on stage logs generates gibberish with deeply nested blocks
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-38614 Mouseover on stage logs generates gibberish with deeply nested blocks Change By: Sam Van Oort Summary: Mouseover on stage logs generates gibberish with deeply nested blocks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38614) Mouseover on stage logs generates gibberish
Title: Message Title
Sam Van Oort updated an issue
Jenkins / JENKINS-38614
Mouseover on stage logs generates gibberish
Change By:
Sam Van Oort
Looks like an unintended side effect here of showing the end steps for blocks, but run the following pipeline:{code:java}stage('sample') {node {dir('sample') {dir('more') {sh 'failme'}}}}{code}Then mouseover the stage and look at the popup, which will now extend above the top of the screen and show some serious ugliness (see screenshot). !Screen Shot 2016-09-29 at 2.43.37 PM.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38614) Mouseover on stage logs generates gibberish
Title: Message Title
Sam Van Oort created an issue
Jenkins / JENKINS-38614
Mouseover on stage logs generates gibberish
Issue Type:
Bug
Assignee:
Sam Van Oort
Attachments:
Screen Shot 2016-09-29 at 2.43.37 PM.png
Components:
pipeline-stage-view-plugin
Created:
2016/Sep/29 6:49 PM
Environment:
pipeline-stage-view-plugin 2.0
Labels:
ux regression
Priority:
Critical
Reporter:
Sam Van Oort
Looks like an unintended side effect here of showing the end steps for blocks, but run the following pipeline:
stage('sample') {
node {
dir('sample') {
dir('more') {
sh 'failme'
}
}
}
}
Then mouseover the stage and look at the popup, which will now extend above the top of the screen and show some serious ugliness (see screenshot).
[JIRA] (JENKINS-37945) Hover log output on longer stages exceeds the vertical bounds of the overlay box
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37945 Hover log output on longer stages exceeds the vertical bounds of the overlay box Change By: Sam Van Oort Labels: ux Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Adam Hajduk reopened an issue
I have the same issue. I'm running Jenkins where neither host nor slave nodes have docker tools. The Jenkins file looks like here:
parallel 'test 1': {
node {
stage('Integ Tests 1') {}
docker.withServer('tcp://my.docker.host:5001', 'integ-docker-certs') {
def cimg1 = docker.image('my-image/npf-dist-docker')
cimg1.run('-p 5000:6000')
cimg1.stop()
}
}
}
When I run the pipeline, the output is like here:
[Pipeline] [test 1] { (Integ Tests 1)
[Pipeline] [test 1] }
[Pipeline] [test 1] // stage
[Pipeline] [test 1] withDockerServer
[Pipeline] [test 1] {
[Pipeline] [test 1] sh
[test 1] [my-prod] Running shell script
[test 1] + docker run -d -p 5000:6000 my-image/npf-dist-docker
[test 1] /var/lib/jenkins/workspace/Products/Prod/npf-Docker-Test@tmp/durable-5a1339e2/script.sh: line 2: docker: command not found
[Pipeline] [test 1] }
[Pipeline] [test 1] // withDockerServer
[Pipeline] [test 1] }
[Pipeline] [test 1] // node
[Pipeline] [test 1] }
[test 1] Failed in branch test 1
So it does not seems to connect to external Docker server, it seems to try to run it locally... Am I missing some setup? Thanks, /Adam
Jenkins / JENKINS-32709
Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Change By:
Adam Hajduk
Resolution:
Incomplete
Status:
Resolved Reopened
[JIRA] (JENKINS-38500) No failure tags in test reports
Title: Message Title Daniel Pfeiffer commented on JENKINS-38500 Re: No failure tags in test reports We're seeing the same issue—except it is specifically with our UI tests where failures are being marked as successes. Xcode 8 changed the way UI tests report failure in the console. I've opened a pull request to address this: https://github.com/jenkinsci/xcode-plugin/pull/75 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36322 Re: NaN execution time may appear if a stage gets terminated incorrectly Code changed in jenkins User: Sam Van Oort Path: ui/src/main/js/view/templates/pipeline-staged.hbs http://jenkins-ci.org/commit/pipeline-stage-view-plugin/a11279d0d3bb3ad133fdde26407a95a5637265bb Log: Do not display average durations that are 0 or NaN - JENKINS-36322 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-38449 ZipExtractionInstaller not working behind proxy Change By: Martin Weber Component/s: cmakebuilder-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26133) Shell script taking/returning output/status
Title: Message Title Julien Carsique commented on JENKINS-26133 Re: Shell script taking/returning output/status Fixed in pipeline (workflow-durable-task-step-plugin) 2.4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26133) Shell script taking/returning output/status
Title: Message Title Julien Carsique updated an issue Jenkins / JENKINS-26133 Shell script taking/returning output/status Change By: Julien Carsique Component/s: workflow-durable-task-step-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38613) Pass "Google Play account"-variable as build parameter
Title: Message Title Max Walther updated an issue Jenkins / JENKINS-38613 Pass "Google Play account"-variable as build parameter Change By: Max Walther Attachment: image-2016-09-29-18-45-05-086.png Would it be possible to pass an environment variable from the credential-plugin as the "Google Play account"-parameter instead of a fixed choice within the build job. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37017) Github Org folder projects detail screen missing org name in path
Title: Message Title Thorsten Scherler started work on JENKINS-37017 Change By: Thorsten Scherler Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38580) Declarative Pipeline does not work with Milestone without Ordinal
Title: Message Title Andrew Bayer commented on JENKINS-38580 Re: Declarative Pipeline does not work with Milestone without Ordinal Frankly, I think this isn't a bug - https://github.com/jenkinsci/pipeline-milestone-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/pipeline/milestone/MilestoneStep.java#L62 - the ordinal is a required field. I'm honestly not sure how it works outside declarative without the ordinal! Jesse Glick - is there some magic in DSL that auto-inserts 0 for DataBoundConstructor int parameters that are unspecified? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38548) Freestyle Job hangs when running on a JNLP Mac OSX agent
Title: Message Title Daniel Beck updated JENKINS-38548 Jenkins / JENKINS-38548 Freestyle Job hangs when running on a JNLP Mac OSX agent Change By: Daniel Beck Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38613) Pass "Google Play account"-variable as build parameter
Title: Message Title Max Walther updated an issue Jenkins / JENKINS-38613 Pass "Google Play account"-variable as build parameter Change By: Max Walther Component/s: credentials-plugin Component/s: credentials-binding-plugin Would it be possible to pass an environment variable from the credential- binding- plugin as the "Google Play account"-parameter instead of a fixed choice within the build job. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-38580) Declarative Pipeline does not work with Milestone without Ordinal
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-38580 Declarative Pipeline does not work with Milestone without Ordinal Change By: Patrick Wolf Component/s: pipeline-milestone-step-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38613) Pass "Google Play account"-variable as build parameter
Title: Message Title Max Walther created an issue Jenkins / JENKINS-38613 Pass "Google Play account"-variable as build parameter Issue Type: Improvement Assignee: Christopher Orr Components: credentials-binding-plugin, google-play-android-publisher-plugin Created: 2016/Sep/29 4:29 PM Priority: Minor Reporter: Max Walther Would it be possible to pass an environment variable from the credential-binding-plugin as the "Google Play account"-parameter instead of a fixed choice within the build job. Add Comment
[JIRA] (JENKINS-36781) Display of SCM identifiers should be consistent
Title: Message Title Thorsten Scherler updated JENKINS-36781 Jenkins / JENKINS-36781 Display of SCM identifiers should be consistent Change By: Thorsten Scherler Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38612) With the new Timezone expression in Cron, should the help tab not reflect the timezone listed in the expression?
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-38612 With the new Timezone _expression_ in Cron, should the help tab not reflect the timezone listed in the _expression_? Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-09-29 at 11.55.24 AM.png Components: core Created: 2016/Sep/29 4:00 PM Priority: Minor Reporter: Alex Taylor When using the TZ _expression_ in Cron I was thinking that when you navigate away and it gives you the message when it would have last run(ex: Would last have run at Thursday, September 29, 2016 11:55:02 AM EDT; would next run at Thursday, September 29, 2016 11:55:02 AM EDT.), I think that it should reflect that Timezone that is listed in the _expression_ rather than the current Jenkins one right? In the screenshot I have a TZ of Los Angeles but my Jenkins is configured to be EDT I would think it should reflect PDT instead since I changed the timezone. Add Comment
[JIRA] (JENKINS-37925) Show full log only shows 10000 lines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37925 Re: Show full log only shows 1 lines Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js http://jenkins-ci.org/commit/blueocean-acceptance-test/e790fc63dea94b6c3b8e578108efebe57b9b1462 Log: JENKINS-37925 change full log link in steps to the backend log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37925) Show full log only shows 10000 lines
Title: Message Title Thorsten Scherler updated JENKINS-37925 Jenkins / JENKINS-37925 Show full log only shows 1 lines Change By: Thorsten Scherler Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38548) Freestyle Job hangs when running on a JNLP Mac OSX agent
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-38548 Freestyle Job hangs when running on a JNLP Mac OSX agent Change By: Andrew Bayer Attachment: jenkins-38548-agent-dump.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38548) Freestyle Job hangs when running on a JNLP Mac OSX agent
Title: Message Title Andrew Bayer reopened an issue Re-opening with the thread dump from a hung agent attached. Jenkins / JENKINS-38548 Freestyle Job hangs when running on a JNLP Mac OSX agent Change By: Andrew Bayer Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-36781) Display of SCM identifiers should be consistent
Title: Message Title Thorsten Scherler started work on JENKINS-36781 Change By: Thorsten Scherler Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38610) Jenkins hangs after plugin install
Title: Message Title ken cooper commented on JENKINS-38610 Re: Jenkins hangs after plugin install attatched is the results. If i go to the main url for the jenkins server, I get: Please wait while Jenkins is getting ready to work Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38611) If 'Set status for GitHub commit [universal]' in config, 'Apply' changes gets an exception
Title: Message Title
Peter Andrews created an issue
Jenkins / JENKINS-38611
If 'Set status for GitHub commit [universal]' in config, 'Apply' changes gets an exception
Issue Type:
Bug
Assignee:
Unassigned
Components:
github-api-plugin
Created:
2016/Sep/29 3:33 PM
Environment:
Jenkins 2.2.3
Labels:
git
Priority:
Minor
Reporter:
Peter Andrews
Noticed that 'Apply' of configure got an exception. By process of elimination determined that if the Post-build Action 'Set status for GitHub commit [universal]' was in project the bug occurred. Was able to create a brand new project and replicate simply by adding that post build action (no need to set any of its parameters). The stack trace: Stack trace
javax.servlet.ServletException: java.lang.Error: Failed to instantiate class org.jenkinsci.plugins.github.status.sources.BuildRefBackrefSource from {"stapler-class":"org.jenkinsci.plugins.github.status.sources.BuildRefBackrefSource","$class":"org.jenkinsci.plugins.github.status.sources.BuildRefBackrefSource"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at
[JIRA] (JENKINS-38610) Jenkins hangs after plugin install
Title: Message Title ken cooper updated an issue Jenkins / JENKINS-38610 Jenkins hangs after plugin install Change By: ken cooper Attachment: results.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38610) Jenkins hangs after plugin install
Title: Message Title Christopher Orr assigned an issue to Unassigned Jenkins / JENKINS-38610 Jenkins hangs after plugin install Change By: Christopher Orr Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock Any update on this? :/ Jenkins: 2.7.1 Build Blocker Plugin: 1.7.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38610) Jenkins hangs after plugin install
Title: Message Title Christopher Orr commented on JENKINS-38610 Re: Jenkins hangs after plugin install Moved from INFRA to JENKINS, as this is not a project infrastructure issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38610) Jenkins hangs after plugin install
Title: Message Title Christopher Orr commented on JENKINS-38610 Re: Jenkins hangs after plugin install ken cooper: Are you able to get a thread dump when this happens? https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38610) Jenkins hangs after plugin install
Title: Message Title Christopher Orr moved an issue Jenkins / JENKINS-38610 Jenkins hangs after plugin install Change By: Christopher Orr Project: Infrastructure Jenkins Key: INFRA JENKINS - 938 38610 Workflow: classic default workflow JNJira + In-Review Component/s: core Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-37974) WARNING: Caught exception evaluating: c.displayExecutors in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetException
Title: Message Title Timmy Brolin edited a comment on JENKINS-37974 Re: WARNING: Caught exception evaluating: c.displayExecutors in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetException Same here. Running Jenkins ver. 1.625.2When this happens, Jenkins becomes dead slow. Also, when this happens, I noticed that some jobs seem to become stuck in endless loops, slowly executing the same step over and over.Jenkins seems to snap out of it if I kill all active jobs and delete all workspaces. Copy of error from our log below. Seems more or less identical to yours.***WARNING hudson.ExpressionFactory2$JexlExpression evaluateCaught exception evaluating: c.displayExecutors in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor364.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-38609) Shared libraries root to be specified in the PATH field
Title: Message Title Martin Fousek updated an issue Jenkins / JENKINS-38609 Shared libraries root to be specified in the PATH field Change By: Martin Fousek Summary: Shared libraries root to be specified as folder in the PATH field Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38609) Shared libraries root to be specified as folder
Title: Message Title Martin Fousek created an issue Jenkins / JENKINS-38609 Shared libraries root to be specified as folder Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Sep/29 3:15 PM Priority: Critical Reporter: Martin Fousek Currently the Pipeline Shared Libraries plugin takes the shared libs only from ROOT of the repository like /vars, /src etc. Please could it be taking PATH which would point to the ROOT of the shared libraries for this plugin? I know that there would be workaround to create second GIT repository just for building stuff but we would like to keep the versioning of sources and the build setup on one place. Thanks in advance. Add Comment
[JIRA] (JENKINS-38381) Optimize log handling
Title: Message Title Jesse Glick commented on JENKINS-38381 Re: Optimize log handling I think I have a design that will work, but still fleshing out a prototype. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Keith Zantow started work on JENKINS-38363 Change By: Keith Zantow Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38572) Support Core Plugin gets java.lang.NoClassDefFoundError: jenkins/plugins/asynchttpclient/AHCUtils at startup
Title: Message Title Matthew Webber commented on JENKINS-38572 Re: Support Core Plugin gets java.lang.NoClassDefFoundError: jenkins/plugins/asynchttpclient/AHCUtils at startup I originally said "I have only seen the message during initial startup", but I just looked now, and see another occurrence in the log. That is consistent with the davida2009's comment. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38607) Wrong parsing of 'property content' drops backslash from string
Title: Message Title Oleg Nenashev commented on JENKINS-38607 Re: Wrong parsing of 'property content' drops backslash from string Yes, it's caused by the resolution of JENKINS-31573. But the new behavior complies with https://en.wikipedia.org/wiki/.properties#Format instead of the original one, so I do not consider it as a bug. Wiki explicitly mentions this potential compatibility issue. But I definitely should update the data in update center in order to notice users about such compatibility change Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
