[JIRA] [active-choices-plugin] (JENKINS-33473) Groovy script with default values when job is started by timer
Title: Message Title Mattias Andersson created an issue Jenkins / JENKINS-33473 Groovy script with default values when job is started by timer Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 11/Mar/16 7:57 AM Environment: Active Choices Plug-in version 1.4 Jenkins ver. 1.652 Priority: Minor Reporter: Mattias Andersson I have an Active choice parameter (Multi select) with the following Groovy script ['ONE:selected','TWO:selected','TREE:selected','FOUR:selected'] And the following fallback ['FALLBACK'] If I start the job with a timer the parameter gets the value ONE:selected, I was expecting ONE,TWO,TREE,FOUR This is related to JENKINS-3240
[JIRA] [checkstyle-plugin] (JENKINS-33472) Checkstyle Trend does not show up for Workflow scripts (Pipeline plugin)
Title: Message Title
Punit Agrawal updated an issue
Jenkins / JENKINS-33472
Checkstyle Trend does not show up for Workflow scripts (Pipeline plugin)
Change By:
Punit Agrawal
I am using the Pipeline plugin to setup a workflow using a script. To publish the checkstyle report, I use this line:{code:java}step([$class: 'CheckStylePublisher', pattern: '**/scalastyle-result.xml', unstableTotalAll: '0', usePreviousBuildAsReference: true]){code}The checkstyle warnings show up in the build but the "Checkstyle Trend" on the main build page is missing. (See attached). Also the checkstyle warnings link does not show up on the main build page. Let me know if more info is needed
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle-plugin] (JENKINS-33472) Checkstyle Trend does not show up for Workflow scripts (Pipeline plugin)
Title: Message Title Punit Agrawal created an issue Jenkins / JENKINS-33472 Checkstyle Trend does not show up for Workflow scripts (Pipeline plugin) Issue Type: Bug Assignee: Ulli Hafner Attachments: Screen Shot 2016-03-10 at 11.43.38 PM.png Components: checkstyle-plugin Created: 11/Mar/16 7:45 AM Environment: Ubuntu 14.04, Jenkins 1.647, Checkstyle 3.45, Pipeline plugin 1.14 Priority: Critical Reporter: Punit Agrawal I am using the Pipeline plugin to setup a workflow using a script. To publish the checkstyle report, I use this line: step([$class: 'CheckStylePublisher', pattern: '**/scalastyle-result.xml', unstableTotalAll: '0', usePreviousBuildAsReference: true]) The checkstyle warnings show up in the build but the "Checkstyle Trend" on the main build page is missing.
[JIRA] [tfs-plugin] (JENKINS-26375) Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later
Title: Message Title Eric Lordahl commented on JENKINS-26375 Re: Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later https://github.com/jenkinsci/tfs-plugin/pull/73 submitted. As i specified in the PR, i'm not entirely sure of the big picture, but it satisfies my local, AD, and LDAP use cases. Hopefully it'll get merged soon. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fxcop-runner-plugin] (JENKINS-18151) FxCop-Runner sets build results to unstable when FxCop runs succesfully
Title: Message Title apgray commented on JENKINS-18151 Re: FxCop-Runner sets build results to unstable when FxCop runs succesfully Is this going to be fixed? I am still getting this problem occur and it is 2016. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33411) Converting Tom's tabs to scroll-spy tabs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33411 Re: Converting Tom's tabs to scroll-spy tabs Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/resources/hudson/model/Job/configure.jelly core/src/main/resources/lib/form/select/select.js core/src/main/resources/lib/layout/layout.jelly war/src/main/js/api/securityConfig.js war/src/main/js/config-tabbar.js war/src/main/js/pluginSetupWizardGui.js war/src/main/js/widgets/config/model/ConfigSection.js war/src/main/js/widgets/config/model/ConfigTableMetaData.js war/src/main/js/widgets/config/tabbar.js war/src/main/js/widgets/config/tabbar.less war/src/main/js/widgets/form/form-mixins.less war/src/main/js/widgets/layout-mixins.less war/src/main/js/widgets/variables.less war/src/main/webapp/css/style.css war/src/test/js/widgets/config/tabbar-spec.js http://jenkins-ci.org/commit/jenkins/9fb542369206c8abb886360cb2bb23d06db86493 Log: Merge pull request #2106 from gusreiber/2.0_j-33411 [FIX JENKINS-33411] Use scrolling tabs Compare: https://github.com/jenkinsci/jenkins/compare/36528a681a54...9fb542369206 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33411) Converting Tom's tabs to scroll-spy tabs
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33411 Converting Tom's tabs to scroll-spy tabs Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33471) Config page layout breaks when the page
Title: Message Title Kohsuke Kawaguchi updated an issue Jenkins / JENKINS-33471 Config page layout breaks when the page Change By: Kohsuke Kawaguchi Follow up from [PR #2106|https://github.com/jenkinsci/jenkins/pull/2106][~jglick] reports that with a screen that's very wide, the layout breaks. See his comment from [here|https://github.com/jenkinsci/jenkins/pull/2106#issuecomment-195172969] ! [screenshot| https://cloud.githubusercontent.com/assets/154109/13693211/aeea336c-e716-11e5-9e8b-e3faa9d8b56b.png ! ] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33471) Config page layout breaks when the page
Title: Message Title Kohsuke Kawaguchi assigned an issue to gus reiber Jenkins / JENKINS-33471 Config page layout breaks when the page Change By: Kohsuke Kawaguchi Assignee: gus reiber Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33471) Config page layout breaks when the page
Title: Message Title Kohsuke Kawaguchi created an issue Jenkins / JENKINS-33471 Config page layout breaks when the page Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Mar/16 4:57 AM Labels: 2.0 Priority: Major Reporter: Kohsuke Kawaguchi Follow up from PR #2106 Jesse Glick reports that with a screen that's very wide, the layout breaks. See his comment from here Add Comment
[JIRA] [core] (JENKINS-33471) Config page layout breaks when the page
Title: Message Title Kohsuke Kawaguchi updated an issue Jenkins / JENKINS-33471 Config page layout breaks when the page Change By: Kohsuke Kawaguchi Follow up from [PR #2106|https://github.com/jenkinsci/jenkins/pull/2106][~jglick] reports that with a screen that's very wide, the layout breaks. See his comment from [here|https://github.com/jenkinsci/jenkins/pull/2106#issuecomment-195172969] !https://cloud.githubusercontent.com/assets/154109/13693211/aeea336c-e716-11e5-9e8b-e3faa9d8b56b.png! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33462) Security Token dialogue should link to quality docs about where to find Jenkins logs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33462 Re: Security Token dialogue should link to quality docs about where to find Jenkins logs Code changed in jenkins User: R. Tyler Croy Path: core/src/main/resources/jenkins/install/SetupWizard/authenticate-security-token.jelly http://jenkins-ci.org/commit/jenkins/4a675ed51f60ab4a62787c0dfe79b48440ee Log: Provide more consistent copy in the security token dialogue and a link to find logs I believe this text is more clear for a new user to understand why they must complete this step of the process. Fixes JENKINS-33462 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-33355) Support Pipeline (Workflow) plugin
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-33355 Support Pipeline (Workflow) plugin Change By: Jesse Glick Issue Type: Bug New Feature Component/s: workflow-plugin Assignee: Jesse Glick Labels: workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33395) Jenkins should install a default UncaughtExceptionHander
Title: Message Title Jesse Glick commented on JENKINS-33395 Re: Jenkins should install a default UncaughtExceptionHander the threads won;t just silently die without any trace Well, by default a stack trace is printed to stderr. Which may or may not be reported to an admin. In practice most threads in Jenkins already catch all errors at some other level and log them somehow. But this could be useful as a final fallback. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21249) Update Groovy
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21249 Re: Update Groovy Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml core/src/main/java/hudson/cli/GroovyshCommand.java core/src/main/java/hudson/util/spring/BeanBuilder.java pom.xml test/pom.xml test/src/test/java/hudson/cli/GroovyshCommandTest.java http://jenkins-ci.org/commit/jenkins/54d1cf11c9e8cceb7cd593b81c170b2c784257d6 Log: Merge pull request #2034 from daspilker/2.0-JENKINS-21249 JENKINS-21249 Update Groovy to 2.4.6 Compare: https://github.com/jenkinsci/jenkins/compare/219481a2926a...54d1cf11c9e8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33395) Jenkins should install a default UncaughtExceptionHander
Title: Message Title Jesse Glick started work on JENKINS-33395 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33395) Jenkins should install a default UncaughtExceptionHander
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33395 Jenkins should install a default UncaughtExceptionHander Change By: Jesse Glick Labels: robustness Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33462) Security Token dialogue should link to quality docs about where to find Jenkins logs
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-33462 Security Token dialogue should link to quality docs about where to find Jenkins logs Change By: R. Tyler Croy Attachment: jenkins2_security_token_1.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-33470) Global build-pipeline-view throws ServletException: Please login to access job for user without permissions
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-33470 Global build-pipeline-view throws ServletException: Please login to access job for user without permissions Issue Type: Bug Assignee: Unassigned Attachments: default-page.html Components: build-pipeline-plugin Created: 11/Mar/16 2:35 AM Environment: Ubuntu 14.04 x86_64 Jenkins ver. 1.642.1 Oracle JDK 1.7 Build Pipeline Plugin 1.5.1 Role-based Authorization Strategy 2.2.0 Priority: Blocker Reporter: Rick Liu Related to: JENKINS-21188 Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access for not-logged in users I'm using "role-based authorization strategy" plugin for my user access control. I have a global build-pipeline view containing jobs accessible to some users only. When people, who d
[JIRA] [core] (JENKINS-33462) Security Token dialogue should link to quality docs about where to find Jenkins logs
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-33462 Security Token dialogue should link to quality docs about where to find Jenkins logs Change By: R. Tyler Croy Attachment: jenkins2_security_token.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-33469) Support for environment variable expansion in View Mappings
Title: Message Title
Adi Chiru updated an issue
Jenkins / JENKINS-33469
Support for environment variable expansion in View Mappings
Change By:
Adi Chiru
At this moment there is no way to use the polling does not uses the variables (environment or even job parameters) used into the " View Mappings filed " field of the P4Plugin and this makes the actual build to work but the polling to fail . This is a feature Having support for env variables expansion in the other perforce plugin supports and it make Polling mechanism makes sense especially when you need to build from various locations Perforce but you also need to limit the number of jobs. For example I am using one job for each project to continuously build from master branch but . Instead of using another set of jobs, with 99% identical configuration, I want would like to use the same job to build from release branches. If This means I need to create a special release modify something like://main-repo/products/app1/master/... //${JOB_NAME}/...to look like://main-repo/products/$app/$ branch the entire setups becomes more complicated /... //${JOB_NAME}/... and with a lot feed the values of redundant those vars as parameters of the job.Doing so works for the build but the polling mechanism is not capable of resolving those vars.It would be nice to actually have its own configuration for the polling location maybe . ...
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] [p4-plugin] (JENKINS-33469) Support for environment variable expansion in View Mappings
Title: Message Title Adi Chiru created an issue Jenkins / JENKINS-33469 Support for environment variable expansion in View Mappings Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 11/Mar/16 1:43 AM Priority: Major Reporter: Adi Chiru At this moment there is no way to use variables (environment or even job parameters) into the View Mappings filed of the P4Plugin. This is a feature the other perforce plugin supports and it make sense especially when you need to limit the number of jobs. For example I am using one job to continuously build from master branch but I want to use the same job to build from release branches. If I need to create a special release branch the entire setups becomes more complicated and with a lot of redundant configuration. Add Comment
[JIRA] [core] (JENKINS-31176) Ability to limit job types based on permissions
Title: Message Title Daniel Beck commented on JENKINS-31176 Re: Ability to limit job types based on permissions Patrick Wolf What happened to this one? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-26375) Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later
Title: Message Title Eric Lordahl edited a comment on JENKINS-26375 Re: Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later i have a fix in place for this, and will submit a PR when i have a full understanding of all use cases of this plugin. My changes simply drop the domain when looking up the user, which might not be correct if your users have the domain prepended. Question: Are [~oli_at_jsi], are there scenarios where Jenkins will create a user-id with the domain prepended? It does not appear to work this way in my instance, but i see that Jenkins User.get will replace '\' with '_'. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-26375) Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later
Title: Message Title Eric Lordahl commented on JENKINS-26375 Re: Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later i have a fix in place for this, and will submit a PR when i have a full understanding of all use cases of this plugin. My changes simply drop the domain when looking up the user, which might not be correct if your users have the domain prepended. Question: Are there scenarios where Jenkins will create a user-id with the domain prepended? It does not appear to work this way in my instance, but i see that Jenkins User.get will replace '\' with '_'. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33256) Re-enable GitHub PR support for public repos
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33256 Re: Re-enable GitHub PR support for public repos Code changed in jenkins User: Jesse Glick Path: CHANGES.md multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/SCMBinder.java multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/SCMBinderTest.java pom.xml http://jenkins-ci.org/commit/workflow-plugin/76bdc6f044f2eaf60f0f313cb09c7e006802e9a5 Log: Merge pull request #244 from jglick/getTrustedRevision JENKINS-33256 Calling SCMSource.getTrustedRevision Compare: https://github.com/jenkinsci/workflow-plugin/compare/f19e83d255e2...76bdc6f044f2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit-trail-plugin] (JENKINS-32333) Audit Trail Plugin : can't install plugin
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-32333 Audit Trail Plugin : can't install plugin Change By: Christopher Orr Labels: plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33334) Out of the Box: Restart -button is barely visible on 1280 x 800 screen
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-4 Out of the Box: Restart -button is barely visible on 1280 x 800 screen Change By: Christopher Orr Labels: 2.0 user-experience Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33334) Out of the Box: Restart -button is barely visible on 1280 x 800 screen
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-4 Out of the Box: Restart -button is barely visible on 1280 x 800 screen Change By: Christopher Orr Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"
Title: Message Title
Michael Rose commented on JENKINS-30244
Re: Stash command with includes: '**' fails due to "unclosed entries"
CORRECTION: It has nothing to do with the number of time stash is called. It simply failed when run on RHEL 5.6.
x = ['x86_64-Linux-2.618'] //,'x86_64-Linux-RHEL7']
conf=[:]
for (int i = 0; i < 2; i++){
def arch=x[i]
node(arch) {
sh "mkdir -p $arch/x/xx/xxx/; touch $arch-y1 $arch/x/xx/y2 $arch/x/xx/xxx/y3 $arch/x/xx/xxx//y4"
stash includes: "$arch-y1,$arch/**/*", name: "${arch}-$i-common"
}
}
This caused an error when run on: -sh-3.2$ uname -a Linux b261802 2.6.18-238.5.1.el5 #1 SMP Mon Feb 21 05:52:39 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33462) Security Token dialogue should link to quality docs about where to find Jenkins logs
Title: Message Title R. Tyler Croy started work on JENKINS-33462 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33441) GitSCMSource: Includes & excludes match more than expected
Title: Message Title
Alastair D'Silva edited a comment on JENKINS-33441
Re: GitSCMSource: Includes & excludes match more than expected
I disagree, as the claimed existing use is a corner case which replicates the functionality of the leading wildcard ('*'), if a user wanted this functionality, they should be explicitly asking for it, indeed, there exists explicit code and tests for handling that case.Nevertheless, I have amended the pull request to instead introduce a regex mode, enabled on a per-token basis by prefixing the token with a caret (regex anchor to the start). This should be safe as carets are not valid characters for git names. You can find it here: https://github.com/jenkinsci/git-plugin/pull/384
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33441) GitSCMSource: Includes & excludes match more than expected
Title: Message Title
Alastair D'Silva commented on JENKINS-33441
Re: GitSCMSource: Includes & excludes match more than expected
I disagree, as the claimed existing use is a corner case which replicates the functionality of the leading wildcard ('*'), if a user wanted this functionality, they should be explicitly asking for it, indeed, there exists explicit code and tests for handling that case.
Nevertheless, I have amended the pull request to instead introduce a regex mode, enabled on a per-token basis by prefixing the token with a caret (regex anchor to the start). This should be safe as carets are not valid characters for git names.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-publisher-plugin] (JENKINS-18105) Views are not updated when builds are published
Title: Message Title Karl Schulz commented on JENKINS-18105 Re: Views are not updated when builds are published Any update here? I just setup an instance to publish from one Jenkins to another and notice that the build status in the published views are not updated (they just show N/A for me). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"
Title: Message Title
Michael Rose commented on JENKINS-30244
Re: Stash command with includes: '**' fails due to "unclosed entries"
Actually it looks like the problem has nothing to do with parallel and is just the fact that stash is being called more than once.
This script produces the same error.
x = ['x86_64-Linux-RHEL7','x86_64-Linux-2.618']
conf=[:]
for (int i = 0; i < 2; i++){
def arch=x[i]
node(arch) {
sh "mkdir -p $arch/x/xx/xxx/; touch $arch-y1 $arch/x/xx/y2 $arch/x/xx/xxx/y3 $arch/x/xx/xxx//y4"
stash includes: "$arch-y1,$arch/**/*", name: "${arch}-common"
}
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"
Title: Message Title
Michael Rose reopened an issue
I am having the same issue with the workflow script that I created.
Jenkins version: 1.651 Pipeline plugin version: 1.14
Here is a simplified version of the script that produces the error.
x = ['x86_64-Linux-RHEL7','x86_64-Linux-2.618']
conf=[:]
for (int i = 0; i < 2; i++){
def arch=x[i]
conf[arch] = {
node(arch) {
sh "mkdir -p $arch/x/xx/xxx/; touch $arch-y1 $arch/x/xx/y2 $arch/x/xx/xxx/y3 $arch/x/xx/xxx//y4"
stash includes: "$arch-y1,$arch/**/*", name: "${arch}-common"
}
}
}
node('master'){
parallel conf
}
Jenkins / JENKINS-30244
Stash command with includes: '**' fails due to "unclosed entries"
Change By:
Michael Rose
Resolution:
Incomplete
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [sidebar-link-plugin] (JENKINS-33458) Make Sidebar-Link Plugin Compatible With Pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33458 Re: Make Sidebar-Link Plugin Compatible With Pipeline Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/c90a35dec2f8ac2fd5d52f5b1ca39b9a13e51571 Log: Merge pull request #361 from alexanderrtaylor/master JENKINS-33458 Note Sidebar Link plugin Compare: https://github.com/jenkinsci/workflow-plugin/compare/1d45a6ea661f...c90a35dec2f8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title Jesse Glick commented on JENKINS-33456 Re: durable-task 1.8 breaks workflow bat steps Given JENKINS-32000 I wonder if I should just have some global configuration pulldown for Windows users letting them select an arbitrary version of the code after trial and error. What version of Windows do you run? Do you have a way of reproducing from scratch? Are you able to ascertain whether the control directory is created, and if so, whether the correct output is sent to it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sidebar-link-plugin] (JENKINS-33458) Make Sidebar-Link Plugin Compatible With Pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33458 Re: Make Sidebar-Link Plugin Compatible With Pipeline Code changed in jenkins User: Alex Taylor Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/a52befc18cddcd153cf9468797bd1119e75c13b2 Log: JENKINS-33458 Note Sidebar Link plugin Sidebar link Plugin added to Compatibility.md Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov edited a comment on JENKINS-33468 Re: CLONE - Sandbox cannot handle methods Groovy provides additionally Issue seems same as JENKINS-25119 just something missed.Update: Just see I'm not using latest plug-in. Update center lags behind. Trying latest one now. update 2: same with 1.17 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-33468 CLONE - Sandbox cannot handle methods Groovy provides additionally Change By: akostadinov Environment: RHEL x86_64, Jenkins 1.642.2, Email Extension Plugin 2.38.2, script-security 1. 15 17 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov edited a comment on JENKINS-33468 Re: CLONE - Sandbox cannot handle methods Groovy provides additionally Issue seems same as JENKINS-25119 just something missed. Update: Just see I'm not using latest plug-in. Update center lags behind. Trying latest one now. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-33468 CLONE - Sandbox cannot handle methods Groovy provides additionally Change By: akostadinov Environment: Windows 8 64bit RHEL x86_64 , Jenkins 1. 509 642 . 4 2 , groovy-postbuild Email Extension Plugin 2. 0 38.2 , script-security 1. 6 15 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title
akostadinov updated an issue
Jenkins / JENKINS-33468
CLONE - Sandbox cannot handle methods Groovy provides additionally
Change By:
akostadinov
Running Basically creating a following pre-send script for editable email plug-in results in the exception below. Here's the part of the script blowing: {code :java } "30".toInteger def artifactNamed ( build, name ) { return build.artifacts.find { it.fileName == name } ; } {code} Results following error Console log :{ noformat code:java } Setting up sandbox for pre-send scriptgroovy.lang.MissingPropertyException: No such property: it for class: Script1 at org. jenkinsci codehaus . plugins groovy . scriptsecurity runtime . ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:454) at org.kohsuke.groovy. sandbox. RejectedAccessException impl.Checker$4.call(Checker.java : unclassified method 243) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onGetProperty(GroovyInterceptor. java :52) at org . kohsuke.groovy.sandbox.GroovyValueFilter.onGetProperty(GroovyValueFilter.java:73) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221) at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:177) at Script1$_artifactNamed_closure1.doCall(Script1.groovy:2) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java. lang. String toInteger reflect.Method.invoke(Method.java:606) at org. jenkinsci codehaus . plugins groovy . scriptsecurity reflection . CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:39) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.BooleanReturningMethodInvoker.invoke(BooleanReturningMethodInvoker.java:49) at org.codehaus.groovy.runtime.callsite.BooleanClosureWrapper.call(BooleanClosureWrapper.java:52) at org.codehaus.groovy.runtime.DefaultGroovyMethods.find(DefaultGroovyMethods.java:2695) at org.codehaus.groovy.runtime.dgm$261.invoke(Unknown Source) at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271) at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodS
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov commented on JENKINS-33468 Re: CLONE - Sandbox cannot handle methods Groovy provides additionally Issue seems same as JENKINS-25119 just something missed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov created an issue Jenkins / JENKINS-33468 CLONE - Sandbox cannot handle methods Groovy provides additionally Issue Type: Bug Assignee: Jesse Glick Components: script-security-plugin Created: 10/Mar/16 9:37 PM Environment: Windows 8 64bit, Jenkins 1.509.4, groovy-postbuild 2.0, script-security 1.6 Priority: Major Reporter: akostadinov Running a following script "30".toInteger(); Results following error: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.String toInteger at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:63) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:111) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:108) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStat
[JIRA] [core] (JENKINS-33464) Inconsistent verbiage in 2.0 plugin setup screen
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33464 Re: Inconsistent verbiage in 2.0 plugin setup screen Code changed in jenkins User: R. Tyler Croy Path: core/src/main/resources/jenkins/install/pluginSetupWizard.properties http://jenkins-ci.org/commit/jenkins/29371d38594ce0a3bcd66f4d950d2fe1aeec51f3 Log: Clean-up the verbiage in the new-user plugin setup dialog I worked much of this out with @orrc and @omehegan in #jenkins-community, but feel these string changes will make the dialog more clear and understandable to a new Jenkins user. [FIX JENKINS-33464] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33464) Inconsistent verbiage in 2.0 plugin setup screen
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33464 Inconsistent verbiage in 2.0 plugin setup screen Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33296) Initial plugin setup needs to consider implied dependencies
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33296 Re: Initial plugin setup needs to consider implied dependencies Code changed in jenkins User: Daniel Beck Path: war/src/main/js/api/plugins.js http://jenkins-ci.org/commit/jenkins/7f87486c73b1c63cc595c0fc380d42ada45f6116 Log: Temporarily remove plugins affected by JENKINS-33296 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-organization-folder-plugin] (JENKINS-32155) Recognize new repositories automatically
Title: Message Title
Kurt Madel commented on JENKINS-32155
Re: Recognize new repositories automatically
This does not appear to work with the 1.0 release of github-organization-folder-plugin (on Jenkins core 1.625.3).
The Jenkins logs do contain the following, but the org repos are not rescanned:
Mar 10, 2016 7:56:27 PM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent Received POST for https://github.beescloud.com/sa-team/repo-scan-test
Here is what was sent from GitHub (enterprise, v 2.5.1): Headers {{Request URL: http://sa-team-beescloud.jenkins-latest.beedemo.net/github-webhook/ Request method: POST content-type: application/x-www-form-urlencoded Expect: User-Agent: GitHub-Hookshot/35ff2c9 X-GitHub-Delivery: 21537c00-e6fa-11e5-98ed-cdbdb66a9a74 X-GitHub-Event: repository}}
Payload (partial) {{{ "action": "created", "repository": { "id": 6, "name": "repo-scan-test", "full_name": "sa-team/repo-scan-test", "owner": {}}
Nothing happens in the GitHub Org folder in Jenkins.
A manual re-scan will find and add the new repo.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Yannick Kamezac commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed I tried parallel builds with MSBuild plugin 1.25 on top of Jenkins 1.580.1 but unfortunately I still get this error (fatal error C1090: PDB API call failed, error code '23'). Did I miss something ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33464) Inconsistent verbiage in 2.0 plugin setup screen
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-33464 Inconsistent verbiage in 2.0 plugin setup screen Change By: R. Tyler Croy Attachment: jenkins2_customize_strings_3.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33464) Inconsistent verbiage in 2.0 plugin setup screen
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-33464 Inconsistent verbiage in 2.0 plugin setup screen Change By: R. Tyler Croy Attachment: jenkins2_customize_strings_2.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Jesse Glick commented on JENKINS-33467 Re: CauseAction.causes can become huge JENKINS-4831 deduplicated the display, but not the storage. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33464) Inconsistent verbiage in 2.0 plugin setup screen
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-33464 Inconsistent verbiage in 2.0 plugin setup screen The "customize strings" screenshot contains some experimentation with new verbiage Change By: R. Tyler Croy Attachment: jenkins2_customize_strings.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33465) Add Jenkins build status badge
Title: Message Title Ludovic Fernandez commented on JENKINS-33465 Re: Add Jenkins build status badge My PR is not valid because the build status doesn't represent the branch master. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Jesse Glick started work on JENKINS-33467 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-33467 CauseAction.causes can become huge Issue Type: Bug Assignee: Jesse Glick Components: core Created: 10/Mar/16 8:07 PM Labels: performance Priority: Major Reporter: Jesse Glick If you have some tool constantly pinging jobs/.../build?token=... but the job is stuck in the queue for a long time, you will get a CauseAction with a potentially unbounded number of causes, all identical RemoteCause instances. In a system with tens of thousands of build records loaded, there can be millions of such causes. This is a waste of heap space (and disk space, disk I/O time to load). Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-33466) Current master branch fail to build
Title: Message Title Ludovic Fernandez updated an issue Jenkins / JENKINS-33466 Current master branch fail to build Change By: Ludovic Fernandez Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33466) Current master branch fail to build
Title: Message Title Ludovic Fernandez created an issue Jenkins / JENKINS-33466 Current master branch fail to build Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 10/Mar/16 8:05 PM Priority: Blocker Reporter: Ludovic Fernandez The merge of the PR772 (https://github.com/jenkinsci/job-dsl-plugin/pull/772) break the build. See https://jenkins.ci.cloudbees.com/job/plugins/job/job-dsl-plugin/1915/console Add Comment
[JIRA] [git-plugin] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-19022 GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields Change By: Jesse Glick Labels: branch build.xml builddata git performance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33465) Add Jenkins build status badge
Title: Message Title Ludovic Fernandez commented on JENKINS-33465 Re: Add Jenkins build status badge https://github.com/jenkinsci/job-dsl-plugin/pull/780 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33465) Add Jenkins build status badge
Title: Message Title Ludovic Fernandez created an issue Jenkins / JENKINS-33465 Add Jenkins build status badge Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 10/Mar/16 7:55 PM Priority: Minor Reporter: Ludovic Fernandez Add Jenkins build status badge. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-33464) Inconsistent verbiage in 2.0 plugin setup screen
Title: Message Title R. Tyler Croy started work on JENKINS-33464 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-31814) dpkg error installing jenkins 1.639 on debian platforms
Title: Message Title Trevor Jones commented on JENKINS-31814 Re: dpkg error installing jenkins 1.639 on debian platforms Jenkins now appears to require java 7. This solved it for me on Ubuntu 12.04: sudo add-apt-repository ppa:webupd8team/java sudo apt-get update sudo apt-get install oracle-java7-installer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32561) Add NotExecutedNodeAction support to workflow
Title: Message Title Sam Van Oort resolved as Fixed Jenkins / JENKINS-32561 Add NotExecutedNodeAction support to workflow Change By: Sam Van Oort Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33464) Inconsistent verbiage in 2.0 plugin setup screen
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-33464 Inconsistent verbiage in 2.0 plugin setup screen Issue Type: Task Assignee: R. Tyler Croy Attachments: plugin-setup.png Components: core Created: 10/Mar/16 7:33 PM Labels: 2.0 community-bee Priority: Minor Reporter: R. Tyler Croy This ticket is really just to track some work that I had already started to change some verbiage in the "plugin setup" screen (see attached image). For example, there are three different verbs used to refer to the same action "Choose plugins" "Install the set of plugins" and "Select from a" I'll submit a pull request shortly making these more consistent
[JIRA] [job-dsl-plugin] (JENKINS-33463) Support BuildResultTriggerPlugin
Title: Message Title Ludovic Fernandez commented on JENKINS-33463 Re: Support BuildResultTriggerPlugin https://github.com/jenkinsci/job-dsl-plugin/pull/779 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33463) Support BuildResultTriggerPlugin
Title: Message Title Ludovic Fernandez created an issue Jenkins / JENKINS-33463 Support BuildResultTriggerPlugin Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 10/Mar/16 7:26 PM Labels: plugin Priority: Minor Reporter: Ludovic Fernandez Support BuildResultTriggerPlugin. https://wiki.jenkins-ci.org/display/JENKINS/BuildResultTrigger+Plugin Add Comment
[JIRA] [xshell-plugin] (JENKINS-33431) Single variable that includes multiple arguments does not work on Linux.
Title: Message Title Mike Murray commented on JENKINS-33431 Re: Single variable that includes multiple arguments does not work on Linux. This might help explain the issue. The same test.sh is being invoked first by "execute shell", then by "XShell", with a single TEST parameter having value of: 1, 2 3 4,5\ 6 [workspace] $ /bin/sh -xe /tmp/hudson5780634845144170328.sh + test.sh 1, 2 3 '4,5\' 6 SHELL: /bin/bash Arg count: 5 [workspace] $ test.sh $TEST SHELL: /bin/bash Arg count: 1 test.sh: echo "SHELL: $SHELL" echo "Arg count: $#" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Inv
Title: Message Title Larry Shatzer, Jr. deleted an issue Jenkins / JENKINS-33460 t This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33462) Security Token dialogue should link to quality docs about where to find Jenkins logs
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-33462 Security Token dialogue should link to quality docs about where to find Jenkins logs Change By: R. Tyler Croy Labels: 2.0 security Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33462) Security Token dialogue should link to quality docs about where to find Jenkins logs
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-33462 Security Token dialogue should link to quality docs about where to find Jenkins logs Issue Type: Task Assignee: R. Tyler Croy Attachments: jenkins2_securitytoken.png Components: core Created: 10/Mar/16 6:53 PM Environment: 4e27ea291108b6ae16903b9d0b01622134a097eb Priority: Minor Reporter: R. Tyler Croy Currently on the 2.0 branch (4e27ea291108b6ae16903b9d0b01622134a097eb) doing some strings work and I noticed that the dialog, screenshot below, does not provide the user much guidance on where to actually find the logs which will contain the security token. This should link to clear documentation to answer "where can I find the logs?" which would outline what exists on Windows, Mac OS X, jenkisn.war, Linux packages, etc.
[JIRA] [mailer-plugin] (JENKINS-33461) The post-build mail action should have an option to trigger only on the first failed build
Title: Message Title Jeffrey Marshall created an issue Jenkins / JENKINS-33461 The post-build mail action should have an option to trigger only on the first failed build Issue Type: Improvement Assignee: Unassigned Components: mailer-plugin Created: 10/Mar/16 6:38 PM Labels: user-experience Priority: Minor Reporter: Jeffrey Marshall As per the summary, there should be an option to send a notification to the "build breakers" only on the first failed build in a string of consecutive failed builds. If a subsquent build continues to fail, no individual notification emails should be sent if the option is selected. Add Comment
[JIRA] [workflow-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26535 Re: DescribableHelper does not handle wildcards well Code changed in jenkins User: Kohsuke Kawaguchi Path: plugin/src/main/java/org/jenkinsci/plugins/symbol/describable/DescribableModel.java http://jenkins-ci.org/commit/symbol-plugin/f467a821c1139b55cc74f4b8a11e81393bb71cef Log: JENKINS-26535 tiger-types to the rescue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33358) Groovy and PermGen memory leak
Title: Message Title
Christian Lague updated an issue
Jenkins / JENKINS-33358
Groovy and PermGen memory leak
Change By:
Christian Lague
Attachment:
permgenIssue.jpg
We have recently experienced OutOfMemory errors on some large Jenkins instances that predominantly have frequently executed jobs that contain either System Groovy scripts or Build Flow project types. In one case after disabling a groovy script that was being executed via the Global Post Script Plugin after every build, the PermGen profile improved dramatically. !permgenIssue.jpg|thumbnail! We tested further with GroovyShell to run a groovy script, not depending on Jenkins. Java7: java.lang.OutOfMemoryError: PermGen spaceJava8: java.lang.OutOfMemoryError: Java heap spaceThe tests use 2.4.6 version of groovy which is the latest version. However, the issue is still there.org.codehaus.groovygroovy-all2.4.6---Configure 10 jobs which build per minuteEach build triggers a groovy script by Global Post Script Plugin.{noformat}class Main {static void main(String... args) {println 'Groovy world!'def p = new Person()p.write()}}class Person {def write(){println 'i am writing ...!'}}{noformat}After sometime, the perm gen is eaten up. See the screenshot of jvisualvm.!Screenshot from 2016-03-07 09.43.29.png|thumbnail!I checked the source code of the plugin:https://github.com/jenkinsci/global-post-script-plugin/blob/master/src/main/java/com/orctom/jenkins/plugin/globalpostscript/ScriptExecutor.javaMy feeling is that it is probably caused by GroovyShell. Jenkins loads and runs groovy extensively and maybe there are places in core or other plugins having similar logic, I wonder1. if this is a potential memory leak, and2. if anyone has met similar issue.
Add Comment
[JIRA] [core] (JENKINS-29179) IndexOutOfBounds Exception when viewing live console
Title: Message Title bcalmac commented on JENKINS-29179 Re: IndexOutOfBounds Exception when viewing live console I've also encountered this in 1.635 while watching the console output of a job: Caused by: java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) at hudson.MarkupText.addMarkup(MarkupText.java:258) at hudson.tasks._maven.Maven3MojoNote.annotate(Maven3MojoNote.java:56) at hudson.console.ConsoleAnnotationOutputStream$1.annotate(ConsoleAnnotationOutputStream.java:115) at hudson.console.ConsoleAnnotator$1Aggregator.annotate(ConsoleAnnotator.java:111) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:145) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:74) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:90) at org.kohsuke.stapler.framework.io.LargeText$HeadMark.moveTo(LargeText.java:312) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:227) at hudson.console.AnnotatedLargeText.writeHtmlTo(AnnotatedLargeText.java:169) at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:143) at org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:262) at hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:91) at sun.reflect.GeneratedMethodAccessor629.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-33358) Groovy and PermGen memory leak
Title: Message Title
Christian Lague updated an issue
Jenkins / JENKINS-33358
Groovy and PermGen memory leak
Change By:
Christian Lague
We have recently experienced OutOfMemory errors on some large Jenkins instances that predominantly have frequently executed jobs that contain either System Groovy scripts or Build Flow project types. In one case after disabling a groovy script that was being executed via the Global Post Script Plugin after every build, the PermGen profile improved as shown: dramatically. We test tested further with GroovyShell to run a groovy script, not depending on Jenkins. Java7: java.lang.OutOfMemoryError: PermGen spaceJava8: java.lang.OutOfMemoryError: Java heap spaceThe tests use 2.4.6 version of groovy which is the latest version. However, the issue is still there.org.codehaus.groovygroovy-all2.4.6---Configure 10 jobs which build per minuteEach build triggers a groovy script by Global Post Script Plugin.{noformat}class Main {static void main(String... args) {println 'Groovy world!'def p = new Person()p.write()}}class Person {def write(){println 'i am writing ...!'}}{noformat}After sometime, the perm gen is eaten up. See the screenshot of jvisualvm.!Screenshot from 2016-03-07 09.43.29.png|thumbnail!I checked the source code of the plugin:https://github.com/jenkinsci/global-post-script-plugin/blob/master/src/main/java/com/orctom/jenkins/plugin/globalpostscript/ScriptExecutor.javaMy feeling is that it is probably caused by GroovyShell. Jenkins loads and runs groovy extensively and maybe there are places in core or other plugins having similar logic, I wonder1. if this is a potential memory leak, and2. if anyone has met similar issue.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-33358) Groovy and PermGen memory leak
Title: Message Title
Christian Lague updated an issue
Jenkins / JENKINS-33358
Groovy and PermGen memory leak
Change By:
Christian Lague
We got the problem from the operation team who observe have recently experienced OutOfMemory errors on some large Jenkins instances that the perm gen size has been increased by monitoring plugin predominantly have frequently executed jobs that contain either System Groovy scripts or Build Flow project types . This is quite important for us because more and more In one case after disabling a groovy based steps are integrated into our CI procedure.After analysis, we simplify script that was being executed via the testing environment with 10 jobs and Global Post Script Plugin . after every build, the PermGen profile improved as shown: We test further with GroovyShell to run a groovy script, not depending on Jenkins. Java7: java.lang.OutOfMemoryError: PermGen spaceJava8: java.lang.OutOfMemoryError: Java heap spaceThe tests use 2.4.6 version of groovy which is the latest version. However, the issue is still there.org.codehaus.groovygroovy-all2.4.6---Configure 10 jobs which build per minuteEach build triggers a groovy script by Global Post Script Plugin.{noformat}class Main {static void main(String... args) {println 'Groovy world!'def p = new Person()p.write()}}class Person {def write(){println 'i am writing ...!'}}{noformat}After sometime, the perm gen is eaten up. See the screenshot of jvisualvm.!Screenshot from 2016-03-07 09.43.29.png|thumbnail!I checked the source code of the plugin:https://github.com/jenkinsci/global-post-script-plugin/blob/master/src/main/java/com/orctom/jenkins/plugin/globalpostscript/ScriptExecutor.javaMy feeling is that it is probably caused by GroovyShell. Jenkins loads and runs groovy extensively and maybe there are places in core or other plugins having similar logic, I wonder1. if this is a potential memory leak, and2. if anyone has met similar issue.
Add Comment
[JIRA] [ec2-plugin] (JENKINS-8970) Connect EBS volumes to EC2 for shared workspaces between nodes
Title: Message Title Ebrahim Moshaya commented on JENKINS-8970 Re: Connect EBS volumes to EC2 for shared workspaces between nodes definitely a good idea.. Especially if you are using Maven and want to share the private maven repository between slaves. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-33460) t
Title: Message Title Marcus Mosttler closed an issue as Incomplete Jenkins / JENKINS-33460 t Change By: Marcus Mosttler Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-33460) t
Title: Message Title Marcus Mosttler created an issue Jenkins / JENKINS-33460 t Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 10/Mar/16 5:17 PM Priority: Minor Reporter: Marcus Mosttler Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "J
[JIRA] [project-inheritance-plugin] (JENKINS-22885) Creation of Inheritance Project throws Exception
Title: Message Title Jirong Hu edited a comment on JENKINS-22885 Re: Creation of Inheritance Project throws Exception Is there any impact changing from "Plain Text" to "Raw HTML"? I am having the same issue with Windows Jenkins ver. 1.638. Install the 1.5.1 plugin has the same issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance-plugin] (JENKINS-22885) Creation of Inheritance Project throws Exception
Title: Message Title Jirong Hu commented on JENKINS-22885 Re: Creation of Inheritance Project throws Exception Is there any impact changing from "Plain Text" to "Raw HTML"? I am having the same issue with Windows Jenkins ver. 1.638. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33374) Setup wizard offers the restart button even when it doesn't work
Title: Message Title Daniel Beck commented on JENKINS-33374 Re: Setup wizard offers the restart button even when it doesn't work Not a major issue as all qualifying plugins won't require a restart after JENKINS-33106 has been implemented. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25488) New UI wastes horizontal space
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-25488 New UI wastes horizontal space Change By: Daniel Beck Labels: 2.0 -rejected user-experience Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21486) Fail a plugin if its dependencies doesn't exist
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-21486 Fail a plugin if its dependencies doesn't exist Change By: Daniel Beck Labels: 2.0 -rejected plugin-manager robustness Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4610) hudson.scm.CVSChangeLogSet$CVSChangeLog cannot be cast to hudson.plugins.mercurial.MercurialChangeSet
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-4610 hudson.scm.CVSChangeLogSet$CVSChangeLog cannot be cast to hudson.plugins.mercurial.MercurialChangeSet Change By: Daniel Beck Labels: 2.0 -rejected Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33406) Jenkins cannot be installed offline
Title: Message Title Daniel Beck resolved as Cannot Reproduce Seems the secure setup fixed this. Jenkins / JENKINS-33406 Jenkins cannot be installed offline Change By: Daniel Beck Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33459) Polling schedule text timestamps ignore "H"
Title: Message Title David Kaelbling created an issue Jenkins / JENKINS-33459 Polling schedule text timestamps ignore "H" Issue Type: Improvement Assignee: Unassigned Components: core Created: 10/Mar/16 4:21 PM Priority: Trivial Reporter: David Kaelbling I have a job with build schedule "H/30 * * * *". The text under the schedule says: Would last have run at Thursday, March 10, 2016 11:00:18 AM EST; would next run at Thursday, March 10, 2016 11:30:18 AM EST. In fact the job runs at 13 or 43 minutes after the hour. It would be kinder to factor "H" into the timestamps shown, or to include some wording to indicate that "would next run at" does not reflect when the job will next run. Add Comment
[JIRA] [job-import-plugin] (JENKINS-33379) Importing jobs doenst do anything since version 1.3
Title: Message Title Werner Keil commented on JENKINS-33379 Re: Importing jobs doenst do anything since version 1.3 Minor for a bug that made the plugin effectively useless. What's a major one then? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-33454) Cannot configure EnvInject plugin using job-dsl
Title: Message Title Tuure Laurinolli commented on JENKINS-33454 Re: Cannot configure EnvInject plugin using job-dsl Thank you. Restart helped. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-33454) Cannot configure EnvInject plugin using job-dsl
Title: Message Title Tuure Laurinolli closed an issue as Not A Defect Jenkins / JENKINS-33454 Cannot configure EnvInject plugin using job-dsl Change By: Tuure Laurinolli Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sidebar-link-plugin] (JENKINS-33458) Feature Request: Make Sidebar-Link Plugin Compatible With Pipeline
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-33458 Feature Request: Make Sidebar-Link Plugin Compatible With Pipeline Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sidebar-link-plugin] (JENKINS-33458) Feature Request: Make Sidebar-Link Plugin Compatible With Pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33458 Feature Request: Make Sidebar-Link Plugin Compatible With Pipeline Change By: Jesse Glick Component/s: sidebar-link-plugin Component/s: workflow-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sidebar-link-plugin] (JENKINS-33458) Make Sidebar-Link Plugin Compatible With Pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33458 Make Sidebar-Link Plugin Compatible With Pipeline Change By: Jesse Glick Summary: Feature Request: Make Sidebar-Link Plugin Compatible With Pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33458) Feature Request: Make Sidebar-Link Plugin Compatible With Pipeline
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-33458 Feature Request: Make Sidebar-Link Plugin Compatible With Pipeline Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 10/Mar/16 3:34 PM Environment: Jenkins version 1.625.x.x Sidebar plugin 1.7 Build Pipeline plugin 1.5.1 Labels: workflow Priority: Minor Reporter: Alex Taylor Please make the Sidebar-Link Plugin compatible with the pipeline plugin by adding the sidebar link access to pipeline jobs. https://wiki.jenkins-ci.org/display/JENKINS/Sidebar-Link+Plugin
[JIRA] [tfs-plugin] (JENKINS-33386) Shared project in Visual Studio solution not being pulled into workspace
Title: Message Title Olivier Dagenais closed an issue as Not A Defect Closing issue. Jenkins / JENKINS-33386 Shared project in Visual Studio solution not being pulled into workspace Change By: Olivier Dagenais Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33296) Initial plugin setup needs to consider implied dependencies
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-33296 Initial plugin setup needs to consider implied dependencies Change By: Keith Zantow Assignee: Tom FENNELLY Keith Zantow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
Volker commented on JENKINS-23273
Re: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Since there don't seem to be an overall agreement on how to set the default I would propose the following solution (untested pseudocode):
# Ensure the right ownership on files
. /etc/sysconfig/jenkins
JENKINS_CHOWN_USER=${JENKINS_USER:-jenkins}
JENKINS_CHOWN_HOME=${JENKINS_HOME:-/var/lib/jenkins}
if [ ! -e /var/lib/jenkins/.ran-chown-for-${JENKINS_CHOWN_USER} ]; then
# in case there where different users before
rm /var/lib/jenkins/.ran-chown-for-*
chown -R ${JENKINS_CHOWN_USER} /var/log/jenkins
chown -R ${JENKINS_CHOWN_USER} ${JENKINS_CHOWN_HOME}
echo $(date) >> /var/lib/jenkins/.chowned-to-${JENKINS_CHOWN_USER}
fi
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
