Hello!
We're considering to set up a public CI for Revit Lookup (https://github.com/jeremytammik/RevitLookup). The output could be something like http://dynamobuilds.com/.
I'm thinking Travis or Jenkins for the builds. We would provide the infrastructure and maintenance for this service.
I'd love to get your feedback on this idea.
Best regards,
Peter
Dear Peter,
Thank you very much for your very kind offer!
Thank you also for raising it here in public after our short email conversation.
CI stands for continuous integration, by the way, among many other things:
https://en.wikipedia.org/wiki/Continuous_integration
I think this sounds like a great idea and am happy to support it.
It sounds as if the build system and server would be completely independent of the existing GitHub repository, then.
Would it affect it in any way at all?
How would the automatic builds be triggered?
I hope everybody else who has any thoughts or suggestions on this will chip in and say so.
In the hope to get more feedback, I also added a note of this to today's blog post:
http://thebuildingcoder.typepad.com/blog/2017/03/family-bounding-box-and-aec-hackathon-munich.html#4
Thank you!
Best regards,
Jeremy
Hi Jeremy,
thank you for supporting this idea!
It sounds as if the build system and server would be completely independent of the existing GitHub repository, then.
Exactly. We would provide the necessary infrastructure in-house or on a remote server.
Would it affect it in any way at all?
It should not affect the github repo in any way. If everything works as expected you could add a `build passing` badge (https://github.com/dwyl/repo-badges).
How would the automatic builds be triggered?
As a first step I would just poll the repository every 5 minutes or so and build if a new commit is detected. Later we could think about git hooks, but this is not really necessary.
Best regards,
Peter
Sounds great!
Fully agree.
Looking forward to further ideas and suggestions from the community...
Thank you!
Cheers,
Jeremy
Hi Jeremy,
first version is up and running, see https://lookupbuilds.com
I'm using Jenkins in a multi-branch project configuration to build all branches and tags from your github repository. The output is dual-signed with our certificate, zipped and published to a Amazon S3 bucket.
Currently the 2014.x releases are missing because I have no RevitAPI.dlls in this version.
New commits to the master branch and new tags should trigger a build within about 10 minutes.
I did some very brief testing on my Windows 10 machine with the latest releases for 2015/2016/2017 and master branch. Further testing and feedback by the community would be appreciated.
Best regards,
Peter
Dear Peter,
Thank you very much for setting this up!
I added a note highlighting it to the RevitLookup documentation:
https://github.com/jeremytammik/RevitLookup#builds
Cheers,
Jeremy
Dear Clark,
You install RevitLookup just like any other Revit add-in, by copying the add-in manifest and the assembly DLL to the Revit Add-Ins folder:
http://help.autodesk.com/view/RVT/2018/ENU/?guid=GUID-4FFDB03E-6936-417C-9772-8FC258A261F7
If you specify the full DLL pathname in the add-in manifest, it can also be located elsewhere.
For more information on installing Revit add-ins in general, please refer to the Revit API getting started material:
http://thebuildingcoder.typepad.com/blog/about-the-author.html#2
I added a note on installation to the RevitLookup GitHub documentation for you:
https://github.com/jeremytammik/RevitLookup#installation
Cheers,
Jeremy
Can't find what you're looking for? Ask the community or share your knowledge.