You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our Docker CI is triggered every merge, but what it builds is the latest release. What we really need, is to build whatever was merged. What I'm suggesting, is to create a new branch in our opam-repository fork, that will build BAP packages directly from the master branch (using the git url, instead of the archive). This will facilitate the release process, as we may be assured that whatever we are realising is actually buildable.
We also, need to have some feedback from dockerhub, that the build was successful (currently one need to go and look at the queue, not very CIish).
The text was updated successfully, but these errors were encountered:
Speaking of the integration, we should be able to get a nice DockerHub build status icon (ala the Travis Build status icon) once the badges/shields#856 is merged.
gitoleg
added a commit
to gitoleg/bap
that referenced
this issue
Jan 18, 2017
Currently, our Docker CI is triggered every merge, but what it builds is the latest release. What we really need, is to build whatever was merged. What I'm suggesting, is to create a new branch in our opam-repository fork, that will build BAP packages directly from the master branch (using the git url, instead of the archive). This will facilitate the release process, as we may be assured that whatever we are realising is actually buildable.
We also, need to have some feedback from dockerhub, that the build was successful (currently one need to go and look at the queue, not very CIish).
The text was updated successfully, but these errors were encountered: