I pushed a test JOD update to the jsoftware git repos. The commits show but it 
didn’t trigger a JAL build.

Are the builds scheduled or is there a manual step on your end?

Sent from my iPhone

> On May 21, 2018, at 12:45 PM, chris burke <[email protected]> wrote:
> 
> Each addon repo has a webhook that is used to update the J server addons.
> It sends a "commit" event to the J server so it can update the addon if the
> manifest version has been incremented. This is essentially the same as the
> old SVN commit event.
> 
> Also, if you wish you can transfer your repos to your personal github
> account. I would encourage you to do so, though it will also be fine to
> leave them on the Jsoftware account. To make a transfer, login to github,
> view the repo and open Settings. Then in the Danger Zone at the foot of the
> Settings page, click the Transfer button and follow the instructions. Once
> transferred, you are free to rename it and change access permissions.
> 
> 
> 
>> On Mon, May 21, 2018 at 11:31 AM, John Baker <[email protected]> wrote:
>> 
>> In the next few days I will be committing a minor JOD update to the new
>> GitHub addon repos.
>> 
>> I see I am a contributor to the JOD addons and I have set up local git
>> versions of them. I haven’t tried committing anything yet because I not
>> sure if there is anything else that needs to done to trigger an addon
>> build. When changes were committed to the old SVN repos JAL builds were
>> kicked off. I presume something similar will happen with the Git repos but
>> I fuzzy on the details.
>> 
>> Jdb
>> 
>> Sent from my iPhone
>> ----------------------------------------------------------------------
>> For information about J forums see http://www.jsoftware.com/forums.htm
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to