I have a web project written in Sitecore 8/uCommerce. I am using Teamcity to compile and package the project and Octopus deploy to push it out. When I commit to SVN Teamcity picks up the changes, compiles and packages it up and Octopus deploys it to the Dev environment. All works well. However when I try to promote to test I get an error...
Error running conventions; running failure conventions... Fatal
10:24:19 Deployment on the Tentacle failed.
In the project I have a post deploy script (PostDeploy.ps1) to remove unwanted config files. There is only one line...
.\DeleteConfig.exe $OctopusEnvironmentName
I changed it to this from..
.\DeleteConfig.exe $OctopusParameters['Octopus.Environment.Name']
Due to an article I read, but this hasn't changed the error. I have also tried..
.\DeleteConfig.exe $OctopusParameters['OctopusEnvironmentName']
Again no effect. If I comment out the line of code I no longer get the error.
I have been trying to fix this for sometime now, read and followed the articles and post I can find on the problem but cannot find the fix.
A slight curveball is that this is the second project we deploy in this way. The first is also Sitecore/uCommerce and in the PostDeploy.ps1 the line
.\DeleteConfig.exe $OctopusParameters['Octopus.Environment.Name']
works perfectly.
Any help or pointers would be appreciated.
You don't need a post deploy script as there is a community task that cleans up any extra configuration files. It's at https://library.octopusdeploy.com/step-templates/9a2b84db-2940-4d9a-b61f-c82df35cee6c/actiontemplate-file-system-clean-configuration-transforms.
If you want to do it your way, I would simply use Poweshell like this:
Get-ChildItem -Filter Web.*.config l Remove-Item
Related
I have a WebApp I am trying to deploy using Elastic Beanstalk. I have set up a code pipeline to my github repo and code build to build it. The build succeeds, but at the last part of the pipeline (the deploy), there is a failure and the logs say the error is
web: dotnet ./DiscoverOnDemand.dll
I have looked at fellow developers procfiles and mine does not seem to be any different, yet I cannot get it working. Does anyone have any ideas?
Procfile
https://github.com/JerryKumarNZ/DiscoverOnDemand/blob/main/Procfile
I have checked the procfile for extra newlines but there were none, and I can't find any online resource that will 'check procfile' for me
Found the reason, in Rider and I couldn't see it, but when I went to edit the file in GitHub I could see a space at the start before web. Removing this fixed the issue, still not sure why it was invisible in Rider
i am getting some errors while trying to build an AWS example "HelloWorld" app using SAM with Maven. Note that i've tried the same procedure using Gradle and everything works fine. I've followed this guide: https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-getting-started-hello-world.html.
The first terminal command "sam init" works fine as it should.
The problems starts with the second part where I typed "sam build", and that's where the following error happens.
Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved: org.apache.maven.plugins:maven-clean-plugin:jar:2.5 was not found in http://www.mycompany.com/maven-repository-manager during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of mrm-maven-plugin has elapsed or updates are forced -> [Help 1]
Despite with this error, the command created the folders for the project but when i open it using IntelliJ, it says that it couldn't find all the dependencies that are in the pom.xml file. I've also tried to delete the .aws folder like someone on the internet suggested but it doesn't worked. Note that i'm using Windows 11
I am using the Visual Studio AWS add-on/plugin to deploy my application, but want to move to a CI/CD server and scripted deployment.
I've installed the AWS SDK for Windows and thus want to use the awsdeploy.exe command line to accomplish this.
I've used msbuild and a publish profile to create the .zip deployable of my application (ASP.NET WebApi project)
I've put together the following command line command:
awsdeploy.exe -r -w -v -l "C:\<path_to>\deploylog.txt" "-DDeploymentPackage=C:\<path_to>\my_app.zip" "-DAWSAccessKey=<my_access_key>" "-DAWSSecretKey=<my_secret_key>" "C:\<path_do>\AWSDeployConfiguration.txt"
The "AWSDeployConfiguration.txt" file is what was generated by VisualStudio when I did the first deployment.
RESULT:
The console output and the text written to the log is:
INFO - Scanning configuration.
INFO - ...inspecting application '<my_app_name>' for environment '<my_environment_name>' and version 'v20180918223701'
Nothing happens with the ELB application.
What am I missing and/or how do I get more information to figure this out?
I posted this question on the AWS forums and got the following answer that also worked for me.
Hi! I have this same what You when I trying run this from cmd. But it You will try check what application is returning You will see that value is 3. Generally everything !=0 is error.
What I did?
1. I checked with Process Monitor if application is doing any network request to AWS - no it even not trying. https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
I decided to recompile awasdeploy.exe and I found out that in the main procedure is a try... catch.. without any logs and just return(3). I added some logs and get a detailed error - look at attached image.
After few attempts I get a list of missing dll files:
AWSSDK.MobileAnalytics.dll
AWSSDK.CognitoIdentity.dll
All these files I found in: C:\Program Files (x86)\AWS SDK for .NET\bin and just simply copied to: C:\Program Files (x86)\AWS Tools\Deployment Tool (next to awsdeploy.exe)
Now deploy is working again.
I am trying to setup an IBM Block Chain setup in my local environment.
I am referring to the below manual for setup :
https://console.ng.bluemix.net/docs/services/blockchain/ibmblockchain_tutorials.html
When following these steps:
1) Setup the environment
Install GoLang
SETUP GOROOT & GOPATH
2) SETUP GITHUB
Under GITHUB setup, at point 6, When I try to run the command go build ./
It should give No errors/text. But it is giving an exception. Please have a look at below screenshot for an exact exception.
Exception-screenshot.
Can anyone help me, how can I solve this error, Ideally build should be successful.
The error is pretty obvious.
Replace
stub *shim.ChaincodeStub with stub shim.ChaincodeStubInterface everywhere in your chaincode_start.go file.
Furthermore, read the following issue on github as it will really help,
https://github.com/IBM-Blockchain/ibm-blockchain-issues/issues/29
When I build my cloudbees project it gives the following error:
ERROR: No such file /scratch/jenkins/workspace/glassfish-myruby/pom.xml
Where my project name is glassfish-myruby.
Go to the job you created and click on the "Workspace" link on the left. This will show you how your project was checked out. The pom may be in a different place than you expect.
I ran into a similar problem. My project was building fine, then suddenly stopped with the same error:
Parsing POMs
ERROR: No such file /scratch/jenkins/workspace/MyMoney/pom.xml
Perhaps you need to specify the correct POM file path in the project configuration?
[cloudbees-deployer] Skipping deployment as build result is FAILURE
Finished: FAILURE
I realized the only thing I had changed was adding a GitHub page (as described in http://pages.github.com/)
For reasons I don't understand, this was causing my project to check out from the gh-pages branch instead of master, as reflected in the console output:
Commencing build of Revision 88d8d7ee822e02aa2cdae11e07265eb7a8403fed (origin/gh-pages)
This was also reflected in the jenkins workspace (it contained the GitHub pages files, rather than my project files).
I'm sure there is a way to get this to work AND use GitHub pages, but for me the GitHub page was just an experiment, so I deleted the branch using:
git push origin --delete gh-pages
I then also did another commit to make sure all was OK and rebuilt.
The project is now checking out from master again and building OK.