how I ride the bullet - how I set up a testing environment

Discussions and requests related to new CMSimple features, plugins, templates etc. and how to develop.
Please don't ask for support at this forums!
cmb
Posts: 13273
Joined: Tue Jun 21, 2011 11:04 am
Location: Mü-Sa, RLP, DE
Contact:

Re: how I ride the bullet - how I set up a testing environme

Post by cmb » Tue Jan 20, 2015 5:15 pm

cmb wrote:To be honest I had installed JSDoc 3.2.2 manually quite a while ago. For the article Development Environment I had chosen to use Node.js for JSDoc 3 to avoid this manual installation and requiring Java. I presumed that the installation would be easier, but had not tried it.

Now I did. It is not necessary to use the node.js command prompt; a standard cmd.exe is sufficient (however, the installation folder of node.js has to be in the PATH). CD to the XH working copy and run:

Code: Select all

npm install jsdoc@"<=3.3.0"
set path=node_modules\.bin;%PATH%
phing js-doc
The first command creates the folder node_modules, which is then added to the PATH. The last command should create the JS documentation in doc/js/.

If we agree on the local installation, we should ignore the node_module folder (i.e. set the respective SVN property), and I'll add some explanations to the Wiki article.
In the meantime I learned that npm modules can be installed globally with the -g flag. That might be preferable, at least as long as we need no further Node modules.
Christoph M. Becker – Plugins for CMSimple_XH

manu
Posts: 761
Joined: Wed Jun 04, 2008 12:05 pm
Location: St. Gallen - Schweiz
Contact:

Re: how I ride the bullet - how I set up a testing environment

Post by manu » Sat Jan 18, 2020 10:40 am

Wie ich erfahre, werden zahlreiche Test und wohl auch die builds neuerding auf Github mit Travis CI ausgeführt. Damit sind die Angaben in unserem Wiki wohl nicht mehr aktuell.
Es stellen sich folgende Fragen:
  • Welche Installationen braucht ein Publisher noch Client seitig?
  • Wo ist der Workflow mittels travis CI dokumentiert? Wie werden diese Aktionen ausgelöst?
Ziel ist es, im Wiki das Thema "Entwicklungsumgebung" auf den aktuellen Stand zu bringen.

******************

As I learn, numerous tests and probably the builds on Github are carried out with Travis CI. This means that the information in our wiki is no longer up to date.
The following questions arise:
  • Which installations does a publisher still need on the client side?
  • Where is the workflow documented using travis CI? How are these actions triggered?
The aim is to bring the topic "development environment" up to date in the wiki.

manu
Posts: 761
Joined: Wed Jun 04, 2008 12:05 pm
Location: St. Gallen - Schweiz
Contact:

Re: how I ride the bullet - how I set up a testing environment

Post by manu » Thu Jan 30, 2020 12:51 pm

Update:
to install Composer and its depencies globally in Windows:
  • install Composer
  • copy CMSimpleRoot/composer.json to %APPDATA%\Composer
  • execute on command line

    Code: Select all

    composer global install
  • add to your PATH: %APPDATA%\Composer\vendor\bin

Post Reply