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/04/02 19:48:57 UTC
Automatic website publishing
Hi all,
We now have a jenkins task that updates the website whenever master is
changed (then the asf-site is automagically uploaded to the webserver).
All this currently takes a few minutes.
I'm not sure I like the final setup (the script is hosted at jenkins,
not in our repos), so I won't close NETBEANS-522 [1] as of yet. Maybe we
want ot modify the script ([2]) and include it inside the asf-site
branch itself.
Please modify the web pages as you see fit to make sure everything works
correctly.
Thanks,
Antonio
[1]
https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-522
[2]
https://builds.apache.org/view/Incubator
Projects/job/incubator-netbeans-website
---------------------------------------------------------------------
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: Automatic website publishing
Posted by Geertjan Wielenga <ge...@googlemail.com>.
That makes sense, thanks.
I'll delete the branches that I inadvertently created and from this point
only work from my own fork.
Gj
On Tue, Apr 3, 2018 at 2:37 PM, Neil C Smith <ne...@apache.org> wrote:
> On Tue, 3 Apr 2018 at 13:15 Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> > So far, I haven't cloned. I.e., I do the PR from and against the master
> > repo.
> >
>
> Yes, if you have commit access it will edit in a branch in that repo,
> whereas for others the edit button will automatically fork. It might be
> useful if it created a fork for everyone though? The problem is the number
> of branches we end up with in the main repo -
> https://github.com/apache/incubator-netbeans-website/branches
>
> When you merge a PR it should give you the option to delete the branch,
> which would probably be good for this.
>
> Best wishes,
>
> Neil
> --
> Neil C Smith
> Artist & Technologist
> www.neilcsmith.net
>
> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>
Re: Automatic website publishing
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 3 Apr 2018 at 13:15 Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> So far, I haven't cloned. I.e., I do the PR from and against the master
> repo.
>
Yes, if you have commit access it will edit in a branch in that repo,
whereas for others the edit button will automatically fork. It might be
useful if it created a fork for everyone though? The problem is the number
of branches we end up with in the main repo -
https://github.com/apache/incubator-netbeans-website/branches
When you merge a PR it should give you the option to delete the branch,
which would probably be good for this.
Best wishes,
Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net
Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Automatic website publishing
Posted by Antonio <an...@vieiro.net>.
I tried it yesterday and works as expected.
On 03/04/18 14:14, Geertjan Wielenga wrote:
> So far, I haven't cloned. I.e., I do the PR from and against the master
> repo.
>
> Gj
>
> On Tue, Apr 3, 2018 at 2:06 PM, Antonio <an...@vieiro.net> wrote:
>
>>
>>
>> On 03/04/18 12:40, Geertjan Wielenga wrote:
>>
>>> And I did that without checking out the website sources, i.e., edited live
>>> on GitHub. Fantastic.
>>>
>>> Gj
>>>
>>>
>> Yes. Users can now fork the repository at github, edit and preview the
>> (say, wiki) pages in their clones and then submit PRs with their
>> modifications. All that in the web, without ever touching their hard disks.
>>
>> I think we should document that somewhere (in the website? ;-)) and start
>> updating the wiki somehow.
>>
>> Cheers,
>> 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
Re: Automatic website publishing
Posted by Geertjan Wielenga <ge...@googlemail.com>.
So far, I haven't cloned. I.e., I do the PR from and against the master
repo.
Gj
On Tue, Apr 3, 2018 at 2:06 PM, Antonio <an...@vieiro.net> wrote:
>
>
> On 03/04/18 12:40, Geertjan Wielenga wrote:
>
>> And I did that without checking out the website sources, i.e., edited live
>> on GitHub. Fantastic.
>>
>> Gj
>>
>>
> Yes. Users can now fork the repository at github, edit and preview the
> (say, wiki) pages in their clones and then submit PRs with their
> modifications. All that in the web, without ever touching their hard disks.
>
> I think we should document that somewhere (in the website? ;-)) and start
> updating the wiki somehow.
>
> Cheers,
> 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: Automatic website publishing
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Apr 3, 2018 at 2:06 PM, Antonio <an...@vieiro.net> wrote:
> ...I think we should document that somewhere (in the website? ;-)) ...
For me the natural place to look for website publishing instructions
is the README at
https://github.com/apache/incubator-netbeans-website
-Bertrand
---------------------------------------------------------------------
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: Automatic website publishing
Posted by Antonio <an...@vieiro.net>.
On 03/04/18 12:40, Geertjan Wielenga wrote:
> And I did that without checking out the website sources, i.e., edited live
> on GitHub. Fantastic.
>
> Gj
>
Yes. Users can now fork the repository at github, edit and preview the
(say, wiki) pages in their clones and then submit PRs with their
modifications. All that in the web, without ever touching their hard disks.
I think we should document that somewhere (in the website? ;-)) and
start updating the wiki somehow.
Cheers,
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: Automatic website publishing
Posted by Geertjan Wielenga <ge...@googlemail.com>.
And I did that without checking out the website sources, i.e., edited live
on GitHub. Fantastic.
Gj
On Tue, Apr 3, 2018 at 12:35 PM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Wow, amazing, it works.
>
> https://netbeans.apache.org/community/events.html
>
> The above I tweaked a bit, created a PR (I think that's the safest way to
> track things), and then merged it -- within 5 minutes the change was live.
>
> Gj
>
> On Tue, Apr 3, 2018 at 12:15 PM, Antonio <an...@vieiro.net> wrote:
>
>>
>>
>> On 03/04/18 11:50, Neil C Smith wrote:
>>
>>> You mean I've finally got to that time where my job has been superseded
>>> by
>>> a robot?! ;-)
>>>
>>>
>> Exactly! Lucky you! I still had to fight Jenkins, github & gitbox, I need
>> a robot too! :-)
>>
>>
>>> The push to asf-site on GitBox is what I expected from earlier
>>> conversations, with the webhook triggered on GitHub. But what was the
>>> issue earlier then? PR24 looks like it was on GitHub?
>>>
>>
>> Ah, I wasn't aware of those expectations. The issue was that infra did
>> set up a webhook at github, but we couldn't push to github, so we changed
>> the repo to gitbox, and the webhook didn't fire there.
>>
>> Now we use github for the webhook and gitbox for pushing to this asf-site
>> branch.
>>
>>
>>> Is there something in the GitBox sync that stops GitHub webhooks? Still,
>>> requiring a PR doesn't sound like a bad idea in general for this.
>>>
>>>
>> AFAIK hooks are not cloned, so maybe the gitbox repo doesn't have this
>> webhook in github, also the jenkins plugin we're using is specific to
>> github, so it may fail if the request is coming from gitbox or elsewhere.
>>
>> Regarding the PR: these are not strictly required: the jenkins job is set
>> up to "Build when a change is pushed to GitHub" on the master branch (aka
>> the "GitHub hook trigger for GITScm polling" option, because the "Github
>> pull request builder" is going to be deprecated by infra).
>>
>> So I assume changing files directly to master (without a PR) will also
>> trigger the build. We should check that.
>>
>> Kind regards,
>> Antonio
>>
>>
>> Best wishes,
>>>
>>> Neil
>>>
>>>
>> ---------------------------------------------------------------------
>> 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: Automatic website publishing
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 3 Apr 2018 at 11:58 Antonio <an...@vieiro.net> wrote:
> Mmm... the jenkins job fired twice: once for the push (build ok: website
> updated) and another for the merge (build failed because there was
> nothing to commit).
>
Maybe check GitHub squash and merge for the PR?
Best wishes,
Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net
Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Automatic website publishing
Posted by Antonio <an...@vieiro.net>.
Hi,
Mmm... the jenkins job fired twice: once for the push (build ok: website
updated) and another for the merge (build failed because there was
nothing to commit).
I'll ask my robot to fine tune that.
Cheers,
Antonio
On 03/04/18 12:35, Geertjan Wielenga wrote:
> Wow, amazing, it works.
>
> https://netbeans.apache.org/community/events.html
>
> The above I tweaked a bit, created a PR (I think that's the safest way to
> track things), and then merged it -- within 5 minutes the change was live.
>
> Gj
>
> On Tue, Apr 3, 2018 at 12:15 PM, Antonio <an...@vieiro.net> wrote:
>
>>
>>
>> On 03/04/18 11:50, Neil C Smith wrote:
>>
>>> You mean I've finally got to that time where my job has been superseded by
>>> a robot?! ;-)
>>>
>>>
>> Exactly! Lucky you! I still had to fight Jenkins, github & gitbox, I need
>> a robot too! :-)
>>
>>
>>> The push to asf-site on GitBox is what I expected from earlier
>>> conversations, with the webhook triggered on GitHub. But what was the
>>> issue earlier then? PR24 looks like it was on GitHub?
>>>
>>
>> Ah, I wasn't aware of those expectations. The issue was that infra did set
>> up a webhook at github, but we couldn't push to github, so we changed the
>> repo to gitbox, and the webhook didn't fire there.
>>
>> Now we use github for the webhook and gitbox for pushing to this asf-site
>> branch.
>>
>>
>>> Is there something in the GitBox sync that stops GitHub webhooks? Still,
>>> requiring a PR doesn't sound like a bad idea in general for this.
>>>
>>>
>> AFAIK hooks are not cloned, so maybe the gitbox repo doesn't have this
>> webhook in github, also the jenkins plugin we're using is specific to
>> github, so it may fail if the request is coming from gitbox or elsewhere.
>>
>> Regarding the PR: these are not strictly required: the jenkins job is set
>> up to "Build when a change is pushed to GitHub" on the master branch (aka
>> the "GitHub hook trigger for GITScm polling" option, because the "Github
>> pull request builder" is going to be deprecated by infra).
>>
>> So I assume changing files directly to master (without a PR) will also
>> trigger the build. We should check that.
>>
>> Kind regards,
>> Antonio
>>
>>
>> Best wishes,
>>>
>>> Neil
>>>
>>>
>> ---------------------------------------------------------------------
>> 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
Re: Automatic website publishing
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Wow, amazing, it works.
https://netbeans.apache.org/community/events.html
The above I tweaked a bit, created a PR (I think that's the safest way to
track things), and then merged it -- within 5 minutes the change was live.
Gj
On Tue, Apr 3, 2018 at 12:15 PM, Antonio <an...@vieiro.net> wrote:
>
>
> On 03/04/18 11:50, Neil C Smith wrote:
>
>> You mean I've finally got to that time where my job has been superseded by
>> a robot?! ;-)
>>
>>
> Exactly! Lucky you! I still had to fight Jenkins, github & gitbox, I need
> a robot too! :-)
>
>
>> The push to asf-site on GitBox is what I expected from earlier
>> conversations, with the webhook triggered on GitHub. But what was the
>> issue earlier then? PR24 looks like it was on GitHub?
>>
>
> Ah, I wasn't aware of those expectations. The issue was that infra did set
> up a webhook at github, but we couldn't push to github, so we changed the
> repo to gitbox, and the webhook didn't fire there.
>
> Now we use github for the webhook and gitbox for pushing to this asf-site
> branch.
>
>
>> Is there something in the GitBox sync that stops GitHub webhooks? Still,
>> requiring a PR doesn't sound like a bad idea in general for this.
>>
>>
> AFAIK hooks are not cloned, so maybe the gitbox repo doesn't have this
> webhook in github, also the jenkins plugin we're using is specific to
> github, so it may fail if the request is coming from gitbox or elsewhere.
>
> Regarding the PR: these are not strictly required: the jenkins job is set
> up to "Build when a change is pushed to GitHub" on the master branch (aka
> the "GitHub hook trigger for GITScm polling" option, because the "Github
> pull request builder" is going to be deprecated by infra).
>
> So I assume changing files directly to master (without a PR) will also
> trigger the build. We should check that.
>
> Kind regards,
> Antonio
>
>
> Best wishes,
>>
>> Neil
>>
>>
> ---------------------------------------------------------------------
> 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: Automatic website publishing
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 3 Apr 2018 at 12:32 Antonio <an...@vieiro.net> wrote:
> I think PRs are also great, but we should start thinking of removing
> those branches once the PR is merged. Otherwise we'll end up with tons
> of branches.
>
Agreed! In fact, I hadn't realised this was polluting the main repo as
opposed to Geertjan's repo with branches. If we protect the master branch
I wonder if that would enforce editing in the user's fork?
IIRC there's an option to delete the branch when you merge the PR in
GitHub, as well as in the branch list.
Best wishes,
Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net
Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Automatic website publishing
Posted by Antonio <an...@vieiro.net>.
On 03/04/18 12:58, Neil C Smith wrote:
> On Tue, 3 Apr 2018 at 11:15 Antonio <an...@vieiro.net> wrote:
> [...]
>> AFAIK hooks are not cloned, so maybe the gitbox repo doesn't have this
>> webhook in github, also the jenkins plugin we're using is specific to
>> github, so it may fail if the request is coming from gitbox or elsewhere.
>>
>
> No, but I would have expected a GitHub webhook to fire when GitBox syncs.
> Unless the webhook we're talking about is actually part of GitBox's syncing
> process. Anyway, it's working - let's not question the magic.
I talked to infra early in the morning and they didn't know why the
webhook didn't fire from gitbox yesterday for Geertjan's merge. They
looked at it but found nothing. Agreed: it's working so let it be.
>
> Regarding the PR: these are not strictly required: ...
>
>
>> So I assume changing files directly to master (without a PR) will also
>> trigger the build.
>>
>
> No, it's not, unless we switch off direct commits to master (which I'm
> personally in favour of for all our repos, but no-one else seems to be!)
> However, I meant more documenting it as the process to be followed - as
> Geertjan also said, it's safer, and also means we get email notifications.
>
I think PRs are also great, but we should start thinking of removing
those branches once the PR is merged. Otherwise we'll end up with tons
of branches.
Jenkins can also send an additional email if required.
> Time to edit the process I wrote up on the wiki for doing this manually
> then?! Still be tempted to keep in something about checking the asf-site
> commit for expected changes though, at least for now.
>
Maybe we want to keep it for a while, until we bullet proof this. After
that we may want to keep it around as a workaround in case jenkins fails
or a manual intervention is required. Also I think I should document the
(very simple) jenkins job, explaining those little tricks and that a
(infra approved) webhook in github is in place.
Kind regards,
Antonio
> Best wishes,
>
> Neil
>
---------------------------------------------------------------------
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: Automatic website publishing
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 3 Apr 2018 at 11:15 Antonio <an...@vieiro.net> wrote:
> On 03/04/18 11:50, Neil C Smith wrote:
> > You mean I've finally got to that time where my job has been superseded
> by
> > a robot?! ;-)
> >
>
> Exactly! Lucky you! I still had to fight Jenkins, github & gitbox, I
> need a robot too! :-)
>
:-)
> Ah, I wasn't aware of those expectations. The issue was that infra did
> set up a webhook at github, but we couldn't push to github,
This was mentioned in the ticket or an email somewhere - as it's somewhat
of a backdoor for Jenkins to talk to GitBox, makes sense it has to be
within ASF infrastructure?
> AFAIK hooks are not cloned, so maybe the gitbox repo doesn't have this
> webhook in github, also the jenkins plugin we're using is specific to
> github, so it may fail if the request is coming from gitbox or elsewhere.
>
No, but I would have expected a GitHub webhook to fire when GitBox syncs.
Unless the webhook we're talking about is actually part of GitBox's syncing
process. Anyway, it's working - let's not question the magic.
Regarding the PR: these are not strictly required: ...
> So I assume changing files directly to master (without a PR) will also
> trigger the build.
>
No, it's not, unless we switch off direct commits to master (which I'm
personally in favour of for all our repos, but no-one else seems to be!)
However, I meant more documenting it as the process to be followed - as
Geertjan also said, it's safer, and also means we get email notifications.
Time to edit the process I wrote up on the wiki for doing this manually
then?! Still be tempted to keep in something about checking the asf-site
commit for expected changes though, at least for now.
Best wishes,
Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net
Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Automatic website publishing
Posted by Antonio <an...@vieiro.net>.
On 03/04/18 11:50, Neil C Smith wrote:
> You mean I've finally got to that time where my job has been superseded by
> a robot?! ;-)
>
Exactly! Lucky you! I still had to fight Jenkins, github & gitbox, I
need a robot too! :-)
>
> The push to asf-site on GitBox is what I expected from earlier
> conversations, with the webhook triggered on GitHub. But what was the
> issue earlier then? PR24 looks like it was on GitHub?
Ah, I wasn't aware of those expectations. The issue was that infra did
set up a webhook at github, but we couldn't push to github, so we
changed the repo to gitbox, and the webhook didn't fire there.
Now we use github for the webhook and gitbox for pushing to this
asf-site branch.
>
> Is there something in the GitBox sync that stops GitHub webhooks? Still,
> requiring a PR doesn't sound like a bad idea in general for this.
>
AFAIK hooks are not cloned, so maybe the gitbox repo doesn't have this
webhook in github, also the jenkins plugin we're using is specific to
github, so it may fail if the request is coming from gitbox or elsewhere.
Regarding the PR: these are not strictly required: the jenkins job is
set up to "Build when a change is pushed to GitHub" on the master branch
(aka the "GitHub hook trigger for GITScm polling" option, because the
"Github pull request builder" is going to be deprecated by infra).
So I assume changing files directly to master (without a PR) will also
trigger the build. We should check that.
Kind regards,
Antonio
> Best wishes,
>
> Neil
>
---------------------------------------------------------------------
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: Automatic website publishing
Posted by Neil C Smith <ne...@apache.org>.
Hi,
On Mon, 2 Apr 2018 at 20:49 Antonio <an...@vieiro.net> wrote:
> We now have a jenkins task that updates the website whenever master is
> changed (then the asf-site is automagically uploaded to the webserver).
You mean I've finally got to that time where my job has been superseded by
a robot?! ;-)
Great news!
On Tue, 3 Apr 2018 at 08:35 Antonio <an...@vieiro.net> wrote:
> So we finally had to use two different repos: 1. github (master branch)
> for firing the jenkins job through an infra webhook and gitbox (asf-site
> branch) for pushing.
>
The push to asf-site on GitBox is what I expected from earlier
conversations, with the webhook triggered on GitHub. But what was the
issue earlier then? PR24 looks like it was on GitHub?
Is there something in the GitBox sync that stops GitHub webhooks? Still,
requiring a PR doesn't sound like a bad idea in general for this.
Best wishes,
Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net
Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Automatic website publishing
Posted by Antonio <an...@vieiro.net>.
Hi again,
So we finally had to use two different repos: 1. github (master branch)
for firing the jenkins job through an infra webhook and gitbox (asf-site
branch) for pushing.
So again please feel free to submit PRs as appropriate. Let me know if
anything does not work as expected.
Kind regards,
Antonio
P.S.: I added some links to the Apache NetBeans Day UK 2018.
On 02/04/18 23:22, Antonio wrote:
> Exactly: the change is because of my manual build.
>
> Infra added a webhook @github (that's the preferred way nowadays, they
> will deprecate others in the future) but I don't think the webhook moved
> to gitbox.
>
> We can ask them to set up the webhook at gitbox or we can use the one at
> github and then merge to the gitbox repo ourselves. These webhooks can
> be only added by them.
>
> I'll talk to them tomorrow to see what the most efficient approach is.
>
> Thanks,
> Antonio
>
> On 02/04/18 23:16, Geertjan Wielenga wrote:
>> OK, thanks. I can see the change now, but that's because of your manual
>> build, I suppose.
>>
>> Gj
>>
>> On Mon, Apr 2, 2018 at 11:13 PM, Antonio <an...@vieiro.net> wrote:
>>
>>> Hi,
>>>
>>> So the webhook doesn't seem to work from gitbox, but only from github,
>>> right? It seems we've missed [1] from Geertjan.
>>>
>>> Infra said it should work, but doesn't. I'll take a look at that
>>> tomorrow.
>>>
>>> For this one I'll trigger a manual build.
>>>
>>> Thanks,
>>> Antonio
>>>
>>>
>>> [1] https://github.com/apache/incubator-netbeans-website/pull/24
>>>
>>>
>>> On 02/04/18 21:48, Antonio wrote:
>>>
>>>> Hi all,
>>>>
>>>> We now have a jenkins task that updates the website whenever master is
>>>> changed (then the asf-site is automagically uploaded to the
>>>> webserver). All
>>>> this currently takes a few minutes.
>>>>
>>>> I'm not sure I like the final setup (the script is hosted at
>>>> jenkins, not
>>>> in our repos), so I won't close NETBEANS-522 [1] as of yet. Maybe we
>>>> want
>>>> ot modify the script ([2]) and include it inside the asf-site branch
>>>> itself.
>>>>
>>>> Please modify the web pages as you see fit to make sure everything
>>>> works
>>>> correctly.
>>>>
>>>> Thanks,
>>>> Antonio
>>>>
>>>> [1]
>>>> https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-522
>>>>
>>>> [2]
>>>> https://builds.apache.org/view/Incubator Projects/job/incubator-netbean
>>>> s-website
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
Re: Automatic website publishing
Posted by Antonio <an...@vieiro.net>.
Exactly: the change is because of my manual build.
Infra added a webhook @github (that's the preferred way nowadays, they
will deprecate others in the future) but I don't think the webhook moved
to gitbox.
We can ask them to set up the webhook at gitbox or we can use the one at
github and then merge to the gitbox repo ourselves. These webhooks can
be only added by them.
I'll talk to them tomorrow to see what the most efficient approach is.
Thanks,
Antonio
On 02/04/18 23:16, Geertjan Wielenga wrote:
> OK, thanks. I can see the change now, but that's because of your manual
> build, I suppose.
>
> Gj
>
> On Mon, Apr 2, 2018 at 11:13 PM, Antonio <an...@vieiro.net> wrote:
>
>> Hi,
>>
>> So the webhook doesn't seem to work from gitbox, but only from github,
>> right? It seems we've missed [1] from Geertjan.
>>
>> Infra said it should work, but doesn't. I'll take a look at that tomorrow.
>>
>> For this one I'll trigger a manual build.
>>
>> Thanks,
>> Antonio
>>
>>
>> [1] https://github.com/apache/incubator-netbeans-website/pull/24
>>
>>
>> On 02/04/18 21:48, Antonio wrote:
>>
>>> Hi all,
>>>
>>> We now have a jenkins task that updates the website whenever master is
>>> changed (then the asf-site is automagically uploaded to the webserver). All
>>> this currently takes a few minutes.
>>>
>>> I'm not sure I like the final setup (the script is hosted at jenkins, not
>>> in our repos), so I won't close NETBEANS-522 [1] as of yet. Maybe we want
>>> ot modify the script ([2]) and include it inside the asf-site branch itself.
>>>
>>> Please modify the web pages as you see fit to make sure everything works
>>> correctly.
>>>
>>> Thanks,
>>> Antonio
>>>
>>> [1]
>>> https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-522
>>>
>>> [2]
>>> https://builds.apache.org/view/Incubator Projects/job/incubator-netbean
>>> s-website
>>>
>>
>> ---------------------------------------------------------------------
>> 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
Re: Automatic website publishing
Posted by Geertjan Wielenga <ge...@googlemail.com>.
OK, thanks. I can see the change now, but that's because of your manual
build, I suppose.
Gj
On Mon, Apr 2, 2018 at 11:13 PM, Antonio <an...@vieiro.net> wrote:
> Hi,
>
> So the webhook doesn't seem to work from gitbox, but only from github,
> right? It seems we've missed [1] from Geertjan.
>
> Infra said it should work, but doesn't. I'll take a look at that tomorrow.
>
> For this one I'll trigger a manual build.
>
> Thanks,
> Antonio
>
>
> [1] https://github.com/apache/incubator-netbeans-website/pull/24
>
>
> On 02/04/18 21:48, Antonio wrote:
>
>> Hi all,
>>
>> We now have a jenkins task that updates the website whenever master is
>> changed (then the asf-site is automagically uploaded to the webserver). All
>> this currently takes a few minutes.
>>
>> I'm not sure I like the final setup (the script is hosted at jenkins, not
>> in our repos), so I won't close NETBEANS-522 [1] as of yet. Maybe we want
>> ot modify the script ([2]) and include it inside the asf-site branch itself.
>>
>> Please modify the web pages as you see fit to make sure everything works
>> correctly.
>>
>> Thanks,
>> Antonio
>>
>> [1]
>> https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-522
>>
>> [2]
>> https://builds.apache.org/view/Incubator Projects/job/incubator-netbean
>> s-website
>>
>
> ---------------------------------------------------------------------
> 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: Automatic website publishing
Posted by Antonio <an...@vieiro.net>.
Hi,
So the webhook doesn't seem to work from gitbox, but only from github,
right? It seems we've missed [1] from Geertjan.
Infra said it should work, but doesn't. I'll take a look at that tomorrow.
For this one I'll trigger a manual build.
Thanks,
Antonio
[1] https://github.com/apache/incubator-netbeans-website/pull/24
On 02/04/18 21:48, Antonio wrote:
> Hi all,
>
> We now have a jenkins task that updates the website whenever master is
> changed (then the asf-site is automagically uploaded to the webserver).
> All this currently takes a few minutes.
>
> I'm not sure I like the final setup (the script is hosted at jenkins,
> not in our repos), so I won't close NETBEANS-522 [1] as of yet. Maybe we
> want ot modify the script ([2]) and include it inside the asf-site
> branch itself.
>
> Please modify the web pages as you see fit to make sure everything works
> correctly.
>
> Thanks,
> Antonio
>
> [1]
> https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-522
>
> [2]
> https://builds.apache.org/view/Incubator
> Projects/job/incubator-netbeans-website
---------------------------------------------------------------------
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