Skip to content
New issue

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

Automatically regenerate schema diagrams #179

Merged
merged 2 commits into from
Oct 23, 2015
Merged

Automatically regenerate schema diagrams #179

merged 2 commits into from
Oct 23, 2015

Conversation

lubomir
Copy link
Member

@lubomir lubomir commented Oct 21, 2015

On each push to master, before documentation is deployed, the diagrams
are regenerated.

There is actually an issue with the generated documentation: Travis only
checks out latest 50 commits. If the latest python-pdc-* tag is older
than that, getting version will fail.

JIRA: PDC-1110

@erichuanggit
Copy link
Collaborator

Looks good to me.
If we tag every SP, I think it won't be problem.

@lubomir
Copy link
Member Author

lubomir commented Oct 22, 2015

That could work. However, we need to figure out some consistent way of using the tags. Currently, the version is base only on tags created by tito (and it's actually not correct – dev server shows version as 0.1.0-1.79.g2c7e619). I think we should switch it back to using the manual tags v0.*.* and just make sure that tito builds are done from that commit.

@ycheng-aa
Copy link
Contributor

👍

1 similar comment
@bliuredhat
Copy link
Contributor

+1

On each push to master, before documentation is deployed, the diagrams
are regenerated.

There is actually an issue with the generated documentation: Travis only
checks out latest 50 commits. If the latest python-pdc-* tag is older
than that, getting version will fail.

JIRA: PDC-1110
This was done automatically using the script from previous commit.
@lubomir lubomir merged commit 015fdc3 into master Oct 23, 2015
@lubomir lubomir deleted the update-diagrams branch October 23, 2015 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants