Hi , I'm unable to complete this build due to changes in Jenkins. One step is "CANCELED" and another has an "ERROR" . Please see the most recent output here:

=> CANCELED [jenkins-configuration-as-code-sandbox-gitlab-setup 2/5] RUN apt-get update &&  apt-get install -y software-properties-common &&  add-apt-repository -y ppa:deadsnakes/ppa &&  apt-mark hold python2 python2-minimal python2.7 python2.7-mi  52.7s
 => [jenkins-configuration-as-code-sandbox-jenkins-docker 2/6] RUN mkdir /var/jenkins_home/casc_configs                                                                                                                                                    1.4s
 => [jenkins-configuration-as-code-sandbox-jenkins-docker 3/6] COPY ./jenkins.yaml /var/jenkins_home/casc_configs/jenkins.yaml                                                                                                                             0.1s
 => [jenkins-configuration-as-code-sandbox-jenkins-docker 4/6] RUN apt-get update       && apt-get install -y iproute2       && rm -rf /var/lib/apt/lists/*                                                                                               22.0s
 => ERROR [jenkins-configuration-as-code-sandbox-jenkins-docker 5/6] RUN install-plugins.sh   configuration-as-code   blueocean   job-dsl   cloudbees-folder   workflow-aggregator   pipeline-utility-steps   generic-webhook-trigger   git-changelog   v  1.4s
------
 > [jenkins-configuration-as-code-sandbox-jenkins-docker 5/6] RUN install-plugins.sh   configuration-as-code   blueocean   job-dsl   cloudbees-folder   workflow-aggregator   pipeline-utility-steps   generic-webhook-trigger   git-changelog   violation-comments-to-gitlab:
#0 0.954 WARN: install-plugins.sh has been removed, please switch to jenkins-plugin-cli
------
failed to solve: process "/bin/sh -c install-plugins.sh   configuration-as-code   blueocean   job-dsl   cloudbees-folder   workflow-aggregator   pipeline-utility-steps   generic-webhook-trigger   git-changelog   violation-comments-to-gitlab" did not complete successfully: exit code: 1

When I run the docker compose I am getting an error about being unable to execute jenkins-wrapper.sh. If I make this file executable I get other errors:
ERROR: for jenkins-configuration-as-code-sandbox_gitlab-setup_1 Cannot start service gitlab-setup: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: "/bootstrap/main.sh": permission denied": unknown

ERROR: for gitlab-setup Cannot start service gitlab-setup: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: "/bootstrap/main.sh": permission denied": unknown

On running the setup-gitlab.sh the following error occurs, even after configuring git identity.

Jenkins-configuration-as-code-sandbox/gitlab-docker/setup/project1/git-repo/.git/

*** Please tell me who you are.

Run

git config --global user.email "[email protected]"
git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect e-mail address (got 'me@here.(none)')
error: src refspec master does not match any
error: failed to push some refs to 'http://root:thepassword@localhost/root/project20name.git'

Hi,

This is a great project. Thanks for sharing!

The most recent version of gitlab is not compatible with create-personal-access-token.sh.
I've made a PR for a python version of the script

vitalyisaev2/gitlab_token@f00ab87

You could apply the changes to the script yourself... or maybe consider using approach from this fork
agdula@f8051db

I have been successful at installing your plugin in Jenkins and configuring a freestyle job that uses the plugin so that I can reference variables and headers sent from the GitHub JSON based payload.

The Jenkins job that is working right now is configured with a regular hard-coded token, not the Jenkins credential based token option that you provide. I have been trying to migrate away from the hard-coded token to the credential based token without success. In Jenkins I successfully create a user/password based credential without problem but that new Jenkins credential does not display as an option in the “Token Credential” drop down.

Any advice on what I might be doing wrong?

Hi,

the Jenkins service failed to start for me with a complaint that there is no applicable method concurrentBuild() for an argument of boolean type. I finally found that this method was deprecated in version 1.76 of the Job DSL plugin and has apparently been removed since.

I could fix this with the following patch:

diff --git a/jenkins-docker/jenkins.yaml b/jenkins-docker/jenkins.yaml
index 55bb310..b1f6769 100644
--- a/jenkins-docker/jenkins.yaml
+++ b/jenkins-docker/jenkins.yaml
@@ -58,7 +58,9 @@ jobs:
   - script: >
       pipelineJob('Create Jobs Pipeline') {
         quietPeriod(0)
-        concurrentBuild(false)
+        properties {
+          disableConcurrentBuilds()
+        }
         logRotator {
           numToKeep(10)
         }

Cheers,
Christoph