Grzegorz Lewandowski Atlassian Team

Fisheye/Crucible is an single application with dual licensing (Fisheye and Crucible). You can freely upgrade the application and both products will be upgraded. 

In order to use trial period you should generate evaluation license for Bamboo product and just use it. You can generate license on http://my.atlassian.com/ portal. 

You can have different tiers licenses for Crucible and Fisheye, but when using Fisheye&Crucible, Fisheye license must have an equal or greater number of users to be compatible with Crucible. Any user who has permissions to access Crucible has permissions to access Fisheye as well. Any user who has access to Fisheye might…

Hey, what @Jeremy M wrote is true, however FishEye&Crucible instance supports an Admin Principal workflow. Where, while having 5 uses license you can't have 5+1, you still can use this Admin Principal. You can log in as SuperAdmin by going to _FISHEYE_URL_/admin, you'll be asked for a password. The password was setup…

It means your patch was anchored to given file revision. This allows for iterative pre commit reviews and full file context. More information available here.

Hey, thanks for raising this. I raised a feature request to add possibility to remove project for project level admins. You can track and vote here.

I think you might be missing global permissions that's why the users can't login. If you go to user details on admin pages can you see a _FISHEYE USER_ or _NO ACCESS_ ? If the latter you have to grant global permissions to those users to access the application. More info…

Sorry, I'm not sure what's there to fix. Name of the thread IncrPing3 DPC indicates it's incremental indexing, so I think Fisheye indexes only new changes. I don't know how much repository slurp takes on your instance. There should be a INFO logs indicating how much time it's take for Fisheye to index a single set of…

I believe you should be fine by doing a Fisheye&Crucible backup on Linux machine and just restoring it on Windows one. 

Incremental indexing and full reindex are two different things: * incremental indexing is the thing you'd like to have -> pull newest changes and index new commits only * reindex means dropping current repository indexes and indexing repository from scratch In order to see updates on a repository in Fisheye you need…

I think there may be couple of causes for your problem: * Review lucene index holds date of last modification for given review so if you set a range between 08/01/2017 and 08/02/2017 it'll look for reviews which have last modification timestamp within given range * Custom filter use Lucene indexes thus make sure yours are…

You can use Smart Commits for that purpose. 

Hi, this is a community portal with community help. If you require Atlassian Support raise appropriate issue on https://getsupport.atlassian.com portal. Please attach all log files to speed up the process. 

Bamboo 6.1 release contined support for Miscellanous plugins configuration via Bamboo Specs. Since it was not possible to configure this part of plan via Bamboo Specs before 6.1 some users might have configure it via UI. If you're going to use the same plan specification in 6.1 it could clear all plugin configurations.…

Sorry, I don't really understand the question. Yes, Fisheye is able to index repositories with higher numer of commiters, however, Starter license have a number of limitations and number of historic committers per repository is one of them. 

Bamboo as any other CI is just a tool which runs the cofinguration you asked it to. So I believe on branch A Bamboo executes test which are on branch A, unless obviously you have some scripts whith change this behaviour. I assuming you don't, thus Bamboo on branch 'batchA' builds code on 'batchA' and on branch 'master'…

Generally speaking, Fisheye isn't very good in showing diffs for git commits. Currently it just shows conflict diffs (changes made to both of the parent commits) There's an open improvment issue to track this https://jira.atlassian.com/browse/FE-4004 inconvenience

Fisheye reads whole history of the repository and detects committers of it. Starter license has a limitation that only 5 commiters are allowed. It doesn't matter that nowadays actievly only 3 people commit to that repository. Is the list connected to some repository? Is that repository's name then "next"? Yes, that is a…

TBH, I have troubles understanding your question but generally speaking: * If test is listed on test failures, it means Bamboo detected a failed test and reports it on given branch, within given plan run. It doesn't matter if the test is running sucessfully on your local machine, it failed on Bamboo agent. * When Bamboo…

This information bascially states that given test also fails on a master branch. The background on this issue is that, when you create branch from a master which has failing tests, your branch is going to have them as well, thus Bamboo indicate that those failures might origin from master. 

FishEye&Crucible is a single application with dual licensing. Just go to FISHEYE_URL/admin/sysinfo.do and add your Crucible license. 

I'm not sure what exact problem are you facing: * FishEye server doesn't respond and you can't access it ? * FishEye server starts, it responds but due to broken applinks you can't log in. If the former, it may be hard to help you by using this portal, it's going to be the best if you contact support…

You can also use Bamboo Specs which was released in Bamboo 6.0 and 6.1 to create Specs plans definition to provide a common definition and then create couple of separate plans which have different variables. In this way you'll still have couple of separate plans but you won't need to have to keep them in sync since the…

Hello, yes indeed the referenced tutorial is out of date. You should use **com.atlassian.event.api.EventListener** annotation on a method level. Please make sure you register your bean to an **EventPublisher** instance. **Do not** to deregister it while bean is destroyed, you'll introduce memory leaks otherwise! You can…

You have duplicated **http** in the URL Most probably the valid one will be: http://172.20.0.1:8580/bamboo

You can't use **localhost** as a Bamboo Server URL. Agent runs in a Docker container thus is means it tries to find Bamboo server in the same container (since it looks it under **localhost**). Bamboo runs outside this container thus it can't connect to it. You should use publicly accessible IP as a BAMBOO_SERVER variable 

Take a look FECru server logs in directory: target/fecru/home/var/log/ It should be a information from plugin system stating why plugin can't be enabled. 

Hey, it's not possible. Include/Exclude paths was designed in this way to include or hide certain paths from repository from user perspective. In example, let's consider following changeset: A directoryA/file1 M directoryB/file2 Let's say FishEye is configured in a way that include/exclude paths includes only directoryA…

Technically it is possible to configure paths for a Crucible project. But this function was rather designed to allow users use more than one repository in a single project. I'm not entairly sure how it's going to work in your use case. However, having so big single SVN repository in FishEye is generally not recommended…

Hi, the workflow you desire is not possible in Crucible. Defects and resuming to reviewing upon raising them was designed to be configurable per reviewer, as per: I want to be resumed to a review once somebody raises a defect. Every Crucible user can change this setting for himself in user profile.