I am running on minikube.
[web] Running shell script
++ cat ../../VERSION
+ jx promote -b --all-auto --timeout 1h --version 0.0.4
Promoting app tabletoprank-web version 0.0.4 to namespace jx-staging
Using pipeline: ****/tabletoprank-web/master build: #1
Cloning into '/home/jenkins/.jx/environments/****/environment-orioleazure-staging'...
Found remote branch names master, HEAD -> origin/master, master
Switched to branch 'promote-tabletoprank-web-0.0.4'
[promote-tabletoprank-web-0.0.4 3372b38] Promote tabletoprank-web to version 0.0.4
1 file changed, 8 insertions(+), 5 deletions(-)
fatal: unable to get credential storage lock: Read-only file system
To https://github.com/****/environment-orioleazure-staging.git
* [new branch] HEAD -> promote-tabletoprank-web-0.0.4
Created Pull Request: https://github.com/****/environment-orioleazure-staging/pull/1
Using pipeline: ****/tabletoprank-web/master build: #1
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
...
I think it is probably due to fatal: unable to get credential storage lock: Read-only file system
camusd
All 22 comments
@camusd sorry to hear that!
I wonder is there any information in the Pull Request; does the PR CI job complete and be valid? You could always look in Jenkins jx console and check out the jobs on the PR of environment-orioleazure-staging and on master of environment-orioleazure-staging to see if there's any build issues?
jstrachan
on 23 Mar 2018
I figured I'd try creating a cluster on GKE and seeing if I could get a build promoted but I still get an error. Here is the PR CI job build issue I am getting now when I run on GKE:
[-dragonglitter-staging_PR-1-EIWUC7VVN4N44PZJGX7JFP25OITEZW77LD6VRZ3OC3NXUQSYCC7A] Running shell script
+ make build
rm -rf requirements.lock
helm version
Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
helm init
Creating /home/jenkins/.helm
Creating /home/jenkins/.helm/repository
Creating /home/jenkins/.helm/repository/cache
Creating /home/jenkins/.helm/repository/local
Creating /home/jenkins/.helm/plugins
Creating /home/jenkins/.helm/starters
Creating /home/jenkins/.helm/cache/archive
Creating /home/jenkins/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://127.0.0.1:8879/charts
$HELM_HOME has been configured at /home/jenkins/.helm.
Warning: Tiller is already installed in the cluster.
(Use --client-only to suppress this message, or --upgrade to upgrade Tiller to the current version.)
Happy Helming!
helm repo add releases http://jenkins-x-chartmuseum:8080
"releases" has been added to your repositories
helm repo add jenkins-x http://chartmuseum.build.cd.jenkins-x.io
"jenkins-x" has been added to your repositories
helm dependency build "env"
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):
Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: getsockopt: connection refused
...Successfully got an update from the "releases" chart repository
...Successfully got an update from the "stable" chart repository
...Successfully got an update from the "jenkins-x" chart repository
Update Complete. ⎈Happy Helming!⎈
Error: tabletoprank-web chart not found in repo http://jenkins-x-chartmuseum:8080
make: *** [build] Error 1
script returned exit code 2
The charts are showing up in monocular, but it appears that there is an issue pulling the chart. The chart is named 'web' in monocular, but it seems from the error message that it is looking for a chart named 'tabletoprank-web', which is the name of my github repo, while 'web', is the name of my local git repo.
camusd
on 24 Mar 2018
I was able to get it to successfully finish the pipeline by modifying the the Jenkinsfile, Chart.yaml, and values.yaml to reference 'tabletoprank-web' instead of 'web'. Not sure why this fixed it, since everything was previously named 'web'. There must be one place where it is trying to reference to the name of my github repo, which in my case is 'tabletoprank-web'.
camusd
on 25 Mar 2018
In my case, repository name is correct, however, I get same message.
Nothing happens after I merge pull request to environment repository...
Found remote branch names master, HEAD -> origin/master, master, promote-golang-http-0.0.1, promote-golang-http-0.0.2
Switched to branch 'promote-go2-http-0.0.1'
[promote-go2-http-0.0.1 0b85f59] Promote go2-http to version 0.0.1
1 file changed, 3 insertions(+)
To https://github.com/****/environment-pythonlaser-staging.git
* [new branch] HEAD -> promote-go2-http-0.0.1
Created Pull Request: https://github.com/****/environment-pythonlaser-staging/pull/3
Using pipeline: ****/go2-http/master build: #1
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-pythonlaser-staging/pull/3 ref 0b85f59181ec016ae6629cfbdb9786142950d602 Could not find a status for repository ****/environment-pythonlaser-staging with ref 0b85f59181ec016ae6629cfbdb9786142950d602
Pull Request https://github.com/****/environment-pythonlaser-staging/pull/3 is merged at sha 12a35480a263fe2783486a0008e2da427607fe2a
Merge commit has not yet any statuses on repo ****/environment-pythonlaser-staging merge sha 12a35480a263fe2783486a0008e2da427607fe2a
oleksiidzhulai
on 26 Mar 2018
Ok sounds like there's something not quite right with the placeholder replacements that happens after the draft create that jx does. Thanks for reporting, I can take a look at this.
rawlingsj
on 27 Mar 2018
I think the go placement stuff is fixed now btw
jstrachan
on 17 Apr 2018
Hi James. I am also having this problem:
0506d0a7a521545408119b2889f2adff016e5490 Could not find a status for repository */environment-mythzircon-staging with ref 0506d0a7a521545408119b2889f2adff016e5490.
I am wondering if there is an update? I am trying to build on AWS. In my case, the job just hangs.
eecarus
on 19 Apr 2018
That message is a result of the PR build not completing yet on the environment git repository. I wonder if you look in Jenkins at the environment-mythzircon-staging project is the PR build started and still pending? If so it could be your cluster is low on resources maybe?
If the PR build hasn't even been triggered then its probably webhooks (i.e. github can't trigger Jenkins - can't access it due to firewall issues maybe?). If thats the case you could manually trigger the PR build and when that merges, the pipeline in the master branch for environment-mythzircon-staging
jstrachan
on 19 Apr 2018
Hi, For me jx promote stage is failing with following issue:
WARNING: Failed to query the Pull Request last commit status for https://github.com/gauravnavgire/environment-sharkbig-staging/pull/2 ref d2880b9e26bfc49dda7dc3513026a82ab7fe9493 Could not find a status for repository gauravnavgire/environment-sharkbig-staging with ref d2880b9e26bfc49dda7dc3513026a82ab7fe9493
EXITCODE 0error: Pull request https://github.com/gauravnavgire/environment-sharkbig-staging/pull/2 last commit has status error for ref d2880b9e26bfc49dda7dc3513026a82ab7fe9493
I'm not sure why its not able to find the status .
gauravnavgire
on 19 Apr 2018
@gauravnavgire see my comment above. Could you see if the Pull Request build has been triggered in Jenkins? It could be lack of resources or that webhooks are not working.
jstrachan
on 19 Apr 2018
@gauravnavgire @eecarus @odzhu @camusd I've just fixed this issue: #674 so that if, for whatever reason, webhooks are not working/configured/allowed through your firewall, then promotion should still work (albeit slow - it polls every 5 minutes for pending Pull Requests / merges to master)
To try out this fix you can run this:
jx upgrade cli
which should upgrade your jx version to at least 1.2.8 or later to get this fix.
Then either re-create a Jenkins X cluster from scratch or:
- delete your environments via:
jx delete env staging
jx delete env production
Then remove the jobs from jenkins in the UI
jx console
Then recreate the Environments again:
jx create env staging
....
jx create env production
....
then the new projects for the environments should have a background poll of 5 minutes applied. (You can always edit this time to shorter in the Jenkins UI if you Configure the environment projects in the Jenkins UI)
jstrachan
on 19 Apr 2018
@jstrachan Thanks James. Will try the solution you have provided.
And yes I suppose web-hooks are not working. The pull request check fails as the web-hook is "http://www.unconfigured-jenkins-location.com/job/" instead of "http://jenkins.jx.3x.2xx.xx.xxx.nip.io"
gauravnavgire
on 19 Apr 2018
James,
Thank you so much for the quick response. I will start from a fresh install on AWS and update the CLI like you suggested. This will insure that I don't have anything else messing me up, like security groups, and the like.
best regards,
Charlie
From: James Strachan notifications@github.com
Sent: Thursday, April 19, 2018 5:42 AM
To: jenkins-x/jx
Cc: eecarus; Mention
Subject: Re: [jenkins-x/jx] Fails to promote to staging (#493)
@gauravnavgirehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgauravnavgire&data=02%7C01%7C%7Cc7cb9d6b1de243f3cd8808d5a5d9cfff%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597277263394211&sdata=6SLc9tePizR%2FGIsAR19Q4HXe2qD6FALT418eHUC7EZA%3D&reserved=0 @eecarushttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feecarus&data=02%7C01%7C%7Cc7cb9d6b1de243f3cd8808d5a5d9cfff%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597277263394211&sdata=%2BOD3KlWCPFY%2FDPTvTcwyv8Cdg%2FhPs7n%2BfRoyesQPY9c%3D&reserved=0 @odzhuhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fodzhu&data=02%7C01%7C%7Cc7cb9d6b1de243f3cd8808d5a5d9cfff%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597277263550464&sdata=TWau8bBOboppKZ6XSv5ZPkRoJq3F1ObTdzkPe7tZH34%3D&reserved=0 @camusdhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcamusd&data=02%7C01%7C%7Cc7cb9d6b1de243f3cd8808d5a5d9cfff%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597277263550464&sdata=CtoioIvkiWXFciJNAfYhURTf1aXXJJQ6fosgktosN20%3D&reserved=0 I've just fixed this issue: #674https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-x%2Fjx%2Fissues%2F674&data=02%7C01%7C%7Cc7cb9d6b1de243f3cd8808d5a5d9cfff%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597277263550464&sdata=uK6ItquPMD7jBsfUpi%2Fn5nZvNuLWMFynlkNGpb2KSDU%3D&reserved=0 so that if, for whatever reason, webhooks are not working/configured/allowed through your firewall, then promotion should still work (albeit slow - it polls every 5 minutes for pending Pull Requests / merges to master)
To try out this fix you can run this:
jx upgrade cli
which should upgrade your jx version to at least 1.2.8 or later to get this fix.
Then either re-create a Jenkins X cluster from scratch or:
- delete your environments via:
jx delete env staging
jx delete env production
Then remove the jobs from jenkins in the UI
jx console
Then recreate the Environments again:
jx create env staging
....
jx create env production
....
then the new projects for the environments should have a background poll of 5 minutes applied. (You can always edit this time to shorter in the Jenkins UI if you Configure the environment projects in the Jenkins UI)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-x%2Fjx%2Fissues%2F493%23issuecomment-382674910&data=02%7C01%7C%7Cc7cb9d6b1de243f3cd8808d5a5d9cfff%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597277263550464&sdata=Ea50bT1ctWConZzulw1hQN2W8kaZsTQPlxXy8lLwQqY%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGLBBF_vWnAanRrrhJupDjdnm0Ryhu1cks5tqFvsgaJpZM4S5Wl6&data=02%7C01%7C%7Cc7cb9d6b1de243f3cd8808d5a5d9cfff%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597277263550464&sdata=AnQb6eGc%2F1rLbaIJct8KPFRR0AIrCyynTOzCXAFEu0E%3D&reserved=0.
eecarus
on 19 Apr 2018
@jstrachan Hi. Your suggestion worked. I did bump up the number of nodes on the default Kubernetes cluster from 3 to 5, and patiently waited between each step before proceeding to the next step of the demo. Following that, I did not have the issue with the hung promote step. As a second question, is there a way to increase the number of ready Jenkins nodes? it seems that jobs tend to queue up waiting for another slave pod to be allocated.
BTW, this is GREAT! My knowledge of Jenkins, fabric8, and Kubernetes are both so limited that this thing appears like _magic_ to me. I wish I could do something to help you guys.
best regards, Charlie
eecarus
on 20 Apr 2018
@eecarus great, glad its working! :) BTW is the delay around a pipeline being triggered in Jenkins and the build pod not starting up; or are you waiting for the job to appear to start inside Jenkins? If its the latter then that sounds like the slow polling thats the backup to webhooks not working. Its best getting webhooks to work so that builds are triggered within a second or so of a git push.
To diagnose webhooks, if you go into, say, the github repo page then settings then webhooks you can see if github can invoke your jenkins server (there should be webhooks created on each environment or each repo you create/import). It might require whitelisting the github IP addresses to get through your firewall? Another option is to edit the Jenkins projects and reduce the polling from 5 minutes to something much lower - but the worry is you use up your github API limits if you poll too frequently.
jstrachan
on 20 Apr 2018
@eecarus BTW the first build of any kind can be sluggish as the kubernetes nodes need to download the docker images for the build pods etc. You should be able to re-trigger a job directly in the Jenkins UI and it should start executing pretty quick - it can take 10s or so for the pod to actually start running; not sure why its not instant; something to do with the kubernetes-plugin I think
jstrachan
on 20 Apr 2018
@jstrachan when i recreated the vpc, i modified the security group to allow 0.0.0.0. so that must have helped! After you mentioned the webhooks, I double checked that they existed in each repo and that GH thought it was ok.
I can see the jobs in Jenkins queuing up. They tend to go pending waiting for an executor. when an executor pod appears, they’d start running. When there is a PR promote (so there is 2 merge jobs, one to master on the code, and one to the auto promote environment), it almost looks like both jobs are waiting on each other. That’s why I was asking if the number of executor pods was controlled by Jenkins or by Kubernetes or by JX.
Cheers! Thank you again for the fine work. There are some great ideas here.
From: James Strachan notifications@github.com
Sent: Thursday, April 19, 2018 11:25:55 PM
To: jenkins-x/jx
Cc: eecarus; Mention
Subject: Re: [jenkins-x/jx] Fails to promote to staging (#493)
@eecarushttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feecarus&data=02%7C01%7C%7Cabe94aa57aa24f485dc108d5a66e6e3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597915574585987&sdata=Ad3giI8soC%2FTXRzgW5rhnGs3dh%2BnqveyrsQwTeCJjVU%3D&reserved=0 great, glad its working! :) BTW is the delay around a pipeline being triggered in Jenkins and the build pod not starting up; or are you waiting for the job to appear to start inside Jenkins? If its the latter then that sounds like the slow polling thats the backup to webhooks not working. Its best getting webhooks to work so that builds are triggered within a second or so of a git push.
To diagnose webhooks, if you go into, say, the github repo page then settings then webhooks you can see if github can invoke your jenkins server (there should be webhooks created on each environment or each repo you create/import). It might require whitelisting the github IP addresses to get through your firewall? Another option is to edit the Jenkins projects and reduce the polling from 5 minutes to something much lower - but the worry is you use up your github API limits if you poll too frequently.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-x%2Fjx%2Fissues%2F493%23issuecomment-382960736&data=02%7C01%7C%7Cabe94aa57aa24f485dc108d5a66e6e3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597915574585987&sdata=Nx3dJeZzCeXH6l3YKm6hbK8IaVF31%2Faz3XuRn%2FP7Lgg%3D&reserved=0, or mute the threadhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGLBBDFK82cufVPJsqfjEfr_DxEubIFrks5tqVVDgaJpZM4S5Wl6&data=02%7C01%7C%7Cabe94aa57aa24f485dc108d5a66e6e3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636597915574585987&sdata=vHZmDeRyxUlFIJhH%2Bj7Gy6EEhlvJzbYMHyC73YB3aaY%3D&reserved=0.
eecarus
on 20 Apr 2018
incidentally we've made the jx promote command capable of manually triggering the environment's PR or release pipelines if folks haven't got webhooks enabled (or can't use them as they are using minikube/minishift etc) https://github.com/jenkins-x/jx/issues/687
so am hoping this issue is now fixed. Let us know if not and we can reopen!
jstrachan
on 23 Apr 2018
I met the error "Error: pipelinetest chart not found in repo http://jenkins-x-chartmuseum:8080" and in monocular it has the chart "tet".
I am using jx version 1.2.109. And the Jenkinsfile, chart.yaml, values are referred with "tet".
Could you please give some comments on this @jstrachan Thanks a lot.
liuxiaopiao
on 8 Jun 2018
@liuxiaopiao that sounds like a separate issue - could you post your pipeline log to a separate issue please?
jstrachan
on 8 Jun 2018
Per @jstrachan 's guide, currently we can use the same name for repo and Artifact. The issue is gone. Thanks a lot @jstrachan
liuxiaopiao
on 8 Jun 2018
Hi @jstrachan, I had initialized a release build before the PR build was complete (the PR then had stopped in the middle). At the jenkins configuration my pull requests does a clean up and now I do not see older PRs. When I create a new PR that gets built and deployed successfully. How can I create a new release ? Each time it fails when I try to promote with error like:
_422 Validation Failed [{Resource:PullRequest Field:head Code:invalid Message:}]_
When trying to promote from my local jx cli I get the error:
_error: Pull request https://github.com/thbs-bu01/environment-jx-release-1/pull/43 last commit has status error for ref 4b7cc17391530cac475b8ac4c329aa799f35faf3_
rohan-sharma-thbs
on 26 Aug 2019
Related issues
renatoaraujoc
·
3Comments
SmartassSkeleton
·
4Comments
tdcox
·
3Comments
jstrachan
·
4Comments
rudolph9
·
3Comments
Most helpful comment
I figured I'd try creating a cluster on GKE and seeing if I could get a build promoted but I still get an error. Here is the PR CI job build issue I am getting now when I run on GKE:
The charts are showing up in monocular, but it appears that there is an issue pulling the chart. The chart is named 'web' in monocular, but it seems from the error message that it is looking for a chart named 'tabletoprank-web', which is the name of my github repo, while 'web', is the name of my local git repo.