I know this not a common question that would normally be asked in the support forum. We use the open source version of Gradle in our CI/CD pipeline to build our backend applications and am in the process of getting Gradle 7.6 approved to use in our environment. I am being asked by our Risk Management group whether any advanced algorithms, predictive analytics, dynamic components, machine learning, or artificial intelligence are used within or by this product, and whether any part of the input or output process involves any of these techniques.
I found this article and the enterprise edition, but does it apply to the open sourced version as well. I understand that the Gradle build tool and the Gradle Enterprise software are complete separate products but couldn't get a straight answer on the Gradle support forum which I could understand. I didnt know about this forum so here I am with the same question. Can someone please provide some clarity and shed some light?
Related
I have to say I am fairly new to CI/CD and how to automatically update softwares.
I am developping a monitoring software for industrial customers. We have come to the point where we need to think about an updating strategy to make it easier to deploy our newest version to customers. However, my knowledge on the matter is quite poor and I don't really know where to start.
Our main idea is to have some sort of launcher where, on startup, the software detects that a new version is available and asks the customer if he wants to download it. The problem is that I don't know where to start to put in place that strategy.
Prior to my researches, I had come accross kubernetes, docker, Jenkins, and GitLab but can't figure out if they do actually what I want. Furthermore, I have looked at Microsoft's Configuration Manager but it seemslike you can only update softs that are on your network.
Feel free to ask for any info.
Thank you in advance for your help ! :)
I am new to ODL. I'm using Northbound Networks ZodiacFX switches to learn with.
All the tutorials I read are written on the basis that l2switch is up and working. Without this working I have to manually build all flow table entries to allow basic switch connectivity.
1) What versions of ODL have this feature available
2) Why was proactive l2 switch programming feature removed from ODL?
Thank you.
l2switch was removed in Fluorine, so any version before that (Oxygen would be
the most recent) should have l2switch.
It was removed because the project no longer had an active community. It would
be welcome to revive if there were contributors willing to do the work.
We are a company developing opensource search engine.
It's hosted in github (https://github.com/fastcatgroup/fastcatsearch)
I think we need contributor globaly, but don't know where to start.
Have any good idea or strategies?
Giving it to Apache or Jboss community is good idea?
Thanks.
It's importance that the open-source solution is which many people need, and solution must be stable. Here's an simple strategy.
Make a stable opensource solution
Write a detail manuals online.
Promote an opensource using SNS
If online group getting larger, start to make a offline group.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
There are so many tools out there. You can do so much things around developing that it is a full time job on its own. So why not integrating features / tools to an powerful server application.
Is there a server which integrates (some of) these features:
static code analysis
automated builds (e.g. through maven)
continuious integreation
automated tests
project website (source code, team collaboration, documentation, java doc)
bug tracking
version control (e.g. through SVN)
statistics
download section
code coverage
any other metrics and quality supporting features
I am sure there are more useful features which do not come to my mind right now. There are tools out there supporting one or the other feature.
Is there any software that supports some more of those features? It would be perfect if that software would be free, but at least it should be non commercial. I am mostly using Java.
Thanks in advance.
What you need is a setup for Hudson, Maven, Nexus Repository Manager and a Bug Tracking Tool like Redmine. The Redmine can be started with a Bitnami Stack which includes Subversion.
The code analysis can be done by using cobertura, findbugs etc. with Maven (using Plugins). If you need more metrics take a look at sonar with support of a Maven Plugin.
The Web-Site etc. can be done by using Maven (site generation).
Sounds like you want Cruise Control or Hudson. Both can do most of the items on your laundry list.
I like Launchpad...
Launchpad is a software collaboration platform that provides:
Bug tracking
Code hosting using Bazaar Code reviews
Ubuntu package building
Hosting Translations
Mailing lists
Answer tracking and FAQs
Specification tracking
Take the tour!
The key is the package building. You should check it out.
If your requirement is "[Ff]ree" I'd suggest Hudson. It's quite modern and has a ton of plugins that can take care of the requirements you've asked for. Hudson is very actively maintained and the plugins receive lots of attention too.
Homepage here: http://hudson-ci.org/
List of plugins here: http://wiki.hudson-ci.org/display/HUDSON/Plugins
IRC Channel (great resource for help): irc://chat.freenode.net/#hudson
Hudson literally takes minutes to setup and bootstrap as well, in simple cases.
You can get exactly everything you need in one package, and free, in fazend.com. The platform integrates SVN, Trac, CruiseControl, Maven, etc. You start a project with one click.
I would like to know if you could share some (trusted) sources of information (books, URLs) that you consider the most relevant for learning Windows Installer. They could be for starting on this technology or for an advanced or professional level of knowledge.
Where can a future deployment engineer start and where can he/she go to keep on the right direction (step by step)?
I'm obviously biased but I think my blog and the WiX toolset are good ways to learn:
http://robmensching.com/blog
http://wix.sf.net (click on the Manual or Tutorial links on the right)
Some people like Phil Wilson's "The Definitive Guide to Windows Installer" but I never read it. I learned straight out of the MSI SDK.
I did 7 years of writing InstallScript installers before ever picking up MSI. While there is a huge difference between procedural script-driven imperative installs and data driven declarative installs, they both do the same fundemental thing: deploy software.
I became an MSI Expert but studying everything I could on the domain, writing LOTS of installs and by blogging for 7 years and answering over 4,400 posts on the InstallShield community forums. The only way to go in my book is to have been there and done that.
So the first step in your quest should be to understand the Windows Platform and related technologies very thoroughly. These evolve over the years but you should get a decent understanding of:
Fundamentals
Registry
FileSystem
NTFS
ACL's
DLL Types ( Win32, COM, .NET Assembly)
Win32 API
.NET Base Class Libraries
Service Control Manager Drivers ODBC
SQL IIS Active Directory ( GPO, LDAPand so on )
Global Assembly Cache
WinSxS Cache
DLL Hell
Good and Bad Installer Behavior
The second step is
Tools
Now let's start to writing installs. As Leslie ( Easter I assume ) said in another answer, pick a tool and learn how to use it to accomplish the above things. But don't stop there, as soon as you can go to the next step.
MSI
Start digging deep down into how your tool is working behind the scenes as soon as you can. Just as you can write C# in .NET and look at the IL with ILDASM, learn to use ORCA and see what is happening. Read the MSI SDK. Yes, it's rough and cryptic but I spent 3 months commuting beween DC and TX and I spent at least 16 hours a week traveling away from internet connections but nothing except the SDK to read. Read it, know it, live it... the cryptic help topics will eventually start to click and become second nature.
And finally, read my blog: DeploymentEngineering.com and every other blog you can find.
There is not a simple answer. The primary reason is that most install developers use a specific tool which in turn hides the bulk of Windows Installer behavior. While it would be nice if those developers had an in-depth knowledge of Windows Installer, that's not the case.
My suggestion would be as follows:
Focus on a specific tool. Many of the development environments offer a trial period and some are free. The on-line help for these tools plus the act of building some sample packages will be a useful process.
If practical, consider taking a training class for the tool. I know Flexera sells their basic and advanced InstallShield course manuals. They are a bit over-priced, but it does include need-to-know Windows Installer specifics. The problem you'll run into is that most documentation is specific to the tool without explaining a lot of the connectivity to Windows Installer.
You'll need the Windows Installer SDK -- in addition to the help file, there are some interesting tools and VBScript scripts. Orca is one tool that is included with the SDK and there are similar tools on the Internet (SuperOrca, InstEd, etc.). The SDK is not a great read but it is a great reference. As you come across specific questions regarding Windows Installer use the SDK help file to understand the deeper internals.
Google 'windows installer blog'. You probably don't want to hear that, but there are many great blogs available that cover many bits and pieces of Windows Installer. Make sure you pick up the Windows Installer Team blog.
No matter what path you choose, you'll find learning Windows Installer to be a hands-on process. I hope this helps!
I'm also biased, but this might be helpful. I recently revisited WiX for a real-world Windows Installer project and wrote up my solution which ultimately plugged into a continuous integration server.
The steps in the article take you through using WiX, localizing the MSI, and creating a bootstrapper for installing any prerequisites.
For learning, Tramontana's tutorial WiX helped me a lot.
A nice little blog post about how to debug custom actions is WiX and DTF: Debug a Managed Custom Action and how to generate an MSI log.