[all] Automatic site update

[Emmanuel Bourg <eb...@apache.org>]

Hi all,

A part of the release process is to update the web site. I wonder if
this could be simplified with a Jenkins job watching for the release
tags and building/uploading the new site automatically. That would make
one less thing to think about when releasing new versions. I suspect the
most difficult issue to solve is to let Jenkins publish the content
without compromising the security.

Thoughts?

Emmanuel Bourg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

AW: [all] Automatic site update

["Jan Matèrne (jhm)" <ap...@materne.de>]

> > A part of the release process is to update the web site. I wonder if
> > this could be simplified with a Jenkins job watching for the release
> > tags and building/uploading the new site automatically. That would
> > make one less thing to think about when releasing new versions. I
> > suspect the most difficult issue to solve is to let Jenkins publish
> > the content without compromising the security.

If you are willing to start the Jenkins job manually, you could use build parameters for asking for the security infos.

You could also use several jobs
- automatic job1 checks for thinks to do. If then send an email "manual things have to be done". Otherwise be quite.
- manual job2 does the secured actions


Jan


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [all] Automatic site update

[Gary Gregory <ga...@gmail.com>]

One big pain is releasing IMO is having to manage BOTH Nexus (with the
extra checksum mess) AND SVN dist/dev + dist/release.

It would be nice if Nexus had a menu option as part of Closing a repo to
"remove extra checksum"...

Gary

On Thu, Jun 2, 2016 at 2:39 PM, Emmanuel Bourg <eb...@apache.org> wrote:

> Hi all,
>
> A part of the release process is to update the web site. I wonder if
> this could be simplified with a Jenkins job watching for the release
> tags and building/uploading the new site automatically. That would make
> one less thing to think about when releasing new versions. I suspect the
> most difficult issue to solve is to let Jenkins publish the content
> without compromising the security.
>
> Thoughts?
>
> Emmanuel Bourg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [all] Automatic site update

[sebb <se...@gmail.com>]

On 2 June 2016 at 23:15, Gary Gregory <ga...@gmail.com> wrote:
> On Thu, Jun 2, 2016 at 2:57 PM, Benedikt Ritter <br...@apache.org> wrote:
>
>> Emmanuel Bourg <eb...@apache.org> schrieb am Do., 2. Juni 2016 um
>> 23:39 Uhr:
>>
>> > Hi all,
>> >
>> > A part of the release process is to update the web site. I wonder if
>> > this could be simplified with a Jenkins job watching for the release
>> > tags and building/uploading the new site automatically. That would make
>> > one less thing to think about when releasing new versions. I suspect the
>> > most difficult issue to solve is to let Jenkins publish the content
>> > without compromising the security.
>>
>>
>> > Thoughts?
>> >
>>
>> I'm all for automation. The only problem I see is, that I usually publish
>> the final site from a dirty working copy. This is because I don't put the
>> release date into changes.xml until after the release.
>
>
> I like to use the RC date for changes.xml (which I forgot to do when I
> recently RM'd Commons CSV 1.4!)
>
> If the RC becomes the release, then you are done. If the RC does not, then
> update the date again for the next RC. I think that is 'sane' step.

What I do if I remember is add 4-5 days to the start of the RC vote.
This gives time for the vote plus publication delay.
I can then time the announce for the correct date.

But it's not too difficult to fix the website if necessary later.

> Our Maven plugin could be changed to do this so it becomes a command line
> thing instead of a manual edit.
>
> Gary
>
> However I have
>> realized that for example maven central uses that date the RC was upload to
>> the staging repo as the release date. We could simply adopt this and use
>> that date in changes.xml and commit it to the release tag.
>>
>> I'm sure it would even be possible to let jenkins create site archives as
>> we're currently doing for some components.
>>
>> I have no idea about the security implications of this proposal.
>>
>> Benedikt
>>
>>
>> >
>> > Emmanuel Bourg
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > For additional commands, e-mail: dev-help@commons.apache.org
>> >
>> >
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [all] Automatic site update

[Gary Gregory <ga...@gmail.com>]

On Thu, Jun 2, 2016 at 2:57 PM, Benedikt Ritter <br...@apache.org> wrote:

> Emmanuel Bourg <eb...@apache.org> schrieb am Do., 2. Juni 2016 um
> 23:39 Uhr:
>
> > Hi all,
> >
> > A part of the release process is to update the web site. I wonder if
> > this could be simplified with a Jenkins job watching for the release
> > tags and building/uploading the new site automatically. That would make
> > one less thing to think about when releasing new versions. I suspect the
> > most difficult issue to solve is to let Jenkins publish the content
> > without compromising the security.
>
>
> > Thoughts?
> >
>
> I'm all for automation. The only problem I see is, that I usually publish
> the final site from a dirty working copy. This is because I don't put the
> release date into changes.xml until after the release.


I like to use the RC date for changes.xml (which I forgot to do when I
recently RM'd Commons CSV 1.4!)

If the RC becomes the release, then you are done. If the RC does not, then
update the date again for the next RC. I think that is 'sane' step.

Our Maven plugin could be changed to do this so it becomes a command line
thing instead of a manual edit.

Gary

However I have
> realized that for example maven central uses that date the RC was upload to
> the staging repo as the release date. We could simply adopt this and use
> that date in changes.xml and commit it to the release tag.
>
> I'm sure it would even be possible to let jenkins create site archives as
> we're currently doing for some components.
>
> I have no idea about the security implications of this proposal.
>
> Benedikt
>
>
> >
> > Emmanuel Bourg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>



-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [all] Automatic site update

[Benedikt Ritter <br...@apache.org>]

Emmanuel Bourg <eb...@apache.org> schrieb am Do., 2. Juni 2016 um
23:39 Uhr:

> Hi all,
>
> A part of the release process is to update the web site. I wonder if
> this could be simplified with a Jenkins job watching for the release
> tags and building/uploading the new site automatically. That would make
> one less thing to think about when releasing new versions. I suspect the
> most difficult issue to solve is to let Jenkins publish the content
> without compromising the security.


> Thoughts?
>

I'm all for automation. The only problem I see is, that I usually publish
the final site from a dirty working copy. This is because I don't put the
release date into changes.xml until after the release. However I have
realized that for example maven central uses that date the RC was upload to
the staging repo as the release date. We could simply adopt this and use
that date in changes.xml and commit it to the release tag.

I'm sure it would even be possible to let jenkins create site archives as
we're currently doing for some components.

I have no idea about the security implications of this proposal.

Benedikt


>
> Emmanuel Bourg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>