[cle-release-team] Changing/cleaning logins for builds.sakaiproject.org and other build stuffs

[Earle R Nietzel]

Same here! I am just looking at builds and there status's don't know if
I really need more than that!

Earle


On Wed, 2012-02-29 at 16:02 -0500, Aaron Zeckoski wrote:
> I probably don't actually need access but I don't mind terribly if I
> have it.
> -AZ
> 
> 
> On Wed, Feb 29, 2012 at 3:06 PM, Matthew Jones <matthew at longsight.com>
> wrote:
>         Hmm, maybe this was the wrong sublist of people. :( Jenkins is
>         confusing. I guess there's a list for the people who have
>         recently made commits and one for those who have recently been
>         active working on the system.
>         
>         
>         There shouldn't be any reason why you COULDN'T have access if
>         you needed/wanted, but I think a few people weren't included
>         that should be. :)
>         
>         
>         So disregard if you want as well, and in that case thanks for
>         your work on some aspect of Sakai! ;) I'll send this email to
>         a different list in a second.
>         
>         
>         
>         On Wed, Feb 29, 2012 at 2:49 PM, Matthew Jones
>         <matthew at longsight.com> wrote:
>                 Hi all!
>                 
>                 I identified this list based on the people who have
>                 logged into the builds.sakaiproject.machine in the
>                 last month.
>                 
>                 
>                 1) First off, I plan to clean up the list of people
>                 who have access to builds.sakaiproject.org to only the
>                 people on this email (those who have actually logged
>                 in recently), and remove the rest. Ideally I'd like to
>                 switch the access to this machine entirely over to
>                 openid (because it's not secure) and the functionality
>                 for that is enabled. So ideally, everyone would click
>                 this button and create an openid (google, yahoo, aol,
>                 wordpress, etc) link, then we can just reassign
>                 permissions and delete all of the internal accounts.
>                 Any issues with this?
>                 
>                 
>                 Inline image 1
>                 
>                 
>                 2) Secondly, sorry for the emails for the build
>                 failures for the last few days most of those were my
>                 fault. All of the previously broken builds should be
>                 caught up by now.
>                 
>                 The cause of this was that the release team had
>                 decided to change the deployment of the CLE (and OAE)
>                 artifacts. I updated the kernel and master for trunk
>                 to deploy to the new repository but I couldn't get
>                 access to update the existing settings.xml file, and I
>                 missed removing the deploy task from some of the
>                 existing projects when I worked on this Friday.
>                 
>                 
>                 They were previously deployed to
>                 http://source.sakaiproject.org/maven2/
>                   and now over to 
>                 https://oss.sonatype.org/content/repositories/snapshots/org/sakaiproject/ 
>                 
>                 
>                 The snapshots will be deployed there to start. When we
>                 do releases from Jenkins, they will be staged and
>                 moved to maven central. This will have the advantages
>                 of being a more reliable process, a process that's
>                 already standard and mostly already documented, and
>                 any tool should be able to build much easier if the
>                 poms use fixed release versions since they are in a
>                 standard repository.
>                 
>                 The hold of getting access to the shell of the build
>                 machine has made this a multi-step process for me. As
>                 of now, it looks like all of the builds that were
>                 previously in a failure state are cleaning up and
>                 building, though at this point (2:30PM EST) only the
>                 master and kernel are deploying. Ideally by the end of
>                 the day all (SNAPSHOT) artifacts will be in sonatype
>                 then these releases will begin.
>                 
>                 
>                 3) Third, I'm very available via skype (jonespm9) and
>                 at the CLE release meeting (Thursday 10AM EST) if you
>                 have any other comments/suggestions/time to work on
>                 anything.
>         
>         
> 
> 
> 
> 
> -- 
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>