[JIRA] (JENKINS-53888) Batch step running on a node other than the master fails
Title: Message Title mishal shah edited a comment on JENKINS-53888 Re: Batch step running on a node other than the master fails Started seeing this after updating Pipeline: Nodes and Processes (2.22 -> 2.24) and Durable Task Plugin (1.25 -> 1.26). ERROR: script apparently exited with code 0 but asynchronous notification was lost Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53888) Batch step running on a node other than the master fails
Title: Message Title mishal shah commented on JENKINS-53888 Re: Batch step running on a node other than the master fails Started seeing this after updating Pipeline: Nodes and Processes (2.22 -> 2.24) and Durable Task Plugin (1.25 -> 1.26). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41600) Parallel step running forever if too much console output is logged
Title: Message Title mishal shah commented on JENKINS-41600 Re: Parallel step running forever if too much console output is logged Joerg Schwaerzler Did you find a workaround for this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44483) Large console logs cause infinite loops in slave
Title: Message Title mishal shah commented on JENKINS-44483 Re: Large console logs cause infinite loops in slave is there any workaround to this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38381) Optimize log handling in Pipeline and Durable Task
Title: Message Title mishal shah commented on JENKINS-38381 Re: Optimize log handling in Pipeline and Durable Task Jesse Glick Do you know when this will be released? We are also seeing infinite log issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title mishal shah commented on JENKINS-43038 Re: Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins Renjith Pillai Did you find a workaround for the x4 slowness? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility
Title: Message Title mishal shah commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility What is the current status of this issue? This is major issue, can we change the priority? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42032) Support for Pull request testing by trigger
Title: Message Title mishal shah commented on JENKINS-42032 Re: Support for Pull request testing by trigger Another reason why trigger base PR is important. https://twitter.com/paaleksey/status/833353340079706112 "TIL: There are bots on Github that create pull requests to projects using CI replacing all code with bitcoin-mining code." - paaleksey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title mishal shah commented on JENKINS-39343 Re: Persistent search/overviews/filtered views This would be really useful, when Jenkins has 20+ jobs. It would be great if this could be priorities. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42038) Blue Ocean - Views/Folders to organizes jobs
Title: Message Title mishal shah created an issue Jenkins / JENKINS-42038 Blue Ocean - Views/Folders to organizes jobs Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/14 10:18 PM Environment: Jenkins 2.32.2 Blue Ocean 1.0-b23 Priority: Minor Reporter: mishal shah Blue Ocean shows all of the jobs, it makes it hard to look at sub groups. For Example, infrastructure jobs. Views in classic makes much easier to find jobs, also look at overall status of sub group by filtering the jobs. Search is useful but having to remember all of the job name is hard. Add Comment
[JIRA] (JENKINS-42035) Blue Ocean - Button to go between classic and blue ocean view.
Title: Message Title mishal shah created an issue Jenkins / JENKINS-42035 Blue Ocean - Button to go between classic and blue ocean view. Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/14 9:58 PM Environment: Jenkins 2.32.2 Blue Ocean 1.0-b23 Priority: Minor Reporter: mishal shah Blue Ocean should have a button to go back to classic view, so user are not stuck on blue ocean UI only. Currently, I have to modify the URL to change the view between blue ocean and classic view. I might have missed a button somewhere, please let me know if this already exist. Add Comment
[JIRA] (JENKINS-42032) Support for Pull request testing by trigger
Title: Message Title mishal shah created an issue Jenkins / JENKINS-42032 Support for Pull request testing by trigger Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/14 7:30 PM Environment: Jenkins 2.32.2 Priority: Minor Reporter: mishal shah I am not sure which component this should be assigned to, please feel free to move it to right component. Pull request testing is important to our project, and we are currently using Github Pull request builder plugin https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin. However, this plugin has not be updated recently because it up for adoption. Blue Ocean team has been working on pull request feature and it would be key to have following features available for us to use the new PR feature. 1. Pull request should not automatically start, it must be triggered by user in whitelist. 2. Whitelist - Users with Commit access to the repo, specific org and specific users. 3. Status check should be made for pending, building, finished. 4. Pull request trigger should be able to request test and merge. 5. Pull request testing should be aborted soon as new commit has been made to the PR. 6. Pull request testing should be able to make comment on the PR once completed. 7. Multiple trigger support for each repository. Example: Please test macOS Please test Linux Please test Please smoke test macOS. Here is example of what swift project does. https://github.com/apple/swift/blob/master/docs/ContinuousIntegration.md#pull-request-testing
[JIRA] (JENKINS-41830) SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Title: Message Title mishal shah updated an issue Jenkins / JENKINS-41830 SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job Change By: mishal shah Component/s: git-changelog-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-41830) SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Title: Message Title mishal shah commented on JENKINS-41830 Re: SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job Paul Wellner Bou I was not sure which component this should be assigned to, I will move it to git-plugin. 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-41830) SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Title: Message Title mishal shah updated an issue Jenkins / JENKINS-41830 SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job Change By: mishal shah Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41830) SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Title: Message Title mishal shah updated an issue Jenkins / JENKINS-41830 SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job Change By: mishal shah Attachment: Screen Shot 2017-02-09 at 5.06.22 PM.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-41781) Support multiple parallels within a stage in the Pipeline Visualization
Title: Message Title mishal shah commented on JENKINS-41781 Re: Support multiple parallels within a stage in the Pipeline Visualization Michael Neale Yes, this sounds closer to what I was looking for. https://issues.jenkins-ci.org/browse/JENKINS-38442 is lot more complex but it would work too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41830) SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Title: Message Title
mishal shah updated an issue
Jenkins / JENKINS-41830
SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Change By:
mishal shah
Build page contain same change list multiple times, when using parallel in pipeline. {code:java} ``` parallel ("test1" : { checkout([$class: 'GitSCM', branches: [[ name: 'master' ]], doGenerateSubmoduleConfigurations: false, extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'test1' ],[ $class: 'ScmName', name: 'test1' ]], submoduleCfg: [], userRemoteConfigs: [[ credentialsId: 'test', url: 'ssh://g...@github.com/test1' ]]])},"test2" : { checkout([$class: 'GitSCM', branches: [[ name: 'master' ]], doGenerateSubmoduleConfigurations: false, extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'test2' ],[ $class: 'ScmName', name: 'test2' ]], submoduleCfg: [], userRemoteConfigs: [[ credentialsId: 'test', url: 'ssh://g...@github.com/test2' ]]]) },"test3" : { checkout([$class: 'GitSCM', branches: [[ name: 'master' ]], doGenerateSubmoduleConfigurations: false, extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'test3' ],[ $class: 'ScmName', name: 'test3' ]], submoduleCfg: [], userRemoteConfigs: [[ credentialsId: 'test', url: 'ssh://g...@github.com/test3' ]]]) } ){code}
[JIRA] (JENKINS-41830) SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Title: Message Title
mishal shah created an issue
Jenkins / JENKINS-41830
SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Issue Type:
Bug
Assignee:
Paul Wellner Bou
Components:
git-changelog-plugin
Created:
2017/Feb/08 12:58 AM
Environment:
Jenkins 2.32.2
Priority:
Major
Reporter:
mishal shah
Build page contain same change list multiple times, when using parallel in pipeline.
```
parallel (
"test1" : {
checkout([
$class: 'GitSCM',
branches: [[
name: 'master'
]],
doGenerateSubmoduleConfigurations: false,
extensions: [[
$class: 'RelativeTargetDirectory',
relativeTargetDir: 'test1'
],[
$class: 'ScmName',
name: 'test1'
]],
submoduleCfg: [],
userRemoteConfigs: [[
credentialsId: 'test',
url: 'ssh://g...@github.com/test1'
]]
])
},
"test2" : {
checkout([
$class: 'GitSCM',
branches: [[
name: 'master'
]],
doGenerateSubmoduleConfigurations: false,
extensions: [[
$class: 'RelativeTargetDirectory',
[JIRA] (JENKINS-41829) Blue Ocean - Add node name for each stage
Title: Message Title mishal shah created an issue Jenkins / JENKINS-41829 Blue Ocean - Add node name for each stage Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/08 12:46 AM Environment: Jenkins 2.32.2 Priority: Minor Reporter: mishal shah Blue Ocean UI should display information about which node it executed the stage on. Add Comment
[JIRA] (JENKINS-41781) Blue Ocean - UI support for multiple build and test in parallel
Title: Message Title mishal shah created an issue Jenkins / JENKINS-41781 Blue Ocean - UI support for multiple build and test in parallel Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2017-02-06 at 6.16.53 PM.png Components: blueocean-plugin Created: 2017/Feb/07 2:23 AM Environment: Jenkins 2.32.2 Priority: Minor Reporter: mishal shah Add support in the UI to handle multiple build in parallel. Please see attached screen shot. Add Comment
[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.
Title: Message Title mishal shah commented on JENKINS-41717 Re: Blue Ocean - Steps section should show full log for given step. Thanks James Dumay! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.
Title: Message Title mishal shah commented on JENKINS-41717 Re: Blue Ocean - Steps section should show full log for given step. James Dumay Is it possible to increases the priority of JENKINS-40526? 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-41718) Support Build Failure Analyzer with Blue Ocean
Title: Message Title mishal shah created an issue Jenkins / JENKINS-41718 Support Build Failure Analyzer with Blue Ocean Issue Type: Bug Assignee: Tomas Westling Components: blueocean-plugin, build-failure-analyzer-plugin Created: 2017/Feb/03 10:43 PM Environment: Jenkins 2.32.2 Priority: Minor Reporter: mishal shah Provide build failure information analyzed by the plugin in Blue Ocean UI. Add Comment
[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.
Title: Message Title mishal shah updated an issue Jenkins / JENKINS-41717 Blue Ocean - Steps section should show full log for given step. Change By: mishal shah Summary: Blue Ocean - Steps section should show full log for the given step. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for the given step.
Title: Message Title mishal shah created an issue Jenkins / JENKINS-41717 Blue Ocean - Steps section should show full log for the given step. Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/03 10:14 PM Environment: Jenkins 2.32.2 BlueOcean 1.0.0-b21 Priority: Major Reporter: mishal shah "Show complete log" button will take me to plain text and it really hard to parse the information when pipeline steps are executed in parallel. Blue Ocean makes it easy to see steps with the UI diagram but truncating the log makes it impossible to find the error inside of blue ocean UI. Going into pain text requires downloading the logs and parsing the information by cat | grep "[stage name]" this makes it really difficult to find issues. Add Comment
[JIRA] [build-failure-analyzer-plugin] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
mishal shah reopened JENKINS-17658 Provide a token so that build failure causes can be included in build failure emails is it possible to change the order in which BFA runs? I am not able to send out email with BFA info because BFA runs after email plugin is triggered. Change By: mishal shah (07/Nov/14 10:08 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
mishal shah commented on JENKINS-17658 Provide a token so that build failure causes can be included in build failure emails is it possible to change the order in which BFA runs? I am not able to send out email with BFA info because BFA runs after email plugin is triggered. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
