We have several projects in Octopus Deploy Cloud and we have never had issues deploying to the existing targes.
As of today, all deployment steps get skipped with this message in the logs:
Skipping this step as no matching targets were found
This has affected all projects, all channels and all environments (we have five different environments in five different AWS accounts).
== Skipped: Step 1: Create or Update IIS Website == 10:40:29
Verbose | Searched for targets: 10:40:29 Verbose | *
specifically matching these ids: Machines-534 and Machines-535
| * that are enabled
| * with no id exclusions
| * with no environment exclusions
| * has a role that overlaps: APII
| * with no tenant exclusions
| * has a health status of: Healthy or HasWarnings 10:40:29 Info | Skipping this step as no
matching targets were found
The above is part of the raw log.
All deployment targets in the given environment and channel are Healthy (green). Any idea what can be the cause of this?
You have encountered this bug. This issue can be resolved by upgrading to 2019.10.12 or later.
Related
Is it possible to report on / query the data that is displayed here (red arrows in screen shot below) for individual octopus deployment steps? I have looked at the database schema and their RESTful API but don't see anything. I am trying to generate a report that aggregates time spent for each process across deployments.
The information presented here is calculated from the task log. You can access the task log via the API at /api/{spaceId}/tasks/{taskId}/raw
For example:
| == Success: Step 1: Run a Script ==
01:04:18 Verbose | Run a Script completed
|
| == Success: Worker ==
01:04:12 Verbose | Octopus Server version: 2022.3.425
01:04:12 Verbose | Environment Information:
-- snip ---
01:04:18 Verbose | Successfully finished Run a Script on a Worker
|
From the Task Log view:
There is some examples of interacting with the API for tasks in the OctopusDeploy-Api repo, such as this one to get task details.
The logs around the error is this below. It used to work but after a few days ago, this start failing. I didn't not change deploy flow.
The only change is that we started to pay. Before that we used it as a trial member.
Though I don't think that is the cause...
Does anyone know how to get over this error?
Using app from: /Users/vagrant/deploy/app-production-[REDACTED]-bitrise-signed.apk
Configuration read successfully
Authenticating
Authenticated client created
Create new edit
editID: xxxxxxx
Edit insert created
Upload apks or app bundles
Uploading /Users/vagrant/deploy/app-production-[REDACTED]-bitrise-signed.apk 1/1
Uploaded apk version: 36
Done uploading of 1 apps
New version codes to upload: 36
Applications uploaded
Update track
Release version codes are: [36]
alpha track will be updated.
updated track: alpha
Track updated
Committing edit
Failed to commit edit, error: googleapi: Error 403: You cannot rollout this [REDACTED] because it does not allow any existing users to upgrade to the newly added APKs., forbidden
| |
+---+---------------------------------------------------------------+----------+
| x | google-play-deploy#3.6 (exit code: 1) | 19.44 sec|
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-io/steps-google-play-deploy/issues |
| Source: https://github.com/bitrise-io/steps-google-play-deploy |
+---+---------------------------------------------------------------+----------+
I have a problem with bamboo-artifactory-plugin at bamboo elastic-agent. Build fail with error:
Could not execute task no Plugin with key 'org.jfrog.bamboo.bamboo-artifactory-plugin:maven3Task' is installed.
Bamboo agents on hardware run same build successfully.
I use Bamboo version 7.2, bamboo-artifactory-plugin version 3.2.1 and JFrog Artifactory version 6.18.1
As it looks like, the plugin is not installed on your agent. This may occur due to many reasons. Please try to reinstall the plugin and check the agent's logs.
For example, one possible reason is the lack of memory in the agent. If you see errors such as:
INFO | jvm 1 | 2020/11/10 11:12:36 | 2020-11-10 11:12:36,120 ERROR [remoteEventRebroadcasterMessageListenerContainer-1] [ScanningPluginLoader] Unable to deploy plugin 'org.jfrog.bamboo.bamboo-artifactory-plugin' from 'Unit: /Users/yahavi/bamboo-agent-home/plugins/user-installed/plugin_8527020839401694412_bamboo-artifactory-plugin-3.1.0.jar (1604999532000)'.
INFO | jvm 1 | 2020/11/10 11:12:36 | 2020-11-10 11:12:36,121 ERROR [remoteEventRebroadcasterMessageListenerContainer-1] [ScanningPluginLoader] Because of the following exception:
INFO | jvm 1 | 2020/11/10 11:12:36 | java.lang.OutOfMemoryError: GC overhead limit exceeded
That means your agent has insufficient heap size. I'd recommend on the resolution in this guide: https://confluence.atlassian.com/bamkb/outofmemory-errors-in-bamboo-server-or-in-remote-agent-307038120.html
Edit:
For Elastic agents, you can use this guide:
https://confluence.atlassian.com/bamkb/outofmemory-errors-in-bamboo-elastic-agent-826899144.html
My production site developed in CodeIgniter Frame work, It has more than 10k files, I deployed last week successfully without any issues. Today My deployment got failed, I just corrected one query in script.
I got the below issues
C:\myproject>gcloud app deploy --version 13 app.yaml
Services to deploy:
descriptor: [C:\myproject\app.yaml]
source: [C:\myproject]
target project: [xyz]
target service: [uat]
target version: [13]
target url: [https://uat-dot-xyz.appspot.com]
Do you want to continue (Y/n)? Y
Beginning deployment of service [uat]...
#============================================================#
#= Uploading 0 files to Google Cloud Storage =#
#============================================================#
File upload done.
ERROR: (gcloud.app.deploy) INVALID_ARGUMENT: This deployment has too many files. New versions are limited to 10000 files for this app.
- '#type': type.googleapis.com/google.rpc.BadRequest
fieldViolations:
- description: This deployment has too many files. New versions are limited to 10000
files for this app.
field: version.deployment.files[...]
I referred the below SO posting
gcloud app deploy failed because deployment has too many files for PHP CodeIgnitor files
gcloud app deploy : This deployment has too many files
Approaches for overcoming 10000 file limit on Google App Engine?
Communicating between google app engine services
I enabled .gcloudignore file as per the below and created in myproject
https://cloud.google.com/sdk/gcloud/reference/topic/gcloudignore
How to include files in .gcloudignore that are ignored in .gitignore
C:\>gcloud config set gcloudignore/enabled true
Updated property [gcloudignore/enabled].
C:\>gcloud config list
[accessibility]
screen_reader = False
[compute]
region = region-name
zone = zone-name
[core]
account = xyz#domainname.com
disable_usage_reporting = True
project = xyz
[gcloudignore]
enabled = true
My current Cloud SDK version is: 320.0.0
Installing components from version: 320.0.0
I could not find the solution. Why suddenly My deployment failed Using Gcloud SDK to GAE flexible environment ( Note: My project has more than 10 k files, Upto Last week I didnt get this issue)
Plz, Help me to solve this issue, If I miss anything in this,
Thanks in Advance.
It looks that there was a change on the way App Engine deploy the files.
Running the command gcloud config set app/trigger_build_server_side false solved the issue
Now on Dec 15 this change seems to be reverted and normal deploys should be working as before
At first I was getting this error on my local build server, but I managed to fix it there... the query is still the same, but gatsby isn't throwing any errors with the query. But every time I try to deploy on Netlify it fails with the following message:
toFormat seems to be empty, we need a fileExtension to set it.
1 | fragment GatsbyContentfulFluid_tracedSVG on ContentfulFluid {
> 2 | tracedSVG
| ^
3 | aspectRatio
4 | src
5 | srcSet
6 | sizes
7 | }
failed during stage 'building site': Build script returned non-zero exit code: 1
8 |
9 | query optbuildreposrccomponentsshopProductsJs2136335468 {
10 | products: allContentfulProduct {
11 | edges {
12 | node {
Shutting down logging, 22 messages pending
File path: /opt/build/repo/src/components/shop/Products.js
Plugin: none
This is the same error I was getting locally and I have no idea why it is occurring. There should be no reason that toFormat is a required parameter. This is using the standard gatsby-source-contentful plugin API request which has always served the image without issue in the past. If I change the request to 'fixed' instead of 'fluid' the problem goes away, but I need fluid images for this part of the site.
I emailed the Netlify staff a few days ago, but am yet to receive a reply. Any help would be greatly appreciated.
For Those who are facing the same issue I came up with a simple solution.
Remove from all your file places that you used this extension _tracedSVG.
eg.
GatsbyContentfulFixed_tracedSVG
to
GatsbyContentfulFixed
Stop your gatsby server and use the follow command:
gatsby clean && gatsby develop
Commit and push your changes (in case you are using Github)
On Netlify find the option: Clear cache and deploy site
It should fix your Deployment on Netlify as well errors on your console :)
Two suggestions:
Local: Double check your content for any image references that do not append a suffix of .png or .jpg
Netlify: Clear cache and deploy site