Hello

I meet some problem with variable inheritance between role. Is it a normal behavior ?

Test Case

• ROLE : FATHER / Create Variable : TEST = FATHER

Log-Debug ROLE FATHER - VALEUR = : $TEST

• ROLE : SON / Dependencies: FATHER / Orchestration:

Log-Debug ROLE SON - VALEUR = : $TEST

• Assign Role SON to a Server.

Force "Check configuration"

Results:

Configuration matches template.
ROLE : FATHER - VALEUR = FATHER
Could not resolve variable $TEST 
Collection run complete.
Collection run failed.

While I expect :

ROLE : FATHER - VALEUR = FATHER
ROLE : SON - VALEUR = FATHER 

Best regards

PhilippeC.

Thanks for the fast resolution

Hi @atripp

I upgraded from 2.2.21.

windows extension is 1.6.2

Hello
the following plan

# General
for server VM121007
{
    Execute-PowerShell >>"HELLO WORLD">>
}

is not working on Otter 2.2.22 as expected while it was working fine on the previous version.

If I rollback to the previous version , it is working.

The error message is :

DEBUG: 2020-07-01 15:39:24Z - Job 1389 has no servers, server roles, or environments specified.
DEBUG: 2020-07-01 15:39:24Z - Skipping collection run; execute only.
INFO : 2020-07-01 15:39:24Z - Collection run succeeded.
DEBUG: 2020-07-01 15:39:24Z - Beginning execution run...
ERROR: 2020-07-01 15:39:24Z - Impossible de trouver le chemin d'accès à "C:\ProgramData\Otter\Executions\_E141722", car il n'existe pas.
INFO : 2020-07-01 15:39:24Z - HELLO WORLD
ERROR: 2020-07-01 15:39:24Z - Execution run failed.
DEBUG: 2020-07-01 15:39:24Z - Cleaning up temporary files on Local Server...

This is a big regression for me as many of my orchestration plans fail . Any answer would be helpful.

The extensions are all up to date

Best Regards

PhilippeC.

Hello

I just report a bug in Otter 2.2.21.

Test Case
Create a new Raft RaftTest (I am using a Git raft, but he pb must exist for any kind of raft)
Create a module

• Name : ModuleTest
• Path : PathTest

module ModuleTest
{
    Log-information Hello world
}

Create a Plan : PlanTest
Edit the Plan in GUI Mode
Add the Module RaftTest::PathTest/ModuleTest (drag'n drop)
After you add it, you have an error message:

Call template DSC::ModuleTest
Template Error: template DSC::ModuleTest could not be found.

Switch to Text Mode

##AH:UseTextMode
call RaftTest::ModuleTest();

whereas it shoud be

##AH:UseTextMode
call RaftTest::PathTest/ModuleTest();

If you make the correction and stay in text mode, the plan is working fine.
If you go back to GUI mode you lose the correction and break the plan.

Et voilà !

Hi @rhessinger

I am an old sysadmin so I am really not fluent with .Net stuff and I don't have VS on my computer
but you give me a good starting point, I will make a try.

Best Regards
PhilippeC.

Hello @atripp

I was still looking trying to share the same library in OTTER and Buildmaster despite the difference of the function Gitlab::source.
Is it possible that you create a built-in variable like

$InedoProgram=<Otter | BuildMaster>

in some next release, so I could bypass the problem in my module like this.

If $InedoProgram = Otter
{
        # OTTER
        {
            GitLab::Get-Source
            (
                Credentials: gitlab-inedo,
                Group: ansible/playbooks,
                Project: $tolower($PLAYBOOK),
                DiskPath: $DOSSIER,
                Branch: master,
                KeepInternals: false,
                GitExePath: /usr/bin/git,
                CleanWorkspace: true
            );
        }

}
else
{
        # BUILDMASTER
        {
        GitLab::Get-Source global::GitLab
        (
            Namespace: ansible/playbooks,
            Project: $tolower($PLAYBOOK),
            DiskPath: $DOSSIER,
            Branch: master,
            KeepInternals: false,
            GitExePath: /usr/bin/git,
            CleanWorkspace: false
        );
}

I did the trick with my own variable but it would be nice to have such variable.

" small steps for Inedo, giant leap for me"

Best Regards
PhilippeC.

Error querying list source: 404 Project Not Found

After I installed the pre release extension, I assigned the Resource - Gitlab resource

I used the project name from the resource which is defined at applicaiton level

And I have got the following message:

Error querying list source: 404 Project Not Found

Do I need to make some config on the gitlab side ?

Gitlab Branches only 1 parameter ...

whereas GitHub Branches 2 ...

Bug ?

In my opinion, using $ApplicationName is not possible, at least for Gitlab

Indeed from GitLab ref, we read :

The URL a badge points to, as well as the image URL, can contain placeholders which will be evaluated when displaying the badge. 
The following placeholders are available:
* %{project_path}: Path of a project including the parent groups
* %{project_id}: Database ID associated with a project
* %{default_branch}: Default branch name configured for a project’s repository
* %{commit_sha}: ID of the most recent commit to the default branch of a project’s repository

As %{project_path} is different from $ApplicationName if the project is defined in a group, the only link between the gitlab project and the builmaster application is the commit_sha var.

I think you just need to add stage as querystring and make the search for the result of the pipeline named stage for which exists an active build variable ($commitId in my example) with a value of commit_sha.

• and $commitId has to be unique over all BuidMaster.

Actually, it is not possible to get more variables (ideally %{project_path} at the GitLab::Get-source step.
The filter would be then better (Filter for project_path+ commitid + stage), but this is still a build variable and not an implicit variable like $ApplicationName

I don't know if there a better way because I have just started to use Gitlab.

@atripp said in Buildmaster CI Badge for pipeline step ?:

I'm envisioning adding in a querystring parameter for Stage or something

This should work.

In Gitlab, the definition of the badge would be (for the img part)

https://buildmaster.domain.local/api/ci-badges/image?Key=<API_KEY>&$CommitId=%{commit_sha}&stage=Integration

and it would give a CI badge with the current status of the pipeline stage of the build for which $commitId = {commit_sha}
However, the CI badge text has to be dynamic (3 first characters of stage value seems good enough for me)

• 
• 
• 
• 
• 

2 variables are needed in the query string:

• One to set the application to look for ($CommitId)
• One for the stage for which we want the status

Passing one variable to the query string ($commitId in the exemple) will still work in the same way

For beginners
$CommitId is the value of CommitHash (- {commit_sha} from Gitlab -) assign to a variable at the build level
at the inital pipeline stage.

Example with Gitlab

        GitLab::Get-Source global::GitLab
        (
            Namespace: $Namespace,
            Project: $Project,
            Branch: $Branch,
            PreserveLastModified: true,
            CommitHash => $commit
        );

        Set-BuildVariable CommitId
        (
            Value: $commit
        );

This will work for all kind of source repository I think

Hello

It would be great to have the application page like the otter plan plan (i.e. the plans are grouped by path).

I don't know if I am clear enough, but I think you understand.

Just a suggestion :)
Best Regards
PhilippeC.

Hello
I was looking to create a shared libray with Otter and BM and I meet the following probem with the Gitlab extension:
The credentials are not call in the same way, so it is not possible to share it.

In Otter:

                GitLab::Get-Source
                (
                    Credentials: gitlab-inedo,
                    Group: ansible/playbooks,
                    Project: $tolower($PLAYBOOK),
                    DiskPath: $DOSSIER,
                    Branch: master,
                    KeepInternals: false,
                    GitExePath: /usr/bin/git,
                    CleanWorkspace: true
                );

in BuildMaster:

GitLab::Get-Source global::GitLab
(
    Namespace: ansible/playbooks,
    Project: $tolower($PLAYBOOK),
    DiskPath: $DOSSIER,
    Branch: master,
    KeepInternals: false,
    GitExePath: /usr/bin/git,
    CleanWorkspace: true
);

When do you think the extension will be the same ?
I can bypass the problem, it is just to know.

Best regards
PhilippeC.

Hello
I am using Gitlab CE and successfully display the build step on it.
there I am looking to display badge for the pipeline steps.

Is it possible ?

I am looking for displaying something like that on Gitlab,

<build badge> | <integration badge> | <preprod badge> | <prod badge>

Thanks

Hello

I submit two features for the Application template:

• Select what you want to update (Variables, Pipeline etc ....) when you apply to an existing application

• Ability to apply to a group of applications

I don't know if anyone is also interested but it would be nice to have these features (I can't evaluate if it is simple or not implement)

Best regards
PhilippeC.

Gitlab offers too many options/features we don't need (CI/CD, Kubernetes, Promotheus etc ....).
This is why I was looking for a more lightweight Git repo

I was previously using BonoboGit on Windows which a very basic Git repo but good enough for our need.
As the webhook is not possible, I am looking to replace it.

I think we will stay on GitLab CE - everything is working
and I can't spend my time to evaluate all the possible software, I have to pick one and use it.

I finally switch to GitLab CE

I tested with Gitea.

I get the same 401 response as Gogs (as Gitea is a fork of Gogs it is not a big surprise).

As I am not good enough to create a a dedicated webhook in Gitea or Gogs for BM, I think I will stay stuck to GitHub.

As we are looking for a deeper automation with BM, the weebhook is a need for us, so we will stay on GitHub but we are still looking in my company to have a lightweight internal git repo.

I let you know if I found something.

Thanks for the answer.

Hey

It is not working
Gogs post X-Gogs-Signature whereas Buildmaster is expected X-Hub-Signature
And the GoG's json format seems far away from Github

@atripp
There was no errors, I had variables in the template and I re apply the template because I made some modifications on the Pipeline.
I did not anticiped that the reload of the tempalte removed the new value of the variables.

It would be nice to be able to check when you reload a Tempalte what you want to update (Variables, Pipeline etc ....).

And I did not find if it is possible to re-apply a template to a Group of applications