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-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
