singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [singa] nudles commented on issue #585: Release, versioning and continous integration
Date Tue, 31 Mar 2020 14:31:46 GMT
nudles commented on issue #585: Release, versioning and continous integration
URL: https://github.com/apache/singa/issues/585#issuecomment-606664865
 
 
   > 
   > 
   > > 1. if the building of the conda package fails, we need to delete the newly updated
tag? Alternatively, we may need to consider a pre-release version like 3.0.0-alpha0.  Then,
we need to parse the version ID with `-alphaX`.
   > > 2. both the CMake and Conda building scripts need to parse the version from the
git tag.
   > > 3. The CI needs to monitor both the dev and master branch. Only when the tag
of the master branch changes, it uploads the pacakges (and docker images?).
   > 
   > All of this can be easily done with [Github Actions](https://github.com/features/actions).
The CI in Github can be configured to monitor a given branch. There are many actions available
for use that manage the [version tags](https://github.com/sdras/awesome-actions#semantic-versioning),
[create docker containers](https://github.com/sdras/awesome-actions#docker-container-actions)
and so on.
   
   Is it possible to build the website via Github Action? We need the following steps
   1. when there is a new commit to singa-doc, we build the website to generate the html files
   2. push the html files to singa-site as a new commit

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message