I'm trying to setup my build definition with YAML. I'm using the AppCenterDistribute task. It requires and endpoint to MS App Center. I've setup one as per this tutorial.
However, I got that error message:
"Step input serverEndpoint references endpoint Appcenter which could not be found. The service endpoint does not exist or has not been authorized for use."
This is exactly the same issue as this post although I've made sure that I AM in the correct VSTS project.
What could be the problem? I can't even run my build now.
Here's the YAML section:
variables:
APKName: 'com.project.this.apk'
- task: AppCenterDistribute#1
displayName: Deploy APK to App Center
inputs:
serverEndpoint: Appcenter
appSlug: 'Project/Learn'
appFile: '$(build.artifactstagingdirectory)\$(APKName)'
symbolsIncludeParentDirectory: false
releaseNotesInput: Notes
Note that I do have a normal VSTS web build (with a slightly different name) in the same VSTS project that does build and can distribute using the same endpoint to App Center.
Here's the error when I submit a YAML build:
I can also reproduce the issue when the App Center Distribute task is added in a YAML build definition.
And I also create an issue App Center Distribute task show errors when queuing YAML build for it. You can follow up.
You followed the App Center tutorial but you still have to create the Endpoint in VSTS which I think is what you're missing. It cannot be done through your Yaml.
To do so, connect to VSTS and start creating a new empty-process build definition MANUALLY for the SAME project. Add the the "App Center Distribute" task. There is a dropdown for the endpoint. It is empty and there is a "New" button to create one. Do so and give it the name that you use in your Yaml. Then you can cancel your build definition creation and use your Yaml.
UPDATE:
I replied too fast as you said you already have a build defintion working fine with your App Center endpoint. I still keep the above as it could help others.
However, when I compare your Yaml to mine, I notice that I use quotes while you don't. That may be the issue (also I may just have quotes because I have a space in my endpoint name and you don't).
serverEndpoint: 'App Center'
On your existing working build definition, did you try the "View Yaml" button on the top right corner? This gives you the corresponding yaml and it is very useful :-)
Related
In AWS Codebuild's build project I am trying to set my FILE_PATH "Don't start a build under these conditions." However, I can't get it to work.
how would I go about setting the proper regex that the aws build project will recognize?
info
Source Provider: GitHub
Event type: Push
Commits to this file should not trigger a build: README.md
I don't believe amazon is following the traditional regex pattern but here is a picture what I currently have (I based it on the documentation where they have ^buildspec.*). Also this is just an example I want to get working before I move on, the real requirement is to list multiple files to be ignored by my build project.
P.S. I tried read this post but still could not figure it out. Specify file_path while triggering AWS codebuil
Working on usage of GitLab web hooks for activating Google Cloud Build triggers. Problem that I'm facing is that my web hook to push trigger is working fine, but merge trigger is never started, instead push trigger is activated. On GitLab side web hook URLs are different and pointing to right trigger URLs.
While trying to troubleshoot has following: when using dummy build trigger that has inline default step ( ubuntu image to run echo hello world) it works fine, when I'm adding Substitution vars getting an error:
Your build failed to run: generic::invalid_argument: generic::invalid_argument: invalid value for 'build.substitutions': key in the template "URL" is not a valid built-in substitution
_URL is using $(body.project.git_ssh_url), which in accordance to doc should be fine for Merge request event , so it could mean that there is a difference on event type.
Please advise or suggest direction for debugging like get logs of trigger build events.
Best,
Alex
P.S. Used/read docs for web hooks and substitution already, so please do not recommend to read general docs again.
I'm working with AWS Amplify, specifically following this tutorial AWS-Hands-On-Tutorial.
I'm getting a build failure when I try to deploy the application.
So far I have tried creating multiple backend environments and connecting them with the frontend, hoping that this would alleviate the issue. The error message leads me to believe that the deploy is not set up to also detect the backend environment, despite that I have it set to do so.
Also, I have tried changing the environment that is set to deploy with the frontend by creating another develop branch to see if that is the issue.
I've had no success with trying any of these, the build continues to fail. I have also tried running the 'amplify env add' command as the error message states. I have not however tried "restoring its definition in your team-provider-info.json" as I'm not sure what that entails and can't find any information on it. Regardless, I would think creating a new environment would solve the potential issues there, and it didn't. Any help is appreciated.
Due to the documentation being out of date, I completed the steps below to resolve this issue:
Under Build Settings > Add package version override for Amplify CLI and leave it as 'latest'
When the tutorial advises to "update your front end branch to point to the backend environment you just created. Under the branch name, choose Edit...", where the tutorial advises to use 'dev' it actually had us setup 'staging', choose that instead.
Lastly, we need to setup a 'Service Role' under General. Select General > Edit > Create New Service Role > Select the default options and save the role, it should have a name of amplifyconsole-backend-role. Once the role is saved, you can go back to General > Edit > Select your role from the dropdown, if it doesn't show by default start typing it in.
After completing these steps, I was able to successfully redeploy my build and get it pushed to prod with authentication working. Hope it helps anyone who is running into this issue on Module 3 of the AWS Amplify Starter Tutorial!
We are trying to deploy a web job via octopus. We have different eventhub keys saved in the variables and we expect the webjob to pick up the right key depending on the environment that it is being deployed to. Has one one done this before? Any advice on settings up configurations in octopus?
<========== UPDATE ===========>
We were being careless and didn't quite set our octopus process to transform the Configuration Variables. You should be able to do so by clicking 'configure variables' in the process step.
I don't think it being deployed via Octopus is all that relevant here. Generally, a .NET WebJob is able to access Azure App Setting using standard configuration API.
If that is not working for you, please update your question to clarify what you tries, and specifically what didn't work.
I would like to run WSO2 on two hosts, one serves as manager and the other as gateway worker.
I consulted the clustering guide and product profiles documentation, and I understand that after configuring the two hosts correctly, I can run the product with selected profile:
-Dprofile=gateway-manager on the manager node
-Dprofile=gateway-worker on the gateway worker node
In addition to perform selective-run, I would also like the gateway-worker to have the minimal possible deployment, i.e. to be installed only with artifacts it really needs.
Three options I can think of, from best to worst:
Download a minimized deployment package - in case there is one? In the site I saw only complete package which contains artifacts of all the components. Are there other download options which contain selective artifacts per profile?
Download the complete package and then remove the artifacts which are not necessary for gateway-worker (how do I know which files/directories to remove?)
Download the source from github and run a selective build? (which components should I build and how do I package them for deployment)?
There are no separate product packs for each profiles to download. So option 1 is not there. But you can do the option 2 to some extent. You can remove the publisher, store and admin-dashboard application from the product by removing 'jaggeryapps' folder in 'wso2am-1.10.0/repository/deployment/server/' location. Other than that we are not recommending to remove any components from the pack.
You can check the profile generation code for API Manager 1.10 in here. It only has module import definitions. These component are needed to be there for each profile.