mxclyde / mendix-kubernetes-azure Goto Github PK

We started getting the below error since 26 November across all the application landscape (DEV, QA and PROD - QA and PROD were taken from this git repository):

Error: No such container:path: mendixapp:/build/model/metadata.json
/usr/bin/docker failed with return code 1

It is failing on this step:

This is running Ubuntu 18.04.

Any idea/pointers to what may be causing this?

When running the initial template deploy i get errors on 'Add Task Group'. Gives unhandled error with code 401. If I copy out the section for adding a group and try to import the task group manually i get the following error: Import of task group failed with error TypeError: n.metaTaskInputs.map is not a function.

Few updates can be made to the "Add Task Group: Create New App Onboarding Release pipeline"

1. The definition id passed is 2 assuming that the definition id 2 exists since 1 is the empty release pipeline and 2 is the Initial Mendix setup pipeline. This might not always be the case if it is a project which had these release pipelines cleaned up and newer ones created. Azure Dev Ops doesn't claim a deleted definition id it just does max+1. In this case it would throw a 404, release pipeline doesn't exist error.
2. How about passing 0 based on the Azure Dev Ops recommendation as listed in their documentation https://docs.microsoft.com/en-us/rest/api/azure/devops/release/definitions/create?view=azure-devops-rest-5.1 . This will then auto-generate a defintion with the next sequence number for definition id
3. This I am not too sure but from what I understand we don't need to pass the url and links (which references the wrong release pipeline) as this would be generated as a part of response "Release definition"

	"url": "https://vsrm.dev.azure.com/mxclydedemo/01a29e90-f89b-4f9f-b1ea-2e845b5f3cb2/_apis/Release/definitions/2",
	"_links": {
		"self": {
			"href": "https://vsrm.dev.azure.com/mxclydedemo/01a29e90-f89b-4f9f-b1ea-2e845b5f3cb2/_apis/Release/definitions/2"
		},
		"web": {
			"href": "https://dev.azure.com/mxclydedemo/01a29e90-f89b-4f9f-b1ea-2e845b5f3cb2/_release?definitionId=2"
		}
	}

4. Finally it is no longer in preview so instead of passing /release/definitions?api-version=5.1-preview.3 we can pass /release/definitions?api-version=5.1 but Azure Dev Ops would still handle the redirection even if we did pass the preview version

Reference - Line No 807 https://github.com/MXClyde/mendix-kubernetes-azure/blob/master/manifests/azuredevops/Initial%20Mendix%20Setup.json#L807

Thanks again Clyde for this awesome piece of documentation

Abe

Getting the following error when trying to build in Devops, any suggestions?

Build Agent = Ubuntu 18.04
Using the docker-mendix-buildpack-telegrafext-nonroot build pack.

2019-10-25T15:03:12.0971652Z Step 16/29 : WORKDIR /buildpack 2019-10-25T15:03:12.3028897Z ---> Running in 49c82ca107b4 2019-10-25T15:03:13.1061786Z Removing intermediate container 49c82ca107b4 2019-10-25T15:03:13.1063443Z ---> db26a0f26b8e 2019-10-25T15:03:13.1064238Z Step 17/29 : RUN "/buildpack/compilation" /build /cache && rm -fr /cache /tmp/javasdk /tmp/opt && useradd -r -U -u 1050 -d /root mendix && chown -R mendix /buildpack /build /.java /root 2019-10-25T15:03:13.3101294Z ---> Running in 335f977bd175 2019-10-25T15:03:13.7595624Z �[91m/bin/sh: 1: /buildpack/compilation: Permission denied 2019-10-25T15:03:14.1249185Z �[0mThe command '/bin/sh -c "/buildpack/compilation" /build /cache && rm -fr /cache /tmp/javasdk /tmp/opt && useradd -r -U -u 1050 -d /root mendix && chown -R mendix /buildpack /build /.java /root' returned a non-zero code: 126 2019-10-25T15:03:14.1390865Z ##[error]The command '/bin/sh -c "/buildpack/compilation" /build /cache && rm -fr /cache /tmp/javasdk /tmp/opt && useradd -r -U -u 1050 -d /root mendix && chown -R mendix /buildpack /build /.java /root' returned a non-zero code: 126 2019-10-25T15:03:14.1424510Z ##[error]The process '/opt/hostedtoolcache/docker-stable/17.9.0-ce/x64/docker' failed with exit code 126

The ID mentioned for this (and other similar tasks) is not valid anymore.
The old id 6f9cdff3-a6b9-47e1-90a8-6590ba11e157 needs to be replaced with ffd54dce-ce4f-4080-bdda-a110f334feff which is a task JSON to variable with below specs

Task : JSON to Variable
Description : Task that will read a JSON file and create build and/or release variables available to other tasks for the data in the JSON
Version : 1.0.21
Author : Jeff Przylucki
Help :