[JIRA] (JENKINS-37190) Unauthenticated request to GitHub trigger rate limits when adding organization
Title: Message Title Michael Neale commented on JENKINS-37190 Re: Unauthenticated request to GitHub trigger rate limits when adding organization This looks like it is due to the name of the item being created being the github org (that was a recent change, but likely the real bug). Thus if you put in a name for an org you don't own, that could result in rate limits (would that make sense?) 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-37932) Error if no "agent" specified
Title: Message Title Patrick Wolf commented on JENKINS-37932 Re: Error if no "agent" specified Yes, just to be clear I meant I like agent none for what it currently does - forces manual configuration. I agree that a default of any is the best user experience. 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-37932) Error if no "agent" specified
Title: Message Title Michael Neale edited a comment on JENKINS-37932 Re: Error if no "agent" specified [~hrmpw] the "any" was suggested by me but Andrew didn't like another reserved word (they have a way of biting). Also, there is space for a "default" if people can agree what it is (and you your suggestion that it is any node I still think is a good one). A default of "none" would be probably a bad experience. 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-37932) Error if no "agent" specified
Title: Message Title Michael Neale commented on JENKINS-37932 Re: Error if no "agent" specified Patrick Wolf the "any" was suggested by me but Andrew didn't like another reserved word (they have a way of biting). Also, there is space for a "default" if people can agree what it is (and you suggestion that it is any node I still think is a good one). A default of "none" would be probably a bad experience. 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-37932) Error if no "agent" specified
Title: Message Title Patrick Wolf commented on JENKINS-37932 Re: Error if no "agent" specified I like agent none because it is fairly literal. The 'agent' step declares a default for all stages to run in unless otherwise specified. With this context, 'none' states that there is no default and it must be specified on the stage. I can't think of a better way to express that. agent any seems more elegant than agent label:"" but having the "label" keyword there makes it very easy to understand the change needed to run on a specific node. What about agent label:any so it is specific that it will run on any label and the change to a specific label is straightforward. 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-38014) Very bad pipeline syntax error results in blank results screen
Title: Message Title Michael Neale commented on JENKINS-38014 Re: Very bad pipeline syntax error results in blank results screen Thorsten Scherler don't think this is a regression, I just never realised how easy it is to reproduce this. It should fall back to showing the log. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38014) Very bad pipeline syntax error results in blank results screen
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38014 Very bad pipeline syntax error results in blank results screen Change By: Michael Neale Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38014) Very bad pipeline syntax error results in blank results screen
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38014 Very bad pipeline syntax error results in blank results screen Change By: Michael Neale To reproduce: * Create an ordinary pipeline* Put in the text: "fdsfdsafdsafdsafdsa" as the pipeline * Run itOpen results page. You will see a blank screen. Expected behavior: Shows the log (with all its gory errors) and no steps. 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-35408) TECoreException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters
Title: Message Title Luisa Marvin commented on JENKINS-35408 Re: TECoreException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters Long Path Tool can help you to remove blocked files or too long path files. You can easily fix file errors with this software. 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-38012) Pipeline has failed but its only stage is successful
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38012 Pipeline has failed but its only stage is successful Change By: Michael Neale Comment: There seems to be something wrong with pipeline model - this doesn't happen with classic script. Also, I am not seeing pipeline model use block scoped stages (I get a deprecation warning when using it), so 0.2 needs to be released ASAP 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-38014) Very bad pipeline syntax error results in blank results screen
Title: Message Title Michael Neale assigned an issue to Thorsten Scherler Jenkins / JENKINS-38014 Very bad pipeline syntax error results in blank results screen Change By: Michael Neale Assignee: Thorsten Scherler 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-38014) Very bad pipeline syntax error results in blank results screen
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38014 Very bad pipeline syntax error results in blank results screen Change By: Michael Neale Sprint: 1.0-beta-1 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-38014) Very bad pipeline syntax error results in blank results screen
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38014 Very bad pipeline syntax error results in blank results screen Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/07 5:26 AM Priority: Major Reporter: Michael Neale To reproduce: Create an ordinary pipeline Put in the text: "fdsfdsafdsafdsafdsa" Run it Open results page. You will see a blank screen. Expected behavior: Shows the log (with all its gory errors) and no steps. Add Comment
[JIRA] (JENKINS-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Michael Neale edited a comment on JENKINS-38007 Re: 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io If this is the SSE deadlock, it would show up more like: https://issues.jenkins-ci.org/browse/JENKINS- 38007 37921 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-37932) Error if no "agent" specified
Title: Message Title
Michael Neale commented on JENKINS-37932
Re: Error if no "agent" specified
James Dumay more magic is only a last resort. By far the most common case will be "node {...} " so it isnt' a terrible default. "agent none" is when you want to control the nodes (maybe there is a better way to express that).
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33903) github-organization fails to detect new repositories, probably due to pagination
Title: Message Title Patrick Wolf commented on JENKINS-33903 Re: github-organization fails to detect new repositories, probably due to pagination Is this a duplicate of JENKINS-34563 ? 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-37932) Error if no "agent" specified
Title: Message Title James Dumay commented on JENKINS-37932 Re: Error if no "agent" specified Michael Neale what about if we aliased agent:any to agent:""? What is the use case for agent none? Seems obtuse at first glance. 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-38013) Profile and minifi blue ocean loading
Title: Message Title Michael Neale commented on JENKINS-38013 Re: Profile and minifi blue ocean loading Tom FENNELLY just thought I would park this in case you feel the need for speed. 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-38013) Profile and minifi blue ocean loading
Title: Message Title Michael Neale assigned an issue to Tom FENNELLY Jenkins / JENKINS-38013 Profile and minifi blue ocean loading Change By: Michael Neale Assignee: Tom FENNELLY 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-38013) Profile and minifi blue ocean loading
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38013 Profile and minifi blue ocean loading Change By: Michael Neale It is worth investigating the where the load time is for blueocean, and then consider optimising. Minification is a logical third step (although this will bring other challenges).In scope: * Investigate loading/profile loading* Optimise loading* Minification 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-38013) Profile and minifi blue ocean loading
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38013 Profile and minifi blue ocean loading Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/07 5:05 AM Priority: Major Reporter: Michael Neale It is worth investigating the where the load time is for blueocean, and then consider optimising. Minification is a logical third step (although this will bring other challenges). Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38012) Pipeline has failed but its only stage is successful
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-38012 Pipeline has failed but its only stage is successful Change By: James Dumay Assignee: Vivek Pandey 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-38012) Pipeline has failed but its only stage is successful
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38012 Pipeline has failed but its only stage is successful Change By: James Dumay Priority: Minor Blocker 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-37880) Starting, stopping and replaying a run in quick succession does not work
Title: Message Title James Dumay commented on JENKINS-37880 Re: Starting, stopping and replaying a run in quick succession does not work Vivek Pandey yes, all of these cases received a 500. Ivan Meredith / Vivek Pandey it would be nice we could sidestep this stuff for replay. Take the commit Ids from the run that is being replayed, ask Jenkins to build those, etc (allowing it to read the Jenkinsfile again instead of using the previous pipeline state). Probably easier said than 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-37880) Starting, stopping and replaying a run in quick succession does not work
Title: Message Title Vivek Pandey edited a comment on JENKINS-37880 Re: Starting, stopping and replaying a run in quick succession does not work [~jamesdumay] In this case 500 is correct error, no? Its un-replayble - what do you mean, is it 500 error every time you click replay or something else? Might be worth checking with [~imeredith], think he wrote replay functionality in pipeline 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-37880) Starting, stopping and replaying a run in quick succession does not work
Title: Message Title Vivek Pandey commented on JENKINS-37880 Re: Starting, stopping and replaying a run in quick succession does not work James Dumay In this case 500 is correct error, no? Its un-replayble - what do you mean, is it 500 error every time you click replay or something else? Might be worth checking with Ivan Meredith, think he wrote replay functionality in pipeline 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-37880) Starting, stopping and replaying a run in quick succession does not work
Title: Message Title James Dumay commented on JENKINS-37880 Re: Starting, stopping and replaying a run in quick succession does not work Michael Neale replay seems to only work if the flow graph was persisted correctly to disk. If it is not there (in the case of there being no flow nodes in the last example) then it fails. 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-37880) Starting, stopping and replaying a run in quick succession does not work
Title: Message Title Michael Neale commented on JENKINS-37880 Re: Starting, stopping and replaying a run in quick succession does not work So perhaps not trivial? 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-38012) Pipeline has failed but its only stage is successful
Title: Message Title Michael Neale commented on JENKINS-38012 Re: Pipeline has failed but its only stage is successful There seems to be something wrong with pipeline model - this doesn't happen with classic script. Also, I am not seeing pipeline model use block scoped stages (I get a deprecation warning when using it), so 0.2 needs to be released ASAP 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-37932) Error if no "agent" specified
Title: Message Title
Michael Neale edited a comment on JENKINS-37932
Re: Error if no "agent" specified
agent none is "I'll manage my own" - as documented . (perhaps that needs to be clearer or repeated) "I'll run anywhere" currently is: agent label:''this proposal is to make the default. So if you have: {noformat}pipeline { stages { stage('build') { sh 'echo 42' } }}{noformat}It will work as if it had "agent label:''" in there.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title
Michael Neale edited a comment on JENKINS-37932
Re: Error if no "agent" specified
no, agent none is "I'll manage my own" - as documented. "I'll run anywhere" currently is: agent label:''this proposal is to make the default. So if you have: {noformat}pipeline { stages { stage('build') { sh 'echo 42' } }}{noformat}It will work as if it had "agent label:''" in there.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title
Michael Neale commented on JENKINS-37932
Re: Error if no "agent" specified
no, agent none is "I'll manage my own" - as documented. "I'll run anywhere" currently is: agent label:'' this proposal is to make the default. So if you have:
pipeline {
stages {
stage('build') {
sh 'echo 42'
}
}
}
It will work as if it had "agent label:''" in there.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37866) The plugin spams Github API
Title: Message Title Michael Neale closed an issue as Duplicate I think this is really saying the same thing (there may be optimisations in org folder, but they are minor compared to the multibranch issues) Jenkins / JENKINS-37866 The plugin spams Github API Change By: Michael Neale Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-34600) Improve the performance of scheduling a build
Title: Message Title Michael Neale commented on JENKINS-34600 Re: Improve the performance of scheduling a build Or webhooks have to support both auth and non auth mode (and in the case of non auth, then you can't trust and have to fetch). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Michael Neale commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Dominic Scheirlinck Jesse Glick it seems that if we can assume webhook payloads are authenticated, then it is possible to trust them. If not, then it is a bit philosphical. At the moment they aren't required to be trusted right? And not trusting them means you can only use them as a trigger to go fetch data? 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-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Michael Neale commented on JENKINS-38007 Re: 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io If this is the SSE deadlock, it would show up more like: https://issues.jenkins-ci.org/browse/JENKINS-38007 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-38011) REGRESSION: modal header is incorrect for multi-branch pipeline
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38011 REGRESSION: modal header is incorrect for multi-branch pipeline Change By: Michael Neale Summary: Regression REGRESSION : modal header is incorrect for multi-branch pipeline 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-38009) Executing step is not expanded when there is a proceeding failing step
Title: Message Title Michael Neale commented on JENKINS-38009 Re: Executing step is not expanded when there is a proceeding failing step this is really weird, I don't think that sequence of "states" was anticipated. It looks bad that there is a "red failure" as part of normal operation, but certainly yes this isn't correct behavior of expanding at least. 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-38011) Regression: modal header is incorrect for multi-branch pipeline
Title: Message Title James Dumay assigned an issue to Thorsten Scherler Jenkins / JENKINS-38011 Regression: modal header is incorrect for multi-branch pipeline Change By: James Dumay Assignee: Thorsten Scherler 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-38011) Regression: modal header is incorrect for multi-branch pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38011 Regression: modal header is incorrect for multi-branch pipeline Change By: James Dumay Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38012) Pipeline has failed but its only stage is successful
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38012 Pipeline has failed but its only stage is successful Change By: James Dumay Summary: Incorrect Pipeline has failed but its only stage state reported is successful 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-38012) Incorrect stage state reported
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-38012
Incorrect stage state reported
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Jenkins Blue Ocean 2016-09-07 13-26-57.png
Components:
blueocean-plugin
Created:
2016/Sep/07 3:38 AM
Priority:
Minor
Reporter:
James Dumay
This pipeline has failed but the stage is reported as successfulJenkinsfile example
pipeline {
agent docker:'java'
stages {
stage ('Build') {
sh 'mvn clean source:jar package'
}
stage ('Browser Tests') {
parallel (
'Firefox': {
sh "echo 'setting up selenium environment'"
sh 'sleep 5000'
},
'Safari': {
sh "echo 'setting up selenium environment'"
sh 'sleep 5000'
},
'Chrome': {
sh "echo 'setting up selenium environment'"
sh 'sleep 3000'
},
'Internet Explorer': {
sh "echo 'setting up selenium environment'"
sh 'sleep 2000'
}
)
}
stage ('Static Analysis') {
sh 'mvn findbugs:findbugs'
}
stage ('Package') {
sh 'mvn source:jar package -Dmaven.test.skip'
}
}
postBuild {
always {
junit '**/target/surefire-reports/TEST-*.xml'
archive '**/target/*.jar'
}
}
}
[JIRA] (JENKINS-38011) Regression: modal header is incorrect for multi-branch pipeline
Title: Message Title James Dumay created an issue Jenkins / JENKINS-38011 Regression: modal header is incorrect for multi-branch pipeline Issue Type: Bug Assignee: Unassigned Attachments: Jenkins Blue Ocean 2016-09-07 13-23-36.png, Jenkins Blue Ocean 2016-09-07 13-23-47.png Components: blueocean-plugin Created: 2016/Sep/07 3:35 AM Priority: Minor Reporter: James Dumay At some point we broke the navigation and naming of the multi-branch Pipeline This Pipeline is called "Jenkins / App Store" If I open a run the name is "Jenkins / master" but should be "Jenkins / App Store / master" Add Comment
[JIRA] (JENKINS-38010) no JMeter files matching have been found
Title: Message Title Allan Haywood created an issue Jenkins / JENKINS-38010 no JMeter files matching have been found Issue Type: Bug Assignee: Andrey Pokhilko Components: performance-plugin Created: 2016/Sep/07 3:22 AM Environment: Ubuntu 14.04.5 LTS Jenkins Version: 2.21 Performance plugin: 2.14 java.runtime.version 1.8.0_101-b13 Priority: Blocker Reporter: Allan Haywood This is the first time I have tried getting the performance plugin working, so it may be operator error. I have a jenkins slave node dedicated to running the performance tests. The jmeter tests are being run, and I see the result files, but when the Jenkins project runs, I get the following error: Performance: no JMeter files matching '/home/jenkins/jmeter_results/*.jtl' have been found. Has the report generated? However, they are clearly on the slave node: ls -la /home/jenkins/jmeter_results/*.jtl rw-rw-r- 1 jenkins jenkins 361 Sep 6 19:35 /home/jenkins/jmeter_results/build.jtl rw-rw-r- 1 jenkins jenkins 1429 Sep 6 19:36 /home/jenkins/jmeter_results/exara_unit_tests.jtl Am I doing something wrong? Is the performance plugin looking for the files on the slave node, or on the master node? Thank you.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title Andrew Bayer commented on JENKINS-37932 Re: Error if no "agent" specified agent none is "I'll manage node blocks myself", not "I can run anywhere". 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-37932) Error if no "agent" specified
Title: Message Title Patrick Wolf commented on JENKINS-37932 Re: Error if no "agent" specified I assumed agent none was equivalent to not having a default node and making it required on the stage. I think there is a difference between not having a default node and having a default node with no label. 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-37932) Error if no "agent" specified
Title: Message Title James Dumay commented on JENKINS-37932 Re: Error if no "agent" specified Patrick Wolf so that would be agent none? This is what we recommend as a last resort option in the docs. 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-38009) Executing step is not expanded when there is a proceeding failing step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38009 Executing step is not expanded when there is a proceeding failing step Change By: James Dumay Issue Type: Task Bug 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-38009) Executing step is not expanded when there is a proceeding failing step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38009 Executing step is not expanded when there is a proceeding failing step This will be a common state to get into when people start using Kyoto and Blue Ocean. The examples in Kyoto use Docker. The first step is inspecting a local container called "java". If this command fails (it will the first time because it doesn't exist locally) then it will fetch it from the docker repository. Change By: James Dumay Attachment: Jenkins Blue Ocean 2016-09-07 12-44-40.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
[JIRA] (JENKINS-38009) Executing step is not expanded when there is a proceeding failing step
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-38009
Executing step is not expanded when there is a proceeding failing step
Issue Type:
Task
Assignee:
Unassigned
Attachments:
actual.png
Components:
blueocean-plugin
Created:
2016/Sep/07 2:43 AM
Priority:
Minor
Reporter:
James Dumay
Steps to reproduce Try this example Pipeline
node {
try {
sh 'exit 1'
} catch (Throwable e) {
sh 'echo "Eat all exceptions"'
} finally {
sh 'sleep 1000'
sh 'sleep 1000'
sh 'sleep 5000'
sh 'sleep 1000'
sh 'sleep 1000'
sh 'sleep 5000'
sh 'sleep 1000'
sh 'sleep 1000'
sh 'sleep 5000'
sh 'echo "Succeeds"'
}
}
Run the Pipeline. When executing this pipeline looks like: It is not possible to close the failing shell step - it opens again after a second or two What it should look like When this condition is hit and the run is executing:
The proceeding failing step should be closed
Running step should be open and tailing output
If the user opens or closes the failing step the UI should never change the expand state of the step.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title Patrick Wolf commented on JENKINS-37932 Re: Error if no "agent" specified I don't remember us specifically talking about making it required, maybe I was in Mongolia for that. Either way, there has to be an easier way than writing: agent label:"" This looks ugly and awkward to me. I think it is fine if the GUI creates an agent step even if it's empty but when creating a Jenkinsfile by hand it seems silly to force users to type in an empty string just to get a generic "node". 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-37880) Starting, stopping and replaying a run in quick succession does not work
Title: Message Title James Dumay commented on JENKINS-37880 Re: Starting, stopping and replaying a run in quick succession does not work Vivek Pandey Michael Neale I found another case where replay doesn't work (500 is received). I believe this run had a problem connecting to Github and is now un-replayable. Started by user James Dumay Connecting to https://api.github.com using i386/** > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from 2 remote Git repositories > git config remote.origin.url https://github.com/i386/app-store-demo.git # timeout=10 Fetching upstream changes from https://github.com/i386/app-store-demo.git > git --version # timeout=10 using .gitcredentials to set credentials > git config --local credential.username i386 # timeout=10 > git config --local credential.helper store --file=/var/folders/11/5vmtkd9j6kd3w6sbrsrw0sh8gn/T/git561487727535648502.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/i386/app-store-demo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from https://github.com/i386/app-store-demo.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:85) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:207) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress https://github.com/i386/app-store-demo.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: unable to access 'https://github.com/i386/app-store-demo.git/': Couldn't connect to server at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1740) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1476) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797) ... 8 more GitHub has been notified of this commit’s build result ERROR: null Finished: FAILURE
[JIRA] (JENKINS-37356) OWASP checker can't update on slave
Title: Message Title Steve Springett resolved as Fixed Changes were made to the core in v1.4.3 that should resolve this issue. Jenkins / JENKINS-37356 OWASP checker can't update on slave Change By: Steve Springett 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
[JIRA] (JENKINS-37467) OWASP Dependency-Check Plugin with default options fails
Title: Message Title Steve Springett closed an issue as Fixed Changes were made to the core in v1.4.3 that should resolve this issue. Jenkins / JENKINS-37467 OWASP Dependency-Check Plugin with default options fails Change By: Steve Springett Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-37478) OWASP does not release files from scan
Title: Message Title Steve Springett commented on JENKINS-37478 Re: OWASP does not release files from scan Changes were made to the core in 1.4.3. Could you try this version and report back. 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-37932) Error if no "agent" specified
Title: Message Title Andrew Bayer commented on JENKINS-37932 Re: Error if no "agent" specified You mean agent shouldn't be required? That's a change from what we've discussed and agreed on previously, fwiw. 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-37905) Accessing a member in PTC Integrity through Jenkins
Title: Message Title Sumit Sharma assigned an issue to Sumit Sharma Jenkins / JENKINS-37905 Accessing a member in PTC Integrity through Jenkins Change By: Sumit Sharma Assignee: Sumit Sharma 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-37905) Accessing a member in PTC Integrity through Jenkins
Title: Message Title Sumit Sharma assigned an issue to Unassigned Jenkins / JENKINS-37905 Accessing a member in PTC Integrity through Jenkins Change By: Sumit Sharma Assignee: Sumit Sharma 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-37932) Error if no "agent" specified
Title: Message Title Patrick Wolf commented on JENKINS-37932 Re: Error if no "agent" specified I talked to Kohsuke Kawaguchi at lunch today and he agrees that the default should be a no-label node rather than to require an agent. James Dumay do you have any opinion here? 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-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Michael Neale edited a comment on JENKINS-38007 Re: 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io FYI sometimes the timeout is a non-issue, just the way chrome shows the http 1.1 connection for SSE (it it stays open for a minute or so, and sometimes shows up as "timing out"). [~kktest11] did you see any errors in console other than that? can you attache them? Also were you logged in or anon? 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-37907) Include abililty to hook branch deletion.
Title: Message Title Michael Neale commented on JENKINS-37907 Re: Include abililty to hook branch deletion. Travis Cline not sure what this is asking for. Do you mean recieve the webhook from github so that it can clean things up as soon as they are removed? Or something else ? (a something else I have wanted is for agents to cleanup workspaces ASAP after deletion to save disk, not sure if that is what you are thinking about?) 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-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Michael Neale commented on JENKINS-38007 Re: 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io Tom FENNELLY not sure if there is much to diagnose, I am not seeing this, but worth a look (perhaps at least to eliminate this, may not actually be SSE at all). 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-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38007 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io Change By: Michael Neale Sprint: 1.0-beta-1 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-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Michael Neale assigned an issue to Tom FENNELLY Jenkins / JENKINS-38007 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io Change By: Michael Neale Assignee: Tom FENNELLY 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-37931) PR build can use PR's head/merge Jenkinsfile insted of master branch.
Title: Message Title Michael Neale commented on JENKINS-37931 Re: PR build can use PR's head/merge Jenkinsfile insted of master branch. You can do this by doing a PR from a branch in the same repo - which I think is a better way to honour the intent of the security model of github. Right? 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-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Michael Neale edited a comment on JENKINS-38007 Re: 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io FYI sometimes the timeout is a non-issue, just the way chrome shows the http 1.1 connection for SSE (it it stays open for a minute or so, and sometimes shows up as "timing out"). [~kktest11] did you see any errors in console other than that? can you attache them? Also were you logged in or anon? 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-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Michael Neale commented on JENKINS-38007 Re: 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io FYI sometimes the timeout is a non-issue, just the way chrome shows the http 1.1 connection for SSE (it it stays open for a minute or so, and sometimes shows up as "timing out"). Kohsuke Kawaguchi did you see any errors in console other than that? can you attache 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-38008) unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is
Title: Message Title krishna b created an issue Jenkins / JENKINS-38008 unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is able to open Issue Type: Task Assignee: Michael Fazio Components: hp-quality-center-plugin Created: 2016/Sep/07 1:29 AM Priority: Critical Reporter: krishna b unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM getting RPC server unavailable error but when launching from ALM UFT is able to open and run the script Add Comment
[JIRA] (JENKINS-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Kohsuke Kawaguchi created an issue Jenkins / JENKINS-38007 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/07 1:26 AM Priority: Major Reporter: Kohsuke Kawaguchi I was trying to play with ci.blueocean.io and nothing was loading. Looking at the chrome developer tools, I see that sse-gateway is causing timeout. The complete HTTP archive here James Dumay and I were chatting when I had that issue, and he said it is working for him. Classic Jenkins UI was working fine, too. James Dumay sounded like he knows about this lock inside SSE gateway that had caused a similar problem in the past, so this might be a known problem? Add Comment
[JIRA] (JENKINS-37939) Provide the option to exclude forks
Title: Message Title Michael Neale commented on JENKINS-37939 Re: Provide the option to exclude forks The problem I see is people turning this on, and then wondering why pipelines dont' show up (plenty of people work off forks, but I think primarily in OSS). I would like to think of what is the default: could the default be to not add forks as pipelines? If so, then I think this is a good idea (and the checkbox be to turn it on). 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-38006) REGRESSION: logs not tailing with freestyle
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38006 REGRESSION: logs not tailing with freestyle Change By: Michael Neale Sprint: 1.0-beta-1 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-38006) REGRESSION: logs not tailing with freestyle
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38006 REGRESSION: logs not tailing with freestyle Issue Type: Bug Assignee: Thorsten Scherler Components: blueocean-plugin Created: 2016/Sep/07 12:56 AM Priority: Major Reporter: Michael Neale If you create a freestyle job that outputs a lot of lines, it doesn't follow it along to the end. For example, create a freestyle job with nothing but the following: ping www.apple.com And once it flows past the view port, it doesn't tail along with the end. I used this to be "slow" to easily see it happen (it probably could be done with a faster script). In scope: Diagnose above Ideally have ATH test to cover freestyle tailling fix to tail freestyle (pipeline seems to work correctly)
[JIRA] (JENKINS-37744) Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation
Title: Message Title Vivek Pandey updated JENKINS-37744 Jenkins / JENKINS-37744 Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation Change By: Vivek Pandey Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-38005
Using archiveArtifacts with a non-matching pattern silently fails the build
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
pipeline
Created:
2016/Sep/07 12:42 AM
Environment:
Jenkins 2.7.3, Pipeline 2.3
Priority:
Minor
Reporter:
R. Tyler Croy
If you happen to specify a pattern that doesn't match any files in the workspace, archiveArtifacts will silently fail the build. Jenkinsfile
node {
sh 'echo "lol"'
archiveArtifacts artifacts: 'lol*.zip'
}
Console Output
Started by user admin
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor
Running on Azure0907122157 in /home/azureuser/workspace/Experiments/bad-artifacts
[Pipeline] {
[Pipeline] sh
[bad-artifacts] Running shell script
+ echo lol
lol
[Pipeline] step
Archiving artifacts
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: FAILURE
archive step In contrast, the use of the archive step (e.g. archive 'lol*.zip' in the above Jenkinsfile) will result in a silently successful build.
[JIRA] (JENKINS-37744) Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation
Title: Message Title Vivek Pandey updated JENKINS-37744 Jenkins / JENKINS-37744 Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34842) Getting Started page broken
Title: Message Title R. Tyler Croy closed an issue as Fixed I believe this has been fixed by Jesse Glick's work for JENKINS-34239 Jenkins / JENKINS-34842 Getting Started page broken 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 subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-28950) Cucumber Test Result Plugin Fails to parse JSON: Expected BEGIN_ARRAY but was STRING
Title: Message Title Brian Jameson commented on JENKINS-28950 Re: Cucumber Test Result Plugin Fails to parse JSON: Expected BEGIN_ARRAY but was STRING Any update on this issue? I am experiencing this issue as well. Version: 0.8.2 Jenkins: 2.19 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-38004) junit snippet generator with "Health report" Double doesn't generate proper Groovy output
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-38004 junit snippet generator with "Health report" Double doesn't generate proper Groovy output Issue Type: Bug Assignee: Jesse Glick Attachments: junit-health-factor.png Components: junit-plugin, pipeline Created: 2016/Sep/06 11:34 PM Environment: Jenkins 2.7.3, Pipeline 2.3 Priority: Minor Reporter: R. Tyler Croy Reproduction steps are pretty easy: Open snippet generator Choose junit step Add a "Health report amplification factor" different than the default of 1.0 Get invalid Groovy Expected: junit healthScaleFactor: 3.0, testResults: 'build/test-reports/*.xml' Received junit healthScaleFactor: Double>, testResults: 'build/test-reports/*.xml'
[JIRA] (JENKINS-34148) Provide a `junit` step for archiving test results
Title: Message Title R. Tyler Croy closed an issue as Fixed There is now a junit step (Pipeline 2.3) Jenkins / JENKINS-34148 Provide a `junit` step for archiving test results 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 subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-33703) Exceptions in generated DSL documentation for `unarchive`
Title: Message Title R. Tyler Croy commented on JENKINS-33703 Re: Exceptions in generated DSL documentation for `unarchive` FWIW this is still present as of Pipeline 2.3 / Jenkins 2.7.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38003) Lockable Resources Plugin ignores timeouts currently in effect
Title: Message Title
John Zila created an issue
Jenkins / JENKINS-38003
Lockable Resources Plugin ignores timeouts currently in effect
Issue Type:
Bug
Assignee:
Unassigned
Components:
lockable-resources-plugin
Created:
2016/Sep/06 11:16 PM
Priority:
Major
Reporter:
John Zila
Using the lockable resources plugin with pipelines, timeouts don't work. I have a lock that appears as follows:
...
timeout(30) {
...
lock("foo_${env.NODE_NAME}") {
sh 'do something on node in my current context'
}
...
}
When the code in the critical section hangs, I expect the 30 minute timeout to kill the build (or at least the scope we're in). This doesn't happen. Might be related to JENKINS-38002
Add Comment
[JIRA] (JENKINS-30411) Add the PROMOTION_ENV token macro
Title: Message Title Michael Fowler commented on JENKINS-30411 Re: Add the PROMOTION_ENV token macro Is it expected that PROMOTION_ENV should be able to retrieve env vars added or changed by the env_inject 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-38002) Lockable Resources Plugin releases executor while waiting and executing
Title: Message Title
John Zila created an issue
Jenkins / JENKINS-38002
Lockable Resources Plugin releases executor while waiting and executing
Issue Type:
Bug
Assignee:
Unassigned
Components:
lockable-resources-plugin
Created:
2016/Sep/06 11:14 PM
Priority:
Major
Reporter:
John Zila
When using the lockable resources plugin with pipelines, nothing really works as it should. I have a lock that appears as follows:
lock("foo_${env.NODE_NAME}") {
sh 'do something on node in my current context'
}
The intent is to be able to run many jobs on one machine, but only lock critical sections on a node-by-node basis, for things that require singleton resources on the node. However, as soon as my job starts waiting, it releases its executor. If it doesn't wait, it still releases the executor but continues executing. This can cause jobs to execute when they shouldn't be, and can lose access to nodes that are necessary once out of the critical section.
[JIRA] (JENKINS-37744) Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37744 Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation Change By: Michael Neale In scope: * Check that the newly released Kyoto plugin https://github.com/jenkinsci/pipeline-config-plugin works nicely with blue ocean (when released)* Bundle the plugin with aggregator* Bump Jenkins version to Jenkins 2.7.3 LTS* Check that blue ocean (beta?) works on a fresh jenkins install "out of box" as much as possible* Add a test that uses multiple parallels and multiple stages so we can ensure this gets displayed correctly * Fix unprotected root action when JWT is disabled Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-37744) Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37744 Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation Change By: Michael Neale In scope: * Check that the newly released Kyoto plugin https://github.com/jenkinsci/pipeline-config-plugin works nicely with blue ocean (when released)* Bundle the plugin with aggregator* Bump Jenkins version to Jenkins 2.7.3 LTS* Check that blue ocean (beta?) works on a fresh jenkins install "out of box" as much as possible* Add a test that uses multiple parallels and multiple stages so we can ensure this gets displayed correctly * Fix unprotected root action when JWT is disabled Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-37744) Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37744 Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation Change By: Michael Neale In scope: * Check that the newly released Kyoto plugin https://github.com/jenkinsci/pipeline-config-plugin works nicely with blue ocean (when released)* Bundle the plugin with aggregator* Bump Jenkins version to Jenkins 2.7.3 LTS* Check that blue ocean (beta?) works on a fresh jenkins install "out of box" as much as possible* Add a test that uses multiple parallels and multiple stages so we can ensure this gets displayed correctly * Fix unprotected root action when JWT is disabled Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-38001) Cannot rename a GitHub Org Folder
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-38001 Cannot rename a GitHub Org Folder Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: rename.png Components: github-organization-folder-plugin Created: 2016/Sep/06 11:07 PM Environment: Jenkins 2.7.3, GitHub Organization Folder plugin 1.4 Priority: Minor Reporter: R. Tyler Croy Pretty simple steps to reproduce: Create a GitHub Org Folder Go back to 'Configure' Change "Name" field to something Hit Save Confirm you want to rename Hit page with "Recomputation is currently in progress" (http://localhost:8080/job/reiseburo/rename?newName=reise=Recomputation+is+currently+in+progress) Wait forever and ever and ever Interestingly, this does seem to kick-off a Re-scan of the Organization, but it doesn't ever rename the folder.
[JIRA] (JENKINS-37832) Any API 401 should redirect to login page
Title: Message Title Michael Neale commented on JENKINS-37832 Re: Any API 401 should redirect to login page Current approach is to use a header to track if user name logged in has changed, and if it has, trigger a refresh 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-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Matthew Mitchell commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module So the proposed fix isn't the correct one? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37233) Switch to a responsive table component
Title: Message Title James Dumay commented on JENKINS-37233 Re: Switch to a responsive table component Cliff Meyers go for it One thing that I like about this is filtering, sorting and mobile responsiveness. 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-38000) Make Jenkins post a vote but comments
Title: Message Title Khai Do created an issue Jenkins / JENKINS-38000 Make Jenkins post a vote but comments Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Sep/06 10:56 PM Environment: Jenkins 1.625.3 Gerrit Trigger Plugin 2.22.0 Labels: plugins gerrit-trigger Priority: Minor Reporter: Khai Do We get too many comments from Jenkins which clutters up comments in a change and makes reviewing difficult. I would like Jenkins to vote (Verified +1/-1) on my change but not send any comments back to Gerrit. Essentially I want silent to be true, while skip vote to be false. However it looks like enabling silentMode will override skipVote and make Jenkins not vote. Add Comment
[JIRA] (JENKINS-29956) Wipe out repository & force clone ignore's Windows directory junctions
Title: Message Title Michael Fowler commented on JENKINS-29956 Re: Wipe out repository & force clone ignore's Windows directory junctions Oleg Nenashev Could this be backported to an LTS release? 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-36929) Add the version of protocols used by connectors
Title: Message Title Owen Wood commented on JENKINS-36929 Re: Add the version of protocols used by connectors https://github.com/jenkinsci/jenkins/commit/b1e3f6fdd2095d17293ce2c9b26e40ea98380d73#diff-2697fe18d8c92287ad0be309d1fbfd89R126 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-32267) Allow replacement based on parameters at creation time
Title: Message Title Michael Fowler reopened an issue Jenkins / JENKINS-32267 Allow replacement based on parameters at creation time Change By: Michael Fowler Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25624) CLI Support for build submission parameters
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25624 Re: CLI Support for build submission parameters Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinition.java src/test/java/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinitionTest.java http://jenkins-ci.org/commit/matrix-combinations-plugin/e5b77a923ea99e2e9fe0215596b86d7fa5fb5a51 Log: [FIXED JENKINS-25624] Support CLI 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-37685) Evaluate mutable vs. immutable data structures w/ MobX
Title: Message Title Cliff Meyers updated JENKINS-37685 Jenkins / JENKINS-37685 Evaluate mutable vs. immutable data structures w/ MobX Change By: Cliff Meyers Status: In Review 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-37932) Error if no "agent" specified
Title: Message Title Michael Neale commented on JENKINS-37932 Re: Error if no "agent" specified Patrick Wolf right exactly. 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-33401) Credentials Integration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33401 Re: Credentials Integration Code changed in jenkins User: propspero238 Path: src/main/java/org/jenkinsci/plugins/liquibase/common/PropertiesAssembler.java http://jenkins-ci.org/commit/liquibase-runner-plugin/7c865b8427bf0a46dc6ae12d6e944b890b10c898 Log: JENKINS-33401 - Credentials Integration null check on credentials lookup 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-37744) Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-37744 Bundle and test Kyoto plugin with blue ocean, and test out of box with fresh Jenkins installation Change By: Vivek Pandey In scope: * Check that the newly released Kyoto plugin https://github.com/jenkinsci/pipeline-config-plugin works nicely with blue ocean (when released)* Bundle the plugin with aggregator* Bump Jenkins version to Jenkins 2.7.3 LTS* Check that blue ocean (beta?) works on a fresh jenkins install "out of box" as much as possible* Add a test that uses multiple parallels and multiple stages so we can ensure this gets displayed correctly 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-37999) Debian Jessie package produce error on installation, Jenkins fails to start
Title: Message Title JEK NIS created an issue Jenkins / JENKINS-37999 Debian Jessie package produce error on installation, Jenkins fails to start Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 2016/Sep/06 10:05 PM Priority: Critical Reporter: JEK NIS Following the installation instructions for debian packages found here: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu is not successful. The installation process fails with this error: Setting up default-jre-headless (2:1.7-52) ... Setting up jenkins (2.7.3) ... Job for jenkins.service failed. See 'systemctl status jenkins.service' and 'journalctl -xn' for details. invoke-rc.d: initscript jenkins, action "start" failed. dpkg: error processing package jenkins (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ca-certificates (20141019+deb8u1) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d done. done. Setting up openjdk-7-jre-headless:amd64 (7u111-2.6.7-1~deb8u1) ... update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java to provide /usr/bin/java (java) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/pack200 to provide /usr/bin/pack200 (pack200) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/unpack200 to provide /usr/bin/unpack200 (unpack200) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/orbd to provide /usr/bin/orbd (orbd) in auto
