Publish only HTML docs corresponding to releases about psyneulink HOT 6 CLOSED

In general this should now be true, in that we consider pushes to master to correspond to a release. It's possible that there have been problems with the build server that generates the documentation, because when this issue was posted we had already released v0.4.6.0, and at the moment the version on the docs seems to be correct. I'm going to try to pinpoint the cause of this

from psyneulink.

@kmantel, I think this one should be fixed.
The current script updates branches/$BRANCH on push to master, devel, and docs branches.
The root documentation is only updated on tags present on master, other pushes to master do not regenerate the root docs (only branches/master)

from psyneulink.

from psyneulink.

@kmantel, I think this one should be fixed.
The current script updates branches/$BRANCH on push to master, devel, and docs branches.
The root documentation is only updated on tags present on master, other pushes to master do not regenerate the root docs (only branches/master)

Checking https://princetonuniversity.github.io/PsyNeuLink/branch/master/, the version is 0.8.5.1+47, and the version of the parent commit of current master is 0.8.5.1+46. I'm guessing the cause of the original problem (if it wasn't entirely before we'd push a new tag on each push to master) was jenkins building docs for the master push before the updated tag was pushed, resulting in the + version in the same way. From what I can see, the Action would handle this. Has the problem happened again?

from psyneulink.

@kmantel, I think this one should be fixed.
The current script updates branches/$BRANCH on push to master, devel, and docs branches.
The root documentation is only updated on tags present on master, other pushes to master do not regenerate the root docs (only branches/master)

Checking https://princetonuniversity.github.io/PsyNeuLink/branch/master/, the version is 0.8.5.1+47, and the version of the parent commit of current master is 0.8.5.1+46. I'm guessing the cause of the original problem (if it wasn't entirely before we'd push a new tag on each push to master) was jenkins building docs for the master push before the updated tag was pushed, resulting in the + version in the same way. From what I can see, the Action would handle this. Has the problem happened again?

The commit ussually comes before the tag, since the commit created on gh and the tag is added after.
Nothing new here, just checking if this can be closed since it looks fixed.

from psyneulink.

Ok, I think we can consider it fixed by #1888.

from psyneulink.