|[eclipse.org-architecture-council] [Bug 285074] New: Build User IDs should have Commit Rights to Projects|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=285074 Product/Component: Community / Architecture Council Summary: Build User IDs should have Commit Rights to Projects Product: Community Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: Architecture Council AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx ReportedBy: d_a_carver@xxxxxxxxx CC: nickboldt+bugzilla@xxxxxxxxx, d_a_carver@xxxxxxxxx, linux.distros-inbox@xxxxxxxxxxx, dash.commonbuilder- inbox@xxxxxxxxxxx Blocks: 264713 The user ids that are using by Eclipse to check out and build code, do not allow one of the best practices from a Continuous Integration standpoint to occur. The HudsonBuilder id does not have write access rights to the repositories that it checks code out from. This makes it impossible for Hudson to Tag the builds either pre-build or post build. The same is true for when using Cruisecontrol, or other continuous integration servers. While I realise that there is a legacy build process in place, I think in general from a release engineering standpoint we need to revisit why we don't allow write access rights by the build machine user id. It is causing unnecessary hoop jumping to have to occur by the various build processes. +++ This bug was initially created as a clone of Bug #264713 +++ We should tag SVN each time we do a build so that it's reproducible. This will also alleviate our rather hairy release engineering procedures. -- Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
Back to the top