[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Michael Neale Assignee: Cliff Meyers 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Michael Neale stopped work on JENKINS-35768 Change By: Michael Neale 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Michael Neale assigned an issue to Cliff Meyers Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Michael Neale Assignee: Michael Neale Cliff Meyers 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Michael Neale Sprint: atlantic indian 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-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-38811 Blue Ocean does not start on Internet Explorer 11 Change By: Torsten Kleiber Attachment: blueocean.js 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Michael Neale commented on JENKINS-35768 Re: Developer can filter the activity list to a specific branch Vivek Pandey do we have an api for showing what branches are available in a multibranch job (really just what jobs are in a MB folder) - or does there need to be another ticket to track 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-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber commented on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 Have save the file blueocean.js from ie debugger. 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Michael Neale A user should be able to filter the list of branches on an activity screenIn Scope: * Popover/filter as per attached visual and behavior design (assuming JDL popover will help, but may not) - see graphic and gif video * Fetch Fetching a complete list of available branches to populate the choice (this may need to be optimised to pre-fill with current pages worth of branch names, while it fetches more)* Selecting of a branch .In scope* Developer can click on the "All Branches" button* Popover should appear that has result in a list and search box* The list fetch of branches within the popover is scrollable* Popover should have a max size (20% pages worth of the window height? You might need to play with this to get it right.)* Initial content shows the most recently built branches data ( max of 10)* Contents of list update as you type (search)* Clicking on a branch described by Vivek in the popovers list will update the Activity tab to show runs from a single branch comments) and hide then updating of the branch column activity listing * Clicking the X clears the search box and resets the current filter back URI should be updated to "All Branches", showing reflect the branch column again filtered status * When the URI should filter is applied the URL of the page params should change be honoured ( so that the filter state page can be linked . to, required elsewhere) * There Sorting should be a slight shadow on the popover master first, followed by alpha sorted list Out of scope: * There is no pagination for the list (load all branches) Recently used searches * Don't add this Adding to the JDL (this stays in dashboard)How it works: We only have a pages worth of data on the activity screen initially, but a drop down will need to fetch a list of available branches (perhaps [~vivek] can advice how). When a list for a filter is shown, it can show a pages worth of data just for that branch. Add Comment
[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Michael Neale A user should be able to filter the list of branches on an activity screen In Scope: * Popover/filter as per attached visual and behavior design* Fetch a complete list of available branches to populate the choice (this may need to be optimised to pre-fill with current pages worth of branch names, while it fetches more)* Selecting of a branch .In scope* Developer can click on the "All Branches" button* Popover should appear that has a list and search box* The list of branches within the popover is scrollable* Popover should have a max size (20% of the window height? You might need to play with this to get it right.)* Initial content shows the most recently built branches (max of 10)* Contents of list update as you type (search)* Clicking on a branch in the popovers list will update the Activity tab to show runs from a single branch and hide the branch column* Clicking the X clears the search box and resets the current filter back to "All Branches", showing the branch column again* When the filter is applied the URL of the page should change so that the filter state can be linked.* There should be a slight shadow on the popover* There is no pagination for the list (load all branches)* Don't add this to the JDL Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Michael Neale edited a comment on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 thanks [~tkleiber] heh - one case where i18n isn't actually helping ;) EDIT: wouldn't hurt to get some lines of code around: adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:84892:9 if possible. otherwise I think this will easily reproduce with IE11. 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-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Michael Neale commented on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 thanks Torsten Kleiber heh - one case where i18n isn't actually helping 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-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38811 Blue Ocean does not start on Internet Explorer 11 Change By: Michael Neale Sprint: indian 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-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title
Torsten Kleiber commented on JENKINS-38811
Re: Blue Ocean does not start on Internet Explorer 11
Error is reproducible furthermore, here is the copy of the ie console: HTML1300: Navigation wurde ausgeführt. Datei: blue TypeError: Die Eigenschaft "apply" eines undefinierten oder Nullverweises kann nicht abgerufen werden. { [functions]: , _proto_: { [functions]: , _proto_: { [functions]: , _proto_: { }, message: "", name: "Error" }, message: "", name: "TypeError" }, description: "Die Eigenschaft "apply" eines undefinierten oder Nullverweises kann nicht abgerufen werden.", message: "Die Eigenschaft "apply" eines undefinierten oder Nullverweises kann nicht abgerufen werden.", name: "TypeError", number: -2146823281, stack: "TypeError: Die Eigenschaft "apply" eines undefinierten oder Nullverweises kann nicht abgerufen werden. at startApp (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:84892:9) at Anonymous function (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:84932:5) at nextArg (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7006:25) at _filterExtensions (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7050:17) at Anonymous function (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7018:17) at checkLoading (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7146:21) at Anonymous function (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7174:17) at dec (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7212:17) at Anonymous function (" }
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
[JIRA] (JENKINS-37245) Developer can jump to the run history for a specific branch
Title: Message Title Brody Maclean assigned an issue to Michael Neale Jenkins / JENKINS-37245 Developer can jump to the run history for a specific branch Change By: Brody Maclean Assignee: Brody Maclean Michael Neale 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-37245) Developer can jump to the run history for a specific branch
Title: Message Title Brody Maclean commented on JENKINS-37245 Re: Developer can jump to the run history for a specific branch Zeplin – https://zpl.io/ZtGMt8 Updated Screenshot 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-37245) Developer can jump to the run history for a specific branch
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-37245 Developer can jump to the run history for a specific branch Change By: Brody Maclean Attachment: Branches.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-38916) Special Character (for example ~) in Password breaks function
Title: Message Title Niklas Fiedler created an issue Jenkins / JENKINS-38916 Special Character (for example ~) in Password breaks function Issue Type: Bug Assignee: Félix Belzunce Arcos Attachments: Log.txt Components: active-directory-plugin Created: 2016/Oct/12 5:26 AM Environment: Jenkins ver.2.25 Active Directory Plugin 2.0 Labels: Password ActiveDirectory Specialcharacter Priority: Major Reporter: Niklas Fiedler If you use a special character like ~ in your password, everything after the character is recognized as command which obviously makes no sense and causes the Plugin to fail. Please see attached log file.
[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch
Title: Message Title Brody Maclean commented on JENKINS-35768 Re: Developer can filter the activity list to a specific branch Updated ✅ 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Brody Maclean Attachment: Filter.gif 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Brody Maclean Attachment: Filter.gif 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Michael Neale commented on JENKINS-35768 Re: Developer can filter the activity list to a specific branch That last gif is missing the unselected filter icon from the image 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Brody Maclean commented on JENKINS-35768 Re: Developer can filter the activity list to a specific branch 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Brody Maclean Attachment: Filter.gif 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-38878) The result from jtl is different from jmeter' result
Title: Message Title zmkhp cn commented on JENKINS-38878 Re: The result from jtl is different from jmeter' result I use the default jmeter's jtl format.Yesterday I analysis the real reason may be the wrong format,too. The JTL file has been attached. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38878) The result from jtl is different from jmeter' result
Title: Message Title zmkhp cn updated an issue Jenkins / JENKINS-38878 The result from jtl is different from jmeter' result Change By: zmkhp cn Attachment: test.jtl 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-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Chris Kitching updated an issue Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runner Change By: Chris Kitching Currently, there seem to be numerous features of Groovy that simply do not work when used in Jenkinsfiles or associated scripts.Even really basic things such as groovy-style iterators are not suppported: something I wasted a lot of time on until I finally came across https://issues.jenkins-ci.org/browse/JENKINS-26481 I wrote a nifty thing that uses inheritance, got "General error during canonicalisation: Unexpected variable type: null", and then finally found https://issues.jenkins-ci.org/browse/JENKINS-34428 - apparently inheritance doesn calls to super don 't work, either.Writing nontrivial Jenkinsfiles currently involves a cycle in which you write your code, it produces a confusing crash in the CPS engine, you go hunting, eventually find a bug report, remove the offending language feature, and repeat.This is not fun.Can we please have documentation stating which subset of the Groovy language actually works?Even better: where it is possible to do so simply (such as for inheritance) can we please have a nice readable error message instead of an incomprehensible one? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch
Title: Message Title Brody Maclean assigned an issue to Michael Neale Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Brody Maclean Assignee: Brody Maclean Michael Neale 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Brody Maclean commented on JENKINS-35768 Re: Developer can filter the activity list to a specific branch Zeplin Link https://zpl.io/Z1U8Iw2 Flow Mockup Filter Icon https://design.google.com/icons/#ic_filter_list Dropdown List Order: master, then alpha order. 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-20797) UserIdCause should be used, not UserCause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20797 Re: UserIdCause should be used, not UserCause Code changed in jenkins User: Mustafa Ulu Path: src/main/java/hudson/plugins/release/ReleaseWrapper.java http://jenkins-ci.org/commit/release-plugin/d91ea96a096a3459179e08edc959eb7161fa7db4 Log: JENKINS-20797 - Trigger builds with Cause.UserIdCause (#20) JENKINS-20797 - Trigger with Cause.UserIdCause 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-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Chris Kitching updated an issue Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runner Change By: Chris Kitching Currently, there seem to be numerous features of Groovy that simply do not work when used in Jenkinsfiles or associated scripts.Even really basic things such as groovy-style iterators are not suppported: something I wasted a lot of time on until I finally came across https://issues.jenkins-ci.org/browse/JENKINS-26481 I wrote a nifty thing that uses inheritance, got "General error during canonicalisation: Unexpected variable type: null", and then finally found https://issues.jenkins-ci.org/browse/JENKINS-34428 - apparently inheritance doesn't work, either.Writing nontrivial Jenkinsfiles currently involves a cycle in which you write your code, it produces a confusing crash in the CPS engine, you go hunting, eventually find a bug report, remove the offending language feature, and repeat.This is not fun.Can we please have documentation stating which subset of the Groovy language actually works? Even better: where it is possible to do so simply (such as for inheritance) can we please have a nice readable error message instead of an incomprehensible one? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Chris Kitching updated an issue Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runner Change By: Chris Kitching Currently, there seem to be numerous features of Groovy that simply do not work when used in Jenkinsfiles or associated scripts.Even really basic things such as groovy-style iterators are not suppported: something I wasted a lot of time on until I finally came across https://issues.jenkins-ci.org/browse/JENKINS-26481 I wrote a nifty thing that uses inheritance, got "General error during canonicalisation: Unexpected variable type: null", and then finally found https://issues.jenkins-ci.org/browse/JENKINS- 27927 34428 - apparently inheritance doesn't work, either.Writing nontrivial Jenkinsfiles currently involves a cycle in which you write your code, it produces a confusing crash in the CPS engine, you go hunting, eventually find a bug report, remove the offending language feature, and repeat.This is not fun.Can we please have documentation stating which subset of the Groovy language actually works? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: Brody Maclean Attachment: Branch Filter.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-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Chris Kitching updated an issue Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runner Change By: Chris Kitching Currently, there seem to be numerous features of Groovy that simply do not work when used in Jenkinsfiles or associated scripts.Even really basic things such as groovy-style iterators are not suppported: something I wasted a lot of time on until I finally came across https://issues.jenkins-ci.org/browse/JENKINS-26481 I wrote a nifty thing that uses inheritance, got "General error during canonicalisation: Unexpected variable type: null", and then finally found https://issues.jenkins-ci.org/browse/JENKINS-27927 - apparently inheritance doesn't work, either. Writing nontrivial Jenkinsfiles currently involves a cycle in which you write your code, it produces a confusing crash in the CPS engine, you go hunting, eventually find a bug report, remove the offending language feature, and repeat.This is not fun.Can we please have documentation stating which subset of the Groovy language actually works? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runner Change By: Oleg Nenashev Labels: documentation ux Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Oleg Nenashev commented on JENKINS-38915 Re: Please document the limitations of the Jenkinsfile runner Fixed the component and the assignee 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-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runner Change By: Oleg Nenashev Labels: documentation 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-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Oleg Nenashev assigned an issue to Jesse Glick Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runner Change By: Oleg Nenashev Assignee: Oleg Nenashev Jesse Glick 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-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runner Change By: Oleg Nenashev Component/s: pipeline Component/s: _unsorted 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-38915) Please document the limitations of the Jenkinsfile runer
Title: Message Title Chris Kitching created an issue Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runer Issue Type: Improvement Assignee: Oleg Nenashev Components: _unsorted Created: 2016/Oct/12 2:55 AM Priority: Minor Reporter: Chris Kitching Currently, there seem to be numerous features of Groovy that simply do not work when used in Jenkinsfiles or associated scripts. Even really basic things such as groovy-style iterators are not suppported: something I wasted a lot of time on until I finally came across https://issues.jenkins-ci.org/browse/JENKINS-26481 Writing nontrivial Jenkinsfiles currently involves a cycle in which you write your code, it produces a confusing crash in the CPS engine, you go hunting, eventually find a bug report, remove the offending language feature, and repeat. This is not fun. Can we please have documentation stating which subset of the Groovy language actually works? Add Comment
[JIRA] (JENKINS-38915) Please document the limitations of the Jenkinsfile runner
Title: Message Title Chris Kitching updated an issue Jenkins / JENKINS-38915 Please document the limitations of the Jenkinsfile runner Change By: Chris Kitching Summary: Please document the limitations of the Jenkinsfile runer runner 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-37792) Pipeline Config: Notifications per stage
Title: Message Title Michael Neale commented on JENKINS-37792 Re: Pipeline Config: Notifications per stage well, obviously "lastly" is literally the worst name ever in the history of bad names. Well maybe after "vietnam4j". postBuild terminology is used elsewhere (outside of jenkins) and is fairly self explanatory (but it isn't as nice as the pluralised "notifications"). I view it as an abbrevation of "post build actions" - plural. There is probably a single german word for that The camel case isn't optimal, yeah. Whatever the keyword names/reserved names are, the ideal is that as much as possible, things that can be done globally could be done in a stage, which are then scoped to it. unfortunately the name "post build" doesn't quite work. Notifications as a name works... I do agree that having the same events as notifications/postBuild in stage is nice (often there is a need to always cleanup, regardless of outcome). Given this ticket is is about notifications - I think it is ok to say that notifications happening in the node that the stage happens with is ok (doesn't make a lot of difference to the user). If we want to talk about general events, naming, globally or stages, we should setup a time to explore it on a hangout, as there is lots we could cover, and there are good ideas 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
[JIRA] (JENKINS-38914) hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory
Title: Message Title Dilip Mahadevappa updated an issue Jenkins / JENKINS-38914 hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Change By: Dilip Mahadevappa Attachment: heap-screenshot-3.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-38914) hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory
Title: Message Title Dilip Mahadevappa updated an issue Jenkins / JENKINS-38914 hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Change By: Dilip Mahadevappa Attachment: heap-screenshot-0.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-38914) hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory
Title: Message Title Dilip Mahadevappa updated an issue Jenkins / JENKINS-38914 hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Change By: Dilip Mahadevappa Attachment: heap-screenshot-3.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-38914) hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory
Title: Message Title Dilip Mahadevappa updated an issue Jenkins / JENKINS-38914 hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Change By: Dilip Mahadevappa Attachment: heap-screenshot-0.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-38914) hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory
Title: Message Title Dilip Mahadevappa updated an issue Jenkins / JENKINS-38914 hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Change By: Dilip Mahadevappa Summary: hudson.model.ParametersAction heavily bloats memory use and size of build.xml with by loading all builds TextParameterValue in memory 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-38914) hudson.model.ParametersAction heavily bloats memory use and size of build.xml with TextParameterValue
Title: Message Title Dilip Mahadevappa created an issue Jenkins / JENKINS-38914 hudson.model.ParametersAction heavily bloats memory use and size of build.xml with TextParameterValue Issue Type: Bug Assignee: Unassigned Attachments: build.xml-screenshot.png, heap-screenshot-0.png, heap-screenshot-1.png Components: core Created: 2016/Oct/12 2:08 AM Environment: 1.651.3 Labels: memory outofmemoryerror Priority: Major Reporter: Dilip Mahadevappa Hi, Recently we upgraded from 1.596.3 to 1.651.3 and observing that the later version is consuming lot of heap as soon as it comes up. WE have got many jobs with huge build history.. in terms of 4000 builds. Each builds's build.xml is in terms of 500k. Whenever the instance is restarted the heap starts to grow and finally the instance crashed with OEM. The heap dump shows that values defined under hudson.model.TextParameterValue of each build is loaded into memory! Refer screenshots: heap-screenshot-0.png & heap-screenshot-1.png Here is the contents of build.xml of one such build. refer screenshot build.xml-screenshot.png Is it this commit SECURITY-170 Store initial parameters list for later use which is loading all values?
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title David Beck commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I also have been having this issue. But I have just setup Jenkins to automate a MSBuild for our team. Pipeline jobs work fine but Multipath does not work. Currently our deepest file on our repository is 197 characters deep. leaving me just 63 for the file path. 52 are consumed by the supposed fix for %2 and that leaves me 11 chars C:\ consumes 3\ and then I can't handle even the git branch name. So this totally breaks my code. I know I am running close to the edge and will have a conversation with my devs about it but currently its a waste of 52 chars. I think I could live with 8 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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Shane McDonald edited a comment on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
I ran into this as well. I got around the issue by checking "Use custom child workspace" in my job config, and setting "Child Directory" to "{{ ${SHORT_COMBINATION} }}"
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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Shane McDonald commented on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
I ran into this as well. I got around the issue by checking "Use custom child workspace" in my job config, and setting "Child Directory" to "{{$ {SHORT_COMBINATION} }}"
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-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Brian Saville edited a comment on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens Ran into the same thing here. *UPDATE*: This was due to us using the "Suppress automatic SCM triggering" option on a GitHub multibranch project. After reading through the source, I incorrectly assumed it would prevent only the initial branch index from firing off new builds, but since the GitHub plugin webhook actually uses the branch indexing to fire off builds after receiving a hook payload, it ignored those as all. Disabling this property on the multibranch project fixed the issue completely for me. 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 yeah that is clearly part of it, but you try it yourself and see if it is "reasonable" for you (is it?) 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-38720) 500 Server Error when notifying master of new mercurial commit: "Response header too large"
Title: Message Title Nick Sonneveld commented on JENKINS-38720 Re: 500 Server Error when notifying master of new mercurial commit: "Response header too large" Jesse Glick Hrm, I wonder if you can generate the "Response header too large" exception while adding properties to the header. It looks like the size isn't checked until the header is flushed just before the body starts being written. I'm certainly not checking the results in the header but others might. Should it just be a cap with no warning? Or should there be a further header with number of projects triggered? (with a possible "truncated" property as well?) 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-38875) Git configurations lost in every single job after update to 3.0.0
Title: Message Title Mark Waite commented on JENKINS-38875 Re: Git configurations lost in every single job after update to 3.0.0 Usually if you can't see git as an option in source code management it means the plugin was not loaded because a dependency was not satisfied. The git plugin dependencies are listed on the wiki page and include things like: mailer (version:1.17) ssh-credentials (version:1.12) git-client (version:2.0.0) matrix-project (version:1.7.1) credentials (version:2.1.4) workflow-scm-step (version:1.14.2) scm-api (version:1.2) It also includes the following optional dependencies: promoted-builds (version:2.27, optional) parameterized-trigger (version:2.4, optional) token-macro (version:1.11, optional) Can you share any log messages in the failure case which might confirm that one or more of those dependencies could not be loaded? I believe that job definitions are not generally overwritten at Jenkins startup, even if the plugin did not load due to failed dependency. Thus, I'm surprised that your job definitions were damaged by a failure to load the git plugin. Do you have anything in your Jenkins instance which would have caused those job definitions to be saved while the plugin was not loaded? One example of that might be the configuration slicing plugin, which is able to save modifications to many jobs at once. If after starting Jenkins with the git plugin unloadable (due to an unsatisfied dependency), if you used the configuration slicing plugin to save those job definitions, the git information would likely be removed from the job. Add Comment
[JIRA] (JENKINS-38253) Optimize static resource fetch
Title: Message Title Michael Neale commented on JENKINS-38253 Re: Optimize static resource fetch yep, close this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38875) Git configurations lost in every single job after update to 3.0.0
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38875 Git configurations lost in every single job after update to 3.0.0 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-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Andrew Sumner updated an issue Jenkins / JENKINS-37193 inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Change By: Andrew Sumner Component/s: inedo-buildmaster-plugin Component/s: inedo-proget-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-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner updated an issue Jenkins / JENKINS-38633 As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Change By: Andrew Sumner Component/s: inedo-buildmaster-plugin Component/s: inedo-proget-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-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title Michael Neale edited a comment on JENKINS-35776 Re: Bundle all licenses in the license directory and display them on /legal I don't think it should be different - /about exists for that reason. 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-20718) Add Documentation and help for startup-trigger-plugin
Title: Message Title Emory Penney resolved as Fixed Jenkins / JENKINS-20718 Add Documentation and help for startup-trigger-plugin Change By: Emory Penney 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-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title Michael Neale commented on JENKINS-35776 Re: Bundle all licenses in the license directory and display them on /legal I don't think it should be different - /about exists for that reason. 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-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Brian Saville commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens Ran into the same thing 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json I don't see a 1.5, do you mean 1.1.5? I can confirm the bug replicates in that version as well. 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-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Jon Starbird commented on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Thanks Andrew. This will make usage of the plugin much better for our use 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain updated an issue Jenkins / JENKINS-28877 Bitbucket Plugin unable to parse Bitbucket webhook response json Change By: Justen Britain Environment: jenkins Jenkins 1.617, bitbucket-plugin 1.1.0 Jenkins 2.25, bitbucket-plugin 1.1.5 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-20718) Add Documentation and help for startup-trigger-plugin
Title: Message Title Danny Staple commented on JENKINS-20718 Re: Add Documentation and help for startup-trigger-plugin No - go ahead. 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-20718) Add Documentation and help for startup-trigger-plugin
Title: Message Title Danny Staple edited a comment on JENKINS-20718 Re: Add Documentation and help for startup-trigger-plugin No objections - go ahead. 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-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title recampbell commented on JENKINS-35776 Re: Bundle all licenses in the license directory and display them on /legal How is this different from the existing Jenkins about page? 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-38410) Job-dsl-plugin issue with rundeck instance
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38410 Re: Job-dsl-plugin issue with rundeck instance Code changed in jenkins User: Daniel Spilker Path: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/c23fef6ba31a0d628717a4d0127fe8b12ec200f2 Log: Merge remote-tracking branch 'marekkapowicki/JENKINS-38410' Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/a3228f6a3fd6...c23fef6ba31a 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-38410) Job-dsl-plugin issue with rundeck instance
Title: Message Title Daniel Spilker resolved as Fixed Will be fixed in 1.52. Jenkins / JENKINS-38410 Job-dsl-plugin issue with rundeck instance Change By: Daniel Spilker 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-38410) Job-dsl-plugin issue with rundeck instance
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38410 Re: Job-dsl-plugin issue with rundeck instance Code changed in jenkins User: Marek Kapowicki Path: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/c335917906be99b11eb98006cf2d069121b5527a Log: JENKINS-38410 Fix the backward compatibility with rundeck 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-38891) Pull Requests page is confusing
Title: Message Title Michael Neale commented on JENKINS-38891 Re: Pull Requests page is confusing ah yes, this is to make you appear more productive and have more pull requests yeah this does seem wrong. I think what happens is that when there are multiple commits from multiple people they show up like this. Antonio Muñiz can you link to some actual PRs this lists, so we can confirm? 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-37792) Pipeline Config: Notifications per stage
Title: Message Title Patrick Wolf commented on JENKINS-37792 Re: Pipeline Config: Notifications per stage I still don't like the idea of having a special notifications block at the top level but a separate method for notifications inside a stage. This creates a poor user experience IMO. 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-38508) git scm poll doesn't ignore changes with pipeline
Title: Message Title Jesse Glick commented on JENKINS-38508 Re: git scm poll doesn't ignore changes with pipeline Would need to study your example more closely since so far I do not understand it. (Generally, steps to reproduce from scratch are more helpful than explanations.) Possibly same as JENKINS-38659. 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-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Andrew Sumner commented on JENKINS-37193 Re: inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Work is underway but hit a snag getting some information I needed using the BuildMaster API, Inedo are working on this and the information will be provided as part of a 5.5 BuildMaster release (I should have access to a beta version in the next day or two). I'll update you when I have more information. 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-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner commented on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Work is underway but hit a snag getting some information I needed using the BuildMaster API, Inedo are working on this and the information will be provided as part of a 5.5 BuildMaster release (I should have access to a beta version in the next day or two). I'll update you when I have more information. 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-38508) git scm poll doesn't ignore changes with pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38508 git scm poll doesn't ignore changes with pipeline Change By: Jesse Glick Component/s: workflow-scm-step-plugin Component/s: workflow-cps-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-38821) Global library class calling another global libraries static method fails
Title: Message Title Jesse Glick resolved as Duplicate I am afraid constructors need to be marked @NonCPS. Jenkins / JENKINS-38821 Global library class calling another global libraries static method fails Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-38824) Nullpointer when trying to use params global variable
Title: Message Title Jesse Glick resolved as Incomplete Steps to reproduce from scratch? Log output? Jenkins / JENKINS-38824 Nullpointer when trying to use params global variable Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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-38720) 500 Server Error when notifying master of new mercurial commit: "Response header too large"
Title: Message Title Jesse Glick commented on JENKINS-38720 Re: 500 Server Error when notifying master of new mercurial commit: "Response header too large" Well, then you just have a huge number of jobs all using the same repository, I guess? So MercurialStatus needs to be patched to cap the number of job names it will enumerate in its header. 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-38720) 500 Server Error when notifying master of new mercurial commit: "Response header too large"
Title: Message Title Nick Sonneveld commented on JENKINS-38720 Re: 500 Server Error when notifying master of new mercurial commit: "Response header too large" Jesse Glick hah, I know. It was my attempt to de-identify the logs. They are all unique job names however. 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-35698) Initial run of parameterized pipeline build should return properties default value
Title: Message Title Jesse Glick updated JENKINS-35698 Jenkins / JENKINS-35698 Initial run of parameterized pipeline build should return properties default value Change By: Jesse Glick 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-35698) Initial run of parameterized pipeline build should return properties default value
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35698 Re: Initial run of parameterized pipeline build should return properties default value Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/cps/ParamsVariable.java src/main/resources/org/jenkinsci/plugins/workflow/cps/ParamsVariable/help.jelly http://jenkins-ci.org/commit/workflow-cps-plugin/0161aecc2877ec4c7086c1bce7d0c69f42e6c267 Log: [FIXED JENKINS-35698] Make params offer default parameter values from the current definition as a fallback. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked, but branches names are now stripped (I'm ok with that).For the record, in my case, it was failing to create install packages in a python * virtualenv inside working directory * (path too long), during {{pip install -r requirements.txt}}:{code}bad interpreter: Permission denied{code}Before plugin update {color:green}(was working, 56 characters){color}:{code}/var/lib/jenkins/workspace/project/project/master@script{code}After update {color:red}(failing, 109 characters){color}:{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E@script{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this {color:green}(working, 88 characters){color}:{code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked, but branches names are now stripped (I'm ok with that). For the record, in my case, it was failing to create a python virtualenv inside working directory (path too long), during {{pip install -r requirements.txt}}:{code}bad interpreter: Permission denied{code} Before plugin update {color:green}(was working, 56 characters){color}:{code}/var/lib/jenkins/workspace/project/project/master@script{code}After update {color:red}(failing, 109 characters){color}:{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E@script{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this {color:green}(working, 88 characters){color}:{code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked . Branches , but branches names are now stripped Instead (I'm ok with that) .Before plugin update {color:green}(was working, 56 characters){color}:{code}/var/lib/jenkins/workspace/project/project/master@script{code}After update {color:red}(failing, 109 characters){color}:{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E@script{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this {color:green}(working, 88 characters){color}:{code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked. Branches names are now strippedInstead.Before plugin update {color:green} (was working , 56 characters ) {color} :{code}/var/lib/jenkins/workspace/project/project/ branch_name master @script{code}After update {color:red} (failing , 109 characters ) {color} :{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E@script{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this {color : green}(working, 88 characters){color}: {code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked. Branches names are now strippedInstead.Before plugin update (was working):{code}/var/lib/jenkins/workspace/project/project/branch_name@script{code}After update (failing):{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E @script {code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this:{code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked. Branches names are now strippedInstead.Before plugin update (was working):{code}/var/lib/jenkins/workspace/project/project/branch_name@script{code}After update (failing):{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this:{code} /var/lib/jenkins/workspace/ r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Gabriel Le Breton commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I updated my plugins recently and my builds stopped working. I tried Jesse Glick's suggestion and it worked. Branches names are now stripped Instead. Before plugin update (was working): /var/lib/jenkins/workspace/project/project/branch_name@script After update (failing): /var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E Adding the following line to /etc/default/jenkins: JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30" Results in this: r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash. In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too: /j folder, as opposed to /var/lib/jenkins. But not quite sure what's the best way to achieve this. Related SO Questions: http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-build http://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux Add Comment
[JIRA] (JENKINS-20718) Add Documentation and help for startup-trigger-plugin
Title: Message Title Emory Penney commented on JENKINS-20718 Re: Add Documentation and help for startup-trigger-plugin With the exception of one missing help button which has been fixed in GitHub I believe this issue has been addressed. Danny Staple, do you have any objections to me marking this issue resolved? 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-36614) Ignoring specific files or commit strings for change detection required
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-36614 Ignoring specific files or commit strings for change detection required Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35535) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Title: Message Title Jesse Glick commented on JENKINS-35535 Re: Upgrade to Credentials 2.1.0+ API for populating credentials drop-down While here, might as well implement retrieve(String revision, TaskListener) and retrieveRevisions and relax dropdowns as in git PR 437. 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-33241) Mercurial branches with spaces not correctly escaped getting changelog
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-33241 Mercurial branches with spaces not correctly escaped getting changelog Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37274) mercurial changelog displays changes from previous commit but not current
Title: Message Title Jesse Glick resolved as Not A Defect Text printed to the build log is not the changelog. This is just incidental output from some calculations the plugin is doing. To avoid confusion I can make it less chatty. Jenkins / JENKINS-37274 mercurial changelog displays changes from previous commit but not current Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-20718) Add Documentation and help for startup-trigger-plugin
Title: Message Title Emory Penney started work on JENKINS-20718 Change By: Emory Penney Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37384) Changes view issues using Mercurial with Multibranch pipeline
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-37384
Changes view issues using Mercurial with Multibranch pipeline
Change By:
Jesse Glick
I've created a pipeline multibranch project with mercurial repo as a source, build configuration set in {{ Jenkinsfile }} in repo and set to build periodically to poll the repo every two minutes (H/2). The first step inside {{ Jenkinsfile }} is _checkout scm_ {{checkout scm}} .It seems that for newly created branches (that have only one commit) the changes view is totally empty. On the other hand, when there are more commits it seems that they are logged twice (see screenshot below).!Zrzut ekranu z 2016-08-12 o 21.48.08.png|thumbnail!This looks like a similar issue to https://issues.jenkins-ci.org/browse/ JENKINS-30491 or https://issues.jenkins-ci.org/browse/ JENKINS-31079 yet this time it happens with mercurial instead of git.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because
[JIRA] (JENKINS-38702) AccuRev for Jenkins Plugin does not display Depots
Title: Message Title Joseph Petersen commented on JENKINS-38702 Re: AccuRev for Jenkins Plugin does not display Depots Peter Lingesso Peter, could you please try the following build, it attempts to override ACCUREV_HOME for both master and slaves with the respective root directory for each machine set inside Jenkins. How to install: http://YOURJENKINSSERVER:8080/pluginManager/advanced - At Upload Plugin, choose the downloaded file and hit upload! Direct link: https://jenkins.ci.cloudbees.com/job/plugins/job/accurev-plugin/144/org.jenkins-ci.plugins$accurev/artifact/org.jenkins-ci.plugins/accurev/0.7.3-SNAPSHOT/accurev-0.7.3-SNAPSHOT.hpi Below I linked the build, if you question the direct link. Download the .hpi file Link to actual build: https://jenkins.ci.cloudbees.com/job/plugins/job/accurev-plugin/144/org.jenkins-ci.plugins$accurev/ 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-37384) Changes view issues using Mercurial with Multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-37384 Re: Changes view issues using Mercurial with Multibranch pipeline Probably the same basic cause as JENKINS-29326. 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-37384) Changes view issues using Mercurial with Multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-37384 Re: Changes view issues using Mercurial with Multibranch pipeline for newly created branches (that have only one commit) the changes view is totally empty JENKINS-33274 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.
