Currently the release is performed on the release manager's machine. I suppose it could be done in Jenkins but that doesn't buy us a whole lot. I'm also not sure what the "last successful artifacts" are from "mvn site site:stage -DstagingDirectory=$HOME/log4j" would be. I guess if we ran it from Jenkins $HOME would be replaced with $WORKSPACE. I actually do that in my $day job. The last step of the Jenkins job is a script that moves the built site to the appropriate Apache directory on the same server.
Ralph > On Nov 29, 2015, at 12:03 AM, Alex Harui <aha...@adobe.com> wrote: > > A Jenkins build can publish a set of files to the web via the "last > successful artifacts" option, so I'm wondering if you could do what you want > on builds.a.o instead of home.a.o. Or whether that would bog down > builds.a.o. I even can use builds.a.o and Jenkins to effectively run cron > jobs. > > -Alex > > From: Ralph Goers <ralph.go...@dslextreme.com> > Date: Saturday, November 28, 2015 at 10:23 PM > To: Alex Harui <aha...@adobe.com> > Cc: Log4J Developers List <log4j-dev@logging.apache.org>, Apache > Infrastructure <infrastruct...@apache.org> > Subject: Re: [NOTICE] people.apache.org web space is moving to home.apache.org > > I’m not sure if that was a question for me, but I don’t understand the last > part of the sentence “and calls that last successful artifacts”. > > Ralph > >> On Nov 28, 2015, at 11:00 PM, Alex Harui <aha...@adobe.com> wrote: >> >> Is it against any rules to have a job on builds.a.o that picks up the zip >> and expands it and calls that last successful artifacts? >> >> -Alex >> >> From: Ralph Goers <ralph.go...@dslextreme.com> >> Date: Saturday, November 28, 2015 at 4:27 PM >> To: Log4J Developers List <log4j-dev@logging.apache.org> >> Cc: Apache Infrastructure <infrastruct...@apache.org> >> Subject: Re: [NOTICE] people.apache.org web space is moving to >> home.apache.org >> >> Thanks Gavin. As I mentioned we have had a buildbot job that has been >> failing for months. We ended up doing our CI builds on Jenkins and just >> ignore the failure messages since we can’t seem to get them fixed. >> >> I also don’t see how buildbot can do what we want to do. Our current process >> is to build the site from the release tag, zip it up and scp it to the >> release managers account on people.apache.org where it is unzipped into >> their web space. The site is then reviewed along with the source and >> binaries as part of the release process. I’d prefer it if a process could >> be put in place to allow us to do this on home.apache.org, but should that >> not be possible we will make due with the project VM we have requested. >> >> Ralph >> >>> On Nov 28, 2015, at 4:49 PM, Gavin McDonald <gmcdon...@apache.org> wrote: >>> >>> Ralph et al >>> >>> (As I mentioned on your INFRA jira ticket…) >>> >>> Some projects opt to use https://ci.apache.org/projects/ to host >>> RC/Snapshot websites. >>> This is done via Buildbot and a config file is all that needs to be >>> maintained. >>> >>> Examples: >>> >>> https://ci.apache.org/projects/asterixdb/index.html >>> https://ci.apache.org/projects/flink/flink-docs-release-0.10/index.html >>> https://ci.apache.org/projects/tomcat/tomcat8/docs/index.html >>> >>> Projects are also welcome to stage API and code coverage docs there too:- >>> >>> https://ci.apache.org/projects/wicket/apidocs/8.x/index.html >>> https://ci.apache.org/projects/cayenne/api/index.html >>> https://ci.apache.org/projects/tomcat/tomcat8/coverage/coverage/index.html >>> >>> And finally, projects are welcome to host alpha/beta/snapshot/nightly >>> developer only previews of their software releases:- >>> >>> https://ci.apache.org/projects/subversion/nightlies/index.html >>> https://ci.apache.org/projects/jmeter/nightlies/index.html >>> https://ci.apache.org/projects/ofbiz/snapshots/index.html >>> >>> File an INFRA jira ticket if interested and I’ll gladly help set something >>> up. >>> >>> Gav… >>> >>> >>>> On 27 Nov 2015, at 6:00 am, Ralph Goers <ralph.go...@dslextreme.com> wrote: >>>> >>>> When performing releases we typically create a new web site for our >>>> project on our local machine, zip it up and then unzip it on p.a.o for >>>> reviewers to look at during voting on the release. The site is way too big >>>> to try to do file by file with sftp. How will we be able to accomplish >>>> this with the new plan? >>>> >>>> Ralph >>>> >>>>> On Nov 25, 2015, at 5:20 AM, Daniel Gruno <humbed...@apache.org> wrote: >>>>> >>>>> Hi folks, >>>>> as the subject says, people.apache.org is being decommissioned soon, and >>>>> personal web space is being moved to a new home, aptly named >>>>> home.apache.org ( https://home.apache.org/ ) >>>>> >>>>> IMPORTANT: >>>>> If you have things on people.apache.org that you would like to retain, >>>>> please make a copy of it and move it to home.apache.org. (note, you will >>>>> have to make a folder called 'public_html' there, for items to show up >>>>> under https://home.apache.org/~yourID/ ). >>>>> >>>>> We will _NOT_ be moving your data for you. There is simply too much old >>>>> junk data on minotaur (the current people.apache.org machine) for it to >>>>> make sense to rsync it across, so we have made the decision that moving >>>>> data is up to each individual committer. >>>>> >>>>> The new host, home.apache.org, will ONLY be for web space, you will not >>>>> have shell access to the machine (but you can copy data to it using SFTP >>>>> and your SSH key). Access to modify LDAP records (for project chairs) >>>>> will be moved to a separate host when the time comes. >>>>> >>>>> There will be a 3 month grace period to move your data across. After >>>>> this time span (March 1st, 2016), minotaur will no longer serve up >>>>> personal web space, and visits to people.apache.org will be redirected >>>>> to home.apache.org. >>>>> >>>>> With regards, >>>>> Daniel on behalf of the Apache Infrastructure Team. >>>>> >>>>> PS: All replies to this should go to infrastruct...@apache.org >>>>> >>>> >>>> >>> >>> >> >
