Grains of sand on the beach

Obviously we say ClinkerHQ is linked to opensource software. It’s a product based on the integration of opensource software tools. Precisely what we do is that all these integrated tools form a more sophisticated system to manage the lifecycle of our software engineering projects.

Our team believes that we have a debt to the opensource software community, and all those people and companies behind these tools. This is why that to the best of our ability we try to contribute our grain of sand.

Recently we launched a mirror service located in Spain to improve downloads of Jenkins and SonarQube. From looking at the access statistics we can see it was really needed.

To talk about the Netty project is to talk about one of the biggest projects in recent years. Both Norman Maurer and Trustin Lee are two great engineers who daily share their experience so that we others can learn.

Through twitter we heard they were having problems with their current continuous integration environment, and we didn’t hesitate a second to provide a ClinkerHQ Cloud Instance completely free of charge. The experience during the period of initial setup and migration has been amazing. It’s been very satisfying for our team to see that our product focus, different from our competitors, fits into scenarios that are present on our blackboard.

If you’d like more information about ClinkerHQ, don’t hesitate to get in touch with us at @clinkerhq or hello@clinkerhq.com

Sonar PDF Report Plugin 2.11

We are pleased to announce a new release of Sonar PDF Plugin (Commercial edition).

SonarQube 4.4 was published in July, 31. A lot of changes come with it, and one of them made Sonar PDF Plugin unusable: the XML support in the WS API was removed, only JSON format is available now.

Today, seven days later we are ready to support the JSON API in PDF Plugin. Version 2.11 does not include big features or improvements, but it is compatible with SonarQube 4.4.

So, if you are an early adopter and you are already using 4.4, take a look at the plugin page and request for an evaluation license!

ClinkerHQ Single Sign On

As you perhaps know, ClinkerHQ includes a set of tools that can help you to manage your software development life cycle. But ClinkerHQ goes beyond that, we have developed additional pieces to make as easy as possible what is usually difficult, saving you both time and money.

One of the key parts of this “glue” is ClinkerHQ SSO Gateway. This component acts as an identity provider and authorization source inside the ecosystem. Like any advanced SSO system, ClinkerHQ SSO has four main features:

  • Authentication: Who are you?
  • Authorization: What are you allowed to do?
  • Session propagation: I already know who you are.
  • Anonymous access.

When you do login on every integrated application (Jenkins, Sonar, Redmine, etc) you will always see the same login form (it is actually the SSO Gateway login form). This is authentication:

ClinkerHQ SSO Gateway

After login you will be redirected to the original application. At this point, authorization, the second part of the SSO comes into play. Every application has an SSO plugin installed, which must do the following:

  1. Catch the incoming request
  2. Check the authentication state
  3. Get the list of permissions for the user from the SSO
  4. Set up the logged in session in the concrete application

As a result, the user only perceives that the login form is not the same as the one in the original application. But there is one other feature that you’ll love. If the user opens a new browser tab and goes to another application the logged in session will be automatically propagated; no new login (nor click on login button) is required. This is session propagation, and it is performed as part of point 1 described above. If the incoming request comes with an alive SSO session, the authorization is done automatically (without user interaction).

The Single Sign On provides ClinkerHQ users with two main benefits:

  • Work and surf on the ecosystem doing only one login.
  • Centralize the users and permissions management on one tool.

At this point, you are probably thinking “What is the management tool?” It is ClinkerHQ Desktop, and we will talk about it soon in this blog, so stay tuned!

If you want to see the SSO working, we published a video some time ago (it’s really about configuring a Scala project in ClinkerHQ, but you will perceive the SSO there).

ClinkerHQ for trainers

We’re setting up a new way to use ClinkerHQ.

Up until now, anyone who wanted to use it had two options: ClinkerHQ Cloud, a mode in which you completely forget about the infrastructure and just concentrate on developing your software projects. And on the other hand, ClinkerHQ Virtual Appliance, a virtual machine image that you deploy on your servers.

A while back, we thought it might be a good idea for trainers to be able to have tools like Git, Subversion, Nexus, Jenkins, SonarQube or Redmine suitably installed and configured, and ready to use.

Those professionally engaged in training, and anyone who has organised a training activity, know that configuring the infrastructure they need for the course or seminar is a chore. And it can get complicated if the participants need to access that infrastructure in order to practise.

Yes, we were thinking of tech professionals like you.

Mr. Israel Alcázar. Git Consultant & Trainer. Agile / Lean Consultant & Trainer

As of today, you can use ClinkerHQ Cloud to teach courses or give seminars and talks, in a way that is completely FREE. There’s only one limitation and one request. The limitation is that the instance will be available for a maximum of 7 days. And the request is that, after you use ClinkerHQ, we would love to hear your honest opinion, impressions and suggestions for any improvements through a blog post.

Are you a trainer? Use ClinkerHQ for FREE in your courses, talks or seminars.

What does a “supported stack” mean?

Our home page shows a section named “Supported stacks”, followed by a list of technology stacks. What does this mean?

When we add a supported technology stack we are saying that every tool inside ClinkerHQ is pre-configured to work with that stack, getting the best of each tool for it. You don’t have to configure or add anything.

Obviously, some tools are more coupled to the stack than others. For example, Redmine is exactly the same for Java, PHP or Ruby. On the other hand, Jenkins requires a lot of specific runtime dependencies based on the stack, because it runs builds, tests, and deploys, all of which are technology dependent.

SonarQube requires additional dependencies for different stacks, so when we say that ClinkerHQ supports Scala, it means that we have pre-configured SonarQube to analyze Scala code.

ClinkerHQ currently supports the following stacks:

  • NodeJS
  • Python
  • Java
  • PHP
  • Mac and iOS
  • Ruby
  • Android
  • C++
  • Scala

In this list there are some special stacks, like Mac and iOS, which are supported by providing a dedicated build node running over a MacOS.

Is your preferred stack missing from this list? Tell us!