[JIRA] (JENKINS-36481) Remove clutter from BlueOceanUI
Title: Message Title Vivek Pandey resolved as Fixed Jenkins / JENKINS-36481 Remove clutter from BlueOceanUI Change By: Vivek Pandey 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-13190) Add ACLPermissionOverride Extension Point to grant additional permissions to an ACL regardless of the AuthorizationStrategy being used
Title: Message Title ikedam commented on JENKINS-13190 Re: Add ACLPermissionOverride Extension Point to grant additional permissions to an ACL regardless of the AuthorizationStrategy being used > Though this is really rough investigation, I can conclude that A is a really bad idea as it affects too many plugins. I also note that A contains popular plugins like matrix-auth-plugin and role-strategy-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-13190) Add ACLPermissionOverride Extension Point to grant additional permissions to an ACL regardless of the AuthorizationStrategy being used
Title: Message Title ikedam commented on JENKINS-13190 Re: Add ACLPermissionOverride Extension Point to grant additional permissions to an ACL regardless of the AuthorizationStrategy being used I believe there're two ways to introduce overriding ACLs. As ACL itself doesn't hold what item it is for, overriding should be performed to AuthorizationStrategy. A: Jenkins#getAuthorizationStrategy returns overridden AuthorizationStrategy. A new method Jenkins#getBaseAuthorizationStrategy is introduced to return the original AuthorizationStrategy. B: Jenkins#getAuthorizationStrategy returns the original AuthorizationStrategy. A new method Jenkins#getOverriddenAuthorizationStrategy is introduced to return the overridden AuthorizationStrategy. These two ways result following regressions: A: Plugins using Jenkins#getAuthorizationStrategy not to resolve ACLs (e.g. to test its own strategy is configured as Jenkins#getAuthorizationStrategy() instanceof XxxxAuthorizationStraetgy) will be broken. B: Plugins retrieving ACLs via Jenkins#getAuthorizationStrategy will be broken. I searched github of jenkinsci with getAuthorizationStrategy and list up plugins affected by A and B as followings: A: ssh2easy-plugin collabnet-plugin role-strategy-plugin gitlab-auth-plugin jenkins-scripts security-no-captcha-plugin matrix-auth-plugin puppet-jenkins B. gitlab-auth-plugin pubsub-light-module support-core-plugin Though this is really rough investigation, I can conclude that A is a really bad idea as it affects too many plugins. Plugins should use Jenkins.getACL, Item.getACL and so on instread of getAuthorizationStrategy().getACL(item). Add Comment
[JIRA] (JENKINS-36895) favorite star layout issues if running at page zoom < 100%
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-36895 favorite star layout issues if running at page zoom < 100% Change By: Ben Walding Attachment: image-2016-07-23-12-10-54-717.png 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-36895) favorite star layout issues if running at page zoom < 100%
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-36895 favorite star layout issues if running at page zoom < 100% Change By: Ben Walding Attachment: image-2016-07-23-12-11-18-019.png h3. Overview* set page zoom to 90%* look at favorite starsh3. ExpectedFavorite stars are fully formedFavorite stars are alignedh3. Actual Favorite stars are slightly clippedFavorite stars are not horizontally aligned (note - one of my jobs is not triggered by commits - but by scheduled polling - I suspect that is the cause of some of the layout issue - no commit identifier) !image-2016-07-23-12-05-35-016.png|thumbnail! !image-2016-07-23-12- 10 11 - 54 18 - 717 019 .png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-36895) favorite star layout issues if running at page zoom < 100%
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-36895 favorite star layout issues if running at page zoom < 100% Change By: Ben Walding Summary: favorite star clipped layout issues if running at page zoom < 100% Attachment: image-2016-07-23-12-10-54-717.png h3. Overview* set page zoom to 90%* look at favorite starsh3. Expected Favourite Favorite stars are fully formed Favorite stars are aligned h3. Actual Favourite Favorite stars are slightly clipped Favorite stars are not horizontally aligned!image-2016-07-23-12-05-35-016.png|thumbnail! !image-2016-07-23-12-10-54-717.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36895) favorite star clipped if running at page zoom < 100%
Title: Message Title Ben Walding created an issue Jenkins / JENKINS-36895 favorite star clipped if running at page zoom < 100% Issue Type: Improvement Assignee: Unassigned Attachments: image-2016-07-23-12-05-35-016.png Components: blueocean-plugin Created: 2016/Jul/23 2:07 AM Environment: Chrome on OSX Blueocean plugin pack 1.0-alpha-4 Priority: Trivial Reporter: Ben Walding Overview set page zoom to 90% look at favorite stars Expected Favourite stars are fully formed Actual Favourite stars are slightly clipped Add Comment
[JIRA] (JENKINS-35102) Xvfb is not stopped
Title: Message Title Nick Mitchell commented on JENKINS-35102 Re: Xvfb is not stopped We have also begun to see this problem. We are running 1.0.16. It seems that, when a (freestyle, for us) job fails, Xvfb sometimes does not get cleaned up properly. We're running one slave per SoftLayer VM, no parallelism on node, but multiple jobs running across 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-36894) Refactor shortcuts of matrix-combination plugin
Title: Message Title ikedam created an issue Jenkins / JENKINS-36894 Refactor shortcuts of matrix-combination plugin Issue Type: Task Assignee: ikedam Components: matrix-combinations-parameter-plugin Created: 2016/Jul/23 12:56 AM Environment: matrix-combinations-plugin 1.0.9 Priority: Major Reporter: ikedam _javascript_s for "Successful", "Failed", "All", "None" links are implemented in an ad-hoc way and it results: causes problems like JENKINS-36861, JENKINS-30918 lacks extensibility like JENKINS-36860, JENKINS-29797 I'll refactor this. Add Comment
[JIRA] (JENKINS-36511) Multi-configuration (matrix) multi-branch project configurations do not match standard Matrix type
Title: Message Title Rick Liu closed an issue as Fixed Confirm fixed. Jenkins / JENKINS-36511 Multi-configuration (matrix) multi-branch project configurations do not match standard Matrix type Change By: Rick Liu Status: Resolved Closed 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-36512) Multibranch project stops sync configuration to sub-branch project after making changes in sub-branch project
Title: Message Title Rick Liu closed an issue as Fixed Confirm fixed. Jenkins / JENKINS-36512 Multibranch project stops sync configuration to sub-branch project after making changes in sub-branch project Change By: Rick Liu Status: Resolved Closed 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-36893) Pipelines cannot change directory if directory is called stage
Title: Message Title
Charles Toller created an issue
Jenkins / JENKINS-36893
Pipelines cannot change directory if directory is called stage
Issue Type:
Bug
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2016/Jul/23 12:33 AM
Priority:
Minor
Reporter:
Charles Toller
In the latest version of Jenkins LTS, if you create a pipeline and make Groovy code that changes to a directory called 'stage', "stage", or '''stage''', it will still try and interpret it to a build stage and expect a name argument. If you go dir 'stage' {}, it will complain that you provided a closure to the name argument of a stage command. Furthermore (and, I find this even stranger), this Groovy code STILL tries to run stage in the same spot.
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
//This occurs with 'stage', "stage", or '''stage'''
def STG_DIRECTORY = 'stage'
dir STG_DIRECTORY {
//Some code
}
[JIRA] (JENKINS-36861) Matrix combination select Successful includes non-successful (skipped) item
Title: Message Title Rick Liu started work on JENKINS-36861 Change By: Rick Liu 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-36860) Add support to select matrix selection from previous build
Title: Message Title Rick Liu started work on JENKINS-36860 Change By: Rick Liu 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-36860) Add support to select matrix selection from previous build
Title: Message Title Rick Liu commented on JENKINS-36860 Re: Add support to select matrix selection from previous build Created pull-request: https://github.com/jenkinsci/matrix-combinations-plugin/pull/14 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-36860) Add support to select matrix selection from previous build
Title: Message Title Rick Liu assigned an issue to Rick Liu Jenkins / JENKINS-36860 Add support to select matrix selection from previous build Change By: Rick Liu Assignee: Rick Liu 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-31919) bitbucket plugin hook does not work for Jenkins behind SSL with self-signed cert: "NET_ERR"
Title: Message Title Alex Java updated an issue Jenkins / JENKINS-31919 bitbucket plugin hook does not work for Jenkins behind SSL with self-signed cert: "NET_ERR" Change By: Alex Java Priority: Blocker 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-31919) bitbucket plugin hook does not work for Jenkins behind SSL with self-signed cert: "NET_ERR"
Title: Message Title Alex Java commented on JENKINS-31919 Re: bitbucket plugin hook does not work for Jenkins behind SSL with self-signed cert: "NET_ERR" I added "/" at the end of the URL and now it works. thanks! would it make sense to make it work with either URL though? 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-36861) Matrix combination select Successful includes non-successful (skipped) item
Title: Message Title Rick Liu assigned an issue to Rick Liu Jenkins / JENKINS-36861 Matrix combination select Successful includes non-successful (skipped) item Change By: Rick Liu Assignee: Rick Liu 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-36861) Matrix combination select Successful includes non-successful (skipped) item
Title: Message Title Rick Liu commented on JENKINS-36861 Re: Matrix combination select Successful includes non-successful (skipped) item Created pull-request: https://github.com/jenkinsci/matrix-combinations-plugin/pull/13 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-36829) Test results not found, incorrect URL used
Title: Message Title Keith Zantow resolved as Fixed Jenkins / JENKINS-36829 Test results not found, incorrect URL used Change By: Keith Zantow 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-36892) Expose DSL.NamedArgsAndClosure and related methods
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-36892 Expose DSL.NamedArgsAndClosure and related methods Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Jul/22 11:00 PM Priority: Major Reporter: Andrew Bayer I'm working on something that requires doing some introspection on Pipeline script before execution time, and it'd be awfully handy to be able to use the NamedArgsAndClosure-related tooling in DSL from workflow-cps (and the Step lookup in invokeMethod too, but that's not that much code anyway), rather than homebrewing my own argument introspection to match it. More specifically, I'm looking to be able to look up a Step, inspect its arguments' types and compare them to the Pipeline script code I'm working with, so I can verify any missing required arguments, invalid argument types, etc. If there's an existing way to do this, great! But if not, exposing NamedArgsAndClosure (and the parseArgs method in particular) would make doing pre-execution validation of Pipeline code dramatically easier. Add Comment
[JIRA] (JENKINS-35157) Allow conditional build step to be used in promotion process
Title: Message Title Michael Fowler commented on JENKINS-35157 Re: Allow conditional build step to be used in promotion process I'm using the Promoted Builds 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-21056) Ability to separate build build history of parameterized projects
Title: Message Title Gustavo Garcia commented on JENKINS-21056 Re: Ability to separate build build history of parameterized projects I agree this is a very interesting feature. It would reduce a lot job duplication and will make it easier to maintain our pipelines. 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-36231) "House of pain" Log should not "jump around" as it is tailing
Title: Message Title Thorsten Scherler commented on JENKINS-36231 Re: "House of pain" Log should not "jump around" as it is tailing add more videos to https://github.com/jenkinsci/blueocean-plugin/pull/370 with different scenarios 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-36231) "House of pain" Log should not "jump around" as it is tailing
Title: Message Title Thorsten Scherler edited a comment on JENKINS-36231 Re: "House of pain" Log should not "jump around" as it is tailing add more videos to https://github.com/jenkinsci/blueocean-plugin/pull/370 with different scenarioswhich one do you prefer? 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-36231) "House of pain" Log should not "jump around" as it is tailing
Title: Message Title
Thorsten Scherler updated an issue
Jenkins / JENKINS-36231
"House of pain" Log should not "jump around" as it is tailing
Change By:
Thorsten Scherler
Comment:
pipelineJenkinsfilenode {stage 'deploy'sh '''#!/bin/bash -lecho $0COUNTER=0while [ $COUNTER -lt 5000 ]; do echo The counter is $COUNTER let COUNTER=COUNTER+1donesleep 2;'''stage 'end'sh '''#!/bin/bash -lecho $0COUNTER=0while [ $COUNTER -lt 5000 ]; do echo The counter is $COUNTER let COUNTER=COUNTER+1donesleep 2;'''}
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-36231) "House of pain" Log should not "jump around" as it is tailing
Title: Message Title
Thorsten Scherler commented on JENKINS-36231
Re: "House of pain" Log should not "jump around" as it is tailing
pipeline Jenkinsfile node { stage 'deploy' sh '''#!/bin/bash -l echo $0 COUNTER=0 while [ $COUNTER -lt 5000 ]; do echo The counter is $COUNTER let COUNTER=COUNTER+1 done sleep 2; ''' stage 'end' sh '''#!/bin/bash -l echo $0 COUNTER=0 while [ $COUNTER -lt 5000 ]; do echo The counter is $COUNTER let COUNTER=COUNTER+1 done sleep 2; ''' }
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-34882) Jenkins update center does not failover to other update sites if the default one is offline
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-34882 Jenkins update center does not failover to other update sites if the default one is offline Change By: Keith Zantow Assignee: Keith Zantow 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-34882) Jenkins update center does not failover to other update sites if the default one is offline
Title: Message Title Keith Zantow started work on JENKINS-34882 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-34882) Jenkins update center does not failover to other update sites if the default one is offline
Title: Message Title Keith Zantow commented on JENKINS-34882 Re: Jenkins update center does not failover to other update sites if the default one is offline Oleg Nenashev - if we fix the issue that the 'default' update site is hardcoded in the install wizard, do you think this could be considered a sufficient fix for this issue? E.g., it will ping the local update site instead of the unavailable 'default' for the connectivity test and default location to install plugins from. I hope this fix can be eligible for back-port into the 2.7 line. 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-15118) Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project
Title: Message Title Henry Yei commented on JENKINS-15118 Re: Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project This failure below does NOT fail the build like it should and ended up only failing when submitting to the app store. [ContentBlocker] $ /usr/bin/agvtool new-version -all 377 Setting version of project XProject to: 377. Also setting CFBundleVersion key (assuming it exists) Updating CFBundleVersion in Info.plist(s)... Cannot find "XProject.xcodeproj/../ INFOPLIST_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-36231) "House of pain" Log should not "jump around" as it is tailing
Title: Message Title Thorsten Scherler edited a comment on JENKINS-36231 Re: "House of pain" Log should not "jump around" as it is tailing We can further play with const INITIAL_RENDER_CHUNK_SIZE = 100;const INITIAL_RENDER_DELAY = 300;const RENDER_CHUNK_SIZE = 500; -> reducing this would make slower in scrolling down, since we would stop earlier to go downconst RERENDER_DELAY = 17; ATM we render every 17 milliseconds 500 lines. Playing with this numbers gives us some margin. 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-36231) "House of pain" Log should not "jump around" as it is tailing
Title: Message Title Thorsten Scherler commented on JENKINS-36231 Re: "House of pain" Log should not "jump around" as it is tailing We can further play with const INITIAL_RENDER_CHUNK_SIZE = 100; const INITIAL_RENDER_DELAY = 300; const RENDER_CHUNK_SIZE = 500; -> reducing this would make slower in scrolling down, since we would stop earlier to go down const RERENDER_DELAY = 17; 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-36231) "House of pain" Log should not "jump around" as it is tailing
Title: Message Title Thorsten Scherler commented on JENKINS-36231 Re: "House of pain" Log should not "jump around" as it is tailing https://github.com/jenkinsci/blueocean-plugin/pull/370 You find BEFORE: https://youtu.be/KOe5VqWeCZo AFTER: https://youtu.be/mkBaPrNNjys 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-36690) New Item doesn't show anything
Title: Message Title Nicolas de Marqué resolved as Fixed Jenkins / JENKINS-36690 New Item doesn't show anything Change By: Nicolas de Marqué 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-36690) New Item doesn't show anything
Title: Message Title Nicolas de Marqué started work on JENKINS-36690 Change By: Nicolas de Marqué 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-36690) New Item doesn't show anything
Title: Message Title Nicolas de Marqué stopped work on JENKINS-36690 Change By: Nicolas de Marqué Status: In Progress 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-36690) New Item doesn't show anything
Title: Message Title Oleg Nenashev commented on JENKINS-36690 Re: New Item doesn't show anything https://github.com/jenkinsci/jenkins/pull/2468 likely fixes this problem. CC Manuel Recena Soto 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-36891) New release of kubernetes plugin
Title: Message Title Ben Parees created an issue Jenkins / JENKINS-36891 New release of kubernetes plugin Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Jul/22 8:55 PM Priority: Minor Reporter: Ben Parees Can you do a new release of the plugin? in particular i'd like to take advantage of the ability to configure the pod service account that was added: https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/PodTemplate/config.jelly#L79-L81 Add Comment
[JIRA] (JENKINS-36891) New release of kubernetes plugin
Title: Message Title Ben Parees updated an issue Jenkins / JENKINS-36891 New release of kubernetes plugin Change By: Ben Parees Issue Type: New Feature Task 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-36856) Cannot delete Bitbucket Team job unless there is a repo already
Title: Message Title Isaac Cohen closed an issue as Cannot Reproduce This was already fixed in the latest version of cloudbees-folder (v5.5). Once the plugins are updated it works. Jenkins / JENKINS-36856 Cannot delete Bitbucket Team job unless there is a repo already Change By: Isaac Cohen Status: Open Closed Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-36317) Logs within a stage should be flattened
Title: Message Title daryl piffre commented on JENKINS-36317 Re: Logs within a stage should be flattened I would be interested in this, or at least to make it an option ! 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-36890) PR's do not meet the criteria when Include Branches is set
Title: Message Title Isaac Cohen created an issue Jenkins / JENKINS-36890 PR's do not meet the criteria when Include Branches is set Issue Type: Bug Assignee: Antonio Muñiz Attachments: Screen Shot 2016-07-22 at 4.13.35 PM.png, Screen Shot 2016-07-22 at 4.13.59 PM.png Components: bitbucket-branch-source-plugin Created: 2016/Jul/22 8:16 PM Environment: Jenkins 1.642 bitbucket-branch-source-plugin 1.5 scm-api 1.2 Priority: Major Reporter: Isaac Cohen When a multibranch pipeline is created with Bitbucket, if the Include Branches Filter is changed from the default * to a different value, PR's are not being built. My understanding is that PR's should be built regardless of the branch filters specified. Steps to reproduce: Create a new Multibranch Pipeline Choose Bibucket as the Source and specify the repo info as well as an Include Branches For example I specified: "master* PR*" to build the master + PR branches but nothing else Create a PR in the Bitbucket run the Branch Indexing Jenkins will not pick up the PR
[JIRA] (JENKINS-36889) Extreme docker plugin logging cannot be turned off
Title: Message Title John Mellor updated an issue Jenkins / JENKINS-36889 Extreme docker plugin logging cannot be turned off Change By: John Mellor Summary: Extreme docker plugin loggin logging cannot be turned off 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-36889) Extreme docker plugin loggin cannot be turned off
Title: Message Title John Mellor updated an issue Jenkins / JENKINS-36889 Extreme docker plugin loggin cannot be turned off Change By: John Mellor When building a docker image from a Dockerfile to run the build in, extreme docker build logging cannot be turned off.This issue makes the first 20 pages of the build log essentially useless.Filtering it or adding the -q flag would resolve this.E.g. from a typical build log with verbose logging flag not enabled :10:51:06 $ docker build --file /home/esadmin/build/Dockerfile.precise /home/esadmin/build10:51:06 Sending build context to Docker daemon 557.1 kBSending build context to Docker daemon 1.114 MBSending build context to Docker daemon 1.671 MBSending build context to Docker daemon 2.228 MBSending build context to Docker daemon 2.785 MBSending build context to Docker daemon 3.342 MBSending build context to Docker daemon 3.899 MBSending build context to Docker daemon 4.456 MBSending build context to Docker daemon 5.014 MBSending build context to Docker daemon 5.571 MBSending build context to Docker daemon 6.128 MBSending build context to Docker daemon 6.685 MBSending build context to Docker daemon 7.242 MBSending build context to Docker daemon 7.799 MBSending build context to Docker daemon 8.356 MBSending build context to Docker daemon 8.913 MBSending build context to Docker daemon 9.47 MBSending build context to Docker daemon 10.03 MBSending build context to Docker daemon 10.58 MBSending build context to Docker daemon 11.14 MBSending build context to Docker daemon 11.7 MB. . . (for 20 pages) Add Comment
[JIRA] (JENKINS-36889) Extreme docker plugin loggin cannot be turned off
Title: Message Title John Mellor updated an issue Jenkins / JENKINS-36889 Extreme docker plugin loggin cannot be turned off Change By: John Mellor Summary: Extreme docker plugin loggin cannot ge be turned off 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-36889) Extreme docker plugin loggin cannot ge turned off
Title: Message Title John Mellor created an issue Jenkins / JENKINS-36889 Extreme docker plugin loggin cannot ge turned off Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 2016/Jul/22 8:01 PM Environment: Jenkins 1.656, Ubuntu Linux Labels: user-experience plugins Priority: Minor Reporter: John Mellor When building a docker image from a Dockerfile to run the build in, extreme docker build logging cannot be turned off. This issue makes the first 20 pages of the build log essentially useless. Filtering it or adding the -q flag would resolve this. E.g. from a typical build log: 10:51:06 $ docker build --file /home/esadmin/build/Dockerfile.precise /home/esadmin/build 10:51:06 Sending build context to Docker daemon 557.1 kB Sending build context to Docker daemon 1.114 MB Sending build context to Docker daemon 1.671 MB Sending build context to Docker daemon 2.228 MB Sending build context to Docker daemon 2.785 MB Sending build context to Docker daemon 3.342 MB Sending build context to Docker daemon 3.899 MB Sending build context to Docker daemon 4.456 MB Sending build context to Docker daemon 5.014 MB Sending build context to Docker daemon 5.571 MB Sending build context to Docker daemon 6.128 MB Sending build context to Docker daemon 6.685 MB Sending build context to Docker daemon 7.242 MB Sending build context to Docker daemon 7.799 MB Sending build context to Docker daemon 8.356 MB Sending build context to Docker daemon 8.913 MB Sending build context to Docker daemon 9.47 MB Sending build context to Docker daemon
[JIRA] (JENKINS-36746) Jenkins 2.7.1 for debian-stable install fails: Size mismatch
Title: Message Title R. Tyler Croy closed an issue as Fixed No problem, I know how frustrating problems like this can be, sometimes it seems like everything breaks at the same time. With our partnership with Azure we're going to be migrating from this mirrored setup to a direct CDN which will prevent issues like this in the future. Jenkins / JENKINS-36746 Jenkins 2.7.1 for debian-stable install fails: Size mismatch Change By: R. Tyler Croy 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
[JIRA] (JENKINS-29946) Console Output blown up with refreshed line content
Title: Message Title John Mellor commented on JENKINS-29946 Re: Console Output blown up with refreshed line content JENKINS-36886 appears to be a more generic issue with the same cause. 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-36746) Jenkins 2.7.1 for debian-stable install fails: Size mismatch
Title: Message Title Elwin Andriol commented on JENKINS-36746 Re: Jenkins 2.7.1 for debian-stable install fails: Size mismatch I have just tried several new installs from The Netherlands and they now all appear to work. For the ones that did not appear to work yesterday, I may have only myself to blame for. It turns out that an apt-proxy server that I disabled/bypassed when this problem first appeared, got turned on and might have been serving the outdated packages (at least yesterday), while they no longer exist on any mirrors. My sincere apologies for this mistake on my end. 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-36888) Move non-JDL styles out of JDL
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36888 Move non-JDL styles out of JDL Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Jul/22 7:44 PM Labels: technical-debt Priority: Minor Reporter: James Dumay There are a few here that should not exist - like the pipeline result - that need to be moved into blueocean (including their story books) Add Comment
[JIRA] (JENKINS-36887) Default JDL full page dialog style
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36887 Default JDL full page dialog style Issue Type: Task Assignee: Unassigned Attachments: Detail modal.png Components: blueocean-plugin Created: 2016/Jul/22 7:41 PM Priority: Minor Reporter: James Dumay In Scope default header should be a min of 80px high default header has a size 18 header text Add Comment
[JIRA] (JENKINS-36886) Terminal escape sequences being shown
Title: Message Title John Mellor commented on JENKINS-36886 Re: Terminal escape sequences being shown A specific problem resulting from this more generic 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-36886) Terminal escape sequences being shown
Title: Message Title John Mellor created an issue Jenkins / JENKINS-36886 Terminal escape sequences being shown Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 2016/Jul/22 7:29 PM Environment: Ubuntu Linux, Jenkins 1.656, output from Robot, pip, many others. Labels: regression user-experience plugins Priority: Minor Reporter: John Mellor ANSI escape sequences in jobs run directly on a Jenkins slave are either not present or stripped out. These escape sequences are not stripped when running in a docker image being managed by this plugin. This makes dockerized build output parsing different, and unxexpectedly tricky for postbuild actions, and in many cases makes the output much noisier than necessary. e.g: a job that does a simple "ls --color=auto" can be easily shown in a docker machine to have color escapes present in the log, but not present in a non-docker build. Doing the same action on a docker image and on a real machine, we can see that the output in colorized in both cases, narrowing the issue down to a problem in the Jenkins plugin.
[JIRA] (JENKINS-36885) AVD not being created
Title: Message Title Arie Miller created an issue Jenkins / JENKINS-36885 AVD not being created Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 2016/Jul/22 7:27 PM Priority: Major Reporter: Arie Miller [android] Using Android SDK: C:\Users\\AppData\Local\Android\sdk [android] Creating Android AVD: C:\Users\\.android\avd\hudson_en-US_160_WVGA_android-23_armeabi_jenkins.avd [android] C:\Users\\AppData\Local\Android\sdk/tools/android.bat create avd -f -a -c 32M -s WVGA800 -n hudson_en-US_160_WVGA_android-23_armeabi_jenkins -t android-23 --abi armeabi [android] Could not create Android emulator: Failed to parse AVD config file Finished: NOT_BUILT It seems the first step where it's supposed to be creating avd files doesn't actually make anything since that directory only contains avd that I've made in Android Studio. Add Comment
[JIRA] (JENKINS-36481) Remove clutter from BlueOceanUI
Title: Message Title Vivek Pandey commented on JENKINS-36481 Re: Remove clutter from BlueOceanUI Separate ticket opened to integrate rollbar, https://issues.jenkins-ci.org/browse/JENKINS-36884 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-36884) Add Rollbar support
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-36884 Add Rollbar support Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Jul/22 7:14 PM Priority: Minor Reporter: Vivek Pandey We should avoid putting such tools in core modules such as blueocean-web, blueocean-rest or blueocean-commons, It should be done in a separate plugin. Stretch goal could be to load such tools via a JS extension defined somewhere in blueocean-dashboard as there may be need to load such tools before everything else. Add Comment
[JIRA] (JENKINS-36836) Git path polling ignores do not work in Pipeline jobs
Title: Message Title mcrooney commented on JENKINS-36836 Re: Git path polling ignores do not work in Pipeline jobs Seeing this as well on a normal pipeline job, so I don't believe it is specific to multibranch ones. Perhaps the issue has something to do with the way workspaces are handled for Pipeline jobs? I posted about it here: https://groups.google.com/forum/#!msg/jenkinsci-users/wNIMGhJ76rA/HddRoHW-CAAJ 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-36361) StackOverflowError in UpdateSite$Plugin.isNeededDependenciesCompatibleWithInstalledVersion
Title: Message Title Sujay Paranjape commented on JENKINS-36361 Re: StackOverflowError in UpdateSite$Plugin.isNeededDependenciesCompatibleWithInstalledVersion Thank you all for the pointers. I was able to workaround this issue by updating subversion using a downloaded hpi 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-36836) Git path polling ignores do not work in Pipeline jobs
Title: Message Title mcrooney updated an issue Jenkins / JENKINS-36836 Git path polling ignores do not work in Pipeline jobs Change By: mcrooney Summary: Git path polling ignores do not work in Multibranch Pipeline job jobs 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-36481) Remove clutter from BlueOceanUI
Title: Message Title Vivek Pandey started work on JENKINS-36481 Change By: Vivek Pandey 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-36256) "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically
Title: Message Title Daniel Possamai commented on JENKINS-36256 Re: "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically Installing Plugins/Upgrades Preparation Checking internet connectivity Checking update center connectivity Success jenkins.war Failure - hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/war/2.14/jenkins.war (redirected to: http://ftp-chi.osuosl.org/pub/jenkins/war/2.14/jenkins.war) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1153) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1650) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketTimeoutException: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1105) ... 6 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source) at sun.net.www.http.HttpClient.parseHTTP(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown Source) at java.net.URLConnection.getHeaderFieldLong(Unknown Source) at java.net.URLConnection.getContentLengthLong(Unknown Source) at java.net.URLConnection.getContentLength(Unknown Source) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1104) ... 6 more Add
[JIRA] (JENKINS-36746) Jenkins 2.7.1 for debian-stable install fails: Size mismatch
Title: Message Title R. Tyler Croy commented on JENKINS-36746 Re: Jenkins 2.7.1 for debian-stable install fails: Size mismatch Elwin Andriol the mirrors in the netherlands and serbia were the ones that were so out of date that I disabled them a few days ago (see also our mirrors status page) Since last night I have been provisioning, and destroying, new Jenkins masters on EC2 and I haven't yet seen any issues. This is mostly in us-west-2 so I will only be hitting the US mirrors however. Unfortunately since the mirrors are pull-based and operated voluntarily the best I can do is identify mirrors which have not pulled updates properly and disable them from our mirror indexing service. 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-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Richard Boyer commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. Its not possible to blend them without multiple inheritance. The timestamp plugin works via an EnvironmentContributor which is distinct from SCM: https://github.com/jenkinsci/build-timestamp-plugin/blob/master/src/main/java/com/orctom/jenkins/plugin/buildtimestamp/BuildTimestampEnvironmentContributor.java I'm a Jenkins plugin newbie, so this is pushing the limits of what I can reason about effectively. Especially with this new pipeline layer on top. 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-36811) Cannot update JIRA custom field through jira-ext plugin
Title: Message Title Dan Alvizu commented on JENKINS-36811 Re: Cannot update JIRA custom field through jira-ext plugin Is the field you are updating a multi-select field? If so I don't think that's supported yet in jira-ext plugin. There's a way to select it in the svc but this is not exposed in the UI, it will need to be implemented: https://github.com/jenkinsci/jira-ext-plugin/commit/5169f766c3300a37832f6c3db63d2f4fc1069602 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-36882) Gitlab integration - Double job execution
Title: Message Title Facu Mateo edited a comment on JENKINS-36882 Re: Gitlab integration - Double job execution I have my environment all setup. The job is simple:1 - It fetch data from giblab.2 - It build a maven projectI have disabled every option in my configuration. The only 2 plugins currently activated that could couse cause this problem are git-plugin and gitlabplugin.If you have some ideas to try I will test them. 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Possibly also related to: JENKINS-33484 - P4 sync on triggered 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-36882) Gitlab integration - Double job execution
Title: Message Title Facu Mateo commented on JENKINS-36882 Re: Gitlab integration - Double job execution I have my environment all setup. The job is simple: 1 - It fetch data from giblab. 2 - It build a maven project I have disabled every option in my configuration. The only 2 plugins currently activated that could couse this problem are git-plugin and gitlabplugin. If you have some ideas to try I will test them. 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-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Jason Davis commented on JENKINS-34924 Re: p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace After more testing with 1.4.3 I was able to more readily track down the problem I was experiencing. This issue still sounds like it's related, but it's not seemingly the same as described here, so I logged a new issue for tracking there: JENKINS-36883 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-34815) NodeJS plugin unable to install global NPM packages
Title: Message Title Davi Koscianski Vidal edited a comment on JENKINS-34815 Re: NodeJS plugin unable to install global NPM packages No [~signus]. I cloned nodejs-plugin repository, built the plugin using maven and uploaded the resulting hpi. The built resulted in nodejs-plugin version 0.3.With this up-to-date version I was able to install NodeJS 6.3.0 + global packages. Edit: sorry for my poor English. 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis created an issue Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Jul/22 6:37 PM Priority: Major Reporter: Jason Davis I’ve found that the latest versions of files that are mapped in a workspace and also in an “Exclude changes from Depot path” polling filter, are not being synced at build time. Here’s the scenario. I’m currently set Jobs to use Manual workspaces set in Jenkins, to do a Force Sync, and have the “Populate have list” flag set. The Workspace includes an example path: PathA/… PathB/… Also configured with the Polling Filter - “Exclude changes from Depot path” is set to a path under PathB (actually in my test it was the same path). What happens: A check-in under Path A is recognized from polling and triggers a build which has a quiet period associated with it. During the quiet period, one or more check-ins occur under Path B. These files naturally have a higher changelist number than what triggered the build. When the quiet period expires, the build starts and syncs Path A’s files to latest available changelist for that Path, whatever it may be – All is good! For the files in Path B, however, the build syncs to the changelist number from Path A that triggered the build, NOT the latest available changelist. That causes the files under Path B, to be sync’ed to non-latest state. Again, if check-ins occur in the quiet period under Path A – the latest versions of those files ARE being synced.
[JIRA] (JENKINS-34815) NodeJS plugin unable to install global NPM packages
Title: Message Title Davi Koscianski Vidal commented on JENKINS-34815 Re: NodeJS plugin unable to install global NPM packages No Matthew Sexton. I cloned nodejs-plugin repository, built the plugin using maven and uploaded the resulting hpi. The built resulted in nodejs-plugin version 0.3. With this up-to-date version I was able to install NodeJS 6.3.0 + global packages. 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-36882) Gitlab integration - Double job execution
Title: Message Title Mark Waite commented on JENKINS-36882 Re: Gitlab integration - Double job execution I see no polling schedule in the job definition. I don't plan to spend significant time investigating this, since I don't see the problem in my test environments. I'll need to rely on you to identify what settings cause the problem to appear, and what settings cause it to disappear. 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-36882) Gitlab integration - Double job execution
Title: Message Title Facu Mateo updated an issue Jenkins / JENKINS-36882 Gitlab integration - Double job execution Change By: Facu Mateo Attachment: config.xml 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-36882) Gitlab integration - Double job execution
Title: Message Title Facu Mateo commented on JENKINS-36882 Re: Gitlab integration - Double job execution I uploaded my job config.xml 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-36881) Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER
Title: Message Title Oleg Nenashev commented on JENKINS-36881 Re: Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER I'm not sure it's related to Promoted Builds plugin. Maybe artifactory plugin? Please provide your job configuration 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-34678) Emulator executable value is ignored for snapshot listing
Title: Message Title Karol Wrotniak updated an issue Jenkins / JENKINS-34678 Emulator executable value is ignored for snapshot listing Proposed fix: https://github.com/jenkinsci/android-emulator-plugin/pull/61 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-36882) Gitlab integration - Double job execution
Title: Message Title Facu Mateo commented on JENKINS-36882 Re: Gitlab integration - Double job execution Yes, I know about some bugs in git-plugin that have the same effect and could be related. I will upload my job definition soon 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-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Mark Waite commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. Richard Boyer nice find that the build timestamp plugin has the necessary technique in it. Are you able to review the source code of the build timestamper plugin and submit a comparable pull request for the git 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-36882) Gitlab integration - Double job execution
Title: Message Title Mark Waite commented on JENKINS-36882 Re: Gitlab integration - Double job execution You'll need to provide your job definition to confirm that you truly are not polling for SCM changes. The message seems to indicate that something is causing a poll for SCM changes, and that poll detects a 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.
[JIRA] (JENKINS-36882) Gitlab integration - Double job execution
Title: Message Title Facu Mateo updated an issue Jenkins / JENKINS-36882 Gitlab integration - Double job execution Change By: Facu Mateo I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "gitlabSourceBranch" is not set. This shows me that this build wasn't started by the gitlab plugin."Poll SCM" trigger is disabled in my job configuration. In Jenkins log I see there is only one push notification from Gitlab which is correct.I am expecting one push -> one build. 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
[JIRA] (JENKINS-36882) Gitlab integration - Double job execution
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-36882 Gitlab integration - Double job execution 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-36882) Gitlab integration - Double job execution
Title: Message Title Facu Mateo updated an issue Jenkins / JENKINS-36882 Gitlab integration - Double job execution Change By: Facu Mateo I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "gitlabSourceBranch" is not set. This shows me that this build wasn't started by the gitlab plugin."Poll SCM" trigger is disabled in my job configuration. I am expecting one push -> one build. 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
[JIRA] (JENKINS-36882) Gitlab integration - Double job execution
Title: Message Title
Facu Mateo updated an issue
Jenkins / JENKINS-36882
Gitlab integration - Double job execution
Change By:
Facu Mateo
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable " ${ gitlabSourceBranch } " is not set. This shows me that this build wasn't started by the gitlab plugin."Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build.
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
[JIRA] (JENKINS-36882) Gitlab integration - Double job execution
Title: Message Title
Facu Mateo updated an issue
Jenkins / JENKINS-36882
Gitlab integration - Double job execution
Change By:
Facu Mateo
I 'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "${gitlabSourceBranch}" is not set. This shows me that this build wasn't started by the gitlab plugin."Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build.
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
[JIRA] (JENKINS-36882) Gitlab integration - Double job execution
Title: Message Title
Facu Mateo updated an issue
Jenkins / JENKINS-36882
Gitlab integration - Double job execution
Change By:
Facu Mateo
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "${gitlabSourceBranch}" is not set. This shows me that this build wasn't started by the gitlab plugin."Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build.
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
[JIRA] (JENKINS-36882) Gitlab integration - Double job execution
Title: Message Title
Facu Mateo created an issue
Jenkins / JENKINS-36882
Gitlab integration - Double job execution
Issue Type:
Bug
Assignee:
Mark Waite
Attachments:
Sin título.png
Components:
git-client-plugin, git-plugin, gitlab-plugin
Created:
2016/Jul/22 5:57 PM
Environment:
Jenkins v2.14 Gitlab v8.5 Gilab-plugin v1.3.0 git-client-plugin v1.19.7 git-plugin 2.5.2
Labels:
gitlab git
Priority:
Critical
Reporter:
Facu Mateo
I working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "$ {gitlabSourceBranch} " is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build.
[JIRA] (JENKINS-34815) NodeJS plugin unable to install global NPM packages
Title: Message Title Matthew Sexton commented on JENKINS-34815 Re: NodeJS plugin unable to install global NPM packages Davi Koscianski Vidal - By 0.3 you mean v6.3.0? I will test again with NodeJS 6.3.0 now that I am on Jenkins 2.14. 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-36881) Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER
Title: Message Title
SUNIJ khatri created an issue
Jenkins / JENKINS-36881
Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
promoted-builds-plugin
Created:
2016/Jul/22 5:55 PM
Priority:
Minor
Reporter:
SUNIJ khatri
We have Jobs which are under nested folder in Jenkins, and the build runs successfully and the build artifacts are published to Artifactory and when we try to run the 'Artifactory Release Promotion", we get error: Promoting build Performing dry run promotion (no changes are made during dry run) ... ERROR: Promotion failed during dry run (no change in Artifactory was done): HTTP/1.1 404 Not Found { "errors" : [ { "status" : 404, "message" : "Cannot find builds by the name 'Athena :: athena-waf-alerter-tag-build' and the number '6'." } ] } Completed After looking into this issue found out that Artifactory Build info does not have the correct build URL . The URL shows: https://JENKINS.vrsn.com/jenkins/job/Athena/job/waf-alerter-tag-build/6/ Which should have been https://JENKINS.vrsn.com/jenkins/view/Athena/job/Athena/job/athena-waf-alerter-tag-build/ We have workaround the issue but wondering if there is a quick way to fix this.
[JIRA] (JENKINS-36131) "Show all" link required anywhere a log is displayed
Title: Message Title Thorsten Scherler started work on JENKINS-36131 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-36169) Log does not match final style
Title: Message Title Thorsten Scherler started work on JENKINS-36169 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-35157) Allow conditional build step to be used in promotion process
Title: Message Title Oleg Nenashev commented on JENKINS-35157 Re: Allow conditional build step to be used in promotion process Michael Fowler It would be useful if somebody answers to Dominik's question above. Regarding the Promoted Builds plugin, it could be done 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-34648) Cannot create new items after upgrade to 2.1
Title: Message Title Manuel Recena Soto commented on JENKINS-34648 Re: Cannot create new items after upgrade to 2.1 A fix was pushed. 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-35719) Log should never horizontally scroll
Title: Message Title Thorsten Scherler resolved as Fixed Jenkins / JENKINS-35719 Log should never horizontally scroll Change By: Thorsten Scherler 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-36853) pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Title: Message Title
David Walter updated an issue
Jenkins / JENKINS-36853
pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Change By:
David Walter
Calling cancel on job step waiting on input terminates normally, both curl POST or hubot http.postCalling proceedEmpty fails with exception: input/ApproveDeployment/proceedEmpty.jenkinsfile has:timeout(time: 7, unit: 'DAYS'){ input id: 'ApproveDeployment', message: 'Waiting for response. Deploy to environment or cancel / abort' }Using curl POST or hubot POST both fail with the servlet exception .Stack tracejavax.servlet.ServletException: java.lang.IndexOutOfBoundsException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876...Even if data is added to the post it continues to fail.
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
[JIRA] (JENKINS-36853) pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Title: Message Title
David Walter updated an issue
Jenkins / JENKINS-36853
pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Change By:
David Walter
Calling cancel on job step waiting on input terminates normally, both curl POST or hubot http.postCalling proceedEmpty fails with exception: input/ApproveDeployment/proceedEmpty.jenkinsfile has: timeout(time: 7, unit: 'DAYS'){ input id: 'ApproveDeployment', message: 'Waiting for response. Deploy to environment or cancel / abort' } Using curl POST or hubot POST both fail. {{ Stack tracejavax.servlet.ServletException: java.lang.IndexOutOfBoundsException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876 }} ... Even if data is added to the post it continues to fail.
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
[JIRA] (JENKINS-36853) pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Title: Message Title
David Walter updated an issue
Jenkins / JENKINS-36853
pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Change By:
David Walter
Calling cancel on job step waiting on input terminates normally, both curl POST or hubot http.postCalling proceedEmpty fails with exception: input/ApproveDeployment/proceedEmpty.jenkinsfile has:< pre code >timeout(time: 7, unit: 'DAYS'){ input id: 'ApproveDeployment', message: 'Waiting for response. Deploy to environment or cancel / abort' } pre code >Using curl POST or hubot POST both fail.{{Stack tracejavax.servlet.ServletException: java.lang.IndexOutOfBoundsException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876}}Even if data is added to the post it continues to fail.
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
[JIRA] (JENKINS-36853) pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Title: Message Title
David Walter updated an issue
Jenkins / JENKINS-36853
pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Change By:
David Walter
Calling cancel on job step waiting on input terminates normally, both curl POST or hubot http.postCalling proceedEmpty fails with exception: input/ApproveDeployment/proceedEmpty.jenkinsfile has: {{ bq. timeout(time: 7, unit: 'DAYS'){ bq. input id: 'ApproveDeployment', message: 'Waiting for response. Deploy to environment or cancel / abort' bq. } }} Using curl POST or hubot POST both fail.{{Stack tracejavax.servlet.ServletException: java.lang.IndexOutOfBoundsException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876}}Even if data is added to the post it continues to fail.
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
[JIRA] (JENKINS-36853) pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Title: Message Title
David Walter updated an issue
Jenkins / JENKINS-36853
pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Change By:
David Walter
Calling cancel on job step waiting on input terminates normally, both curl POST or hubot http.postCalling proceedEmpty fails with exception: input/ApproveDeployment/proceedEmpty.jenkinsfile has: {{ timeout(time: 7, unit: 'DAYS'){ input id: 'ApproveDeployment', message: 'Waiting for response. Deploy to environment or cancel / abort' } }} Using curl POST or hubot POST both fail.{{Stack tracejavax.servlet.ServletException: java.lang.IndexOutOfBoundsException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876}}Even if data is added to the post it continues to fail.
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
