Planet

You can see your Jenkins build history and re-deploy the older APKs from your Mobile Phone !

This is particularly useful when you want to have multiple of version of your Mobile App to your QA or Beta Testers (just like you !) without having to redeploy or notify anyone: you can go back and forth in a time-machine as many times you want !

Jenkins acts like a APK binary repository with full access to:

• Code changes
• Unit-test executions
• Console output

Join JenkinsMobi V4 Beta now and give your feedback today.

JenkinsMobi V4 Beta program continues with the support of Assembla SSO Login.

Assembla.com is Cloud ALM that provides Project Workspaces, featuring project management software elements such as task management, issue tracking, cardwall (Kanban), agile project management, Git/Svn  repositories and scrum meetings.

When you configure Jenkins with Assembla Auth Plugin the Jenkins Login process goes through the Assembla SSO Form-based login: this is now automatically managed by JenkinsMobi V4 Beta.

As usual, everything is plug&play: just enter your Assembla Credentials in the JenkinsMobi settings … and then play with JenkinsMobi V4 Beta !

Reblogged from GitEnterprise:

GerritForge is proud to organise the first European Gerrit Code Review Hackathon in London (UK) for three days: 7th, 8th and 9th of May 2013.
The Hackathon is a great way to have the core Gerrit developer Team working side-by-side on some new exciting new features for the OpenSource community. Some of the major improvements in Gerrit architecture and functionality came out from past Hackathons.

Read more… 23 more words

Keep calm and Gerrit Code Review Hackathon

When you configure Jenkins with OpenID SSO, the authentication phase goes through an external web-site (GitHub, Google or others) for authenticating your credentials: when authentication succeded, Jenkins gives you a Session-ID to continue using the API until the session expires.

From JenkinsMobi V4.6.1 (see how to upgrade from JenkinsMobi home screen) you can even automatically manage a 2-step SSO Authentication with your Google Account and Google Authenticator.

1. Edit your JenkinsMobi settings and put your Jenkins URL and SSO username and password.
2. Whenever your Google SSO request a 2-step authentication, you will see a pop-up asking to enter your one-time verification code
3. Tap on “Auth App” to jump directly to Google Authenticator
4. Read the verification code and tap on the “back” button of your Android phone
5. Enter the verification code and tap Verify
6. JenkinsMobi contacts Google SSO and enters again your SSO credentials and one-time verfication code

Your authenticated session will last for the time-to-live of Jenkins Session: should the session be disconnected, you would need to go through the Google SSO and 2-step verification again.

Enjoy JenkinsMobi with Google Authenticator securely over the Internet

 

 

Thanks to the first feedback of the JenkinsMobi V4 Beta, today we have certified JenkinsMobi with OpenID: you don’t have to do anything, just insert your OpenID credentials in the JenkinsMobi V4 settings and, if you have Jenkins-OpenID SSO, everything will magically works

 

JenkinsMobi V4 Beta program is officially started ! 

Follow the the four simple steps described at http://jenkins-ci.mobi/#v4beta and starting exploring the new possibility and provide your feedback on the new JenkinsMobi V4 Architecture.

Tweet

I was reading this article from Steve and Sacha about the API copyrightability, and found myself in a violent agreement. If you haven’t read it, I highly recommend it.

For those of you who haven’t been following the tech news, the issue at hand is Android — Google neatly side-stepped Java’s compatibility requirements by introducing a new runtime/VM and said that Android is not Java. Oracle sued Google claiming that the Java API is a copyrightable material, and that Google can’t just create a whole new implementation that’s API-compatible with Java. Oracle lost the case, but now Oracle is appealing, and they are garthering legacy vendor friends to argue that API not copyrightable is bad for economy.

But wait, surely more competition is bad for them vendors, but what about the instant gain we the developers got when Android came along, in becoming instantly productive in this entirely new platform?

Looking at the comment secion of the article, I was bit disappointed that some people saw this only as a storm in a teacup, or that this is an issue only about Java, and their favorite programming ecosystem (C#, Ruby, …) are OK. But it’s quite a contrary. If the appeal is successful, it has a broad implication on all sorts of APIs. As they say, first they come for the communists, and you think you are safe, but by the time they come to you, it might be too late!

Take Mono for example. Sure, C# and CLI are under Microsoft Community Promise. But what about the vast APIs in the .NET Framework, which is necessary for writing any meaningul application? What about all the Win32 APIs that Wine implements? Or how about Eucalyptus implementing the Amazon Web Services API? Sure, they might be in a good relationship now, but what if IBM acquires Eucalyptus and started a cloud offering of the same API?

As a developer I benefit every day from the compatibility and being able to migrate from one vendor to another without losing everything. And when I look back at PC/AT, x86 instruction sets, Java EE APIs, and so on, I truly believe that the openness is good not just for us the developers but for the broader economy as a whole.

So after reading the article, I felt like I wanted to help the cause and voice my support, but I wasn’t sure how — I’m just a developer and not a lawyer. So I created a White House petition. Not so much because I expect the White House to do something about it, but it’s a good enough neutral petition site that hopefully people feel safe enough to join. If you agree with the cause, please join the petition and help spread the words, so that our voices get heard.

In previous post my colleague showed how to create RPM packages with CMake. As a really versatile tool it is also able to create and build Visual Studio projects on Windows. This property makes it very valuable when you want to integrate your project into a CI cycle(in our case Jenkins).

Prerequisites:

To be able to compile anything following packages needed to be installed beforehand:

•  CMake. It is helpful to put it in the PATH environment variable so that absolute paths aren’t needed.
• Microsoft Windows SDK for Windows 7 and .NET Framework 4 (the web installer or  the ISOs).  The part “.NET Framework 4” is very important, since when the SDK for the .NET Framework 3.5 is installed you will get following parse error for your *.vcxproject files:
  

  error MSB4066: The attribute “Label” in element is unrecognized

  at the following position:

  <ItemGroup Label=”ProjectConfigurations”>

  Probably equally important is the bitness of the installed SDK. The x64 ISO differs only in one letter from the x86 one. Look for the X if want 64 bit.

• .NET Framework 4, necessary to make msbuild run

It is possible that you encounter following message during your SDK setup:

A problem occurred while installing selected Windows SDK components. Installation of the “Microsoft Windows SDK for Windows 7″ product has reported the following error: Please refer to Samples\Setup\HTML\ConfigDetails.htm document for further information. Please attempt to resolve the problem and then start Windows SDK setup again. If you continue to have problems with this issue, please visit the SDK team support page at http://go.microsoft.com/fwlink/?LinkId=130245. Click the View Log button to review the installation log. To exit, click Finish.

The reason behind this wordy and less informative error message were the Visual C++ Redistributables installed on the system. As suggested by Microsoft KB article removing them all helped.

Makefiles:

For CMake to build anything you need to have a CMakeLists.txt file in your project. For a tutorial on how to use CMake, look at this page. Here is a simple CMakeLists.txt to get you started:

project(MyProject) cmake_minimum_required(VERSION 2.6) set(source_files main.cpp ) include_directories( ${CMAKE_CURRENT_SOURCE_DIR} ) add_executable(MyProject ${source_files}) Building:

To build a project there are few steps necessary. You can enter them in your CI directy or put them in a batch file.

call "%ProgramFiles%\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /Release /x86

With this call all necessary environment variables are set. Be careful on 64 bit platforms as jenkins slave executes this call in a 32 bit context and so “%ProgramFiles%” is resolved to “ProgramFiles (x86)” where the SDK does not lie.

del CMakeCache.txt

This command is not strictly necessary, but it prevents you from working with outdated generated files when you change your configuration.

cmake -G "Visual Studio 10" .

Generates a Visual Studio 2010 Solution. Every change to the solution and the project files will be gone when you call it, so make sure you track all necessary files in the CMakeLists.txt.

cmake --build . --target ALL_BUILD --config Release

The final step. It will net you the MyProject.exe binary. The target parameter is equal to the name of the project in the solution and the config parameter is one of the solution configurations.

Final words:

The hardest and most time consuming part was the setup of prerequisites. Generic, not informative error messages are the worst you can do to a clueless customer. But… when you are done with it, you are only two small steps apart from an automatically built executable.

JenkinsMobi v4 has been showcased in Wasaw yesterday, during the 33rd Degree Conference for Java Developers.

SmartPhones and Tablets have revolutionised the way we think, write and use software: software development on Mobile has and need to be agile … but how can you make one step further and have actually your SmartPhone to drive your development ?

Thanks to Jenkins, can Mobile App development and Continuous Delivery be pushed to the edges?

See how you can follow every step of your development with your SmartPhone end-to-end:

• Continuous Integration and Delivery with Jenkins
• Beta notification and distribution to all Mobile stakeholders
• Test execution
• Issue tracking
• Production monitoring

This is a new dimension for the Jenkins eco-system: you will be able to write your plugins to do even more to shorted your continuous application development, testing and deployment.

Beta testing will start shortly … stay tuned

 

JenkinsMobi v4 is the Mobile Engine that powers the 33rd Degree Conference !

The long wait is over … JenkinsMobi has been completely rewritten and will be officially launched next week, 13-15 March  during the 33rd Degree Conference for Java Developers in Warsaw PL.

We will show the new architecture of JenkinsMobi, designed to completely revolutionize the way to organise your Mobile Application Development lifecycle, from the Continuous Integration to Deployment, QA and management of your Production instances in the Cloud.

Follow the JenkinsMobi v4 talk and change the way you manage your Mobile Apps from TODAY !

JenkinsMobi v4 is available for preview as the official App of the 33rd Degree Conference: DOWNLOAD NOW at  or scan the following QR Code.

JenkinsMobi is back !