Got lost with my VSTS CI build which stoped working overnight with a random 404 error message:
[debug] C:\a\1\Nuget\tempNuGet_293.config
[command]C:\LR\MMS\Services\Mms\TaskAgentProvisioner\... C:\a\1\Nuget\tempNuGet_293.config
Using credentials from config. UserName: VssSessionToken
Response status code does not indicate success: 404 (Not Found).
... and further the failed publisher result:
[debug]rc:1
[debug]success:false [debug]rm -rf C:\a\1\Nuget\tempNuGet_293.config
[error]Error: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\... failed with return code: 1
[error]Packages failed to install
[debug]task result: Failed [error]Return code: 1
Twelve hours ago the Publisher task reported success:
[debug] C:\a\1\Nuget\tempNuGet_285.config
[command]C:\LR\MMS\Services\Mms\TaskAgentProvisioner\... C:\a\1\Nuget\tempNuGet_293.config
Using credentials from config. UserName: VssSessionToken
Your package was pushed.
A ran the build multiple times with the same result. Any idea what is going on?
It turned out this was an issue of VSTS and was resolved; presumably by Microsoft. I just had to wait some hours and the problem disappeared.
Related
The App is working fine, in fact I have built 2 release APKs. This time I modified the code and came to do ./gradlew assembleRelease and I got the following error:
Error
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:mergeReleaseResources'.
Expectation
To generate a healthy APK ready to publish.
Extra Info
I have done the signing and the .keystore in the right place ../android/app
Updated ../android/gradle.properties as instructed
Here is the complete stacktrace:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:mergeReleaseResources'.Close stacktrace
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:110)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:77)
at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59)
at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ResolveBuildCacheKeyExecuter.execute(ResolveBuildCacheKeyExecuter.java:79)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:59)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:101)
at org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute(FinalizeInputFilePropertiesTaskExecuter.java:44)
at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:91)
at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:62)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:59)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.run(EventFiringTaskExecuter.java:51)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:46)
at org.gradle.execution.taskgraph.LocalTaskInfoExecutor.execute(LocalTaskInfoExecutor.java:42)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:277)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:262)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:135)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:130)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.execute(DefaultTaskPlanExecutor.java:200)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.executeWithWork(DefaultTaskPlanExecutor.java:191)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.run(DefaultTaskPlanExecutor.java:130)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Screenshot from the Scan1
Screenshot from the Scan2
Screenshot from the Scan3
from android Studio - I believe it is related to the issue
Screenshot from the Scan4
I believe this could be a duplicate of this question:
Error Execution failed for task ':app:mergeReleaseResources' building APK
The problem occured becaused when I tried to build once, it has
created drawables dirs on android/app/src/main/res/. Then when I tried
on second time, it has shown me this error Execution failed for task
':app:mergeReleaseResources' building APK
I just deleted the drawable-* dirs and it worked.
To remove the directory drawable--*:
rm -rf android/app/src/main/res/drawable-*
There is no drawable folder inside res, still the error occurs.
While running the emulator the build is successful and emulator works fine but I couldn't take release apk because of build failure.
I am trying my hands on Go, and started with the go1.11 beta.
The first Hello world example worked fine and I was able to view it via the browser.
In my second attempt, I created multiple .go files (main.go, datastore.go).
I am able to run it locally and it works fine.
However when I attempt to deploy, I get the following error (deployment in first example worked just fine):
gcloud app deploy
...
File upload done.
Updating service [default]...failed.
ERROR: (gcloud.app.deploy) Error Response: [9] Cloud build 67d67177-13cd-4e80-980a-ea36a0760678 status: FAILURE.
Build error details: go build: cannot use -o with multiple packages
On the server, the build logs show:
Step #1 - "builder": building app with command '[go build -o /tmp/staging735225713/usr/local/bin/start ./...]', env '[PATH=/go/bin:/usr/local/go/bin:/builder/google-cloud-sdk/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=d0f271c7f5b8 HOME=/builder/home BUILDER_OUTPUT=/builder/outputs DEBIAN_FRONTEND=noninteractive GOROOT=/usr/local/go/ GOPATH=/go GOPATH=/tmp/staging735225713/srv/gopath]': err=exit status 1, out=go build: cannot use -o with multiple packages
Finished Step #1 - "builder"
ERROR
ERROR: build step 1 "gcr.io/gae-runtimes/go111_app_builder:go111_20181212_RC00" failed: exit status 1
What am I doing wrong?
UPDATE:
Tried various things, including subfolder or a 'vendor' folder as suggested, but no avail.
Updating service [default]...failed.
ERROR: (gcloud.app.deploy) Error Response: [9] Cloud build 79c39e82-3185-4ae1-a7ff-6afa1be448e7 status: FAILURE.
Build error details: srv/proto/myfile.pb.go:8:2: cannot find package "github.com/golang/protobuf/proto" in any of:
/usr/local/go/src/github.com/golang/protobuf/proto (from $GOROOT)
/tmp/staging770905501/srv/gopath/src/github.com/golang/protobuf/proto (from $GOPATH)
I am trying to run the sample java watson conversation with discovery service in my IBM account.
I have created the java app and added the service details in environment variables and tried to deploy the code but getting below error .
please let me know what is the cause for this issue.
Preparing to start the job...
Cloning the 'master' branch from repo 'https://git.eu-gb.bluemix.net/anil.narayanaswamy002/tnchatbot.git'
Repository successfully cloned
Download https://plugins.gradle.org/m2/com/moowork/gradle/gradle-node-plugin/0.12/gradle-node-plugin-0.12.pom
Download https://plugins.gradle.org/m2/com/moowork/gradle/gradle-gulp-plugin/0.12/gradle-gulp-plugin-0.12.pom
FAILURE: Build failed with an exception.
What went wrong:
A problem occurred configuring root project 'conversation-with-discovery'.
Could not resolve all dependencies for configuration ':classpath'.
Could not resolve org.codehaus.groovy:groovy-backports-compat23:2.3.5.
Required by:
com.ibm.watson.wea.app:conversation-with-discovery:0.5.0-SNAPSHOT
Could not GET 'https://plugins.gradle.org/m2/org/codehaus/groovy/groovy-backports-compat23/2.3.5/groovy-backports-compat23-2.3.5.pom'.
peer not authenticated
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Total time: 8.217 secs
Finished: FAILED
Our deployments for the default module of a particular app are failing, seemingly at random, at least 50% of the time, which is constantly disrupting our workflow.
With verbose logging turned on via appcfg.py update app.yaml --verbose, this error appears on the terminal:
03:43 PM Uploaded 4 files and blobs.
03:43 PM Compilation starting.
2015-09-23 15:43:51,886 INFO appcfg.py:1735 Send: /api/appversion/precompile, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
03:43 PM Compilation completed.
03:43 PM Starting deployment.
2015-09-23 15:43:54,215 INFO appcfg.py:1735 Send: /api/appversion/deploy, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
2015-09-23 15:43:56,341 INFO appcfg.py:2601 HTTP Error (HTTP Error 400: Bad Request Unexpected HTTP status 400)
03:43 PM Rolling back the update.
2015-09-23 15:43:56,341 INFO appcfg.py:1735 Send: /api/appversion/rollback, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
Error 400: --- begin server output ---
Client Error (400)
The request is invalid for an unspecified reason.
--- end server output ---
The failure is extremely consistent, in that most of the time we try deploying the module after not having deployed for a few hours, the deployment attempt will fail with the above output.
Then, without changing any app code, retrying the deployment usually succeeds (but at times, the second attempt also fails, requiring subsequent deployment attempts).
This problem started happening earlier this year. Once the problem started occurring, it has not ceased. Before it occurred, we had no no issues with deployments.
The version of the module being deployed has no effect on the rate of deployment success. We are using the Python runtime for this module.
I have already emailed a Solutions Architect from Google about this, but apart from upgrading to a paid support plan to ensure someone looks into this, he suggested I post on here with the hope that the App Engine support team gets back to me.
App Engine support team - can you find out what is going on (and ideally provide a fix)? If you need more information (such as my app ID), please let me know.
some thing weird thing happened to my Jenkins setup and killing me for whole day to solve the issue.
I have Jenkins job setup which connects to git repository on remote server through Http proxy. Below are the details
Jenkins Version: 1.527
Git client plugin : 1.9.1
Git plugin : 2.2.2
It was working fine for more than a month without any issue. But started giving Http 503 error when it try to pull the latest changes from that repository recently.
Below is the error:
Fetching changes from the remote Git repository
git.exe config remote.origin.url https://<userName>:<Passwd>#<giturl>
Fetching upstream changes from https://<userName>#<giturl>
git.exe --version FATAL: Failed to fetch from https://<userName>#<giturl>
hudson.plugins.git.GitException: Failed to fetch from
https://<userName>#<giturl> at
hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:623) at
hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:855) at
hudson.plugins.git.GitSCM.checkout(GitSCM.java:880) at
hudson.model.AbstractProject.checkout(AbstractProject.java:1408) at
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
at
jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
at hudson.model.Run.execute(Run.java:1597) at
hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at
hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:247) Caused by:
hudson.plugins.git.GitException: Failed to connect to
https://<userName>#<giturl> (status = 503)
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1978)
After working with my network team, it is a issue with Http Proxy. I was asked to use git:// instead of https:// in the github URL. It works great now.