You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Antonio <an...@vieiro.net> on 2018/03/07 20:43:13 UTC
Automating website publishing
Hi all,
I've just submitted https://issues.apache.org/jira/browse/INFRA-16157 to
INFRA to request a Jenkins job that publishes
https://netbeans.apache.org (copying the resulting website from master
to the asf-site branch)
I don't know how often that should be run. Some possibilities I can
think of:
a) Whenever 'master' is updated.
b) On demand.
c) Each X days.
Ideas? Opinions?
Thanks,
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Automating website publishing
Posted by Neil C Smith <ne...@apache.org>.
Pending automation, Mr ultra-slow Jenkins here has updated the live site
based on the last two PR's on master.
Incidentally noticed while git diffing the changes that the asciidoc
converter seems to add a <div class="paragraph"> tag around every <p> tag.
That may be the most blatant example of superfluous markup ever! ;-)
Any idea why? Unless there's a good reason for it, I'll look into how we
get rid of it.
Best wishes,
Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net
Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Automating website publishing
Posted by Geertjan Wielenga <ge...@googlemail.com>.
I’d be fine with a daily update at a specific time, e.g., 18.00 CET for
example.
Gj
On Wednesday, March 7, 2018, Christian Lenz <ch...@gmx.net> wrote:
> For me, it only makes sense when master was updated or a new tag (maybe we
> don’t Need tags).
>
>
> Cheers
>
> Chris
>
> Von: Antonio
> Gesendet: Mittwoch, 7. März 2018 21:43
> An: dev@netbeans.incubator.apache.org
> Betreff: Automating website publishing
>
> Hi all,
>
> I've just submitted https://issues.apache.org/jira/browse/INFRA-16157 to
> INFRA to request a Jenkins job that publishes
> https://netbeans.apache.org (copying the resulting website from master
> to the asf-site branch)
>
> I don't know how often that should be run. Some possibilities I can
> think of:
>
> a) Whenever 'master' is updated.
> b) On demand.
> c) Each X days.
>
> Ideas? Opinions?
>
> Thanks,
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>
Re: AW: Automating website publishing
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 8 Mar 2018 at 11:29 Thilina Ranathunga <r....@gmail.com> wrote:
> At this stage, the site is getting updates frequently (say, Multiple
> commits/pull requests per day). So, I assume "c) Each X days" would be good
> in the current situation.
>
Why? Having run a range of sites for clients and personally off a similar
arrangement, I don't see the issue with having multiple builds happen in a
day. I'd much rather people can immediately check any applied changes have
built and applied correctly to the live site.
Just as a point of comparison, GitHub pages has a limit of 10 builds per
hour, Netlify of 3 builds per minute - multiple builds in a day doesn't
seem like we're asking a lot from the infrastructure.
Best wishes,
Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net
Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: AW: Automating website publishing
Posted by Thilina Ranathunga <r....@gmail.com>.
My suggestion is,
At this stage, the site is getting updates frequently (say, Multiple
commits/pull requests per day). So, I assume "c) Each X days" would be good
in the current situation.
Once when the site is more stable and rich enough not to get changed
frequently, we may go for "a) Whenever 'master' is updated."
On Thu, Mar 8, 2018 at 4:17 PM, Antonio <an...@vieiro.net> wrote:
> Hi Neil,
>
> Yes, I think that makes most sense. I'll update the issue with that.
>
> Thanks,
> Antonio
>
>
> On 07/03/18 22:17, Neil C Smith wrote:
>
>> Hi,
>>
>> On Wed, 7 Mar 2018, 21:10 Antonio, <an...@vieiro.net> wrote:
>>
>> The problem I have with publishing whenever master is updated is that if
>>> somebody solves many typos & makes many commits we'll end up with many
>>> builds. That wastes ASF resources.
>>>
>>>
>> Not if we do this by pull request and not direct commits to upstream
>> master.
>>
>> Best wishes,
>>
>> Neil
>>
>> --
>>>
>> Neil C Smith
>> Artist & Technologist
>> www.neilcsmith.net
>>
>> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
--
Best regards,
Thilina Ranathunga.
Re: AW: Automating website publishing
Posted by Antonio <an...@vieiro.net>.
Hi Neil,
Yes, I think that makes most sense. I'll update the issue with that.
Thanks,
Antonio
On 07/03/18 22:17, Neil C Smith wrote:
> Hi,
>
> On Wed, 7 Mar 2018, 21:10 Antonio, <an...@vieiro.net> wrote:
>
>> The problem I have with publishing whenever master is updated is that if
>> somebody solves many typos & makes many commits we'll end up with many
>> builds. That wastes ASF resources.
>>
>
> Not if we do this by pull request and not direct commits to upstream
> master.
>
> Best wishes,
>
> Neil
>
>> --
> Neil C Smith
> Artist & Technologist
> www.neilcsmith.net
>
> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: AW: Automating website publishing
Posted by Neil C Smith <ne...@apache.org>.
Hi,
On Wed, 7 Mar 2018, 21:10 Antonio, <an...@vieiro.net> wrote:
> The problem I have with publishing whenever master is updated is that if
> somebody solves many typos & makes many commits we'll end up with many
> builds. That wastes ASF resources.
>
Not if we do this by pull request and not direct commits to upstream
master.
Best wishes,
Neil
> --
Neil C Smith
Artist & Technologist
www.neilcsmith.net
Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: AW: Automating website publishing
Posted by Antonio <an...@vieiro.net>.
Hi,
The problem I have with publishing whenever master is updated is that if
somebody solves many typos & makes many commits we'll end up with many
builds. That wastes ASF resources.
A periodic build, on the other hand, wastes ASF resources... well,
periodically :-)
What I mean is that I don't know which be less wasteful: a build per
commit or a periodic build. :-?
Thanks
Antonio
On 07/03/18 21:56, Christian Lenz wrote:
> For me, it only makes sense when master was updated or a new tag (maybe we don’t Need tags).
>
>
> Cheers
>
> Chris
>
> Von: Antonio
> Gesendet: Mittwoch, 7. März 2018 21:43
> An: dev@netbeans.incubator.apache.org
> Betreff: Automating website publishing
>
> Hi all,
>
> I've just submitted https://issues.apache.org/jira/browse/INFRA-16157 to
> INFRA to request a Jenkins job that publishes
> https://netbeans.apache.org (copying the resulting website from master
> to the asf-site branch)
>
> I don't know how often that should be run. Some possibilities I can
> think of:
>
> a) Whenever 'master' is updated.
> b) On demand.
> c) Each X days.
>
> Ideas? Opinions?
>
> Thanks,
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
AW: Automating website publishing
Posted by Christian Lenz <ch...@gmx.net>.
For me, it only makes sense when master was updated or a new tag (maybe we don’t Need tags).
Cheers
Chris
Von: Antonio
Gesendet: Mittwoch, 7. März 2018 21:43
An: dev@netbeans.incubator.apache.org
Betreff: Automating website publishing
Hi all,
I've just submitted https://issues.apache.org/jira/browse/INFRA-16157 to
INFRA to request a Jenkins job that publishes
https://netbeans.apache.org (copying the resulting website from master
to the asf-site branch)
I don't know how often that should be run. Some possibilities I can
think of:
a) Whenever 'master' is updated.
b) On demand.
c) Each X days.
Ideas? Opinions?
Thanks,
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists