We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In https://github.com/Seneca-CDOT/telescope/blob/master/tools/autodeployment/builds.js#L79-L80 and https://github.com/Seneca-CDOT/telescope/blob/master/tools/autodeployment/builds.js#L68-L71 we have a bug where we don't set the builds.previous to be the current build when changing to a new build, thus losing track of that info.
builds.previous
If you go to our autodeployment server's /status endpoint, you'll see that previous is always null:
/status
previous
null
We should take whatever is current and move it to previous so we don't lose it.
current
The text was updated successfully, but these errors were encountered:
@humphd Can I work on this?
Sorry, something went wrong.
@dhillonks absolutely
dhillonks
Successfully merging a pull request may close this issue.
In https://github.com/Seneca-CDOT/telescope/blob/master/tools/autodeployment/builds.js#L79-L80 and https://github.com/Seneca-CDOT/telescope/blob/master/tools/autodeployment/builds.js#L68-L71 we have a bug where we don't set the
builds.previous
to be the current build when changing to a new build, thus losing track of that info.If you go to our autodeployment server's
/status
endpoint, you'll see thatprevious
is alwaysnull
:We should take whatever is
current
and move it toprevious
so we don't lose it.The text was updated successfully, but these errors were encountered: