[cross-project-issues-dev] Service downtime.

[Webmaster(Matt Ward)]

Hi Folks,

  Just to let you know that we've finished moving the hippcentos slave
as well as our sonar instance and they are back up.

We had some issues with upgrading sonar but it looks ok now.  Sorry
about the extra time required.

-Matt.

___
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] Correction: Eclipse Top-Level Project Participates in Oxygen

[Daniel Megert]

It of course Oxygen!

Dani

- Forwarded by Daniel Megert/Zurich/IBM on 29.07.2016 17:32 -

From:   Daniel Megert/Zurich/IBM
To: cross-project-issues-dev 
Date:   29.07.2016 16:37
Subject:Eclipse Top-Level Project Participates in Neon


The Eclipse top-level project participates in Neon with offset +0. For 
details see https://projects.eclipse.org/projects/eclipse/releases/4.7.0.


Dani

___
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] Eclipse Top-Level Project Participates in Neon

[Daniel Megert]

The Eclipse top-level project participates in Neon with offset +0. For 
details see https://projects.eclipse.org/projects/eclipse/releases/4.7.0.


Dani

___
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] Service downtime

[Lorenzo Bettini]

On 28/07/2016 12:25, Frederic Gurr wrote:
> My suggestion was to get this fixed in Hudson/Sonar plugin.
> 
> In the meantime, Mikael Barbero suggested that you don't need to use the
> Sonar plugin to run an analysis.
> According to
> http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Maven
> you can do it from Maven directly. The only thing that needs to be
> changed to make this work is the .m2/settings.xml file.

Maybe I'm still missing something (Mikael is in CC): from what I
understand, we need to use the sonar plugin to run the analysis since
HIPP is configured with the correct user and password to access sonar,
and this is kept hidden to us.  In fact, I see this line when using the
sonar plugin in hudson (where the user and password are unknown to us
and kept hidden)

-Dsonar.jdbc.driver=com.mysql.jdbc.Driver
-Dsonar.jdbc.url=jdbc:mysql://dbmaster:3306/sonar?autoReconnect=true=true=utf8
  -Dsonar.host.url=http://sonar.eclipse.org:9000/sonar

so how can I run the sonar analysis directly?

Again, if the problem is the plugin version, would that be possible to
downgrade that in HIPP?

thanks in advance
Lorenzo

> 
> On 28.07.2016 10:31, Lorenzo Bettini wrote:
>> I'm not sure I understand what you suggest...
>>
>> We requested to switch to JIPP but that's not possible at the moment
>>
>> Could we request to downgrade the Hudson/Sonar plugin?
>>
>> Or simply we can't analyze our projects anymore?
>>
>> On 27/07/2016 20:09, Frederic Gurr wrote:
>>> Fix the bug in Hudson/Sonar plugin or move to Jenkins (in the long run). ;)
>>>
>>> On 27.07.2016 18:14, Lorenzo Bettini wrote:
 On 27/07/2016 18:08, Frederic Gurr wrote:
> Hi,
>
> AFAICT, the bug is caused by an incompatibility between the Sonar plugin
> and Hudson. So upgrading the Sonar *server* will not address this.
>
> Regards,
>
> Fred

 Hi

 so what can we do about that?

>
> On 27.07.2016 17:54, Lorenzo Bettini wrote:
>> On 27/07/2016 17:41, Frederic Gurr wrote:
>>> Hi,
>>>
>>> To make the best use of the planned downtime, I will upgrade Sonar after
>>> it has been moved. This will be just a small upgrade from version 4.5.4
>>> to 4.5.7 and should have no big impact.
>>> It's a prerequisite to be able to upgrade to the latest LTS version
>>> (5.6) in the near future after some more testing.
>>>
>>> If there are any questions about the Sonar upgrade, please let me know.
>>
>> Do you think the upgrade will also address this
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=474406 ?
>>
>> thanks
>>  Lorenzo
>>
> ___
> 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
> 


-- 
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
___
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] [aeri] How To Automatically Create Bug Reports from your Error Reports

[Donát Csikós]

For me both the request reopening and the create bug report idea
sounds fine. This way there won't any point in time where the user
would feel stuck how to give feedback. Which is - if I understand
correctly - the purpose of the AERI project.

Anyway, thanks for the feedback and also thanks for the AERI project
in general. For Buildship we use it extensively and it really helped
us to understand problems and how people use our software in general.


2016-07-27 15:25 GMT+02:00 Marcel Bruch :
> There is nothing yet that allows a normal user to reopen a problem. There
> are other means like auto actions that can reopen a problem as soon as a new
> incident arrives that shows an already closed error still exists in a newer
> version of Buildship. See [1] for an example.
>
> However, we (the Architecture Council, Mike, Wayne, Janet and me) discussed
> whether could give normal users anonymized read access to error reports and
> also allow them to create bug reports from them. All agreed that (given we
> do a proper anonymization), there is no reason why we should not allow users
> to create bug reports.
>
> There is, however, the risk of having users blindly clicking on “Create Bug
> Report” from their submissions page when it becomes too easy. We should
> require (anonymous) users to provide little more content manually and put a
> minimum hurdle in place so that we do not get flooded.
>
> We may also allow users to reopen a bug report with a comment - but I’m not
> sure this is a great idea.
>
> Instead, we could allow users to “request reopening” and put this into
> (weekly/daily) email digests if you like.
>
> We have many options. But there is currently nothing implemented that fully
> satisfies your need. Let’s discuss what you need and see where we go/end up
> with...
>
>
>
>
>
>
> [1] https://blog.ctrlflow.com/hidden-gems-auto-reopening-problems/
>
>
>
> On 27 Jul 2016, at 12:28, Donát Csikós  wrote:
>
> I'm just trying to understand the workflow here. Let's say as an
> Eclipse user I enconunter an exception and I report it via AERI. For
> some cases I might get the response that this issues was resolved as
> invalid (no bug reports involved). Now, what if I know it is not true
> and I have an example exhibiting the problem. Can update the report or
> at least send my notes to the committers via AERI in an easy way?
>
> 2016-07-27 12:00 GMT+02:00 Marcel Bruch :
>
> At the moment, they would have to put comment on / reopen the bug in
> Bugzilla.
>
> Would you like to have something "more interactive” or a different behavior?
> If so, let me know what you would like to see.
>
> FWIW,
> AERI can (in general) reopen bugs in Bugzilla.
>
> Cheers,
> Marcel
>
>
> On 27 Jul 2016, at 11:53, Donát Csikós  wrote:
>
> Hi Marcel,
>
> Just a quick question: what if a reviewer incorreclty closes a report?
> Is there a way for a reporter to reopen it if they are unhappy with
> the resolution?
> Cheers,
>
>
> --
> Donát Csikós
> Software Engineer
> Gradle GmbH
> Firmensitz: Manteuffelstr. 60, 10999 Berlin, Germany
> Registergericht: Amtsgericht Charlottenburg, HRB 162310
> Geschäftsführer: Regine Dockter
> T. +49-30-609886880
> W. www.gradle.org
>
> 2016-07-22 11:29 GMT+02:00 Marcel Bruch :
>
> Greetings Cross-Projects,
>
> a question that was raised by several committers (and I think might be
> relevant to some of you as well) was, how to configure AERI to automatically
> create Bugzillas from your error reports. I published a short blog post
> describing how projects can configure this behavior via an automated action
> here [1].
>
> In case you have any further question or need assistance on setting this up,
> please do not hesitate to contact me...
>
> Cheers,
> Marcel
>
>
> [1]
> https://blog.ctrlflow.com/hidden-gems-automatically-create-bugs-error-reports/
>
>
>
> ___
> 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
>
>
> --
> Codetrails GmbH
> The knowledge transfer company
>
> Robert-Bosch-Str. 7, 64293 Darmstadt
> Phone: +49-6151-276-7092
> Mobile: +49-179-131-7721
> http://www.codetrails.com/
>
> Managing Director: Dr. Marcel Bruch
> Handelsregister: Darmstadt HRB 91940
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password,