[JIRA] (JENKINS-21422) Jenkins crashing due to out of memory when rebuilding jobs
Title: Message Title Marc Popp commented on JENKINS-21422 Re: Jenkins crashing due to out of memory when rebuilding jobs As a temp. workaround: We increased the JavaVM's Memory to 2G and did not run in the problem very often anymore. 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] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Marc Popp updated JENKINS-26210 Configure Jobs to be hidden from the delivery pipeline Change By: Marc Popp (15/Feb/15 8:52 AM) Description: ItwouldbecooltobeabletoconfigureJobstobehiddenfromthedeliverypipeline.Ihavetheproblem,thatIhavemultipleDeployJobswhichareallusingthesameparameterizedMultiJob.TheSub-TasksoftheMultiJobaredisplayedtotallyoutoforderand are notimportantforthehighlevelpipelineview. 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] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Marc Popp commented on JENKINS-26210 Configure Jobs to be hidden from the delivery pipeline I have a multijob 'Deploy' that is called with parameters to deploy a host. It looks like that: Name: Deploy - Phase 1 - Job Step 1 - Phase 2 - Job Step 2 - Job Step 3 Then I have one multijob per host, that calls the common multijob 'Deploy' with parameters: Deploy_XYZ - Phase 1 - Call Parameterised Job: Deploy If I create the pipeline for one job everything is fine: Deploy_XYZ - Deploy -+- Step 1 | +- Step 2 | +- Step 3 Also, in the the pipeline view I'm not interested in the common multijob 'Deploy' and the Steps, but just something like: +-+ +-+ | ENV - QS|--| ENV - PROD | | Deploy_XYZ1 | | Deploy_ABC1 | | Deploy_XYZ2 | | Deploy_ABC2 | | Deploy_XYZ3 | | Deploy_ABC3 | +-+ +-+ I've attached a screenshot of how the pipeline looks like, with 2 ENVs and 1 Deploy Job each. 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] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Marc Popp updated JENKINS-26210 Configure Jobs to be hidden from the delivery pipeline Screenshot with 2 ENVs and 1 Deploy Job each. Change By: Marc Popp (15/Feb/15 9:23 AM) Attachment: ScreenShot2015-02-15at10.19.23.png 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] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Marc Popp updated JENKINS-26210 Configure Jobs to be hidden from the delivery pipeline Change By: Marc Popp (23/Dec/14 11:03 AM) Description: ItwouldbecooltobeabletoconfigureJobstobehiddenfromthedeliverypipeline.Ihavetheproblem,thatIhavemultipleDeployJobswhichareallusingthesameparameterizedMultiJob.TheSub-TasksoftheMultiJobaredisplayedtotallyoutoforder andnotimportantforthehighlevelpipelineview . 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] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Marc Popp created JENKINS-26210 Configure Jobs to be hidden from the delivery pipeline Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 23/Dec/14 11:02 AM Description: It would be cool to be able to configure Jobs to be hidden from the delivery pipeline. I have the problem, that I have multiple Deploy Jobs which are all using the same parameterized MultiJob. The Sub-Tasks of the MultiJob are displayed totally out of order. Project: Jenkins Priority: Minor Reporter: Marc Popp 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] [jenkins-multijob-plugin] (JENKINS-24612) Add the feature to re-run (resume) failed builds
Marc Popp created JENKINS-24612 Add the feature to re-run (resume) failed builds Issue Type: New Feature Assignee: Unassigned Components: jenkins-multijob-plugin Created: 06/Sep/14 11:53 AM Description: I know that feature from Atlassian Bamboo. It is extremly helpful in environments with big multi job projects, that run for several hours. Project: Jenkins Labels: plugin Priority: Major Reporter: Marc Popp 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] [jenkins-multijob-plugin] (JENKINS-24612) Add the feature to re-run (resume) failed builds in a MultiJob Project
Marc Popp updated JENKINS-24612 Add the feature to re-run (resume) failed builds in a MultiJob Project Change By: Marc Popp (06/Sep/14 11:56 AM) Summary: Addthefeaturetore-run(resume)failedbuilds inaMultiJobProject 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] [jenkins-multijob-plugin] (JENKINS-24612) Add the feature to re-run (resume) failed builds in a MultiJob Project
Marc Popp updated JENKINS-24612 Add the feature to re-run (resume) failed builds in a MultiJob Project Change By: Marc Popp (06/Sep/14 5:22 PM) Description: IknowthatfeaturefromAtlassianBamboo.Itisextremlyhelpfulinenvironmentswithbigmultijobprojects,thatrunforseveralhours. Acceptancecriteria:*ButtoninMultiJobDetailViewtore-run(resume)failedsteps*re-run(resume)failedstepsmeansthatallfailedorunstablebuildsshouldbestartedagainwiththesameparameterastheinitialbuild. 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.
