[cross-project-issues-dev] Disk usage report for Hudson/Build
Compiled 2015-05-20T12:07 build.eclipse.org - Usage exceeding 1GB for: Hudson master jobs and workspace (2015-05-20T10:00) 4.2G gef4-master 2.8G papyrus-trunk-nightly 2.3G ep45I-unit-lin64 1.7G ep45N-unit-lin64 1.6G emf-cdo-integration 1.5G ep45N-unit-mac64 1.5G ep45I-unit-win32 1.5G ep45I-unit-mac64 1.5G ep45N-unit-win32 1.5G ep44M-unit-lin64 1.4G ep44M-unit-mac64 1.4G ep44M-unit-win32 1.3G mdt-uml2-master 1.2G m2m-atl-master 1.1G mylyn-release - Usage exceeding 1GB for: /shared (1000G capacity) (2015-05-20T10:00) 349.8G hipp 126.6G rt 61.5G eclipse 46.7G jobs 43.1G technology 27.6G webtools 23.1G SLES 17.3G common 12.2G tools 11.2G simrel 8.3G orbit 6.7G cbi-ng 5.6G modeling 1.6G mylyn 1.4G cbi 1.4G soa - Usage exceeding 1GB for: /shared/modeling 3.1G build - Usage exceeding 1GB for: /shared/tools 4.6G tm 3.0G objectteams 1.4G mtj 1.2G windowbuilder 1.1G aspectj - Usage exceeding 1GB for: /shared/technology 18.6G epp 11.1G sapphire 4.8G stem 2.4G cosmos 2.1G babel 1.6G m2e END: build.eclipse.org hudson-slave1.eclipse.org /dev/xvda1158G 52G 106G 33% / - Usage exceeding 1GB for: Hudson workspace on hudson-slave1 (50G capacity) (2015-05-19T21:00) 17.0G mihini-nightly 3.2G koneki-ldt 2.9G koneki-ldt-maintenance 1.5G skalli 1.3G gef-master 1.1G tycho-mtj-nightly END: hudson-slave1.eclipse.org hudson-slave2.eclipse.org - Usage exceeding 1GB for: END: hudson-slave2.eclipse.org hudson-slave3.eclipse.org /dev/xvda1 55G 32G 24G 58% / - Usage exceeding 1GB for: Hudson workspace on hudson-slave3 (50G capacity) (2015-05-19T18:00) END: hudson-slave3.eclipse.org ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] When are Gerrit commits automatically applied?
I'm not sure what's the goal here? Enable submit-to-gerrit-and-leave - without awaiting the result from hudson? ;P If you wait for success, what harm is done by having to do two more clicks? my 2c. Stephan On 05/20/2015 07:44 AM, Eike Stepper wrote: Hi, I'm not a Gerrit expert, but a quick search for gerrit auto approve gives a number of hints, for example a Gerrit hook script: http://renier.morales-rodriguez.net/post/49144483266/configuring-gerrit-to-auto-submit-on-patch-ap Personally I'd also like it if my simrel patch sets would be submitted automatically if Hudson gives a +1, but I'm not sure if that's a security concern. Cheers /Eike http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper Am 18.05.2015 um 19:24 schrieb Mickael Istria: On 05/18/2015 06:43 PM, David M Williams wrote: I don't know the answer to Sven's question ... quoted here ... does anyone else? Am I right if committer of the org.eclipse.simrel.build Git repo must be manually set them as code reviewer if they want to apply the patch to the Git repo? I've hoped that the push is automatically done if the Hudson build is successful and a fast forward merge is possible. I would hope that it would be applied automatically ... but, from my experience it doesn't seem to be. But, I've only done it a few times, and hope a more Gerrit knowledgeable person can answer authoritatively ... as well as make sure the right thing happens, if it takes a new bug for webmasters or others to change some setting. Gerrit requires a manual approval from a Simrel committer to merge a commit. There is no mechanism to automatically merge a review if automated tests have succeeded; and since I believe the paradigm of Gerrit and code-review is really to involve an additional human step (in best case a 3rd-party) in the change, automating merge is probably not something desirable. However, as a committer, you can apply your own patch via Gerrit UI, or push without using a Gerrit review (and automated tests). https://wiki.eclipse.org/index.php?title=Simrel/Contributing_to_Simrel_Aggregation_Build#Pushing_your_changes HTH -- Mickael Istria Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools My blog http://mickaelistria.wordpress.com - My Tweets http://twitter.com/mickaelistria ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] When are Gerrit commits automatically applied?
On 05/21/2015 12:11 AM, Konstantin Komissarchik wrote: [...] but once that verification has been done, what's the value of waiting for the developer to click on things? Maybe encouraging the developer to wait until s/he knows whether the job is done or not? :) Disclaimer: as much as I like gerrit, for simrel contributions I still prefer running the validation at home and then push directly .. Call me I'm old-school, if you like. Stephan -Original Message- From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Stephan Herrmann Sent: Wednesday, May 20, 2015 2:42 PM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] When are Gerrit commits automatically applied? I'm not sure what's the goal here? Enable submit-to-gerrit-and-leave - without awaiting the result from hudson? ;P If you wait for success, what harm is done by having to do two more clicks? my 2c. Stephan On 05/20/2015 07:44 AM, Eike Stepper wrote: Hi, I'm not a Gerrit expert, but a quick search for gerrit auto approve gives a number of hints, for example a Gerrit hook script: http://renier.morales-rodriguez.net/post/49144483266/configuring-gerri t-to-auto-submit-on-patch-ap Personally I'd also like it if my simrel patch sets would be submitted automatically if Hudson gives a +1, but I'm not sure if that's a security concern. Cheers /Eike http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper Am 18.05.2015 um 19:24 schrieb Mickael Istria: On 05/18/2015 06:43 PM, David M Williams wrote: I don't know the answer to Sven's question ... quoted here ... does anyone else? Am I right if committer of the org.eclipse.simrel.build Git repo must be manually set them as code reviewer if they want to apply the patch to the Git repo? I've hoped that the push is automatically done if the Hudson build is successful and a fast forward merge is possible. I would hope that it would be applied automatically ... but, from my experience it doesn't seem to be. But, I've only done it a few times, and hope a more Gerrit knowledgeable person can answer authoritatively ... as well as make sure the right thing happens, if it takes a new bug for webmasters or others to change some setting. Gerrit requires a manual approval from a Simrel committer to merge a commit. There is no mechanism to automatically merge a review if automated tests have succeeded; and since I believe the paradigm of Gerrit and code-review is really to involve an additional human step (in best case a 3rd-party) in the change, automating merge is probably not something desirable. However, as a committer, you can apply your own patch via Gerrit UI, or push without using a Gerrit review (and automated tests). https://wiki.eclipse.org/index.php?title=Simrel/Contributing_to_Simre l_Aggregation_Build#Pushing_your_changes HTH -- Mickael Istria Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools My blog http://mickaelistria.wordpress.com - My Tweets http://twitter.com/mickaelistria ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] When are Gerrit commits automatically applied?
Umm... As software guys, our raison d'etre is to rid the world of manual steps wherever we see them. :) If I squint just right, I can sort of see the reason that Hudson is a useful contributor to the process here (see my prior objections), but once that verification has been done, what's the value of waiting for the developer to click on things? - Konstantin -Original Message- From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Stephan Herrmann Sent: Wednesday, May 20, 2015 2:42 PM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] When are Gerrit commits automatically applied? I'm not sure what's the goal here? Enable submit-to-gerrit-and-leave - without awaiting the result from hudson? ;P If you wait for success, what harm is done by having to do two more clicks? my 2c. Stephan On 05/20/2015 07:44 AM, Eike Stepper wrote: Hi, I'm not a Gerrit expert, but a quick search for gerrit auto approve gives a number of hints, for example a Gerrit hook script: http://renier.morales-rodriguez.net/post/49144483266/configuring-gerri t-to-auto-submit-on-patch-ap Personally I'd also like it if my simrel patch sets would be submitted automatically if Hudson gives a +1, but I'm not sure if that's a security concern. Cheers /Eike http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper Am 18.05.2015 um 19:24 schrieb Mickael Istria: On 05/18/2015 06:43 PM, David M Williams wrote: I don't know the answer to Sven's question ... quoted here ... does anyone else? Am I right if committer of the org.eclipse.simrel.build Git repo must be manually set them as code reviewer if they want to apply the patch to the Git repo? I've hoped that the push is automatically done if the Hudson build is successful and a fast forward merge is possible. I would hope that it would be applied automatically ... but, from my experience it doesn't seem to be. But, I've only done it a few times, and hope a more Gerrit knowledgeable person can answer authoritatively ... as well as make sure the right thing happens, if it takes a new bug for webmasters or others to change some setting. Gerrit requires a manual approval from a Simrel committer to merge a commit. There is no mechanism to automatically merge a review if automated tests have succeeded; and since I believe the paradigm of Gerrit and code-review is really to involve an additional human step (in best case a 3rd-party) in the change, automating merge is probably not something desirable. However, as a committer, you can apply your own patch via Gerrit UI, or push without using a Gerrit review (and automated tests). https://wiki.eclipse.org/index.php?title=Simrel/Contributing_to_Simre l_Aggregation_Build#Pushing_your_changes HTH -- Mickael Istria Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools My blog http://mickaelistria.wordpress.com - My Tweets http://twitter.com/mickaelistria ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] When are Gerrit commits automatically applied?
What's the value in encouraging the developer to wait until verification is done? Either, it's critical that the contribution goes in, in which case the developer will wait anyway, or it's not critical and any failures can be dealt with tomorrow. - Konstantin PS: Personally, I'd like to see gerrit/hudson style automated verification combined with bullet-proof aggregation process that is not susceptible to contributed repositories changing from underneath it. -Original Message- From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Stephan Herrmann Sent: Wednesday, May 20, 2015 3:23 PM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] When are Gerrit commits automatically applied? On 05/21/2015 12:11 AM, Konstantin Komissarchik wrote: [...] but once that verification has been done, what's the value of waiting for the developer to click on things? Maybe encouraging the developer to wait until s/he knows whether the job is done or not? :) Disclaimer: as much as I like gerrit, for simrel contributions I still prefer running the validation at home and then push directly .. Call me I'm old-school, if you like. Stephan -Original Message- From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Stephan Herrmann Sent: Wednesday, May 20, 2015 2:42 PM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] When are Gerrit commits automatically applied? I'm not sure what's the goal here? Enable submit-to-gerrit-and-leave - without awaiting the result from hudson? ;P If you wait for success, what harm is done by having to do two more clicks? my 2c. Stephan On 05/20/2015 07:44 AM, Eike Stepper wrote: Hi, I'm not a Gerrit expert, but a quick search for gerrit auto approve gives a number of hints, for example a Gerrit hook script: http://renier.morales-rodriguez.net/post/49144483266/configuring-gerr i t-to-auto-submit-on-patch-ap Personally I'd also like it if my simrel patch sets would be submitted automatically if Hudson gives a +1, but I'm not sure if that's a security concern. Cheers /Eike http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper Am 18.05.2015 um 19:24 schrieb Mickael Istria: On 05/18/2015 06:43 PM, David M Williams wrote: I don't know the answer to Sven's question ... quoted here ... does anyone else? Am I right if committer of the org.eclipse.simrel.build Git repo must be manually set them as code reviewer if they want to apply the patch to the Git repo? I've hoped that the push is automatically done if the Hudson build is successful and a fast forward merge is possible. I would hope that it would be applied automatically ... but, from my experience it doesn't seem to be. But, I've only done it a few times, and hope a more Gerrit knowledgeable person can answer authoritatively ... as well as make sure the right thing happens, if it takes a new bug for webmasters or others to change some setting. Gerrit requires a manual approval from a Simrel committer to merge a commit. There is no mechanism to automatically merge a review if automated tests have succeeded; and since I believe the paradigm of Gerrit and code-review is really to involve an additional human step (in best case a 3rd-party) in the change, automating merge is probably not something desirable. However, as a committer, you can apply your own patch via Gerrit UI, or push without using a Gerrit review (and automated tests). https://wiki.eclipse.org/index.php?title=Simrel/Contributing_to_Simr e l_Aggregation_Build#Pushing_your_changes HTH -- Mickael Istria Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools My blog http://mickaelistria.wordpress.com - My Tweets http://twitter.com/mickaelistria ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your
[cross-project-issues-dev] Mars RC1 Staging repository is done
Please test the usual location: http://download.eclipse.org/releases/staging/ A couple of caveats. 1. WindowBuilder is not in there. There were issues with some of their packed jars, and as I understand it they had trouble with their build system recently, and while we have exchanged a few emails about things they can and plan to do, I have not heard anything for a week or so, so not positive exactly where things stand. 2. Some of the links in the repo report are broken. I saw this a few days ago, and always assumed I would be able to fix them up by hand, but now, due to other issues, discovered I can not. The most important broken one, is the unsigned report. It's correct URL (temporarily) needs an '8' added: http://download.eclipse.org/releases/staging/buildInfo/reporeports/reports/verifydiroutput/unsigned8.txt Assuming no blocking issues are discovered, I'll add this to the composite repo at .../releases/mars approximately 10 AM Friday (Eastern). Thanks all! ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
