Jump to content

Plastic SCM Plugin for Crucible


Recommended Posts

Okay, so here is my current dilemma (and PLEASE bear with me, as my Linux experience is minimal).  I inherited a Systems Administrator position in which we had Atlassian Jira installed on Ubuntu 14.04.  They wanted it upgraded to the newest release of Ubuntu, and they wanted a bunch more Atlassian products to go along with it.  In a test environment, I've cloned our Jira Server and upgraded it to Ubuntu 16.04.  ALL works well.  I've been able to install Bamboo, Confluence, Crucible, TeamCity, etc, and they've been tested to work perfectly.

I have Plastic SCM installed on a Windows 2012 R2 Server.  I have Crucible installed on a Linux VM (Ubuntu 16.04).  I have a Test Repository setup on our Plastic Server, for our group to test on.

However, when I try to install the Plastic SCM Plugin on Crucible, it breaks something.  And I've found NO instructions online to install or troubleshoot this Plugin installation.  So here are the steps I take and the errors that I run into.


I'm running Crucible 4.4.0 (the most recent version).
I'm using the most recent Crucible Plugin (vs 4.2).

I go to my Administration screen.  
Click "Manage Add-Ons."
I upload the add-on.
I check to see that it's enabled.
I add the repository (and doublecheck the port/hostname/repository)
When i click repositories, it does not show up on my list of "Plugins." 

Then, when I restart the server to make sure the plugin is installed and configured, I get the following error:

An error has occurred:
Error calling server:com.google.gwt.user.client.rpc.StatusCodeException: 500 The call failed on the server; see server log for details Unknown.Hd(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@13019) Unknown.Oub(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@24) Unknown.f8b(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@23) Unknown.gbc(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@18966) Unknown.eCb(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@141) Unknown.xCb(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@13568) Unknown.<anonymous>(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@65) Unknown.awb(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@30) Unknown.dwb(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@46) Unknown.<anonymous>(http://disti-jira-test:8060/static/ooaqce/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html@46)
You are running release CR4.4.0 FE4.4.0 (20170412122150 2017-04-12), please report your release number when reporting bugs.
Link to comment
Share on other sites

  • 2 weeks later...

In the mean time, is there a way you can provide me with the last known compatible configuration of Crucible/Plastic, so I can roll my installations back a version or two. I need to get my team testing the product, and would love to be able to provide them with something for now.

Link to comment
Share on other sites

  • 2 weeks later...

Yikes, that's quite a few versions back, my friend.

Version Release Date

 22 Releases ago, it appears?  So I'm guessing this fix isn't going to be soon?

Link to comment
Share on other sites

  • 2 months later...
  • 6 months later...

So did this get updated?

- I see some movement in the release notes here that the Crucible plugin is working with the 7.0 client?:


Feb 13 2018

Crucible plugin: a bug slipped into our code and prevented our plugin from loading the Crucible repositories. Fixed.

Link to comment
Share on other sites

  • 2 months later...


Yes, it should be also doable:


1) You will need to run a "cm find shelve" where you can get the changeset id for your desired shelve.

2) Once we have the id, we will need to run the following command with the negative value that represents this is actually a shelve and not regular changeset.

      Option 2.1) cm diff cs:-123 --download=c:\ExportFolder

      Option 2.2) cm patch  cs:-123





Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...