Pipeline: Repository Variables in GitHub Bitbucket for Version Info

Blogs, LabVIEW Blog, Snippets
Recently I've been working a lot with pipelines to automate the build aspects of a LabVIEW framework development and it's quite interesting how it all takes in various directions. To be frank, I think there are too many options when you come into this world from a fixed monolithic application world. Anyways a new learning today is the repository variables used as version info. LabVIEW Project & Version Limitation When it comes to LabVIEW (or maybe in other environments too, I'm not sure), you can save the version info of a built config only to the source file, ie., .lvproj in the LabVIEW case. You can't change this version info in the .lvproj file after your build server builds the executable because you usually don't want the build server to…
Read More

Get paid for your source code contribution.

Blogs, Random Thoughts
This blog is from my random thoughts collection.Just imagine what would happen if you are getting paid for your source code contribution. Na na na..! Not for any rubbish feature you add, but for the feature which is getting viral and used by most people of the main repo. For this to happen the main source code in the should be generating the revenue wherever it's used. And that generated revenue should be split to the key feature which is making the people to buy that repo. A mechanism to identify which feature is most used, most used feature is the selling-point. Based on feature usage, money can be split-up and paid to the right contributed persons.So, are you ready to fork a repo, and add some feature to start…
Read More