[OTTER]Gitlab Secure Ressource gone

[atripp]

Hi @philippe-camelio_3885,

I didn't realize it was possible to create those in Otter

I thought only Generic Git repositories work. There's no GitLab/Github/etc.-specific functionality available in Otter, those are primarily intended for BuildMaster's integrations.

I would just use Generic Git repository, since the Git-base doperations will all be the same.

Cheers,
Alana

[philippe.camelio_3885]

@atripp said in [OTTER]Gitlab Secure Ressource gone:

I would just use Generic Git repository, since the Git-base doperations will all be the same.

This was possible from in Otter 3

I tried to create a Generic Git, but it always asks me for a $commit,

My script

    Git::Checkout-Code
    (
        To: $DossierVisHab,
        From: gitlab-vishab
    );

Git Ressource :

Any advice ?

[philippe.camelio_3885]

@philippe-camelio_3885

Small question, why don't you use the same extension for both Otter and BM ?

[atripp]

Hi @philippe-camelio_3885 ,

In BuildMaster 2022, we redesigned the Git and Source Control experience, which required significant changes to the various Git extensions (Git, GitHub, GitLab, and AzureDevOps).

With these changes, instead of using service-specific operations like GitHub::Get-Source, you can simply use operations like Git::Checkout-Code. Behind the scenes, BuildMaster wires everything up using build variables like $Repository and $Commit.

In Otter, you'll need to specify those variables or To and BranchOrCommit properties, similar to this:

Git::Checkout-Code
(
    To: $DossierVisHab,
    From: gitlab-vishab
    BranchOrCommit: master,
 );

The extensions are indeed the same between BuildMAster and Otter, but they do different things than before. Now, the GitLab extension mostly just provides integration into Issue Tracking, and information intended for the BuildMaster UI, such as a list of organizations, repositories, etc.

Best,
Alana

[philippe.camelio_3885]

@atripp said in [OTTER]Gitlab Secure Ressource gone:

Git::Checkout-Code
(
To: $DossierVisHab,
From: gitlab-vishab,
BranchOrCommit: master
);

Thanks for the explanation.
I made a new test with your suggestion but I still have the same error message.

[atripp]

Hi @philippe-camelio_3885,

Without looking closer or testing it's hard to say, but that error sounds like the property isn't being set? You can see rom the the source code of Git::Checkout-Code, the BranchOrCommit argument (called Objectish in the code) will use DefaultValue of $commit unless a property is specified .

I guess just as a test, does set $commit = master make any difference?

Thanks,
Alana

[philippe.camelio_3885]

Hello @atripp

New error :

Code:

 Vishab
{
    set $DossierVisHab = c:\maestro\scripts\powershell\vishab;

    set $commit = master;
   
    Ensure-Directory $DossierVisHab;

Git::Checkout-Code
(
    To: $DossierVisHab,
    From: gitlab-vishab,
    BranchOrCommit: master,
 );
}

I really like Otter, but with each major version too many functions change or broken, it's frustrating

Migration is a lot of work, we have to retest every otter script we have done.

Best regards
PhilippeC.

[apxltd]

Hi @philippe-camelio_3885 ,

We'll investigate/fix this via OT-507 in an upcoming Otter release. I suspect it's related to the SDK changes that came out of BuildMaster 2023; we do not test Git with Otter, so it's not surprising it doesn't work.

I really like Otter, but with each major version too many functions change or broken, it's frustrating

Yeah same here; unfortunately we're struggling with "product market fit" so the product is going through changes and

The first versions (v1/v2) were designed as an improvement on the "desired state" concepts from Puppet, Chef, DCS, etc. But the whole "Infrastructure as Code" market never really "took" on Windows. And obviously "no one" uses IaC on Linux anymore thanks to Docker.

In the next versions (v3), we repositioned Otter to be "PowerShell job/script runner" and "compliance as code". This is how most customers used the product, so it seemed like there was a market there. That broke a lot of DSC stuff that hardly anyone used (sadly!)

Very open to ideas on where to take Otter; I think security/compliance monitoring is maybe the right direction, but if that's the case, we need to figure out how to get a lot more pre-built code/scripts in Otter.

[philippe.camelio_3885]

Hi @apxltd
Thanks for the answer.
Please, don't give up Otter, it is the most efficient and simple tool to manage scripts from a single point for both Windows and Linux.

Best regards
PhilippeC.

[apxltd]

@philippe-camelio_3885 thank you, I appreciate that! No plans to give up -- it's a passion of mine, and I feel someday we'll figure out a better product marketing fit :)

[atripp]

Hi @philippe-camelio_3885 ,

FYI - I was able to reproduce and fix this, at least the resource resolution portion.

Unfortunately you will still need to have a variable named $Commit and $Repository, but that's a much more complex problem to solve....

This works:

set $Commit = gitlab-vishab;
set $Repository = mast;
Git::Checkout-Code;

Or you could also just set a system-scoped vairalbe with the same name.

This will go in next maintennce release of Otter, which is scheduled May 31, but we can make a pre-release if you'd like.

[philippe.camelio_3885]

@atripp
Thank you for your time and the fix.
I can wait for the next release.

Best regards
PhilippeC.