[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] HIPP user rights


I think you are addressing a different use case. Sharing the whole workspace is indeed very fragile and not worthwhile.

Allowing users to browse the HIPP configuration seems very important. Allowing browsing of the actual files in the workspace would be helpful.

Even as a committer I get frustrated at not being able to see how some other project handles a particular build problem.


        Ed Willink

On 22/02/2016 15:36, Thanh Ha wrote:
In my opinion workspaces should not be shared with anonymous users as there's no way to know for sure what is beign shared and they only exist until the next build starts, which depending on how active your project is might not be very long. Instead if you want to retain certain files such as logs you should use the Hudson Archiving feature to save specifically selected data with the build results.


On Mon, Feb 22, 2016 at 6:44 AM, Christian Pontesegger <christian.pontesegger@xxxxxx> wrote:

we had this topic with some bad commits that were used to inject bad code that runs on HIPP and may harm the eclipse infrastructure. So I guess we might help these attackers a little when we expose what our build jobs do and how the workspace looks like. This was the reason I asked for any security concerns.


cbi-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit