Re: [cross-project-issues-dev] Trying to aggregate source features using b3 aggregator editor
opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=408786
As a workaround, you could disable binary feature inclusion using
plugin
groupIdorg.eclipse.tycho.extras/groupId
artifactIdtycho-source-feature-plugin/artifactId
version${tycho-version}/version
configuration
includeBinaryFeaturefalse/includeBinaryFeature
/configuration
/plugin
(since tycho 0.17.0 [1])
Regards
Jan
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=401420
-Original Message-
From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Jeff Johnston
Sent: Mittwoch, 22. Mai 2013 18:51
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Trying to aggregate source features
using b3 aggregator editor
Thanks David,
I think you nailed it. We are using tycho-extras to generate the source
features from the regular features. It isn't propagating the filters.
Each generated source feature has an include of the regular feature in it.
-- Jeff J.
On 05/21/2013 09:37 PM, David M Williams wrote:
Off hand, I'd guess related to filters. I've not looked in detail, but
nothing obviously wrong with your file or repo. But ... for filters,
it's complicated to get them right for everything ... and sure you'd
want your source filtered, or might not display in all standalone
info servers (not sure about that ... just saying, should be tested).
But, back to filters ...
Just to give an example,
Let's say
org.eclipse.linuxtools.callgraph.feature.feature.group
installs in a aggregator just fine. That means it an all its bundles
have a matching set of features, say to limit installation on to linux
only platforms.
Now, if when your source is added
org.eclipse.linuxtools.callgraph.feature.source.feature.group
It may report can not find
org.eclipse.linuxtools.callgraph.feature.feature.group but what it may
really mean (or, should say) is
can not find [it] while trying to install [source.group] for windows.
So, that's just a thought ... make sure your source features/bundles
have all the same filters as your code (since ... your source requires
your code ... which is a bit odd anyway, but maybe a separate issues).
HTH
From: Jeff Johnston jjohn...@redhat.com
To: Cross project issues cross-project-issues-dev@eclipse.org,
Date: 05/21/2013 02:53 PM
Subject: [cross-project-issues-dev] Trying to aggregate source features
using b3 aggregator editor
Sent by: cross-project-issues-dev-boun...@eclipse.org
I am trying to add the Linux Tools source features (without categories)
so end-users can install them if desired.
When I add these features to the linuxtools.b3aggrcon file, I am getting
an error trying to validate the aggregation. The source features
require the normal features and the b3 aggregator editor is saying that
the feature is missing.
The missing feature in question is also in the b3aggrcon file (with
category) and is found when validating the repository. If I remove the
source features, the aggregation validates fine.
Below is the actual message. Is there something wrong with our repo or
is it a known issue with the b3 aggregator editor trying to have new
feature groups requiring other new feature groups?
I have attached the b3aggrcon file for reference.
-- Jeff J.
===
Cannot complete the install because one or more required items could not
be found.
Missing requirement: C/C++ Call Graph Visualization Developer Resources
1.1.0.201305211237
(org.eclipse.linuxtools.callgraph.feature.source.feature.group
1.1.0.201305211237) requires
'org.eclipse.linuxtools.callgraph.feature.feature.group
[1.1.0.201305211237]' but it could not be found
InstallableUnit(org.eclipse.linuxtools.callgraph.feature.feature.group
[1.1.0.201305211237,1.1.0.201305211237]) is required by:
ValidationSet(main)
Contribution(Linux Tools)
MappedRepository(http://download.eclipse.org/linuxtools/update-kepler-rc1)
Feature(org.eclipse.linuxtools.callgraph.feature.source.feature.group
1.1.0.201305211237)
[attachment linuxtools.b3aggrcon deleted by David M
Williams/Raleigh/IBM] ___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for RC1 ... its going to be a late night!
On May 22, 2013, at 11:43 PM, David M Williams david_willi...@us.ibm.com wrote: There's no change in policy. Projects choose to be in the (our) common repo. Part of that is to provide valid input to the build. Normally the tools work well to send out notifications for problems. Occasionally the contributed input is so bad that the tool can't even read it well enough to find the email addresses. You can wait until someone tells you that, if you'd like. But, as tonight, sometimes that takes 3 or 4 hours (or longer) for someone else to notice. As you said, you were waiting for a build ... how long would you wait before you looked at https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/simrel.kepler.runaggregator/ ? I looked at it and the error was exec returned: 13. How am I supposed to know that this is related to ptp? Is your expectation that I should dig into how it works to determine what is causing this problem? I don't think so. The automatic notifications may be deceptive, because they say they are from me but its all automated. I do not send them. I do not even see most of them ... at least, usually, until after the contributors have already fixed their problem. If it fails so badly that it can not find email addresses, I get an RSS notification that the Hudson failed. But, you may be surprised to hear, I am not on-line monitoring that queue 24 hours a day! Come on David, you said that it was ptp breaking the builds... and you ...spent an extra hour of my time fixing that. So you obviously knew there was a problem, but chose not to inform anyone about it. And, I'll be blunt, I'm sensitive to this for the PTP project, because similar things have happened several times before, most recently in M7... also last minute. (I know, I know, you were on vacation then :) But, I somehow how get the impression your project has not yet learned the convenience of using the b3 aggregator editor, a requirement that is well documented in http://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build Maybe it should be named the b3 repository interactive compiler and you'd have a different impression of it :) But seriously, you say you have no idea how the aggregation works. Well, if you want to know, here it is: it works just like p2 installing software ... and does a few extra quality checks. And, if it can read the addresses, it sends email if it can not install someone's contribution. That's about it. If I may, I'll quote another contributor who recently learned to use it ... that is, after I suggested him to use the validate and validate aggregation functions ... Sure enough I am impressed :-) That was easy and it does stuff :-) Actually the change was made using the b3 aggregation editor. I was going to make the change by hand because the editor doesn't appear to work for me in kepler, but Beth insisted on using it. So whatever went wrong was caused by your own tools. I hope a few of my comments are constructive and encouraging, I don't mean to argue about it. But, I am pretty firm about schedules. And you've not answered any of my original questions (except to provide a bug number), so if you'd like an exception, I'll ask you go through the full Planning Council exception process: http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Planning_Council_Exception_Process (And, BTW, I'm not blind to the fact that is it a very bad bug ... but ... at the time of this writing, it doesn't say very much, such as what the fix is, if there are workarounds, etc. Although the fix has zero chance of affecting anyone, I don't think it's worth the chance that there will be build problems at this late stage. Seriously, thanks for your comments and and thanks for your contributions to Eclipse. From:Greg Watson g.wat...@computer.org To:Cross project issues cross-project-issues-dev@eclipse.org, Date:05/22/2013 10:28 PM Subject:Re: [cross-project-issues-dev] Status and outlook for RC1 ...itsgoing to be a late night! Sent by:cross-project-issues-dev-boun...@eclipse.org David, Somewhat late at night to be arguing, but I find this statement perplexing: All projects are responsible for making sure the build works, notified or not. I have no idea how the aggregation works, nor have I seen any policy that indicates that I need to. I'm happy to take responsibility for our repo, but I think those responsible for the aggregation are also responsible for contacting projects if there are any problems. Isn't this is why we are listed as contacts in the simrel.b3aggr file, after all? As far as I'm aware, this is how it has worked in the past. Are you proposing a change to the process? Greg ___
[cross-project-issues-dev] SSH down on Build.eclipse.org?
I can't get to build.eclipse.org via ssh. But I can get there via http ( http://build.eclipse.org). anyone else having issues or is it just something local? -- Mark R Russell (724) 473-3140 Software Engineer in Test Google Shopping Express Google Pittsburgh ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] SSH down on Build.eclipse.org?
I'm able to ssh to this server - it must be you ;) Bob - Original Message - I can't get to build.eclipse.org via ssh. But I can get there via http ( http://build.eclipse.org ). anyone else having issues or is it just something local? -- Mark R Russell ( 724) 473-3140 Software Engineer in Test Google Shopping Express Google Pittsburgh ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] SSH down on Build.eclipse.org?
I get there with no problem Von: Mark Russell mrruss...@google.commailto:mrruss...@google.com Antworten an: Cross issues cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org Datum: Donnerstag, 23. Mai 2013 15:32 An: Cross issues cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org Betreff: [cross-project-issues-dev] SSH down on Build.eclipse.org? I can't get to build.eclipse.orghttp://build.eclipse.org via ssh. But I can get there via http (http://build.eclipse.org). anyone else having issues or is it just something local? -- Mark R Russell (724) 473-3140 Software Engineer in Test Google Shopping Express Google Pittsburgh - compeople AG Untermainanlage 8 60329 Frankfurt/Main fon: +49 (0) 69 / 27 22 18 0 fax: +49 (0) 69 / 27 22 18 22 web: www.compeople.dehttp://www.compeople.de/ Vorstand: J?rgen Wiesmaier Aufsichtsratsvorsitzender: Christian Glanz Sitz der Gesellschaft: Frankfurt/Main Handelsregister Frankfurt HRB 56759 USt-IdNr. DE207665352 - ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] SSH down on Build.eclipse.org?
Works for me. Are you coming in from a new IP addr where it sends you email to confirm it's really you? ...Beth Beth Tibbitts Eclipse Parallel Tools Platform http://eclipse.org/ptp IBM STG - High Performance Computing Tools Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511 | | From: | | -| |Mark Russell mrruss...@google.com | -| | | To:| | -| |Cross project issues cross-project-issues-dev@eclipse.org | -| | | Date: | | -| |05/23/2013 09:37 AM | -| | | Subject: | | -| |[cross-project-issues-dev] SSH down on Build.eclipse.org? | -| | | Sent by: | | -| |cross-project-issues-dev-boun...@eclipse.org | -| I can't get to build.eclipse.org via ssh. But I can get there via http ( http://build.eclipse.org). anyone else having issues or is it just something local? -- Mark R Russell (724) 473-3140 Software Engineer in Test Google Shopping Express Google Pittsburgh ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev inline: graycol.gifinline: ecblank.gif___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for RC1 ... its going to be a late night!
Hi Greg, [1] shows that the build was triggered by only one SCM change with the comment: For ptp, add org.eclipse.ptp.debug.sdm feature. Before of this change the build was working. So IMO it suggests itself that this commit was breaking the build. BTW: This is exactly the way how I was checking that my change for Kepler RC1 was not breaking the build (because it was my first commit into the simrel repo), that was obviously not that case [2] ;) In general I would vote to use Gerrit and CI a little bit closer together how it is mentioned in [3]. But IMO this is not acceptable for such a build sprint. [1] https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/476/ [2] https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/472/ [3] http://blogs.collab.net/teamforge/teamforge-git-gerrit-integration-with-jenkins-ci Cheers, Sven Von: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von Greg Watson Gesendet: Donnerstag, 23. Mai 2013 13:38 An: Cross project issues Betreff: Re: [cross-project-issues-dev] Status and outlook for RC1 ... its going to be a late night! On May 22, 2013, at 11:43 PM, David M Williams david_willi...@us.ibm.commailto:david_willi...@us.ibm.com wrote: There's no change in policy. Projects choose to be in the (our) common repo. Part of that is to provide valid input to the build. Normally the tools work well to send out notifications for problems. Occasionally the contributed input is so bad that the tool can't even read it well enough to find the email addresses. You can wait until someone tells you that, if you'd like. But, as tonight, sometimes that takes 3 or 4 hours (or longer) for someone else to notice. As you said, you were waiting for a build ... how long would you wait before you looked at https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/simrel.kepler.runaggregator/ ? I looked at it and the error was exec returned: 13. How am I supposed to know that this is related to ptp? Is your expectation that I should dig into how it works to determine what is causing this problem? I don't think so. The automatic notifications may be deceptive, because they say they are from me but its all automated. I do not send them. I do not even see most of them ... at least, usually, until after the contributors have already fixed their problem. If it fails so badly that it can not find email addresses, I get an RSS notification that the Hudson failed. But, you may be surprised to hear, I am not on-line monitoring that queue 24 hours a day! Come on David, you said that it was ptp breaking the builds... and you ...spent an extra hour of my time fixing that. So you obviously knew there was a problem, but chose not to inform anyone about it. And, I'll be blunt, I'm sensitive to this for the PTP project, because similar things have happened several times before, most recently in M7... also last minute. (I know, I know, you were on vacation then :) But, I somehow how get the impression your project has not yet learned the convenience of using the b3 aggregator editor, a requirement that is well documented in http://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build Maybe it should be named the b3 repository interactive compiler and you'd have a different impression of it :) But seriously, you say you have no idea how the aggregation works. Well, if you want to know, here it is: it works just like p2 installing software ... and does a few extra quality checks. And, if it can read the addresses, it sends email if it can not install someone's contribution. That's about it. If I may, I'll quote another contributor who recently learned to use it ... that is, after I suggested him to use the validate and validate aggregation functions ... Sure enough I am impressed :-) That was easy and it does stuff :-) Actually the change was made using the b3 aggregation editor. I was going to make the change by hand because the editor doesn't appear to work for me in kepler, but Beth insisted on using it. So whatever went wrong was caused by your own tools. I hope a few of my comments are constructive and encouraging, I don't mean to argue about it. But, I am pretty firm about schedules. And you've not answered any of my original questions (except to provide a bug number), so if you'd like an exception, I'll ask you go through the full Planning Council exception process: http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Planning_Council_Exception_Process (And, BTW, I'm not blind to the fact that is it a very bad bug ... but ... at the time of this writing, it doesn't say very much, such as what the fix is, if there are workarounds, etc. Although the fix has zero chance of affecting anyone, I don't think it's worth the chance that there will be build problems at this late stage. Seriously, thanks for your
Re: [cross-project-issues-dev] SSH down on Build.eclipse.org?
I've just checked and the service is responding. Most likely it's one of 2 things: 1) You've been blocked due to multiple 'bad' logins (from you, or someone else on your subnet) 2) If this is the first time you've connected from your current IP, a block was created and an 'unblock' email was sent to the address we have on file for you(unless another committer on your subnet did it first) If you send your IP to Webmaster I'll go digging. -Matt. On 05/23/2013 09:32 AM, Mark Russell wrote: I can't get to build.eclipse.org http://build.eclipse.org via ssh. But I can get there via http (http://build.eclipse.org). anyone else having issues or is it just something local? -- Mark R Russell (724) 473-3140 Software Engineer in Test Google Shopping Express Google Pittsburgh ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for RC1 ... its going to be a late night!
Hi, maybe I can step up here, since comments from me :-) are already in this thread. I have to admit that Riena had problems with the aggregation too in the past. I also thought for a long time (actually years) that the only way to try a new contribution is to build, sign, upload, change b3aggrcon,commit,push wait for the aggregation to kick off and pray that there is a reasonable result while I am still awake. (because of the time difference sometimes). Try a new run while its actually already after bed-time in my country. Now yesterday I found that all you need to do is run Eclipse, with org.eclipse.simrel.build checked out in your workspace and the b3 aggregator editor installed (i.e. http://download.eclipse.org/modeling/emft/b3/updates-4.2/) Now I can try to add a new version of Riena, build, sign, upload, change b3aggrcon but now instead of committing,pushing, praying (you remember from above) you can in the aggregation editor right click and say Validate Aggregation. It takes under 5 minutes and you get exactly the same message that you have to search and find in the aggregation build console. Of course you can also locally disable other projects that get in the way of validating your project. Really really EASY and I wish I had tried that years ago Christian campo Von: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von sven.rottst...@sungard.com Gesendet: Donnerstag, 23. Mai 2013 15:44 An: cross-project-issues-dev@eclipse.org Betreff: Re: [cross-project-issues-dev] Status and outlook for RC1 ... its going to be a late night! Hi Greg, [1] shows that the build was triggered by only one SCM change with the comment: For ptp, add org.eclipse.ptp.debug.sdm feature. Before of this change the build was working. So IMO it suggests itself that this commit was breaking the build. BTW: This is exactly the way how I was checking that my change for Kepler RC1 was not breaking the build (because it was my first commit into the simrel repo), that was obviously not that case [2] ;) In general I would vote to use Gerrit and CI a little bit closer together how it is mentioned in [3]. But IMO this is not acceptable for such a build sprint. [1] https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/476/ [2] https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/472/ [3] http://blogs.collab.net/teamforge/teamforge-git-gerrit-integration-with-jenkins-ci Cheers, Sven Von: cross-project-issues-dev-boun...@eclipse.orgmailto:cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von Greg Watson Gesendet: Donnerstag, 23. Mai 2013 13:38 An: Cross project issues Betreff: Re: [cross-project-issues-dev] Status and outlook for RC1 ... its going to be a late night! On May 22, 2013, at 11:43 PM, David M Williams david_willi...@us.ibm.commailto:david_willi...@us.ibm.com wrote: There's no change in policy. Projects choose to be in the (our) common repo. Part of that is to provide valid input to the build. Normally the tools work well to send out notifications for problems. Occasionally the contributed input is so bad that the tool can't even read it well enough to find the email addresses. You can wait until someone tells you that, if you'd like. But, as tonight, sometimes that takes 3 or 4 hours (or longer) for someone else to notice. As you said, you were waiting for a build ... how long would you wait before you looked at https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/simrel.kepler.runaggregator/ ? I looked at it and the error was exec returned: 13. How am I supposed to know that this is related to ptp? Is your expectation that I should dig into how it works to determine what is causing this problem? I don't think so. The automatic notifications may be deceptive, because they say they are from me but its all automated. I do not send them. I do not even see most of them ... at least, usually, until after the contributors have already fixed their problem. If it fails so badly that it can not find email addresses, I get an RSS notification that the Hudson failed. But, you may be surprised to hear, I am not on-line monitoring that queue 24 hours a day! Come on David, you said that it was ptp breaking the builds... and you ...spent an extra hour of my time fixing that. So you obviously knew there was a problem, but chose not to inform anyone about it. And, I'll be blunt, I'm sensitive to this for the PTP project, because similar things have happened several times before, most recently in M7... also last minute. (I know, I know, you were on vacation then :) But, I somehow how get the impression your project has not yet learned the convenience of using the b3 aggregator editor, a requirement that is well documented in http://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build
Re: [cross-project-issues-dev] Status and outlook for RC1 ... its going to be a late night!
David, BTW, I do appreciate all the work you do to ensure the releases are successful. It can be a bit frustrating when things don't go quite right, so we need to all work together to ensure that everything goes as smoothly as possible. Cheers, Greg On May 23, 2013, at 7:38 AM, Greg Watson g.wat...@computer.org wrote: On May 22, 2013, at 11:43 PM, David M Williams david_willi...@us.ibm.com wrote: There's no change in policy. Projects choose to be in the (our) common repo. Part of that is to provide valid input to the build. Normally the tools work well to send out notifications for problems. Occasionally the contributed input is so bad that the tool can't even read it well enough to find the email addresses. You can wait until someone tells you that, if you'd like. But, as tonight, sometimes that takes 3 or 4 hours (or longer) for someone else to notice. As you said, you were waiting for a build ... how long would you wait before you looked at https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/simrel.kepler.runaggregator/ ? I looked at it and the error was exec returned: 13. How am I supposed to know that this is related to ptp? Is your expectation that I should dig into how it works to determine what is causing this problem? I don't think so. The automatic notifications may be deceptive, because they say they are from me but its all automated. I do not send them. I do not even see most of them ... at least, usually, until after the contributors have already fixed their problem. If it fails so badly that it can not find email addresses, I get an RSS notification that the Hudson failed. But, you may be surprised to hear, I am not on-line monitoring that queue 24 hours a day! Come on David, you said that it was ptp breaking the builds... and you ...spent an extra hour of my time fixing that. So you obviously knew there was a problem, but chose not to inform anyone about it. And, I'll be blunt, I'm sensitive to this for the PTP project, because similar things have happened several times before, most recently in M7... also last minute. (I know, I know, you were on vacation then :) But, I somehow how get the impression your project has not yet learned the convenience of using the b3 aggregator editor, a requirement that is well documented in http://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build Maybe it should be named the b3 repository interactive compiler and you'd have a different impression of it :) But seriously, you say you have no idea how the aggregation works. Well, if you want to know, here it is: it works just like p2 installing software ... and does a few extra quality checks. And, if it can read the addresses, it sends email if it can not install someone's contribution. That's about it. If I may, I'll quote another contributor who recently learned to use it ... that is, after I suggested him to use the validate and validate aggregation functions ... Sure enough I am impressed :-) That was easy and it does stuff :-) Actually the change was made using the b3 aggregation editor. I was going to make the change by hand because the editor doesn't appear to work for me in kepler, but Beth insisted on using it. So whatever went wrong was caused by your own tools. I hope a few of my comments are constructive and encouraging, I don't mean to argue about it. But, I am pretty firm about schedules. And you've not answered any of my original questions (except to provide a bug number), so if you'd like an exception, I'll ask you go through the full Planning Council exception process: http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Planning_Council_Exception_Process (And, BTW, I'm not blind to the fact that is it a very bad bug ... but ... at the time of this writing, it doesn't say very much, such as what the fix is, if there are workarounds, etc. Although the fix has zero chance of affecting anyone, I don't think it's worth the chance that there will be build problems at this late stage. Seriously, thanks for your comments and and thanks for your contributions to Eclipse. From:Greg Watson g.wat...@computer.org To:Cross project issues cross-project-issues-dev@eclipse.org, Date:05/22/2013 10:28 PM Subject:Re: [cross-project-issues-dev] Status and outlook for RC1 ...itsgoing to be a late night! Sent by:cross-project-issues-dev-boun...@eclipse.org David, Somewhat late at night to be arguing, but I find this statement perplexing: All projects are responsible for making sure the build works, notified or not. I have no idea how the aggregation works, nor have I seen any policy that indicates that I need to. I'm happy to take responsibility for our repo, but I think those responsible for
Re: [cross-project-issues-dev] SSH down on Build.eclipse.org?
Note that you'll have to send your _externally visible_ IP address, which is sometimes nontrivial to find out. This may help: http://www.whatismyip.com/ I've had that problem in the past when some colleague of mine accidentally had 3 invalid logins in a row - your whole subnet gets locked out. Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Webmaster(Matt Ward) Sent: Thursday, May 23, 2013 3:44 PM To: Cross project issues Subject: Re: [cross-project-issues-dev] SSH down on Build.eclipse.org? I've just checked and the service is responding. Most likely it's one of 2 things: 1) You've been blocked due to multiple 'bad' logins (from you, or someone else on your subnet) 2) If this is the first time you've connected from your current IP, a block was created and an 'unblock' email was sent to the address we have on file for you(unless another committer on your subnet did it first) If you send your IP to Webmaster I'll go digging. -Matt. On 05/23/2013 09:32 AM, Mark Russell wrote: I can't get to build.eclipse.orghttp://build.eclipse.org via ssh. But I can get there via http (http://build.eclipse.org). anyone else having issues or is it just something local? -- Mark R Russell (724) 473-3140 Software Engineer in Test Google Shopping Express Google Pittsburgh ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Hudson seems to need a kick ...
As far as EPP is affected... it 'looks' like the last build finished somehow, but what a surprise I'm unable to access Hudson, too. From my point of view is a restart required... the sooner the better, because it's blocking us, too. Thanks, Markus On Fri, May 24, 2013 at 7:10 AM, David M Williams david_willi...@us.ibm.com wrote: I've been unable to access Hudson for past two hours. This does not impact the RC1 common repo ... I am not sure if EPP packages were finished building or not? But, I know it is blocking our Platform RC2 (due Friday). I've high jacked a similar bug open recently by Ed Willink [1] to raise its severity and document its impact. Just thought I'd inform this list, in case its impacting any of you. Plus ... I wanted to give an example of my sense of humor. Anyone ever notice that Bad Gateway page says ... contact the webmaster where 'webmaster' is a mailto:; link that links to mailto: [name not provided] ... I don't know why, but I find that so funny. (And, seriously, just funny ... no passive/aggressive criticism intended). [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=408851 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- ### EclipseSource Group Telefon: +49 721 664733-0 (GMT +2) Telefax: +49 721 66473329 http://eclipsesource.com Innoopract Informationssysteme GmbH Lammstrasse 21, 76133 Karlsruhe Germany General Manager: Jochen Krause Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
