Comments (13)
@clyde-johnston can you please look into this?
@thirtytwobits why Buildkite, why not GitHub Actions?
from specification.
I would go for actions. Quite easy to setup and use.
from specification.
Or Travis? It'd be nice to not have so many different CI solutions. Can we keep it at two? Can we move our Travis builds to actions?
from specification.
Can we keep it at two? Can we move our Travis builds to actions?
Someday, sure, but we already use GitHub Actions for website deployment.
from specification.
What event should trigger the build? Any push? Any push to master? Any change to the specification directory?
from specification.
from specification.
Any push.
…
On Tue, Jul 14, 2020, 09:21 clyde-johnston @.***> wrote: What event should trigger the build? Any push? Any push to master? Any push to the specification directory? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#72 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZFIZDMGXDERQRYCK5MTOTR3P2O3ANCNFSM4K6QOBDA .
any push to master, right @pavel-kirienko ?
from specification.
Why? Let it be any push to any branch.
from specification.
consistency. Having a single branch that can publish the spec from means there's no risk of another branch being created that publishes different versions. This would create a condition where the last branch to accept a change would be the one that the public-specification was published from. That seems dangerous.
from specification.
This should not be a problem as each artifact is associated with its respective commit ID. Presumably the artifacts associated with commits in the master branch will be canonical. You would need to switch branches to download a more recent artifact in another branch. When the pull request for this branch has been approved and merged, a new artifact will be built from the new commit in the master branch.
from specification.
Automatic builds and automatic publications are two different things.
The doc should be always built and stored somewhere temporarily regardless of the current branch. If the branch is master, the doc should also be published somewhere so that it can be redirected to from uavcan.org/specification
. Do we have any ideas on how to implement that?
Currently, I update the published doc manually by simply overwriting this file here: https://github.com/UAVCAN/uavcan.org/tree/master/specification
from specification.
The normal method is to deploy the artifact (i.e. publish the document) to the web server once the build is complete. This can be done directly from the specification repository without copying the PDF to the uavcan.org repository.
If you want the specification to be part of the web source, you might want to consider making the specification repo a submodule of the uavcan.org repo. The limitation here is that you would need to check in and commit the submodule directory every time there was a change in the specification repo. It might be possible to automate this by sending a custom event from one repo to another but I am not sure. It would be unusual to do it this way.
from specification.
Clyde has set up auto-build but not auto-publish. Closing because this issue is about the former only, which is done.
from specification.
Related Issues (20)
- Question regarding uavcan.node.Heartbeat VSSC HOT 2
- uavcan.node.Heartbeat comment update HOT 2
- UAVCAN/CAN example in section 4.2.3 is incorrect
- G
- Update branding
- Explain Cyphal portmanteau in Specfication HOT 1
- Cyphal/UDP transfer <-> address/port conversion HOT 1
- Permit incomplete namespaces HOT 1
- Incorrect DSDL examples in 3.4.5.6, page 26
- Remove non-inclusive language
- Reserve the special comment form
- Indicate that node-ID values 126 and 127 are reserved for diagnostic tools irrespective of the maximum node-ID value
- Table 4.6 is missing Service Id bit-width and max value. HOT 1
- Cyphal/UDP: MTU shall remain constant for the duration of a transfer
- Transports with monotonic transfer-ID counter should reserve the maximum value 2^64-1
- Delimited serialization
- Scott messed up the example in section 3.7.5
- Implement the subject-ID range review
- Specify Cyphal/UDP HOT 2
- Specify Cyphal/serial HOT 3
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 specification.