[Scons-dev] Roundup tracker demo instance...

Florian Miedniak florian.miedniak at gmail.com
Thu Oct 1 02:15:26 EDT 2015


For now, I granted write access for all of you to show the developer/user
perspective. I just added admin privileges for your account. Have fun - and
don't get lost in configuration settings  ;-)

2015-10-01 5:02 GMT+02:00 Bill Deegan <bill at baddogconsulting.com>:

> Should we have admin access to the demo instance?
>
> On Wed, Sep 30, 2015 at 10:14 PM, Gary Oberbrunner <garyo at oberbrunner.com>
> wrote:
>
>> I don't seem to have any access.  "Forgot password" doesn't work with any
>> username I tried...
>>
>> On Wed, Sep 30, 2015 at 4:58 PM, Florian Miedniak <
>> florian.miedniak at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I have created a on-demand trial setup of the JIRA + bitbucket
>>> integration here: https://scsandbox.atlassian.net with write access to
>>> both parts for Dirk, Gary, Bill Deegan and William Blevins. I'm sure
>>> there's someone I forgot ;-) Just tell me and I'll add you to the users
>>> list.
>>> The very basic integration works:
>>>   - Mention a JIRA issue (SCSAND-<number>) in a commit message and push
>>> it to https://bitbucket.org/scsandbox/jira_bitbucket_integration -> The
>>> issue name will be a hyper-linked to JIRA
>>>  - If you open a JIRA issue on the right there is a section
>>> "Development" which shows all commits belonging to this issue. Here you can
>>> step-wise dive into the commit until you end up on bitbucket's commit view
>>> - It is possible (but not yet configured) to modify the standard JIRA
>>> issue workflow, so an issue e.g. transits to REVIEW to FIXED when a pull
>>> request gets merged. (And there is a ton of other event/notification
>>> configuration options available ...)
>>>
>>> The trial setup is available until 2015/10/6 (due to the trial license),
>>> so feel free to check its look and feel!
>>>
>>> -Florian
>>>
>>> 2015-09-29 8:52 GMT+02:00 Florian Miedniak <florian.miedniak at gmail.com>:
>>>
>>>>
>>>>
>>>> 2015-09-28 21:42 GMT+02:00 William Blevins <wblevins001 at gmail.com>:
>>>>
>>>>>
>>>>>
>>>>> On Mon, Sep 28, 2015 at 7:45 PM, Russel Winder <russel at winder.org.uk>
>>>>> wrote:
>>>>>
>>>>>> On Mon, 2015-09-28 at 13:56 +0100, William L Blevins wrote:
>>>>>> > […]
>>>>>> > I have used Jira and I think if we can get free instances for the
>>>>>> > project, then the direct jira -> bitbucket <- confluence setup will
>>>>>> > give us a lot of project management control.
>>>>>>
>>>>>> Personally I found Confluence a right royal pain in the arse. JIRA on
>>>>>> the other hand worked very well for me. The issue is whether SCons can
>>>>>> have a JIRA directly linked to the Mercurial repository and its pull
>>>>>> requests.
>>>>>>
>>>>>
>>>>>
>>>>> Since they are all Atlassian products, I cannot imagine "no" to be the
>>>>> answer; otherwise, what is the point?
>>>>>
>>>>>
>>>> William, I agree with you, that it is not the question, *if* there is
>>>> support for connecting bitbucket hosted mercurial repos with JIRA. (
>>>> http://blogs.atlassian.com/2012/07/connect-jira-to-your-git-or-mercurial-repositories-with-the-jira-dvcs-connector)
>>>> It's more the question how mature it is. From my previous experience,
>>>> Atlassian does a quite good job of integrating their products.
>>>> Nevertheless, the best (and IMO only) way to find out, if there are any
>>>> technical / user experiance obstacles left for using JIRA<->Bitbucket for
>>>> Scons, is to give it a try:
>>>> 1. Check for JIRA<->Mercurial on Bitbucket integration with a sandbox
>>>> project
>>>> 2. Adapt the scripts of Dirk to import the existing issues from tigris
>>>>
>>>> I'd volunteer to do this to have a solid basis for further
>>>> decision-making.
>>>>
>>>> -Florian
>>>>
>>>
>>>
>>> _______________________________________________
>>> Scons-dev mailing list
>>> Scons-dev at scons.org
>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>
>>>
>>
>>
>> --
>> Gary
>>
>> _______________________________________________
>> Scons-dev mailing list
>> Scons-dev at scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20151001/867ed634/attachment.html>


More information about the Scons-dev mailing list