I build several websites using react and have deployed them automatically to IONOS using Github workflow so far.
But since a few days ago, I haven't been able to deploy them because of this error;
Trigger creation of temporary user
Failed to create temporary user
I am not sure why this happens and very thankful if anybody could help me with the solution to this issue.
Shouldn't happen. It's our fault. I'm working for IONOS and I'm directly involved in Deploy Now.
So far we use a temporary FTP user for the deployment. Currently we're working on an extended worklflow. Besides we will replace the FTP user and switch to SSH. This will hopefully end such hiccups.
As workaround you can manually re-trigger your GitHub Action.
Sorry for the inconvenience.
Related
I have manually deleted a CI build that uses the MS Hosted ubuntu Agent as there was no Cancel option that was showing up. The elapsed time I think shows the build was deleted, but I see that the Hosted Agent continues to show that the build is in progress.
This is the first time I am running in to this situation. What is the best way to abort this build. I tried using the APIs here and here but that does not seem to help
Thanks
After investigation, there is a recently event of availability degradation of Azure DevOps, which affected these services and it has been resolved now.
If you want to know more information, please click here: https://status.dev.azure.com/_history.
Please check that your Cancel option is back to normal.
Why am I getting this error message for my apps deployed with Github at Heroku?
There is an issue with the GitHub token for this app. Disconnect and reconnect to restore functionality
We had the same issue before, it happened with private repositories and disconnecting/reconnecting from time to time seems to do the trick but after a while we started to grow and we needed more automation.
We looked into all kinds of CI/CD tools like Codeship, CircleCi, etc. Ended up choosing DeployBot and stuck with it because it works really well for us and fitted our needs best.
Either way these tools can be lifesavers for the team no matter which one you end up using
I'm trying to fix up a broken Travis CI build script on a repo I was added to as a contributor. Everything works fine in the actual build, but trying to upload the build results to GitHub is broken.
The .travis.yml file contains an OAuth token which it puts into the Environment, and at the end it runs a script that retrieves this environment variable and uses it to upload the build output to GitHub. This is failing with a 401 Unauthorized error, which means the token is probably no longer valid.
I didn't write this up, and the way this works kind of bugs me. I'm not comfortable having authentication information in the repo, publicly accessible to the world, so it's just as well that this token is expired. But as I look things over, I don't see any better way to do this.
I need to do one of two things, either have the Travis build machine upload the build result to GitHub, or download the build result from Travis and upload it myself. Unfortunately, neither one seems to be a good option. No matter where I look on Travis CI's Web interface, I can't find any download link to retrieve the build results, which seems to rule out the second option. As for the first option, it doesn't appear that there's any way to perform the upload without the build machine having authentication information from the repository.
I can't be the first person to notice how problematic this is. I figure it has to be solved somehow; I'm just not sure how to fix it. Does anyone know how to resolve this?
For whatever range of poor reasons...a user schedule workflow has been uploaded to our YouTrack server instance that now automatically generates seemingly hundreds of new issues a minute.
As you might imagine, the web server is totally unresponsive, meaning that we cannot disable or detach the workflow from the project. The workflow editor's attempts to remove the workflow fail with connection timeouts.
How can the workflow be disabled without accessing the usual admin pages? Is there a workflow file somewhere in the server's directory that can be deleted (I can't find one) while the service is stopped? Is there a "run in safe-mode" option for YouTrack?
We're running YouTrack 5 fwiw.
Thanks in advance.
In YouTrack 6.0 we've implemented special Java start parameter (-Djetbrains.youtrack.workflow.detachModified=true), it will work starting from next bug fix release.
This option will detach all the workflows from all the projects on start, except the unmodified supplied ones.
Please, consider https://youtrack.jetbrains.com/issue/JT-27785, the Fix version of this issue will be changes as soon as we release next bug fix.
Workflows are stored inside YT db, so the best variant for you is to contact YT support. It'll be able to modify the db.
We run 8 EC2 instances behind a load balancer currently (used to run 2 - but our app took off and we have more traffic now)
Our code is deployed on Github.
When we had 2 servers, we easily remote desktop-ed into them and did a git pull.
But that seems insane now considering we have 8 servers and might have more in the future.
This is for an Asp.Net webservice (built over MVC3) deployed on IIS on a Windows 2008 server.
I wanted to know what are the best practices to handle this?
I would ideally love it if I could push to a branch / or a completely new production only repo (if needed) and all the servers get notified and pull the changes.
Worst case, I am thinking of writing a notifier service which does this on each server - but before I dive in and spend time on it, was wondering if there is something available out of the box which would help me get there.
Thanks in advance.
Have you tried using http://octopusdeploy.com/ ?
check webhook
https://help.github.com/articles/post-receive-hooks.
you can write a simple http handler to let github push notification to you.
then you can do whatever you wanna do .