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 tag around every tag.
That may be the most blatant example of superfluous markup ever! ;-)
On Thu, 8 Mar 2018 at 11:29 Thilina Ranathunga 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 of
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 '
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, wrote:
The problem I have with publishing whenever master is updated is that if
somebody solves many typos & makes man
Hi,
On Wed, 7 Mar 2018, 21:10 Antonio, 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 up
. 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 mas
ntonio
> 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
>
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.apach
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
t