Comments (13)
Hi @nudles , is it possible to access the machine running jenkins?
from singa.
I have studied how fastai release process works, and semantic versioning and etc.
In my opinion, this topic involves 2 roles:
-
developers code, commit, and send PR to
singa:master
orsinga:dev
. For each PR, CI compiles, builds(conda), tests and returns pass/fail. -
supervisors make release, and decide if the release is a patch, minor, major. There should be some automation here, supervisors then can just run command like
$ make release-patch
or$ make release-minor
.
The automation should do
a) checkout to latest singa:master (the code merged in latest master should pass CI)
b) define new_version
<-- semantic versioning
c) git tag new_version && git push new_version
d) build anaconda package and upload to anaconda cloud
If this approach is ok, then we need to add automation part.
from singa.
Hi @nudles , how release is done currently? is this flag "TRAVIS_SECURE_ENV_VARS" (tool/travis/build.sh line 41) used?
if [[ "$TRAVIS_SECURE_ENV_VARS" == "false" ]];
# install and run unittest
then
echo "no uploading if ANACONDA_UPLOAD_TOKEN not set"
else
# turn off debug to hide the token in travis log
set +x
# upload the package onto anaconda cloud
anaconda -t $ANACONDA_UPLOAD_TOKEN upload -u $USER -l main $CONDA_BLD_PATH/$OS/singa-*.tar.bz2 --force
fi
from singa.
Yes. Currently, we use Travis to build CPU package and Jenkins to build GPU package.
If the TRAVIS_SECURE_ENV_VARS is available, the package will be uploaded to the cloud.
from singa.
Yes. Currently, we use Travis to build CPU package and Jenkins to build GPU package.
If the TRAVIS_SECURE_ENV_VARS is available, the package will be uploaded to the cloud.
Currently, how is the "release" build triggered or how is the Env Var TRAVIS_SECURE_ENV_VARS set? for travis is it done by web UI? https://blog.travis-ci.com/2017-08-24-trigger-custom-build
from singa.
The travis for apache/singa does not upload the package because the variable is not set.
In jenkins, we sync the master branch to nusdbsystem/singa, whose travis will do the building and send the package to the cloud.
from singa.
Hi @nudles , could you kindly advise if this PR caters this issue?
#621
usage: https://github.com/apache/singa/blob/d25539e16b6f3551ad6b1e2a74713025e150d30c/tool/release/README.md
from singa.
- 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
. - both the CMake and Conda building scripts need to parse the version from the git tag.
- 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?).
from singa.
- 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
.- both the CMake and Conda building scripts need to parse the version from the git tag.
- 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. The CI in Github can be configured to monitor a given branch. There are many actions available for use that manage the version tags, create docker containers and so on.
from singa.
Hi @moazreyad , thank you for the advice, I will study how github actions works.
from singa.
- 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
.- both the CMake and Conda building scripts need to parse the version from the git tag.
- 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?).
Regarding 1, after comparing other framework, like tf.
- For
major
release, they havealpha
andbeta
, then followed byrc
, release candidate. - And for
minor
, pre release starts fromrc
. - While
patch
will be released directly.
For torch, similarily:
major
starts fromalpha
, followed byrc
minor
starts fromrc
- patch is released directly.
By right, simply speaking, alpha
is first phase of testing internally. beta
is testing publicly. rc
is almost like stable release unless serious bug is discovered.
from singa.
from singa.
- 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
.- both the CMake and Conda building scripts need to parse the version from the git tag.
- 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. The CI in Github can be configured to monitor a given branch. There are many actions available for use that manage the version tags, create docker containers and so on.
Is it possible to build the website via Github Action? We need the following steps
- when there is a new commit to singa-doc, we build the website to generate the html files
- push the html files to singa-site as a new commit
from singa.
Related Issues (20)
- Switch between CPU and GPU devices for cnn example HOT 4
- Save the downloaded datasets to local directory HOT 2
- Add running scripts for cnn and cifar_distributed_cnn examples HOT 4
- Intermediate information printing HOT 3
- Adding arguments for weight decay and momentum HOT 2
- Increase max epoch for cnn example for better convergence HOT 2
- Update CMakeLists.txt for release 4.0.0 HOT 1
- Check Apache license header for release 4.0.0
- OpenCL Compilation Fails
- Upload Release 4.0.0 Package to SVN HOT 1
- Update the NOTICE file for images HOT 1
- gitignore and gitmodules should be removed from the release tar file HOT 2
- Create a new branch dev-postgresql HOT 2
- Create the SumError New Loss Function HOT 1
- Dynamic Creation of Models HOT 2
- Need to return the gradients from optimizer HOT 4
- Maximum recursion depth exceeded in comparison for string HOT 1
- can sparse all-reduce keep efficiency with large number of gpu workers?
- Update bloodmnist example by refining inline comments HOT 2
- Update documentation for distributed training HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from singa.