Hi all,
I often struggle to build (or setup a CI build for) eclipse projects.
Sometimes, there is a wiki page about how to build the project, but it may be
outdated or not complete. I often want to see how the project setup its jobs on
hudson in order to know how I should properly build the
+1
I fully agree with you, Mikael!
On Thu, Jan 9, 2014 at 10:11 AM, Mikaël Barbero mikael.barb...@gmail.comwrote:
Hi all,
I often struggle to build (or setup a CI build for) eclipse projects.
Sometimes, there is a wiki page about how to build the project, but it may
be outdated or not
HI
Thanks Michael
+1
I certainly want my OCL/QVTd HIPP to be accessible and have been
inconvenienced by not being able to access other HIPPs.
Regards
Ed Willink
On 09/01/2014 08:11, Mikaël Barbero wrote:
Hi all,
I often struggle to build (or setup a CI build for) eclipse
+1 as well.
Is there a bugzilla ticket to follow for that request?
--
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
___
Ed,
Surely the lack of visibility of HIPPs contradicts our normal Eclipse
policies of openness, so all HIPPs should have anonymous read access unless
specifically requested (and justified) otherwise?
I can't manage to think about a proper justification for that, but I fully
agree that it
On 01/09/2014 12:00 PM, Mikaël Barbero mikael.barb...@gmail.com wrote:
To be sure I understand, you mean that there is something like a
private key in your job configuration? IMHO, I don't think it is safe
to rely on Hudson privacy settings to protect such a thing.
It's not a private key but a
Anonymous users can see the console log which prints in order everything
that's run although I guess does require more parsing on the reader's
part to figure out the job full setup.
I do like the idea of allowing people to see how a job was setup but I
do have a concern related to security.
According
http://projects.eclipse.org/releases/luna
There are 75 projects participating in Luna (from my quick count). Two of
those, Orion and Paho, are not aggregated in common repository, so that
implies we should have 73 files in 'org.eclipse.simrel.builds. In fact, we
have 77 files ... I
On 09/01/14 06:00 AM, Mikaël Barbero wrote:
Anyway, yes Hudson always lets you activate a per-project (job) permissions and
thus change permissions for a given user on a per job basis.
In my experience with Hudson permissions the permissions are additive,
not subtractive. So if we globally
In my experience with Hudson permissions the permissions are additive, not
subtractive. So if we globally set that Anonymous users can view a job
configuration. You cannot remove that permission inside an individual job
configuration.
I agree. I was wrong.
For example all the Hudson
On 01/09/2014 11:43 AM, Winston Prakash wrote:
I would suggest to upgrade HPP instances to Hudson to 3.1.* and enable
Team Management authorization instead of Project Matrix Authorization.
This has few advantages
- Sys Admins can be still be Eclipse IT
- Create Team Admins (Eclipse Project
I count 77 projects on the /releases/luna page.
The page indicates that the following projects from last year have
not yet opted in:
Agent Modeling Platform
EclipseLink Project
SCA Tools
If I have missed your request to join, please let me
12 matches
Mail list logo
