How to fix [ERROR] Failed to execute goal external.atlassian.jgitflow:jgitflow-maven-plugin:1.0-m5.1:release-start (default-cli) on project

Hello folks,

If you ended up in this post, I guess you probably run into some trouble, regarding your Jenkins release job.
So, you have configured a release job that uses the jgitflow-maven-plugin and you get the following error during the build:

[ERROR] Failed to execute goal external.atlassian.jgitflow:jgitflow-maven-plugin:1.0-m5.1:release-start (default-cli) on project [project-name]: Execution default-cli of goal external.atlassian.jgitflow:jgitflow-maven-plugin:1.0-m5.1:release-start failed: String index out of range: -6 -> [Help 1]

Searching the Jira tickets of the plugin,, I found out that there is a workaround, where you have to add an additional behavior of checkout to specific local branch:

Figure 1. Recommended workaround

In my case, I just went directly for the Clean before checkout option, (Source Code Management -> Additional Behaviors -> Add):

Figure 2. My workaround

Both are fine, depending on your preferences.

Cheers!

Advertisements

How to solve Failed to execute ‘send’ on ‘XMLHttpRequest’: Failed to load [filename]

So, the other day I was writing my AngularJS Routing Example for the WCG community and I suddenly got in a kind of trouble: I couldn’t seem to get it working!!!

My app’s critical point was that I was trying to deploy an app that included ng-view, to a browser.

By default, a browser doesn’t allow AJAX requests to files located on your local file system. This happens for security reasons. But, ng-view uses an AJAX request to load templates, so the options are:

  • Configuring your browser in order to allow local files access; (this link explains how to implement this action in Google Chrome)
  • Run your app in a local web server.
The first option is quite straightforward, so I’ll stick with the second one. I recommend users that don’t have locally a web-server, to go for an open-source solution, like http-server, which can be configured very easily.
I’m a Java lover and I have installed one distribution of Tomcat in all of my working instances, so the following demonstration is about running an Angular app to Tomcat:
  • Copy or move your app’s folder to Tomcat’s /webapps folder and execute:
  • Navigate to Tomcat’s /bin folder and execute the startup script:

  • Verify that Tomcat deployed your app:
  • Access your app from Tomcat, you should have a clear console now:
Cheers!